diff options
| author | Karl Berry <karl@freefriends.org> | 2006-12-14 00:56:47 +0000 |
|---|---|---|
| committer | Karl Berry <karl@freefriends.org> | 2006-12-14 00:56:47 +0000 |
| commit | 13328a265ebe4ef58c26ab99e0c071edb0ca0195 (patch) | |
| tree | 604fbea81411a5bda1ff25d9cd6ee5dd75acd761 /Master/texmf-doc/doc | |
| parent | da29691fd87e0073830e9d11a1dccd9725f01cc6 (diff) | |
3.16c+html
git-svn-id: svn://tug.org/texlive/trunk@2723 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-doc/doc')
416 files changed, 6734 insertions, 4509 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/ChangeLog b/Master/texmf-doc/doc/english/FAQ-en/ChangeLog index 00ec5a6ee1c..d71a5483d3a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/ChangeLog +++ b/Master/texmf-doc/doc/english/FAQ-en/ChangeLog @@ -1,3 +1,161 @@ +2006-12-11 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex: v3.16c + + * faq.sty: bludgeon \CTANhref in pdf mode + + * faqbody.tex: v3.16b-6, today + (subsection{Document structure}): put titlesec and sectsty into + different paras, offer rationale for choice om q-secthead + (subsection{LaTeX macro tools and techniques}): mention \@dblarg in + q-oarglikesect + +2006-12-07 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * filectan.tex: shiny new *longer* path for btxmac + +2006-12-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (subsection{Typesetting specialities}): correct typos in + ctanrefs in q-music + +2006-12-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (subsection{Creating citations}): correct reed.edu link, + thanks to barbara b + +2006-11-30 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{Creating bibliographies}): make an itemised + list of alternative styles in q-citeurl, add babelbib to list + +2006-11-28 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{Creating bibliographies}): add two more + examples in q-bibprefixsort + +2006-11-26 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex: v3.16b-5, today + (section{Documentation and Help}): reference kmf's page about pgf/tikz + +2006-11-22 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex: v3.16b-4, today + (subsection{Spacing of characters and lines}): \linestretch -> + \linespread (per ulrike fischer) in q-linespace + +2006-11-20 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{TeX Systems}): correct sciword uk phone nos in + q-commercial + +2006-11-17 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * dirctan.tex: add everypage and draftwatermark; correct wd2latex, + remove wasy and xymtex + + * faqbody.tex (subsection{Page layout}): mention draftwatermark (and + its everypage) in q-watermark + +2006-11-15 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{Graphics}): ctan ref for mptopdf + in q-mpprologues + + * dirctan.tex: add pdftex-graphics + + * faqbody.tex (section{The joy of TeX errors}): mention "h" response + in q-optionclash + +2006-11-14 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * add-general.tex (subsection{Floating tables, figures, etc.}): new + q-figurehere + +2006-11-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (preamble): today's date; input archive.cfg regardless of + whether we're using pdf + + * faq.sty: yet more baroquery towards \CTANhref + +2006-11-13 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{Introduction}): ref to vis faq in "how to use" + + * faq.sty: new command \CTANhref works for dvi version so far; + no longer requires \Status for pdf working, uses ifpdf pkg instead; + a fair bit of more minor tidying + +2006-11-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (subsection{Floating tables, figures, etc.}): example + code in {quote} in q-vertspacefloat and q-mcfloat + +2006-11-06 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{Tables, figures and diagrams}): mention the + case of multirow-multicolumn in q-multirow + (subsection{"Generic" macros and techniques}): new q-isdef from + add-general + +2006-11-03 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * sanitize-beta.pl (sanitize_line): correct \cmdinvoke{c}{arg1}{arg2} + sanitize.pl (sanitize_line): -beta works, so correct here too + +06-11-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * add-general.tex (subsection{"Generic" macros and techniques}): bunch + of editorials in q-isdef + (subsection{"Generic" macros and techniques}): tidy narrow layout of + example, add wide version and hack at words a bit in q-ovwtsym + +2006-10-31 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * add-general.tex (subsection{Generic macros}): \csx{relax} in place of + \relax(!) in q-isdef + + * dirctan.tex: add pspicture + + * faqbody.tex (section{Graphics}): correct ctan ref for pspicture + +2006-10-31 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex: today's date, v3.16b-3 + (subsection{LaTeX macro programming}): dot \makeat* liberally around + examples in q-running-nos + +2006-10-23 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{Page layout}): draftcopy doesn't work with + pdflatex (in q-watermark) + +2006-10-19 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex: version 3.16b-2, date now iso format (with hyphens) + + * patchdates.tex: pl4.13, date now iso format (with hyphens) + + * add-general.tex (subsection{Generic macros and techniques}): new + q-ovwtsym from a post by enrico gregorio (latest instance of an + oft-repeated answer) + +2006-10-05 Robin Fairbairns <rf10@pb000.cl.cam.ac.uk> + + * Makefile.CTAN: basis of mechanism to install CHANGES files + +2006-10-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * texfaq2html: sigh...merge in intro patch from texfaq2html-beta + + * dirctan.tex: add figflow + + * faqbody.tex: v3.16c, today + (subsection{Tables, figures and diagrams}): add figflow for plain, tidy + some of the ghastly verbatim in q-textflow + 2006-10-04 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> * faqbody.tex: 3.16b-1, today diff --git a/Master/texmf-doc/doc/english/FAQ-en/dirctan.tex b/Master/texmf-doc/doc/english/FAQ-en/dirctan.tex index fe01ededb1e..c128687850d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/dirctan.tex +++ b/Master/texmf-doc/doc/english/FAQ-en/dirctan.tex @@ -260,6 +260,7 @@ \CTANdirectory{dpfloat}{macros/latex/contrib/dpfloat} \CTANdirectory{dpmigcc}{systems/msdos/dpmigcc} \CTANdirectory{draftcopy}{macros/latex/contrib/draftcopy} +\CTANdirectory{draftwatermark}{macros/latex/contrib/draftwatermark} \CTANdirectory{dratex}{graphics/dratex} \CTANdirectory{drawing}{graphics/drawing} \CTANdirectory{dropcaps}{macros/latex209/contrib/dropcaps} @@ -337,6 +338,7 @@ \CTANdirectory{eurofont}{macros/latex/contrib/eurofont} \CTANdirectory{europecv}{macros/latex/contrib/europecv} \CTANdirectory{eurosym}{fonts/eurosym} +\CTANdirectory{everypage}{macros/latex/contrib/everypage} \CTANdirectory{excalibur}{systems/mac/support/excalibur} \CTANdirectory{excerpt}{web/spiderweb/tools/excerpt} \CTANdirectory{expdlist}{macros/latex/contrib/expdlist} @@ -646,6 +648,7 @@ \CTANdirectory{pbox}{macros/latex/contrib/pbox} \CTANdirectory{pcwritex}{support/pcwritex} \CTANdirectory{pdfpages}{macros/latex/contrib/pdfpages} +\CTANdirectory{pdftex-graphics}{macros/pdftex/graphics} \CTANdirectory{pdftricks}{macros/latex/contrib/pdftricks} \CTANdirectory{penelope}{web/spiderweb/src/penelope} \CTANdirectory{pfm2afm}{fonts/utilities/pfm2afm} @@ -698,6 +701,7 @@ \CTANdirectory{psnfss}{macros/latex/required/psnfss} \CTANdirectory{psnfss-addons}{macros/latex/contrib/psnfss-addons} \CTANdirectory{psnfssx-mathtime}{macros/latex/contrib/psnfssx/mathtime} +\CTANdirectory{pspicture}{macros/latex/contrib/pspicture} \CTANdirectory{psprint}{dviware/psprint} \CTANdirectory{pst-pdf}{macros/latex/contrib/pst-pdf} \CTANdirectory{pstab}{support/pstab} @@ -944,10 +948,9 @@ \CTANdirectory{w2latex}{support/w2latex} \CTANdirectory{wallpaper}{macros/latex/contrib/wallpaper} \CTANdirectory{was}{macros/latex/contrib/was} -\CTANdirectory{wasy}{fonts/wasy} \CTANdirectory{wasy2}{fonts/wasy2} \CTANdirectory{wasysym}{macros/latex/contrib/wasysym} -\CTANdirectory{wd2latex}{dviware/wd2latex} +\CTANdirectory{wd2latex}{support/wd2latex} \CTANdirectory{web}{systems/knuth/web} \CTANdirectory{web2c}{systems/web2c} \CTANdirectory*{web2c*}{systems/web2c} @@ -973,10 +976,14 @@ \CTANdirectory{xmltex}{macros/xmltex/base} \CTANdirectory*{xpdf}{support/xpdf} \CTANdirectory{xtab}{macros/latex/contrib/xtab} -\CTANdirectory{xymtex}{macros/latex/contrib/xymtex} \CTANdirectory{xypic}{macros/generic/diagrams/xypic} \CTANdirectory{yhmath-fonts}{fonts/yhmath} \CTANdirectory{yhmath-macros}{macros/latex/contrib/yhmath} \CTANdirectory{zefonts}{fonts/zefonts} \CTANdirectory{zoon-mp-eg}{info/metapost/examples} \endinput + +%%% Local Variables: +%%% mode: plain-tex +%%% TeX-master: "faqbody" +%%% End: diff --git a/Master/texmf-doc/doc/english/FAQ-en/faq.sty b/Master/texmf-doc/doc/english/FAQ-en/faq.sty index 45ab038250d..f46ecaf735f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/faq.sty +++ b/Master/texmf-doc/doc/english/FAQ-en/faq.sty @@ -3,6 +3,7 @@ % uses production LaTeX 2e commands \NeedsTeXFormat{LaTeX2e}[1994/06/01]% at least! \ProvidesPackage{faq}[2002/10/01 v2.3 English TeX FAQ macros] + % % something affecting fonts: do we use only freely available fonts % (i.e., are we going to make the postscript of this publicly @@ -34,35 +35,23 @@ \DeclareRobustCommand\acro[1]{##1\@{}} } +% debugging (requires etex, like much of this package) +%\tracingifs=1 + % suppress bold maths if they're not available \ifboldmathavail\else\let\boldmath\@empty\fi % -% switches (potentially) to be set according to status -\newif\ifpdf +% true for pdf output \newif\ifsinglecolumn -% -% Status values -\providecommand{\Status}{0} -\ifcase\Status\relax - % 0: default case is do nothing -% \typeout{faq.sty: default output using \ifprivate private\else -% public\fi\space fonts} - \singlecolumnfalse - \pdffalse -\or - % 1: pdf output using public fonts - \typeout{faq.sty: 1-col pdf output using public fonts} - \singlecolumntrue - \pdftrue - \let\multicols\@gobble - \let\endmulticols\relax -\or - % 2: pdf output using public fonts, two columns - \typeout{faq.sty: 2-col pdf output using public fonts} - \singlecolumnfalse - \pdftrue +\RequirePackage{ifpdf} +\ifpdf + \PackageInfo{faq}{1-column PDF output\@gobble} + \expandafter\singlecolumntrue +\else + \PackageInfo{faq}{2-column DVI output\@gobble} + \expandafter\singlecolumnfalse \fi % @@ -167,7 +156,7 @@ % tables are all long'uns \RequirePackage{booktabs} % -% we define html only stuff using Eijkhout's package +% we define conditional stuff using Eijkhout's package \RequirePackage{comment} \excludecomment{htmlversion} \ifpdf @@ -182,8 +171,16 @@ \excludecomment{wideversion} \fi % -% but we also want a `short' version, like LaTeX2HTML's +% but we also want short versions, like LaTeX2HTML's \let\htmlonly\@gobble +\let\nothtml\@firstofone +\let\latexhtml\@firstoftwo +% +% the little bit(s) of code that's(re) going to be ignored when the +% html is generated are enclosed by the following two commands +\let\htmlignore\relax +\let\endhtmlignore\relax + % % the Baskerville and other logos and abbreviations \providecommand\BV{\emph{Baskerville}} @@ -439,9 +436,7 @@ % deleted from comments 2000/03/24) \newcommand\Email{\begingroup \urlstyle{tt}\Url} % email address \ifpdf -\def\mailto{\@ifnextchar|\@mailto@vert\@mailto@brace} % url to mail somewhere -\def\@mailto@vert|#1|{\href{mailto:#1}{\Email{#1}}} -\def\@mailto@brace#1{\href{mailto:#1}{\Email{#1}}} +\def\mailto#1{\href{mailto:#1}{\Email{#1}}} \else \newcommand\mailto{\begingroup \urlstyle{tt}\Url} % mailable address \fi @@ -564,15 +559,15 @@ \newcommand{\@CTANdirectory}[2]{\@ifundefined{ctan-#1}{% \expandafter\gdef\csname ctan-#1\endcsname{\@CTAN\LocalCTAN{#2}\CTANDirFmt}% }{% - \PackageWarningNoLine{faq}{Repeated definition of label: #1}% - \stepcounter{CTAN@replabs}% + \PackageWarningNoLine{faq}{Repeated definition of label: #1}% + \stepcounter{CTAN@replabs}% }} \ifpdf \newcommand{\@sCTANdirectory}[2]{\@ifundefined{ctan-#1}{% \expandafter\gdef\csname ctan-#1\endcsname{\@CTAN\LocalCTAN{#2}/}% }{% - \PackageWarningNoLine{faq}{Repeated definition of label: #1}% - \stepcounter{CTAN@replabs}% + \PackageWarningNoLine{faq}{Repeated definition of label: #1}% + \stepcounter{CTAN@replabs}% }} \fi % @@ -600,10 +595,32 @@ \PackageWarning{CTAN}{Undefined reference: #1}% \stepcounter{CTAN@unrefs}% }{% -% \edef\@tempa{\noexpand\CTAN{\csname ctan-#1\endcsname}}\@tempa \csname ctan-#1\endcsname }} % +% href to a ctan package +\ifpdf + \DeclareRobustCommand{\CTANhref}[2]{\@ifundefined{ctan-#1}{% + \PackageWarning{CTAN}{Undefined reference: #1}% + \stepcounter{CTAN@unrefs}% + }{{% + \def\@CTAN##1##2##3{http://www.tex.ac.uk/tex-archive/##2}% + \href{\csname ctan-#1\endcsname}{#2}% + }}} +\else % DVI version + \DeclareRobustCommand{\CTANhref}[2]{\@ifundefined{ctan-#1}{% + \PackageWarning{CTAN}{Undefined reference: #1}% + \stepcounter{CTAN@unrefs}% + }{{% + \def\@ctan@path##1{\expandafter\httpify\LocalCTAN!##1} + \edef\@tempa{\csname ctan-#1\endcsname}% + \expandafter\href\expandafter{\@tempa}{#2}% + }}} +\fi +% +% this is surely temporary +\def\httpify ftp://ftp#1!{http://www#1} +% % hook for diagnosing undefined references at the end \AtEndDocument{\ifthenelse{\theCTAN@unrefs > 0}{% \PackageWarningNoLine{ctan}{There were \arabic{CTAN@unrefs} undefined @@ -702,17 +719,6 @@ \xspaceskip=.5em\relax \hangindent=1pc\relax} % -% the little bit(s) of code that's(re) going to be ignored when the -% html is generated are enclosed by the following two commands -\let\htmlignore\relax -\let\endhtmlignore\relax -% -% or it's the argument to \nothtml -\newcommand\nothtml[1]{#1} -% -% a trivium that appears differently in the two modes -\newcommand\latexhtml[2]{#1} -% % things needed for the benefit of texfaq2html's `sanitise_line' \let\textpercent\% \let\faq@@textbar\textbar diff --git a/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex b/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex index 01bf67ffedf..f0d68addcb0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex +++ b/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex @@ -1,4 +1,4 @@ -\def\faqfileversion{3.16b-1} \def\faqfiledate{2006/10/04} +\def\faqfileversion{3.16c} \def\faqfiledate{2006-12-11} % % The above line defines the file version, and must remain the first % line with any `assignment' in the file, or things will blow up @@ -8,9 +8,7 @@ % % configuration for the lists, if we're going to need to generate urls % for the files -\ifpdf \InputIfFileExists{archive.cfg}{}{} -\fi % % ... directories \input{dirctan} @@ -35,7 +33,8 @@ You may use the \acro{FAQ} \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. + search restricted to the \acro{FAQ} itself, or +\item via Scott Pakin's \CTANhref{visualFAQ}{Visual FAQ}. \end{itemize} \begin{htmlversion} @@ -107,7 +106,7 @@ Michael Downes, % (RIP) on (ams)maths stuff Jean-Pierre Drucbert, % corrected my interpretation of minitoc Thomas Esser, Ulrike Fischer, % spotted boondoggle in q-tabcellalign - % args like \section improvement + % args like \section improvement; general typos Anthony Goreham, Norman Gray, Eitan Gurari, % comparative html translators @@ -1540,6 +1539,13 @@ excellent introduction to graphics use. It's available on \acro{CTAN}, but the sources aren't available (promised ``some time soon''). +Kjell Magne Fauske offers a set of examples of the use of the drawing +packages % ! line break +\Qref*{\acro{PGF} and \acro{T}ik\acro{Z}}{Q-drawing}; the % ! line break +\href{http://www.fauskes.net/pgftikzexamples/}{examples catalogue} +includes examples (with output) from the package documentation as well +as code written by the author himself. + Vincent Zoonekynd provides a set of excellent (and graphic) tutorials on the programming of % !line breaks, ... \href{http://zoonek.free.fr/LaTeX/LaTeX_samples_title/0.html}{title page styles}, @@ -1812,6 +1818,12 @@ itself be formatted with \LaTeX{}). Classes that are not part of the distribution are commonly based on ones that are, and start by loading the standard class with \csx{LoadClass}~--- an example of this technique may be seen in \Package{ltxguide.cls} + +An % !!! line break +\href{http://www.tug.org/pracjourn/2006-4/flynn/flynn.pdf}{annotated version of \Class{article}}, +as it appears in \File{classes.dtx}, was published in the Prac\TeX{} +Journal 2006, No.\,4. The article is by Peter Flynn, and offers a +slightly easier way in to understanding \File{classes.dtx} \begin{ctanrefs} \item[classes.dtx]\CTANref{latex-classes} \item[ltxguide.cls]\CTANref{ltxguide} @@ -3315,8 +3327,7 @@ also have email, and normal telephone and fax support. East Lothian, \acro{EH}33 1\acro{AS}\\ \acro{UK}\\[0.25\baselineskip] Tel: 0845 766\,0340 (within the \acro{UK}) \\ - Tel: +44 1875 616516 \\ - Fax: 01875 613513 (within the \acro{UK}) \\ + Fax: 0845 603\,9443 (within the \acro{UK}) \\ Email: \mailto{christopher@sciword.demon.co.uk} \\ Web: \URL{http://www.sciword.demon.co.uk} \end{quote} @@ -7093,6 +7104,7 @@ the question\dots{} \begin{ctanrefs} \item[mps2eps]\CTANref{mps2eps} \item[mpsproof.tex]\CTANref{mpsproof} +\item[mptopdf]Part of \CTANref{pdftex-graphics} \end{ctanrefs} \Question[Q-drawing]{Drawing with \TeX{}} @@ -7161,7 +7173,7 @@ of drawing, and setup, here are a few systems you may consider: \item[dratex.sty]\CTANref{dratex} \item[mfpic]\CTANref{mfpic} \item[pdftricks.sty]\CTANref{pdftricks} -\item[pspicture.sty]Distributed as part of \CTANref{carlisle} +\item[pspicture.sty]\CTANref{pspicture} \item[pgf.sty]\CTANref{pgf} \item[pict2e.sty]\CTANref{pict2e} \item[pstricks]\CTANref{pstricks} @@ -7605,21 +7617,25 @@ entry will look like: \end{quote} A possible alternative approach is to use \BibTeX{} styles other than the standard ones, that already have \acro{URL} entry types. -Pre-eminent are the \Package{natbib} styles (\Package{plainnat}, -\Package{unsrtnat} and \Package{abbrevnat}). These styles are -extensions of the standard styles, principally for use with -\Package{natbib} itself, but they've acquired \acro{URL}s and other -``modern'' entries along the way. The same author's -\Package{custom-bib} is also capable of generating styles that honour -\acro{URL} entries. - -Another candidate is the \Package{harvard} package (if its citation -styles are otherwise satisfactory for you). \Package{Harvard} -bibliography styles all include a ``|url|'' field in their -specification; however, the typesetting offered is somewhat feeble -(though it does recognise and use \ProgName{LaTeX2HTML} macros if they -are available, to create hyperlinks). - +Candidates are: +\begin{itemize} +\item The \Package{natbib} styles (\Package{plainnat}, + \Package{unsrtnat} and \Package{abbrevnat}), which are extensions of + the standard styles, principally for use with \Package{natbib} + itself. However, they've acquired \acro{URL}s and other ``modern'' + entries along the way. The same author's \Package{custom-bib} is + also capable of generating styles that honour \acro{URL} entries. +\item The \Package{babelbib} bundle, which offers % ! line break + \Qref*{multilingual bibliographies}{Q-i18nbib}, similarly provides a + set of standard-style equivalents that have \acro{URL} entries. +\item More modern styles such as the \Package{harvard} package (if the + citation styles are otherwise satisfactory for you). + \Package{Harvard} bibliography styles all include a ``\texttt{url}'' + field in their specification; however, the typesetting offered is + somewhat feeble (though it does recognise and use + \ProgName{LaTeX2HTML} macros if they are available, to create + hyperlinks). +\end{itemize} You can also acquire new \BibTeX{} styles by use of Norman Gray's \Package{urlbst} system, which is based on a \ProgName{Perl} script that edits an existing \BibTeX{} style file to produce a new @@ -7661,6 +7677,7 @@ is an acceptable character in an \acro{URL}. Any current version of the ``\texttt{\textpercent}--end-of-line'' structure in its argument, and removes it. \begin{ctanrefs} +\item[babelbib \nothtml{\rmfamily}bundle]\CTANref{babelbib} \item[custom-bib \nothtml{\rmfamily}bundle]\CTANref{custom-bib} \item[harvard.sty]\CTANref{harvard} \item[hyperref.sty]\CTANref{hyperref} @@ -7731,21 +7748,68 @@ follows: @ARTICLE{Rayleigh1, AUTHOR = "{\noopsort{Rayleigh}}{Lord Rayleigh}", ... +} \end{verbatim} \end{wideversion} \begin{narrowversion} \begin{verbatim} @PREAMBLE{ {\providecommand{\noopsort}[1]{}} - } +} ... @ARTICLE{Rayleigh1, AUTHOR = "\noopsort{Rayleigh}{Lord Rayleigh}", ... +} \end{verbatim} \end{narrowversion} \end{quote} +Note that this \csx{noopsort} applies to the last name in this kind of +construct, so an author with an Arabic name might be rendered: +\begin{wideversion} +\begin{quote} +\begin{verbatim} +... +AUTHOR = "Ali {\noopsort{Hadiidii}}{al-Hadiidii}", +... +\end{verbatim} +\end{quote} +\end{wideversion} +\begin{narrowversion} +\begin{quote} +\begin{verbatim} +... +AUTHOR = + "Ali {\noopsort{Hadiidii}}{al-Hadiidii}", +... +\end{verbatim} +\end{quote} +\end{narrowversion} +A further use might deal with word order games, as in the famous +Vietnamese name: +\begin{wideversion} +\begin{quote} +\begin{verbatim} +... +AUTHOR = "\noopsort{Thanh Han The}{Han The Thanh}", +... +\end{verbatim} +\end{quote} +\end{wideversion} +\begin{narrowversion} +\begin{quote} +\begin{verbatim} +... +AUTHOR = + "\noopsort{Thanh Han The}{Han The Thanh}", +... +\end{verbatim} +\end{quote} +\end{narrowversion} +though that author seems well-acquainted with Western confusion about +the significance of the parts of his name (even to the extent of +missing out the accentuation, as above\dots{}). \Question[Q-bibtranscinit]{Transcribed initials in \BibTeX{}} @@ -7947,12 +8011,12 @@ Fortunately, help is at hand, on the Web, with this problem: sorted into their nominal topics as well as providing a good range of examples, is the Reed College % ! line break \begin{narrowversion} - ``Bibliographies in \LaTeX{}'' - (\URL{http://web.reed.edu/cis/help/BibTeXstandard.html}). + ``Choosing a \BibTeX{} style'' + (\URL{http://web.reed.edu/cis/help/LaTeX/bibtexstyles.html}). \end{narrowversion} \begin{wideversion} % ! line break - ``\href{http://web.reed.edu/cis/help/BibTeXstandard.html}{Bibliographies in \LaTeX{}}''. + ``\href{http://web.reed.edu/cis/help/LaTeX/bibtexstyles.html}{Choosing a \BibTeX{} style}''. \end{wideversion} \end{itemize} @@ -9017,12 +9081,16 @@ and then use \csx{ssection} and \csx{ssubsection} in place of \csx{section} and \csx{subsection}. This isn't perfect: section numbers remain in bold, and starred forms need a separate redefinition. -The package \Package{sectsty} provides an easy-to-use set of tools to -do this job, while the package \Package{titlesec} has a structured -approach based on redefinition of the sectioning and chapter commands -themselves. \Package{Titlesec}'s approach allows it to offer far more -radical adjustment: its options provide (in effect) a toolbox for -designing your own sectioning commands' output. +The \Package{titlesec} package offers a structured approach to the +problem, based on redefinition of the sectioning and chapter commands +themselves. This approach allows it to offer radical adjustment: its +options provide (in effect) a toolbox for designing your own +sectioning commands' output. + +The \Package{sectsty} package provides a more simply structured set of +tools; while it is less powerful than is \Package{titlesec}, it is +perhaps preferable for minor adjustments, since you can use it after +having read a smaller proportion of the manual. The \Package{fncychap} package provides a nice collection of customised chapter heading designs. The \Package{anonchap} package provides a @@ -9636,9 +9704,9 @@ those situations: even if your corrections add a whole page to the chapter, the most you have to redistribute is that chapter.) The problem, at first sight, seems pretty much the same as that in -another answer on \nothtml{running numbers within a chapter (}% +another answer on % beware line break -\Qref[question]{running numbers within a chapter}{Q-running-nos}\nothtml{)}, +\Qref*{running numbers within a chapter}{Q-running-nos}, and the basic technique is indeed pretty similar. However, tidying-up loose ends, making sure the page number gets reset @@ -10025,24 +10093,38 @@ be achieved with the \Package{draftcopy} package. This can deal with many types of \acro{DVI} processors (in the same way that the graphics package does) and knows translations for the word `DRAFT' into a wide range of languages (though you can choose your own word, too). +Unfortunately, however, the package relies on \PS{} specials, and will +therefore fail if you are viewing your document with \ProgName{xdvi}, +and won't even compile if you're using \PDFLaTeX{}. (\PDFLaTeX{} +users need one of the other solutions below.) + +The \Package{wallpaper} package builds on \Package{eso-pic} (see +below). Apart from the single-image backdrops described above +(``wallpapers'', of course, to this package), the package provides +facilities for tiling images. All its commands come in pairs: one for +``general'' use, and one applying to the current page only. + +The \Package{draftwatermark} package uses the same author's +\Package{everypage} package to provide a simple interface for adding +textual (`DRAFT'-like) watermarks. More elaborate watermarks may be achieved using the \Package{eso-pic} -package, which in turn uses the package \Package{everyshi}, part of -Martin Schr\"oder's \Package{ms} bundle. \Package{Eso-pic} attaches a +package, which in turn uses the package \Package{everyshi}, or by +using \Package{everypage}. \Package{Eso-pic} attaches a \environment{picture} environment to every page as it is shipped out; you can put things into that environment. The package provides commands for placing things at certain useful points (like ``text upper left'' or ``text centre'') in the picture, but you're at liberty to do what you like. -The \Package{wallpaper} package builds, as above, on -\Package{eso-pic}. Apart from the single-image backdrops described -above (``wallpapers'', of course, to this package), the package -provides facilities for tiling images. All its commands come in -pairs: on for ``general'' use, and one applying to the current page only. +\Package{Everypage} allows you to add ``something'' to every page, or +to a particular page; you therefore need to construct your own +apparatus for anything complicated. \begin{ctanrefs} \item[draftcopy.sty]\CTANref{draftcopy} +\item[draftwatermark.sty]\CTANref{draftwatermark} \item[eso-pic.sty]\CTANref{eso-pic} +\item[everypage.sty]\CTANref{everypage} \item[everyshi.sty]Distributed as part of \CTANref{ms} \item[wallpaper.sty]\CTANref{wallpaper} \end{ctanrefs} @@ -10440,7 +10522,7 @@ version 6.0 onwards) you have installed: \Question[Q-linespace]{Double-spaced documents in \LaTeX{}} A quick and easy way of getting inter-line space for copy-editing is -to change \csx{baselinestretch}~--- \cmdinvoke{linestretch}{1.2} (or, +to change \csx{baselinestretch}~--- \cmdinvoke{linespread}{1.2} (or, equivalently \cmdinvoke{renewcommand}{\csx{baselinestretch}}{1.2}) may be adequate. Note that \csx{baselinestretch} changes don't take effect until you select a new font, so make the change in the preamble @@ -11082,16 +11164,15 @@ documents is \href{http://www.lilypond.org}{Lilypond}. Lilypond is does most of its work without TeX. Lilypond's input syntax is far less cryptic than is Musix\TeX{}'s, and it handles much more stuff automatically, yielding the same or better quality with less effort. -Lilypond can also produce basic \acro{MIDI} oputput. +Lilypond can also produce basic \acro{MIDI} output. \begin{ctanrefs} \item[abc2mtex]\CTANref{abc2mtex} \item[M-Tx]\CTANref{mtx} \item[midi2tex]\CTANref{midi2tex} \item[musictex]\CTANref{musictex} -\item[musixtex \nothtml{\rmfamily}(Taupin's - version)]\CTANref{musixtex-taupin} -\item[musixtex \nothtml{\rmfamily}(Egler's - version)]\CTANref{musixtex-egler} +% ! line breaks +\item[musixtex \nothtml{\rmfamily}(Taupin's version)]\CTANref{musixtex-taupin} +\item[musixtex \nothtml{\rmfamily}(Egler's version)]\CTANref{musixtex-egler} \item[mutex]\CTANref{mutex} \item[pmx]\CTANref{pmx} \end{ctanrefs} @@ -13491,6 +13572,38 @@ down one or other side of a table (with the help of the (which gives text going upwards; use angle |-90| for text going downwards, of course). +To make a \csx{multicolumn} multi-row ``cell'' in a table, you have to +enclose a \csx{multirow} inside a \csx{multicolumn}~--- the other way +around does not work, so: +\begin{quote} +\begin{wideversion} +\begin{verbatim} +\begin{tabular}{|c|c|c|}\hline +\multicolumn{2}{|c|}{\multirow{2}{*}{combined cells}} + &top right\\ \cline{3-3} +\multicolumn{2}{|c|}{} + &middle right\\ \hline +bottom left + &bottom center + &bottom right\\ \hline +\end{tabular} +\end{verbatim} +\end{wideversion} +\begin{narrowversion} +\begin{verbatim} +\begin{tabular}{|c|c|c|}\hline +\multicolumn{2}{|c|}{\multirow{2}{*}% + {combined cells}} + &top right\\ \cline{3-3} +\multicolumn{2}{|c|}{} + &middle right\\ \hline +bottom left + &bottom center + &bottom right\\ \hline +\end{tabular} +\end{verbatim} +\end{narrowversion} +\end{quote} \Package{Multirow} is set up to interact with the \Package{bigstrut} package (which is also discussed in the answer to % beware line break \Qref[question]{spacing lines in tables}{Q-struttab}). You use an @@ -13550,15 +13663,18 @@ list-handling code; and lists always separate themselves from the material around them. Meanwhile, there are parameters provided to adjust the spacing between floating environments and their surroundings; so if we have: +\begin{quote} \begin{verbatim} \begin{figure} \begin{center} \includegraphics{...} - \caption{...} + \caption{...} \end{center} \end{figure} \end{verbatim} +\end{quote} \nothtml{\noindent}or worse still: +\begin{quote} \begin{verbatim} \begin{figure} \begin{center} @@ -13567,17 +13683,21 @@ surroundings; so if we have: \caption{...} \end{figure} \end{verbatim} +\end{quote} unwarranted vertical space is going to appear. The solution is to let the float and the objects in it position themselves, and to use ``generic'' layout commands rather than their list-based encapsulations. +\begin{quote} \begin{verbatim} \begin{figure} - \centering \includegraphics{...} - \caption{...} + \centering + \includegraphics{...} + \caption{...} \end{figure} \end{verbatim} +\end{quote} (which even involves less typing). This alternative code will work with any \LaTeX{} package. It will @@ -13588,7 +13708,7 @@ genesis of \csx{includegraphics}. \Question[Q-2colfloat]{Placing two-column floats at bottom of page} -You specified placement `|[htbp]|' for your full-width figure or +You specified placement `\texttt{[htbp]}' for your full-width figure or table, but they always get placed at the top of the page\dots{} Well, it \emph{is} what the documentation says: \LaTeX{}, unadorned, only allows full-width floats at the top of a page, or occupying (part of) a @@ -13628,18 +13748,22 @@ something approximating the effect it would have.) \Question[Q-mcfloat]{Floats in multicolumn setting} If you use +\begin{quote} \begin{verbatim} \begin{figure} ... \end{figure} \end{verbatim} +\end{quote} in a \environment{multicols} environment, the figure won't appear. If instead you use +\begin{quote} \begin{verbatim} \begin{figure*} ... \end{figure*} \end{verbatim} +\end{quote} the figure will stretch right across the page (just the same as a \environment{figure*} in standard \LaTeX{}'s |twocolumn| option). @@ -14507,8 +14631,8 @@ following minimal solution: \begin{wideversion} \begin{verbatim} \def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}} -\RCS$Revision: 1.409 $ % or any RCS keyword -\RCS$Date: 2006/10/05 07:24:34 $ +\RCS$Revision: 1.423 $ % or any RCS keyword +\RCS$Date: 2006/12/11 23:23:07 $ ... \date{Revision \RCSRevision, \RCSDate} \end{verbatim} @@ -14518,8 +14642,8 @@ following minimal solution: \def\RCS$#1: #2 ${\expandafter \def\csname RCS#1\endcsname{#2}% } -\RCS$Revision: 1.409 $ % or any RCS keyword -\RCS$Date: 2006/10/05 07:24:34 $ +\RCS$Revision: 1.423 $ % or any RCS keyword +\RCS$Date: 2006/12/11 23:23:07 $ ... \date{Revision \RCSRevision, \RCSDate} \end{verbatim} @@ -16820,6 +16944,110 @@ and away we go. The form \csx{mypkg@...} is (sort of) blessed for \LaTeX{} package internal names, which is why this example uses macros of that form. +\Question[Q-isdef]{Is this command defined?} + +Macro sets from the earliest days of \TeX{} programming may be +observed to test whether commands exist by using +\begin{quote} +\csx{ifx} \csx{}\texttt{\emph{command}} \csx{undefined} \meta{stuff} \dots{} +\end{quote} +(which of course actually tests that the command \emph{doesn't} +exist). \LaTeX{} programmers can make use of the internal command +\begin{quote} + \cmdinvoke*{@ifundefined}{cmd name}{action1}{action2} +\end{quote} +which executes \texttt{action1} if the command is undefined, and +\texttt{action2} if it is defined +(\emph{cmd name} is the command name only, omitting the `|\|' character). + +The \csx{@ifundefined} command is based on the sequence +\begin{quote} +\begin{narrowversion} +\begin{verbatim} +\expandafter + \ifx\csname cmd name\endcsname\relax +\end{verbatim} +\end{narrowversion} +\begin{wideversion} +\begin{verbatim} +\expandafter \ifx \csname cmd name\endcsname \relax +\end{verbatim} +\end{wideversion} +\end{quote} +which relies on the way \csx{csname} works: if the command doesn't +exist, it simply creates it as an alias for \csx{relax}. + +So: what is wrong with these techniques? + +Using \csx{undefined} blithely assumes that the command is indeed not +defined. This isn't entirely safe; one could make the name more +improbable, but that may simply make it more difficult to spot a +problem when things go wrong. \LaTeX{} programmers who use the +technique will typically employ \csx{@undefined}, adding a single +level of obscurity. + +The \csx{@ifundefined} mechanism has the unfortunate property of +polluting the name space: each test that turns out undefined adds a +name to the set \TeX{} is holding, and often all those ``\csx{relax}'' +names serve no purpose whatever. Even so (sadly) there are places in +the code of \LaTeX{} where the existence of the \csx{relax} is relied +upon, after the test, so we can't get away from \csx{@ifundefined} +altogether. + +David Kastrup offers the (rather tricky) +\begin{quote} +\begin{wideversion} +\begin{verbatim} +{\expandafter}\expandafter\ifx \csname cmd name\endcsname\relax ... +\end{verbatim} +\end{wideversion} +\begin{narrowversion} +\begin{verbatim} +{\expandafter}\expandafter + \ifx \csname cmd name\endcsname \relax ... +\end{verbatim} +\end{narrowversion} +\end{quote} +which ``creates'' the \csx{relax}-command inside the group of the first +\csx{expandafter}, therefore forgets it again once the test is done. +The test is about as good as you can do with macros. + +The \Qref*{\eTeX{} system}{Q-etex} system comes to our help here: it +defines two new primitives: +\begin{itemize} +\item \csx{ifdefined}, which tests whether a thing is defined (the + negative of comparing with \csx{undefined}, as it were), and +\item \csx{ifcsname} \texttt{cmd name}\csx{endcsname}, which does the + negative of \csx{@ifundefined} without the \csx{relax}-command + side-effect. +\end{itemize} +So, in an \eTeX{}-based system, the following two conditional clauses do +the same thing: +\begin{quote} +\begin{verbatim} +\ifdefined\foo + \message{\string\foo\space is defined}% +\else + \message{no command \string\foo}% +\fi +% +\ifcsname foo\endcsname + \message{\string\foo\space is defined}% +\else + \message{no command \string\foo}% +\fi +\end{verbatim} +\end{quote} +However, after using the \LaTeX{} +\cmdinvoke{@ifundefined}{foo}\dots{}, the conditionals will detect the +command as ``existing'' (since it has been \csx{let} to \csx{relax}); +so it is important not to mix mechanisms for detecting the state of a +command. + +Since most distributions nowadays use \eTeX{} as their base executable +for most packages, these two primitives may be expected appear widely +in new macro packages. + \subsection{\LaTeX{} macro tools and techniques} \Question[Q-plninltx]{Using Plain or primitive commands in \LaTeX{}} @@ -17159,6 +17387,7 @@ mandatory argument, but \csx{newcommand} requires that you `know' the value of the default beforehand. The requisite trick is to use a macro in the optional argument: +\begin{quote} \begin{verbatim} \documentclass{article} \newcommand\thing[2][\DefaultOpt]{% @@ -17171,6 +17400,21 @@ The requisite trick is to use a macro in the optional argument: \thing[opti]{manda}% #1="opti" \end{document} \end{verbatim} +\end{quote} +\LaTeX{} itself has a trickier (but less readily understandable) +method, using a macro \csx{@dblarg}; inside \LaTeX{}, the example +above would have been programmed: +\begin{quote} +\begin{verbatim} +\newcommand\thing{\@dblarg\@thing} +\newcommand\@thing[2][\@error]{% + optional arg: #1, mandatory arg: #2% +} +\end{verbatim} +\end{quote} +In that code, \csx{@thing} is only ever called with an optional and a +mandatory argument; if the default from the \csx{newcommand} is +invoked, a bug in user code has bitten\dots{} \Question[Q-twooptarg]{More than one optional argument} @@ -17576,12 +17820,14 @@ writes something like: \begin{verbatim} \makeatletter \@removefromreset{figure}{chapter} +\makeatother \end{verbatim} \end{quote} -and the automatic renumbering stops. You then need to redefine the +and the automatic renumbering stops. You may then need to redefine the way in which the figure number (in this case) is printed: \begin{quote} \begin{verbatim} +\makeatletter \renewcommand{\thefigure}{\@arabic\c@figure} \makeatother \end{verbatim} @@ -17596,17 +17842,21 @@ numbered per chapter, try: \begin{quote} \begin{wideversion} \begin{verbatim} +\makeatletter \@removefromreset{figure}{section} \@addtoreset{figure}{chapter} \renewcommand{\thefigure}{\thechapter.\@arabic\c@figure} +\makeatother \end{verbatim} \end{wideversion} \begin{narrowversion} \begin{verbatim} +\makeatletter \@removefromreset{figure}{section} \@addtoreset{figure}{chapter} \renewcommand{\thefigure}% {\thechapter.\@arabic\c@figure} +\makeatother \end{verbatim} \end{narrowversion} \end{quote} @@ -18743,7 +18993,7 @@ are needed. \begin{ctanrefs} \item[dblfloatfix.sty]\CTANref{dblfloatfix} \item[fix2col.sty]Distributed as part of \CTANref{carlisle} -\item[fixltx2e.sty]Part of the \LaTeX{} distribution. +\item[fixltx2e.sty]Part of the \LaTeX{} distribution \end{ctanrefs} \Question[Q-tabacc]{Accents misbehave in \environment{tabbing}} @@ -21847,8 +22097,9 @@ which could quite reasonably (and indeed correctly) have been typed: But if you've not made that mistake (even with several lines separating the \csx{usepackage} commands, it's pretty easy to spot), the problem could arise from something else loading the package for -you. How do you find the culprit? Well, it's down to the log -analysis games discussed in % ! line break +you. How do you find the culprit? The "\texttt{h}" response to the +error message tells you which options were loaded each time. +Otherwise, it's down to the log analysis games discussed in % ! line break ``\Qref*{How to approach errors}{Q-erroradvice}''; the trick to remember is that that the process of loading each file is parenthesised in the log; so if package \Package{foo} loads \Package{graphics}, the log diff --git a/Master/texmf-doc/doc/english/FAQ-en/filectan.tex b/Master/texmf-doc/doc/english/FAQ-en/filectan.tex index 232e11861aa..951bdeb602f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/filectan.tex +++ b/Master/texmf-doc/doc/english/FAQ-en/filectan.tex @@ -23,7 +23,7 @@ \CTANfile{bidstobibtex}{biblio/bibtex/utils/bids/bids.to.bibtex} \CTANfile{bold-extra}{macros/latex/contrib/misc/bold-extra.sty} \CTANfile{braket}{macros/latex/contrib/misc/braket.sty} -\CTANfile{btxmactex}{macros/eplain/btxmac.tex} +\CTANfile{btxmactex}{macros/eplain/tex/eplain/btxmac.tex} \CTANfile{cancel}{macros/latex/contrib/misc/cancel.sty} \CTANfile{capt-of}{macros/latex/contrib/misc/capt-of.sty} \CTANfile{catalogue}{help/Catalogue/catalogue.html} diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2colfloat.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2colfloat.html index 240e4e3baba..561d265a260 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2colfloat.html +++ b/Master/texmf-doc/doc/english/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 +<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,11 +18,11 @@ 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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2colfltorder.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2colfltorder.html index ba9850857b0..5b9e631bc38 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2colfltorder.html +++ b/Master/texmf-doc/doc/english/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 @@ -26,7 +26,7 @@ are needed. <dl> <dt><tt><i>dblfloatfix.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/dblfloatfix.sty">macros/latex/contrib/misc/dblfloatfix.sty</a> <dt><tt><i>fix2col.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>) -<dt><tt><i>fixltx2e.sty</i></tt><dd>Part of the LaTeX distribution. +<dt><tt><i>fixltx2e.sty</i></tt><dd>Part of the LaTeX distribution </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfltorder">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfltorder</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2letterfontcmd.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2letterfontcmd.html index 0d5de9e2c18..3a5c3f40841 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2letterfontcmd.html +++ b/Master/texmf-doc/doc/english/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: @@ -9,7 +9,7 @@ commands, so you used them as: <pre> {\bf Fred} was {\it here\/}. </pre> -</blockquote> +</blockquote><p> with the font change enclosed in a group, so as to limit its effect; note the italic correction command <code>\</code><code>/</code> that was necessary at the end of a section in italics. @@ -23,14 +23,14 @@ any other font settings, keeping only the size. So, for example, <pre> {\bf\it Here we are again\/} </pre> -</blockquote> +</blockquote><p> ignores <code>\</code><code>bf</code> and produces text in italic, medium weight (and the italic correction has a real effect), whereas <blockquote> <pre> {\it\bf happy as can be\/} </pre> -</blockquote> +</blockquote><p> ignore <code>\</code><code>it</code> and produces upright text at bold weight (and the italic correction has nothing to do). The same holds if you mix LaTeX2e font selections with the old style commands: @@ -38,13 +38,13 @@ LaTeX2e font selections with the old style commands: <pre> \textbf{\tt all good friends} </pre> -</blockquote> +</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 @@ -56,7 +56,7 @@ course). A few examples <pre> {\bfseries\ttfamily and jolly good company!} </pre> -</blockquote> +</blockquote><p> produces bold typewriter text (but note the lack of a <a href="FAQ-bold-extras.html">bold typewriter font</a> @@ -66,9 +66,9 @@ in the default Computer Modern fonts), or <pre> {\slshape\sffamily Never mind the weather\/} </pre> -</blockquote> +</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> @@ -77,7 +77,7 @@ becomes <code>\</code><code>texttt{</code><em>text</em><code>}</code>. Block co <pre> \textit{\textbf{Never mind the rain}} </pre> -</blockquote> +</blockquote><p> to produce bold italic text (note that the block commands supply italic corrections where necessary), and they be nested with the LaTeX2e modal commands, too: @@ -86,41 +86,39 @@ LaTeX2e modal commands, too: <pre> \texttt{\bfseries So long as we're together} </pre> -</blockquote> +</blockquote><p> for bold typewriter, or <blockquote> <pre> {\slshape \textbf{Whoops! she goes again}\/} </pre> -</blockquote> +</blockquote><p> for a bold slanted instance of the current family (note the italic correction applied at the end of the modal command group, again). <p>The new commands (as noted above) override commands of the same type. In almost all cases, this merely excludes ludicrous ideas such as -"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> {\fontshape{ui}\selectfont Tra la la, di dee} </pre> -</blockquote> +</blockquote><p> <dl> <dt><tt><i>smallcap.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smallcap.zip">macros/latex/contrib/smallcap</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smallcap.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/smallcap/">browse</a>) </dl> -<p> -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2letterfontcmd">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2letterfontcmd</a> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2letterfontcmd">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2letterfontcmd</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-8000.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-8000.html index dbcc7105ae9..11d089484b1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-8000.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-AMSpkg.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-AMSpkg.html index 43fe34acdee..361430da52c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-AMSpkg.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-AMSpkg.html @@ -4,9 +4,9 @@ <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 +the American Mathematical Society (AMS) during 1983–1985 and is described in the book -"<a href="FAQ-books.html">The Joy of TeX</a>". +“<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-doc/doc/english/FAQ-en/html/FAQ-BibTeXing.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-BibTeXing.html index 400b65a0aa7..88d6276dc55 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-BibTeXing.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-BibTeXing.html @@ -4,23 +4,27 @@ <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 +of Leslie Lamport’s LaTeX manual (see <a href="FAQ-books.html">TeX-related books</a>). -The document "BibTeXing", contained in the file <i>btxdoc.tex</i>, -expands on the chapter in Lamport's book. <em>The LaTeX Companion</em> +The document “BibTeXing”, contained in the file <i>btxdoc.tex</i>, +expands on the chapter in Lamport’s book. <em>The LaTeX Companion</em> (see <a href="FAQ-books.html">TeX-related books</a>) also has information on BibTeX and writing BibTeX style files. -<p>The document "Designing BibTeX Styles", contained in the file +<p>The document “Designing BibTeX Styles”, contained in the file <code>btxhak.tex</code>, explains the postfix stack-based language used to write BibTeX styles (<code>.bst</code> files). The file <code>btxbst.doc</code> is the template for the four standard styles (<code>plain</code>, <code>abbrv</code>, <code>alpha</code>, <code>unsrt</code>). It also contains their documentation. The complete BibTeX documentation set (including 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 +may also be found on CTAN. <dl> <dt><tt><i>BibTeX documentation</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/distribs/doc.zip">biblio/bibtex/distribs/doc</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/distribs/doc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/distribs/doc/">browse</a>) <dt><tt><i>BibTeX documentation, in PDF</i></tt><dd> <a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/doc.zip">biblio/bibtex/contrib/doc</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/doc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/doc/">browse</a>) +<dt><tt><i>Tame the BeaST</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/bibtex/tamethebeast/ttb_en.pdf">info/bibtex/tamethebeast/ttb_en.pdf</a> </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=BibTeXing">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=BibTeXing</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-CD.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-CD.html index 0653ab0be3c..94df44f1992 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-CD.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-CD.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label CD</title> </head><body> <h3>The TeX Live distribution</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. <p>The TeX Live distribution provides this, together with a ready-to-run TeX system. The TeX Live installation disc offers -teTeX for use on Unix-like systems, and fpTeX for use on Windows -systems. There is also a 'demonstration' disc and an archive snapshot +teTeX for use on Unix-like systems, and ProTeXt for use on Windows +systems. There is also a ‘demonstration’ disc and an archive snapshot (all on CD- or DVD-ROMs). TeX-Live was originally developed under the auspices of a consortium of User Groups (notably TUG, UK TUG and diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ECfonts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ECfonts.html index b96ea44a6cc..8e4173d82d8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ECfonts.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ECfonts.html @@ -3,24 +3,23 @@ </head><body> <h3>What are the EC fonts?</h3> <p>A font consists of a number of <em>glyphs</em>. In order that the -glyphs may be printed, they are -<a href="FAQ-whatenc.html"><em>encoded</em></a>, and the -encoding is used as an index into tables within the font. For +glyphs may be printed, they are <a href="FAQ-whatenc.html"><em>encoded</em></a>, and +the encoding is used as an index into tables within the font. For various reasons, Knuth chose deeply eccentric encodings for his -Computer Modern family of fonts; in -particular, he chose different encodings for different fonts, so that -the application using the fonts has to remember which font of the -family it's using before selecting a particular glyph. +Computer Modern family of fonts; in particular, he chose different +encodings for different fonts, so that the application using the fonts +has to remember which font of the family it’s using before selecting a +particular glyph. <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 @@ -31,36 +30,48 @@ 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 there are far more of them than there are CM fonts. The simple number of fonts has acted as a disincentive to the production of Adobe -Type 1 versions of the fonts,, but several commercial suppliers offer +Type 1 versions of the fonts, but several commercial suppliers offer EC or -EC-equivalent fonts in type 1 or TrueType form - see +EC-equivalent fonts in type 1 or TrueType form — see -<a href="FAQ-commercial.html">commercial suppliers</a>, and free -<a href="FAQ-textrace.html">auto-traced versions</a> are -available. -What's more, until corresponding fonts for mathematics are produced, -the CM fonts must be retained because some mathematical symbols -are drawn from text fonts in the CM encodings. +<a href="FAQ-commercial.html">commercial suppliers</a>. Free +<a href="FAQ-textrace.html">auto-traced versions</a> (the CM-super +and the LGC fonts), and the Latin Modern series (rather +directly generated from Metafont sources), are available. +<p> + + +Note that the Cork encoding doesn’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 fonts, which cover ‘basic’ +TeX mathematics; more advanced mathematics are likely to need +separate fonts anyway. Suitable mathematics fonts for use with other +font families are discussed in +“<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 PostScript fonts, and also by the <i>txfonts</i> and <i>pxfonts</i> font packages -(see <a href="FAQ-psfchoice.html">"choice of scalable fonts"</a>). +(see <a href="FAQ-psfchoice.html">“choice of scalable fonts”</a>). <dl> +<dt><tt><i>CM-super fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.zip">fonts/ps-type1/cm-super</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super/">browse</a>) +<dt><tt><i>CM-LGC fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-lgc.zip">fonts/ps-type1/cm-lgc</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-lgc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-lgc/">browse</a>) <dt><tt><i>EC and TC fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ec.zip">fonts/ec</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ec.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ec/">browse</a>) +<dt><tt><i>Latin Modern fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/lm.zip">fonts/lm</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/lm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/lm/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ECfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ECfonts</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-HPdrivers.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-HPdrivers.html index fce6aed9f3e..51051bee670 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-HPdrivers.html +++ b/Master/texmf-doc/doc/english/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>. <i>dviljk</i> is no longer distributed as a separate source, but the teTeX distribution holds a copy under the name <i>dvilj</i>. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX2HTML.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX2HTML.html index 75b78d95868..ed9708daa31 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX2HTML.html +++ b/Master/texmf-doc/doc/english/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 @@ -38,18 +38,18 @@ browsing may be brighter - see <p> A mailing list for users may be found via <a href="http://tug.org/mailman/listinfo/latex2html">http://tug.org/mailman/listinfo/latex2html</a> <dt><i>TtH</i><dd>a compiled program that supports either LaTeX - or plain TeX, and uses the font/table technique for representing + or Plain TeX, and uses the font/table technique for representing mathematics. It is written by Ian Hutchinson, using <i>flex</i>. The distribution consists of a single C source (or a compiled executable), which is easy to install and very fast-running. <dt><i>Tex4ht</i><dd>a compiled program that supports either - LaTeX or plain TeX, by processing a DVI file; it uses + LaTeX or Plain TeX, by processing a DVI file; it uses bitmaps for mathematics, but can also use other technologies where appropriate. Written by Eitan Gurari, it parses the DVI file generated when you run (La)TeX over your file with - <i>tex4ht</i>'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>TeXpider</i><dd> a commercial program from @@ -60,7 +60,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> @@ -68,8 +68,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-doc/doc/english/FAQ-en/html/FAQ-LaTeX3.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX3.html index f01ec0197a5..7b0ae4b846d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX3.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX3.html @@ -8,21 +8,22 @@ to produce a major new document processing system based on the principles pioneered by Leslie Lamport in the current LaTeX. It will remain freely available and it will be fully documented at all levels. -<p>The LaTeX3 team's first product (LaTeX2e) was delivered in 1994 -(it's now properly called "LaTeX", since no other version is current). +<p>The LaTeX3 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 (see -<a href="http://www.latex-project.org/articles.html">http://www.latex-project.org/articles.html</a>), as is some of the -project's experimental code -(<a href="http://www.latex-project.org/experimental">http://www.latex-project.org/experimental</a>). You can +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 <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). You can participate in discussions of the future of LaTeX through the mailing list <code>latex-l</code>. Subscribe to the list by sending a -message '<code>subscribe latex-l <<em>your name</em>></code>' to +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>LaTeX project publications</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/ltx3pub.zip">info/ltx3pub</a> (<a href="ftp://cam.ctan.org/tex-archive/info/ltx3pub.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/ltx3pub/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXandPlain.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXandPlain.html index 7b376a47aeb..174238f9a88 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXandPlain.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXandPlain.html @@ -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. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXtoPlain.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXtoPlain.html index 3451357ed15..7becdda3f9a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXtoPlain.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXtoPlain.html @@ -2,11 +2,11 @@ <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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-MF.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-MF.html index 54042becd41..fe88f3967e6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-MF.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-MP.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-MP.html index 40723a3397a..c5c44518920 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-MP.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-NTS.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-NTS.html deleted file mode 100644 index 3851bb20dc5..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-NTS.html +++ /dev/null @@ -1,43 +0,0 @@ -<head> -<title>UK TeX FAQ -- question label NTS</title> -</head><body> -<h3>The <i>NTS</i> project</h3> - -<p>The <i>NTS</i> project was established in 1992, to produce a typesetting -system that's even better than TeX. The project is not simply -enhancing TeX, for two reasons: first, that TeX itself has been -frozen by Knuth -(see <a href="FAQ-TeXfuture.html">the future of TeX</a>), and second, -even if they <em>were</em> allowed to develop the program, some members -of the <i>NTS</i> team feel that TeX in its present form is simply -unsuited to further development. While all those involved in the -project are committed to TeX, they recognise -that the end product may very well have little in common with TeX -other than its philosophy. -<p>The group's first product was nevertheless a set of -extensions and enhancements to TeX, implemented through the standard -medium of a change-file. The extended system is known e-TeX, and is -100% compatible with TeX; furthermore, e-TeX can -construct a format -that <em>is</em> "TeX", with no extensions or enhancements present. -<p>The most recent base source of e-TeX (i.e., the Web change file) is -available on CTAN. Following a suggestion from the -<a href="FAQ-LaTeX3.html">LaTeX project</a>, most (La)TeX distributions now -make <em>all</em> their LaTeX executables with the -e-TeX extensions (that is, <i>latex</i> is really e-LaTeX, -<i>pdflatex</i> is really PDFe-LaTeX, and so on). In -this context, some of the newer LaTeX packages are designed to -require the e-TeX extensions. -<p>The project has now produced a beta-version of -TeX written (from scratch) in Java. Since it <em>isn't</em> TeX -(it remains slightly incompatible in microscopic ways), it's known as -<i>NTS</i>. As might be expected, this first re-implementation runs -rather slowly, but its operation <em>has</em> been demonstrated in -public, and the beta-release is available on -CTAN. -<dl> -<dt><tt><i>e-TeX</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/systems/e-tex/">systems/e-tex/</a> -<dt><tt><i>NTS</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/nts.zip">systems/nts</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/nts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/nts/">browse</a>) -</dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=NTS">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=NTS</a> -</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-PSpreview.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-PSpreview.html index 83df84b454c..923a654de90 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-PSpreview.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-PSpreview.html @@ -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-doc/doc/english/FAQ-en/html/FAQ-RCS.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-RCS.html index cb445fc0b8c..730fe6cc140 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-RCS.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-RCS.html @@ -14,19 +14,19 @@ flexible way. The package <i>rcsinfo</i> is simpler, but does most of what you want, and some people prefer it; it is explicitly compatible with <i>LaTeX2HTML</i>. <p>If, however, you need a solution which works without using external -packages, or which will work in plain TeX, then you can use the +packages, or which will work in Plain TeX, then you can use the following minimal solution: <blockquote> <pre> \def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}} -\RCS$Revision: 1.299 $ % or any RCS keyword -\RCS$Date: 2005/07/07 13:52:16 $ +\RCS$Revision: 1.423 $ % or any RCS keyword +\RCS$Date: 2006/12/11 23:23:07 $ ... \date{Revision \RCSRevision, \RCSDate} </pre> -</blockquote> -<p>If you've entered the brave new world of <i>subversion</i>, the +</blockquote><p> +<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> @@ -41,7 +41,7 @@ about dealing with dates: <code>\</code><code>maketitle</code><br> <code>...</code><br> <code>\</code><code>end{document}</code> -</blockquote> +</blockquote><p> will (once <i>subversion</i> has committed a copy of the document) cause <code>\</code><code>maketitle</code> use the date that has been written into the <code>$Date$</code> keyword. @@ -50,8 +50,8 @@ same mechanisms as does <i>svn</i> but with a rather different focus. <i>Svninfo</i> does the date trick that <i>svn</i> performs (controlled by a package option), and can set up page foot-lines using <a href="FAQ-fancyhdr.html">package <i>fancyhdr</i></a>. -There isn't much to choose between the two packages: you should read -the packages' documentation to see which you find best. +There isn’t much to choose between the two packages: you should read +the packages’ documentation to see which you find best. <dl> <dt><tt><i>rcs.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rcs.zip">macros/latex/contrib/rcs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rcs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/rcs/">browse</a>) <dt><tt><i>rcsinfo.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rcsinfo.zip">macros/latex/contrib/rcsinfo</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rcsinfo.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/rcsinfo/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-SGML2TeX.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-SGML2TeX.html index b3aa88906b6..4f1fe189248 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-SGML2TeX.html +++ b/Master/texmf-doc/doc/english/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,28 +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 - <a href="ftp://ftp.th-darmstadt.de/pub/text/sgml/stil"><i>stil</a></i>, - written in Common Lisp. - + 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’). </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-doc/doc/english/FAQ-en/html/FAQ-TUGstar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TUGstar.html index 5eca3a33458..babb1228147 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TUGstar.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TUGstar.html @@ -8,22 +8,22 @@ 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 web site is a valuable resource for all sorts of +<p>TUG’s web site is a valuable resource for all sorts of TeX-related matters, such as details of TeX software, and lists of TeX vendors and TeX consultants. Back articles from <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> @@ -34,7 +34,7 @@ too; TUG's web site maintains a list of Fax: +1 503-223-3960<br> Email: <a href="mailto:tug@mail.tug.org"><i>tug@mail.tug.org</i></a><br> Web: <a href="http://www.tug.org/">http://www.tug.org/</a> -</blockquote> +</blockquote><p> <p> <p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TUG*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TUG*</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXfuture.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXfuture.html index 61d6bbd7661..5be869e5ac5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXfuture.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXfuture.html @@ -7,22 +7,25 @@ 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 is version +limit pi (at the time of writing, Knuth’s latest release is version 3.141592). Knuth wants TeX to be frozen at version pi when he -dies; thereafter, no further changes may be made to Knuth's source. +dies; thereafter, no further changes 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.718.) +limit e, and currently stands at 2.71828.) <p>Knuth explains his decision, and exhorts us all to respect it, in a paper originally published in <i>TUGboat</i> 11(4) (and reprinted in the <a href="http://www.ntg.nl/maps/pdf/5_34.pdf">NTG journal MAPS</a>). -<p><p>There are projects (some of them long-term +<p>There are projects (some of them long-term projects: see, for example, <a href="FAQ-LaTeX3.html">the LaTeX3 project</a>) to build substantial new macro packages based on TeX. For the even longer term, there -are various projects to build a <em>successor</em> to TeX; see -<a href="FAQ-omega.html">the Omega project</a> and <a href="FAQ-NTS.html">NTS</a>. +are various projects to build a <em>successor</em> to TeX; see, for example, +the + <a href="FAQ-omegaleph.html">Omega/Aleph</a> and <a href="FAQ-extex.html">ExTeX</a> + projects. + <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXfuture">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXfuture</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXpronounce.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXpronounce.html index 375ad3aa38a..ab4ab182aeb 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXpronounce.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXpronounce.html @@ -1,18 +1,20 @@ <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 -Chi, -and is pronounced by English-speakers either a bit like the 'ch' in -the Scots word 'loch' ([x] in the IPA) or 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'; the logo TeX is +<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 merely the uppercase version of the first three (Greek) letters of the -word. +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> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html index e7e0ef51ec3..00914bccb4b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html @@ -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> Instructions for retrieving the <i>web2c</i> Unix TeX distribution via anonymous <code>ftp</code> are to be found in @@ -18,25 +18,25 @@ <code>teTeX-texmf</code> and <code>teTeX-texmfsrc</code>. <p> No sets of teTeX binaries are provided on CTAN; however, compilation of teTeX is pretty stable, on a wide variety of - platforms. If you don't have the means to compile teTeX - yourself, you will find that most "support" sites carry compiled - versions in their "free area", and the TeX-live discs also + platforms. If you don’t have the means to compile teTeX + yourself, you will find that most “support” sites carry compiled + versions in their “free area”, and the TeX-live discs also carry a wide range of binary distributions. -<p> There's a mailing list for teTeX installation problems (and the +<p> There’s a mailing list for teTeX installation problems (and the like): subscribe by sending mail to <a href="mailto:majordomo@dbs.uni-hannover.de"><i>majordomo@dbs.uni-hannover.de</i></a> containing nothing more than - "<code>subscribe tetex</code>". The list is archived at + “<code>subscribe tetex</code>”. The list is archived at <a href="http://www.mail-archive.com/tetex@dbs.uni-hannover.de/">http://www.mail-archive.com/tetex@dbs.uni-hannover.de/</a>, and an RSS feed is available at the same site: <a href="http://www.mail-archive.com/tetex@dbs.uni-hannover.de/maillist.xml">http://www.mail-archive.com/tetex@dbs.uni-hannover.de/maillist.xml</a> <p> During periods when teTeX is itself under development, a - "teTeX-beta" is available. Before proceeding with the + “teTeX-beta” is available. Before proceeding with the beta-release, check the <i>ANNOUNCE</i> files in the two directories on CTAN: it may well be that the - beta-release doesn't offer you anything new, + beta-release doesn’t offer you anything new, that you need. <p> MacOS X users should refer to the information below, - under item "Mac". + under item “Mac”. <dl> <dt><tt><i>tetex</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/systems/unix/teTeX/current/distrib/">systems/unix/teTeX/current/distrib/</a> <dt><tt><i>tetex-beta</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/unix/teTeX-beta.zip">systems/unix/teTeX-beta</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/unix/teTeX-beta.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/unix/teTeX-beta/">browse</a>) @@ -54,51 +54,8 @@ <dt><tt><i>vtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/linux.zip">systems/vtex/linux</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/linux.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/linux/">browse</a>) <dt><tt><i>vtex required common files</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.zip">systems/vtex/common</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/common/">browse</a>) </dl> -<dt>PC; MSDOS or OS/2<dd> EmTeX, by Eberhard Mattes, - includes LaTeX, BibTeX, previewers, and drivers, and is - available as a series of zip archives. Documentation is - available in both German and English. Appropriate memory managers - for using emTeX with 386 (and better) processors and under - Windows, are included in the distribution. EmTeX will operate - under Windows, but Windows users are better advised to use a - distribution tailored for the Windows environment. -<p> A version of emTeX, packaged to use a - - <a href="FAQ-tds.html">TDS directory structure</a>, is separately available as - an emTeX '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. - <dl> - <dt><tt><i>emtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex.zip">systems/msdos/emtex</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/emtex/">browse</a>) - <dt><tt><i>emtexTDS</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/os2/emtex-contrib/emtexTDS.zip">obsolete/systems/os2/emtex-contrib/emtexTDS</a> (<a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/os2/emtex-contrib/emtexTDS.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/obsolete/systems/os2/emtex-contrib/emtexTDS/">browse</a>) - </dl> -<dt>PC; MSDOS<dd> The most recent MSDOS offering is a - port of the Web2C 7.0 implementation, using the GNU - <i>djgpp</i> compiler. While this package is more recent than - emTeX, it still implements a rather old instance of (La)TeX. - <dl> - <dt><tt><i>djgpp</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/djgpp.zip">systems/msdos/djgpp</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/djgpp.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/djgpp/">browse</a>) - </dl> -<dt>PC; OS/2<dd> OS/2 may also use a free version of the - commercial - <a href="FAQ-commercial.html">VTeX</a>, which specialises - in direct production of PDF from (La)TeX input. - <dl> - <dt><tt><i>vtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/os2.zip">systems/vtex/os2</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/os2.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/os2/">browse</a>) - <dt><tt><i>vtex required common files</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.zip">systems/vtex/common</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/common/">browse</a>) - </dl> <dt>PC: Win32<dd> - fpTeX, by Fabrice Popineau, is a version of teTeX for Windows - systems. As such, it is particularly attractive to those who need - to switch back and forth between Windows and Unix environments, and - to administrators who need to maintain both (fpTeX can use the - same <code>texmf</code> tree as a teTeX installation). fpTeX's - previewer (<i>Windvi</i>) is based on <i>xdvi</i>, and takes - advantage of extra facilities in the Win32 environment. - <i>Windvi</i> is capable of printing directly, and a version of - <i>dvips</i> is also available. -<p> MiKTeX, by Christian Schenk, is also a comprehensive + MiKTeX, by Christian Schenk, is also a comprehensive distribution, developed separately from the teTeX work. It has its own previewer, YAP, which is itself capable of printing, though the distribution also includes a port of <i>dvips</i>. @@ -106,22 +63,39 @@ HTML files in the directory offer hints on what you need to get going). The MiKTeX developers provide a ready-to-run copy of the distribution, on CDROM (for purchase) via the - <a href="http://www.miktex.org/cd/">MiKTeX web site</a>. + <a href="http://www.miktex.org/cd/">MiKTeX web site</a>; otherwise the + <i>setup</i> executable is available on CTAN, together with + all the optional packages. <p> <a href="http://tug.org/protext/">ProTeXt</a>, by Thomas Feuerstack, is a further option for installing MiKTeX. It bundles a MiKTeX setup with some further useful utilities, together with a PDF file which contains clickable links for the various installation steps, along with explanations. It again it is freeware, and copies are distributed with the <a href="FAQ-CD.html">TeX-live CD set</a>. +<p> <a href="https://xemtex.groups.foundry.supelec.fr/">XEmTeX</a>, by + Fabrice Popineau (he who created the excellent, but now defunct, + fpTeX distribution), is an integrated distribution of TeX, LaTeX, + ConTeXt, <i>XEmacs</i> and friends for Windows. All programs + have been compiled natively to take the best advantage of the + Windows environment. Configuration is provided so that the + resulting set of programs runs out-of-the-box. +<p> The (Japanese) W32TEX distribution was motivated by + the needs of Japanese users (Japanese won’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 + of space: the minimum documented download is as small as + 95 MBytes. Investigate the distribution at + <a href="http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/web2c75-e.html">http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/web2c75-e.html</a> <p> A further (free) option arises from the - <a href="http://www.cygwin.com">"CygWin" bundle</a>, which presents a + <a href="http://www.cygwin.com">“CygWin” bundle</a>, which presents a Unix-like environment over the Win32 interface; an X-windows server is available. If you run CygWin on your Windows machine, you have the option of using teTeX, too (you will need the X-server, to run <i>xdvi</i>). Of course, teTeX components will look like - Unix applications (but that's presumably what you wanted), but it's + Unix applications (but that’s presumably what you wanted), but it’s also reputedly somewhat slower than native Win32 implementations - such as MiKTeX or fpTeX. TeTeX is available as part of the + such as MiKTeX or XEmTeX. TeTeX is available as part of the CygWin distribution (in the same way that a version is available with most Linux distributions, nowadays), and you may also build your own copy from the current sources. @@ -131,33 +105,69 @@ TeX, which further the focus. <dl> <dt><tt><i>bakoma</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/win32/bakoma.zip">nonfree/systems/win32/bakoma</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/win32/bakoma.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/systems/win32/bakoma/">browse</a>) - <dt><tt><i>fptex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/win32/fptex.zip">systems/win32/fptex</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/win32/fptex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/win32/fptex/">browse</a>) - <dt><tt><i>miktex</i></tt><dd>Acquire <a href="ftp://cam.ctan.org/tex-archive/systems/win32/miktex/setup/setup.exe">systems/win32/miktex/setup/setup.exe</a>, and read - <a href="ftp://cam.ctan.org/tex-archive/systems/win32/miktex/setup/install.html">systems/win32/miktex/setup/install.html</a> + <dt><tt><i>miktex</i></tt><dd>Acquire <a href="ftp://cam.ctan.org/tex-archive/systems/win32/miktex/setup/setup.exe">systems/win32/miktex/setup/setup.exe</a> (also available from the + MiKTeX web site), and read installation instructions from + + <a href="http://www.miktex.org/2.5/Setup.aspx">the MiKTeX installation page</a> <dt><tt><i>protext.exe</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/texlive/Images/protext.exe">systems/texlive/Images/protext.exe</a> <dt><tt><i>tetex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/unix/teTeX/current/distrib/">systems/unix/teTeX/current/distrib/</a> </dl> +<dt>PC: MSDOS or OS/2<dd> EmTeX, by Eberhard Mattes, + includes LaTeX, BibTeX, previewers, and drivers, and is + available as a series of zip archives. Documentation is + available in both German and English. Appropriate memory managers + for using emTeX with 386 (and better) processors and under + Windows, are included in the distribution. EmTeX will operate + under Windows, but Windows users are better advised to use a + distribution tailored for the Windows environment. +<p> A version of emTeX, packaged to use a + + <a href="FAQ-tds.html">TDS directory structure</a>, is separately available as + an emTeX ‘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. + <dl> + <dt><tt><i>emtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex.zip">systems/msdos/emtex</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/emtex/">browse</a>) + <dt><tt><i>emtexTDS</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/os2/emtex-contrib/emtexTDS.zip">obsolete/systems/os2/emtex-contrib/emtexTDS</a> (<a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/os2/emtex-contrib/emtexTDS.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/obsolete/systems/os2/emtex-contrib/emtexTDS/">browse</a>) + </dl> +<dt>PC: MSDOS<dd> The most recent MSDOS offering is a + port of the Web2C 7.0 implementation, using the GNU + <i>djgpp</i> compiler. While this package is more recent than + emTeX, it still implements a rather old instance of (La)TeX. + <dl> + <dt><tt><i>djgpp</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/djgpp.zip">systems/msdos/djgpp</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/djgpp.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/djgpp/">browse</a>) + </dl> +<dt>PC: OS/2<dd> OS/2 may also use a free version of the + commercial + <a href="FAQ-commercial.html">VTeX</a>, which specialises + in direct production of PDF from (La)TeX input. + <dl> + <dt><tt><i>vtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/os2.zip">systems/vtex/os2</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/os2.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/os2/">browse</a>) + <dt><tt><i>vtex required common files</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.zip">systems/vtex/common</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/common/">browse</a>) + </dl> <dt>Windows NT, other platforms<dd> Ports of MiKTeX for NT on Power PC and AXP are available. Neither version has been updated for version 1.2 (or later) of - MiKTeX - they may not be satisfactory. + MiKTeX — they may not be satisfactory. <dl> - <dt><tt><i>miktex for AXP</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/win32/miktex-AXP.zip">systems/win32/miktex-AXP</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/win32/miktex-AXP.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/win32/miktex-AXP/">browse</a>) - <dt><tt><i>miktex for Power PC</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/win32/miktexppc.zip">systems/win32/miktexppc</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/win32/miktexppc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/win32/miktexppc/">browse</a>) + <dt><tt><i>miktex for AXP</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/win32/miktex-AXP.zip">obsolete/systems/win32/miktex-AXP</a> (<a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/win32/miktex-AXP.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/obsolete/systems/win32/miktex-AXP/">browse</a>) + <dt><tt><i>miktex for Power PC</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/win32/miktexppc.zip">obsolete/systems/win32/miktexppc</a> (<a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/win32/miktexppc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/obsolete/systems/win32/miktexppc/">browse</a>) </dl> <dt>Mac<dd> OzTeX, by Andrew Trevorrow, is a shareware version of TeX for the Macintosh. A DVI previewer and PostScript driver are also included. -<p> UK TUG prepays the shareware fee, so that its members may +<p> UK TUG prepays the shareware fee for its members, so + that they may acquire the software without further payment. Questions about OzTeX may be directed to <a href="mailto:oztex@midway.uchicago.edu"><i>oztex@midway.uchicago.edu</i></a> <p> Another partly shareware program is CMacTeX, put together by Tom Kiffe. This is much closer to the Unix TeX setup (it uses <i>dvips</i>, for instance). - CMacTeX includes a port of the latest version of - <a href="FAQ-omega.html">Omega</a>. + CMacTeX includes a port of a version of + <a href="FAQ-omegaleph.html">Omega</a>. <p> Both OzTeX and CMacTeX run on either MacOS X or on a sufficiently recent MacOS with CarbonLib (v1.3 for OzTeX, v1.4 for CMacTeX). @@ -166,16 +176,24 @@ <a href="http://www.rna.nl/tex.html">gwTeX</a>, by Gerben Wierda (which is based on teTeX). This is naturally usable from the command line, just like any other Unix-based system, but it can also - be used Mac-style as the engine behind Richard Koch's (free) + be used Mac-style as the engine behind Richard Koch’s (free) <a href="http://www.uoregon.edu/~koch/texshop/texshop.html">TeXShop</a>, which is an integrated TeX editor and previewer. +<p> From its 2005 release, the <a href="FAQ-CD.html">TeX-Live disc set</a> + includes “MacTeX”, a CDROM image that contains + MacOS X teTeX (the Gerben Wierda set mentioned + above), TeXshop, and <a href="FAQ-xetex.html">XeTeX</a>. Details (and a + downloadable distribution set) may be found on the + <a href="http://tug.org/mactex">TUG web site</a>; the distribution + is also on CTAN. <p> A useful <a href="http://www.esm.psu.edu/mac-tex/">resource for Mac users</a> - has a news and 'help' section, as well as details of systems and + has a news and ‘help’ section, as well as details of systems and tools. <dl> <dt><tt><i>cmactex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/cmactex.zip">nonfree/systems/mac/cmactex</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/cmactex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/systems/mac/cmactex/">browse</a>) + <dt><tt><i>mactex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/mac/mactex.zip">systems/mac/mactex</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/mac/mactex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/mac/mactex/">browse</a>) <dt><tt><i>oztex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/oztex.zip">nonfree/systems/mac/oztex</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/oztex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/systems/mac/oztex/">browse</a>) <dt><tt><i>MacOS X teTeX</i></tt><dd><a href="ftp://ftp.nluug.nl/pub/comp/macosx/tex-gs/">ftp://ftp.nluug.nl/pub/comp/macosx/tex-gs/</a> <dt><tt><i>TeXShop</i></tt><dd><a href="http://darkwing.uoregon.edu/~koch/texshop/texshop.html">http://darkwing.uoregon.edu/~koch/texshop/texshop.html</a> @@ -189,7 +207,7 @@ </dl> <dt>Atari<dd> TeX is available for the Atari ST. <p> If anonymous <code>ftp</code> is not available to you, send a message - containing the line '<code>help</code>' to + containing the line ‘<code>help</code>’ to <a href="mailto:atari@atari.archive.umich.edu"><i>atari@atari.archive.umich.edu</i></a> <dl> <dt><tt><i>Atari TeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/atari.zip">systems/atari</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/atari.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/atari/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-WYGexpts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-WYGexpts.html index f094dab05c6..b56cfd4f020 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-WYGexpts.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-WYGexpts.html @@ -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. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-abspos.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-abspos.html index 874a494cb22..1fd200c5de7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-abspos.html +++ b/Master/texmf-doc/doc/english/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. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-acrobat.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-acrobat.html index 361c70f4ba5..3f783f9ac40 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-acrobat.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-acrobat.html @@ -1,14 +1,14 @@ <head> <title>UK TeX FAQ -- question label acrobat</title> </head><body> -<h3>Making Acrobat documents from LaTeX</h3> -<p>There are three general routes to Acrobat output: Adobe's original -'distillation' route (via PostScript output), conversion of a +<h3>Making Acrobat PDF documents from (La)TeX</h3> +<p>There are three general routes to Acrobat output: Adobe’s original +‘distillation’ route (via PostScript output), conversion of a DVI file, and the use of a direct PDF generator such as -PDFTeX (see <a href="FAQ-pdftex.html">the PDFTeX project</a>) or -MicroPress's VTeX (see -<a href="FAQ-commercial.html">commercial TeX implementations</a> -and <a href="FAQ-TeXsystems.html">'free' TeX implementations)</a>). +PDFTeX (see <a href="FAQ-whatpdftex.html">PDFTeX</a>) or +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 Linux systems). <p>For simple documents (with no hyper-references), you can either <ul> <li> process the document in the normal way, produce PostScript @@ -31,8 +31,8 @@ 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 HyperTeX specification (see <a href="FAQ-hyper.html">Making hypertext documents from TeX</a>): -Sebastian Rahtz's <i>hyperref</i>, and Michael Mehlich's -<i>hyper</i>. <i>Hyperref</i> +Heiko Oberdiek’s <i>hyperref</i>, and Michael Mehlich’s +<i>hyper</i>. uses a configuration file to determine how it will generate hypertext; it can operate using PDFTeX primitives, the hyperTeX <code>\</code><code>special</code>s, or DVI driver-specific <code>\</code><code>special</code> commands. @@ -41,27 +41,34 @@ it can operate using PDFTeX primitives, the hyperTeX translates the DVI with these <code>\</code><code>special</code> commands into PostScript acceptable to Distiller, and <i>dvipdfm</i> has <code>\</code><code>special</code> commands of its own. +<p>(In practice, almost everyone uses <i>hyperref</i>; <i>hyper</i> +hasn’t been updated since 2000.) +<p>If you use Plain TeX, Eplain macro package can help you create +Acrobat documents with hyper-references (see +“<a href="FAQ-eplain.html">what is Eplain</a>”). +It can operate using PDFTeX primitives, or <code>\</code><code>special</code> commands +for the <i>dvipdfm</i> DVI driver. <p>There is no free implementation of all of <i>Adobe</i> -<i>Distiller</i>'s -functionality, but recent versions of <i>ghostscript</i> +<i>Distiller</i>’s +functionality, any but the very oldest versions of <i>ghostscript</i> provide pretty reliable distillation (but beware of the problems discussed in <a href="FAQ-dvips-pdf.html"><i>dvips</i> output for distillation</a>). In fact, <i>Distiller</i> itself is now remarkably cheap (for academics at least). -<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>ghostview</i> or <i>GSview</i> can display and print PDF files. <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 -incredibly clumsy - <i>GSview</i> doesn't make the same +cycle of “Edit-> Process-> Preview” become +incredibly 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-doc/doc/english/FAQ-en/html/FAQ-actinarg.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-actinarg.html index 368f07a8548..1096d750a62 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-actinarg.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-actinarg.html @@ -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> @@ -24,7 +24,7 @@ we can define: \gdef#{$\sharp$} \endgroup </pre> -</blockquote> +</blockquote><p> and: <blockquote> <pre> @@ -34,10 +34,10 @@ and: \def~{$\flat$}% } </pre> -</blockquote> +</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> @@ -52,25 +52,25 @@ split in two. So we write: \endgroup } </pre> -</blockquote> +</blockquote><p> and we can use the command as <code>\</code><code>chord{F#}</code> or <code>\</code><code>chord{Bb minor}</code>. <p>Two features of the coding are important: <ul> <li> <code>\</code><code>begingroup</code> in <code>\</code><code>chord</code> opens a group that is closed by <code>\</code><code>endgroup</code> in <code>\</code><code>Xchord</code>; this group limits the change of - category codes, which is the <em>raison d'ê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 analagous 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-doc/doc/english/FAQ-en/html/FAQ-activechars.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-activechars.html index af47d69125b..5cc1b11adac 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-activechars.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-activechars.html @@ -4,31 +4,31 @@ <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>. +<code>\catcode‘_=\active</code>. <p>Any character could, in principle, be activated this way and defined -as a macro (<code>\def_{</code><code>\</code><code><code>}</code> - the simple answer to +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 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> \catcode`\z=\active \def z{Yawn, I'm tired}% </pre> -</blockquote> -and each subsequent "<code>z</code>" in the text would become a yawn. This would be +</blockquote><p> +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,7 +42,7 @@ 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 @@ -51,8 +51,8 @@ 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> @@ -61,7 +61,7 @@ For example, the definition \def_{\textunderscore\-}% } </pre> -</blockquote> +</blockquote><p> does not work because it attemts to define an ordinary <code>_</code> character: When the macro is used, the category change does not apply to the underscore character already in the macro definition. Instead, one may @@ -76,11 +76,11 @@ use: } \endgroup </pre> -</blockquote> -The alternative ("tricksy") way of creating such an isolated +</blockquote><p> +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> @@ -91,7 +91,7 @@ explicitly changing a catcode: \def~{\textunderscore\-}% }% </pre> -</blockquote> +</blockquote><p> The two definitions have the same overall effect (the character is defined as a command, but the character does not remain active), except that the first defines a <code>\</code><code>global</code> command. @@ -107,10 +107,10 @@ special active <em>maths code</em>, as with }% \mathcode`x="8000 </pre> -</blockquote> +</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="ftp://cam.ctan.org/tex-archive/macros/latex/base.zip">macros/latex/base</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-addtoreset.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-addtoreset.html index 58f03509b9d..c0770eee25d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-addtoreset.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-addtoreset.html @@ -2,56 +2,56 @@ <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 corrolaries per theorem, for example. If -you're defining these things by hand, you declare the relationship +algorithms per section, or corrollaries per theorem, for example. If +you’re defining these things by hand, you declare the relationship when you define the counter in the first place: <blockquote> <code>\</code><code>newcounter{</code><em>new-name</em><code>}[</code><em>master</em><code>]</code> -</blockquote> +</blockquote><p> 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: <blockquote> <code>\</code><code>@addtoreset{</code><em>new-name</em><code>}{</code><em>master</em><code>}</code> -</blockquote> +</blockquote><p> (but remember that it needs to be between <code>\</code><code>makeatletter</code> and <code>\</code><code>makeatother</code>, or in a package of your own). <p>The <i>chngcntr</i> package encapsulates the <code>\</code><code>@addtoreset</code> command into a command <code>\</code><code>counterwithin</code>. So: <blockquote> <pre> -\counterwithin*{corrolary}{theorem} +\counterwithin*{corrollary}{theorem} </pre> -</blockquote> -will make the corrolary counter slave to theorem counters. The +</blockquote><p> +will make the corrollary counter slave to theorem counters. The command without its asterisk: <blockquote> <pre> -\counterwithin{corrolary}{theorem} +\counterwithin{corrollary}{theorem} </pre> -</blockquote> -will do the same, and also redefine <code>\</code><code>thecorrolary</code> as -<<i>theorem number</i>>.<<i>corrolary number</i>>, which is a good scheme -if you ever want to refer to the corrolaries - there are potentially -many "corrolary 1" in any document, so it's as well to tie its number +</blockquote><p> +will do the same, and also redefine <code>\</code><code>thecorrollary</code> as +<<i>theorem number</i>>.<<i>corollary number</i>>, which is a good scheme +if you ever want to refer to the corrollaries — there are potentially +many “corrollary 1” in any document, so it’s as well to tie its number 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 @@ -61,14 +61,14 @@ of the techniques described there, using package <i>perpage</i>, may be applied to any counter. The command: <blockquote> <code>\</code><code>MakePerPage{</code><em>counter</em><code>}</code> -</blockquote> +</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="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/chngcntr.sty">macros/latex/contrib/misc/chngcntr.sty</a> -<dt><tt><i>perpage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/perpage.sty">macros/latex/contrib/misc/perpage.sty</a> +<dt><tt><i>perpage.sty</i></tt><dd>Distributed as part <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse</a>) </dl> <p> <p><p><p><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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-adobetypen.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-adobetypen.html index 435a23cd734..be29d0f560d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-adobetypen.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-adobetypen.html @@ -4,13 +4,13 @@ <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, but -we'll discuss the two formats most commonly encountered in the +in PostScript files; this question doesn’t attempt to be encyclopaedic, but +we’ll discuss the two formats most commonly encountered in the (La)TeX context, types 1 and 3. <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 things are showing signs of change. @@ -27,21 +27,21 @@ their use (see <a href="FAQ-dvips-pdf.html">PDF quality</a>). PostScript operators is permissible, including bitmaps operators. 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 inreasingly 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>-> -<code>Fonts ...</code>, and it will show some font or other as "Type 3" -(usually with encoding "Custom"). (This problem has disappeared +<code>Fonts ...</code>, and it will show some font or other as “Type 3” +(usually with encoding “Custom”). (This problem has disappeared with version 6 of Acrobat Reader.) <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-doc/doc/english/FAQ-en/html/FAQ-aleph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-aleph.html deleted file mode 100644 index e581989757b..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-aleph.html +++ /dev/null @@ -1,27 +0,0 @@ -<head> -<title>UK TeX FAQ -- question label aleph</title> -</head><body> -<h3>The Aleph project</h3> -<p>The Aleph project aims to build a -"usable" version of -<a href="FAQ-omega.html">Omega</a>, incorporating e-TeX extensions -from the <a href="FAQ-NTS.html"><i>NTS</i> project</a>. -<p>Two sets of concerns have provided impetus to the project: first, that -many users need the e-TeX extensions, and they're not on the -Omega development path; and second, -that the Omega project is currently -immersed in radical restructuring of -Omega, and is not able to be -particularly responsive to user requirements in the short term. In -the longer term, the Aleph project hope -that their work will be rendered irrelevant by the development of -Omega proper. -<p>The current pre-release snapshot of -Aleph resides on CTAN with the -rather modest name of e-Omega. Follow development by subscribing -to the project mailing list via <a href="http://www.ntg.nl/mailman/listinfo/aleph">http://www.ntg.nl/mailman/listinfo/aleph</a> -<dl> -<dt><tt><i>e-omega</i></tt><dd>Browse <a href="ftp://cam.ctan.org/tex-archive/systems/aleph.zip">systems/aleph</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/aleph.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/aleph/">browse</a>) -</dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=aleph</a> -</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-algorithms.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-algorithms.html index f6f6df07821..c493b9d9395 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-algorithms.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-algorithms.html @@ -2,7 +2,7 @@ <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. <p>Pseudocode differs from actual program listings in that it lacks @@ -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 @@ -27,9 +27,9 @@ conditional constructs. These primitives can easily be redefined to produce different text in the output. However, there is no support for adding new primitives. Typesetting the pseudocode itself is performed in <i>algorithmic</i>; the <i>algorithms</i> package -uses the facilities of the the <i>float</i> package to number +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 similiar 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-doc/doc/english/FAQ-en/html/FAQ-alreadydef.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-alreadydef.html index 97cf247ecb6..4bd4869922e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-alreadydef.html +++ b/Master/texmf-doc/doc/english/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> @@ -12,7 +12,7 @@ commands it defines is already present. For example, both the \usepackage{txfonts} \usepackage{amsmath} </pre> -</blockquote> +</blockquote><p> produces a string of error messages of the form: <blockquote> <pre> @@ -20,24 +20,24 @@ produces a string of error messages of the form: Or name \end... illegal, see p.192 of the manual. </pre> -</blockquote> +</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} @@ -46,11 +46,11 @@ us, there's the package <i>savesym</i>. The sequence: \usepackage{txfonts} \restoresymbol{TXF}{iint} </pre> -</blockquote> +</blockquote><p> does the job; restoring the <i>amsmath</i> version of the command, and making the <i>txfonts</i> version of the command available as <code>\</code><code>TXFiint</code>. -<p>Documentation of <i>savesym</i> doesn'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="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-altabcr.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-altabcr.html index 5c3ce9b95d4..5f4f9f0db80 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-altabcr.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-altabcr.html @@ -3,7 +3,7 @@ </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 +environment is being processed. “Alignment tabs” are the <code>&</code> signs that separate the columns of a tabular; so the error message <blockquote> @@ -11,7 +11,7 @@ message <pre> ! Extra alignment tab has been changed to \cr </pre> -</blockquote> +</blockquote><p> could arise from a simple typo, such as: <blockquote> <pre> @@ -20,13 +20,13 @@ could arise from a simple typo, such as: goodbye & now \end{tabular} </pre> -</blockquote> +</blockquote><p> 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 - an extra -"<code>l</code>" in that solves the problem. (As a result of the error, -"<code>jim</code>" will be moved to a row of his own.) +two-column <code>ll</code> column specification can cope with — an extra +“<code>l</code>” in that solves the problem. (As a result of the error, +“<code>jim</code>” will be moved to a row of his own.) <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} @@ -36,16 +36,16 @@ here & we are again \\ happy & as can be \end{tabular} </pre> -</blockquote> +</blockquote><p> the problem here (as explained in <a href="FAQ-tabcellalign.html">tabular cell alignment</a>) is that the <code>\</code><code>raggedright</code> command in the column specification has overwritten -<code>tabular</code>'s definition of <code>\\</code>, so that -"<code>happy</code>" appears in a new line of the second column, and the +<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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-amfonts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-amfonts.html index b9a3de899e3..8d02c4e874d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-amfonts.html +++ b/Master/texmf-doc/doc/english/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, all you can reasonably do is to edit the document. The appearance of DVI files that request them is sufficiently rare that no-one has undertaken the mammoth task of creating a translation of diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ant.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ant.html index 2bdd1d57184..45b6f0e7b7c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ant.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ant.html @@ -2,22 +2,22 @@ <title>UK TeX FAQ -- question label ant</title> </head><body> <h3>The ANT typesetting system</h3> -<p>Achim Blumensath's ANT project, in contrast to <i>NTS</i>, aims +<p>Achim Blumensath’s <a href="http://ant.berlios.de">ANT</a> project, +in contrast to <i>NTS</i>, aims not to replicate TeX with a different implementation technique, but rather to provide a replacement for TeX which uses TeX-like typesetting algorithms in a very different programming environment. ANT remains under development, but it is now approaching the status of a usable typesetting system. -<p>ANT'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 downloads</i></tt><dd> - <a href="http://www-mgi.informatik.rwth-aachen.de/~blume/Download.html">http://www-mgi.informatik.rwth-aachen.de/~blume/Download.html</a> +<dt><tt><i>ANT</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/ant.zip">systems/ant</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/ant.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/ant/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ant">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ant</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-appendix.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-appendix.html index 987606c84b9..8cbbdb68736 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-appendix.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-appendix.html @@ -20,7 +20,7 @@ to alphabetic. So: \section{How I became inspired} ... </pre> -</blockquote> +</blockquote><p> would be typeset (in an <i>article</i> document) something like: <blockquote> <b>1 My inspiration</b> @@ -29,11 +29,11 @@ would be typeset (in an <i>article</i> document) something like: <p>... <p><b>A How I became inspired</b> <p>... -</blockquote> +</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 @@ -46,11 +46,11 @@ contents; this would be achieved by \appendixpage \addappheadtotoc </pre> -</blockquote> -The <code>\</code><code>appendixpage</code> command adds a separate title "Appendices" +</blockquote><p> +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 @@ -62,10 +62,10 @@ package options; the above example would be achieved by ... \end{appendices} </pre> -</blockquote> +</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> @@ -86,7 +86,7 @@ as <code>\</code><code>section</code>s. So one might write: \section{Developing the inspiration} ... </pre> -</blockquote> +</blockquote><p> Which will produce output something like: <blockquote> <b>1 My inspiration</b> @@ -95,7 +95,7 @@ Which will produce output something like: <p>... <p><b>2 Developing the inspiration</b> <p>... -</blockquote> +</blockquote><p> <p>There are many other merry things one may do with the package; the user is referred to the package documentation for further details. <p>The <i>memoir</i> class includes the facilities of the diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-archives.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-archives.html index 6abd70d4849..c24be742466 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-archives.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-archives.html @@ -25,7 +25,7 @@ or mirror closest to you. A complete and current list of CTAN sites and known mirrors is available as file <a href="ftp://cam.ctan.org/tex-archive/CTAN.sites">CTAN.sites</a> on the archives themselves. <p>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-doc/doc/english/FAQ-en/html/FAQ-askquestion.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-askquestion.html index 91065d6b5cb..45a5b3e0f5a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-askquestion.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-askquestion.html @@ -2,59 +2,59 @@ <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 -going to <a href="FAQ-maillists.html">ask your question</a>, but how do you +<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 needs your local <i>xyzthesis</i> class, or some other resource not generally available, be sure to include a pointer to how the resource can be obtained. -<li> Be as succinct as possible. Your helpers don't usually need to - know <em>why</em> you're doing something, just <em>what</em> you're +<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-doc/doc/english/FAQ-en/html/FAQ-atsign.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsign.html index 6613c579645..f456e10baab 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsign.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsign.html @@ -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 make the '@' sign active, so that +<h3>How to type an ‘@’ sign?</h3> +<p>Long ago, some packages used to make the ‘@’ sign active, 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-doc/doc/english/FAQ-en/html/FAQ-atsigns.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsigns.html index 732a14f49ea..03ca954246c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsigns.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsigns.html @@ -3,10 +3,11 @@ </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. An -exemplar of the problems caused is discussed in -"<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 +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>”. +<p>The problems users see are caused by copying bits of a class +(<code>.cls</code> file) or package (<code>.sty</code> file) into a document, or by including a class or package file into a LaTeX document by some means other than <code>\</code><code>documentclass</code> or <code>\</code><code>usepackage</code>. LaTeX defines internal @@ -15,30 +16,35 @@ 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 wrongly, you solve the problem by using the +<p>If you’ve included a file wrongly, you solve the problem by using the correct command. -<p>If you're using a fragment of a package or class, you may well feel -confused: books such as <a href="FAQ-books.html"><em>The LaTeX Companion</em></a> +<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. -<p>For example, there's a lengthy section in <em>The Companion</em> about -<code>\</code><code>@startsection</code> and how to use it to control the appearance of -section titles. Page 15 discusses the problem; and -suggests that you make such changes in the document preamble, between -<code>\</code><code>makeatletter</code> and <code>\</code><code>makeatother</code>. So the redefinition of -<code>\</code><code>subsection</code> on page 26 could be: +This problem has been solved in the second edition, and in addition, +all the examples from the <em>Companion</em> are now available on-line. +To see the technique in practice, look at the example below, from file +<i>2-2-7.ltx</i> in the <em>Companion</em> examples directory: <blockquote> <pre> \makeatletter -\renewcommand{\subsection}{\@startsection - {subsection}% % name - ... +\renewcommand\subsection{\@startsection + {subsection}{2}{0mm}%name, level, indent + {-\baselineskip}% beforeskip + {0.5\baselineskip}% afterskip {\normalfont\normalsize\itshape}}% style \makeatother </pre> -</blockquote> +</blockquote><p> +(That example appears on page 29 of <em>The LaTeX Companion</em>, +second edition.) <p>The alternative is to treat all these fragments as a package proper, bundling them up into a <code>.sty</code> file and including them with -<code>\</code><code>usepackage</code>. (This approach is marginally preferable, from the -LaTeX purist's point of view.) +<code>\</code><code>usepackage</code>; this way you hide your LaTeX internal code somewhere +that LaTeX internal code is expected, which often looks ‘tidier’. +<dl> +<dt><tt><i>Examples from the Companion</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/examples/tlc2.zip">info/examples/tlc2</a> (<a href="ftp://cam.ctan.org/tex-archive/info/examples/tlc2.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/examples/tlc2/">browse</a>) +</dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsigns">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsigns</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atvert.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atvert.html index 69420aa5e11..379e4e22925 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atvert.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atvert.html @@ -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-doc/doc/english/FAQ-en/html/FAQ-backref.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-backref.html index 7b96f1ff472..d8def1f0f13 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-backref.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-backref.html @@ -9,8 +9,8 @@ citing command, is often useful in large documents. <i>hyperref</i> bundle, and supports hyperlinks back to the citing command. <i>Citeref</i> is the older, and seems to rely on rather simpler (and therefore possibly more stable) code. Neither collapses -lists of pages ("<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-doc/doc/english/FAQ-en/html/FAQ-badhyph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-badhyph.html index d2b9a1f7914..02c169f6c36 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-badhyph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-badhyph.html @@ -19,17 +19,17 @@ -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-doc/doc/english/FAQ-en/html/FAQ-balance.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-balance.html index 6cbaf7f7400..5224ff99625 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-balance.html +++ b/Master/texmf-doc/doc/english/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,7 +35,7 @@ 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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-baselinepar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-baselinepar.html index bbb9ff88461..ac4d3a411ea 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-baselinepar.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-baselinepar.html @@ -10,12 +10,12 @@ single character with a larger size, as: <pre> {\Huge A} </pre> -</blockquote> -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 +</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 (<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 ... @@ -23,7 +23,7 @@ Paragraph text ... ... into the paragraph.} ... paragraph continues ... </pre> -</blockquote> +</blockquote><p> will look silly, since the <code>8pt</code> interjection will end up set on the <code>12pt</code> <code>\</code><code>baselineskip</code> of the paragraph, rather than its preferred <code>8.5pt</code>. Finally, something like @@ -35,7 +35,7 @@ Paragraph text ... Next paragraph starts... </pre> -</blockquote> +</blockquote><p> will set the body of the first paragraph on the constricted <code>\</code><code>baselineskip</code> of the <code>\</code><code>footnotesize</code> comment. <p>So, how to deal with these problems? The oversized (short) section is @@ -51,11 +51,11 @@ Paragraph text ... {\Huge A\strut} ... paragraph continues ... </pre> -</blockquote> +</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 @@ -72,7 +72,7 @@ Paragraph text ... \end{quote} ... paragraph continues ... </pre> -</blockquote> +</blockquote><p> Such quote-bracketing also deals with the problem of a trailing comment on the paragraph. <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=baselinepar">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=baselinepar</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibaccent.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibaccent.html index 8fb52729811..743ad3855b3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibaccent.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibaccent.html @@ -6,9 +6,9 @@ <a href="FAQ-capbibtex.html">case of letters in your bibliography</a>, also makes a hash of accent commands: -"<code>ma\~nana</code>" comes out as "ma nana" (!). The solution is +“<code>ma\~nana</code>” comes out as “ma nana” (!). The solution is similar: enclose the troublesome sequence in braces, as -"<code>{</code><code>\~n</code><code>}</code>", in this example. +“<code>{</code><code>\~n</code><code>}</code>”, in this example. <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibaccent">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibaccent</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibinline.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibinline.html index 7c4cdfba27d..5e637b2650b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibinline.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibinline.html @@ -12,8 +12,10 @@ the entry appear in a footnote. on the format of entry that your <code>.bst</code> file generates, but is otherwise undemanding of the bibliography style. <li> The package <i>inlinebib</i>, which requires that you use its - <i>inlinebib.bst</i> -<li> The package <i>jurabib</i>, which was originally targetted at + <i>inlinebib.bst</i>. <i>Inlinebib</i> was actually designed for + footnote citations: its <em>expected</em> use is that you place a + citation inline as the argument of a <code>\</code><code>footnote</code> command. +<li> The package <i>jurabib</i>, which was originally designed for German law documents, and has comprehensive facilities for the manipulation of citations. The package comes with four bibliography styles that you may use: <i>jurabib.bst</i>, <i>jhuman.bst</i> and @@ -22,13 +24,13 @@ the entry appear in a footnote. <p>Options for entries in footnotes are <ul> <li> The package <i>footbib</i>, and -<li> The package <i>jurabib</i>, again. +<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's -best to use <i>jurabib</i>, to avoid confusion of footnotes and -foot-citations. +footnotes. Therefore, in a document which has other footnotes, it may +be advisable to use <i>jurabib</i> (or of course +<i>inlinebib</i>), to avoid confusion of footnotes and foot-citations. <dl> <dt><tt><i>bibentry.sty</i></tt><dd><em>Distributed with</em> <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.zip">macros/latex/contrib/natbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib/">browse</a>) <dt><tt><i>footbib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footbib.zip">macros/latex/contrib/footbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footbib/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibplain.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibplain.html index dcb02c736ef..f9b2d7d49e1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibplain.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibplain.html @@ -8,7 +8,7 @@ TeX, either directly or with <a href="FAQ-eplain.html">Eplain</a>. See <a href="FAQ-BibTeXing.html">the use of BibTeX</a> for more information about BibTeX itself. <dl> -<dt><tt><i>btxmac.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/eplain/btxmac.tex">macros/eplain/btxmac.tex</a> +<dt><tt><i>btxmac.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/eplain/tex/eplain/btxmac.tex">macros/eplain/tex/eplain/btxmac.tex</a> <dt><tt><i>eplain system</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/eplain.zip">macros/eplain</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/eplain.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/eplain/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibplain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibplain</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibprefixsort.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibprefixsort.html index 38a5510a169..39de6ce1905 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibprefixsort.html +++ b/Master/texmf-doc/doc/english/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: @@ -25,8 +25,32 @@ follows: @ARTICLE{Rayleigh1, AUTHOR = "{\noopsort{Rayleigh}}{Lord Rayleigh}", ... +} </pre> -</blockquote> +</blockquote><p> +Note that this <code>\</code><code>noopsort</code> applies to the last name in this kind of +construct, so an author with an Arabic name might be rendered: +<blockquote> +<pre> +... +AUTHOR = "Ali {\noopsort{Hadiidii}}{al-Hadiidii}", +... +</pre> +</blockquote><p> + +A further use might deal with word order games, as in the famous +Vietnamese name: +<blockquote> +<pre> +... +AUTHOR = "\noopsort{Thanh Han The}{Han The Thanh}", +... +</pre> +</blockquote><p> + +though that author seems well-acquainted with Western confusion about +the significance of the parts of his name (even to the extent of +missing out the accentuation, as above...). <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibprefixsort">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibprefixsort</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibstrtl.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibstrtl.html index 97f9387bc33..806f8c86d0f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibstrtl.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibstrtl.html @@ -1,35 +1,42 @@ <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 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 +<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 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="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/abstract.bst">biblio/bibtex/contrib/abstract.bst</a>), and rename it (e.g., on a -long file-name system to <i>abstract-long.bst</i>). Now edit it: find +from CTAN — <a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/bibtools/abstract.bst">biblio/bibtex/utils/bibtools/abstract.bst</a>), and rename it (e.g., on a +long file-name system, to <i>abstract-long.bst</i>). Now edit it: find function <code>output.nonnull</code> and <ul> <li> change its first line (line 60 in the version on CTAN) - from <code>"{ 's :="</code> to <code>"{ swap$"</code>, and -<li> delete its last line, which just says <code>"s"</code> (line 84 in the - version on CTAN). + from + <blockquote> +<pre> +{ 's := +</pre> + </blockquote><p> +to + <blockquote> +<pre> +{ swap$ +</pre> + </blockquote><p> + Finally, +<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> - - - - -<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> @@ -40,7 +47,7 @@ of the entry in a separate file: abstract = "{\input{abstracts/long.tex}}" } </pre> -</blockquote> +</blockquote><p> In this way, you arrange that all BibTeX has to deal with is the file name, though it will tell TeX (when appropriate) to include all the long text. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtocorder.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtocorder.html index 84d7ec73f90..0545356846a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtocorder.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-bibtranscinit.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtranscinit.html index 5a8d9c11f4c..bcdf6c20345 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtranscinit.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtranscinit.html @@ -13,12 +13,12 @@ Consider the following example from the real world: title = ... } </pre> -</blockquote> -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, ...". +</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, ...”. <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 @@ -33,12 +33,12 @@ you need to add that command to your bibliography with the title = ... } </pre> -</blockquote> +</blockquote><p> If you have many such commands, you may want to put them in a separate file and <code>\</code><code>input</code> that LaTeX file in a <code>@preamble</code> directive. <p>An alternative is to make the transcription look like an accent, from -BibTeX'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> @@ -47,9 +47,9 @@ does nothing: title = ... } </pre> -</blockquote> +</blockquote><p> Like the solution by generating extra commands, this involves tedious extra typing; which of the two techniques is preferable for a given bibliography will be determined by the names in it. -<p><p><p><p><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> +<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibtranscinit">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibtranscinit</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bold-extras.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bold-extras.html index cd52419820d..7cea6ff7058 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bold-extras.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bold-extras.html @@ -2,39 +2,45 @@ <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-wherefiles.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-instpackages.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>. -Of course, commercial fixed-width fonts (even the default -<i>Courier</i>) almost always come with a bold variant, so that's +<p>Of course, commercial fixed-width fonts (even the default +<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 -compunctions about providing them in a bold form. +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 +freely available (monospace text in the typeset version of this +FAQ uses <i>LuxiMono</i>, with the metrics and LaTeX +support available on the archive. <dl> <dt><tt><i>bold-extra.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/bold-extra.sty">macros/latex/contrib/misc/bold-extra.sty</a> <dt><tt><i>bold tt and small caps fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/mf-extra/bold.zip">fonts/cm/mf-extra/bold</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/cm/mf-extra/bold.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/mf-extra/bold/">browse</a>) +<dt><tt><i>LuxiMono fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/LuxiMono.zip">fonts/LuxiMono</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/LuxiMono.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/LuxiMono/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bold-extras">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bold-extras</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-boldgreek.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-boldgreek.html index 20b00c7d35a..aa7f2f46ea9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-boldgreek.html +++ b/Master/texmf-doc/doc/english/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. @@ -16,14 +16,14 @@ outlined below. <pre> {\boldmath$\theta$} </pre> -</blockquote> -but <code>\</code><code>boldmath</code> may not be used in maths mode, so this 'solution' +</blockquote><p> +but <code>\</code><code>boldmath</code> may not be used in maths mode, so this ‘solution’ requires arcana such as: <blockquote> <pre> $... \mbox{\boldmath$\theta$} ...$ </pre> -</blockquote> +</blockquote><p> which then causes problems in superscripts, etc. <p>These problems may be addressed by using a bold mathematics package. <ul> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-books.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-books.html index 3da9f7a3143..c18343690e5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-books.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-books.html @@ -2,31 +2,31 @@ <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 - <a href="FAQ-tutorials.html">(La)TeX tutorials</a>) + ISBN 0-201-56882-9 — now out of print, but see + <a href="FAQ-ol-books.html">online books</a>) <dt>TeX for the Beginner<dd>by Wynter Snow (Addison-Wesley, 1992, ISBN 0-201-54799-6) <dt>TeX for the Impatient<dd>by Paul W. Abrahams, Karl Berry and Kathryn A. Hargreaves (Addison-Wesley, 1990, - ISBN 0-201-51375-7 - now out of print, but see - <a href="FAQ-tutorials.html">(La)TeX tutorials</a>) + 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 @@ -37,23 +37,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> @@ -83,6 +83,10 @@ For LaTeX, see: +<dt>Digital Typography Using LaTeX<dd>Incorporating some + multilingual aspects, and use of <a href="FAQ-omegaleph.html">Omega</a>, by + Apostolos Syropoulos, Antonis Tsolomitis and Nick Sofroniou + (Springer, 2003, ISBN 0-387-95217-9). <p> A list of errata for the first printing is available from: <a href="http://www.springer-ny.com/catalog/np/jan99np/0-387-98708-8.html">http://www.springer-ny.com/catalog/np/jan99np/0-387-98708-8.html</a> <dt>First Steps in LaTeX<dd>by George Grätzer (Birkhäuser, 1999, @@ -95,30 +99,30 @@ For LaTeX, see: 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-tutorials.html">tutorials</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-doc/doc/english/FAQ-en/html/FAQ-braket.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-braket.html index 9967f3edf52..75d2f9113a5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-braket.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-braket.html @@ -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>\left( <expression> \right)</code> - the size of the parentheses is +<code>\left( <expression> \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 @@ -17,11 +17,11 @@ needing a <code>\</code><code>middle</code> command, to be used in expressions l \left\{ x \in \mathbb{N} \middle| x \mbox{ even} \right\} </pre> -</blockquote> +</blockquote><p> to specify the set of even natural numbers. The -<a href="FAQ-NTS.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 +<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 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. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-breakbox.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-breakbox.html index aeec4e372d6..f150d1cee64 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-breakbox.html +++ b/Master/texmf-doc/doc/english/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. @@ -33,11 +33,11 @@ device-independent Metafont for the shading). The author of there are reasons to suspect that it may be unstable working with current LaTeX. <dl> -<dt><tt><i>backgrnd.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/backgrnd.tex">macros/generic/backgrnd.tex</a> +<dt><tt><i>backgrnd.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/misc/backgrnd.tex">macros/generic/misc/backgrnd.tex</a> <dt><tt><i>boites.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/boites.zip">macros/latex/contrib/boites</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/boites.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/boites/">browse</a>) <dt><tt><i>framed.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/framed.sty">macros/latex/contrib/misc/framed.sty</a> <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) -<dt><tt><i>shade.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/shade.sty">macros/generic/shade.sty</a> +<dt><tt><i>shade.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/shade.zip">macros/generic/shade</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/generic/shade.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/generic/shade/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=breakbox">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=breakbox</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-breaklinks.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-breaklinks.html index a4abc5c3e8e..224d26ffa3d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-breaklinks.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-breaklinks.html @@ -1,9 +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 @@ -13,14 +14,30 @@ 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 only known solution to this problem is to use the -<i>breakurl</i> package. This package provides a very simple -solution: in place of the single link, the <code>\</code><code>burl</code> command produces -a sequences of small pieces, between each of which a line break is -permitted. Each sequence of pieces, that ends up together in one +<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 +this case <i>hyperref</i> employs the <i>url</i> package to +split up the URL (as described in +<a href="FAQ-setURL.html">typesetting URLs</a>), but the +<i>dvips</i> driver then suppresses the breaks. The way out is +the <i>breakurl</i> package, which modifies the <code>\</code><code>url</code> command +to produce several smaller pieces, between each of which a line break +is permitted. Each group of pieces, that ends up together in one line, is converted to a single clickable link. +<p>Second, if you have a table of contents, list of figure or tables, or +the like, <i>hyperref</i> will ordinarily make the titles in the +table of contents, or captions in the lists, active. If the title or +caption is long, it will need to break within the table, but the +<i>dvips</i> driver will prevent that. In this case, load +<i>hyperref</i> with the option <code>linktocpage</code>, and only +the page number will be made active. +<p>Otherwise, if you have a lengthy piece of text that you want active, +you have at present no simple solution: you have to rewrite your text, +or to use a different PDF generation mechanism. <dl> <dt><tt><i>breakurl.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/breakurl.zip">macros/latex/contrib/breakurl</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/breakurl.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/breakurl/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-brkinline.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-brkinline.html new file mode 100644 index 00000000000..a10665e1067 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-brkinline.html @@ -0,0 +1,54 @@ +<head> +<title>UK TeX FAQ -- question label brkinline</title> +</head><body> +<h3>Line-breaking in in-line maths</h3> +<p>TeX, by default, allows you to split a mathematical expression at +the end of the line; it allows breaks at relational operators (like +“=”, “<”, 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” +associated with each type of operator: the penalty + says how +undesirable a break at each point is. Default values are: +<blockquote> +<pre> +\relpenalty = 500 +\binoppenalty = 700 +</pre> +</blockquote><p> +You make the break progressively less attractive by increasing these +values. You can actually forbid all breaks, everywhere, by: +<blockquote> +<pre> +\relpenalty = 10000 +\binoppenalty = 10000 +</pre> +</blockquote><p> +If you want just to prevent breaks in a single expression, write: +<blockquote> +<pre> +{% + \relpenalty = 10000 + \binoppenalty = 10000 + $a=b+c$ +} +</pre> +</blockquote><p> +and the original values will remain undisturbed outside the braces. +This is tedious: there is often value in an alternative approach, +in which you say which parts of the expression may not break whatever +happens, and fortunately this is surprisingly easy. Suppose we want +to defer a break until after the equality, we could write: +<blockquote> +<pre> +${a+b+c+d} = z+y+x+w$ +</pre> +</blockquote><p> +The braces say “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><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-doc/doc/english/FAQ-en/html/FAQ-buffovl.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buffovl.html index 4fbfbd20aa9..5dbf6e85c97 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buffovl.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-bug.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bug.html index dd613b47bc3..0468681e93f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bug.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bug.html @@ -7,29 +7,42 @@ <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, -however. He only looks at bugs once or twice a year, and even then +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@math.ams.org</i>), or contact +(<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> -using mechanisms supplied in the LaTeX distribution. -<p>If you've found a bug in LaTeX 2.09, or some other such unsupported -software, there's not a lot you can do about it. You may find help or +<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 +contacting the author (if you can find a contact address). However, +it’s generally best to treat any package as unsupported, in the first +instance, and only try the author <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 +software, you may find help or <em>de facto</em> support on a newsgroup such as <i>comp.tex.tex</i> or on a mailing list such as -<a href="mailto:texhax@tug.org"><i>texhax@tug.org</i></a>, but posting non-bugs to any of these forums -can lay you open to ridicule! Otherwise you may need to pay for -help - TUG maintains a +<a href="mailto:texhax@tug.org"><i>texhax@tug.org</i></a>; be carefule to include a +<a href="FAQ-minxampl.html">code example</a> of the +failure, if relevant. +<p>Failing all else, you may need to pay for +help — TUG maintains a <a href="http://www.tug.org/consultants.html">register of TeX consultants</a>. -<p></body> +<p><p> + + + +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buildbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buildbib.html index 15f08699153..5a5cf86848e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buildbib.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buildbib.html @@ -10,35 +10,34 @@ 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 (there's no documentation other than the oddly-named - <i>tex2bib.readme</i>). + probably help. <li> There are a number of BibTeX bibliography management systems available, some of which permit a graphical user interface to the task. Sadly, none seems to be available with the ordinary TeX distributions. <p> Tools such as <i>Xbibfile</i> (a graphical user interface), - <i>ebib</i> (a database application written to run '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. @@ -59,15 +58,18 @@ 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 - subscription service, available to UK academics as BIDS). + 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> </ul> <dl> +<dt><tt><i>bids.to.bibtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/bids/bids.to.bibtex">biblio/bibtex/utils/bids/bids.to.bibtex</a> <dt><tt><i>btOOL</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/btOOL.zip">biblio/bibtex/utils/btOOL</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/btOOL.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/btOOL/">browse</a>) <dt><tt><i>ebib</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/ebib.zip">biblio/bibtex/utils/ebib</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/ebib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/ebib/">browse</a>) <dt><tt><i>isi2bibtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/isi2bibtex.zip">biblio/bibtex/utils/isi2bibtex</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/isi2bibtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/isi2bibtex/">browse</a>) -<dt><tt><i>tex2bib</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/tex2bib/tex2bib">biblio/bibtex/contrib/tex2bib/tex2bib</a> -<dt><tt><i>tex2bib.readme</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/tex2bib/tex2bib.readme">biblio/bibtex/contrib/tex2bib/tex2bib.readme</a> +<dt><tt><i>tex2bib</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/tex2bib/tex2bib">biblio/bibtex/utils/tex2bib/tex2bib</a> +<dt><tt><i>tex2bib.readme</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/tex2bib/README">biblio/bibtex/utils/tex2bib/README</a> <dt><tt><i>xbibfile</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/xbibfile.zip">biblio/bibtex/utils/xbibfile</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/xbibfile.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/xbibfile/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=buildbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=buildbib</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cancellation.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cancellation.html index 73befe2ed4e..835fac1369a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cancellation.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cancellation.html @@ -4,8 +4,8 @@ <h3>Cancelling terms in maths expressions</h3> <p>A technique used when explaining the behaviour of expressions or equations (often for pedagogical purposes). The <i>cancel</i> -package provides several variants of cancellation marks ("<code>\</code>", -"<code>/</code>" and "<code>X</code>"), and a means of cancelling 'to' a particular +package provides several variants of cancellation marks (“<code>\</code>”, +“<code>/</code>” and “<code>X</code>”), and a means of cancelling ‘to’ a particular value. <p>Documentation of <i>cancel</i> is in the package file. <dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-capbibtex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-capbibtex.html index 614b55f97a2..e02940bd381 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-capbibtex.html +++ b/Master/texmf-doc/doc/english/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.). @@ -14,7 +14,7 @@ BibTeX should not touch, in braces, as: <pre> title = {The {THE} operating system}, </pre> -</blockquote> +</blockquote><p> Sometimes you find BibTeX changing the case of a single letter inappropriately. No matter: the technique can be applied to single letters, as in: @@ -22,21 +22,21 @@ letters, as in: <pre> title = {Te{X}niques and tips}, </pre> -</blockquote> +</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> title = {{TeXniques and tips}}, </pre> -</blockquote> +</blockquote><p> though that does ensure that the capitalisation is not changed. Your BibTeX database should be a general-purpose thing, not something tuned to the requirements of a particular document, or to the way you are thinking today. -<p>There'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-doc/doc/english/FAQ-en/html/FAQ-captsty.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-captsty.html index 6acb9de0b2e..77936b06c80 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-captsty.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-captsty.html @@ -6,25 +6,25 @@ 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}} </pre> -</blockquote> +</blockquote><p> which will cause the number to be typeset in bold face. (Note that the original definition used <a href="FAQ-fixnam.html"><code>\</code><code>figurename</code></a>.) More elaborate changes can be made by patching the <code>\</code><code>caption</code> command, but since there are packages to do the job, such changes (which can get rather tricky) -aren'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-doc/doc/english/FAQ-en/html/FAQ-casechange.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-casechange.html index 7aa645c40ef..6a8daaa7085 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-casechange.html +++ b/Master/texmf-doc/doc/english/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 @@ -15,13 +15,13 @@ They have (for example) no mathematical sense, and <pre> \uppercase{About $y=f(x)$} </pre> -</blockquote> +</blockquote><p> will produce <blockquote> <pre> ABOUT $Y=F(X)$ </pre> -</blockquote> +</blockquote><p> which is probably not what is wanted. <p>In addition, <code>\</code><code>uppercase</code> and <code>\</code><code>lowercase</code> do not deal very well with non-American characters, for example @@ -43,12 +43,12 @@ using a user-defined command, for example: \section{A section title \protect\mytable{} with a table} </pre> -</blockquote> +</blockquote><p> Note that <code>\</code><code>mytable</code> has to be protected, otherwise it will be expanded and made upper case; you can achieve the same result by declaring it with <code>\</code><code>DeclareRobustCommand</code>, in which case the -<code>\</code><code>protect</code> won'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,10 +56,10 @@ 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>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>) +<dt><tt><i>textcase.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textcase.zip">macros/latex/contrib/textcase</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textcase.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textcase/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=casechange">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=casechange</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changebars.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changebars.html index ab3577e3668..f9785178d79 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changebars.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changebars.html @@ -3,15 +3,15 @@ </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 being that TeX 'proper' -doesn't provide the programmer with any information about the -"current position" from which a putative start- or end-point of a +the commonest technique, “change bars” (also known as “revision +bars”), requires surprisingly much +trickery of the programmer (the problem being that TeX ‘proper’ +doesn’t provide the programmer with any information about the +“current position” from which a putative start- or end-point of a bar might be calculated; PDFTeX <em>does</em> provide the -information, but we're not aware yet of any programmer taking +information, but we’re not aware yet of any programmer taking advantage of the fact to write a PDFTeX-based changebar package). -<p>The simplest package that offers change bars is Peter Schmitt'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 @@ -19,23 +19,26 @@ information that <i>backgrnd</i> patches their output routine, and will watch its behaviour very carefully (patching the LaTeX output routine is not something to undertake lightly...). <p>The longest-established solution is the <i>changebar</i> package, -which uses <code>\</code><code>special</code> commands supplied by the driver 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 generate <code>\</code><code>special</code>s for (in the same way that you need to tell the <i>graphics</i> package); the list of available drivers is pretty -restricted, but does include <i>dvips</i>. The package comes with +wide, but does not include <i>dvipdfm</i>. The package comes with a shell script <i>chbar.sh</i> (for use on Unix machines) that will compare two documents and generate a third which is marked-up -with <i>changebar</i> macros to highlight changes. The (excellent) +with <i>changebar</i> macros to highlight changes. The shareware <i>WinEDT</i> editor has a macro that will generate <i>changebar</i> (or other) macros to show differences from an earlier version of your file, stored in an -<i>RCS</i>-controlled repository - see +<i>RCS</i>-controlled 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 must be present); it's thus the -smallest of the packages for change bar marking, since it leaves all -the trickery to another package. The <i>framed</i> package is +<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 +change bar marking, since it leaves all the trickery to another +package. <i>Vertbars</i> defines a <code>vertbar</code> +environment to create changebars. +<p>The <i>framed</i> package is another that provides bars as a side-effect of other desirable functionality: its <code>leftbar</code> environment is simply a stripped-down frame (note, though, that the environment makes a @@ -44,20 +47,20 @@ 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>Another way to keep track of changes is employed by some -word-processors - to produce a document that embodies both "old" -and "new" versions. The <i>Perl</i> script <i>latexdiff</i> +word-processors — to produce a document that embodies both “old” +and “new” versions. The <i>Perl</i> script <i>latexdiff</i> does this for LaTeX documents; you feed it the two documents, and it produces a new LaTeX document in which the changes are very visible. An example of the output is embedded in the documentation, <a href="http://www.tex.ac.uk/tex-archive/support/latexdiff/latexdiff-man.pdf">latexdiff-man.pdf</a> (part of the distribution). -A rudimentary revision facilility is provided by another +A rudimentary revision facility is provided by another <i>Perl</i> script, <i>latexrevise</i>, which accepts or rejects all changes. Manual editing of the difference file can be used to accept or reject selected changes only. <dl> -<dt><tt><i>backgrnd.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/backgrnd.tex">macros/generic/backgrnd.tex</a> +<dt><tt><i>backgrnd.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/misc/backgrnd.tex">macros/generic/misc/backgrnd.tex</a> <dt><tt><i>changebar.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/changebar.zip">macros/latex/contrib/changebar</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/changebar.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/changebar/">browse</a>) <dt><tt><i>framed.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/framed.sty">macros/latex/contrib/misc/framed.sty</a> <dt><tt><i>latexdiff, latexrevise</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/latexdiff.zip">support/latexdiff</a> (<a href="ftp://cam.ctan.org/tex-archive/support/latexdiff.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/latexdiff/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changemargin.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changemargin.html index 9c95b56aff8..153d7c2567f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changemargin.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changemargin.html @@ -2,101 +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>Lamport's warning to beginners in his section on 'Customizing the -Style' - "don't do it" - needs to be taken seriously. One-inch -margins on A4 paper are 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>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 -comprehensive. -<p>Somewhat simpler to use is the <i>vmargin</i> package, which has a -canned set of paper sizes (a superset of that provided in LaTeX2e), -provision for custom paper, margin adjustments and provision for -two-sided printing. -<p>LaTeX controls the page layout with a number of parameters, which -allow you to change the distance from the edges of a page to the left -and top edges of your typeset text, the width and height of the text, -and the placement of other text on the page. However, they are -somewhat complex, and it is easy to get their interrelationships wrong -when redefining the page layout. The layout package defines a -<code>\</code><code>layout</code> command which draws a diagram of your existing page -layout, with the dimensions (but not their interrelationships) shown. -This FAQ recommends that you use a package to establish +<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 +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>This set of FAQs recommends that you use a package to establish consistent settings of the parameters: the interrelationships are taken care of in the established packages, without you needing to -think about them. -<p>If you're still eager to "do it yourself", 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>The text height and width, <code>\</code><code>textheight</code> and <code>\</code><code>textwidth</code>, -require more care than you might expect: the height should be set to -fit an integral number of text lines, and the width should be -constrained by the number of characters per line, as mentioned above. -<p>Margins are controlled by three parameters. The pair -<code>\</code><code>oddsidemargin</code> and <code>\</code><code>evensidemargin</code> are so-called because it -is conventionally taken that odd-numbered pages appear on the -right-hand side of a two-page spread ('recto') and even-numbered pages -on the left-hand side ('verso'). Both parameters refer to the -left-hand margin; the right-hand margin is specified by implication, -from the size of <code>\</code><code>textwidth</code> and the width of the paper. The -"origin" (the zero position) on the page is one inch from the top of -the paper and one inch from the left side; positive horizontal -measurements extend right across the page, and positive vertical -measurements extend down the page. Thus, the parameters -<code>\</code><code>evensidemargin</code>, <code>\</code><code>oddsidemargin</code> and <code>\</code><code>topmargin</code>, should -be set to be 1 inch less than the true margin; for margins closer to -the left and top edges of the page than 1 inch, the margin parameters -must be set to negative values. -<p>Another surprise is that you cannot change the width or height of the -text within the document, simply by modifying the text size -parameters. The simple rule is that the parameters should only be -changed in the preamble of the document, i.e., before the -<code>\</code><code>begin{document}</code> statement. To adjust text width within a -document we define an environment: -<blockquote> -<pre> -\newenvironment{changemargin}[2]{% - \begin{list}{}{% - \setlength{\topsep}{0pt}% - \setlength{\leftmargin}{#1}% - \setlength{\rightmargin}{#2}% - \setlength{\listparindent}{\parindent}% - \setlength{\itemindent}{\parindent}% - \setlength{\parsep}{\parskip}% - }% - \item[]}{\end{list}} -</pre> -</blockquote> -This environment takes two arguments, and will indent the left and -right margins, respectively, by the parameters' values. Negative -values will cause the margins to be narrowed, so -<code>\</code><code>begin{changemargin}{-1cm}</code>{-1cm} narrows the left and right -margins by 1cm. -<p>The <i>chngpage</i> package provides ready-built commands to do the -above; it includes provision for changing the shifts applied to your -text according to whether you're on an odd or an even page of a -two-sided document. The package's documentation (in the file itself) -suggests a strategy for changing text dimensions between pages - as -mentioned above, changing the text dimensions within the body of a -page may lead to unpredictable results. -<dl> -<dt><tt><i>chngpage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/chngpage.sty">macros/latex/contrib/misc/chngpage.sty</a> -<dt><tt><i>geometry.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/geometry.zip">macros/latex/contrib/geometry</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/geometry.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/geometry/">browse</a>) -<dt><tt><i>layout.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) -<dt><tt><i>vmargin.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/vmargin.zip">macros/latex/contrib/vmargin</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/vmargin.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/vmargin/">browse</a>) -</dl> +think about them, but +<p>The following answers deal with the ways one may choose to proceed: +<ul> +<li> <a href="FAQ-marginpkgs.html">Choose which package to use</a>. +<li> <a href="FAQ-marginmanual.html">Find advice on setting up page layout by hand</a>. +</ul> +There is a related question — 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> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=changemargin">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=changemargin</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chapbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chapbib.html index 4b7ec58be9f..9d480244e66 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chapbib.html +++ b/Master/texmf-doc/doc/english/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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-charshift.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-charshift.html index 504e9cf57e9..12d73558d35 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-charshift.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-charshift.html @@ -3,17 +3,17 @@ </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-doc/doc/english/FAQ-en/html/FAQ-chngmargonfly.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chngmargonfly.html new file mode 100644 index 00000000000..5a0616a5a66 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chngmargonfly.html @@ -0,0 +1,65 @@ +<head> +<title>UK TeX FAQ -- question label chngmargonfly</title> +</head><body> +<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 +on the fly, and LaTeX only ever looks at text height when starting +a new page. +<p>So the simple rule is that the parameters should only be +changed in the preamble of the document, i.e., before the +<code>\</code><code>begin{document}</code> statement (so before any typesetting has +happened. +<p>To adjust text width within a document we define an environment: +<blockquote> +<pre> +\newenvironment{changemargin}[2]{% + \begin{list}{}{% + \setlength{\topsep}{0pt}% + \setlength{\leftmargin}{#1}% + \setlength{\rightmargin}{#2}% + \setlength{\listparindent}{\parindent}% + \setlength{\itemindent}{\parindent}% + \setlength{\parsep}{\parskip}% + }% + \item[]}{\end{list}} +</pre> +</blockquote><p> +The environment takes two arguments, and will indent the left and +right margins, respectively, by the parameters’ 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 +environment (which is a close relation of the LaTeX +<code>quote</code> environment) <em>doesn’t</em> change the text width +as far as TeX is concerned: it merely moves text around inside the +width that TeX believes in. +<p>The <i>chngpage</i> package provides ready-built commands to do the +above; it includes provision for changing the shifts applied to your +text according to whether you’re on an odd or an even page of a +two-sided document. The package’s documentation (in the file itself) +suggests a strategy for changing text dimensions between pages — as +mentioned above, changing the text dimensions within the body of a +page may lead to unpredictable results. +<p>Changing the vertical dimensions of a page is clunkier still: the +LaTeX command <code>\</code><code>enlargethispage</code> adjusts the size of the current +page by the size of its argument. Common uses are +<blockquote> +<pre> +\enlargethispage{\baselineskip} +</pre> +</blockquote><p> +to make the page one line longer, or +<blockquote> +<pre> +\enlargethispage{-\baselineskip} +</pre> +</blockquote><p> +to make the page one line shorter. +<dl> +<dt><tt><i>chngpage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/chngpage.sty">macros/latex/contrib/misc/chngpage.sty</a> +</dl> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chngmargonfly">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chngmargonfly</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citeURL.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citeURL.html index 1d64912d08f..3e41089bc68 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citeURL.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citeURL.html @@ -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: @@ -26,23 +26,29 @@ entry will look like: howpublished = "\url{http://...}" } </pre> -</blockquote> +</blockquote><p> A possible alternative approach is to use BibTeX styles other than the standard ones, that already have URL entry types. -Pre-eminent are the <i>natbib</i> styles (<i>plainnat</i>, -<i>unsrtnat</i> and <i>abbrevnat</i>). These styles are -extensions of the standard styles, principally for use with -<i>natbib</i> itself, but 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. -<p>Another candidate is the <i>harvard</i> package (if its citation -styles are otherwise satisfactory for you). <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). -<p>You can also acquire new BibTeX styles by use of Norman Gray's +Candidates are: +<ul> +<li> The <i>natbib</i> styles (<i>plainnat</i>, + <i>unsrtnat</i> and <i>abbrevnat</i>), which are extensions of + the standard styles, principally for use with <i>natbib</i> + itself. However, they’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>” + 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 <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 @@ -61,17 +67,18 @@ cases, a useful technique is something like: } </pre> -</blockquote> +</blockquote><p> There is good reason to use the <i>url</i> or <i>hyperref</i> packages in this context: BibTeX has a habit of splitting lines it considers excessively long, and if there are no space -characters for it to use as '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="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/babelbib.zip">biblio/bibtex/contrib/babelbib</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/babelbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/babelbib/">browse</a>) <dt><tt><i>custom-bib bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/custom-bib.zip">macros/latex/contrib/custom-bib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/custom-bib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/custom-bib/">browse</a>) <dt><tt><i>harvard.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/harvard.zip">macros/latex/contrib/harvard</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/harvard.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/harvard/">browse</a>) <dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citesort.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citesort.html index 028e0afffcb..e8297ccbc5e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citesort.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citesort.html @@ -4,17 +4,17 @@ <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, +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>If you might need to make hyperreferences to your citations, -<i>cite</i> isn't adequate. If you add the <i>hypernat</i> +<i>cite</i> isn’t adequate. If you add the <i>hypernat</i> package: <pre> \usepackage[...]{hyperref} diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-clsvpkg.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-clsvpkg.html new file mode 100644 index 00000000000..98120322eeb --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-clsvpkg.html @@ -0,0 +1,31 @@ +<head> +<title>UK TeX FAQ -- question label clsvpkg</title> +</head><body> +<h3>What are LaTeX classes and packages?</h3> +<p>Current LaTeX makes a distinction between the macros that define the +overall layout of a document, and the macros that tweak that layout +(to one extent or another) to provide what the author <em>really</em> +wants. +<p>The distinction was not very clear in LaTeX 2.09, and after some +discussion (in the later stages of development of current LaTeX) +the names “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 +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 +disc by a file called <i>footmisc.sty</i>. +<p>The user defines the class of his document with the +<code>\</code><code>documentclass</code> command (typically the first command in a +document), and loads packages with the <code>\</code><code>usepackage</code> command. A +document may have several <code>\</code><code>usepackage</code> commands, but it may have +only one <code>\</code><code>documentclass</code> command. (Note that there are +programming-interface versions of both commands, since a class may +choose to load another class to refine its capabilities, and both +classes and packages may choose to load other packages.) +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=clsvpkg">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=clsvpkg</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cmdstar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cmdstar.html index 0caaa1afd29..cb44adfe439 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cmdstar.html +++ b/Master/texmf-doc/doc/english/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). @@ -17,7 +17,7 @@ of the <i>ifthen</i> package: \newcommand{\mycommandStar}{starred version} \newcommand{\mycommandNoStar}[1]{normal version} </pre> -</blockquote> +</blockquote><p> This does the trick, for sufficiently simple commands, but it has various tiresome failure modes, and it requires <code>\</code><code>mycommandnostar</code> @@ -25,20 +25,21 @@ to take an argument. <p>Of course, the LaTeX kernel has something slicker than this: <blockquote> <pre> -\newcommand{\mycommand}[1]{\@ifstar - \mycommandStar% - \mycommandNoStar% +\newcommand{\mycommand}{\@ifstar + \mycommandStar% + \mycommandNoStar% } -\newcommand{\mycommandStar}{starred version} -\newcommand{\mycommandNoStar}{normal version} +\newcommand{\mycommandStar}[2]{starred version} +\newcommand{\mycommandNoStar}[1]{normal version} </pre> -</blockquote> -Which is all very well, is fast and efficient, but requires the -definition to be <a href="FAQ-atsigns.html"><code>\</code><code>makeatletter</code> protected</a>. -The technique doesn't interfere at all with the definitions of -<code>\</code><code>mycommandStar</code> or <code>\</code><code>mycommandNoStar</code>; they can have any -combination of optional and mandatory arguments that you could define -them to have in the ordinary way. + +</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.) +The <code>\</code><code>@ifstar</code> trick is all very well, is fast and efficient, but +it requires the definition to be +<a href="FAQ-atsigns.html"><code>\</code><code>makeatletter</code> protected</a>. <p>A pleasing alternative is the <i>suffix</i> package. This elegant piece of code allows you to define variants of your commands: @@ -47,18 +48,18 @@ piece of code allows you to define variants of your commands: \newcommand\mycommand{normal version} \WithSuffix\newcommand\mycommand*{starred version} </pre> -</blockquote> -The package needs <a href="FAQ-NTS.html">e-LaTeX</a>, but any new enough +</blockquote><p> +The package needs <a href="FAQ-etex.html">e-LaTeX</a>, but any new enough distribution defines LaTeX as e-LaTeX by default. Command arguments may be specified in the normal way, in both command -definitions (after the "<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> <pre> \WithSuffix\gdef\mycommand*{starred version} </pre> -</blockquote> +</blockquote><p> <dl> <dt><tt><i>ifthen.sty</i></tt><dd>Part of the LaTeX distribution <dt><tt><i>suffix.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-codelist.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-codelist.html index 129b00ade27..fc718386a86 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-codelist.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-codelist.html @@ -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. @@ -33,7 +33,7 @@ int main(int argc, char ** argv) \end{lstlisting} \end{document} </pre> -</blockquote> +</blockquote><p> or you can have it typeset whole files: <blockquote> <pre> @@ -44,9 +44,9 @@ or you can have it typeset whole files: \lstinputlisting{main.c} \end{document} </pre> -</blockquote> +</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 +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 @@ -61,16 +61,16 @@ Documentation is available on the <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 +<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="ftp://cam.ctan.org/tex-archive/support/c2latex.zip">support/c2latex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/c2latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/c2latex/">browse</a>) <dt><tt><i>C++2LaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/C++2LaTeX-1_1pl1.zip">support/C++2LaTeX-1_1pl1</a> (<a href="ftp://cam.ctan.org/tex-archive/support/C++2LaTeX-1_1pl1.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/C++2LaTeX-1_1pl1/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-commercial.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-commercial.html index bc5057661f1..141dc89d7ee 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-commercial.html +++ b/Master/texmf-doc/doc/english/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 @@ -26,7 +26,7 @@ also have email, and normal telephone and fax support. Tel: +1 561-966-8400<br> Email: <a href="mailto:kinch@truetex.com"><i>kinch@truetex.com</i></a><br> Web: <a href="http://www.truetex.com/">http://www.truetex.com/</a> - </blockquote> + </blockquote><p> Source: Mail from Richard Kinch, August 2004. @@ -53,7 +53,7 @@ also have email, and normal telephone and fax support. Fax: +1 415-296-7501<br> Email: <a href="mailto:sales@pctex.com"><i>sales@pctex.com</i></a><br> Web: <a href="http://www.pctex.com/">http://www.pctex.com/</a> - </blockquote> + </blockquote><p> Source: Personal TeX Inc web site, December 2004 <dt>PC; VTeX<dd> DVI, PDF and HTML backends, Visual Tools and Type 1 fonts @@ -66,7 +66,7 @@ also have email, and normal telephone and fax support. Fax: +1 718-575-8038<br> Email: <a href="mailto:support@micropress-inc.com"><i>support@micropress-inc.com</i></a><br> Web: <a href="http://www.micropress-inc.com/">http://www.micropress-inc.com/</a> - </blockquote> + </blockquote><p> Source: Mail from MicroPress, Inc., July 1999 <dt>PC; Scientific Word<dd> Scientific Word and Scientific Workplace offer a mechanism for near-WYSIWYG input of LaTeX documents; they @@ -81,11 +81,10 @@ also have email, and normal telephone and fax support. East Lothian, EH33 1AS<br> UK<br> Tel: 0845 766 0340 (within the UK) <br> - Tel: +44 1875 616516 <br> - Fax: 01875 613513 (within the UK) <br> + Fax: 0845 603 9443 (within the UK) <br> Email: <a href="mailto:christopher@sciword.demon.co.uk"><i>christopher@sciword.demon.co.uk</i></a> <br> Web: <a href="http://www.sciword.demon.co.uk">http://www.sciword.demon.co.uk</a> - </blockquote> + </blockquote><p> <blockquote> MacKichan Software Inc.<br> 19307 8th Avenue, Suite C<br> @@ -96,10 +95,10 @@ also have email, and normal telephone and fax support. Fax: +1 360 394 6039<br> Email: <a href="mailto:info@mackichan.com"><i>info@mackichan.com</i></a><br> Web: <a href="http://www.mackichan.com">http://www.mackichan.com</a> - </blockquote> + </blockquote><p> Source: Mail from Christopher Mabb, November 2004 -<dt>Macintosh; Textures<dd> "A TeX system 'for the rest of - us' "; also gives away a Metafont implementation and some +<dt>Macintosh; Textures<dd> “A TeX system ‘for the rest of + us’ ”; also gives away a Metafont implementation and some font manipulation tools. <blockquote> Blue Sky Research<br> @@ -111,7 +110,7 @@ also have email, and normal telephone and fax support. Fax: +1 503-222-1643<br> Email: <a href="mailto:sales@bluesky.com"><i>sales@bluesky.com</i></a><br> Web: <a href="http://www.bluesky.com/">http://www.bluesky.com/</a> - </blockquote> + </blockquote><p> Source: <i>TUGboat</i> 15(1) (1994) <dt>AmigaTeX<dd> A full implementation for the Commodore Amiga, including full, on-screen and printing support for all PostScript @@ -122,7 +121,7 @@ also have email, and normal telephone and fax support. PO Box 2081<br> Stanford, CA 94309<br> USA - </blockquote> + </blockquote><p> Source: Mail from Tom Rokicki, November 1994 </dl> @@ -130,8 +129,9 @@ also have email, and normal telephone and fax support. <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 -<a href="http://lists.ucc.ie/lists/archives/yandytex.html">mailing list</a> -that was established in 2003. +<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> <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-doc/doc/english/FAQ-en/html/FAQ-compactbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-compactbib.html index 88c497472cb..3465a3bb995 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-compactbib.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-compactbib.html @@ -5,20 +5,20 @@ <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} \setlength{\bibsep}{0.0pt} </pre> -</blockquote> +</blockquote><p> to the preamble of your document. <p>Otherwise, one is into unseemly hacking of something or other. The -<i>mdwlist</i> package actually does the job, but it doesn'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> @@ -29,7 +29,7 @@ BibTeX. Therefore, we need to \setlength{\itemsep}{0pt}% } </pre> -</blockquote> +</blockquote><p> The <i>savetrees</i> package performs such a patch, among a plethora of space-saving measures: you can, in principle, suppress all its other actions, and have it provide you a compressed bibliography diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-compjobnam.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-compjobnam.html index abbbb45fc6f..4f8b465b35e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-compjobnam.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-compjobnam.html @@ -1,14 +1,14 @@ <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> @@ -21,8 +21,8 @@ the "<code>\</code><code>show</code> command" prefix. } </pre> -</blockquote> -And it's used as: +</blockquote><p> +And it’s used as: <blockquote> <pre> \if\jobis{mainfile}% @@ -31,9 +31,9 @@ And it's used as: \message{NO}% \fi </pre> -</blockquote> -Note that the command <code>\</code><code>StripPrefix</code> need not be defined if you're -using LaTeX - there's already an +</blockquote><p> +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-doc/doc/english/FAQ-en/html/FAQ-complist.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-complist.html index 85aebd17959..94d44e84ca4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-complist.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-complist.html @@ -2,16 +2,17 @@ <title>UK TeX FAQ -- question label complist</title> </head><body> <h3>How to reduce 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 -automatically within the list itself. It works by 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, <code>\</code><code>@listi</code> is usually reset -when the font size is changed. As a result, it's rather tricky for -the user to control list spacing; of course, the real answer is to use +<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 +<code>\</code><code>@listi</code> is usually reset when the font size is changed. As a +result, it’s rather tricky for +the user to control list spacing. Of course, the real answer is to use a document class designed with more modest list spacing, but we all -know such things are hard to come by. The <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 @@ -19,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*}% @@ -32,7 +33,7 @@ these commands define pretty straightforwardly - for example: \setlength{\parskip}{0pt}}% {\end{itemize}} </pre> -</blockquote> +</blockquote><p> The <i>paralist</i> package provides several approaches to list compaction: <ul> @@ -42,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 @@ -52,18 +53,24 @@ does. <p><i>Paralist</i> also provides <code>itemize</code> equivalents (<code>asparaitem</code>, etc.), and <code>description</code> equivalents (<code>asparadesc</code>, etc.). +<p>The <i>multenum</i> package offers a more regular form of +<i>paralist</i>’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 +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; so +a “<em>key</em>=<<i>value</i>>” format; so for example, one might write <blockquote> <pre> @@ -73,32 +80,17 @@ for example, one might write \item ... ... \end{enumerate} </pre> -</blockquote> +</blockquote><p> to suppress all spacing above and below your list. <i>Enumitem</i> -also permits manipulation of the label format in a more "basic" +also permits manipulation of the label format in a more “basic” manner than the <a href="FAQ-enumerate.html"><i>enumerate</i> package</a> does. - - - - - - - - - - - - - - - - <dl> <dt><tt><i>enumerate.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) <dt><tt><i>enumitem.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.zip">macros/latex/contrib/enumitem</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem/">browse</a>) <dt><tt><i>expdlist.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/expdlist.zip">macros/latex/contrib/expdlist</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/expdlist.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expdlist/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse</a>) +<dt><tt><i>multenum.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multenum.zip">macros/latex/contrib/multenum</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multenum.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multenum/">browse</a>) <dt><tt><i>paralist.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/paralist.zip">macros/latex/contrib/paralist</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/paralist.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/paralist/">browse</a>) <dt><tt><i>savetrees.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/savetrees.zip">macros/latex/contrib/savetrees</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/savetrees.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/savetrees/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-concrete.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-concrete.html index 079406de340..1b9f6ebe86b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-concrete.html +++ b/Master/texmf-doc/doc/english/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 @@ -41,14 +41,12 @@ that the <i>concmath</i> documentation calls it add <blockquote> <code>\</code><code>renewcommand{<code>\</code><code>bfdefault</code>}{sbc}</code> -</blockquote> +</blockquote><p> to the preamble of your document. -<p>Type 1 versions of the fonts are available. For the OT1 encoding, -they are available from -<a href="FAQ-psfchoice.html">MicroPress</a>. The - +<p>Type 1 versions of the fonts are available. For OT1 encoding, +they are available from <a href="FAQ-psfchoice.html">MicroPress</a>. The <a href="FAQ-textrace.html">CM-Super fonts</a> contain Type 1 versions -of the Concrete fonts in the T1 encoding. +of the Concrete fonts in T1 encoding. <dl> <dt><tt><i>beton.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/beton.zip">macros/latex/contrib/beton</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/beton.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/beton/">browse</a>) <dt><tt><i>ccfonts.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ccfonts.zip">macros/latex/contrib/ccfonts</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ccfonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ccfonts/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-conditional.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-conditional.html index 7708157dc86..48dd3c2ca81 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-conditional.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-conditional.html @@ -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 a general +<code>\</code><code>iffalse</code><code> ... </code><code>\</code><code>fi</code> aren’t really satisfactory (as a general solution) for comments, since the matter being skipped is nevertheless scanned by TeX, not always as you would expect. The scanning -imposes restrictions on what you're allowed to skip; this may not be a -problem in <em>today's</em> job, but could return to bite you tomorrow. +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> @@ -21,21 +21,21 @@ consider what happens if we use \verb|\iftrue| -- a surprise \fi </pre> -</blockquote> +</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 -following <code>\</code><code>fi</code>. Also, <code>\</code><code>gobble</code> is pretty inefficient for any -but trivial arguments, since all the matter to be skipped is copied to -the argument stack before being ignored. +<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 @@ -57,13 +57,13 @@ document looking like: \includepdf[pages=30-40]{yoursource.pdf} \end{document} </pre> -</blockquote> +</blockquote><p> (To include all of the document, you write <blockquote> <pre> \includepdf[pages=-]{yoursource.pdf} </pre> -</blockquote> +</blockquote><p> omitting the start and end pages in the optional argument.) <p>If you want flexible facilities for including or excluding small portions of a file, consider the <i>comment</i>, <i>version</i> or @@ -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 @@ -123,11 +123,11 @@ environments named in its argument. So, for example: ... \end{xcomment} </pre> -</blockquote> +</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> @@ -138,16 +138,16 @@ shows the following usage: extract-cmd={chapter,section} ]{extract} </pre> -</blockquote> +</blockquote><p> which will cause the package to produce a file <i>foobar.tex</i> containing all the <code>figure</code> and <code>table</code> environments, and the <code>\</code><code>chapter</code> and <code>\</code><code>section</code> commands, from the document being processed. The new file <i>foobar.tex</i> is -generated in the course of an otherwise ordinary run on the '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><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/askinclude.sty">macros/latex/contrib/misc/askinclude.sty</a> <dt><tt><i>comment.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/comment.zip">macros/latex/contrib/comment</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/comment.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/comment/">browse</a>) @@ -155,7 +155,7 @@ ready-to-run LaTeX documents with stuff you've extracted. <dt><tt><i>extract.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/extract.zip">macros/latex/contrib/extract</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/extract.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/extract/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>optional.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/optional.sty">macros/latex/contrib/misc/optional.sty</a> -<dt><tt><i>pagesel.sty</i></tt><dd>Distributed with Heiko Oberdiek's packages +<dt><tt><i>pagesel.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>) <dt><tt><i>pdfpages.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdfpages.zip">macros/latex/contrib/pdfpages</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdfpages.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdfpages/">browse</a>) <dt><tt><i>selectp.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/selectp.sty">macros/latex/contrib/misc/selectp.sty</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-context.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-context.html index cc047fd0515..8a87be7f21e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-context.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-context.html @@ -8,14 +8,14 @@ serve the needs of his (Dutch) firm Pragma. It was designed with the same general-purpose aims as LaTeX, but (being younger) reflects much more recent thinking about the structure of markup, etc. In particular, ConTeXt can customise its markup to an -author's language (customising modules for Dutch, English and German +author’s language (customising modules for Dutch, English and German are provided, at present). <p>ConTeXt is well integrated, in all of its structure, with the needs of hypertext markup, and in particular with the -facilities offered by <a href="FAQ-pdftex.html">PDFTeX</a>. +facilities offered by <a href="FAQ-whatpdftex.html">PDFTeX</a>. The default installation employs a version of PDFTeX built with the -<a href="FAQ-NTS.html">e-TeX extensions</a>, which allows further flexibility. -<p>ConTeXt doesn't yet have quite such a large developer community as +<a href="FAQ-etex.html">e-TeX extensions</a>, which allows further flexibility. +<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. Some support is available via a <a href="http://contextgarden.net/">WIKI site</a>. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-crop.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-crop.html index e56882a8a98..7f02601736f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-crop.html +++ b/Master/texmf-doc/doc/english/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="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/crop.zip">macros/latex/contrib/crop</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/crop.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/crop/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-crossref.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-crossref.html index 710563c747a..914cc1e9db3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-crossref.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-crossref.html @@ -23,7 +23,7 @@ environment of its own. For example, people commonly seek help after: \end{center} \label{fig} </pre> -</blockquote> +</blockquote><p> has failed to label correctly. If you really need this centring (and those in the know commonly reject it), code it as: <blockquote> @@ -33,6 +33,6 @@ those in the know commonly reject it), code it as: \label{fig} \end{center} </pre> -</blockquote> +</blockquote><p> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=crossref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=crossref</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-csname.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-csname.html index 0c314c6cab9..abf7849cbbb 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-csname.html +++ b/Master/texmf-doc/doc/english/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. @@ -12,8 +12,8 @@ name of the environment command. <pre> \def\relay#1#2{\def\#1{#2}} </pre> -</blockquote> -doesn't work (the TeX engine interprets it +</blockquote><p> +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 @@ -24,12 +24,12 @@ above should read: \expandafter\def\csname #1\endcsname{#2}% } </pre> -</blockquote> +</blockquote><p> With this definition, <code>\</code><code>relay{blah}{bleah}</code> is equivalent to <code>\</code><code>def</code><code>\</code><code>blah{bleah}</code>. <p>Note that the definition of <code>\</code><code>relay</code> omits the braces round the -'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> @@ -44,14 +44,14 @@ circumstance they make the macro code slightly more tedious. }% } </pre> -</blockquote> +</blockquote><p> With commands <blockquote> <pre> \def\start#1{\csname start#1\endcsname} \def\finish#1{\csname finish#1\endcsname} </pre> -</blockquote> -these 'races' could behave a bit like LaTeX environments. +</blockquote><p> +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-doc/doc/english/FAQ-en/html/FAQ-custbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-custbib.html index 6168e4321ef..893603414ef 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-custbib.html +++ b/Master/texmf-doc/doc/english/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="ftp://cam.ctan.org/tex-archive/biblio/bibtex/distribs/doc.zip">biblio/bibtex/distribs/doc</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/distribs/doc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/distribs/doc/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cv.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cv.html index d5d0848db69..043e5ae246e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cv.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cv.html @@ -2,28 +2,31 @@ <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 +<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 +casual style. It is fairly customizable, allowing you to define your +own style by changing the colours, the fonts, etc. <p>The European Commission has recommended a format for <em>curricula vitarum</em> within Europe, and Nicola Vitacolonna has developed a class <i>europecv</i> to produce it. While (by his own -admission) the class doesn't solve all problems, it seems well-thought -out and supports many EU languages (it omits Dutch and Greek, and all -the languages of the 2004 accessions; instructions for creating new -language options are, however, there for the energetic). +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. @@ -31,6 +34,7 @@ little but advice <em>against</em> trying to use it. <dt><tt><i>currvita.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/currvita.zip">macros/latex/contrib/currvita</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/currvita.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/currvita/">browse</a>) <dt><tt><i>curve.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/curve.zip">macros/latex/contrib/curve</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/curve.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/curve/">browse</a>) <dt><tt><i>europecv.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/europecv.zip">macros/latex/contrib/europecv</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/europecv.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/europecv/">browse</a>) +<dt><tt><i>moderncv.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/moderncv.zip">macros/latex/contrib/moderncv</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/moderncv.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/moderncv/">browse</a>) <dt><tt><i>resume.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/obsolete/macros/latex209/contrib/resume/resume.sty">obsolete/macros/latex209/contrib/resume/resume.sty</a> <dt><tt><i>vita.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/vita.zip">macros/latex/contrib/vita</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/vita.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/vita/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cvtlatex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cvtlatex.html index 030fad6230e..30e02ea73ab 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cvtlatex.html +++ b/Master/texmf-doc/doc/english/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: @@ -39,12 +39,12 @@ long-winded. Since <code>#1</code> is the requisite argument, we have: \relax ... </pre> -</blockquote> +</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> @@ -53,7 +53,7 @@ is to be optional. So: \newcommand\foo[1]{...#1...} \newcommand\foo[2][boo]{...#1...#2...} </pre> -</blockquote> +</blockquote><p> In the last case, <code>\</code><code>foo</code> may be called as <code>\</code><code>foo{goodbye}</code>, which is equivalent to <code>\</code><code>foo[boo]{goodbye}</code> (employing the default value given for the first argument), or as @@ -72,6 +72,6 @@ coding of the last <code>\</code><code>foo</code> above: } \def\@x@foo[#1]#2{...#1...#2...} </pre> -</blockquote> +</blockquote><p> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cvtlatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cvtlatex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dec_comma.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dec_comma.html index 8e422627dba..da92267ebfe 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dec_comma.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dec_comma.html @@ -6,7 +6,7 @@ space is inappropriate if the comma is being used as a decimal separator. An easy solution to this problem, in maths mode, is to type <code>3</code><code>{,}</code><code>14</code> instead of typing -<code>3,14</code>. However, if your language's +<code>3,14</code>. However, if your language’s typographic rules require the comma as a decimal separator, such usage can rapidly become extremely tiresome. There are two packages that can help relieve the tedium: <i>icomma</i> and <i>ziffer</i>. @@ -16,7 +16,7 @@ instance), 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 amount of currency. +for the empty ‘cents’ part of an amount of currency. <dl> <dt><tt><i>icomma.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/was.zip">macros/latex/contrib/was</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/was.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/was/">browse</a>) <dt><tt><i>ziffer.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/ziffer.sty">macros/latex/contrib/misc/ziffer.sty</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-destable.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-destable.html index c4ab5c95a21..99b0c00764b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-destable.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-destable.html @@ -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 @@ -31,7 +31,7 @@ position wrong (by <code>10pt</code>) if you simply write: \end{tabular} \end{table} </pre> -</blockquote> +</blockquote><p> The <i>topcapt</i> package solves this problem: <blockquote> <pre> @@ -44,7 +44,7 @@ The <i>topcapt</i> package solves this problem: \end{tabular} \end{table} </pre> -</blockquote> +</blockquote><p> The <i>KOMA-script</i> classes provide a similar command <code>\</code><code>captionabove</code>; they also have a class option <code>tablecaptionabove</code> which arranges that <code>\</code><code>caption</code> @@ -55,7 +55,7 @@ with an option that has the same effect: <pre> \usepackage[tableposition=top]{caption} </pre> -</blockquote> +</blockquote><p> <p>Doing the job yourself is pretty easy: <i>topcapt</i> switches the values of the LaTeX2e parameters <code>\</code><code>abovecaptionskip</code> (default value <code>10pt</code>) and <code>\</code><code>belowcaptionskip</code> (default value <code>0pt</code>), so: @@ -70,7 +70,7 @@ value <code>10pt</code>) and <code>\</code><code>belowcaptionskip</code> (defaul \end{tabular} \end{table} </pre> -</blockquote> +</blockquote><p> does the job. (The package itself is very slightly more elaborate...) <dl> <dt><tt><i>booktabs.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/booktabs.zip">macros/latex/contrib/booktabs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/booktabs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/booktabs/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-distill-prob.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-distill-prob.html index 0a834869e58..1fc2a3375fe 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-distill-prob.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-divzero.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-divzero.html index 6a08373e4c7..24b188bd6e0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-divzero.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-divzero.html @@ -7,35 +7,35 @@ <pre> ! Package graphics Error: Division by 0. </pre> -</blockquote> +</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} </pre> -</blockquote> +</blockquote><p> In the case that <i>myfig.eps</i> has no depth to start with, the scaling calculations will produce the division-by-zero error. <p>Fortunately, the <i>graphicx</i> package has a keyword <code>totalheight</code>, which allows you to specify the size of the -image relative to the sum of the object's <code>height</code> and +image relative to the sum of the object’s <code>height</code> and <code>depth</code>, so <blockquote> <pre> \includegraphics[angle=180,totalheight=5cm]{myfig.eps} </pre> -</blockquote> +</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> @@ -46,7 +46,7 @@ will resolve the error, and will behave as you might hope. }% } </pre> -</blockquote> +</blockquote><p> <dl> <dt><tt><i>graphics.sty,graphicx.sty</i></tt><dd>Both parts of the <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) bundle </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-doc-dirs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-doc-dirs.html new file mode 100644 index 00000000000..e79b23ff057 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-doc-dirs.html @@ -0,0 +1,13 @@ +<head> +<title>UK TeX FAQ -- question label doc-dirs</title> +</head><body> +<h3>Directories of (La)TeX information</h3> +<p>TUG India is developing a series of online LaTeX tutorials +which can be strongly recommended: select single chapters at a time +from <a href="http://www.tug.org.in/tutorials.html">http://www.tug.org.in/tutorials.html</a> — the +set comprises two parts, “Text” and “Graphics”, so far. +<p>Herbert Voss’s excellent +<a href="http://texnik.de/">LaTeX tips and tricks</a> is an excellent +source of small articles on the use of LaTeX. +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-dirs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-dirs</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-doc-wiki.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-doc-wiki.html new file mode 100644 index 00000000000..16432550efd --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-doc-wiki.html @@ -0,0 +1,21 @@ +<head> +<title>UK TeX FAQ -- question label doc-wiki</title> +</head><body> +<h3>WIKI pages for TeX and friends</h3> +<p>The <em>WIKI</em> concept can be a boon to everyone, if used sensibly. +The “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>, both a +<a href="http://en.wikibooks.org/wiki/TeX">(Plain) TeX WIKI</a> and a +<a href="http://en.wikibooks.org/wiki/LaTeX">LaTeX WIKI</a> have been +established. Both seem rather sparse, as yet, and the LaTeX WIKI +contains some suggestions that go counter to established advice (e.g., +the LaTeX WIKI has details on the +<a href="FAQ-eqnarray.html">use of the <code>eqnarray</code> environment</a>); +however one may hope that both will become useful resources in the +longer term. +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-wiki">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-wiki</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-docotherdir.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-docotherdir.html index c929acdda0f..ef9c4ba7155 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-docotherdir.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-docotherdir.html @@ -5,31 +5,31 @@ <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> Graph: \includegraphics{picture} \input{explanation} </pre> -</blockquote> +</blockquote><p> then <code>\</code><code>import{/home/friend/}{results}</code> will include both graph and explanation as one might hope. A <code>\</code><code>subimport</code> command does the same sort of thing for a subdirectory (a relative path rather @@ -43,15 +43,15 @@ each of which takes directory and file arguments, e.g.: <pre> \cfpart[pt 1]{Part One}{part1}{part} </pre> -</blockquote> -which command will issue a 'normal' command +</blockquote><p> +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.) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dolldoll.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dolldoll.html index 94418b05ef3..a8a2eef7595 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dolldoll.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dolldoll.html @@ -6,20 +6,20 @@ analagous to those that derive from the TeX primitive maths sequences bracketing maths commands with single dollar signs (or pairs of dollar signs). -<p>As it turns out, LaTeX's inline maths grouping, +<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> has code for rationalising vertical spacing in some extreme cases; that code is not available in <code>$$ ... $$</code>, so if you diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dpfloat.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dpfloat.html index 3ee1b5e839d..8693abdb01c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dpfloat.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dpfloat.html @@ -19,7 +19,7 @@ this: the construction to use is: \end{fullpage} \end{figure} </pre> -</blockquote> +</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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawFeyn.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawFeyn.html index 4a307247006..23745790a6d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawFeyn.html +++ b/Master/texmf-doc/doc/english/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,18 +14,18 @@ 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 offers fairly simple diagrams which look good in equations, rather than complicated ones more suitable for display in figures. <dl> -<dt><tt><i>axodraw</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/axodraw/export">graphics/axodraw/export</a> +<dt><tt><i>axodraw</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/axodraw.zip">graphics/axodraw</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/axodraw.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/axodraw/">browse</a>) <dt><tt><i>feyn font bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/feyn.zip">fonts/feyn</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/feyn.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/feyn/">browse</a>) <dt><tt><i>feynman bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/feynman.zip">macros/latex209/contrib/feynman</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/feynman.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex209/contrib/feynman/">browse</a>) <dt><tt><i>feynmf/feynmp bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/feynmf.zip">macros/latex/contrib/feynmf</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/feynmf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/feynmf/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawing.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawing.html index 6694dd9eec2..216a28841e3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawing.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawing.html @@ -10,56 +10,54 @@ sophisticated (but slow) drawing with PiCTeX. Depending on your type of drawing, and setup, here are a few systems you may consider: <ul> <li> <i>pict2e</i>; this was advertised in - <a href="FAQ-books.html">the LaTeX manual</a>, but didn'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 niggles that surround the use of the <code>picture</code> environment. It therefore suffers <em>only</em> from the rather eccentric drawing language of the environment, and is a far more useful tool than the original environment has ever been. (Note that - <i>pict2e</i> supersedes David Carlisle'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 <a href="FAQ-specials.html"><code>\</code><code>special</code> commands</a>. Since PostScript is itself a pretty powerful programming language, this means there are many astounding things that can in principle be achieved. - <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>pdftricks</i>, which (like - <i>epstopdf</i> - see + <i>epstopdf</i> — see <a href="FAQ-pdftexgraphics.html">PDFLaTeX graphics</a>) generates PDF files on the fly from <i>pstricks</i> commands. The documentation is good (you may browse it via the - <a href="http://www.tug.org/applications/PSTricks/"><i>pstricks</a> page</i> - on the TUG web site), and another extremely valuable - <a href="http://www.pstricks.de">web site</a> lists supporting - packages (for various specialised drawing operations) and many - enticing examples. There is also a mailing list + <a href="http://pstricks.tug.org/"><i>pstricks</a> page</i> + on the TUG web site). There is also a mailing list (<a href="mailto:pstricks@tug.org"><i>pstricks@tug.org</i></a>) which you may <a href="http://tug.org/mailman/listinfo/pstricks">join</a>, or you may just browse the <a href="http://tug.org/pipermail/pstricks/">list archives</a>. <li> <i>pgf</i>: while <i>pstricks</i> is very powerful and convenient, using it with PDFLaTeX is an awful fidget: if you - simply want the graphical capabilities, <i>pgf</i> may be a good + simply want the graphical capabilities, <i>pgf</i>, together with + 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 +<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). @@ -68,10 +66,11 @@ of drawing, and setup, here are a few systems you may consider: <dt><tt><i>dratex.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/dratex.zip">graphics/dratex</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/dratex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/dratex/">browse</a>) <dt><tt><i>mfpic</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/mfpic.zip">graphics/mfpic</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/mfpic.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/mfpic/">browse</a>) <dt><tt><i>pdftricks.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdftricks.zip">macros/latex/contrib/pdftricks</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdftricks.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdftricks/">browse</a>) -<dt><tt><i>pspicture.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>) +<dt><tt><i>pspicture.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pspicture.zip">macros/latex/contrib/pspicture</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pspicture.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pspicture/">browse</a>) <dt><tt><i>pgf.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/pgf.zip">graphics/pgf</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pgf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pgf/">browse</a>) <dt><tt><i>pict2e.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pict2e.zip">macros/latex/contrib/pict2e</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pict2e.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pict2e/">browse</a>) <dt><tt><i>pstricks</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.zip">graphics/pstricks</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pstricks/">browse</a>) +<dt><tt><i>tikz.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/graphics/pgf.zip">graphics/pgf</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pgf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pgf/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=drawing">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=drawing</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-driver.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-driver.html index e67b74867d2..ebc89d48b51 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-driver.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-driver.html @@ -12,12 +12,12 @@ the output from a PostScript driver. <p>As well as the DVI file, the driver 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"><code>pk</code> files</a>, +see <a href="FAQ-pk.html">PK files</a>, -<a href="FAQ-tfm.html"><code>tfm</code> files</a>, +<a href="FAQ-tfm.html">TFM files</a>, <a href="FAQ-virtualfonts.html">virtual fonts</a> and <a href="FAQ-usepsfont.html">Using PostScript fonts with TeX</a>. <p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=driver">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=driver</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dropping.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dropping.html index 019b45051fd..fcf35f59c97 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dropping.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dropping.html @@ -5,8 +5,8 @@ <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) -«lettrines», and TeX's primitive +<p>This style is known as “dropped capitals”, or (in French) +«lettrines», 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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html index 0cd08e801f5..bb6f760af39 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html @@ -6,8 +6,8 @@ <a href="FAQ-lit.html">literate programming</a> style, 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. The documented sources conventionally have the suffix <code>.dtx</code>, and should normally be stripped of documentation before use with LaTeX. Alternatively you can run LaTeX on a @@ -24,7 +24,7 @@ write <code>.dtx</code> files; the format is explained in available from CTAN (which comes with skeleton <code>.dtx</code> and <code>.ins</code> files). <p>Composition of <code>.dtx</code> files is supported in <i>emacs</i> by -Matt Swift's <i>swiftex</i> system: it provides a +Matt Swift’s <i>swiftex</i> system: it provides a <code>doc-tex</code> mode which treats <code>.dtx</code> files rather better than <a href="FAQ-editors.html">AUC-TeX</a> manages. <p>Another useful way of generating <code>.dtx</code> files is to write the diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi-bmp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi-bmp.html index e27e86bd841..215ab5e047b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi-bmp.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi-bmp.html @@ -5,20 +5,20 @@ <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 widely -used), and 'exotic' typescripts (ones that you cannot guarantee your +used), and ‘exotic’ typescripts (ones that you cannot guarantee your readers will have available). Other common examples are generation of sample bitmaps, and generation for insertion into some other -application's display - to insert equations into Microsoft +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>. @@ -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 longest-established, <i>dvi2bitmap</i>, will generate XBM and XPM formats, the long-deprecated GIF format (which is now obsolescent, but is diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html index 701145fc5c9..90edef45b5b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html @@ -3,15 +3,15 @@ </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, using TeX in its broadest sense to -include LaTeX, etc. 'DVI' is supposed to be an acronym for +TeX’s main output file, using TeX in its broadest sense to +include LaTeX, etc. ‘DVI’ is supposed to be an acronym for DeVice-Independent, meaning that the file can be printed on almost any kind of typographic output device. The DVI file is designed to be read by a driver (<a href="FAQ-driver.html">DVI drivers</a>) to produce further output designed specifically for a particular printer (e.g., a LaserJet) or to be used as input to a previewer for display on a -computer screen. DVI files use TeX's internal coding; a TeX +computer screen. DVI files use TeX’s internal coding; a TeX input file should produce the same DVI file regardless of which implementation of TeX is used to produce it. <p>A DVI file contains all the information that is needed for printing diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipdfmgraphics.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipdfmgraphics.html index 719736004a7..0b2888602f3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipdfmgraphics.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipdfmgraphics.html @@ -9,12 +9,12 @@ <p><i>Dvipdfm</i> is a particularly flexible application. It will permit the inclusion of bitmap and PDF graphics, as does <a href="FAQ-pdftexgraphics.html">PDFTeX</a>, but is also capable of employing -<i>ghostscript</i> "on the fly" so as to be able to permit the +<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, <i>dvipdfm</i> combines 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: @@ -24,8 +24,8 @@ document: ... \includegraphics[bb=0 0 540 405]{photo.jpg} </pre> -</blockquote> -It's usually not obvious what values to give the "<code>bb</code>" key, +</blockquote><p> +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>: @@ -36,7 +36,7 @@ containing the information; the above numbers came from an %%BoundingBox: 0 0 540 405 %%CreationDate: Mon Mar 8 15:17:47 2004 </pre> -</blockquote> +</blockquote><p> However, if such a file is available, you may abbreviate the inclusion code, above, to read: <blockquote> @@ -45,18 +45,18 @@ code, above, to read: ... \includegraphics{photo} </pre> -</blockquote> +</blockquote><p> which makes the operation feel as simple as does including <code>.eps</code> images in a LaTeX file for processing with <i>dvips</i>; the <i>graphicx</i> package knows to look for a <code>.bb</code> file if no bounding box is provided in the <code>\</code><code>includegraphics</code> command. -<p>The one place where usage isn'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="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.zip">dviware/dvipdfm</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfm/">browse</a>) <dt><tt><i>ebb</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.zip">dviware/dvipdfm</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfm/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips-pdf.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips-pdf.html index 99722f1439c..45e166d4278 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips-pdf.html +++ b/Master/texmf-doc/doc/english/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 @@ -22,24 +22,28 @@ Issues covered are: <li> <a href="FAQ-fuzzy-gs.html"><i>ghostscript</i> too old</a>, which can also result in fuzzy text. -<li> - <a href="FAQ-fuzzy-T1.html">Switching to font encoding T1</a>, which +<li> <a href="FAQ-fuzzy-T1.html">Switching to font encoding T1</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 - <i>dvips</i> configuration file <code>-Ppdf</code>, 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) does not exhibit the -"fuzziness" that so many of the answers below address. This is of -course good news: however, it will inevitably be a long time before -every user in the world has this (or later) versions, so the remedies -below are going to remain for some time to come. +<i>Reader</i> 6 (released in mid-2003, and later versions) does +not exhibit the “fuzziness” that so many of the answers below +address. This is of course good news: however, it will inevitably be +a long time before every user in the world has this (or later) +versions, so the remedies below are going to remain for some time to +come. +<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>. +<dl> +<dt><tt><i>testflow</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/IEEEtran/testflow/">macros/latex/contrib/IEEEtran/testflow/</a> +</dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips-pdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips-pdf</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips.html index 2516238ca41..d0a45303513 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips.html @@ -3,23 +3,18 @@ </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> -library, and sources are available from the TeX live repository. +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. <p>An VMS versions is available as part of the CTAN distribution of TeX for VMS. <p>A precompiled version to work with emTeX is available on CTAN. -<p> - - - - -<p>Macintosh users can use either the excellent drivers built into OzTeX -or Textures, or a port of <i>dvips</i> in the CMacTeX -package. <dl> -<dt><tt><i>MSDOS and {OS/}2</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/dviware/dvips.zip">systems/msdos/dviware/dvips</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/dviware/dvips.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/dviware/dvips/">browse</a>) +<dt><tt><i>MSDOS and OS/2</i></tt><dd> + <a href="ftp://cam.ctan.org/tex-archive/systems/msdos/dviware/dvips.zip">systems/msdos/dviware/dvips</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/dviware/dvips.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/dviware/dvips/">browse</a>) <dt><tt><i>VMS distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/OpenVMS/TEX97_CTAN.ZIP">systems/OpenVMS/TEX97_CTAN.ZIP</a> </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipsgraphics.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipsgraphics.html index a567ff525e1..d0295f7464f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipsgraphics.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipsgraphics.html @@ -12,20 +12,27 @@ 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 -creating EPS files. (Though <i>Unix</i> users should -beware of <i>xv</i>'s claims: it has a tendency to downsample your -bitmap to your screen resolution.) +<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 +your screen resolution.) <p>Special purpose applications <i>jpeg2ps</i> (which converts JPEG files using PostScript level 2 functionality) and <i>bmeps</i> (which converts both JPEG and PNG -files) are also considered "good bets". <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. +files), and <i>a2ping</i>/<i>sam2p</i> (which convert a +bewildering array of bitmap formats to EPS or PDF files; +<i>sam2p</i> is one of the engines that <i>a2ping</i> uses) +are also considered “good bets”. +<p><i>Bmeps</i> comes with patches to produce your own version of +<i>dvips</i> that can cope with JPEG and PNG direct, +using <i>bmeps</i>’s conversion library. <i>Dvips</i>, as +distributed by MiKTeX, comes with those patches built-in. <dl> +<dt><tt><i>a2ping</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/a2ping.zip">graphics/a2ping</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/a2ping.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/a2ping/">browse</a>) <dt><tt><i>bmeps</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/bmeps.zip">support/bmeps</a> (<a href="ftp://cam.ctan.org/tex-archive/support/bmeps.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/bmeps/">browse</a>) <dt><tt><i>jpeg2ps</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/support/jpeg2ps.zip">nonfree/support/jpeg2ps</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/support/jpeg2ps.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/jpeg2ps/">browse</a>) +<dt><tt><i>sam2p</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/sam2p.zip">graphics/sam2p</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/sam2p.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/sam2p/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvipsgraphics">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvipsgraphics</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-edef.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-edef.html index 133d217bc84..89679591c1c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-edef.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-edef.html @@ -2,19 +2,19 @@ <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 are robust only in a context where the <code>\</code><code>protect</code> mechanism is properly handled. The body of an -<code>\</code><code>edef</code> definition doesn't handle <code>\</code><code>protect</code> properly, since +<code>\</code><code>edef</code> definition doesn’t handle <code>\</code><code>protect</code> properly, since <code>\</code><code>edef</code> is a TeX primitive rather than a LaTeX command. <p>This problem is resolved by a LaTeX internal command <code>\</code><code>protected@edef</code>, which does the job of <code>\</code><code>edef</code> while keeping the -<code>\</code><code>protect</code> mechanism working. There's a corresponding +<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-doc/doc/english/FAQ-en/html/FAQ-editors.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-editors.html index ae5bc6049ed..167a7302290 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-editors.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-editors.html @@ -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 - similar way to the the widely-praised <i>Winedt</i> (see below); - details (and downloads) are available from the project's + 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 <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. @@ -71,9 +71,9 @@ Atari, Amiga and NeXT users also have nice environments. LaTeX users looking for <i>make</i>-like facilities should try <i>latexmk</i>. <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="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/support/alpha.zip">nonfree/systems/mac/support/alpha</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/support/alpha.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/systems/mac/support/alpha/">browse</a>) <dt><tt><i>auctex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/auctex.zip">support/auctex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/auctex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/auctex/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-empty.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-empty.html index 170867a7716..fb132a0f368 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-empty.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-empty.html @@ -17,15 +17,15 @@ and <code>\</code><code>cmd{blah}</code>. This is pretty simple: \fi } </pre> -</blockquote> +</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 distinguish (in opposite directions) between a second and 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 +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 lamented Mike Downes. <dl> <dt><tt><i>Around the bend series</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/aro-bend.zip">info/aro-bend</a> (<a href="ftp://cam.ctan.org/tex-archive/info/aro-bend.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/aro-bend/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html index 47cad25980b..97e41672260 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html @@ -4,49 +4,49 @@ <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 <code>emacs</code> and <i>winedt</i> offer this facility). However, groups are not <em>only</em> created by matching <code>{</code> with <code>}</code>: 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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-enlarge.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-enlarge.html index e2a3202dc00..5773403a956 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-enlarge.html +++ b/Master/texmf-doc/doc/english/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> @@ -10,20 +10,20 @@ error message itself, as in: ! TeX capacity exceeded, sorry ... [main memory size=263001]. </pre> -</blockquote> +</blockquote><p> Most of the time this error can be fixed <em>without</em> enlarging TeX. The most common causes are unmatched braces, extra-long lines, and poorly-written macros. Extra-long lines are often introduced when files are transferred incorrectly between operating systems, and line-endings are not preserved properly (the tell-tale sign of an extra-long line error is the complaint -that the '<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-doc/doc/english/FAQ-en/html/FAQ-enumerate.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-enumerate.html index c29d232961e..943ad360e99 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-enumerate.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-enumerate.html @@ -6,9 +6,9 @@ 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 -numberals), and things to act as decoration of the enumeration. So, +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> <pre> @@ -18,7 +18,7 @@ for example \item ... ... \end{enumerate} </pre> -</blockquote> +</blockquote><p> starts a list whose labels run (a), (b), (c), ...; while <blockquote> <pre> @@ -28,7 +28,7 @@ starts a list whose labels run (a), (b), (c), ...; while \item ... ... \end{enumerate} </pre> -</blockquote> +</blockquote><p> starts a list whose labels run I/, II/, III/, ... <p>The <i>paralist</i> package, whose primary purpose is <a href="FAQ-complist.html">compaction of lists</a>, provides the same facilities @@ -44,8 +44,8 @@ The silly roman example above could be achieved by: \item ... ... \end{enumerate} </pre> -</blockquote> -Note that the '<code>*</code>' in the key value stands for the list +</blockquote><p> +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> @@ -57,7 +57,7 @@ references to list item labels: \item ... ... \end{enumerate} </pre> -</blockquote> +</blockquote><p> to make references to the list items format appear as (i), (ii), (iii), etc. <p>The <i>memoir</i> class includes functions that match those in the diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-epigraph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-epigraph.html index 819e5efb11d..6c9d5a3103e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-epigraph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-epigraph.html @@ -6,9 +6,11 @@ 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. However, the <i>epigraph</i> package will do the job for -you, even in situations where it's particularly nasty to get right. -<p>The package defines an <code>\</code><code>epigraph</code> command, for creating a single +yourself. Fortunately, there are two packages that do the job, to +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 epigraph (as at the top of a chapter): <blockquote> <pre> @@ -16,7 +18,7 @@ epigraph (as at the top of a chapter): \epigraph{Oh! My ears and whiskers!}% {Lewis Carroll} </pre> -</blockquote> +</blockquote><p> and an epigraphs environment, for entering more than one epigraph consecutively, in a sort of list introduced by <code>\</code><code>qitem</code> commands: <blockquote> @@ -28,7 +30,7 @@ consecutively, in a sort of list introduced by <code>\</code><code>qitem</code> {A.A. Milne} \end{epigraphs} </pre> -</blockquote> +</blockquote><p> The <code>\</code><code>epigraphhead</code> command enables you to place your epigraph <em>above</em> a chapter header: <blockquote> @@ -41,16 +43,21 @@ The <code>\</code><code>epigraphhead</code> command enables you to place your ep {Lewis Carroll}% } </pre> -</blockquote> +</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...) +<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. <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 @@ -59,6 +66,7 @@ facilities. <dt><tt><i>epigraph.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/epigraph.zip">macros/latex/contrib/epigraph</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/epigraph.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/epigraph/">browse</a>) <dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) +<dt><tt><i>quotchap.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/quotchap.zip">macros/latex/contrib/quotchap</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/quotchap.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/quotchap/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=epigraph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=epigraph</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eplain.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eplain.html index d3ae64f8f09..e94d8d8dace 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eplain.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eplain.html @@ -2,31 +2,46 @@ <title>UK TeX FAQ -- question label eplain</title> </head><body> <h3>What is Eplain?</h3> -<p>The -<a href="http://www.ccs.neu.edu/~dorai/eplain/index.html">Eplain</a> +<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 LaTeX or -<a href="FAQ-texinfo.html">Texinfo</a>. Instead, it +Eplain is not intended to provide “generic typesetting +capabilities”, as do LaTeX or <a href="FAQ-texinfo.html">Texinfo</a>. Instead, it defines macro tools that should be useful whatever commands you choose to use when you prepare your manuscript. <p>For example, Eplain does not have a command <code>\</code><code>section</code>, -which would format section headings in an "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 -numbers in the manuscript. Karl Berry, the author of Eplain, says -he is not aware of any generally available macro packages that do -not force their typographic style on an author, and yet provide -such capabilities. -<p>Eplain documentation is -<a href="http://tug.org/docs/html/eplain">available online</a>, and there's -also a mailing list - sign up, or browse the list archives, via +cross-referencing by labels, so that you don’t have to put actual page +numbers in the manuscript. The authors of Eplain are not aware of +any generally available macro packages that do not force their +typographic style on an author, and yet provide such capabilities. +<p>Another useful feature of Eplain is the ability to create PDF files +with hyperlinks. The cross-referencing macros can implicitly generate +hyperlinks for the cross-references, but you can also create explicit +hyperlinks, both internal (pointing to a destination within the +current document) and external (pointing to another local document or +a URL). +<p>Several LaTeX packages provide capabilities which Plain TeX +users are lacking, most notably text colouring and rotation provided by +the <i>graphics</i> bundle (packages <i>color</i> and +<i>graphics</i>). Although the <i>graphics</i> bundle provides +a Plain TeX “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 +to the packages just as they are in LaTeX. The following packages are +known to work with Eplain: <i>graphics</i>, <i>graphicx</i>, +<i>color</i>, <i>autopict</i> (LaTeX picture environment), +<i>psfrag</i>, and <i>url</i>. +<p><a href="http://tug.org/docs/html/eplain">Eplain documentation</a> is +available online, and there’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="ftp://cam.ctan.org/tex-archive/macros/eplain.zip">macros/eplain</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/eplain.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/eplain/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eps.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eps.html index 11fda9ca8b7..7e44cafe153 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eps.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eps.html @@ -1,37 +1,37 @@ <head> <title>UK TeX FAQ -- question label eps</title> </head><body> -<h3>What is "Encapsulated PostScript"</h3> +<h3>What is “Encapsulated PostScript” (“EPS”)</h3> <p>PostScript has over the years become a <em>lingua franca</em> of powerful printers; since PostScript is also a powerful graphical programming language, it is commonly used as an output medium for drawing (and other) packages. <p>However, since PostScript <em>is</em> such a powerful language, some rules need to be imposed, so that the output drawing may be included -in a document as a figure without "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" 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-doc/doc/english/FAQ-en/html/FAQ-epsf.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-epsf.html index cefa47c7fa1..aa69bc030ee 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-epsf.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-eqnarray.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eqnarray.html index f79aa214b04..ad6d7287488 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eqnarray.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eqnarray.html @@ -13,9 +13,9 @@ things, but it makes a serious mess of spacing. In the system: x & = & y - z \end{eqnarray} </pre> -</blockquote> -the spacing around the "=" signs is <em>not</em> that defined in the -metrics for the font from which the glyph comes - it's +</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 <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 @@ -30,7 +30,7 @@ greater things), code as: x & = y - z \end{align} </pre> -</blockquote> +</blockquote><p> <dl> <dt><tt><i>AMSLaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errmissitem.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errmissitem.html index f7b7ec50148..27f50e1bf25 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errmissitem.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errmissitem.html @@ -7,7 +7,7 @@ <pre> Something's wrong--perhaps a missing \item </pre> -</blockquote> +</blockquote><p> actually means what it says: <blockquote> <pre> @@ -15,7 +15,7 @@ actually means what it says: boo! \end{itemize} </pre> -</blockquote> +</blockquote><p> produces the error, and is plainly in need of an <code>\</code><code>item</code> command. <p>However, the error regularly appears when you would never have thought that a <code>\</code><code>item</code> command might be appropriate. For example, the @@ -28,17 +28,17 @@ seemingly innocent: \end{alltt}% } </pre> -</blockquote> +</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: @@ -52,15 +52,15 @@ modification of the above <em>does</em> work: \end{minipage} } </pre> -</blockquote> -The code above produces a box that's far too wide for the text. One +</blockquote><p> +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 @@ -69,11 +69,11 @@ error: <pre> \fbox{\section{Boxy section}} </pre> -</blockquote> -This is a case where you've simply got to be more subtle; either you -write your own macros to replace the insides of LaTeX's sectioning -macros, or you should look for some alternative in the packages -discussed in "<a href="FAQ-secthead.html">The style of section headings</a>". -<p> -<p><p><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> +</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 +sectioning macros, or look for some alternative in the packages +discussed in +“<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-doc/doc/english/FAQ-en/html/FAQ-erroradvice.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-erroradvice.html index a865241ddbf..6f14c2e7f24 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-erroradvice.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-erroradvice.html @@ -7,33 +7,33 @@ 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 <a href="FAQ-errstruct.html">the structure of errors</a> for further details. -<li> Read the <code>.log</code> file; it contains hints to things you may not - understand, often things that have not even presented as error +<li> Read the <code>.log</code> file; it contains hints to things you may + not understand, often things that have not even presented as error messages. <li> Be aware of the amount of context that TeX gives you. The error messages gives you some bits of TeX code (or of the - document itself), that show where the error "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> <pre> \setcounter{errorcontextlines}{999} </pre> -</blockquote> - 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 +</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 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,24 +45,23 @@ 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-maillists.html">wider public</a> +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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errparnum.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errparnum.html new file mode 100644 index 00000000000..acf76cb6dcb --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errparnum.html @@ -0,0 +1,43 @@ +<head> +<title>UK TeX FAQ -- question label errparnum</title> +</head><body> +<h3>Illegal parameter number in definition</h3> +<p>The error message means what it says. In the simple case, you’ve +attempted a definition like: +<blockquote> +<pre> +\newcommand{\abc}{joy, oh #1!} +</pre> +</blockquote><p> +or (using TeX primitive definitions): +<blockquote> +<pre> +\def\abc{joy, oh #1!} +</pre> +</blockquote><p> +In either of the above, the definition uses an argument, but the +programmer did not tell (La)TeX, in advance, that she was going to. +The fix is simple — <code>\</code><code>newcommand{<code>\</code><code>abc</code>}[1]</code>, in the +LaTeX case, <code>\def\abc#1</code> in the basic TeX case. +<p>The more complicated case is exemplified by the attempted definition: +<blockquote> +<pre> +\newcommand{\abc}{joy, oh joy!% + \newcommand{\ghi}[1]{gloom, oh #1!}% +} +</pre> +</blockquote><p> +will also produce this error, as will its TeX primitive equivalent: +<blockquote> +<pre> +\def\abc{joy, oh joy!% + \def\ghi#1{gloom, oh #1!}% +} +</pre> +</blockquote><p> +This is because special care is needed when defining one macro within +the code of another macro. This is explained elsewhere, separately +for <a href="FAQ-ltxhash.html">LaTeX definitions</a> and for +<a href="FAQ-hash.html">TeX primitive definitions</a> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errparnum">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errparnum</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errstruct.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errstruct.html index d7dcb5d23d5..96584e85424 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errstruct.html +++ b/Master/texmf-doc/doc/english/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 @@ -63,11 +63,11 @@ producing 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' +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-doc/doc/english/FAQ-en/html/FAQ-etex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-etex.html new file mode 100644 index 00000000000..ce6542cd99b --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-etex.html @@ -0,0 +1,35 @@ +<head> +<title>UK TeX FAQ -- question label etex</title> +</head><body> +<h3>What is e-TeX?</h3> +<p>While Knuth has declared that TeX will never +<a href="FAQ-TeXfuture.html">change in any substantial way</a>, there remain +things that one might wish had been done differently, or indeed +implemented at all. +<p>The NTS project set out to produce an advanced replacement for +TeX, to provide a basis for developing such modifications: this +“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 +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. +Such a modified system is known as an e-TeX system, and the concept +has proved widely successful. Indeed, current TeX distributions +are delivered with most formats built with an e-TeX system (for +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 simple (increasing the number of +available registers from 256 to 65536) through to extremely subtle +programming support. +<p><a href="FAQ-context.html">ConTeXt</a> has required e-TeX for its operation +for some time. +<p>Some LaTeX packages already specify the use of e-TeX. Some such +packages may not work at all on a non-e-TeX system; others will +work, but not as well as on an e-TeX system. The +<a href="FAQ-LaTeX3.html">LaTeX team</a> has announced that future LaTeX +packages (specifically those from the team, as opposed to those +individually contributed) may require e-TeX for optimum performance. +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=etex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=etex</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-euro.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-euro.html index 46fb63062bf..ed62f2c201c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-euro.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-euro.html @@ -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 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 @@ -19,19 +19,19 @@ accessing the symbol, which selects a symbol to match the surrounding text. The design of the symbol in the TC fonts is not universally loved... Nevertheless, use the TC font version of the symbol if you are -producing documents using Knuth'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, +<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 achive 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-doc/doc/english/FAQ-en/html/FAQ-exscale.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-exscale.html index cfd3973a759..a2458e57cce 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-exscale.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-extex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extex.html index 7da2a910a4b..0ee13e76201 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extex.html @@ -2,17 +2,16 @@ <title>UK TeX FAQ -- question label extex</title> </head><body> <h3>The ExTeX project</h3> -<p><a href="http://www.dante.de/projects/extex/">The ExTeX project</a> is +<p><a href="http://www.extex.org/">The ExTeX project</a> is building on the experience of the many existing TeX development and extension projects, to develop a new TeX-like system. The system -is to be developed in Java, but will not necessarily use the code of -<a href="FAQ-NTS.html"><i>NTS</i></a>. -<p>While ExTeX will implement all of TeX's primitives, some may be -marked as obsolete, and "modern" alternatives provided (an obvious +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 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-NTS.html">e-TeX</a>, -<a href="FAQ-pdftex.html">PDFTeX</a> and <a href="FAQ-omega.html">Omega</a> +paths). Desirable extensions from <a href="FAQ-etex.html">e-TeX</a>, +<a href="FAQ-whatpdftex.html">PDFTeX</a> and <a href="FAQ-omegaleph.html">Omega</a> have been identified. <p>Usability will be another focus of the work: debugging support and log filtering mechanisms will please those who have long struggled with diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extrabrace.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extrabrace.html index c4fa20c3feb..a0e03cd4640 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extrabrace.html +++ b/Master/texmf-doc/doc/english/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 @@ -15,26 +15,26 @@ moving argument of a <code>\</code><code>section</code> command, as <pre> \section{Mumble\footnote{I couldn't think of anything better}} </pre> -</blockquote> +</blockquote><p> we get told <blockquote> <pre> ! Argument of \@sect has an extra }. </pre> -</blockquote> +</blockquote><p> The same happens with captions (the following is a simplification of a <i>comp.text.tex</i> post): <blockquote> <pre> \caption{Energy: \[e=mc^2\]} </pre> -</blockquote> +</blockquote><p> giving us the error message <blockquote> <pre> ! Argument of \@caption has an extra }. </pre> -</blockquote> +</blockquote><p> The solution is usually to use a robust command in place of the one you are using, or to force your command to be robust by prefixing it with <code>\</code><code>protect</code>, which in the <code>\</code><code>section</code> case would show as @@ -43,11 +43,11 @@ with <code>\</code><code>protect</code>, which in the <code>\</code><code>sectio <pre> \section{Mumble\protect\footnote{I couldn't think of anything better}} </pre> -</blockquote> +</blockquote><p> In both the <code>\</code><code>section</code> case and the <code>\</code><code>caption</code> case, you can separate the moving argument, as in <code>\</code><code>section[</code><em>moving</em><code>]{</code><em>static</em><code>}</code>; this gives us another standard -route - 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> @@ -55,11 +55,11 @@ example as: <pre> \caption[Energy: $E=mc^2$]{Energy: \[E=mc^2\]} </pre> -</blockquote> +</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-doc/doc/english/FAQ-en/html/FAQ-extref.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extref.html index 4bb4baa8f8c..b9e13263f44 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extref.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extref.html @@ -2,28 +2,28 @@ <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> \usepackage{xr} \externaldocument{volume1} </pre> -</blockquote> +</blockquote><p> will load all the references from <i>volume1</i> into your present document. <p>But what if the documents both have a section labelled -"<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} \externaldocument[V1-]{volume1} </pre> -</blockquote> +</blockquote><p> loads the references from <i>volume1</i>, but prefixes every one with the string <code>V1-</code>. So you would refer to the introduction to volume 1 as: @@ -35,10 +35,10 @@ as: ... ... the introduction to volume1 (\ref{V1-introduction})... </pre> -</blockquote> +</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> @@ -48,9 +48,9 @@ compiled), write: ... ... the \nameref{V1-introduction})... </pre> -</blockquote> +</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> @@ -62,7 +62,7 @@ have the .aux file, write: ... the \nameref{V1-introduction})... </pre> -</blockquote> +</blockquote><p> <dl> <dt><tt><i>xr.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) <dt><tt><i>xr-hyper.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extsizes.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extsizes.html index 51938cc23a0..fa71555960b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extsizes.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extsizes.html @@ -1,21 +1,21 @@ <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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fancyhdr.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fancyhdr.html index cf19c99044c..9160b1850dd 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fancyhdr.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fancyhdr.html @@ -2,12 +2,14 @@ <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 (in effect) specify head- and footlines for your -document. The set defined is very restricted, but LaTeX is capable -of much more; people occasionally set about employing LaTeX -facilities to do the job, but that's quite unnecessary - Piet van -Oostrum has already done the work. +<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 +useful abstractions that match the way we typically think about these +things. <p>The <i>fancyhdr</i> package provides simple mechanisms for defining pretty much every head- or footline variation you could want; the directory also contains some @@ -31,7 +33,6 @@ the <i>KOMA-script</i> classes. <dt><tt><i>fancyhdr.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.zip">macros/latex/contrib/fancyhdr</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyhdr/">browse</a>) <dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) -<dt><tt><i>scrpage2.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fancyhdr">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fancyhdr</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fig.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fig.html index 537a8f38199..b0a86b437ba 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fig.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fig.html @@ -8,7 +8,7 @@ is a set of tools which translate the code <i>fig</i>. The list of export formats is very long, and includes Metafont and MetaPost, Encapsulated PostScript and PDF, as well as combinations that wrap a graphics format in a LaTeX import file. -<p>There's no explicit port of <i>xfig</i> to windows (although it is +<p>There’s no explicit port of <i>xfig</i> to windows (although it is believed to work under <i>cygwin</i> with their X-windows system). However, the program <a href="http://tech-www.informatik.uni-hamburg.de/applets/javafig/"><i>jfig</a></i> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html index b52d06b4802..d66aec9f640 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html @@ -1,52 +1,92 @@ <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 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). +(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). <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: +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, +the job is almost trivial: +<blockquote> <pre> - \def\ThisFile{\jobname} - \newcounter{FileStack} - \let\OrigInput\input - \renewcommand{\input}[1]{% - \stepcounter{FileStack} - \expandafter\let - \csname NameStack\theFileStack\endcsname - \ThisFile - \def\ThisFile{#1}% - \OrigInput{#1}% - \expandafter\let\expandafter - \ThisFile - \csname NameStack\theFileStack\endcsname - \addtocounter{FileStack}{-1}% - } +\def\ThisFile{\jobname} +\let\OldInput\input +\renewcommand{\input}[1]{% + \renewcommand{\ThisFile}{#1}% + \OldInput{#1}% +} </pre> -(And similarly for <code>\</code><code>include</code>.) The code assumes you always use -LaTeX syntax for <code>\</code><code>input</code>, i.e., always use braces around the -argument. -<p>The <i>FiNK</i> ("File Name Keeper") package provides a +</blockquote><p> +With that, the macro <code>\</code><code>ThisFile</code> always contains the last thing +input: it starts pointing at the base file of your document +(<code>\</code><code>jobname</code>), and thereafter changes every time you use +<code>\</code><code>input{</code><em>file</em><code>}</code>. +<p>Most ordinary users will quickly become irritated with the simplicity +of of the <code>\</code><code>ThisFile</code> mechanism above. The following code is more +cunning: it maintains details of the files you’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> +<pre> +\def\ThisFile{\jobname} +\newcounter{FileStack} +\let\OrigInput\input +\renewcommand{\input}[1]{% + \stackinput{#1}{\OrigInput}% +} +\newcommand{\stackinput}[2]{% + \stepcounter{FileStack}% + \expandafter\let + \csname NameStack\theFileStack\endcsname + \ThisFile + \def\ThisFile{#1}% + #2{#1}% + \expandafter\let\expandafter + \ThisFile + \csname NameStack\theFileStack\endcsname + \addtocounter{FileStack}{-1}% +} +</pre> +</blockquote><p> +To do the same for <code>\</code><code>include</code>, we need the simple addition: +<blockquote> +<pre> +\let\OrigInclude\include +\renewcommand{\include}[1]{% + \stackinput{#1}{\OrigInclude}% +} +</pre> +</blockquote><p> +Both examples of patching <code>\</code><code>input</code> assume you always use +LaTeX syntax, i.e., always use braces around the argument. +<p>The <i>FiNK</i> (“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>. The bundle includes a -<i>fink.el</i> that provides support under <i>emacs</i> with -AUC-TeX. +extension), in a macro <code>\</code><code>finkfile</code>. If you need the unadorned file +name (without its ‘<code>.tex</code>’), use the commands: +<blockquote> +<pre> +\def\striptexext#1.tex{#1} +... +\edef\ThisFile{\expandafter\stripext\finkfile} +</pre> +</blockquote><p> +The <i>FiNK</i> bundle includes a <i>fink.el</i> that provides +support under <i>emacs</i> with AUC-TeX. <dl> <dt><tt><i>fink.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fink.zip">macros/latex/contrib/fink</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fink.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fink/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filesused.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filesused.html index b189d832bf5..101822a2bf4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filesused.html +++ b/Master/texmf-doc/doc/english/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,14 @@ 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>, +“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 <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 listed by <code>\</code><code>listfiles</code>, since +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 +32,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="ftp://cam.ctan.org/tex-archive/support/bundledoc.zip">support/bundledoc</a> (<a href="ftp://cam.ctan.org/tex-archive/support/bundledoc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/bundledoc/">browse</a>) <dt><tt><i>snapshot.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/snapshot.zip">macros/latex/contrib/snapshot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/snapshot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/snapshot/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfiles.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfiles.html index 33c1a62ddf4..f8298cfb5c1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfiles.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfiles.html @@ -4,45 +4,50 @@ <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://www.dante.de/cgi-bin/ctan-index">http://www.dante.de/cgi-bin/ctan-index</a>; the script returns -the same data as does <code>quote site index</code>, but not truncated and -arranged very neatly as a series of links to directories and -individual files. +at <a href="http://www.dante.de/cgi-bin/ctan-index">http://www.dante.de/cgi-bin/ctan-index</a>; the script scans a +list of files (<i>FILES.byname</i> — see below) and returns a list +of matches, arranged very neatly as a series of links to directories +and to individual files. <p>The <a href="http://www.tex.ac.uk/search">UK</a> and <a href="http://www.ctan.org/search">USA</a> CTANs offer a 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 + +<a href="http://www.tex.ac.uk/tex-archive/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. <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> -in <i>Google</i>'s "search box". You can also enforce the -restriction using <i>Google</i>'s "advanced search" mechanism; +</blockquote><p> +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 Dante's -"<code>quote site index</code>" command uses. This file, <i>FILES.byname</i>, +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 keep an eye on the changes on the archive. Since these files are diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfont.html index 420610918ed..8dcbcacdbe8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfont.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfont.html @@ -13,7 +13,7 @@ every six weeks, by Lee Quin. (and mostly designing highly specialised things with limited appeal to ordinary users). Most new fonts that appear are prepared in some scalable outline form or other (see -<a href="FAQ-psfchoice.html">"choice of scalable fonts"</a>), and they +<a href="FAQ-psfchoice.html">“choice of scalable fonts”</a>), and they are almost all distributed under commercial terms. <dl> <dt><tt><i>Metafont font list</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/metafont-list">info/metafont-list</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findwidth.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findwidth.html index 1bd07c02c6d..c6cfdeef124 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findwidth.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findwidth.html @@ -9,7 +9,7 @@ \setbox0=\hbox{hi} \stringwidth=\wd0 </pre> -</blockquote> +</blockquote><p> Note that if the quantity in the <code>\</code><code>hbox</code> is a phrase, the actual measurement only approximates the width that the phrase will occupy in running text, since the inter-word glue can be adjusted in paragraph @@ -20,8 +20,8 @@ mode. \newlength{\gnat} \settowidth{\gnat}{\textbf{small}} </pre> -</blockquote> -This sets the value of the length command <code>\gnat</code> to the width of "small" +</blockquote><p> +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-doc/doc/english/FAQ-en/html/FAQ-fixnam.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixnam.html index f353952c20b..d8a6bf5120c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixnam.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixnam.html @@ -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 @@ -14,17 +14,17 @@ command is always called <code>\</code><code>contentsname</code> (or rather, wha Changing the canned text is now one of the easiest customisations a user can do to LaTeX. <p>The canned text macros are all of the form -<code>\</code><code><<i>thing</i>>name</code>, and changing them is simplicity +<code>\</code><code><<i>thing</code>name</i>>, and changing them is simplicity itself. Put: <blockquote> -<code>\</code><code>renewcommand{<code>\</code><code><<i>thing</i>>name</code>}{Res minor}</code> -</blockquote> +<code>\</code><code>renewcommand{<code>\</code><code><<i>thing</code>name</i>>}{Res minor}</code> +</blockquote><p> in the preamble of your document, and the job is done. (However, beware of the <i>babel</i> package, which requires you to use a different mechanism: be sure to check <a href="FAQ-latexwords.html">changing <i>babel</i> names</a> if -you're using it.) +you’re using it.) <p>The names that are defined in the standard LaTeX classes (and the <i>makeidex</i> package) are listed below. Some of the names are only defined in a subset of the classes diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixwidtab.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixwidtab.html index 7d32ef10711..c5cc58bb42f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixwidtab.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixwidtab.html @@ -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,33 +16,33 @@ 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 than one <code>X</code> column in a +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 +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> combines the features of the -<i>longtable</i> and <i>tabularx</i> packages: it's important to +<i>longtable</i> and <i>tabularx</i> packages: it’s important to read the documentation, since usage is distinctly odd. <dl> <dt><tt><i>ltxtable.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>) <dt><tt><i>tabularx.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) -<dt><tt><i>tabulary.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>) +<dt><tt><i>tabulary.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tabulary.zip">macros/latex/contrib/tabulary</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tabulary.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tabulary/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixwidtab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixwidtab</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fllost.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fllost.html new file mode 100644 index 00000000000..596df8c8868 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fllost.html @@ -0,0 +1,28 @@ +<head> +<title>UK TeX FAQ -- question label fllost</title> +</head><body> +<h3>Float(s) lost</h3> +<p>The error +<blockquote> +<pre> +! LaTeX Error: Float(s) lost. +</pre> +</blockquote><p> +seldom occurs, but always seems deeply cryptic when it <em>does</em> +appear. +<p>The message means what it says: one or more figures, tables, etc., or +marginpars has not been typeset. (Marginpars are treated internally +as floats, which is how they come to be lumped into this error +message.) +<p>The most likely reason is that you placed a float or a <code>\</code><code>marginpar</code> +command inside another float or marginpar, or inside a +<code>minipage</code> environment, a <code>\</code><code>parbox</code> or <code>\</code><code>footnote</code>. +Note that the error may be detected a long way from the problematic +command(s), so the techniques of +<a href="FAQ-erroradvice.html">tracking down elusive errors</a> all need to be +called into play. +<p>This author has also encountered the error when developing macros that +used the LaTeX internal float mechanisms. Most people doing that +sort of thing are expected to be able to work out their own problems... +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fllost">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fllost</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floatpages.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floatpages.html index 20c1e82ab95..c933ce46d99 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floatpages.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floatpages.html @@ -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 <pre> @@ -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 containing +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 @@ -28,6 +28,6 @@ the separation between floats really big: \setlength\@fpsep{\textheight} \makeatother </pre> -</blockquote> +</blockquote><p> <p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=floatpages">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=floatpages</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floats.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floats.html index 9a0b9e86109..3ff95d552b5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floats.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floats.html @@ -5,40 +5,40 @@ <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>. +<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, consider the <code>[H]</code> placement option offered by the <i>float</i> package: - figures with this placement are made up to look as if they're - floating, but they don't in fact float. Beware outstanding floats, + figures with this placement are made up to look as if they’re + floating, but they don’t in fact float. Beware outstanding floats, though: the <code>\</code><code>caption</code> commands are numbered in the order they - appear in the document, and a <code>[H]</code> float can 'overtake' a float - that hasn't yet been placed, so that figures numbers get out of + appear in the document, and a <code>[H]</code> float can ‘overtake’ a float + that hasn’t yet been placed, so that figures numbers get out of order. <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 +<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> @@ -54,13 +54,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 @@ -76,14 +76,14 @@ 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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-flushboth.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-flushboth.html index 9812becd9a3..b0895f82e77 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-flushboth.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-flushboth.html @@ -17,16 +17,16 @@ 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 other class) will +default, and there’s no knowing what you (or some other class) will have done. -<p>If you are using Martin Schröder's <i>ragged2e</i> package, it is +<p>If you are using Martin Schröder’s <i>ragged2e</i> package, it is worth updating to the latest release (January 2003), which 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. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fmtconv.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fmtconv.html index a5190a026db..4889668394e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fmtconv.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fmtconv.html @@ -3,16 +3,14 @@ </head><body> <h3>Other conversions to and from (La)TeX</h3> <p><dl> -<dt>troff<dd><i>troff-to-latex</i>, written by Kamal Al-Yahya at Stanford - University (California, USA), assists in the translation of a - <i>troff</i> document into LaTeX format. It recognises most +<dt>troff<dd><i>Tr2latex</i>, assists in the translation of a + <i>troff</i> document into LaTeX 2.09 format. It recognises most <code>-ms</code> and <code>-man</code> macros, plus most <i>eqn</i> and some <i>tbl</i> preprocessor commands. Anything fancier needs to be done by hand. Two style files are provided. There is also a man page - (which converts very well to LaTeX...). The program is - copyrighted but free. - <i>tr2latex</i> is an enhanced version of this - <i>troff-to-latex</i>. + (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> @@ -26,10 +24,10 @@ available either for MSDOS or for Unix systems, thanks to its current maintainer Jaroslav Fojtik. <dt>PC-Write<dd><i>pcwritex.arc</i> is a - print driver for PC-Write that "prints" a PC-Write + print driver for PC-Write that “prints” a PC-Write V2.71 document to a TeX-compatible disk file. It was written by Peter Flynn at University College, Cork, Republic of Ireland. -<dt>runoff<dd> Peter Vanroose's <i>rnototex</i> +<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 @@ -38,7 +36,7 @@ <i>refer</i> format as well. The collection is not maintained. <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 convertor to LaTeX by Erwin Wechtl, called <i>rtf2latex</i>. The latest converter, by Ujwal Sathyam and Scott Prahl, is <i>rtf2latex2e</i>; this system seems rather good already, and @@ -53,7 +51,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> If cost is a constraint, the best bet is probably to use an intermediate format such as RTF or HTML. @@ -68,7 +66,7 @@ output in a new format. </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. @@ -76,8 +74,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="ftp://cam.ctan.org/tex-archive/support/excel2latex/xl2latex.zip">support/excel2latex/xl2latex.zip</a> <dt><tt><i>pcwritex.arc</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/pcwritex.zip">support/pcwritex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/pcwritex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/pcwritex/">browse</a>) @@ -88,8 +86,7 @@ translated to or from this one. <i>FrameMaker</i> provides <dt><tt><i>rtf2tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/rtf2tex.zip">support/rtf2tex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/rtf2tex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/rtf2tex/">browse</a>) <dt><tt><i>tex2rtf</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/tex2rtf.zip">support/tex2rtf</a> (<a href="ftp://cam.ctan.org/tex-archive/support/tex2rtf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/tex2rtf/">browse</a>) <dt><tt><i>tr2latex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/tr2latex.zip">support/tr2latex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/tr2latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/tr2latex/">browse</a>) -<dt><tt><i>troff-to-latex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/troff-to-latex.zip">support/troff-to-latex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/troff-to-latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/troff-to-latex/">browse</a>) -<dt><tt><i>wd2latex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/wd2latex.zip">dviware/wd2latex</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/wd2latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/wd2latex/">browse</a>) +<dt><tt><i>wd2latex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/wd2latex.zip">support/wd2latex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/wd2latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/wd2latex/">browse</a>) <dt><tt><i>wp2latex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/wp2latex.zip">support/wp2latex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/wp2latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/wp2latex/">browse</a>) <dt><tt><i>Word processor FAQ (source)</i></tt><dd> <a href="ftp://cam.ctan.org/tex-archive/help/wp-conv.zip">help/wp-conv</a> (<a href="ftp://cam.ctan.org/tex-archive/help/wp-conv.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/wp-conv/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontname.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontname.html index 2b049660600..111a33128a4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontname.html +++ b/Master/texmf-doc/doc/english/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 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-doc/doc/english/FAQ-en/html/FAQ-fonts-pln.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fonts-pln.html new file mode 100644 index 00000000000..6ebd65d03eb --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fonts-pln.html @@ -0,0 +1,86 @@ +<head> +<title>UK TeX FAQ -- question label fonts-pln</title> +</head><body> +<h3>Using non-standard fonts in Plain TeX</h3> +<p>Plain TeX (in accordance with its description) doesn’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: +<blockquote> +<pre> +\font\foo=nonstdfont +... +\foo +Text set using nonstdfont ... +</pre> +</blockquote><p> +The name you use (<code>nonstdfont</code>, above) is the name of the +<code>.tfm</code> file for the font you want. +<p>If you want to use an italic version of <code>\</code><code>foo</code>, you need to use +<code>\</code><code>font</code> again: +<blockquote> +<pre> +\font\fooi=nonstdfont-italic +... +\fooi +Text set using nonstdfont italic... +</pre> +</blockquote><p> +<p>This is all very elementary stuff, and serves for simple use of fonts. +However, there are wrinkles, the most important of which is the matter +of <a href="FAQ-whatenc.html">font encodings</a>. Unfortunately, many fonts that +have appeared recently simply don’t come in versions using Knuth’s +eccentric font encodings — but those encodings are built into Plain +TeX, so that some macros of Plain TeX need to be changed to use +the fonts. LaTeX gets around all these problems by using a “font +selection scheme” — this ‘NFSS’ (‘N’ for ‘new’, as +opposed to what LaTeX 2.09 had) carries around with it separate +information about the fonts you use, so the changes to +encoding-specific commands happen automagically. +<p>If you only want to use the <a href="FAQ-ECfonts.html">EC fonts</a>, you +can in principle use the <i>ec-plain</i> bundle, which gives you a version +of Plain TeX which you can run in the same way that you run +Plain TeX using the original CM fonts, by invoking +<i>tex</i>. (<i>Ec-plain</i> also extends the EC fonts, +for reasons which aren’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. +<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 +family, as well as size and face. The remaining packages all make +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 +for integrating outline fonts with TeX generate <code>.fd</code> files +in their process.) +<p><i>Fontch</i> has special provision for T1 and TS1 +encodings, which you select by arcane commands, such as: +<blockquote> +<pre> +\let\LMTone\relax +\input fontch.tex +</pre> +</blockquote><p> +for T1. +<p><i>Ofs</i> seems to be the most thoroughly thought-through of the +alternatives, and can select more than one encoding: as well as +T1 it covers the encoding IL2, which is favoured in the +Czech Republic and Slovakia. <i>Ofs</i> also covers mathematical fonts, +allowing you the dubious pleasure of using fonts such as the +<a href="FAQ-psfchoice.html"><i>pxfonts</i> and <i>txfonts</i></a>. +<dl> +<dt><tt><i>ec-plain</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/ec-plain.zip">macros/ec-plain</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/ec-plain.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/ec-plain/">browse</a>) +<dt><tt><i>fontch</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/fontch.zip">macros/plain/contrib/fontch</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/fontch.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/fontch/">browse</a>) +<dt><tt><i>font_selection</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/font_selection.zip">macros/plain/contrib/font_selection</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/font_selection.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/font_selection/">browse</a>) +<dt><tt><i>ofs</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/ofs.zip">macros/generic/ofs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/generic/ofs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/generic/ofs/">browse</a>) +<dt><tt><i>plnfss</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/plnfss/">macros/plain/contrib/plnfss/</a> +</dl> +<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fonts-pln">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fonts-pln</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontunavail.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontunavail.html index 24e99f1dff3..3f27b955bc4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontunavail.html +++ b/Master/texmf-doc/doc/english/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,7 +10,7 @@ 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> @@ -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,10 +43,10 @@ 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: diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footintab.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footintab.html index 530963b91ec..8d579563b7d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footintab.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footintab.html @@ -2,27 +2,27 @@ <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 the page. +<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. <p>If your table is floating, your best bet is (unfortunately) to put the table in a <code>minipage</code> environment and to put the notes -underneath the table, or to use Donald Arseneau's package -<i>threeparttable</i> (which implements "table notes" proper). +underneath the table, or to use Donald Arseneau’s package +<i>threeparttable</i> (which implements “table notes” proper). <p>The <i>ctable</i> package extends the model of <i>threeparttable</i>, and also uses the ideas of the <i>booktabs</i> package. The <code>\</code><code>ctable</code> command does the complete job of setting the table, placing the caption, and defining the -notes. The "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>Otherwise, if your table is not floating (it's just a -'<code>tabular</code>' in the middle of some text), there are several +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>Otherwise, if your table is not floating (it’s just a +‘<code>tabular</code>’ in the middle of some text), there are several things you can do to fix the problem. <ul> <li> Use <code>\</code><code>footnotemark</code> to position the little marker appropriately, and then put in <code>\</code><code>footnotetext</code> commands to fill in - the text once you'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> anyway. This provides all the ugliness of footnotes in a minipage with no extra effort. @@ -30,7 +30,7 @@ things you can do to fix the problem. floating tables, and the result might look odd if the table is not floating, but it will be reasonable. <li> Use <i>tabularx</i> or <i>longtable</i> from the LaTeX - tools distribution; they'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> Grab hold of <i>footnote</i>, and put your @@ -41,12 +41,12 @@ things you can do to fix the problem. <li> Use <i>mdwtab</i> from the same bundle; it will handle footnotes properly, and has other facilities to increase the beauty of your tables. It may also cause other table-related packages (not - the standard 'tools' ones, though) to become very unhappy and stop + the standard ‘tools’ ones, though) to become very unhappy and stop working. </ul> <p>The documentation of <i>threeparttable</i> appears in the package file itself; that of <i>ctable</i> is distributed as a PDF -file (for convenience's sake). +file (for convenience’s sake). <dl> <dt><tt><i>ctable.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ctable.zip">macros/latex/contrib/ctable</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ctable.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ctable/">browse</a>) <dt><tt><i>footnote.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footnpp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footnpp.html index 38e935d3654..3a52cc32570 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footnpp.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footnpp.html @@ -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 the link only ever +(“tidily”) at the end of the printed page; so the link only ever works by luck. <p>As a result, resetting footnotes is inevitably a two-pass process, -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 three packages that manage it, one way or another. @@ -24,14 +24,14 @@ list), you can use: <code>\</code><code>MakePerPage[2]{footnote}</code>. <p>The <i>footmisc</i> package provides a variety of means of controlling footnote appearance, among them a package option <code>perpage</code> that adjusts the numbering per page. -<p>Documentation of <i>footnpag</i> comes as a <code>.dvi</code> file +<p>Documentation of <i>footnpag</i> comes as a DVI file <i>footnpag-user</i> in the distribution. Documentation of <i>perpage</i> appears in the package file, only: however, it amounts to no more than appears above\dots <dl> <dt><tt><i>footmisc.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.zip">macros/latex/contrib/footmisc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footmisc/">browse</a>) <dt><tt><i>footnpag.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footnpag.zip">macros/latex/contrib/footnpag</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footnpag.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footnpag/">browse</a>) -<dt><tt><i>perpage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/perpage.sty">macros/latex/contrib/misc/perpage.sty</a> +<dt><tt><i>perpage.sty</i></tt><dd>Distributed as part <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse</a>) </dl> <p><p><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-doc/doc/english/FAQ-en/html/FAQ-formatstymy.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-formatstymy.html index a2faa7bdfd6..ba72434a0aa 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-formatstymy.html +++ b/Master/texmf-doc/doc/english/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. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-formbiblabel.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-formbiblabel.html new file mode 100644 index 00000000000..a79ff3a2684 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-formbiblabel.html @@ -0,0 +1,35 @@ +<head> +<title>UK TeX FAQ -- question label formbiblabel</title> +</head><body> +<h3>Format of numbers in the bibliography</h3> +<p>By default, LaTeX makes entries in the bibliography look like: +<blockquote> + [1] Doe, Joe et al. Some journal. 2004.<br> + [2] Doe, Jane et al. Some journal. 2003. +</blockquote><p> +while many documents need something like: +<blockquote> + 1. Doe, Joe et al. Some journal. 2004.<br> + 2. Doe, Jane et al. Some journal. 2003. +</blockquote><p> +<p>This sort of change may be achieved by many of the “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 +LaTeX commands, in the preamble of your document, will do the job: +<blockquote> +<pre> +\makeatletter +\renewcommand*{\@biblabel}[1]{\hfill#1.} +\makeatother +</pre> +</blockquote><p> +<dl> +<dt><tt><i>natbib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.zip">macros/latex/contrib/natbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib/">browse</a>) +</dl> +<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=formbiblabel">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=formbiblabel</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftncapt.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftncapt.html index a8014a080f6..53117549237 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftncapt.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftncapt.html @@ -16,8 +16,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> @@ -32,16 +32,16 @@ so we have: \end{minipage} \end{figure} </pre> -</blockquote> +</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.) <p>The documentation of the <i>ccaption</i> package describes a really rather awful work-around. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftnsect.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftnsect.html index 2c7520d0ae8..e66e1695c4a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftnsect.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftnsect.html @@ -3,20 +3,20 @@ </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 headings. Unfortunately, -there's no mechanism to suppress the footnote in the heading while +there’s no mechanism to suppress the footnote in the heading while allowing it in the table of contents, though having footnotes in the table of contents is probably unsatisfactory anyway. <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: <code>\section[title]{title</code><code>\</code><code>footnote</code><code>{title ftnt}}</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. </ul> <dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-T1.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-T1.html index 3be4b24f4ef..cdab3a7167c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-T1.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-T1.html @@ -3,31 +3,32 @@ </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>" -for details of these font types; also, note that the font <em>encoding</em> T1 -has nothing directly to do with the font <em>type</em> Type 1). +“<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-doc/doc/english/FAQ-en/html/FAQ-fuzzy-gs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-gs.html index bd4275cf4e5..f3231fa2a9b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-gs.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-fuzzy-type3.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-type3.html index 808556fec33..9c02f418cdc 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-type3.html +++ b/Master/texmf-doc/doc/english/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 @@ -21,14 +21,14 @@ 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 @@ -39,9 +39,9 @@ good versions of the CM fonts are available from the AMS <a href="FAQ-commercial.html">Blue Sky Research</a>). <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> @@ -55,14 +55,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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-getbitmap.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-getbitmap.html index c475e33f837..3eaa08ea12c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-getbitmap.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-getbitmap.html @@ -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> @@ -33,11 +33,11 @@ the public domain by their originators Y&Y and Bluesky Research, in association with the AMS. Unfortunately, the coverage of the sets is slightly different, 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>). <dl> <dt><tt><i>bakoma</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/ps-type1/bakoma.zip">fonts/cm/ps-type1/bakoma</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/cm/ps-type1/bakoma.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/ps-type1/bakoma/">browse</a>) <dt><tt><i>bluesky</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/ps-type1/bluesky/">fonts/cm/ps-type1/bluesky/</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gethelp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gethelp.html new file mode 100644 index 00000000000..8f0b2c4d907 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gethelp.html @@ -0,0 +1,33 @@ +<head> +<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> If you are seeking a particular package or program, look on your own +system first: you might already have it — the better TeX +distributions contain a wide range of supporting material. The +CTAN Catalogue can also help: you can +<a href="http://www.tex.ac.uk/search">search it</a>, or you can browse it +“<a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/bytopic.html">by topic</a>”. + +A catalogue entry has a description of the package, and links to any +documentation known on the net. ... when the entry is up-to-date. +<p>Failing all that, look to see if anyone else has had the problem +before; there are two places where people ask: browse or search the +newsgroup <i>comp.text.tex</i> via +<a href="http://groups.google.com/group/comp.text.tex">Google groups</a>, +and the mailing list <code>texhax</code> via its +<a href="http://tug.org/pipermail/texhax/">archive</a> +<p>If those “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>. +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 +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. +<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-doc/doc/english/FAQ-en/html/FAQ-graph-pspdf.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graph-pspdf.html index 246c763647d..1ac43924e3c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graph-pspdf.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graph-pspdf.html @@ -8,26 +8,27 @@ 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, but the aspirant PDF-maker may be using it for his output, before switching to the scheme). <li> Use <code>\</code><code>includegraphics[...]{filename}</code> without - specifying the extension (i.e., neither <code>.eps</code> nor <code>.pdf</code>). -<li> For every <code>.eps</code> file you will be including, produce a <code>.pdf</code> - version, as described in + specifying the extension (i.e., neither <code>.eps</code> nor + <code>.pdf</code>). +<li> For every <code>.eps</code> file you will be including, produce a + <code>.pdf</code> version, as described in <a href="FAQ-pdftexgraphics.html">Graphics in PDFLaTeX</a>. Having - done this, you will have two copies of each graphic (a <code>.eps</code> and a - <code>.pdf</code> file) in your directory. + 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-doc/doc/english/FAQ-en/html/FAQ-graphicspath.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graphicspath.html index d489cc3e879..6dbcff59b82 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graphicspath.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graphicspath.html @@ -1,55 +1,60 @@ <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> -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". +</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 +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”. <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: +<blockquote> <pre> - \graphicspath{{eps/}{tiff/}} +\graphicspath{{eps/}{tiff/}} </pre> +</blockquote><p> however, if the security checks on your (La)TeX system allow, the path may be anything you choose (rather than strictly relative, like -those above). +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="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) <dt><tt><i>import.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/import.sty">macros/latex/contrib/misc/import.sty</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-grmaxwidth.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-grmaxwidth.html index 91ff2ac262f..271700e262f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-grmaxwidth.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-grmaxwidth.html @@ -20,8 +20,8 @@ of course needs a little LaTeX internals programming): } \makeatother </pre> -</blockquote> -This defines a "variable" width which has the properties you want. +</blockquote><p> +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: @@ -29,6 +29,6 @@ of the graphic. <pre> \includegraphics[width=\maxwidth]{figure} </pre> -</blockquote> -<p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=grmaxwidth">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=grmaxwidth</a> +</blockquote><p> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=grmaxwidth">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=grmaxwidth</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gutter.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gutter.html new file mode 100644 index 00000000000..34a3c78ad16 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gutter.html @@ -0,0 +1,47 @@ +<head> +<title>UK TeX FAQ -- question label gutter</title> +</head><body> +<h3>Why is the inside margin so narrow?</h3> +<p>If you give the standard classes the <code>twoside</code> option, the +class sets the margins narrow on the left of odd-numbered pages, and +on the right of even-numbered pages. This is often thought to look +odd, but it is quite right. +<p>The idea is that the typographic urge for symmetry should also apply +to margins: if you lay an even numbered page to the left of an +odd-numbered one, you will see that you’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”. +<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 +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-marginmanual.html">manual margin setup</a>), the trick is to +calculate your page and margin dimensions as normal, and then: +<ul> +<li> subtract the binding offset from <code>\</code><code>evensidemargin</code>, and +<li> add the binding offset to <code>\</code><code>oddsidemargin</code>. +</ul> +which can be achieved by: +<blockquote> +<pre> +\addtolength{\evensidemargin}{-offset} +\addtolength{\oddsidemargin}{offset} +</pre> +</blockquote><p> +(substituting something sensible like “<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>. +<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gutter">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gutter</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hash.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hash.html index 92290040d6c..2fda5454772 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hash.html +++ b/Master/texmf-doc/doc/english/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> -the macro expansion produces '+++b+++b+++b+++', +</blockquote><p> +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> -<code>\</code><code>a{b}</code> will expand to '+++b+++<code>\def\x b{xxxb}</code>'. This +</blockquote><p> +<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 @@ -26,9 +26,9 @@ define <code>\</code><code>x</code> to be a macro with one argument, you need to <pre> \def\a#1{+++#1+++\def\x ##1{xxx##1}} </pre> -</blockquote> +</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-doc/doc/english/FAQ-en/html/FAQ-howmanypp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-howmanypp.html index 605b8bcef48..f418e2e6e68 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-howmanypp.html +++ b/Master/texmf-doc/doc/english/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. @@ -16,7 +16,7 @@ register) at the end of the document. makes the register it uses available as a LaTeX counter, <code>TotPages</code>, which you can also reference via <code>\</code><code>theTotPages</code>. Of course, the counter <code>TotPages</code> is asynchronous in the same way that -apge numbers are, but snapshots may safely be taken in the output +page numbers are, but snapshots may safely be taken in the output routine. <p>The <i>memoir</i> class defines two counters <code>lastpage</code> and <code>lastsheet</code>, which are set (after the first run of a document) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-htmlbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-htmlbib.html index e850b3b678d..178747e4695 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-htmlbib.html +++ b/Master/texmf-doc/doc/english/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,13 +14,13 @@ 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="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/bbl2html.awk">biblio/bibtex/utils/bbl2html.awk</a> +<dt><tt><i>bbl2html.awk</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/misc/bbl2html.awk">biblio/bibtex/utils/misc/bbl2html.awk</a> <dt><tt><i>bib2xhtml</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/bib2xhtml.zip">biblio/bibtex/utils/bib2xhtml</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/bib2xhtml.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/bib2xhtml/">browse</a>) -<dt><tt><i>noTeX.bst</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/noTeX.bst">biblio/bibtex/utils/noTeX.bst</a> +<dt><tt><i>noTeX.bst</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/misc/noTeX.bst">biblio/bibtex/utils/misc/noTeX.bst</a> </dl> <p> <p><p><p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=htmlbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=htmlbib</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyper.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyper.html index b25b29a9c85..cee095108bc 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyper.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyper.html @@ -27,11 +27,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-doc/doc/english/FAQ-en/html/FAQ-hyperdupdest.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyperdupdest.html index ff8b3826f49..ebd3320f341 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyperdupdest.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyperdupdest.html @@ -9,10 +9,28 @@ (name{page.1}) has been already used, duplicate ignored </pre> -</blockquote> +</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 (usually) due to a problem of +package interaction. Some packages are simply incompatible with +<i>hyperref</i>, but most work simply by ignoring it. In most +cases, therefore, you should load your package before you load +<i>hyperref</i>, and <i>hyperref</i> will patch things up so +that they work: +<blockquote> + <code>\</code><code>usepackage{<em>your package</em>}</code><br> + ...<br> + <code>\</code><code>usepackage[<em>opts</em>]{hyperref}</code> +</blockquote><p> +You should do this as a matter of course, unless the documentation of +a package says you <em>must</em> load it after <i>hyperref</i>. +(There aren’t many such packages: 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-doc/doc/english/FAQ-en/html/FAQ-hyphen.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphen.html index 7831c214b96..6d19b22b297 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphen.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphen.html @@ -3,21 +3,21 @@ </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) often spot ridiculous mis-hyphenation from time +and (if we’re alert) often spot ridiculous mis-hyphenation from time to time (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), and while it's capable of missing "sensible" +by Frank Liang), and while it’s capable of missing “sensible” hyphenation points, it seldom selects grossly wrong ones. The algorithm matches candidates for hyphenation against a set of -"hyphenation patterns". The candidates for hyphenation must be +“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 @@ -25,7 +25,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-doc/doc/english/FAQ-en/html/FAQ-hyphenaccents.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphenaccents.html index 4f99c0bb8af..11218ae82a0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphenaccents.html +++ b/Master/texmf-doc/doc/english/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,14 +14,15 @@ 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. -<p>In the future, perhaps, <a href="FAQ-omega.html">Omega</a> will provide a rather -different solution. +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 + <a href="FAQ-extex.html">ExTeX</a>, + +all of which base their operations on Unicode, that the whole basis of +encodings will change. <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphenaccents">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphenaccents</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphexcept.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphexcept.html index 6361da94463..2291ff25330 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphexcept.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphexcept.html @@ -2,20 +2,20 @@ <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 (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 ... </pre> -</blockquote> +</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 @@ -24,10 +24,10 @@ write: <pre> \hyphenation{man-u-script} </pre> -</blockquote> +</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: @@ -37,10 +37,10 @@ select the appropriate language, and do the same as above: \selectlanguage{french} \hyphenation{re-cher-cher} </pre> -</blockquote> -(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 +</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 with accents in them produce an error: <blockquote> <pre> @@ -48,8 +48,8 @@ with accents in them produce an error: \selectlanguage{french} \hyphenation{r\'e-f\'e-rence} </pre> -</blockquote> -tells us that the hyphenation is "improper", and that it will be "flushed". +</blockquote><p> +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 @@ -62,7 +62,7 @@ patterns provided in the usual distributions, the encoding is \selectlanguage{french} \hyphenation{r\'e-f\'e-rence} </pre> -</blockquote> +</blockquote><p> <p>The same sort of performance goes for any language for which 8-bit fonts and corresponding hyphenation patterns are available. Since you have to select both the language and the font encoding to have your diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphoff.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphoff.html index 3e12f299c24..b5224ca3221 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphoff.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphoff.html @@ -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. @@ -25,16 +25,18 @@ and the <i>hyphenat</i> package uses this technique for its hyphenation. <p>Third, one can set <code>\</code><code>left-</code> and/or <code>\</code><code>righthyphenmin</code> to a sufficiently large value that no hyphenation could possibly succeed, -since the minimum is larger than the the length of the longest word +since the minimum is larger than the length of the longest word TeX is willing to hyphenate (the appropriate value is 62). <p>Fourth, one can suppress hyphenation for all text using the current font by the command +<blockquote> <pre> - \hyphenchar\font=-1 +\hyphenchar\font=-1 </pre> -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 +</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 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 @@ -56,10 +58,8 @@ and underfull lines. To avoid this you have two options. You may use have TeX stretch what would otherwise be underfull lines to fill the space offered, and wrap other lines, while prematurely wrapping overfull lines and stretching the remainder. 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 +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 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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-i18nbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-i18nbib.html index 3b368e5a518..5d0063df514 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-i18nbib.html +++ b/Master/texmf-doc/doc/english/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,34 +20,34 @@ 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="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/babelbib.zip">biblio/bibtex/contrib/babelbib</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/babelbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/babelbib/">browse</a>) <dt><tt><i>bib-fr bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/bib-fr.zip">biblio/bibtex/contrib/bib-fr</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/bib-fr.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/bib-fr/">browse</a>) <dt><tt><i>bibgerm bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/germbib.zip">biblio/bibtex/contrib/germbib</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/germbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/germbib/">browse</a>) <dt><tt><i>custom-bib bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/custom-bib.zip">macros/latex/contrib/custom-bib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/custom-bib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/custom-bib/">browse</a>) -<dt><tt><i>finplain.bst</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/finplain.bst">biblio/bibtex/contrib/finplain.bst</a> +<dt><tt><i>finplain.bst</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/misc/finplain.bst">biblio/bibtex/contrib/misc/finplain.bst</a> <dt><tt><i>norbib bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/norbib.zip">biblio/bibtex/contrib/norbib</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/norbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/norbib/">browse</a>) <dt><tt><i>spain</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/spain.zip">biblio/bibtex/contrib/spain</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/spain.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/spain/">browse</a>) <dt><tt><i>swebib bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/swebib.zip">biblio/bibtex/contrib/swebib</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/swebib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/swebib/">browse</a>) </dl> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=i18nbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=i18nbib</a> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=i18nbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=i18nbib</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ifpdf.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ifpdf.html index 43f8b1c81f4..fabab280854 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ifpdf.html +++ b/Master/texmf-doc/doc/english/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 @@ -18,19 +18,19 @@ was present in the very first releases of PDFTeX) is <running PDFTeX> \fi </pre> -</blockquote> +</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> \let\pdfoutput\undefined </pre> -</blockquote> +</blockquote><p> so that your test will falsely choose the first alternative. While this is a theoretical problem, it is unlikely to be a major one. <p>More important is the user who loads a package that uses -LaTeX-style testing for the command name'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: @@ -46,11 +46,11 @@ test may need to be elaborated: \fi \fi </pre> -</blockquote> +</blockquote><p> If you only want to know whether some PDFTeX extension (such as marginal kerning) is present, you can stop at this point: you know as much as you need. -<p>However, if you need to know whether you'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> @@ -69,12 +69,12 @@ output, you also need to know about the value of <code>\</code><code>pdfoutput</ \fi \fi </pre> -</blockquote> -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. +</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. <dl> -<dt><tt><i>ifpdf.sty</i></tt><dd>Distributed with Heiko Oberdiek's packages <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>) +<dt><tt><i>ifpdf.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ifpdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ifpdf</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-impgraph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-impgraph.html index 76bc6ce9346..7b2c9979e45 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-impgraph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-impgraph.html @@ -3,7 +3,7 @@ </head><body> <h3>How to import graphics into (La)TeX documents</h3> <p>Knuth, when designing the current version of TeX back in the early -1980s, could discern no "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 @@ -30,14 +30,14 @@ the above two cases), but their code could be configured for others. <p>The obvious next step was to make the code configurable dynamically. The LaTeX standard <i>graphics</i> package and its derivatives made this step: it is strongly preferred for all current work. It can -also be used (with the help of the <i>miniltx</i> "LaTeX -emulator" and the <i>graphicx.tex</i> front-end) in documents +also be used (with the help of the <i>miniltx</i> “LaTeX +emulator” and the <i>graphicx.tex</i> front-end) in documents written in Plain TeX. -<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 determins whether PDFLaTeX is running, and selects the definitions for it if so). @@ -49,7 +49,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 @@ -60,33 +60,33 @@ 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="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/epsf.tex">macros/plain/contrib/epsf.tex</a> +<dt><tt><i>epsf.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/epsf/epsf.tex">macros/generic/epsf/epsf.tex</a> <dt><tt><i>epsfig.sty</i></tt><dd>Part of the <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) bundle -<dt><tt><i>epslatex.pdf</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/epslatex.pdf">info/epslatex.pdf</a>; the document is also available - in PostScript format as <a href="ftp://cam.ctan.org/tex-archive/info/epslatex.ps">info/epslatex.ps</a> +<dt><tt><i>epslatex.pdf</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/epslatex/english/epslatex.pdf">info/epslatex/english/epslatex.pdf</a>; the document is also available + in PostScript format as <a href="ftp://cam.ctan.org/tex-archive/info/epslatex/english/epslatex.ps">info/epslatex/english/epslatex.ps</a> <dt><tt><i>graphics.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) <dt><tt><i>graphicx.sty</i></tt><dd>Part of the <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) bundle <dt><tt><i>miniltx.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/graphics.zip">macros/plain/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/graphics/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inclplain.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inclplain.html index 7a579fa0c3e..5351d1f8d0a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inclplain.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inclplain.html @@ -4,25 +4,27 @@ <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 document may be processed: +<blockquote> <pre> \begin{plain} \input{plain-doc} \end{plain} </pre> +</blockquote><p> The package is known to fail, for example, with documents that use AMSTeX; no doubt it would also fail if asked to load Eplain. -All these things can be overcome (although it'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="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-include.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-include.html index dae5082fcaf..e1158bfc6d2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-include.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-inputlev.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inputlev.html index e0ecba13ebb..e4047de4ee8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inputlev.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html index b8f56767729..2ce7546241e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html @@ -14,12 +14,12 @@ so the first thing to do is to just try it. On a system that uses latex sample2e dvips -Pcmz -Pamz -o sample2e.ps sample2e </pre> -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> +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 including the Type 1 font, +this is <i>dvips</i> telling you it’s including the Type 1 font, and you need do no more. <p>If the test has failed, you need to install your own set of the fonts. <p>The CTAN directories listed below contain compressed archives of @@ -27,11 +27,11 @@ the Type 1 files for various architectures, both for the Computer Modern fonts and for the AMS fonts of mathematical and other useful things. Download the archives that are appropriate for your architecture, and -extract the files - you only actually need the contents of the +extract the files — you only actually need the contents of the <i>pfb</i> directories, since you already have the fonts -installed in the "ordinary" way, so that the TFM files are -already present. (You don't need the PostScript font metric - AFM -and PFM - files in any case.) +installed in the “ordinary” way, so that the TFM files are +already present. (You don’t need the PostScript font metric — AFM +and PFM — files in any case.) <p>The files should go into your local <code>texmf</code> tree (<i>texmf.local</i>, <i>texmf-local</i>, <i>localtexmf</i>, or whatever). Create directories at offsets <i>fonts/type1/bluesky/cm</i> and @@ -45,7 +45,7 @@ AMS fonts; for the CM fonts, map files are available separately. <p>The set of map files includes files <code>config.*</code>; each of these contains an instruction to load a single map file. For ordinary use, you -instruct <i>dvips</i> to load the "detailed" map of the +instruct <i>dvips</i> to load the “detailed” map of the CM fonts by use of the command: <pre> dvips -Pcmz myfile diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instfont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instfont.html index 3c08c1f51eb..b3caf4a1a81 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instfont.html +++ b/Master/texmf-doc/doc/english/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 - see, for example, +Other answers discuss specific font families — see, 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-doc/doc/english/FAQ-en/html/FAQ-instmffont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html index d35454526b5..d1fd7f10b4a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html @@ -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, do 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-wherefiles.html">Where to install files</a>" +<p>“<a href="FAQ-wherefiles.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-doc/doc/english/FAQ-en/html/FAQ-instpackages.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instpackages.html index 98112a4fc4c..2e389887e49 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instpackages.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instpackages.html @@ -9,12 +9,12 @@ since version 2.1, offers a <a href="FAQ-miktexinst.html">simpler procedure</a> than that described here, for packages it knows about. <p>Ordinarily, you should download the whole distribution directory; the only occasion when this is not necessary is when you are getting -something from one of the (La)TeX contributed "<i>misc</i>" +something from one of the (La)TeX contributed “<i>misc</i>” directories on CTAN; these directories contain collections of single files, which are supposedly complete in themselves. <p>A small package <<i>smallpack</i>> might be just a single <code>.sty</code> file (typically <i>smallpack.sty</i>) with the usage instructions either -included as comments in the file or in a seperate user manual or +included as comments in the file or in a separate user manual or <i>README</i> file. More often a package <<i>pack</i>> will come as a pair of files, <i>pack.ins</i> and <i>pack.dtx</i>, written to be used with the LaTeX <i>doc</i> system. The package code must be @@ -32,18 +32,20 @@ unpack a <i>doc</i> package <<i>pack</i>>, do the following: manual and possibly a commented version of the package code. <li> Run latex again on <i>pack.dtx</i>, which should resolve any references and generate a Table of Contents if it was called for. -<li> LaTeX may have said "<code>No file pack.ind</code>"; this is the +<li> LaTeX may have said “<code>No file pack.ind</code>”; this is the source for the command index; if you want the index, process the raw - material with:<br> - <code> makeindex -s gind.ist pack</code><br> + material with: + <blockquote> + <code>makeindex -s gind.ist pack</code> + </blockquote><p> and run LaTeX again. <li> Print and read <i>pack.dvi</i> </ul> -Sometimes a user manual is supplied seperately from the <i>.dtx</i> +Sometimes a user manual is supplied separately from the <i>.dtx</i> file. Process this <em>after</em> doing the above, just in case the user manual uses the package it is describing. <p>Almost the final stage of the installation is to put the package -file(s) <em>'where LaTeX can find them'</em>. Where the magic place +file(s) <em>‘where LaTeX can find them’</em>. Where the magic place is, and how you put the files there depends on your particular LaTeX system and how it is set up (see @@ -60,30 +62,23 @@ for this purpose. <dt>teTeX<dd> Run: <br> <code>texhash</code> <dt>web2c<dd> On a current <i>web2c</i> distribution, <code>texhash</code> - ought to work; if it doesn't, run <code>mktexlsr</code> - <dt>fpTeX<dd> Click - <code>Start</code>-> - <code>Programs</code>-> - <code>Texlive</code>-> - <code>Maintenance</code>-> - <code>Rebuild ls-R filenames databases</code>, or open a "command" - window and run <code>texhash</code> -<dt>MiKTeX<dd> On a <i>MikTeX</i> distribution earlier than v2.0, + ought to work; if it doesn’t, run <code>mktexlsr</code> +<dt>MiKTeX<dd> On a <i>MiKTeX</i> distribution earlier than v2.0, click <code>Start</code>-> <code>Programs</code>-> - <code>MikTeX</code>-> + <code>MiKTeX</code>-> <code>Maintenance</code>-> <code>Refresh filename database</code> <p> or get a DOS window and run:<br> <code>initexmf --update-fndb</code> -<p> On a <i>MikTeX</i> distribution v2.0 or later, do:<br> +<p> On a <i>MiKTeX</i> distribution v2.0 or later, do:<br> <code>Start</code>-> <code>Programs</code>-> - <code>MikTeX 2</code>-> - <code>MikTeX Options</code>, and press the + <code>MiKTeX 2</code>-> + <code>MiKTeX Options</code>, and press the <code>Refresh now</code> button (<code>Update filename database</code> in earlier versions of MiKTeX). diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instprinterfont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instprinterfont.html index a8eb8c610b3..788de00a57a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instprinterfont.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instprinterfont.html @@ -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 @@ -29,7 +29,7 @@ coverage of maths-with-<i>Times</i> and -<i>Palatino</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-doc/doc/english/FAQ-en/html/FAQ-instt1font.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html index 4bb0b64aabc..5d5cf7533ed 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html @@ -7,42 +7,44 @@ it may be separated into a modest set of stages. <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 default: if the files are not available, you are unlikely to be able to use the font with (La)TeX. <li> Rename the AFM files and the Type 1 files to match the - " - <a href="FAQ-fontname.html">Berry font naming scheme</a>". + <a href="FAQ-fontname.html">Berry font naming scheme</a>. <li> Generate TeX metric files from the AFM files. The commonest tool for this task is <i>fontinst</i>; the package documentation helps, but other guides are available (see below). The simplest possible script to pass to <i>fontinst</i> is: <blockquote> - <code>\latinfamily{xyz}</code><br> - <code>\bye</code> - </blockquote> +<pre> +\latinfamily{xyz}{} +\bye +</pre> + </blockquote><p> where <code>xyz</code> is the Berry name of the font family. This simple script is adequate for most purposes: its output covers the - font family in both <code>T1</code> and <code>OT1</code> font encodings. Nevertheless, + font family in both T1 and OT1 font encodings. Nevertheless, with fancier fonts, more elaborate things are possible with <i>fontinst</i>: see the documentation for details. <p> <i>Fontinst</i> also generates map files, and LaTeX font definition (<code>.fd</code>) files. <li> Install the files, in your <code>texmf</code> tree. All the strictures about installing non-standard things apply here: be sure - to put the files in the local tree. Reasonable destinations for the - various files are: + to put the files in the local tree. The list gives reasonable + destinations for the various files related to a font whose Berry + name is <<i>bname</i>>: <pre> .pfb, @@ -50,6 +52,14 @@ it may be separated into a modest set of stages. .tfm .../fonts/tfm/<foundry>/<bname> .vf .../fonts/vf/<foundry>/<bname> .fd .../tex/latex/fontinst/<foundry>/<bname> +</pre> + The irregular things being <code>.map</code> files: in teTeX 3.0 and + later, these should be placed according to the revised TDS as +<pre> +.map .../fonts/map/dvips/<foundry> +</pre> +and in other (earlier) systems as +<pre> .map .../dvips/fontinst/<foundry> </pre> <li> Regenerate the file indexes (as described in @@ -64,18 +74,18 @@ it may be separated into a modest set of stages. <pre> updmap --enable Map <xyz>.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> which is described in MiKTeX - <a href="http://www.miktex.org/manual/psfonts.html">online documentation</a>. + <a href="http://docs.miktex.org/manual/psfonts.html#chgupdmapcfg">online documentation</a>. Then execute the command <code>initexmf --mkmaps</code>, and the job is done. </ul> </ul> The whole process is very well (and thoroughly) described in Philipp -Lehman's guide to font installation, which may be found on CTAN. +Lehman’s guide to font installation, which may be found on CTAN. <dl> <dt><tt><i>fontinst.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.zip">fonts/utilities/fontinst</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/fontinst/">browse</a>) <dt><tt><i>Type 1 installation guide</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/Type1fonts/fontinstallationguide/fontinstallationguide.pdf">info/Type1fonts/fontinstallationguide/fontinstallationguide.pdf</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-interruptlist.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-interruptlist.html index de3aaad7b8e..0de9ad2eeb2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-interruptlist.html +++ b/Master/texmf-doc/doc/english/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. @@ -28,12 +28,12 @@ restarting enumerate: ... \end{enumerate} </pre> -</blockquote> +</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 +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> @@ -46,14 +46,14 @@ itself interrupted) in the "commentary text"). ... \end{enumerate} </pre> -</blockquote> +</blockquote><p> The package allows an optional name (as in <code>\</code><code>suspend[id]{enumerate}</code>) to allow you to identify a particular suspension, and hence provide a handle for manipulating nested suspensions. -<p>If you'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 @@ -70,7 +70,7 @@ which requires use of extra braces: ... \end{enumerate} </pre> -</blockquote> +</blockquote><p> The <i>enumitem</i> package, in its most recent release, will allow you to resume lists, at one level only: <blockquote> @@ -83,8 +83,8 @@ release, will allow you to resume lists, at one level only: ... \end{enumerate} </pre> -</blockquote> -which feels just as "natural" as the <i>mdwtools</i> facility, +</blockquote><p> +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>. <dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-isdef.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-isdef.html new file mode 100644 index 00000000000..bfca87b02fc --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-isdef.html @@ -0,0 +1,86 @@ +<head> +<title>UK TeX FAQ -- question label isdef</title> +</head><body> +<h3>Is this command defined?</h3> +<p>Macro sets from the earliest days of TeX programming may be +observed to test whether commands exist by using +<blockquote> +<code>\</code><code>ifx</code> csx<code><em>command</em></code> <code>\</code><code>undefined</code> <<i>stuff</i>> ... +</blockquote><p> +(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). +<p>The <code>\</code><code>@ifundefined</code> command is based on the sequence +<blockquote> + +<pre> +\expandafter \ifx \csname cmd name\endcsname \relax +</pre> +</blockquote><p> +which relies on the way <code>\</code><code>csname</code> works: if the command doesn’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 +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>” +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> +altogether. +<p>David Kastrup offers the (rather tricky) +<blockquote> +<pre> +{\expandafter}\expandafter\ifx \csname cmd name\endcsname\relax ... +</pre> + +</blockquote><p> +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 +defines two new primitives: +<ul> +<li> <code>\</code><code>ifdefined</code>, which tests whether a thing is defined (the + negative of comparing with <code>\</code><code>undefined</code>, as it were), and +<li> <code>\</code><code>ifcsname</code> <code>cmd name</code><code>\</code><code>endcsname</code>, which does the + negative of <code>\</code><code>@ifundefined</code> without the <code>\</code><code>relax</code>-command + side-effect. +</ul> +So, in an e-TeX-based system, the following two conditional clauses do +the same thing: +<blockquote> +<pre> +\ifdefined\foo + \message{\string\foo\space is defined}% +\else + \message{no command \string\foo}% +\fi +% +\ifcsname foo\endcsname + \message{\string\foo\space is defined}% +\else + \message{no command \string\foo}% +\fi +</pre> +</blockquote><p> +However, after using the LaTeX +<code>\</code><code>@ifundefined{foo}</code>..., the conditionals will detect the +command as “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 +for most packages, these two primitives may be expected appear widely +in new macro packages. +<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=isdef">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=isdef</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-isitanum.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-isitanum.html index 85f25e9c91c..0e2111d2a84 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-isitanum.html +++ b/Master/texmf-doc/doc/english/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> @@ -19,10 +19,10 @@ all comparisons: \else\isanumfalse \fi\fi...\fi </pre> -</blockquote> +</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 @@ -30,13 +30,13 @@ that the digits' character codes are consecutive: \fi \fi </pre> -</blockquote> -again used in tail-recursion. However, these forms aren't very -satisfactory: getting the recursion "right" is troublesome (it has a +</blockquote><p> +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> @@ -45,7 +45,7 @@ for an argument being a strictly positive integer: \ifcat_\ifnum0<0#1 _\else A\fi } </pre> -</blockquote> +</blockquote><p> which can be adapted to a test for a non-negative integer thus: <blockquote> <pre> @@ -53,7 +53,7 @@ which can be adapted to a test for a non-negative integer thus: \ifcat_\ifnum9<1#1 _\else A\fi } </pre> -</blockquote> +</blockquote><p> or a test for any integer: <blockquote> <pre> @@ -63,18 +63,18 @@ or a test for any integer: \ifcat_\ifnum9<1\gobbleminus#1 _\else A\fi } </pre> -</blockquote> +</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> \def\testnum#1{\afterassignment\testresult\count255=#1 \end} \def\testresult#1\end{\ifx\end#1\end\isanumtrue\else\isanumfalse\fi} </pre> -</blockquote> +</blockquote><p> (which technique is due to David Kastrup); this can provoke errors. In a later thread on the same topic, Michael Downes offered: <blockquote> @@ -91,13 +91,13 @@ In a later thread on the same topic, Michael Downes offered: } </pre> -</blockquote> +</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>}% @@ -106,12 +106,12 @@ conditionals written "naturally" - for example: <deal with non-integer>% \fi </pre> -</blockquote> +</blockquote><p> The LaTeX <i>memoir</i> class has an internal command of its own, <code>\</code><code>checkifinteger{</code><em>num</em><code>}</code>, that sets the conditional command <code>\</code><code>ifinteger</code> according to whether the argument was an integer. <p>Of course, all this kerfuffle would be (essentially) void if there was -a simple means of "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> @@ -127,9 +127,9 @@ error-catching primitive <code>\</code><code>ifnoerror</code>, one might write: \fi } </pre> -</blockquote> -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 +</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 impossible to program within TeX!). <dl> <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-journalpaper.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-journalpaper.html index 5a43d244639..4e74cbf1606 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-journalpaper.html +++ b/Master/texmf-doc/doc/english/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. +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 +<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-doc/doc/english/FAQ-en/html/FAQ-keepfonts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-keepfonts.html index 11336f0edf9..aa30defd5c3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-keepfonts.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-labelctr.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelctr.html index 903ad03de7c..0226073d97d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelctr.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-labelfig.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelfig.html index b8c83fd31db..41af36c2aff 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelfig.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelfig.html @@ -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,27 +11,44 @@ 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. -(Unfortunately, <i>psfrag</i> can't be used with PDFLaTeX, +(Unfortunately, <i>psfrag</i> can’t be used with PDFLaTeX, though one might hope that it would be susceptible to the same sort of treatment as is used in the <i>pdftricks</i> package. On the other -hand, <a href="FAQ-commercial.html">VTeX</a>'s GeX processor explicitly deals -with <i>psfrag</i>, both in its free and commercial instances.) +hand, + + <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 +<i>psfrag</i>: it provides a means whereby you can put the +<i>psfrag</i> commands into the preamble of your EPS file +itself. <i>Psfrag</i> has such a command itself, but deprecates +it; <i>psfragx</i> has cleaned up the facility, and provides a +script <i>laprint</i> for use with <i>Matlab</i> to produce +appropriately tagged output. (In principle, other graphics +applications could provide a similar facility, but apparently none does.) +<p><i>Emacs</i> users may find the embedded editor <i>iTe</i> a +useful tool for placing labels: it’s a (La)TeX-oriented graphical +editor written in <i>Emacs Lisp</i>. You create +<code>iteblock</code> environments containing graphics and text, and +may then invoke <i>iTe</i> to arrange the elements relative to one +another. <p>Another useful approach is <i>overpic</i>, which overlays a <code>picture</code> environment on a graphic included by use of <code>\</code><code>includegraphics</code>. This treatment lends itself to ready placement of texts and the like on top of a graphic. The package can draw a -grid for planning your "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. -The <i>pstricks</i> web site has a page of -<a href="http://pstricks.de/Examples/overlay.phtml">examples of labelling</a> +can, with all the flexibility of PostScript programming that it offers +The <i>pstricks</i> web site has a page with several +<a href="http://pstricks.tug.org/main.cgi?file=Examples/overlay">examples of labelling</a> which will get you started; if <i>pstricks</i> is <a href="FAQ-drawing.html">an option for you</a>, this route is worth a try. <p>The confident user may, of course, do the whole job in a picture @@ -40,8 +57,11 @@ environment which itself includes the graphic. I would recommend are plainly little more than a convenience over what is achievable with the do-it-yourself approach. <dl> +<dt><tt><i>iTe</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/ite.zip">support/ite</a> (<a href="ftp://cam.ctan.org/tex-archive/support/ite.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/ite/">browse</a>) +<dt><tt><i>laprint</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psfragx.zip">macros/latex/contrib/psfragx</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psfragx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/psfragx/">browse</a>) <dt><tt><i>overpic.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/overpic.zip">macros/latex/contrib/overpic</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/overpic.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/overpic/">browse</a>) <dt><tt><i>psfrag.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psfrag.zip">macros/latex/contrib/psfrag</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psfrag.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/psfrag/">browse</a>) +<dt><tt><i>psfragx.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psfragx.zip">macros/latex/contrib/psfragx</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psfragx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/psfragx/">browse</a>) <dt><tt><i>pstricks.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.zip">graphics/pstricks</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pstricks/">browse</a>) </dl> <p> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelformat.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelformat.html index be9b1eea97b..b3a63660267 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelformat.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelformat.html @@ -3,33 +3,33 @@ </head><body> <h3>How to change the format of labels</h3> <p>By default, when a label is created, it takes on the appearance of the -counter labelled: specifically, it is set to -<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 +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 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> -which would be both tedious and error-prone. What's more, it would be +</blockquote><p> +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> @@ -41,7 +41,7 @@ workings of this aren't quite right, and you need to patch the }% } </pre> -</blockquote> +</blockquote><p> With the patch in place you can now, for example, change the labels on all inner lists by adding the following code in your preamble: <blockquote> @@ -50,9 +50,9 @@ all inner lists by adding the following code in your preamble: \renewcommand{\p@enumii}[1]{\theenumi(#1)} \makeatother </pre> -</blockquote> +</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 @@ -61,7 +61,7 @@ the patch to LaTeX itself). With the package, the code above is <pre> \labelformat{enumii}{\theenumi(#1)} </pre> -</blockquote> +</blockquote><p> In fact, the above example, which we can do in several different ways, has been rendered obsolete by the appearance of the <i>enumitem</i> package, which is discussed in the answer about diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labundef.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labundef.html index 5d5b5be1fe8..2cba86986ff 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labundef.html +++ b/Master/texmf-doc/doc/english/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 @@ -11,19 +11,29 @@ then simply a matter of detecting if the command exists. The usual LaTeX internal way of doing this is to use the command <code>\</code><code>@ifundefined</code>: <blockquote> - <code>\</code><code>@ifundefined{</code><em><code>r@</code>lab-name</em><code>}{</code><em>undef-cmds</em><code>}</code>{def-cmds} -</blockquote> -In which, <<i>lab-name</i>> is exactly what you would use in + <code>\</code><code>@ifundefined{</code><em></em>r@<em>label-name</em><code>}{</code><em>undef-cmds</em><code>}{</code><em>def-cmds</em><code>}</code> +</blockquote><p> +In which, <<i>label-name</i>> is exactly what you would use in a <code>\</code><code>label</code> command, and the remaining two arguments are command sequences to be used if the label is undefined (<<i>undef-cmds</i>>) or if it is defined -(<code><em>def-cmds</em></code>). +(<<i>def-cmds</i>>). <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 +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 +definition is a bit complicated, but the package itself is pretty +powerful. +<dl> +<dt><tt><i>labelcas.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/labelcas.zip">macros/latex/contrib/labelcas</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/labelcas.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/labelcas/">browse</a>) +</dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labundef">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labundef</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-landscape.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-landscape.html index 7995ccb54a5..a14842e51ae 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-landscape.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-landscape.html @@ -2,23 +2,29 @@ <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 deep, and will only fit on the page in landscape orientation, use - the <i>rotating</i> package; this defines <code>sidewaysfigure</code> and - <code>sidewaystable</code> environments which create floats that - occupy a whole page. + the <i>rotating</i> package; this defines + <code>sidewaysfigure</code> and <code>sidewaystable</code> + environments which create floats that occupy a whole page. +<p> Note that <i>rotating</i> has problems in a document that also + loads the <i>float</i> package, which recommended in other + answers in these FAQs, for example that on + <a href="FAQ-floats.html">float placement</a>. The <i>rotfloat</i> package + loads <i>rotating</i> for you, and smooths the interaction with + <i>float</i>. <li> If you have a long sequence of things that need to be typeset in landscape (perhaps a code listing, a wide <code>tabbing</code> environment, or a huge table typeset using <i>longtable</i> or <i>supertabular</i>), use the <i>lscape</i> package (or - <i>pdflscape</i> if you'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 @@ -26,9 +32,9 @@ 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 would use the techniques +behaviour was an absolute necessity, one might use the techniques described in <a href="FAQ-textflow.html">"flowing text around figures"</a>, and would @@ -45,7 +51,7 @@ also give it <code>dvips</code> or <code>pdftex</code> option, output to be properly oriented. The <i>memoir</i> class has the same facilities, in this respect, as does <i>geometry</i>. <p>A word of warning: most current TeX previewers do not honour -rotation requests in <code>.dvi</code> files (the exception is +rotation requests in DVI files. @@ -56,19 +62,21 @@ rotation requests in <code>.dvi</code> files (the exception is -the fpTeX previewer WinDVI). If your previewer is not -capable of rotation, your best bet is to convert your output to PostScript -or to PDF, and to view these 'final' forms with an appropriate -viewer. + + + +Your best bet is to convert your output to PostScript or to PDF, and +to view these ‘final’ forms with an appropriate viewer. <dl> <dt><tt><i>geometry.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/geometry.zip">macros/latex/contrib/geometry</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/geometry.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/geometry/">browse</a>) <dt><tt><i>graphics.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) <dt><tt><i>longtable.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) <dt><tt><i>lscape.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) -<dt><tt><i>pdflscape.sty</i></tt><dd>Distributed with Heiko Oberdiek's packages +<dt><tt><i>pdflscape.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>) <dt><tt><i>rotating.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rotating.zip">macros/latex/contrib/rotating</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rotating.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/rotating/">browse</a>) +<dt><tt><i>rotfloat.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rotfloat.zip">macros/latex/contrib/rotfloat</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rotfloat.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/rotfloat/">browse</a>) <dt><tt><i>supertabular.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/supertabular.zip">macros/latex/contrib/supertabular</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/supertabular.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/supertabular/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=landscape">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=landscape</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latex.html index ac18984344b..022e518df26 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latex.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-latex2e.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latex2e.html index 7508d3d72a2..189dececf96 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latex2e.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latex2e.html @@ -2,7 +2,7 @@ <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 @@ -10,13 +10,13 @@ LaTeX, and draws together several threads of LaTeX development from the later days of LaTeX 2.09. <p>LaTeX2e has several enhancements over LaTeX 2.09, but they were all rather minor, with a view to continuity and stability rather than the -"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 bitter 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="ftp://cam.ctan.org/tex-archive/macros/latex/doc.zip">macros/latex/doc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/doc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/doc/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexbug.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexbug.html index f71b1ad6aa8..7673f440e8e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexbug.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexbug.html @@ -4,24 +4,28 @@ <h3>Reporting a LaTeX bug</h3> <p>The LaTeX team supports LaTeX, and will deal with -<em>bona fide</em> bug reports. However, you need to be slightly +<em>bona fide</em> bug reports. Note that the LaTeX team does +<em>not</em> deal with contributed packages — just the software that +is part of the LaTeX distribution itself: LaTeX and the +“required” packages. +Furthermore, you need to be slightly careful to produce a bug report that is usable by the team. The steps are: <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 will reject your report. +mechanisms may reject your report. <p><b>2.</b> Has your bug already been reported? Browse the <a href="http://www.latex-project.org/cgi-bin/ltxbugs2html?introduction=yes">LaTeX bugs database</a>, to find any earlier instance of your bug. In many cases, the database will list a work-around. <p><b>3.</b> Prepare a -<a href="FAQ-minxampl.html">"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 @@ -34,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 @@ -47,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-doc/doc/english/FAQ-en/html/FAQ-latexpronounce.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexpronounce.html index f08afe3b77b..ede339371fe 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexpronounce.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexpronounce.html @@ -1,15 +1,15 @@ <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. -<p>The 'epsilon' in 'LaTeX2e' is supposed to be suggestive of a small +<p>The ‘epsilon’ in ‘LaTeX2e’ is supposed to be suggestive of a small improvement over the old LaTeX 2.09. Nevertheless, most people -pronounce the name as 'LaTeX-two-ee'. +pronounce the name as ‘LaTeX-two-ee’. <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-doc/doc/english/FAQ-en/html/FAQ-latexwords.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexwords.html index e59a62cb87d..e949a3ce475 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexwords.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-letterclass.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterclass.html index 9193eaf18e0..102ccd33d81 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterclass.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterclass.html @@ -15,14 +15,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 @@ -31,7 +31,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="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/akletter.zip">macros/latex/contrib/akletter</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/akletter.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/akletter/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterspace.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterspace.html index 193d90f4fee..e8a7dbd27e2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterspace.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterspace.html @@ -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 @@ -24,11 +24,11 @@ in some distributions). <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>.) <dl> -<dt><tt><i>letterspacing.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/letterspacing.tex">macros/generic/letterspacing.tex</a> +<dt><tt><i>letterspacing.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/misc/letterspacing.tex">macros/generic/misc/letterspacing.tex</a> <dt><tt><i>soul.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/soul.zip">macros/latex/contrib/soul</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/soul.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/soul/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-limits.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-limits.html index 49ebcf4c7c0..895e067b068 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-limits.html +++ b/Master/texmf-doc/doc/english/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 @@ -15,18 +15,40 @@ difficult-to-read text). It is therefore common (in <code>\</code><code>textsty to place the limits as one would sub- and superscripts of variables. <p>This is not universally satisfactory, so the primitive <code>\</code><code>limits</code> is provided: +<blockquote> <pre> - $\sum\limits_{n=1}^{m} ...$ +$\sum\limits_{n=1}^{m} ...$ </pre> +</blockquote><p> which will place the limits right above and below the symbol (and be blowed to the typography...). <p>Contrariwise, you may wish to change the arrangement of the limits -when in <code>\</code><code>displaystyle</code>. For this purpose, there's a corresponding +when in <code>\</code><code>displaystyle</code>. For this purpose, there’s a corresponding <code>\</code><code>nolimits</code>: +<blockquote> <pre> - \[\sum\nolimits_{n=1}^{m} ...\] +\[\sum\nolimits_{n=1}^{m} ...\] </pre> +</blockquote><p> which will place the limits as they would be in <code>\</code><code>textstyle</code>. +<p>Alternatively, one can manipulate the +<code>\</code><code>textstyle</code>/<code>\</code><code>displaystyle</code> state of the mathematics. To get +“<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, +<code>\</code><code>nolimits</code>: +<blockquote> +<pre> +\[\textstyle\sum_{n=1}^{m} ...\] +</pre> +</blockquote><p> +will serve. Either of these forms may have effects other than on the +operator you’re considering, but there are still those who prefer this +formulation. <p>(Note that the macro <code>\</code><code>int</code> normally has <code>\</code><code>nolimits</code> built in to its definition. There is an example in the TeXbook to show how odd <code>\</code><code>int</code><code>\</code><code>limits</code> looks when typeset.) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linespace.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linespace.html index 7c8fcd08f22..922fe04f6c6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linespace.html +++ b/Master/texmf-doc/doc/english/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>linestretch{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-doc/doc/english/FAQ-en/html/FAQ-linespread.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linespread.html index cab6fe49698..a54af3c6b87 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linespread.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linespread.html @@ -1,37 +1,37 @@ <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> \fontsize{10}{12}% \selectfont </pre> -</blockquote> +</blockquote><p> or: <blockquote> <pre> \linespread{1.2}% \selectfont </pre> -</blockquote> +</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="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/setspace/setspace.sty">macros/latex/contrib/setspace/setspace.sty</a> </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-lit.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-lit.html index 8a8e144ae52..0fd057a21bd 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-lit.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-logos.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-logos.html index c0fd754edb1..0717bba5454 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-logos.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-logos.html @@ -5,20 +5,20 @@ <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 such as AMSTeX, PiCTeX, BibTeX, and so on, -produced in a flurry of different fonts, sizes, and baselines - indeed, +‘bumpy road’ logos such as AMSTeX, PiCTeX, BibTeX, and so on, +produced in a flurry of different fonts, sizes, and baselines — indeed, everything one might hope to cause them to obstruct the reading process. In particular, Lamport invented LaTeX - (silly enough in itself, with a raised small 'A' and a lowered 'E') + (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 LaTeX2e, which appends a lowered single-stroke Greek letter epsilon. -<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 @@ -28,9 +28,9 @@ use of the Knuthian font for MetaPost (you might get - something like 'META O T'). -You needn't despair, however - the author himself uses just 'MetaPost'. -<p>For those who don't wish to acquire the 'proper' logos, the canonical + something like ‘META O T’). +You needn’t despair, however — the author 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> @@ -38,9 +38,6 @@ for AMSTeX, <code>Pic</code><code>\</code><code>TeX</code> for PiCTeX, <code>Bib</code><code>\</code><code>TeX</code> for BibTeX, and so on. -<p>While the author of this FAQ list can't quite bring himself to do away -with the bumpy-road logos herein, he regularly advises everyone else -to... <dl> <dt><tt><i>mflogo.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mflogo.zip">macros/latex/contrib/mflogo</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mflogo.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mflogo/">browse</a>) <dt><tt><i>texnames.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/biblio/texnames.sty">info/biblio/texnames.sty</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-lollipop.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-lollipop.html index f7d16ef0e58..b1a4659f01c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-lollipop.html +++ b/Master/texmf-doc/doc/english/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 -<a href="FAQ-tutorials.html">(La)TeX Tutorials</a>). The manual says of +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 @@ -18,9 +18,9 @@ it: for environments where previously only WYSIWYG packages could be used because adapting the layout is so much more easy with them than with traditional TeX macro packages. -</blockquote> -<p>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 +</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 it taking over from LaTeX is detectable... An article about Lollipop appeared in <i>TUGboat</i> 13(3). diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-longtab.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-longtab.html index b602016ad82..d55fbe8226f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-longtab.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-longtab.html @@ -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 aligment +which is slightly tedious to set up, but which doesn’t force the whole aligment 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,37 +22,37 @@ 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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxabbrv.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxabbrv.html index 6442131ea76..0fba285df84 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxabbrv.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxabbrv.html @@ -1,25 +1,25 @@ <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\dots <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 -defined using an <code>\</code><code><em>xxx</em>def</code> command. +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> </tbody><tbody><tr><td> @@ -51,9 +51,9 @@ 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><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> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxabbrv">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxabbrv</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxcmds.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxcmds.html index 9acacea5c8b..40d9ce5bb68 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxcmds.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxcmds.html @@ -3,22 +3,23 @@ </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 taking commands from the terminal: <blockquote> <pre> +*\makeatletter *\show\protected@edef > \protected@edef=macro: ->\let \@@protect \protect \let \protect \@unexpandable@protect \afterassignment \restore@protect \edef . </pre> -</blockquote> -(I've rearranged the output there, from the rather confused version +</blockquote><p> +(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> @@ -27,8 +28,8 @@ TeX itself produces.) We may perhaps, now, wonder about > \@unexpandable@protect=macro: ->\noexpand \protect \noexpand . </pre> -</blockquote> -and we're starting to see how one part of the <code>\</code><code>protect</code>ion +</blockquote><p> +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: @@ -38,8 +39,8 @@ mechanism works (one can probably fairly safely guess what > \texttt=macro: ->\protect \texttt . </pre> -</blockquote> -so that <code>\</code><code>show</code> isn't much help. Define a command <code>\</code><code>pshow</code> as +</blockquote><p> +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> @@ -51,8 +52,8 @@ shown below, and use that instead: \ttfamily \check@icl #1\check@icr \expandafter \egroup \fi . </pre> -</blockquote> -Note that the command name that is protected is the 'base' command, +</blockquote><p> +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 @@ -65,38 +66,38 @@ 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> <pre> %%% From File: ltdefns.dtx </pre> -</blockquote> +</blockquote><p> When we come to look at it, <i>ltdefns.dtx</i> proves to contain quite a dissertation on the methods of handling <code>\</code><code>protect</code>ion; it also contains some automatically-converted LaTeX 2.09 documentation. -<p>And of course, the kernel isn'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: @@ -109,7 +110,7 @@ we find: %% %% classes.dtx (with options: `article') </pre> -</blockquote> +</blockquote><p> so we need to format <i>classes.dtx</i> to see the definition in context. <p>All these .dtx files are on CTAN as part of the main LaTeX diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxhash.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxhash.html new file mode 100644 index 00000000000..a733f758907 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxhash.html @@ -0,0 +1,55 @@ +<head> +<title>UK TeX FAQ -- question label ltxhash</title> +</head><body> +<h3>Defining LaTeX commands within other commands</h3> +<p>LaTeX command definition is significantly different from the TeX +primitive form discussed in an +<a href="FAQ-hash.html">earlier question</a> about definitions within +macros. +<p>In most ways, the LaTeX situation is simpler (at least in part +because it imposes more restrictions on the user); however, defining a +command within a command still requires some care. +<p>The earlier question said you have to double the <code>#</code> signs in command +definitions: in fact, the same rule holds, except that LaTeX +already takes care of some of the issues, by generating argument lists +for you. +<p>The basic problem is that: +<blockquote> +<pre> +\newcommand{\abc}[1]{joy, oh #1!% + \newcommand{\ghi}[1]{gloom, oh #1!}% +} +</pre> +</blockquote><p> +followed by a call: +<blockquote> +<pre> +\cmdinvoke{abc}{joy} +</pre> +</blockquote><p> +typesets “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) +the definition: +<blockquote> +<pre> +\newcommand{\abc}[1]{joy, oh #1!% + \newcommand{\ghi}[1]{gloom, oh ##1!}% +} +</pre> +</blockquote><p> +does what is required, and <code>\</code><code>ghi{gloom}</code> will expand to +“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> +<pre> +\newcommand{\abc}{joy, oh joy!% + \newcommand{\ghi}[1]{gloom, oh ##1!}% +} +</pre> +</blockquote><p> +is needed to produce a replica of the <code>\</code><code>ghi</code> we defined earlier. +<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxhash">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxhash</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-luatex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-luatex.html new file mode 100644 index 00000000000..762ace63127 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-luatex.html @@ -0,0 +1,21 @@ +<head> +<title>UK TeX FAQ -- question label luatex</title> +</head><body> +<h3>PDFTeX becomes LUATeX</h3> +<p>As is said elsewhere in these FAQs, development of +<a href="FAQ-whatpdftex.html">PDFTeX</a> is “in essence” complete — +development of new facilities continues, but the limitations of the +present structure impose a strong limit on what facilities are +possible. +<p>Thus arose the idea of LUATeX. LUA is a script +language, chosen because its interpreter has a very small +“footprint”, so it is rather easy to build it into other +applications. So LUATeX was launched as a PDFTeX +executable with a LUA interpreter built into it. +<p>The LUATeX project is now proceeding (with monetary support +from various sources) and is pursuing avenues that many of the other +current projects have in their sights, notably Unicode character +representations and support for OpenType fonts. Work is also in hand +to integrate the extensions pioneered by <a href="FAQ-omegaleph.html">Aleph</a>. +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=luatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=luatex</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-maillists.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-maillists.html deleted file mode 100644 index 3893884767c..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-maillists.html +++ /dev/null @@ -1,69 +0,0 @@ -<head> -<title>UK TeX FAQ -- question label maillists</title> -</head><body> -<h3>Where to get help</h3> -<p>First ... read any FAQ you can find. (Which is what you're -doing now, isn't it?) -<p>An ambitious FAQ-like project to collect all TeX-related -information into one place is under way at -<a href="http://algaba.sdf-eu.org/TeEncontreX/TeEncontreX.html">http://algaba.sdf-eu.org/TeEncontreX/TeEncontreX.html</a>; as with any -FAQ, this project needs the support and help of all users - -as yet, it carries an incomplete set of answers to potential -questions. The sources of the package (including a complete set of -<code>html</code> files) are available on CTAN -<p>The tutorials and other on-line documentation (see -<a href="FAQ-tutorials.html">(La)TeX Tutorials</a>) can get you started but -for more in-depth understanding you should get and read at least one of the -many good books on the subject -(see <a href="FAQ-books.html">TeX-related books</a>). The definitive source for -(La)TeX is the source code itself, but that is not something to be -approached lightly (if at all). -<p> If you are seeking a particular package or program, look on your own -system first: you might already have it - the better TeX -distributions contain a wide range of supporting material. -<p> If you have access to the internet, and in particular newsgroups, -then (La)TeX discussions, including Metafont and MetaPost, are on -<i>comp.text.tex</i>. -It is best to -spend a little time familiarising yourself with the current threads before -asking a question. The group is normally very responsive but asking a question -that has just been answered is likely to dampen people's enthusiasm to help -you. -<p><a href="http://groups.google.com/">http://groups.google.com/</a> archives Usenet news discussions, and -<i>comp.text.tex</i> may be found there. Google's archive now -goes impressively far back in time (before <i>comp.text.tex</i> -even existed), and it is a powerful resource for tracking down that -recommendation that no-one can now remember. Google also allows -you to post your own questions or followups. -<p>The few people who can't use the World Wide Web, can't access Usenet -news, but can use electronic mail can seek help through mailing lists. -<p>The TeXhax digest is nowadays operated as a -"<i>MailMan</i>" mailing list: its members now have the option -of receiving messages in 'real time', and answers are more quickly -forthcoming than ever they were in the past. Subscribe via -<a href="http://www.tug.org/mailman/listinfo/texhax">http://www.tug.org/mailman/listinfo/texhax</a>; archives back to -April 2000 are available via the same link, and earlier -digests are available on CTAN. -<p>Many mailing lists exist that cover some small part of the TeX -arena. A good source of pointers is <a href="http://www.tug.org/">http://www.tug.org/</a> -<p>Announcements of TeX-related installations on the CTAN -archives are sent to the mailing list <code>ctan-ann</code>. Subscribe -to the list via its <i>MailMan</i> web-site -<a href="https://sun.dante.de/mailman/listinfo/ctan-ann">https://sun.dante.de/mailman/listinfo/ctan-ann</a>; list archives -are available at the same address. The list archives may also be -browsed via <a href="http://www.mail-archive.com/ctan-ann@dante.de/">http://www.mail-archive.com/ctan-ann@dante.de/</a>, and -an RSS feed is also available: -<a href="http://www.mail-archive.com/ctan-ann@dante.de/maillist.xml">http://www.mail-archive.com/ctan-ann@dante.de/maillist.xml</a> -<p>Issues related to Metafont (and, increasingly, MetaPost) are discussed on -the <code>metafont</code> mailing list; subscribe by sending a message -'<code>subscribe metafont <<em>your name</em>></code>' to <a href="mailto:listserv@ens.fr"><i>listserv@ens.fr</i></a> -<p>A few other TeX-related lists may be accessed via -<a href="mailto:listserv@urz.uni-heidelberg.de"><i>listserv@urz.uni-heidelberg.de</i></a>. Send a message containing -the line '<code>help</code>' to this address, or browse -<a href="http://listserv.uni-heidelberg.de/cgi-bin/wa">http://listserv.uni-heidelberg.de/cgi-bin/wa</a> -<dl> -<dt><tt><i>TeEncontreX sources, etc.</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/spanish/TeEncontreX.zip">info/spanish/TeEncontreX</a> (<a href="ftp://cam.ctan.org/tex-archive/info/spanish/TeEncontreX.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/spanish/TeEncontreX/">browse</a>) -<dt><tt><i>TeXhax digests</i></tt><dd>Browse <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=maillists">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=maillists</a> -</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mailliststar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mailliststar.html new file mode 100644 index 00000000000..47afee4ea91 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mailliststar.html @@ -0,0 +1,32 @@ +<head> +<title>UK TeX FAQ -- question label maillists*</title> +</head><body> +<h3>Specialist mailing lists</h3> +<p>The previous question, “<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. +<p>The TUG web site offers many mailing lists other than just +<code>texhax</code> via its +<a href="http://tug.org/mailman/listinfo">mail list management page</a>. +<p>The French national TeX user group, Gutenberg, offers a Metafont (and, +de facto, MetaPost) mailing list, <a href="mailto:metafont@ens.fr"><i>metafont@ens.fr</i></a>: subscribe to +it by sending a message +<blockquote> +<pre> +subscribe metafont +</pre> +</blockquote><p> +to <a href="mailto:sympa@ens.fr"><i>sympa@ens.fr</i></a> +<p>Note that there’s also a MetaPost-specific mailing list available via the +TUG lists; 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 +to the list via its <i>MailMan</i> web-site +<a href="https://lists.dante.de/mailman/listinfo/ctan-ann">https://lists.dante.de/mailman/listinfo/ctan-ann</a>; list archives +are available at the same address. The list archives may also be +browsed via <a href="http://www.mail-archive.com/ctan-ann@dante.de/">http://www.mail-archive.com/ctan-ann@dante.de/</a>, and +an RSS feed is also available: +<a href="http://www.mail-archive.com/ctan-ann@dante.de/maillist.xml">http://www.mail-archive.com/ctan-ann@dante.de/maillist.xml</a> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=maillists*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=maillists*</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-make.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-make.html index 1e68e3dcda9..9b4efe95361 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-make.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-make.html @@ -4,30 +4,29 @@ <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>For this reason, the only <i>make</i>-like package on CTAN (for a long time) was <i>latexmk</i>, which is a <i>Perl</i> script that analyses your LaTeX source for its dependencies, runs BibTeX or <i>makeindex</i> as and when it notices that those -programs' input (parts of the <code>.aux</code> file, or the <code>.idx</code> file, +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. -<p>The -<a href="FAQ-texinfo.html"><i>texinfo</i> system</a> comes with a -utility called <i>texi2dvi</i>, which is capable of "converting" +man’s WYSIWYG system. +<p>The <a href="FAQ-texinfo.html"><i>texinfo</i> system</a> comes with a +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>FAQ distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.zip">help/uk-tex-faq</a> (<a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-makebib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-makebib.html index d4b1fd609dc..b22b0945c50 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-makebib.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-makebib.html @@ -2,21 +2,21 @@ <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... <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. <p>Documentation of the script is to be found in the file <i>tex2bib.readme</i> <dl> -<dt><tt><i>tex2bib</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/tex2bib/tex2bib">biblio/bibtex/contrib/tex2bib/tex2bib</a> -<dt><tt><i>tex2bib.readme</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/tex2bib/tex2bib.readme">biblio/bibtex/contrib/tex2bib/tex2bib.readme</a> +<dt><tt><i>tex2bib</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/tex2bib/tex2bib">biblio/bibtex/utils/tex2bib/tex2bib</a> +<dt><tt><i>tex2bib.readme</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/tex2bib/README">biblio/bibtex/utils/tex2bib/README</a> </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=makebib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=makebib</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-makeindex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-makeindex.html index 251a9cabbfa..4cb88a99c35 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-makeindex.html +++ b/Master/texmf-doc/doc/english/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> @@ -42,7 +42,7 @@ to be included into the document at the next run. <dt><tt><i>ltxindex.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ltxindex.zip">macros/latex/contrib/ltxindex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ltxindex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ltxindex/">browse</a>) <dt><tt><i>makeindex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/indexing/makeindex.zip">indexing/makeindex</a> (<a href="ftp://cam.ctan.org/tex-archive/indexing/makeindex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/indexing/makeindex/">browse</a>) <dt><tt><i>makeindex (Macintosh)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/mac/macmakeindex2.12.sea.hqx">systems/mac/macmakeindex2.12.sea.hqx</a> -<dt><tt><i>texindex (the script)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/texindex.zip">support/texindex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/texindex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/texindex/">browse</a>) +<dt><tt><i>texindex (the script)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/indexing/texindex.zip">indexing/texindex</a> (<a href="ftp://cam.ctan.org/tex-archive/indexing/texindex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/indexing/texindex/">browse</a>) <dt><tt><i>texindex (the program)</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/texinfo/texinfo.zip">macros/texinfo/texinfo</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/texinfo/texinfo.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/texinfo/texinfo/">browse</a>) <dt><tt><i>texsis (system)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/texsis.zip">macros/texsis</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/texsis.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/texsis/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-latex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-latex.html new file mode 100644 index 00000000000..82eb49440c1 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-latex.html @@ -0,0 +1,56 @@ +<head> +<title>UK TeX FAQ -- question label man-latex</title> +</head><body> +<h3>Online introductions: LaTeX</h3> +<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 also started as course +material) is a pleasing read. A complete copy may be found on +CTAN, but it may also be browsed over the web +(<a href="http://www.tex.ac.uk/tex-archive/info/beginlatex/html/">http://www.tex.ac.uk/tex-archive/info/beginlatex/html/</a>). +<p>Harvey Greenberg’s ‘Simplified Introduction to LaTeX’ was written +for a lecture course, and is also available on CTAN (in PostScript +only, unfortunately). +<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’ +<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> +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 +<a href="http://www.chrisharrison.co.uk/xophbook/mybooks/tex/index.html">TeX book</a> +presents basic LaTeX with useful hints for extensions +<p>Nicola Talbot’s +<a href="http://theoval.cmp.uea.ac.uk/~nlct/latex/novices/novices.html">LaTeX for complete novices</a> +does what it claims: the author teaches LaTeX at the University of +East Anglia. +<p>Nicola Talbot also provides a set of +<a href="http://theoval.cmp.uea.ac.uk/~nlct/latex/">introductory tutorials</a>, +which include exercises (with solutions). The page was developed as +an extension to the LaTeX course Nicola teaches at the University +of East Anglia. +<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 +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="ftp://cam.ctan.org/tex-archive/info/beginlatex/beginlatex-3.6.pdf">info/beginlatex/beginlatex-3.6.pdf</a> +<dt><tt><i>Not so Short Introduction</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/lshort/english/lshort.pdf">info/lshort/english/lshort.pdf</a> + (in English, you may browse for sources and other language versions at + <a href="http://www.tex.ac.uk/tex-archive/info/lshort/">info/lshort/</a>) +<dt><tt><i>Simplified LaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/simplified-latex/simplified-intro.ps">info/simplified-latex/simplified-intro.ps</a> + +<dt><tt><i>The sins of LaTeX users</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/l2tabu/english/l2tabuen.pdf">info/l2tabu/english/l2tabuen.pdf</a>; + source also available: <a href="ftp://cam.ctan.org/tex-archive/info/l2tabu/english/l2tabuen.tex">info/l2tabu/english/l2tabuen.tex</a> +</dl> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-latex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-latex</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-tex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-tex.html new file mode 100644 index 00000000000..284171ca500 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-tex.html @@ -0,0 +1,13 @@ +<head> +<title>UK TeX FAQ -- question label man-tex</title> +</head><body> +<h3>Online introductions: Plain TeX</h3> +<p>Michael Doob’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’, +available on the web at <a href="http://www.ntg.nl/doc/wilkins/pllong.pdf">http://www.ntg.nl/doc/wilkins/pllong.pdf</a> +<dl> +<dt><tt><i>Gentle Introduction</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/gentle/gentle.pdf">info/gentle/gentle.pdf</a> +</dl> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-tex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-tex</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-manyauthor.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-manyauthor.html index eb893f77ca1..18831b01224 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-manyauthor.html +++ b/Master/texmf-doc/doc/english/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 @@ -14,43 +14,43 @@ First Last Last, First Last, Suffix, First </pre> -</blockquote> -and lists of names should be separated with "<code>and</code>". +</blockquote><p> +and lists of names should be separated with “<code>and</code>”. For example: <blockquote> <pre> AUTHOR = {Fred Q. Bloggs, John P. Doe & - Robin Fairbairns} + Another Idiot} </pre> -</blockquote> +</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 & Robin Fairbairns Fred Q. Bloggs +John P. Doe & Another Idiot Fred Q. Bloggs </pre> -</blockquote> -because "John P. Doe & Robin Fairbairns" has become the 'first name', -while "Fred Q. Bloggs" has become the 'last name' of a single +</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 person. The example should have been written: <blockquote> <pre> AUTHOR = {Fred Q. Bloggs and John P. Doe and - Robin Fairbairns} + Another Idiot} </pre> -</blockquote> +</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> AUTHOR = {Fred Q. Bloggs and others} </pre> -</blockquote> +</blockquote><p> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manyauthor">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manyauthor</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-manymathalph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-manymathalph.html index 4c8721c8d5c..a0b87651471 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-manymathalph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-manymathalph.html @@ -5,34 +5,34 @@ <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</em>max</code> 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 +<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>Mathtime Plus</i>) that feature a heavy symbol weight, suppress all use of heavy families by <blockquote> <pre> \renewcommand{\hmmax}{0} </pre> -</blockquote> +</blockquote><p> and then steadily reduce the bold families, starting with <blockquote> <pre> \renewcommand{\bmmax}{3} </pre> -</blockquote> +</blockquote><p> until (with a bit of luck) the error goes away. <dl> <dt><tt><i>bm.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginmanual.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginmanual.html new file mode 100644 index 00000000000..ef5873fa7d8 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginmanual.html @@ -0,0 +1,46 @@ +<head> +<title>UK TeX FAQ -- question label marginmanual</title> +</head><body> +<h3>How to set up page layout “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 +LaTeX manual (pp. 181-182), or corresponding sections in many of the other +good LaTeX manuals (see <a href="FAQ-books.html">LaTeX books</a>). +<p>LaTeX controls the page layout with a number of parameters, which +allow you to change the distance from the edges of a page to the left +and top edges of your typeset text, the width and height of the text, +and the placement of other text on the page. However, they are +somewhat complex, and it is easy to get their interrelationships wrong +when redefining the page layout. The layout package defines a +<code>\</code><code>layout</code> command which draws a diagram of your existing page +layout, with the dimensions (but not their interrelationships) shown. +<p>Even changing the text height and width, <code>\</code><code>textheight</code> and +<code>\</code><code>textwidth</code>, requires more care than you might expect: the height +should be set to fit a whole number of text lines (in terms of +multiples of <code>\</code><code>baselinskip</code>), and the width should be constrained +by the number of characters per line, as mentioned in +“<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 +two-page spread and even-numbered pages on the left-hand side +(‘verso’). Both parameters actually refer to the left-hand margin of +the relevant pages; in each case the right-hand margin is specified by +implication, from the value of <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 +the paper and one inch from the left side; positive horizontal +measurements extend right across the page, and positive vertical +measurements extend down the page. Thus, the parameters +<code>\</code><code>evensidemargin</code>, <code>\</code><code>oddsidemargin</code> and <code>\</code><code>topmargin</code>, should +be set to be 1 inch less than the true margin; for margins closer to +the left and top edges of the page than 1 inch, the margin parameters +must be set to negative values. +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginmanual">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginmanual</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginparside.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginparside.html index 4ce7ed5082e..2a29ccbb504 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginparside.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginparside.html @@ -2,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 "analagous" places on +<p>In an ideal world, marginal notes would be in “analagous” 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-doc/doc/english/FAQ-en/html/FAQ-marginpkgs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginpkgs.html new file mode 100644 index 00000000000..e45539bf772 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginpkgs.html @@ -0,0 +1,30 @@ +<head> +<title>UK TeX FAQ -- question label marginpkgs</title> +</head><body> +<h3>Packages to set up page designs</h3> +<p>The ‘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 +comprehensive. +<p>As is usual, users of the <i>memoir</i> class have built-in +facilities for this task, and users of the <i>KOMA-script</i> classes +are recommended to use an alternative package, <i>typearea</i>. In +either case it is difficult to argue that users should go for +<i>geometry</i>: both alternatives are good. +<p>The documentation of <i>geometry</i> is a bit overwhelming, and +learning all its capabilities may be more than you ever need. +Somewhat simpler to use is the <i>vmargin</i> package, which has a +canned set of paper sizes (a superset of that provided in LaTeX2e), +provision for custom paper, margin adjustments and provision for +two-sided printing. +<dl> +<dt><tt><i>geometry.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/geometry.zip">macros/latex/contrib/geometry</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/geometry.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/geometry/">browse</a>) +<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) +<dt><tt><i>layout.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) +<dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) +<dt><tt><i>typearea.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) +<dt><tt><i>vmargin.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/vmargin.zip">macros/latex/contrib/vmargin</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/vmargin.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/vmargin/">browse</a>) +</dl> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginpkgs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginpkgs</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-matchbrak.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-matchbrak.html new file mode 100644 index 00000000000..efcbf4da21c --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-matchbrak.html @@ -0,0 +1,57 @@ +<head> +<title>UK TeX FAQ -- question label matchbrak</title> +</head><body> +<h3>My brackets don’t match</h3> +<p>(La)TeX has a low-level mechanism for matching braces in document +text. This means you can type something like: +<blockquote> +<pre> +\section{All \emph{OK} now.} +</pre> +</blockquote><p> +and know that the first brace (for the argument of <code>\</code><code>section</code>) will +be matched with the last brace, and the internal pair of braces (for +the argument of <code>\</code><code>emph</code>) will be matched with each other. It’s all +very simple. +<p>However, LaTeX has a convention of enclosing optional arguments in +brackets, as in: +<blockquote> +<pre> +\section[OK]{All \emph{OK} now.} +</pre> +</blockquote><p> +These brackets are not matched by TeX mechanisms, despite the +superficial similarity of their use. As a result, +straightforward-looking usages like: +<blockquote> +<pre> +\section[All [OK] now]{All \emph{OK} now.} +</pre> +</blockquote><p> +aren’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> +<pre> +\section[All {[OK]} now]{All \emph{OK} now.} +</pre> +</blockquote><p> +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> +<pre> +\put(1,2){foo} +</pre> +</blockquote><p> +(a picture environment command). +<p>This mechanism is also prone to problems with matching closing +parentheses, but the issue seldom arises since such arguments rarely +contain text. If it were to arise, the same solution (enclosing the +confused characters in braces) would solve the problem. +<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=matchbrak">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=matchbrak</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathlips.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathlips.html index 685c1948c18..8c40ce88519 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathlips.html +++ b/Master/texmf-doc/doc/english/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 @@ -37,7 +37,7 @@ before being able to read the documentation). Documentation of <dl> <dt><tt><i>amslatex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>) <dt><tt><i>graphics.sty</i></tt><dd>Part of the <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) bundle -<dt><tt><i>mathdots.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/mathdots.sty">macros/generic/mathdots.sty</a> +<dt><tt><i>mathdots.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/mathdots.zip">macros/generic/mathdots</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/generic/mathdots.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/generic/mathdots/">browse</a>) <dt><tt><i>yhmath (fonts)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/yhmath.zip">fonts/yhmath</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/yhmath.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/yhmath/">browse</a>) <dt><tt><i>yhmath (macros)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/yhmath.zip">macros/latex/contrib/yhmath</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/yhmath.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/yhmath/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathml.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathml.html index 4bbcb9c0731..d932b1f0b89 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathml.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathml.html @@ -1,9 +1,9 @@ <head> <title>UK TeX FAQ -- question label mathml</title> </head><body> -<h3>Future WEB technologies and (La)TeX</h3> +<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 plugin 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> @@ -78,12 +78,12 @@ support for new Web standards. 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/mimetex.html">MimeTeX</a>, which sits on your server as a CGI script, and you use it to include @@ -93,7 +93,7 @@ support for new Web standards. <img src="../cgi-bin/mimetex.cgi?f(x)=\int\limits_{-\infty}^xe^{-t^2}dt"> </pre> -</blockquote> +</blockquote><p> </dl> <dl> <dt><tt><i>GELLMU</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/gellmu.zip">support/gellmu</a> (<a href="ftp://cam.ctan.org/tex-archive/support/gellmu.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/gellmu/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathsize.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathsize.html index 5c4b2c83304..a8942dfa9a8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathsize.html +++ b/Master/texmf-doc/doc/english/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-tutorials.html">tutorials</a> that discuss Plain TeX in sufficient +<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> @@ -38,16 +38,16 @@ alternatives. In this case, you might use: <pre> \DeclareMathSizes{10}{9}{7}{5} </pre> -</blockquote> +</blockquote><p> to get 9pt maths when the surrounding body text is (nominal) 10pt. <p><code>\</code><code>DeclareMathSizes</code> may only be used in the preamble of the document: only one association is available for each text font size for the whole document. The default settings are specified in <i>fontdef.dtx</i> in the latex distribution, and are compiled into <i>fontmath.ltx</i>; the arguments to the command are just numbers -('<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-doc/doc/english/FAQ-en/html/FAQ-mathstext.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathstext.html index f6aaf76bb0d..91241a4f485 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathstext.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathstext.html @@ -4,59 +4,59 @@ <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> <pre> $e = mc^2 \mbox{here we go again}$ </pre> -</blockquote> +</blockquote><p> The problem is that, with either, the size of the text remains firmly at the surrounding text size, so that <blockquote> <pre> $z = a_{\mbox{other end}}$ </pre> -</blockquote> +</blockquote><p> looks quite painfully wrong. <p>The other simple technique, <code>\</code><code>textrm</code>, is more promising: <blockquote> <pre> $z = a_{\textrm{other end}}$ </pre> -</blockquote> +</blockquote><p> is definitely right. However, the surrounding text may not be in your roman font; if you care about matching text, you need to choose between <code>\</code><code>textrm</code>, <code>\</code><code>textsf</code>, and so on. <p>(The maths-mode instance of your roman font (<code>\</code><code>mathrm</code>) gets the -size right, but since it'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> <pre> $z = a_{\mbox{\scriptsize other end}}$ </pre> -</blockquote> +</blockquote><p> which works if your surrounding text is at default document size, but gives you the wrong size otherwise. -<p>These short cuts are (just about) OK for the "occasional" +<p>These short cuts are (just about) OK for the “occasional” mathematician, but serious mathematics calls for a technique that relieves the typist of the sort of thought required. As usual, the -AMSLaTeX system provides what's necessary - the <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, so +package, but the “global” <i>amsmath</i> package loads it, so anyone using AMSLaTeX proper has the command available, so even joke mathematicians can write: <blockquote> @@ -65,7 +65,7 @@ joke mathematicians can write: ... $z = a_{\text{other end}}$ </pre> -</blockquote> +</blockquote><p> and the text will be at the right size, and in the same font as surrounding text. <p>AMSLaTeX also makes provision for interpolated comments in the @@ -80,8 +80,8 @@ middle of one of its multi-line display structures, through the \intertext{and} A_3&=\mathcal{N}(\lambda;\omega). \end{align} </pre> -</blockquote> -places the text "and" on a separate line before the last line of the +</blockquote><p> +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> @@ -94,9 +94,9 @@ command from the <i>mathtools</i> package: c =& b \end{align} </pre> -</blockquote> +</blockquote><p> To have the text on the same line as the second equation, one can use -the the <code>flalign</code> environment (from <i>amsmath</i>) +the <code>flalign</code> environment (from <i>amsmath</i>) with lots of dummy equations (represented by the double <code>&</code> signs): <blockquote> @@ -106,7 +106,7 @@ signs): \text{or} && c =& b && \end{flalign} </pre> -</blockquote> +</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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcfloat.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcfloat.html index 740ede66470..7f8679ff342 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcfloat.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcfloat.html @@ -3,24 +3,28 @@ </head><body> <h3>Floats in multicolumn setting</h3> <p>If you use +<blockquote> <pre> \begin{figure} ... \end{figure} </pre> -in a <code>multicols</code> environment, the figure won't appear. If +</blockquote><p> +in a <code>multicols</code> environment, the figure won’t appear. If instead you use +<blockquote> <pre> \begin{figure*} ... \end{figure*} </pre> +</blockquote><p> the figure will stretch right across the page (just the same as a -<code>figure*</code> in standard LaTeX'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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcite.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcite.html index b32edcf83d1..e02dd602bc6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcite.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcite.html @@ -2,34 +2,34 @@ <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> package deals with the problem. <p>The package 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> +</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> -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 +</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 paper 3. <p>You need to make a small change to the bibliography style (<code>.bst</code>) file you use; the <i>mcite</i> package documentation tells you how to do that. -<p>Unfortunately, the <i>revtex</i> system doesn't play with +<p>Unfortunately, the <i>revtex</i> system doesn’t play with <i>mcite</i>. As a result, for that (primarily physics-targeted system) you need to play silly games like: <blockquote> @@ -37,7 +37,7 @@ system) you need to play silly games like: \cite{paper0,paper1,paper3} \nocite{paper2} </pre> -</blockquote> +</blockquote><p> and then edit the <code>.bbl</code> file to merge the two citations, to achieve the effects of <i>mcite</i>. <dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-metrics.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-metrics.html index ce965f8bca5..cddb11091c1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-metrics.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-mfptutorials.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mfptutorials.html index 146415531c6..3f4843658ea 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mfptutorials.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mfptutorials.html @@ -2,43 +2,48 @@ <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 fonts for any text or mathematics. <p>Hans Hagen (of ConTeXt fame) offers a MetaPost tutorial called -MetaFun (which admittedly concentrates on the use of MetaPost within ConTeXt). It may be found on his company's +MetaFun (which admittedly concentrates on the use of MetaPost within +ConTeXt). It may be found on his company’s <a href="http://www.pragma-ade.com/metapost.htm">MetaPost page</a>. -<p>Other MetaPost tutorials that have appeared are one in English by -<a href="http://remote.science.uva.nl/~heck/Courses/mptut.pdf">André Heck</a>, -and one in French (listed here because it's clearly enough written +<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> +and <a href="http://www.tlhiv.org/MetaPost/tutorial/">Urs Oswald</a>, +and one in French (listed here because it’s clearly enough written that this author understands it), by <a href="http://pauillac.inria.fr/~cheno/metapost/metapost.pdf">Laurent Chéno</a>; both have been recommended for inclusion in the FAQ -<p>Vincent Zoonekynd's massive set of example MetaPost files is available on +<p>Urs Oswald’s tutorial is accompanied by a super tool for testing +little bits of MetaPost, which is an invaluable aid to the learner: +<a href="http://www.tlhiv.org/cgi-bin/MetaPostPreviewer/index.cgi">http://www.tlhiv.org/cgi-bin/MetaPostPreviewer/index.cgi</a> +<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="ftp://cam.ctan.org/tex-archive/info/metafont-for-beginners.tex">info/metafont-for-beginners.tex</a> -<dt><tt><i>Peter Wilson's "experiences"</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/metafp.ps">info/metafp.ps</a> - (PostScript) or <a href="ftp://cam.ctan.org/tex-archive/info/metafp.pdf">info/metafp.pdf</a> (PDF format) -<dt><tt><i>Vincent Zoonekynd's examples</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/metapost/examples.zip">info/metapost/examples</a> (<a href="ftp://cam.ctan.org/tex-archive/info/metapost/examples.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/metapost/examples/">browse</a>) +<dt><tt><i>Beginners’ guide</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/metafont/beginners/metafont-for-beginners.pdf">info/metafont/beginners/metafont-for-beginners.pdf</a> +<dt><tt><i>Peter Wilson’s “experiences”</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/metafont/metafp/metafp.pdf">info/metafont/metafp/metafp.pdf</a> + (PDF format) +<dt><tt><i>Vincent Zoonekynd’s examples</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/metapost/examples.zip">info/metapost/examples</a> (<a href="ftp://cam.ctan.org/tex-archive/info/metapost/examples.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/metapost/examples/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mfptutorials">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mfptutorials</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-miktexinst.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-miktexinst.html index 2c922009992..3856b06b125 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-miktexinst.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-miktexinst.html @@ -1,30 +1,39 @@ <head> <title>UK TeX FAQ -- question label miktexinst</title> </head><body> -<h3>Installing MiKTeX "known packages"</h3> -<p>MiKTeX 2.1 (and later) maintains a database of packages it "knows about", +<h3>Installing MiKTeX “known packages”</h3> +<p>MiKTeX 2.1 (and later) maintains a database of packages it “knows about”, together with (coded) installation instructions that enable it to install the packages with minimal user intervention. -<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. <p>First, open the MiKTeX packages window: click on <code>Start</code>-> <code>Programs</code>-> - <code>MikTeX</code>-> - <code>MikTeX Options</code>, and select the + <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 MiKTeX <em>doesn't</em> know about the package you're interested +<p>If you prefer a command-line utility, there’s <i>mpm</i>. Open a +command shell, and type: +<blockquote> +<pre> +mpm --install=<package> +</pre> +</blockquote><p> +(which of course assumes you know the name by which MiKTeX refers to +your package). +<p>If MiKTeX <em>doesn’t</em> know about the package you’re interested in, you have to use the <a href="FAQ-instpackages.html">long-winded procedure</a> outlined elsewhere in this FAQ. <p>If necessary, repeat to select other packages, and then press -"<code>OK</code>"; MiKTeX tells you how many packages you have -selected - if you're happy, press "<code>OK</code>" again. +“<code>OK</code>”; MiKTeX tells you how many packages you have +selected — if you’re happy, press “<code>OK</code>” again. MiKTeX will go off, download the package (as a <code>.cab</code> file), if necessary, install the files of the package, and then refresh the filename database so that the files will be found. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minitoc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minitoc.html index 44a7c193aa7..751599a1d3a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minitoc.html +++ b/Master/texmf-doc/doc/english/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> @@ -17,21 +17,22 @@ would be: ... \begin{document} ... -\tableofcontents -\dominitoc \listoffigures \dominilof ... +\dominitoc \tableofcontents +\dominilof \listoffigures +... \chapter{blah blah} -\minitoc \mtcskip \minilof ... +\minitoc \mtcskip \minilof +... </pre> -</blockquote> -though a lot of elaborations are possible (for example, you don't need +</blockquote><p> +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. However, current versions of -the <i>hyperref</i> package will treat <code>\</code><code>minitoc</code> tables in the -same way as "real" tables of contents. -<p>The documentation is pretty extensive and readable: process the file -<i>minitoc.tex</i> in the distribution +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. <dl> <dt><tt><i>babel.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/babel.zip">macros/latex/required/babel</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/babel.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/babel/">browse</a>) <dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minxampl.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minxampl.html index 1f75e25484c..ee4750a9437 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minxampl.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minxampl.html @@ -1,21 +1,22 @@ <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" 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. <p>There are two valid approaches to this task: building up, and hacking down. -<p>The "building up" process starts with a basic document structure +<p>The “building up” process starts with a basic document structure (for LaTeX, this would have <code>\</code><code>documentclass</code>, <code>\</code><code>begin{document}</code>, <code>\</code><code>end{document}</code>) and adds things. First to add is a paragraph or so around the actual point where the problem occurrs. (It may prove difficult to find the actual -line that's provoking the -problem. If the original problem is an error, reviewing +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> may help.) <p>Note that there are things that can go wrong in one part of the @@ -24,29 +25,30 @@ 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 collapses already, then you're done. +<p>If this file you’ve built up collapses 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 only works at all with another package loaded (or only fails in the context of another package). -<p>The "hacking down" route starts with your entire document, and +<p>The “hacking down” route 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 -unneccessary packages, but mostly, the difficulty is choosing what to +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), run your minimum file -with <code>\</code><code>listfiles</code> enabled, so as to report which versions of packages -you're using. -<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 +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 +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 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 @@ -55,13 +57,13 @@ 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.latex-einfuehrung.de/mini-en.html">http://www.latex-einfuehrung.de/mini-en.html</a>; source of the +<a href="http://www.latex-einfuehrung.de/mini-en.html">http://www.latex-einfuehrung.de/mini-en.html</a>; source of that article may be found at <a href="http://www.latex-einfuehrung.de/">http://www.latex-einfuehrung.de/</a>, in both German and English. <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=minxampl">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=minxampl</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missbegdoc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missbegdoc.html index 0e4016a249f..7a7e314c89c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missbegdoc.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-misschar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-misschar.html index 7db35f127c9..18f8a22bfe7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-misschar.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-misschar.html @@ -2,26 +2,26 @@ <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 £ 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! Missing character: There is no 3 in font rsfs10! </pre> -</blockquote> -(the former demonstrating my TeX's unwillingness to deal in characters +</blockquote><p> +(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 @@ -30,11 +30,11 @@ fonts that were supplied in Adobe standard encoding: <pre> dvips: Warning: missing glyph `Delta' </pre> -</blockquote> +</blockquote><p> The process that generates the metrics for using the fonts generates an instruction to <i>dvips</i> to produce these diagnostics, so that their non-appearance in the printed output is less surprising -than it might be. Quite a few glyphs provided in Knuth'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-doc/doc/english/FAQ-en/html/FAQ-missssymb.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missssymb.html index 4f0ec4e6f8e..48cbe402dd2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missssymb.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missssymb.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label missssymb</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-doc/doc/english/FAQ-en/html/FAQ-moren9.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-moren9.html index 5c4b441e021..37f93400467 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-moren9.html +++ b/Master/texmf-doc/doc/english/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>} </pre> -</blockquote> -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? +</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? <p>If you really must have more than 9 arguments, the way to go is: <blockquote> <pre> @@ -30,12 +30,12 @@ the syntax didn't gobble some other valid usage? <macro body>% } </pre> -</blockquote> +</blockquote><p> This technique is easily extendible by concert pianists of the TeX keyboard, but is really hard to recommend. <p>LaTeX users have the small convenience of merely giving a number of arguments in the <code>\</code><code>newcommand</code> that defines each part of the -relaying mechanism: Knuth'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 @@ -52,9 +52,9 @@ like: soiltype=alkaline } </pre> -</blockquote> +</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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mpprologues.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mpprologues.html index 23a5dd9ab39..aff6d6e4f29 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mpprologues.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mpprologues.html @@ -1,31 +1,31 @@ <head> <title>UK TeX FAQ -- question label mpprologues</title> </head><body> -<h3>Making MetaPost output display in <i>ghostscript</i></h3> +<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 eperience an error such +the PostScript ‘engine’ in <i>ghostscript</i> <em>doesn’t</em> +ordinarily have the fonts loaded, and you’ll eperience an error such as <blockquote> <pre> Error: /undefined in cmmi10 </pre> -</blockquote> +</blockquote><p> There is provision in MetaPost for avoiding this problem: issue the command <code>prologues := 2;</code> at the start of the <code>.mp</code> file. <p>Unfortunately, the PostScript that MetaPost inserts in its output, following this command, is incompatible with ordinary use of the -PostScript in inclusions into (La)TeX documents, so it'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 @@ -35,14 +35,14 @@ by inputting <i>MyFigure.mp</i> indirectly from a simple wrapper prologues := 2; input MyFigure </pre> -</blockquote> +</blockquote><p> or by issuing a shell command such as <blockquote> <pre> mp '\prologues:=2; input MyFigure' </pre> -</blockquote> -(which will work without the quote marks if you're not using a Unix +</blockquote><p> +(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: @@ -55,19 +55,19 @@ shell). \includegraphics{MyFigure.1} \end{document} </pre> -</blockquote> +</blockquote><p> Processing the resulting DVI file with the <i>dvips</i> command <blockquote> <pre> dvips -E -o MyFigure.eps MyFigure </pre> -</blockquote> +</blockquote><p> would then give a satisfactory Encapsulated PostScript file. This procedure may be automated using the <i>Perl</i> script <i>mps2eps</i>, thus saving a certain amount of tedium. -<p>The Plain TeX user may use an adaptation of a jiffy of Knuth'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. @@ -78,6 +78,7 @@ the question... <dl> <dt><tt><i>mps2eps</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/mps2eps.zip">support/mps2eps</a> (<a href="ftp://cam.ctan.org/tex-archive/support/mps2eps.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/mps2eps/">browse</a>) <dt><tt><i>mpsproof.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/metapost/contrib/misc/mpsproof.tex">graphics/metapost/contrib/misc/mpsproof.tex</a> +<dt><tt><i>mptopdf</i></tt><dd>Part of <a href="ftp://cam.ctan.org/tex-archive/macros/pdftex/graphics.zip">macros/pdftex/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/pdftex/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/pdftex/graphics/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mpprologues">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mpprologues</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-msxy.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-msxy.html index 1a22fb49372..3122c0f19e0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-msxy.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-msxy.html @@ -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-doc/doc/english/FAQ-en/html/FAQ-multbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multbib.html index df0dcc6d6bd..1aa4eb9eeca 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multbib.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multbib.html @@ -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 @@ -32,10 +32,10 @@ section or chapter (i.e., it patches \bibliography{bk}{book-bib}{References to books} \bibliography{art}{art-bib}{References to articles} </pre> -</blockquote> +</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 @@ -44,11 +44,11 @@ may list the same set of files.) bibtex bk bibtex art </pre> -</blockquote> +</blockquote><p> after the first run of LaTeX, to get the citations in the correct place. <p>The <i>multibib</i> package allows you to define a series of -"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> @@ -66,7 +66,7 @@ bibliography commands. So one might write: \bibliographybk{book-bib} \bibliographyart{art-bib} </pre> -</blockquote> +</blockquote><p> Again, as for <i>multibbl</i>, any <code>\</code><code>bibliography...</code> command may scan any list of <code>.bib</code> files. <p>BibTeX processing with <i>multibib</i> is much like that with @@ -76,9 +76,9 @@ scan any list of <code>.bib</code> files. bibtex bk bibtex art </pre> -</blockquote> +</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 @@ -102,7 +102,7 @@ bibliographies. Thus, one might have a file <i>diss.tex</i> containing: \btPrintCited \end{btSect} </pre> -</blockquote> +</blockquote><p> Note the different way of specifying a bibliographystyle: if you want a different style for a particular bibliography, you may give it as an optional argument to the <code>btSect</code> environment. @@ -114,13 +114,13 @@ you need to say: bibtex diss1 bibtex diss2 </pre> -</blockquote> +</blockquote><p> <p>There is also a command <code>\</code><code>btPrintNotCited</code>, which gives the rest of the content of the database (if nothing has been cited from the database, this is equivalent to LaTeX standard <code>\</code><code>nocite{*}</code>). <p>However, the <em>real</em> difference from <i>miltibbl</i> and <i>mltibib</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>thebibliograph</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-doc/doc/english/FAQ-en/html/FAQ-multidoc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multidoc.html index 5e6061e687e..60166cabfaa 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multidoc.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multidoc.html @@ -1,12 +1,12 @@ <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 @@ -17,14 +17,21 @@ project, and the corresponding <i>subfiles</i> is used in the master file; arrangements may be made so that the component files will be typeset using different page format, etc., parameters than those used when they are typeset as a part of the main file. -<p>A more 'raw' toolkit is offered by Matt Swift's <i>includex</i> and -<i>moredefs</i> packages, both part of the <i>frankenstein</i> -bundle) offer a possible way forward. -<p><i>Includex</i> enables 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). It doesn't do the whole job for you, though. You need to +<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 +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 +(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 analyse the package use of the individual papers, and ensure that a -consistent set is loaded in the preamble of the main report. +consistent set is loaded in the preamble of the main report. (Both +packages require <i>moredefs</i>, which is also part of the bundle.) <p>A completely different approach is to use the <i>pdfpages</i> package, and to include articles submitted in PDF format into a a PDF document produced by PDFLaTeX. The package @@ -36,9 +43,10 @@ of the included pages. <dl> <dt><tt><i>combine.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/combine.zip">macros/latex/contrib/combine</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/combine.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/combine/">browse</a>) <dt><tt><i>combinet.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/combine.zip">macros/latex/contrib/combine</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/combine.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/combine/">browse</a>) -<dt><tt><i>includex.sty</i></tt><dd>Distributed in the "unsupported" part of +<dt><tt><i>includex.sty</i></tt><dd>Distributed in the “unsupported” part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/frankenstein.zip">macros/latex/contrib/frankenstein</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/frankenstein.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein/">browse</a>) <dt><tt><i>moredefs.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/frankenstein.zip">macros/latex/contrib/frankenstein</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/frankenstein.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein/">browse</a>) +<dt><tt><i>newclude.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/frankenstein.zip">macros/latex/contrib/frankenstein</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/frankenstein.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/frankenstein/">browse</a>) <dt><tt><i>pdfpages.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdfpages.zip">macros/latex/contrib/pdfpages</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdfpages.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdfpages/">browse</a>) <dt><tt><i>subfiles.cls, etc.</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/subfiles.zip">macros/latex/contrib/subfiles</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/subfiles.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/subfiles/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multind.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multind.html index 032560db89d..5bd54ce8209 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multind.html +++ b/Master/texmf-doc/doc/english/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,25 +11,25 @@ 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} \makeindex{general} \makeindex{authors} ... -\index{authors}{Robin Fairbairns} +\index{authors}{Another Idiot} ... \index{general}{FAQs} ... \printindex{general}{General index} \printindex{authors}{Author index} </pre> -</blockquote> +</blockquote><p> To complete the job, run LaTeX on your file enough times that labels, etc., are stable, and then execute the commands <blockquote> @@ -37,39 +37,39 @@ labels, etc., are stable, and then execute the commands makeindex general makeindex authors </pre> -</blockquote> +</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...) <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} \makeindex \newindex{aut}{adx}{and}{Name Index} </pre> -</blockquote> -which load the package, define a "main" (original-style) index, and +</blockquote><p> +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> <pre> -\index[aut]{Robin Fairbairns} +\index[aut]{Another Idiot} ... \index{FAQs} </pre> -</blockquote> +</blockquote><p> Which place an entry in the author index, and then one in the main index. At the end of the document, we have two commands: <blockquote> @@ -77,18 +77,18 @@ index. At the end of the document, we have two commands: \printindex \printindex[aut] </pre> -</blockquote> +</blockquote><p> Which will print the main index and then the author index. Supposing this lot to be in <i>myfile.tex</i>, after enough runs through LaTeX that labels are stable, execute the following commands (Unix-style shell commands shown here, but the principle is the same -whatever system you're using): +whatever system you’re using): <blockquote> <pre> makeindex myfile makeindex myfile.adx -o myfile.and </pre> -</blockquote> +</blockquote><p> and rerun LaTeX. The <i>makeindex</i> commands process <i>myfile.idx</i> to <i>myfile.ind</i> (the default action), and then <i>myfile.adx</i> to <i>myfile.and</i>, the two files needed as input @@ -98,15 +98,15 @@ others: load the package with the <code>split</code> option, and declare each index with a <code>\</code><code>newindex</code> command: <blockquote> <code>\</code><code>newindex[<<i>index name</i>>]{<<i>shortcut</i>>}</code> -</blockquote> +</blockquote><p> 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-doc/doc/english/FAQ-en/html/FAQ-multirow.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multirow.html index e6b53773444..525c9da51c0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multirow.html +++ b/Master/texmf-doc/doc/english/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 @@ -16,7 +16,7 @@ might write: <pre> \begin{tabular}{|c|c|} \hline -\multirow{4}*{Common g text} +\multirow{4}{*}{Common g text} & Column g2a\\ & Column g2b \\ & Column g2c \\ @@ -24,12 +24,12 @@ might write: \hline \end{tabular} </pre> -</blockquote> -and <i>multirow</i> will position "Common g text" at the vertical +</blockquote><p> +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> @@ -43,7 +43,7 @@ case, the argument may contain forced line-breaks: \hline \end{tabular} </pre> -</blockquote> +</blockquote><p> A similar effect (with the possibility of a little more sophistication) may be achieved by putting a smaller table that lines up the text into a <code>*</code>-declared <code>\</code><code>multirow</code>. @@ -55,7 +55,7 @@ down one or other side of a table (with the help of the <pre> \begin{tabular}{|l|l|} \hline -\multirow{4}*{\rotatebox{90}{hi there}} +\multirow{4}{*}{\rotatebox{90}{hi there}} & Column g2a\\ & Column g2b \\ & Column g2c \\ @@ -63,10 +63,27 @@ down one or other side of a table (with the help of the \hline \end{tabular} </pre> -</blockquote> +</blockquote><p> (which gives text going upwards; use angle <code>-90</code> for text going downwards, of course). -<p><i>Multirow</i> is set up to interact with the <i>bigstrut</i> +<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> +\begin{tabular}{|c|c|c|}\hline +\multicolumn{2}{|c|}{\multirow{2}{*}{combined cells}} + &top right\\ \cline{3-3} +\multicolumn{2}{|c|}{} + &middle right\\ \hline +bottom left + &bottom center + &bottom right\\ \hline +\end{tabular} +</pre> + +</blockquote><p> +<i>Multirow</i> is set up to interact with the <i>bigstrut</i> package (which is also discussed in the answer to <a href="FAQ-struttab.html">spacing lines in tables</a>). You use an optional argument to the <code>\</code><code>multirow</code> command to say how many of the diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-music.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-music.html index 7316ca8358e..0080a30db78 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-music.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-music.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label music</title> </head><body> <h3>Typesetting music in TeX</h3> -<p>In the early days, a simple music package called <i>mutex</i> was +<p>In the early days, a simple music package called MuTeX was written by Angelika Schofer and Andrea Steinbach, which demonstrated -that music typesetting was possible; the package was very limited, and -is no longer available. Daniel Taupin took up the baton, and +that music typesetting was possible; the package was very limited, and is +hardly ever used nowadays. Daniel Taupin took up the baton, and developed MusicTeX, which allows the typesetting of polyphonic and other multiple-stave music; MusicTeX remains available, but is most definitely no longer recommended. @@ -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 @@ -33,20 +33,28 @@ which can be written on one stave in standard classical notation, and creates input intended for MusicTeX. However, it should be extendable to many other types of music. <p>Digital music fans can typeset notation for their efforts by using -<i>midi2tex</i>, which translates MIDI data files into MusicTeX -source code. +<i>midi2tex</i>, which translates MIDI data files into +MusicTeX source code. <p>There is a mailing list (<i>TeX-music@icking-music-archive.org</i>) -for discussion of typesetting music in TeX. To subscribe, use +for discussion of typesetting music in TeX; it mostly covers +MusixTeX and related systems. To subscribe, use <a href="http://icking-music-archive.org/mailman/listinfo/tex-music/">http://icking-music-archive.org/mailman/listinfo/tex-music/</a> +<p>An alternative (free) means of embedding music examples into (La)TeX +documents is <a href="http://www.lilypond.org">Lilypond</a>. Lilypond is +(at heart) a batch music typesetting system with plain text input that +does most of its work without TeX. Lilypond’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> <dt><tt><i>abc2mtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/abc2mtex.zip">support/abc2mtex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/abc2mtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/abc2mtex/">browse</a>) <dt><tt><i>M-Tx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/mtx.zip">support/mtx</a> (<a href="ftp://cam.ctan.org/tex-archive/support/mtx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/mtx/">browse</a>) <dt><tt><i>midi2tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/midi2tex.zip">support/midi2tex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/midi2tex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/midi2tex/">browse</a>) <dt><tt><i>musictex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/musictex.zip">macros/musictex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/musictex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/musictex/">browse</a>) -<li>[musixtex (Taupin's - version)]<a href="ftp://cam.ctan.org/tex-archive/macros/musixtex/taupin.zip">macros/musixtex/taupin</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/musixtex/taupin.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/musixtex/taupin/">browse</a>) -<li>[musixtex (Egler's - version)]<a href="ftp://cam.ctan.org/tex-archive/macros/musixtex/egler.zip">macros/musixtex/egler</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/musixtex/egler.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/musixtex/egler/">browse</a>) + +<dt><tt><i>musixtex (Taupin’s version)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/musixtex/taupin.zip">macros/musixtex/taupin</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/musixtex/taupin.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/musixtex/taupin/">browse</a>) +<dt><tt><i>musixtex (Egler’s version)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/musixtex/egler.zip">macros/musixtex/egler</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/musixtex/egler.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/musixtex/egler/">browse</a>) +<dt><tt><i>mutex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/mtex.zip">macros/mtex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/mtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/mtex/">browse</a>) <dt><tt><i>pmx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/pmx.zip">support/pmx</a> (<a href="ftp://cam.ctan.org/tex-archive/support/pmx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/pmx/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=music">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=music</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nameref.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nameref.html index 4631d975370..29a8976f320 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nameref.html +++ b/Master/texmf-doc/doc/english/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>, @@ -30,12 +30,12 @@ course, in this mode its references are not hyperlinked). If you load \usepackage[...]{hyperref} \usepackage{memhfixc} </pre> -</blockquote> +</blockquote><p> <i>nameref</i> commands may be used in a <i>memoir</i> document. <p>Each of the name-reference packages 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 +<code>\</code><code>byshortnameref</code>, which uses the optional ‘short’ title argument to the chapter and section commands. <dl> <dt><tt><i>byname.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smartref.zip">macros/latex/contrib/smartref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smartref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/smartref/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newans.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newans.html index b69d66f5edb..ea46571a378 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newans.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newans.html @@ -5,23 +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 -to the <a href="mailto:faq@tex.ac.uk">maintainers</a>. +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="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.zip">help/uk-tex-faq</a> (<a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfont.html new file mode 100644 index 00000000000..0feb24ebd15 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfont.html @@ -0,0 +1,57 @@ +<head> +<title>UK TeX FAQ -- question label newfont</title> +</head><body> +<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 +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 suffers from exactly the +problems with font encodings and sizes that are outlined in +<a href="FAQ-plninltx.html">using Plain TeX commands in \LaTeX</a>. +<p>Almost all fonts, nowadays, are provided with LaTeX control files +(if they’re adapted to TeX at all). There is therefore little gain +in using <code>\</code><code>newfont</code>. +<p>One temptation arises from the way that LaTeX restricts the sizes +of fonts. In fact, this restriction only significantly applies to the +default (Computer Modern) and the Cork-encoded (T1) EC fonts, but it +is widely considered to be anomalous, nowadays. In recognition of +this problem, there is a package <i>fix-cm</i> which will allow you +to use the fonts, within LaTeX, at any size you choose. If you’re +not using scaleable versions of the fonts, most modern distributions +will just generate an appropriate bitmap for you. +<p>So, suppose you want to use Computer Modern Roman at 30 points, you +might be tempted to write: +<blockquote> +<pre> +\newfont{\bigfont}{cmr10 at 30pt} +{\bigfont Huge text} +</pre> +</blockquote><p> +which will indeed work, but will actually produce a worse result than +<blockquote> +<pre> +\usepackage{fix-cm} +... +{% + \fontsize{30}{36}\selectfont + Huge text% +} +</pre> +</blockquote><p> +Note that the <i>fix-cm</i> package was not distributed until the +December 2003 edition of LaTeX; if you have an older distribution, +the packages <i>type1cm</i> (for CM fonts) and +<i>type1ec</i> (for EC fonts) are available. +<dl> +<dt><tt><i>fix-cm.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.zip">macros/latex/base</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base/">browse</a>) (an unpacked + version is available at <a href="ftp://cam.ctan.org/tex-archive/macros/latex/unpacked/fix-cm.sty">macros/latex/unpacked/fix-cm.sty</a>) +<dt><tt><i>type1cm.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/type1cm.zip">macros/latex/contrib/type1cm</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/type1cm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/type1cm/">browse</a>) +<dt><tt><i>type1ec.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super/type1ec.sty">fonts/ps-type1/cm-super/type1ec.sty</a> (the package is actually part of + the <a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.zip">fonts/ps-type1/cm-super</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super/">browse</a>) distribution, but it works happily in + the absence of the scaled fonts) +</dl> +<p> +<p> +<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfont</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfunction.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfunction.html index 2651b36a52d..fcf30d12aba 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfunction.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfunction.html @@ -3,10 +3,13 @@ </head><body> <h3>Defining a new log-like function in LaTeX</h3> <p>Use the <code>\</code><code>mathop</code> command, as in: +<blockquote> <pre> - \newcommand{\diag}{\mathop{\mathrm{diag}}} +\newcommand{\diag}{\mathop{\mathrm{diag}}} </pre> -<p>Subscripts and superscripts on <code>\</code><code>diag</code> will be placed as they are on +</blockquote><p> +<p>Subscripts and superscripts on <code>\</code><code>diag</code> will be placed below and +above the function name, as they are on <code>\</code><code>lim</code>. If you want your subscripts and superscripts always placed to the right, do: <blockquote> @@ -14,19 +17,26 @@ to the right, do: <pre> \newcommand{\diag}{\mathop{\mathrm{diag}}\nolimits} </pre> -</blockquote> -<p>AMSLaTeX (in its <i>amsopn</i> package) provides a command +</blockquote><p> +<p>AMSLaTeX (in its <i>amsopn</i> package, which is automatically +loaded by <i>amsmath</i>) provides a command <code>\</code><code>DeclareMathOperator</code> that takes does the same job as the first definition above. To create our original <code>\</code><code>diag</code> command, one would say: +<blockquote> <pre> - \DeclareMathOperator{\diag}{diag} +\DeclareMathOperator{\diag}{diag} </pre> +</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>". -<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.) +“<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; 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.) <dl> <dt><tt><i>amsopn.sty</i></tt><dd>In the AMSLaTeX distribution <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlang.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlang.html index 258d42fcd64..20fd4797ce8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlang.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlang.html @@ -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-instpackages.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,38 +52,31 @@ 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> -<dt>fpTeX<dd> Click + 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>Create all format files</code>, or run any of the teTeX options - in a windows command window. -<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>MiKTeX</code>-> <code>Maintenance</code>-> <code>Create all format files</code> <p> or get a DOS window and run:<br> <code>initexmf --dump</code> -<p> On a <i>MikTeX</i> distribtution v2.0 or later, the whole +<p> On a <i>MiKTeX</i> distribtution 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>MikTeX Options</code>, and select the <code>Languages</code> tab. + <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> tab and press the <code>Update Now</code> button. @@ -93,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-doc/doc/english/FAQ-en/html/FAQ-newlineargs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlineargs.html index f30cab61497..68a8d346ccf 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlineargs.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlineargs.html @@ -11,16 +11,16 @@ g <*> [grump] </pre> -</blockquote> +</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: @@ -32,7 +32,7 @@ braces: {*}/ } </pre> -</blockquote> +</blockquote><p> (The above text derives from an actual post to <i>comp.text.tex</i>; this particular bit of typesetting could plainly also be done using the <code>verbatim</code> environment.) @@ -43,16 +43,16 @@ searches of this nature) may be used. From another <i>comp.text.tex</i> example: <blockquote> <pre> -\begin{eqnarry} +\begin{eqnarray} [a] &=& b \\ \relax[a] &=& b -\end{eqnarry} +\end{eqnarray} </pre> -</blockquote> +</blockquote><p> which is a usage this FAQ would not recommend, anyway: refer to the <a href="FAQ-eqnarray.html">reason not to use <code>eqnarray</code></a>. <p>Note that the <i>amsmath</i> package modifies the behaviour of <code>\\</code> in maths. With <i>amsmath</i>, the <code>eqnarray</code> -example doesn'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-doc/doc/english/FAQ-en/html/FAQ-noans.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noans.html index 4191200b96d..b71d0f92289 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noans.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noans.html @@ -1,19 +1,24 @@ <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@tex.ac.uk">maintainers</a> to report the answer -that you find unclear. Time permitting (the team is small and all its -members are busy), we'll try and clarify the answer. This way, with a -bit of luck, we can together improve the value of this resource to the -whole community. -<p>(We need hardly say that we look forward to hearing from none of you: -but we're not so arrogant as to be confident that we won't!) + <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, +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 +work on, or new questions we should answer in future editions. +<p>Those who simply ask questions at that address will be referred to +<a href="mailto:texhax@tug.org"><i>texhax@tug.org</i></a> or to <i>comp.text.tex</i>. <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noans">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noans</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nocitestar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nocitestar.html index 59e5a8413be..013ce258b18 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nocitestar.html +++ b/Master/texmf-doc/doc/english/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><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nocite*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nocite*</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nodollar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nodollar.html index ab7876b5e36..7e8c7c7f90e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nodollar.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nodollar.html @@ -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 commited 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-doc/doc/english/FAQ-en/html/FAQ-nofm.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nofm.html index 6f2b34e981c..8726a73e346 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nofm.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-nohyph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nohyph.html index 1e2b7e22215..cda9186ca1b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nohyph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nohyph.html @@ -1,38 +1,40 @@ <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 +<blockquote> <pre> - \def\hyph{\penalty0\hskip0pt\relax} +\def\hyph{-\penalty0\hskip0pt\relax} </pre> +</blockquote><p> This is <em>not</em> the sort of thing this FAQ would ordinarily recommend... The <i>hyphenat</i> package defines a bundle of such commands (for introducing hyphenation points at @@ -41,8 +43,8 @@ to install it.) 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> @@ -51,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="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyphenat.zip">macros/latex/contrib/hyphenat</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyphenat.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyphenat/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noline.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noline.html index 99cb8653634..efa0517cb29 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noline.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noline.html @@ -10,11 +10,11 @@ See the LaTeX manual or LaTeX Companion for explanation. </pre> -</blockquote> +</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} @@ -22,17 +22,17 @@ so you've written (for example): Text... \end{description} </pre> -</blockquote> +</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.) @@ -44,12 +44,12 @@ rather wide selection of variants of these things.) Text... \end{description} </pre> -</blockquote> +</blockquote><p> which fills out the under-full line before forcing its closure. The <i>expdlist</i> package provides the same functionality with its <code>\</code><code>breaklabel</code> command, and <i>mdwlist</i> provides it via its <code>\</code><code>desclabelstyle</code> command. -<p>The other common occasion for the message is when you'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: @@ -61,8 +61,8 @@ in the environment: body of the centred text... \end{center} </pre> -</blockquote> -The solution here is plain: use the <code>\</code><code>\</code> command in the way it's +</blockquote><p> +The solution here is plain: use the <code>\</code><code>\</code> command in the way it’s supposed to be used, to provide more than just a single line break space. <code>\</code><code>\</code> takes an optional argument, which specifies how much extra space to add; the required effect in the text above can be had @@ -74,10 +74,11 @@ by saying: body of the centred text... \end{center} </pre> -</blockquote> +</blockquote><p> <dl> <dt><tt><i>expdlist.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/expdlist.zip">macros/latex/contrib/expdlist</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/expdlist.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expdlist/">browse</a>) <dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse</a>) </dl> +<p> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noline</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonfree.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonfree.html index 924831835d5..0fe3dfb236e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonfree.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonfree.html @@ -1,10 +1,10 @@ <head> <title>UK TeX FAQ -- question label nonfree</title> </head><body> -<h3>What's the CTAN <code>nonfree</code> tree?</h3> +<h3>What’s the CTAN <code>nonfree</code> tree?</h3> <p>The CTAN archives are currently restructuring their holdings -so that files that are 'not free' are held in a separate tree. The -definition of what is 'free' (for this purpose) is influenced by, but +so that files that are ‘not free’ are held in a separate tree. The +definition of what is ‘free’ (for this purpose) is influenced by, but not exactly the same as the diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonpdfsp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonpdfsp.html index 3883862df00..b901dfb8c0d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonpdfsp.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-nonum.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonum.html index a585be382f0..37016846394 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonum.html +++ b/Master/texmf-doc/doc/english/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. @@ -17,7 +17,7 @@ exemplified by the following error text: 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,8 +34,8 @@ 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. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopagebrk.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopagebrk.html index c1555b648cd..189dea74418 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopagebrk.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopagebrk.html @@ -8,53 +8,53 @@ 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 -exaple is list items - they suggest page breaks between them. Even -if <code>samepage</code> <em>does</em> work, it's likely to leave stuff +exaple 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> \raggedbottom \addtolength{\topskip}{0pt plus 10pt} </pre> -</blockquote> +</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> \addtolength{\topskip}{0pt plus-10pt} </pre> -</blockquote> +</blockquote><p> as well as resetting <code>\</code><code>flushbottom</code>. (Note that the <code>10pt</code> never actually shows up, because it is overwhelmed when the page is shipped out by the stretchability introduced by <code>\</code><code>raggedbottom</code>; however, it could well have an effect if <code>\</code><code>flushbottom</code> was in effect.) <p>An alternative (which derives from a suggestion by Knuth in the -TeXbook) is the package <i>needspace</i> or the <i>memoir</i>, +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 @@ -66,7 +66,7 @@ kept together, the sequence <text generating lines 1-4> % now stuff we don't mind about </pre> -</blockquote> +</blockquote><p> Yet another trick by Knuth is useful if you have a sequence of small blocks of text that need, individually, to be kept on their own page. Insert the command <code>\</code><code>filbreak</code> before each small block, and the @@ -83,8 +83,8 @@ patch would be: \oldsubsubsection } </pre> -</blockquote> -While the trick works for consecutive sequences of blocks, it's +</blockquote><p> +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-doc/doc/english/FAQ-en/html/FAQ-nopageno.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopageno.html index d8f4f81d5c9..ee7f0729a23 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopageno.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopageno.html @@ -7,7 +7,7 @@ document. <p>To suppress page numbers from a single page, use <code>\</code><code>thispagestyle{empty}</code> somewhere within the text of the page. (Note that <code>\</code><code>maketitle</code> and <code>\</code><code>chapter</code> both use -<code>\</code><code>thispagestyle</code> internally, so you need to call it after you've +<code>\</code><code>thispagestyle</code> internally, so you need to call it after you’ve called them.) <p>To suppress page numbers from a sequence of pages, you may use <code>\</code><code>pagestyle{empty}</code> at the start of the sequence, and restore @@ -17,17 +17,17 @@ command. <p>In the <i>memoir</i> class, the troublesome commands (<code>\</code><code>maketitle</code>, <code>\</code><code>chapter</code>, etc.) invoke their own page style (<code>title</code>, <code>chapter</code>, etc.), which you may -redefine using the class's own techniques to be equivalent to -"<code>empty</code>". The <i>KOMA-script</i> classes have +redefine using the class’s own techniques to be equivalent to +“<code>empty</code>”. The <i>KOMA-script</i> classes have commands that contain the page style to be used, so one might say: <blockquote> <pre> \renewcommand*{\titlepagestyle}{empty} </pre> -</blockquote> +</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), which may be undesirable. @@ -37,7 +37,7 @@ the resetting; so one can say <pre> \renewcommand*{\pagemark}{} </pre> -</blockquote> +</blockquote><p> to have the same effect as the <code>gobble</code> trick, without resetting the page number. <dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-normalszmiss.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-normalszmiss.html index 841bdb91645..f5e40246587 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-normalszmiss.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-normalszmiss.html @@ -9,7 +9,7 @@ The font size command \normalsize is not defined: there is probably something wrong with the class file. </pre> -</blockquote> +</blockquote><p> is reporting something pretty fundamental (document base font size not set up). While this <em>can</em>, as the message implies, be due to a broken class file, the more common cause is that you have simply diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noroom.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noroom.html index 4f5dcc0f640..cf320e54560 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noroom.html +++ b/Master/texmf-doc/doc/english/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 @@ -18,34 +18,34 @@ message saying <pre> ! No room for a new \<thing>. </pre> -</blockquote> +</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-NTS.html">e-TeX</a> and <a href="FAQ-omega.html">Omega</a> + Of course, <a href="FAQ-etex.html">e-TeX</a> and <a href="FAQ-omegaleph.html">Omega</a> - both do this, as does <a href="FAQ-commercial.html">MicroPress Inc's VTeX</a>. + both do this, as does <a href="FAQ-commercial.html">MicroPress Inc’s VTeX</a>. <p>The commonest way to encounter one of these error messages is to have broken macros of some sort, or incorrect usage of macros (an example is discussed in <a href="FAQ-epsf.html">epsf problems</a>). <p>However, sometimes one just <em>needs</em> more than TeX can offer, -and when this happens, you'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>. In cases like PiCTeX, it may be possible to use -<a href="FAQ-NTS.html">e-TeX</a> (all modern distributions provide it). The +<a href="FAQ-etex.html">e-TeX</a> (all modern distributions provide it). The LaTeX package <i>etex</i> modifies the register allocation -mechanism to make use of e-TeX's extended register sets (it's a +mechanism to make use of e-TeX’s extended register sets (it’s a derivative of the Plain TeX macro file <i>etex.src</i>, which is used in building the e-TeX Plain format; both files are part of the -e-TeX distribution). Unfortunately, e-TeX doesn't help with +e-TeX distribution). Unfortunately, e-TeX doesn’t help with <code>\</code><code>read</code> or <code>\</code><code>write</code> objects. <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noroom">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noroom</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-notWYSIWYG.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-notWYSIWYG.html index 074eb436abe..723bd5f81ba 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-notWYSIWYG.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-notWYSIWYG.html @@ -2,56 +2,56 @@ <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-doc/doc/english/FAQ-en/html/FAQ-numbersets.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-numbersets.html index e2fb5a5680a..cfa682358c0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-numbersets.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-numbersets.html @@ -7,7 +7,7 @@ other standard number sets. Traditionally these were typeset in bold. Because, in the ordinary course of events, mathematicians do not have access to bold chalk, they invented the special symbols that are now often used for <code>\</code><code>R</code>, <code>\</code><code>C</code>, <em>etc</em>. These symbols are known -as "blackboard bold". Before insisting on using them, consider +as “blackboard bold”. Before insisting on using them, consider whether going back to the old system of ordinary bold might not be acceptable (it is certainly simpler). <p>A set of blackboard bold capitals is available in the AMS @@ -19,34 +19,34 @@ distribution, and are available in Type 1 format with most modern distributions. Support files for using the fonts, both under Plain TeX and LaTeX (packages <i>amssymb</i> and <i>amsfonts</i>), are available. The font shape is a rather -austere sans, which many people don'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>An alternative source of Type 1 fonts with blackboard bold characters may be found in the steadily increasing set of complete families, both commercial and free, that have been prepared for use with (La)TeX (see -"<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}{{\sf R\hspace*{-0.9ex}% @@ -58,13 +58,13 @@ the digit '1', and lower-case 'k'. \newcommand{\C}{{\sf C\hspace*{-0.9ex}% \rule{0.15ex}{1.3ex}\hspace*{0.9ex}}} </pre> -</blockquote> +</blockquote><p> are almost acceptable at normal size if the surrounding text is <i>cmr10</i>. However, they are not part of a proper maths font, and so do not work in sub- and superscripts. Moreover, the size and position of the vertical bar can be affected by the font of the -surrounding text. As we've seen, there are plenty of alternatives: -don't try the macros, or anything similar using capital 'I' (which +surrounding text. As we’ve seen, there are plenty of alternatives: +don’t try the macros, or anything similar using capital ‘I’ (which looks even worse!). <dl> <dt><tt><i>AMS support files (Plain)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/plaintex.zip">fonts/amsfonts/plaintex</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/plaintex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/plaintex/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oarglikesect.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oarglikesect.html index f9b20074004..e5de72fef15 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oarglikesect.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oarglikesect.html @@ -2,15 +2,39 @@ <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> <pre> -\newcommand\thing[2][\DefaultOpt]{\def\DefaultOpt{#2} ...} -</pre> +\documentclass{article} +\newcommand\thing[2][\DefaultOpt]{% + \def\DefaultOpt{#2}% + optional arg: #1, mandatory arg: #2% +} +\begin{document} +\thing{manda}% #1=#2 +\thing[opti]{manda}% #1="opti" +\end{document} +</pre> +</blockquote><p> +LaTeX itself has a trickier (but less readily understandable) +method, using a macro <code>\</code><code>@dblarg</code>; inside LaTeX, the example +above would have been programmed: +<blockquote> +<pre> +\newcommand\thing{\@dblarg\@thing} +\newcommand\@thing[2][\@error]{% + optional arg: #1, mandatory arg: #2% +} +</pre> +</blockquote><p> +In that code, <code>\</code><code>@thing</code> is only ever called with an optional and a +mandatory argument; if the default from the <code>\</code><code>newcommand</code> is +invoked, a bug in user code has bitten... <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oarglikesect">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oarglikesect</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddhyphen.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddhyphen.html index c78f900f681..5831983ded8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddhyphen.html +++ b/Master/texmf-doc/doc/english/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="ftp://cam.ctan.org/tex-archive/language/hyphenation/ukhyphen.tex">language/hyphenation/ukhyphen.tex</a> </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddpage.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddpage.html index 45e592b21c3..8f8332eeab4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddpage.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddpage.html @@ -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,10 +28,16 @@ sets a private-use label, and the page reference part of that label is then examined (in a <i>hyperref</i>-safe way) to set a conditional <code>\</code><code>ifcpoddpage</code> true if the command was issued on an odd page. The <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>chngpage</i> +offers. Koma-Script’s supporting command is +<code>\</code><code>ifthispageodd{<true>}{<false>}</code> executes different things +depending on the page number. <dl> <dt><tt><i>chngpage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/chngpage.sty">macros/latex/contrib/misc/chngpage.sty</a> +<dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oddpage">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oddpage</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ol-books.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ol-books.html new file mode 100644 index 00000000000..9136865f352 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ol-books.html @@ -0,0 +1,29 @@ +<head> +<title>UK TeX FAQ -- question label ol-books</title> +</head><body> +<h3>Freely available (La)TeX books</h3> +<p>People have long argued for (La)TeX books to be made available on +the web, and until relatively recently this demand went un-answered. +<p>The first to appear was Victor Eijkhout’s excellent “TeX by +Topic” in 2001 (it had been published by Addison-Wesley, but was long +out of print). The book is currently available at +<a href="http://www.eijkhout.net/tbt/">http://www.eijkhout.net/tbt/</a>; it’s not a beginner’s tutorial but +it’s a fine reference. +<p>Addison-Wesley have also released the copyright of “TeX for the +Impatient” by Paul W. Abrahams, Karl Berry and Kathryn A. Hargreaves, +another book whose unavailability many have lamented. The authors +have re-released the book under the GNU general documentation +licence, and it is available from CTAN. +<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 +its day, but while it is now somewhat dated, it still has its uses, +and is a welcome addition to the list of on-line resources. A project +to update it is believed to be under way. +<dl> +<dt><tt><i>Making TeX Work</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/makingtexwork/mtw-1.0.1-html.tar.gz">info/makingtexwork/mtw-1.0.1-html.tar.gz</a> +<dt><tt><i>TeX for the Impatient</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/impatient.zip">info/impatient</a> (<a href="ftp://cam.ctan.org/tex-archive/info/impatient.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/impatient/">browse</a>) +</dl> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ol-books">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ol-books</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oldfontnames.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oldfontnames.html index 07752ce071c..ba0374a88ca 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oldfontnames.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-omega.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-omega.html deleted file mode 100644 index 6b634044f67..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-omega.html +++ /dev/null @@ -1,40 +0,0 @@ -<head> -<title>UK TeX FAQ -- question label omega</title> -</head><body> -<h3>The Omega project</h3> -<p>Omega - -is a program built by extension of the TeX sources which works -internally with 'wide' characters (it is capable of dealing with all -of Unicode version 3); this allows it to work with most scripts in the -world with few difficulties from coding schemes. -Omega also has a -powerful concept of input and output filters to allow the user to work -with existing transliteration schemes, <em>etc</em>. -<p>A part of the project is to develop a version of LaTeX to work with -Omega, styled -"Lambda". -<p> - -<p>Omega was first released in November 1996 -by the project originators, John Plaice and Yannis Haralambous; a -recent version is maintained on CTAN. General project -information, as well as copies papers, are available via the - - <a href="http://omega.enstb.org">project's web site</a>. -<p>Implementations of Omega -are available as part of the teTeX, -mikTeX, fpTeX and CMacTeX distributions -(see <a href="FAQ-TeXsystems.html">TeX systems</a>), as well as -in <a href="FAQ-CD.html">TeX Live</a>. -<p>A related project, <a href="FAQ-aleph.html">Aleph</a>, has merged a version of -Omega with the facilities of -<a href="FAQ-NTS.html">e-TeX</a>, as a pathfinder for potential future Omega -development. -<dl> -<dt><tt><i>CTAN distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/omega.zip">systems/omega</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/omega.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/omega/">browse</a>) (not up-to-date: use the - version in your (La)TeX distribution) -</dl> -<p> -<p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=omega">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=omega</a> -</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-omegaleph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-omegaleph.html new file mode 100644 index 00000000000..2a8b40146c5 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-omegaleph.html @@ -0,0 +1,33 @@ +<head> +<title>UK TeX FAQ -- question label omegaleph</title> +</head><body> +<h3>Omega and Aleph</h3> +<p>Omega was developed as an extension of +TeX, to use with multilingual texts, expressed in a variety of +input encodings. Omega uses 16-bit, Unicode-encoded, characters. It +provides many innovative concepts, notably including the “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, its +development was slow, and development was essentially dead by the time +that one of the original developers withdrew (taking with him a bunch +of research students). +<p>Before that distressing event, a separate thread of development was +started, to produce a program called Aleph +, which merged the facilities of +<a href="FAQ-etex.html">e-TeX</a> into a stable Omega codebase and added other +extensions. Aleph also proved an attractive platform for many people; +but its development, too, has dried up. +<p>The latest news (from EuroTeX 2006) is that development of Omega is +picking up again, in parallel with research into what the (new) +authors consider a rational scheme for supporting TeX-style +typesetting. The new system is to be known as Omega-2 +(Omega subscript 2), and is being +designed in a modular fashion so that support of new facilities (such +as use of advanced OpenType fonts) can be added in a relatively +straightforward fashion. +<p>The work done in the Aleph project is also being carried forward in +the <a href="FAQ-luatex.html">LUATeX</a> project. +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=omegaleph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=omegaleph</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-onecolabs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-onecolabs.html index 16b9d4825a9..eddafb746f6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-onecolabs.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-onecolabs.html @@ -18,7 +18,7 @@ the entire page, even in a two-column paper. The required trick is: \end{@twocolumnfalse} ] </pre> -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: <pre> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-optionclash.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-optionclash.html new file mode 100644 index 00000000000..950e0536391 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-optionclash.html @@ -0,0 +1,105 @@ +<head> +<title>UK TeX FAQ -- question label optionclash</title> +</head><body> +<h3>Option clash for package</h3> +<p>So you’ve innocently added: +<blockquote> +<code>\</code><code>usepackage[draft]{graphics}</code> +</blockquote><p> +to your document, and LaTeX responds with +<blockquote> +<pre> +! LaTeX Error: Option clash for package graphics. +</pre> +</blockquote><p> + +<p>The error is a complaint about loading a package +<em>with options</em>, more than once (LaTeX doesn’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 +occurred on the second line of: +<blockquote> +<code>\</code><code>usepackage[dvips]{graphics}</code><br> +<code>\</code><code>usepackage[draft]{graphics}</code> +</blockquote><p> +which could quite reasonably (and indeed correctly) have been typed: +<blockquote> +<code>\</code><code>usepackage[dvips,draft]{graphics}</code> +</blockquote><p> +<p>But if you’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 +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>/graphics.sty ... +...) +... +) +</pre> +</blockquote><p> +(the parentheses for <i>graphics</i> are completely enclosed in +those for <i>foo</i>; the same is of course true if <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 +interested in, you need to ask LaTeX to slip in options when +<i>foo</i> loads it. Instead of: +<blockquote> +<code>\</code><code>usepackage{foo}</code><br> +<code>\</code><code>usepackage[draft]{graphics}</code> +</blockquote><p> +you would write: +<blockquote> +<code>\</code><code>PassOptionsToPackage{draft}{graphics}</code><br> +<code>\</code><code>usepackage{foo}</code> +</blockquote><p> +The command <code>\</code><code>PassOptionsToPackage</code> tells LaTeX to behave as if +its options were passed, when it finally loads a package. As you would +expect from its name, <code>\</code><code>PassOptionsToPackage</code> can deal with a list +of options, just as you would have in the the options brackets of +<code>\</code><code>usepackage</code>. +<p>More trickily, instead of: +<blockquote> +<code>\</code><code>documentclass[...]{bar}</code><br> +<code>\</code><code>usepackage[draft]{graphics}</code> +</blockquote><p> +you would write: +<blockquote> +<code>\</code><code>PassOptionsToPackage{draft}{graphics}</code><br> +<code>\</code><code>documentclass[...]{bar}</code> +</blockquote><p> +with <code>\</code><code>PassOptionsToPackage</code> <em>before</em> the <code>\</code><code>documentclass</code> +command. +<p>However, if the <i>foo</i> package or the <i>bar</i> class loads +<i>graphics</i> with an option of its own that clashes with +what you need in some way, you’re stymied. For example: +<blockquote> +<code>\</code><code>PassOptionsToPackage{draft}{graphics}</code> +</blockquote><p> +where the package or class does: +<blockquote> +<code>\</code><code>usepackage[final]{graphics}</code> +</blockquote><p> +sets <code>final</code> <em>after</em> it’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 +<code>draft</code> has been forgotten). +<p>In such a case, you have to modify the package or class itself +(subject to the terms of its licence). It may prove useful to contact +the author: she may have a useful alternative to suggest. +<p> +<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=optionclash">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=optionclash</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-otherprinters.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-otherprinters.html index 2cd11b92d44..f0559e4bf42 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-otherprinters.html +++ b/Master/texmf-doc/doc/english/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 such drivers for @@ -10,12 +10,11 @@ primary one is that few formats offer the flexibility available through PostScript, and <i>ghostscript</i> is <em>so</em> good, and has <em>such</em> a wide range of printer drivers (perhaps this is where the DVI output driver writers have all gone?). -<p>The general advice, then, is to -<a href="FAQ-dvips.html">generate PostScript</a>, and to process -that with <i>ghostscript</i> set to generate the format for the -printer you actually have. If you are using a Unix system of some -sort, it's generally quite easy to insert <i>ghostscript</i> into -the print spooling process. +<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> +into the print spooling process. <dl> <dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/ghostscript/">nonfree/support/ghostscript/</a> </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ouparmd.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ouparmd.html index dd29c2a60b4..eaaf9d73a81 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ouparmd.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ouparmd.html @@ -7,9 +7,9 @@ <pre> ! LaTeX Error: Not in outer par mode. </pre> -</blockquote> -comes when some "main" document feature is shut up somewhere it -doesn't like. +</blockquote><p> +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> @@ -22,9 +22,9 @@ inside a table: \hline \end{tabular} </pre> -</blockquote> +</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} @@ -32,7 +32,7 @@ but doesn't work, any more than: \end{figure}% } </pre> -</blockquote> +</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. @@ -46,11 +46,11 @@ here: \hline \end{tabular} </pre> -</blockquote> -What was the float for? - as written in the first two examples, it +</blockquote><p> +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> @@ -64,9 +64,9 @@ command): \end{tabular} \end{figure} </pre> -</blockquote> +</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-doc/doc/english/FAQ-en/html/FAQ-outszwrng.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-outszwrng.html index d593b879f61..aa6ca53ec1f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-outszwrng.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-outszwrng.html @@ -15,16 +15,16 @@ depend on the version of Acrobat Reader (or "Adobe Reader" from version 6.0 onwards) you have installed: <ul> <li> Mac OS X, Adobe Reader 6:<br> - in the print dialogue, on the "copies & pages" pane, you'll find a - popup menu titled "Page Scaling". Make sure that the menu reads - "None". + in the print dialogue, on the “copies & pages” pane, you’ll find a + popup menu titled “Page Scaling”. Make sure that the menu reads + “None”. <li> Windows, Adobe Reader 6:<br> - in the print dialogue, select "None" from the drop-down list - "Page Scaling". + in the print dialogue, select “None” from the drop-down list + “Page Scaling”. <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><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=outszwrng">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=outszwrng</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-overfull.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-overfull.html index af1cc71416d..f708e6696e9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-overfull.html +++ b/Master/texmf-doc/doc/english/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> -For both, an "infinite" tolerance is represented by the value +</blockquote><p> +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>The choice of method has time implications - each of the +</blockquote><p> +<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> @@ -93,14 +93,41 @@ LaTeX users could use an environment like: \par } </pre> -</blockquote> +</blockquote><p> enclosing entire paragraphs (or set of paragraphs) in it. -<p><code>\</code><code>emergencystretch</code> is a slightly trickier customer to understand. -The example above set it to <code>3em</code>; the Computer Modern fonts -ordinarily fit three space skips to the em, so the change would -allow anything up to the equivalent of nine extra spaces in each -line. In a line with lots of spaces, this could be reasonable, but -with (say) only three spaces on the line, each could stretch to four -times its natural width. +<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 +right any other way. (The extra scan happens if +<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 +to the equivalent of nine extra spaces in each line. In a line with +lots of spaces, this could be reasonable, but with (say) only three +spaces on the line, each could stretch to four times its natural +width. It is therefore clear that <code>\</code><code>emergencystretch</code> needs to be +treated with a degree of caution. +<p>More subtle (but more tricky to manage) are the microtypographic +extensions provided by PDFTeX. Since PDFTeX is the default +‘engine’ for LaTeX and ConTeXt work in all distributions, +nowadays, the extensions are available to all. There are two +extensions, margin kerning and font expansion; margin kerning only +affects the visual effect of the typeset page, and has little effect +on the ability of the paragraph setter to “get things right”. +Font expansion works like a subtler version of the trick that +<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 +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 +specification of adjustments for yet more fonts are always welcome. +<dl> +<dt><tt><i>microtype.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/microtype.zip">macros/latex/contrib/microtype</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/microtype.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/microtype/">browse</a>) +</dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overfull">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overfull</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pagebychap.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pagebychap.html index 00468f992f6..bfa768c7424 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pagebychap.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pagebychap.html @@ -3,11 +3,11 @@ </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 -another answer on +another answer on <a href="FAQ-running-nos.html">running numbers within a chapter</a>, and the basic technique is indeed pretty similar. @@ -16,11 +16,11 @@ 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. <p>Documentation of <i>chappg</i> is to be found in the package file. <dl> -<dt><tt><i>chappg.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/chappg.sty">macros/latex/contrib/misc/chappg.sty</a> +<dt><tt><i>chappg.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/chappg.zip">macros/latex/contrib/chappg</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/chappg.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/chappg/">browse</a>) </dl> <p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pagebychap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pagebychap</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-papersize.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-papersize.html index 77493ea0663..353e5314cfe 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-papersize.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-papersize.html @@ -2,22 +2,22 @@ <title>UK TeX FAQ -- question label papersize</title> </head><body> <h3>Printer paper sizes</h3> -<p>Paper sizes can be a pain: they're a forgotten backwater, because -there's no DVI command to specify the paper size of the -document. One usually finds American "letter" paper size being +<p>Paper sizes can be a pain: they’re a forgotten backwater, because +there’s no DVI command to specify the paper size of the +document. One usually finds American “letter” paper size being used, by default, in macro packages (such as <i>plain</i> and LaTeX); but distributions provide configuration files for DVI drivers (and since most distributions originate in Europe, -the drivers usually default to ISO "A4" paper size). +the drivers usually default to ISO “A4” paper size). <p>This is (of course) pretty unsatisfactory. Users may change the paper size their document is designed for, pretty easily (and once off), but they have to ensure that every run of <i>xdvi</i>, <i>dvips</i>, or whatever, is given the correct override for using -anything non-'standard'. +anything non-‘standard’. <p>Of course, the default paper size for DVI drivers may be -changed by a distribution management command, but this still doesn't -provide for people using the "wrong" sort of paper for some reason. -<p>An interestingly different issue arises for users of PDFTeX - the +changed by a distribution management command, but this still doesn’t +provide for people using the “wrong” sort of paper for some reason. +<p>An interestingly different issue arises for users of PDFTeX — the PDF format <em>does</em> have the means of expressing paper size, but much of the core software predates PDFTeX, so not even PDFLaTeX sets the correct values into <code>\</code><code>pdfpagewidth</code> and @@ -40,9 +40,11 @@ which instruct <i>geometry</i> which <code>\</code><code>special</code> commands (Note that the options are ignored if you are using either PDFLaTeX or VTeX.) <p>So, the resolution of the problem is to add +<blockquote> <pre> - \usepackage[dvixxx,...]{geometry} +\usepackage[dvixxx,...]{geometry} </pre> +</blockquote><p> (where <code>dvixxx</code> is your current favourite DVI driver), and the document will run correctly with any of LaTeX (whether or not run on VTeX) or PDFLaTeX. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parallel.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parallel.html index d4cc2051f4c..ed533cb12a7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parallel.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parallel.html @@ -2,12 +2,49 @@ <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 typesetting in two columns (not necessarily of the same width) on one -page, or on the two opposing pages of a two-page spread. +page, or on the two opposing pages of a two-page spread. Use can be +as simple as +<blockquote> +<pre> +\usepackage{parallel} +... +\begin{Parallel}{<left-width>}{<right-width} + \ParallelLText{left-text} + \ParallelRText{right-text} + \ParallelPar + ... +\end{Parallel} +</pre> +</blockquote><p> +<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”: +<blockquote> +<pre> +\usepackage{parcolumns} +... +\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. +<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. <dl> <dt><tt><i>ledpar.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ledmac.zip">macros/latex/contrib/ledmac</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ledmac.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ledmac/">browse</a>) <dt><tt><i>parallel.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/parallel.zip">macros/latex/contrib/parallel</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/parallel.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/parallel/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-paraparam.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-paraparam.html index a7844b0d6c0..70ac18b8573 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-paraparam.html +++ b/Master/texmf-doc/doc/english/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). @@ -20,7 +20,7 @@ end the group.} Here's more that needn't be ragged... </pre> -</blockquote> +</blockquote><p> TeX will open a group, and impose the ragged-setting parameters within that group; it will then save a couple of sentences of text and close the group (thus restoring the previous value of the @@ -37,8 +37,8 @@ that is to replace the last three lines above with: end the group.\par} Here's more that needn't be ragged... </pre> -</blockquote> -In this way, the paragraph is completed while <code>\</code><code>raggedright</code>'s +</blockquote><p> +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 @@ -49,11 +49,11 @@ defines an appropriate one: Here's text to be ranged left... \end{flushleft} </pre> -</blockquote> +</blockquote><p> <p>In fact, there are a number of parameters for which TeX only maintains one value per paragraph. A tiresome one is the set of upper case/lower case translations, which (oddly enough) constrains -hyphenation of mutlilingual texts. Another that regularly creates +hyphenation of mutilingual texts. Another that regularly creates confusion is <a href="FAQ-baselinepar.html"><code>\</code><code>baselineskip</code></a>. <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=paraparam">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=paraparam</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parskip.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parskip.html index d8968391a87..3892cb64bf3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parskip.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-patch.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-patch.html index d5d61403e57..8340ec898e3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-patch.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-patch.html @@ -12,12 +12,12 @@ would naturally write: <pre> \renewcommand{\splat}{\mumble\splat} </pre> -</blockquote> +</blockquote><p> However, this would not work: a call to <code>\</code><code>splat</code> would execute <code>\</code><code>mumble</code>, and the call the redefined <code>\</code><code>splat</code> again; this is an -infinite recursive loop, that will quickly exhaust TeX's memory. +infinite recursive loop, 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> @@ -25,7 +25,7 @@ So: \let\OldSmooth\smooth \renewcommand{\smooth}{\mumble\OldSmooth} </pre> -</blockquote> +</blockquote><p> effects the required patch, safely. Adding things at the end of a command works similarly. If <code>\</code><code>smooth</code> takes arguments, one must pass them on: @@ -34,17 +34,17 @@ pass them on: \renewcommand{\smooth}[2]{\mumble\OldSmooth{#1}{#2}} </pre> -</blockquote> +</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> +</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>patch</i> or @@ -59,17 +59,17 @@ substitutions, and it regenerates the command thus amended. The author of this FAQ has (slightly reluctantly) given up using <i>patch</i>... <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 arguments: the command to patch, stuff to stick at the front of its definition, and stuff to stick on the end of its definition. So, if -<code>\</code><code>b</code> contains "<code>b</code>", then +<code>\</code><code>b</code> contains “<code>b</code>”, then <code>\</code><code>patchcommand</code><code>\</code><code>b{a}{c}</code> -will produce a new version of <code>\</code><code>b</code> that contains "<code>abc</code>". +will produce a new version of <code>\</code><code>b</code> that contains “<code>abc</code>”. <dl> -<dt><tt><i>patch.doc</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/patch.doc">macros/generic/patch.doc</a> +<dt><tt><i>patch.doc</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/misc/patch.doc">macros/generic/misc/patch.doc</a> <dt><tt><i>patchcommand.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/patchcmd.zip">macros/latex/contrib/patchcmd</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/patchcmd.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/patchcmd/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=patch">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=patch</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdfpagelabels.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdfpagelabels.html index 1302d60ec7c..10acbf573f3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdfpagelabels.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdfpagelabels.html @@ -7,31 +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 it confuses <i>hyperref</i> since there are pages which seem (to <i>hyperref</i>) to have the same page number. Fortunately, there are -configuration options to make <i>hyperref</i> "do the right -thing". +configuration options to make <i>hyperref</i> “do the right +thing”. <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'. - (If the option is set '<code>true</code>' - the default - + <i>hyperref</i> writes different anchors for pages ‘ii’ and ‘2’. + (If the option is set ‘<code>true</code>’ — the default — <i>hyperref</i> writes page anchors as the arabic form of the absolute page number, rather than the formatted form.) <dt><code>pdfpagelabels</code><dd> Set PDF page labels; i.e., write the value of <code>\</code><code>thepage</code> to the PDF file so that - <i>Acrobat Reader</i> can display the page number as (say) '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 usually are not. -<p>The recipe isn't perfect: it relies on <code>\</code><code>thepage</code> being different +‘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 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="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>) </dl> -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdfpagelabels">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdfpagelabels</a> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdfpagelabels">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdfpagelabels</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdftex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdftex.html deleted file mode 100644 index 77b1f1266fb..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdftex.html +++ /dev/null @@ -1,34 +0,0 @@ -<head> -<title>UK TeX FAQ -- question label pdftex</title> -</head><body> -<h3>The PDFTeX project</h3> -<p>PDFTeX (formerly known as TeX2PDF) arose from -Han The Thanh's -post-graduate research at Masaryk University, Brno, Czech -Republic. The basic idea is very simple: to provide a version of -TeX that can output PDF as an alternative format to -DVI. PDFTeX implements a small number of new -primitives, to switch to PDF output, and to control various -PDF features. -Han The Thanh -worked on PDFTeX throughout his Ph.D. research into -typesetting, and the latest release includes facilities he wrote to -support novel typesetting techniques that he was studying. -<p>Since he completed his studies, Han has had little time to work on -PDFTeX, and day-to-day support is provided by a team of experts -(mostly in Europe). -The latest sources are available on CTAN, and -implementations are available as part of Web2C, as well as in the -teTeX, mikTeX, fpTeX, CMacTeX and TeX live distributions -A version (by the author of CMacTeX) for use with OzTeX is also -available on CTAN. -<p>A mailing list discussing PDFTeX is available; - - subscribe via the - <a href="http://www.tug.org/mailman/listinfo/pdftex">TUG <i>mailman</a> interface</i>. -<dl> -<dt><tt><i>pdftex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/pdftex/pdftex.zip">systems/pdftex/pdftex.zip</a> -<dt><tt><i>pdftex for OzTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/pdftex/pdftex_for_oztex.sit.bin">nonfree/systems/mac/pdftex/pdftex_for_oztex.sit.bin</a> -</dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdftex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdftex</a> -</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdftexgraphics.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdftexgraphics.html index 71fd5d72a93..f40b1ec8f3c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdftexgraphics.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdftexgraphics.html @@ -3,52 +3,55 @@ </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 +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> +<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 use it in files from -sources you don't entirely trust. -<p>A similar package, <i>ps4pdf</i>, permits other things than 'mere' -graphics files in its argument. (Documentation is scarce: see the -<a href="http://www.perce.de/LaTeX/ps4pdf/Examples/">distribution page</a> -for some examples.) +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 +PDFLaTeX, then use LaTeX, <i>dvips</i> and <i>ps2pdf</i> +in succession, to produce a secondary file to input to your next +PDFLaTeX run. (Scripts are provided to ease the production of the +secondary file.) <p>An alternative solution is to use <i>purifyeps</i>, a <i>Perl</i> script which uses the good offices of <i>pstoedit</i> and of MetaPost to convert your Encapsulated PostScript to -"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' -<a href="http://pstricks.de/pdf/pdfoutput.phtml#pdftricks">PDFtricks support page</a>, -which is, in fact, targeted at the use of <i>pstricks</i> in +<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="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>) <dt><tt><i>pdftricks.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdftricks.zip">macros/latex/contrib/pdftricks</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdftricks.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdftricks/">browse</a>) -<dt><tt><i>ps4pdf.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ps4pdf.zip">macros/latex/contrib/ps4pdf</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ps4pdf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ps4pdf/">browse</a>) +<dt><tt><i>pst-pdf.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pst-pdf.zip">macros/latex/contrib/pst-pdf</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pst-pdf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pst-pdf/">browse</a>) <dt><tt><i>pstoedit</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/pstoedit.zip">support/pstoedit</a> (<a href="ftp://cam.ctan.org/tex-archive/support/pstoedit.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/pstoedit/">browse</a>) <dt><tt><i>purifyeps</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/purifyeps.zip">support/purifyeps</a> (<a href="ftp://cam.ctan.org/tex-archive/support/purifyeps.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/purifyeps/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pk.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pk.html index 059614210bf..269187fdd88 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pk.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pk.html @@ -13,7 +13,7 @@ that is each magnification (size) of each design (point) size for each weight for each family. Further, since the PK files for one printer do not necessarily work well for another, the whole set needs to be duplicated for each printer type at a site. As a result, they are -often held in an elaborate directory structure, or in 'font library -files', to regularise access. +often held in an elaborate directory structure, or in ‘font library +files’, to regularise access. <p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pk">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pk</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkfix.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkfix.html index b452169d34d..9c0b4184417 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkfix.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkfix.html @@ -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, @@ -27,7 +27,7 @@ then patched back into the original file. -Yet another option is Frank Siegert's (shareware) +Yet another 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-doc/doc/english/FAQ-en/html/FAQ-pkgdoc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkgdoc.html index 46f148b3ff4..2ed7affb208 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkgdoc.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkgdoc.html @@ -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 a teTeX-based system, the <i>texdoc</i> command is usually useful, as in: @@ -15,17 +15,17 @@ system, the <i>texdoc</i> command is usually useful, as in: <pre> texdoc footmisc </pre> -</blockquote> +</blockquote><p> which opens an <i>xdvi</i> window showing documentation of the <i>footmisc</i> package. According to the type of file <i>texdoc</i> finds, it will launch <i>xdvi</i>, a <i>ghostscript</i>-based PostScript viewer or a PDF reader. -If it can't find any documentation, it may launch a Web browser to +If it 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 CTAN now encourages authors to submit documentation of their packages, that entry may provide a useful lead. -<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. @@ -42,7 +42,7 @@ similarly-named) file, which you process with LaTeX instead. (Sometimes the package author even thinks to mention this wrinkle in a package <code>README</code> file.) <p>Another common form is the separate documentation file; particularly -if a package is "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 @@ -57,13 +57,13 @@ 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. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plainvltx.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plainvltx.html index d0ec2b4a133..e42a28eff35 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plainvltx.html +++ b/Master/texmf-doc/doc/english/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, @@ -11,7 +11,7 @@ brain power. <p>The arguments around this topic can provoke huge amounts of noise and heat, without offering much by way of light; your best bet is to find out what those around you are using, and to go with the crowd. Later -on, you can always switch your allegiance; don't bother about it. +on, you can always switch your 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-doc/doc/english/FAQ-en/html/FAQ-plninltx.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plninltx.html index 423caff49b2..6cc4b4747dd 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plninltx.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plninltx.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 (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,22 +15,22 @@ 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, contrives to miss the effect of the class option <code>fleqn</code>. @@ -50,12 +50,12 @@ saying: \LaTeX \end{document} </pre> -</blockquote> -(the reader is encouraged to try this). The "A" of LaTeX -has pretty much disappeared: LaTeX sets the "A" according to -<em>its</em> idea of the font size (10pt), but "<code>\</code><code>myfont</code>" is more +</blockquote><p> +(the reader is encouraged to try this). The “A” of LaTeX +has pretty much disappeared: LaTeX sets the “A” according to +<em>its</em> idea of the font size (10pt), but “<code>\</code><code>myfont</code>” 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> @@ -65,16 +65,16 @@ source. The mini-document: {\myfont par\`a} \end{document} </pre> -</blockquote> -gives you "German low double quotes" in place of the grave accent. +</blockquote><p> +gives you “German low double quotes” in place of the grave accent. This problem arises because <i>ecrm1000</i> is in a different -<a href="FAQ-whatenc.html">font encoding</a> than LaTeX is expecting - if you +<a href="FAQ-whatenc.html">font encoding</a> than LaTeX is expecting — if you use LaTeX font commands, all the tiresome encoding issues are solved for you, behind the scenes. -<p>So, whether you're dealing with a one-off font or a major new family, you +<p>So, whether you’re dealing with a one-off font or a major new family, you are far more likely to be satisfied with the LaTeX file selection -system, so it's worth investing a small amount of effort to write -declarations of the font's family and how it should be loaded. For +system, so it’s worth investing a small amount of effort to write +declarations of the font’s family and how it should be loaded. For details of the commands you need, see the LaTeX font usage guide, <i>fntguide</i>: this may be viewed on the archive, but you should find a copy of the document in your own system. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-poster.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-poster.html new file mode 100644 index 00000000000..ef7cd3de774 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-poster.html @@ -0,0 +1,54 @@ +<head> +<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 +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 +is provided with the distribution +<p>Otherwise, there is a range of tools, most of which are based on the +<i>a0poster</i> class, which sets up an appropriately-sized piece of +paper, sets font sizes appropriately, and leaves you to your own +devices. +<p>Having used <i>a0poster</i>, you can of course slog it out, and write +all your poster as an unadorned LaTeX document (presumably in +multiple columns, using the <i>multicol</i> package), but it’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 +posters, and a worked example is provided. The author of +<i>flowfram</i> has an experimental tool called +<a href="http://theoval.cmp.uea.ac.uk/~nlct/jpgfdraw/">JpgfDraw</a>, which +allows you to construct the outline of frames for use with +<i>flowfram</i>. +<p>Despite the relative shortage of tools, there are a fair few web pages +that explain the process (mostly in terms of the <i>a0poster</i> +route): +<ul> +<li> from Norman Gray, <a href="http://purl.org/nxg/note/posters">http://purl.org/nxg/note/posters</a>; +<li> from “<em>awf</em>” and “<em>capes</em>” + <a href="http://www.robots.ox.ac.uk/~awf/latex-posters/">http://www.robots.ox.ac.uk/~awf/latex-posters/</a>; +<li> from Brian Wolven, + <a href="http://fuse.pha.jhu.edu/~wolven/posters.html">http://fuse.pha.jhu.edu/~wolven/posters.html</a> (this page also + provides macros and other support suggestions); and +<li> from “<em>pjh</em>”, + <a href="http://www.phys.ufl.edu/~pjh/posters/poster_howto_UF.html">http://www.phys.ufl.edu/~pjh/posters/poster_howto_UF.html</a>, + which covers the specific issue of dealing with University of + Florida styled poster, but has hints which are generally useful. +</ul> +<dl> +<dt><tt><i>a0poster.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/a0poster.zip">macros/latex/contrib/a0poster</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/a0poster.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/a0poster/">browse</a>) +<dt><tt><i>flowfram.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/flowfram.zip">macros/latex/contrib/flowfram</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/flowfram.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/flowfram/">browse</a>) +<dt><tt><i>multicol.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) +<dt><tt><i>sciposter.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sciposter.zip">macros/latex/contrib/sciposter</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sciposter.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sciposter/">browse</a>) +<dt><tt><i>textpos.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textpos.zip">macros/latex/contrib/textpos</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textpos.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textpos/">browse</a>) +</dl> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=poster">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=poster</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-previewers.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-previewers.html index cf673a555da..c2a314e47ee 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-previewers.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-previewers.html @@ -3,13 +3,13 @@ </head><body> <h3>DVI previewers</h3> <p>EmTeX for PCs running MSDOS or OS/2, MiKTeX and -fpTeX for PCs running Windows and OzTeX for the Macintosh, all -come with previewers that can be used on those platforms. EmTeX's +XEmTeX for PCs running Windows and OzTeX for the Macintosh, all +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 +<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>. Unix TeX distributions (such as @@ -18,7 +18,7 @@ using the same version of <i>web2c</i> as the rest of the distribution. <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-doc/doc/english/FAQ-en/html/FAQ-prinvalint.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-prinvalint.html index 2621c930464..d04c18a79e8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-prinvalint.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-privinst.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-privinst.html index 41d28558d7e..c178fbaa85a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-privinst.html +++ b/Master/texmf-doc/doc/english/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> of your own; fortunately, the TDS standard allows for this, and teTeX 2.0 actually makes provision for it, defining an internal variable <code>HOMETEXMF</code> @@ -26,23 +26,23 @@ the definition, but suppressed it with comment markers.) <pre> texhash $HOME/texmf </pre> -</blockquote> -(the argument specifies which tree you are indexing: it's necessary -since you don't, by hypothesis, have access to the main tree, and +</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 <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 <code>HOMETEXMF</code> (teTeX 1.0 -didn't, for example), and second, there may be some obstruction to +you’re using may <em>not</em> define <code>HOMETEXMF</code> (teTeX 1.0 +didn’t, for example), 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 +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 command: <blockquote> <pre> kpsewhich texmf.cnf </pre> -</blockquote> +</blockquote><p> Take a copy of the file and put it into a directory of your own; this could be any directory, but an obvious choice is the <i>web2c</i> directory of the tree you want to create, i.e., @@ -53,13 +53,13 @@ point to this directory: TEXMFCNF=$HOME/texmf/web2c export TEXMFCNF </pre> -</blockquote> +</blockquote><p> (for a Bourne shell style system), or <blockquote> <pre> setenv TEXMFCNF $HOME/texmf/web2c </pre> -</blockquote> +</blockquote><p> (for a C-shell style system). Now edit the copy of <i>texmf.cnf</i> <p>There will be a line in the existing file that defines the tree where everything searches; the simplest form of the line is: @@ -67,26 +67,26 @@ everything searches; the simplest form of the line is: <pre> TEXMF = !!$TEXMFMAIN </pre> -</blockquote> +</blockquote><p> but, as teTeX 1.0 is distributed, there are several alternative -settings behind comment markers ("<code>%</code>"), and the +settings behind 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 TEXMF = {$HOMETEXMF,!!$TEXMFMAIN} % TEXMF = !!$TEXMFMAIN </pre> -</blockquote> +</blockquote><p> the important point being that <code>$HOMETEXMF</code> must come before whatever was there before, inside the braces. For example, if the original was <blockquote> <pre> TEXMF = {!!$LOCALTEXMF,!!$TEXMFMAIN} </pre> -</blockquote> +</blockquote><p> it should be converted to: <blockquote> @@ -95,22 +95,22 @@ HOMETEXMF = $HOME/texmf TEXMF = {$HOMETEXMF,!!$LOCALTEXMF,!!$TEXMFMAIN} % TEXMF = {!!$LOCALTEXMF,!!$TEXMFMAIN} </pre> -</blockquote> +</blockquote><p> (retaining the original, as a comment, is merely an aide-memoir in case you need to make another change, later). The <code>!!</code> signs tell the file-searching library that it should insist on a <i>texhash</i>-ed directory tree; if you can count on yourself remembering to run <i>texhash</i> on your new tree every time you -change it, then it's worth adding the marks to your tree: +change it, then it’s worth adding the marks to your tree: <blockquote> <pre> TEXMF = {!!$HOMETEXMF,!!$LOCALTEXMF,!!$TEXMFMAIN} </pre> -</blockquote> +</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-doc/doc/english/FAQ-en/html/FAQ-proof.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-proof.html index 5c79f00b1cb..e1bf94ca702 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-proof.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-proof.html @@ -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 @@ -27,9 +27,9 @@ equation: \end{equation*} \end{proof} </pre> -</blockquote> +</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="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html index 10327ca08fa..bcc7d341a3b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html @@ -1,29 +1,29 @@ <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.) Places to look for +arguments. (‘Moving’ because data are moved around.) Places to look for 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> -<p>What's going on really, behind the scenes? The commands in the moving +<p>What’s going on really, behind the scenes? The commands in the moving arguments are already expanded to their internal structure during the process of saving. Sometimes this expansion results in invalid TeX -code when processed again. "<code>\</code><code>protect</code><code>\</code><code>cmd</code>" tells LaTeX to save +code when processed again. “<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 expansion. -<p>What is a 'fragile command'? It's a command that expands into illegal +<p>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>Again, commands are marked as 'robust' or 'fragile', as they're -defined in Lamport's book. Sadly, some commands are robust in +<p>Again, commands are marked as ‘robust’ or ‘fragile’, as they’re +defined in Lamport’s book. Sadly, some commands are robust in LaTeX itself, but are redefined by some packages to be fragile; the <code>\</code><code>cite</code> command commonly suffers this treatment. <p>No-one (of course) likes this situation; the LaTeX3 team have diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psatempty.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psatempty.html index 6dd6a8627b5..afaf4f255b3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psatempty.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psatempty.html @@ -9,7 +9,7 @@ written so that initial pages (pages containing a <code>\</code><code>maketitle< <code>\</code><code>part</code>, or <code>\</code><code>chapter</code>) have a different page style from the rest of the document; to achieve this, the commands internally issue <code>\</code><code>thispagestyle{plain}</code>. This is usually not acceptable -behaviour if the surrounding page style is 'empty'. +behaviour if the surrounding page style is ‘empty’. <p>Possible workarounds include: <ul> <li> Put <code>\</code><code>thispagestyle{empty</code>} immediately after the @@ -25,11 +25,11 @@ behaviour if the surrounding page style is 'empty'. \renewcommand{\footrulewidth}{0pt}% } </pre> - and the "<code>empty</code>" page style (invoked by <code>\</code><code>chapter</code> + and the “<code>empty</code>” page style (invoked by <code>\</code><code>chapter</code> commands and title pages) will have no header or footer. <li> If you are using either the <i>memoir</i> class or a <i>KOMA-script</i> class, use the techniques outlined for them in - "<a href="FAQ-nopageno.html">no page numbers</a>". + “<a href="FAQ-nopageno.html">no page numbers</a>”. </ul> <dl> <dt><tt><i>fancyhdr.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.zip">macros/latex/contrib/fancyhdr</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyhdr/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfchoice.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfchoice.html index b72c19f8c6e..f3686216433 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfchoice.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfchoice.html @@ -12,12 +12,12 @@ demands that TeX makes of maths fonts (for details, see the paper by B.K.P. Horn in <i>TUGboat</i> 14(3)). For maths, 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 @@ -42,7 +42,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 @@ -56,7 +56,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. <dt>MathDesign<dd>(3 entire families...so far) Paul Pichareau<br> This (very new: first release was in April 2005) set so far offers @@ -68,18 +68,18 @@ mathematics include: be welcome. Browse the CTAN directory and see which you want: there is a wealth of documentation and examples. <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 exhibits the problems discussed in - "<a href="FAQ-dvips-pdf.html">getting good PDF</a>" - - don't try to read it on-screen in Acrobat reader). + “<a href="FAQ-dvips-pdf.html">getting good PDF</a>” — + don’t try to read it on-screen in Acrobat reader). <dt>mathptmx<dd>Alan Jeffrey, Walter Schmidt and others.<br> This set contains maths italic, symbol, extension, and roman virtual fonts, built from Adobe Times, Symbol, Zapf Chancery, and the @@ -118,22 +118,22 @@ 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> set for - use with T1 texts doesn't (yet) offer support for mathematics. + the OT1 encoding — the <i>cm-super</i> set for + use with T1 texts doesn’t (yet) offer support for 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 @@ -164,7 +164,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 @@ -174,25 +174,27 @@ commercially, include: For further details (including samples) see<br> <a href="http://www.micropress-inc.com/fonts/ifmath/ifmain.htm">http://www.micropress-inc.com/fonts/ifmath/ifmain.htm</a> +<dt>Lucida Bright <em>with</em> Lucida New Math<dd>(25 fonts) Chuck Bigelow and + Kris Holmes<br> + Lucida is a family of related fonts including seriffed, sans serif, + sans serif fixed width, calligraphic, blackletter, fax, Kris Holmes’ + 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 <code>msam</code> and <code>msbm</code> 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 + set. Support under LaTeX is available under the auspices of the + PSNFSS, and pre-built metrics are also provided. +<p> + TUG has recently (November 2005) acquired the right to distribute + these fonts; the web site - - - - - - - - - - - - - - - - - - + “<a href="http://tug.org/lucida/">Lucida and TUG</a>” + has details. + <dt>Adobe Lucida, LucidaSans <em>and</em> LucidaMath<dd>(12 fonts)<br> Lucida and LucidaMath are generally considered to be a bit heavy. The three maths fonts contain only the glyphs in the CM maths @@ -266,8 +268,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> @@ -302,7 +304,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 @@ -326,7 +328,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 @@ -336,13 +338,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 @@ -354,7 +356,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> @@ -371,6 +373,8 @@ print file (PostScript or PDF) for their output device. <dt><tt><i>hfbright collection</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/hfbright.zip">fonts/ps-type1/hfbright</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/hfbright.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/hfbright/">browse</a>) <dt><tt><i>hvmath (free bitmapped version)</i></tt><dd> <a href="ftp://cam.ctan.org/tex-archive/fonts/micropress/hvmath.zip">fonts/micropress/hvmath</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/micropress/hvmath.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/micropress/hvmath/">browse</a>) +<dt><tt><i>Lucida Bright/Math metrics</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/psfonts/bh/lucida.zip">fonts/psfonts/bh/lucida</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/psfonts/bh/lucida.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/psfonts/bh/lucida/">browse</a>) +<dt><tt><i>Lucida PSNFSS support</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psnfssx/lucidabr.zip">macros/latex/contrib/psnfssx/lucidabr</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psnfssx/lucidabr.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/psnfssx/lucidabr/">browse</a>) <dt><tt><i>MathDesign collection</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/fonts/mathdesign/">fonts/mathdesign/</a> <dt><tt><i>pxfonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/pxfonts.zip">fonts/pxfonts</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/pxfonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/pxfonts/">browse</a>) <dt><tt><i>tmmath (free bitmapped version)</i></tt><dd> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html index 09236cac844..fc609fc2173 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html @@ -8,8 +8,8 @@ package, three questions may arise. <p>First, you have to declare to the DVI driver that you are using PostScript fonts; in the case of <i>dvips</i>, this means adding lines to the <code>psfonts.map</code> file, so that <i>dvips</i> will know -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-doc/doc/english/FAQ-en/html/FAQ-ragright.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ragright.html index d0cbab27cad..52cb0c0a86a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ragright.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ragright.html @@ -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 is +TeX version of the command doesn’t suffer this failing, but is rather conservative: it is loath to create too large a gap at the end of the line, but in some circumstances (such as where <a href="FAQ-hyphoff.html">hyphenation is suppressed</a>) painfully large gaps may sometimes be required. -<p>Martin Schröder's <i>ragged2e</i> package offers the best of both +<p>Martin Schröder’s <i>ragged2e</i> package offers the best of both worlds: it provides raggedness which is built on the Plain TeX model, but which is easily configurable. It defines easily-remembered command (e.g., <code>\</code><code>RaggedRight</code>) and environment (e.g., <code>FlushLeft</code>) names that are simply capitalised transformations of the LaTeX kernel originals. The documentation discusses the issues and explains the signficance of the various -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="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readML.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readML.html index a5a281e3515..c3bb9727379 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readML.html +++ b/Master/texmf-doc/doc/english/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="ftp://cam.ctan.org/tex-archive/macros/xmltex/base.zip">macros/xmltex/base</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/xmltex/base.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/xmltex/base/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html index 465875c196d..efc37e800b2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html @@ -2,29 +2,33 @@ <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? -Well, the good news is that TeX systems are available, free, for -most sorts of computer; the bad news is that you need a pretty -complete TeX system even to read a single file, and complete TeX -systems are pretty large. +<p>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. +<p>So, you need to typeset the document. The good news is that TeX +systems are available, free, for most sorts of computer; the bad news +is that you need a pretty complete TeX system even to read a single +file, and complete TeX systems are pretty large. <p>TeX is a typesetting system that arose from a publishing project (see -"<a href="FAQ-whatTeX.html">what is TeX</a>"), +“<a href="FAQ-whatTeX.html">what is TeX</a>”), and its basic source is available free from its author. However, at its root, it is <em>just</em> a typesetting engine: even to view or to print the typeset output, you will need anciliary programs. In short, -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. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reallyblank.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reallyblank.html index 4a6de299fb8..eaf948013a4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reallyblank.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reallyblank.html @@ -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>: @@ -18,18 +18,18 @@ advising the creation of a command <code>\</code><code>clearemptydoublepage</cod {\pagestyle{empty}\origdoublepage}% } </pre> -</blockquote> -The "obvious" thing is then to use this command to replace +</blockquote><p> +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> \let\cleardoublepage\clearemptydoublepage </pre> -</blockquote> +</blockquote><p> Note: this command works because <code>\</code><code>clearemptydoublepage</code> uses a copy of <code>\</code><code>cleardoublepage</code>: instructions on macro programming @@ -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="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.zip">macros/latex/contrib/fancyhdr</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyhdr/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-recovertex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-recovertex.html index f6918cc60c3..67dab6387fd 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-recovertex.html +++ b/Master/texmf-doc/doc/english/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. @@ -21,7 +21,7 @@ for 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> @@ -37,10 +37,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="ftp://cam.ctan.org/tex-archive/dviware/catdvi.zip">dviware/catdvi</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/catdvi.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/catdvi/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ref-doc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ref-doc.html new file mode 100644 index 00000000000..65aac9f7fda --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ref-doc.html @@ -0,0 +1,23 @@ +<head> +<title>UK TeX FAQ -- question label ref-doc</title> +</head><body> +<h3>Reference documents</h3> +<p>For TeX primitive commands a rather nice +<a href="http://www.nmt.edu/tcc/help/pubs/texcrib.pdf">quick reference booklet</a>, +by John W. Shipman, is available; it’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 +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 +well as the primitive commands. +<p>Similarly, there’s no completely reliable command-organised reference +to LaTeX, but the NASA +<a href="http://www.giss.nasa.gov/latex/">Hypertext Help with LaTeX</a> is +recently much improved. It still talks in LaTeX 2.09-isms in places, +but it’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><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ref-doc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ref-doc</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-repeatgrf.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-repeatgrf.html new file mode 100644 index 00000000000..804ade5cd7e --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-repeatgrf.html @@ -0,0 +1,65 @@ +<head> +<title>UK TeX FAQ -- question label repeatgrf</title> +</head><body> +<h3>Repeated graphics in a document</h3> +<p>A logo or “watermark” image, or any other image that is repeated in +your document, has the potential to make the processed version of the +document unmanageably large. The problem is, that the default +mechanisms of graphics usage add the image at every point it’s to be +used, and when processed, the image appears in the output file at each +such point. +<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 +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 +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 +this <em>in place</em> of <i>graphicx</i>, so rather than: +<blockquote> +<pre> +\usepackage[<options>]{graphicx} +</pre> +</blockquote><p> +you will write: +<blockquote> +<pre> +\usepackage[<options>]{graphicx-psmin} +</pre> +</blockquote><p> +and at the start of your document, you write: +<blockquote> +<pre> +\loadgraphics[<bb>]{<list of graphics>} +</pre> +</blockquote><p> +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 +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). +<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 +so pressing, since the distillation mechanism will amalgamate graphics +objects whether or not the PostScript has them amalgamated. PDFTeX does +the same job with graphics, automatically converting multiple uses +into references to graphics objects. +<dl> +<dt><tt><i>graphicx-psmin.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/graphicx-psmin.zip">macros/latex/contrib/graphicx-psmin</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/graphicx-psmin.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/graphicx-psmin/">browse</a>) +</dl> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repeatgrf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repeatgrf</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-repfootnote.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-repfootnote.html index c9a9293690d..3876ced01b2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-repfootnote.html +++ b/Master/texmf-doc/doc/english/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 @@ -18,7 +18,7 @@ solution is simple: merely use the optional argument of ... ...\footnotemark[1] </pre> -</blockquote> +</blockquote><p> ... which is very easy, since we know there will only ever be a footnote number 1. A similar technique can be used once the footnotes are stable, reusing the number that LaTeX has allocated. This can @@ -35,8 +35,8 @@ to the job: ... ...\footnotemark[\thefnnumber] </pre> -</blockquote> -but this is somewhat tedious. LaTeX's labelling mechanism can be +</blockquote><p> +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> @@ -45,9 +45,9 @@ summoned to our aid, but there are ugly error messages before the ... ...\footnotemark[\ref{fn:repeat}] </pre> -</blockquote> +</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: @@ -57,14 +57,14 @@ example to: ... ...\footref{fn:repeat} </pre> -</blockquote> +</blockquote><p> This is the cleanest simple way of doing the job. Note that the <code>\</code><code>label</code> command <em>must</em> be inside the argument of <code>\</code><code>footnote</code>. <p>The <i>fixfoot</i> package takes away some of the pain of the -matter: you declare footnotes you'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} @@ -72,7 +72,7 @@ then use the command you've 'declared' in the body of the document: ...\rep{} ...\rep{} </pre> -</blockquote> +</blockquote><p> The package ensures that the repeated text appears at most once per page: it will usually take more than one run of LaTeX to get rid of the repeats. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-replstdcls.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-replstdcls.html index 94210099e4d..b635a61665a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-replstdcls.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-rerun.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rerun.html index 21de08556a5..dbb98259de7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rerun.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-resolns.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-resolns.html index 48da039d89e..53bfda94754 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-resolns.html +++ b/Master/texmf-doc/doc/english/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 is forced upon the world by the -feebleness of Adobe's <i>Acrobat</i> <i>Reader</i> at dealing +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 the problems that arise. @@ -47,8 +47,8 @@ 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 +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-doc/doc/english/FAQ-en/html/FAQ-reuseq.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reuseq.html index 536d27f39c5..712d948ef0b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reuseq.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reuseq.html @@ -20,7 +20,7 @@ Remember that \tag{\ref{eq1}} \end{equation} </pre> -</blockquote> +</blockquote><p> Here, the second instance of a=b will be typeset with a copy, made by the <code>\</code><code>tag</code> command, of the label of the first instance. @@ -33,5 +33,5 @@ at <a href="ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf">ftp://ftp.ams.org <dt><tt><i>amsmath.sty</i></tt><dd>Distributed as part of AMSLaTeX <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>) </dl> -<p><p><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> +<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-doc/doc/english/FAQ-en/html/FAQ-rulethk.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rulethk.html index 9c8ce272563..625afa7d991 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rulethk.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rulethk.html @@ -6,16 +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. -<p>Refer to the answer on <a href="FAQ-destable.html">design of tables</a>, elsewhere +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 -suimply skipped the issues surrounding table design, and <em>that's</em> -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 @@ -24,10 +25,10 @@ change from the default (see above) only as far as <pre> \setlength{\arrayrulewidth}{1pt} </pre> -</blockquote> +</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-doc/doc/english/FAQ-en/html/FAQ-runheadtoobig.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-runheadtoobig.html index 19d0ab76251..fcd240d77bb 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-runheadtoobig.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-runheadtoobig.html @@ -4,31 +4,31 @@ <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> <pre> \section[short title]{full title} </pre> -</blockquote> +</blockquote><p> If the <<i>short title</i>> is present, it is used both for the table of -contents and for the page heading: the usual answer to people who -complain about the size of the title that's gone in to the running -head, is to suggest that they the optional argument. +contents and for the page heading. The usual answer to people who +complain that their title is too big for the running head is to +suggest that they the optional argument. <p>However, using the same text for the table of contents as for the running head may also be unsatisfactory: if your chapter titles are seriously long (like those of a Victorian novel), a valid and rational scheme is to have a shortened table of contents entry, and a really terse entry in the running head. <p>One of the problems is the tendency of page headings to be set in -capitals; so why not set headings as written 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 +capitals (which take up more space); so why not set headings as written +for “ordinary” reading? It’s not possible to do so with unmodified +LaTeX, but the <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 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: @@ -37,7 +37,7 @@ this knowledge, one can achieve a three-layer structure for chapters: \chapter[middling version]{verbose version} \chaptermark{terse version} </pre> -</blockquote> +</blockquote><p> which should supply the needs of every taste. <p>Chapters, however, have it easy: hardly any book design puts a page header on a chapter start page. In the case of sections, one has @@ -51,14 +51,14 @@ the recipe for sections is more tiresome: \sectionmark{terse version}} \sectionmark{terse version} </pre> -</blockquote> +</blockquote><p> (the first <code>\</code><code>sectionmark</code> deals with the header of the page the <code>\</code><code>section</code> command falls on, and the second deal with subsequent pages; note that here, you need the optional argument to <code>\</code><code>section</code>, -even if "<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 @@ -71,7 +71,7 @@ example: <pre> \section[middling version][terse version]{verbose version} </pre> -</blockquote> +</blockquote><p> As a result, it is always possible for users of <i>memoir</i> to tailor the header text to fit, with very little trouble. <dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-running-nos.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-running-nos.html index a043d02e8aa..1a47dabf32b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-running-nos.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-running-nos.html @@ -4,7 +4,7 @@ <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 one of the <i>removefr</i> and <i>remreset</i> packages; both define a @@ -14,16 +14,18 @@ writes something like: <pre> \makeatletter \@removefromreset{figure}{chapter} +\makeatother </pre> -</blockquote> -and the automatic renumbering stops. You then need to redefine the +</blockquote><p> +and the automatic renumbering stops. You may then need to redefine the way in which the figure number (in this case) is printed: <blockquote> <pre> +\makeatletter \renewcommand{\thefigure}{\@arabic\c@figure} \makeatother </pre> -</blockquote> +</blockquote><p> (remember to do the whole job, for every counter you want to manipulate, within <code>\</code><code>makeatletter</code> ... <code>\</code><code>makeatother</code>). <p>The technique may also be used to change where in a multilevel @@ -32,12 +34,14 @@ structure a counter is reset. Suppose your class numbers figures as numbered per chapter, try: <blockquote> <pre> +\makeatletter \@removefromreset{figure}{section} \@addtoreset{figure}{chapter} \renewcommand{\thefigure}{\thechapter.\@arabic\c@figure} +\makeatother </pre> -</blockquote> +</blockquote><p> (the command <code>\</code><code>@addtoreset</code> is a part of LaTeX itself). <p>The <i>chngcntr</i> package provides a simple means to access the two sorts of changes discussed, defining <code>\</code><code>counterwithin</code> and @@ -47,7 +51,7 @@ these functions. <dt><tt><i>chngcntr.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/chngcntr.sty">macros/latex/contrib/misc/chngcntr.sty</a> <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>removefr.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fragments/removefr.tex">macros/latex/contrib/fragments/removefr.tex</a> (note, this is constructed as a - "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="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-scriptfonts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-scriptfonts.html index dd17d4834d3..255a34df42d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-scriptfonts.html +++ b/Master/texmf-doc/doc/english/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. The package creates a new command <code>\</code><code>mathscr</code>. <p> Type 1 versions of the font have been made available by Taco @@ -36,7 +36,7 @@ modern TeX distributions. </pre> <p> Adobe Zapf Chancery (which the above examples use) is distributed in any but the most basic PostScript printers. A substantially identical - font (to the the extent that the same metrics may be used) is + font (to the extent that the same metrics may be used) is available from URW and is distributed with <i>ghostscript</i>. </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-seccntfmt.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-seccntfmt.html index 227f6632246..53143de4145 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-seccntfmt.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-seccntfmt.html @@ -7,11 +7,14 @@ 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 way the section number is typeset is determined by the -<code>\</code><code>@seccntformat</code> command, which is given the "name" (section, -subsection, ...) of the heading, as argument. Ordinarily, it +<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> merely outputs the section number, and then a <code>\</code><code>quad</code> of space. Suppose you want to put a stop after every section (subsection, subsubsection, ...) number, a trivial change may be implemented by @@ -22,44 +25,45 @@ simple modification of the command: \csname the#1\endcsname.\quad } </pre> -</blockquote> -<p>Many people (for some reason) just want a stop after a section -number. 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: +</blockquote><p> +<p>Many people (for some reason) want a stop after a section number, but +not after a subsection number, or any of the others. +To do this, one must make <code>\</code><code>@seccntformat</code> switch according to its +argument. The following technique for doing the job is slightly +wasteful, but is efficient enough for a relatively rare operation: <blockquote> <pre> \let\@@seccntformat\@seccntformat \renewcommand*{\@seccntformat}[1]{% - \expandafter\let\expandafter\@tempa - \csname @seccntformat@#1\endcsname - \ifx\@tempa\relax + \expandafter\ifx\csname @seccntformat@#1\endcsname\relax \expandafter\@@seccntformat \else - \expandafter\@tempa + \expandafter + \csname @seccntformat@#1\expandafter\endcsname \fi {#1}% } </pre> -</blockquote> +</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: +definition as the original “all levels alike” version: <blockquote> <pre> \newcommand*{\@seccntformat@section}[1]{% \csname the#1\endcsname.\quad } </pre> -</blockquote> +</blockquote><p> Note that all the command definitions of this answer are dealing in <a href="FAQ-atsigns.html">LaTeX internal commands</a>, so the above code should be in a package file, for preference. <p>The <i>Koma-script</i> classes have different commands for specifying changes to section number presentation: <code>\</code><code>partformat</code>, <code>\</code><code>chapterformat</code> and <code>\</code><code>othersectionlevelsformat</code>, but otherwise -their facilities are similar to those of "raw" LaTeX. +their facilities are similar to those of “raw” LaTeX. <dl> <dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secindent.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secindent.html index ec517fcd6b9..ef165878a7f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secindent.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secindent.html @@ -2,7 +2,7 @@ <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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secnumdep.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secnumdep.html index 829ad3f75c5..f3ac98d273b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secnumdep.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secnumdep.html @@ -16,16 +16,16 @@ 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> \setcounter{secnumdepth}{-1} \chapter{Preface} </pre> -</blockquote> +</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>addsec</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-doc/doc/english/FAQ-en/html/FAQ-secthead.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secthead.html index 89e72ed545f..bbf44221cc7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secthead.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secthead.html @@ -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 @@ -15,24 +15,28 @@ probably satisfy your editor. Define yourself new commands <blockquote> <pre> \newcommand{\ssection}[1]{% - \section[#1]{\centering\sc #1}} + \section[#1]{\centering\normalfont\scshape #1}} \newcommand{\ssubsection}[1]{% - \subsection[#1]{\raggedright\it #1}} + \subsection[#1]{\raggedright\normalfont\itshape #1}} </pre> -</blockquote> + +</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 package <i>sectsty</i> provides an easy-to-use set of tools to -do this job, while the package <i>titlesec</i> has a structured -approach based on redefinition of the sectioning and chapter commands -themselves. <i>Titlesec</i>'s approach allows it to offer far more -radical adjustment: its options provide (in effect) a toolbox for -designing your own sectioning commands' output. +<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. +<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. Unfortunately, <i>fncychap</i> is not attuned to the existence of front- and backmatter in <i>book</i> class documents. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-semanticnest.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-semanticnest.html index 4ee01d4c9a4..63eb90037d0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-semanticnest.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-semanticnest.html @@ -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> @@ -21,7 +21,7 @@ easily: \def\silly{\hbox{here's \silly being executed}} \silly </pre> -</blockquote> +</blockquote><p> The extended traceback (see <a href="FAQ-erroradvice.html"><em>general advice</em> on errors</a>) @@ -37,7 +37,7 @@ followed by 100 instances of 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-doc/doc/english/FAQ-en/html/FAQ-setURL.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-setURL.html index 2afdad9e733..7102c270cc1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-setURL.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-setURL.html @@ -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. Note that, because the operation is @@ -48,8 +48,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 +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>Documentation of both <i>path</i> and <i>url</i> is in the package files. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slashbox.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slashbox.html index 04e673fc232..543e20a95dc 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slashbox.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slashbox.html @@ -21,8 +21,8 @@ x y 5 ----------------- </pre> -</blockquote> -However, this doesn't satisfy everyone: many want the labelling in a +</blockquote><p> +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 @@ -30,9 +30,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 @@ -40,9 +40,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="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/slashbox.zip">macros/latex/contrib/slashbox</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/slashbox.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/slashbox/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slidecls.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slidecls.html index 3b148b107bd..111576c1c02 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slidecls.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slidecls.html @@ -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,58 +10,72 @@ 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 - +<p>The advent of Microsoft <i>PowerPoint</i> (feeble though early +versions of it were) has created a demand for “dynamic” slides — images that develop their content in a more elaborate fashion than by merely replacing one foil with the next in the way that was the norm when <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 +replacement for <i>prosper</i> and <i>HA-prosper</i>, co-authored +by the author of <i>HA-prosper</i>. <p><i>Beamer</i> is a relatively easy-to-learn, yet powerful, class that (as its name implies) was designed for use with projection displays. It needs the <i>pgf</i> package (for graphics support), which in turn requires <i>xcolor</i>; while this adds to the tedium of -installing <i>beamer</i> "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 +get to specify a bunch of slide styles, and you can switch from one to +the other between slides, as you need. (The class itself provides +just the one style, in the package <i>greybars</i>: the author +hopes users will contribute their own styles, based on +<i>greybars</i>.) <p><i>Ppower4</i> (commonly known as <i>pp4</i>) is a <i>Java</i>-based support program that will postprocess -PDF, to '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 pakages 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> <dl> <dt><tt><i>beamer.cls</i></tt><dd>Download all of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/beamer.zip">macros/latex/contrib/beamer</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/beamer.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/beamer/">browse</a>) <dt><tt><i>foils.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/macros/latex/contrib/foiltex.zip">nonfree/macros/latex/contrib/foiltex</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/macros/latex/contrib/foiltex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/macros/latex/contrib/foiltex/">browse</a>) +<dt><tt><i>greybars.sty</i></tt><dd>distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/talk.zip">macros/latex/contrib/talk</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/talk.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/talk/">browse</a>) <dt><tt><i>HA-prosper.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ha-prosper.zip">macros/latex/contrib/ha-prosper</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ha-prosper.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ha-prosper/">browse</a>) <dt><tt><i>seminar.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/seminar.zip">macros/latex/contrib/seminar</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/seminar.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/seminar/">browse</a>) <dt><tt><i>pgf.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/pgf.zip">graphics/pgf</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pgf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pgf/">browse</a>) +<dt><tt><i>powerdot.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/powerdot.zip">macros/latex/contrib/powerdot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/powerdot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/powerdot/">browse</a>) <dt><tt><i>pp4</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/ppower4.zip">support/ppower4</a> (<a href="ftp://cam.ctan.org/tex-archive/support/ppower4.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/ppower4/">browse</a>) <dt><tt><i>ppr-prv.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ppr-prv.zip">macros/latex/contrib/ppr-prv</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ppr-prv.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ppr-prv/">browse</a>) <dt><tt><i>prosper.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/prosper.zip">macros/latex/contrib/prosper</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/prosper.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/prosper/">browse</a>) +<dt><tt><i>talk.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/talk.zip">macros/latex/contrib/talk</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/talk.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/talk/">browse</a>) <dt><tt><i>texpower</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/texpower.zip">macros/latex/contrib/texpower</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/texpower.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/texpower/">browse</a>) <dt><tt><i>xcolor.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xcolor.zip">macros/latex/contrib/xcolor</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xcolor.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xcolor/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-sortbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-sortbib.html index c0c54409a70..1619687feb0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-sortbib.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-spaftend.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spaftend.html index 0ff8579ca35..dd26d8d5880 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spaftend.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-specials.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-specials.html index e23eac5b1c3..37cdc5c574f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-specials.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-specials.html @@ -12,13 +12,13 @@ commands; all that TeX does with these commands is to expand their arguments and then pass the command to the DVI file. In most cases, there are macro packages provided (often with the driver) that provide a comprehensible 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, rotation and scaling, and colour typesetting via <code>\</code><code>special</code>s all easy. <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-doc/doc/english/FAQ-en/html/FAQ-spell.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spell.html index 284dffcf5e5..49fb51a7c8f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spell.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spell.html @@ -23,7 +23,7 @@ version of <i>ispell</i>. <dl> <dt><tt><i>4spell</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/4spell.zip">support/4spell</a> (<a href="ftp://cam.ctan.org/tex-archive/support/4spell.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/4spell/">browse</a>) <dt><tt><i>amspell</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/amspell.zip">support/amspell</a> (<a href="ftp://cam.ctan.org/tex-archive/support/amspell.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/amspell/">browse</a>) -<dt><tt><i>aspell</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/aspell/">support/aspell/</a> - 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="ftp://cam.ctan.org/tex-archive/systems/mac/support/excalibur/Excalibur-4.0.2.sit.hqx">systems/mac/support/excalibur/Excalibur-4.0.2.sit.hqx</a> <dt><tt><i>ispell</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/ispell/ispell-3.2.06.tar.gz">support/ispell/ispell-3.2.06.tar.gz</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spinmacro.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spinmacro.html index 6884eb04b2c..1f75263bada 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spinmacro.html +++ b/Master/texmf-doc/doc/english/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>: @@ -33,12 +33,12 @@ appeared on <i>comp.text.tex</i>: <pre> \newcommand{\stline}[1]{ \bigskip \makebox[2cm]{ \textbf{#1} } } </pre> -</blockquote> +</blockquote><p> The macro definition contains five spaces: <ul> <li> after the opening <code>{</code> of the macro body; this space will be - ignored, not because "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 @@ -77,30 +77,30 @@ emphasising the structure): }% } </pre> -</blockquote> +</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-doc/doc/english/FAQ-en/html/FAQ-splitfoot.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-splitfoot.html index cdfcc1dd520..2cdb88851f0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-splitfoot.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-splitfoot.html @@ -9,21 +9,21 @@ 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> <pre> \interfootnotelinepenalty=10000 </pre> -</blockquote> -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 +</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 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-doc/doc/english/FAQ-en/html/FAQ-srchpdf.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-srchpdf.html new file mode 100644 index 00000000000..e0fbdcddfd9 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-srchpdf.html @@ -0,0 +1,35 @@ +<head> +<title>UK TeX FAQ -- question label srchpdf</title> +</head><body> +<h3>Searching PDF files</h3> +<p>In principle, you can search a PDF file: the text of the file +is available to the viewer, and at least some viewers provide a search +facility. (It’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 +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, +that is. The package will instruct PDFTeX to load character +maps into your PDF for output fonts encoded according to the T1 +(Western European Languages), T2A, T2B, or T2C (Cyrillic Languages), +or T5 (Vietnamese) encodings. If your document uses such encodings, +viewers that can search will use the maps to interpret what they find +in the file. +<p>Unfortunately, the package only works with fonts that are directly +encoded, such as the <i>cm-super</i> distribution. Fonts like Adobe +Times Roman (which are encoded for (La)TeX use via virtual fonts) +are not amenable to this treatment. +<dl> +<dt><tt><i>cmap.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cmap.zip">macros/latex/contrib/cmap</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cmap.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cmap/">browse</a>) +<dt><tt><i>cm-super fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.zip">fonts/ps-type1/cm-super</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super/">browse</a>) +</dl> +<p> +<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=srchpdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=srchpdf</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-struttab.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-struttab.html index 9b33711a62a..8861d86c821 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-struttab.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-struttab.html @@ -3,32 +3,34 @@ </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 by the same amount) use <code>\</code><code>extrarowheight</code>, which is defined by the <i>array</i> package: +<blockquote> <pre> \usepackage{array}% in the preamble ... \setlength{\extrarowheight}{length} \begin{tabular}{....} </pre> -<p>To correct a single row whose maladjustment isn't corrected by a +</blockquote><p> +<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 @@ -36,15 +38,32 @@ 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> does a (possibly inferior) job by defining a +new table/array column type “S”, which you apply to each column +specification. So, for example, +<blockquote> +<pre> +\cmdinvoke{begin}{tabular}{l l l p{3cm}} +</pre> +</blockquote><p> +would become +<blockquote> +<pre> +\cmdinvoke{begin}{tabular}{Sl Sl Sl Sp{3cm}} +</pre> +</blockquote><p> +and so on. This technique shows +promise of not interfering so much with other packages, but this +author has heard of no reports from the field. <p>The <i>booktabs</i> package comes with a thought-provoking essay about how tables should be designed. Since table row-spacing problems -most often appear in collisions with rules, the author'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 @@ -53,6 +72,7 @@ found as comments in the package files themselves. <dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) <dt><tt><i>bigstrut.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multirow.zip">macros/latex/contrib/multirow</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multirow.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow/">browse</a>) <dt><tt><i>booktabs.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/booktabs.zip">macros/latex/contrib/booktabs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/booktabs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/booktabs/">browse</a>) +<dt><tt><i>cellspace.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cellspace.zip">macros/latex/contrib/cellspace</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cellspace.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cellspace/">browse</a>) <dt><tt><i>tabls.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/tabls.sty">macros/latex/contrib/misc/tabls.sty</a> </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=struttab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=struttab</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-subsubsub.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-subsubsub.html index 9145abc949a..93fa590fe8a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-subsubsub.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-subverttoks.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-subverttoks.html index aac602ef668..cb8a2813e20 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-subverttoks.html +++ b/Master/texmf-doc/doc/english/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 @@ -22,15 +22,15 @@ allows an independent package to play the exact same game: \let\everypar\mypkg@everypar </pre> -</blockquote> +</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. @@ -38,5 +38,5 @@ As you can see, the package (<i>mypkg</i>) and away we go. <p>The form <code>\</code><code>mypkg@...</code> is (sort of) blessed for LaTeX package internal names, which is why this example uses macros of that form. -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subverttoks">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subverttoks</a> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subverttoks">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subverttoks</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-t1enc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-t1enc.html index dd20b7055fb..1021587adfb 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-t1enc.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-tabacc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tabacc.html index 476a3c811d4..5a683dc7c53 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tabacc.html +++ b/Master/texmf-doc/doc/english/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,20 +22,20 @@ type: <code>...</code><br> <code>\</code><code>begin{tabbing}</code><br> <code>...</code><br> - <code>...</code> <code>\</code><code>></code> <code>voil\'a</code> <code>\</code><code>></code> <code>...</code> -</blockquote> + <code>...</code> <code>\</code><code>></code> <code>voilà</code> <code>\</code><code>></code> <code>...</code> +</blockquote><p> for: <blockquote> - ...\quad voil\'a\quad ... -</blockquote> + ...\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> @@ -44,7 +44,7 @@ example would therefore become: \begin{Tabbing} ... ... \TAB> voil\`a \TAB> ... </pre> -</blockquote> +</blockquote><p> <dl> <dt><tt><i>Tabbing.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/Tabbing.zip">macros/latex/contrib/Tabbing</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/Tabbing.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/Tabbing/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tabcellalign.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tabcellalign.html index bf41eb54fe4..e2409e9b54b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tabcellalign.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tabcellalign.html @@ -2,16 +2,16 @@ <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> <pre> ... & \centering blah ... \\ </pre> -</blockquote> -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. +</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. 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 @@ -28,13 +28,13 @@ terminates it. \let\\=\temp } </pre> -</blockquote> +</blockquote><p> which one uses as: <blockquote> <pre> ... & \PBS\centering blah ... \\ </pre> -</blockquote> +</blockquote><p> (for example). <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> @@ -45,45 +45,43 @@ explicitly: <pre> ... & \centering blah ... \tabularnewline </pre> -</blockquote> +</blockquote><p> which may be incorporated into a simple macro as: <blockquote> <pre> \newcommand{\RBS}{\let\\=\tabularnewline} -... -... & \centering\RBS blah ... \\ </pre> -</blockquote> +</blockquote><p> and used as <blockquote> <pre> ... & \centering\RBS blah ... \\ </pre> -</blockquote> +</blockquote><p> (note, you Preserve backslash with <code>\</code><code>PBS</code> <em>before</em> the command that changes it, and Restore it with <code>\</code><code>RBS</code> <em>after</em> the command; in fact, <code>\</code><code>RBS</code> is marginally preferable, but the old trick lingers on). <p>The <code>\</code><code>PBS</code> and <code>\</code><code>RBS</code> tricks also serve well in <i>array</i> -package "field format" preamble specifications: +package “field format” preamble specifications: <blockquote> <pre> \begin{tabular}{... >{\centering\RBS}p{50mm}} ... </pre> -</blockquote> +</blockquote><p> or <blockquote> -</blockquote> +</blockquote><p> <blockquote> <pre> \begin{tabular}{... >{\PBS\centering}p{50mm}} ... </pre> -</blockquote> -In the <i>tabularx</i> and <i>tabulary</i> packages, there's a +</blockquote><p> +In the <i>tabularx</i> and <i>tabulary</i> packages, there’s a command <code>\</code><code>arraybackslash</code> that has same effect as <code>\</code><code>RBS</code> (above); so in those packages, one might say: <blockquote> @@ -92,17 +90,17 @@ so in those packages, one might say: \begin{tabular}{... >{\centering\arraybackslash}p{50mm}} ... </pre> -</blockquote> +</blockquote><p> in place of the example above; in fact, the very latest (2003/12/01) release of array.sty also provides a <code>\</code><code>tabularnewline</code> command, -that has the "basic tabular/array" meaning of '\\'. +that has the “basic tabular/array” meaning of ‘\\’. -The command does rather lack brevity, but at least you don't have to +The command does rather lack brevity, but at least you don’t have to define it for yourself. <dl> <dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) <dt><tt><i>tabularx.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) -<dt><tt><i>tabulary.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>) +<dt><tt><i>tabulary.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tabulary.zip">macros/latex/contrib/tabulary</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tabulary.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tabulary/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabcellalign">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabcellalign</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tds.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tds.html index 5fbf9f47f60..e7734d8ef2d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tds.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tds.html @@ -5,7 +5,7 @@ <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 'standard' and a (set of) 'local' hierarchies of +provides for both a ‘standard’ and a (set of) ‘local’ hierarchies of directories containing TeX-related files. The TDS reserves the name <code>texmf</code> as the name of the root directory (folder) of the hierarchies. Files supplied as part of the @@ -17,7 +17,7 @@ be at <i>/opt/texmf</i>, or a similar location, but in each case the TeX files will be under the <i>/texmf</i> subdirectory. -<p>There may be more than on 'local' hierarchy in which additional files +<p>There may be more than on ‘local’ hierarchy in which additional files can be stored. In the extreme an installation can have a local hierarchy and each user can also have an individual local hierarchy. The location of any local hierarchy is not only system dependent but also user diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tempinst.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tempinst.html index 41e92886ed4..7f4a4f83fad 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tempinst.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tempinst.html @@ -1,12 +1,12 @@ <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 @@ -15,17 +15,17 @@ 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-instpackages.html">installing them 'properly'</a>. To do +<a href="FAQ-instpackages.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> @@ -35,22 +35,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-doc/doc/english/FAQ-en/html/FAQ-texinfo.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-texinfo.html index df149ea8f45..6dbba11a410 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-texinfo.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-texinfo.html @@ -6,17 +6,26 @@ both on-line information and printed output. So instead of writing two different documents, one for the on-line help and the other for a typeset manual, you need write only one document source file. When -the work is revised, you need only revise one document. You can read -the on-line information, known as an "Info file", with an Info -documentation-reading program. By convention, Texinfo source file -names end with a <code>.texi</code> or <code>.texinfo</code> extension. You can write and -format Texinfo files into Info files within GNU +the work is revised, you need only revise one document. By +convention, Texinfo source file names end with a <code>.texi</code> or +<code>.texinfo</code> extension. +<p>Texinfo is a macro language, somewhat similar to LaTeX, but with +slightly less expressive power. Its appearance is of course rather +similar to any TeX-based macro language, except that its macros +start with <code>@</code> rather than the <code>\</code> that’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. +Texinfo sources into HTML: the language is a far better fit to +HTML than is LaTeX, so that the breast-beating agonies of +<a href="FAQ-LaTeX2HTML.html">converting LaTeX to HTML</a> are largely +avoided. +<p>Finally, of course, you can also print the files, or convert them to +PDF using PDFTeX. <dl> <dt><tt><i>Texinfo distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/texinfo/texinfo.zip">macros/texinfo/texinfo</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/texinfo/texinfo.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/texinfo/texinfo/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textflow.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textflow.html index 4518b668dcf..a73658155b9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textflow.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textflow.html @@ -3,7 +3,7 @@ </head><body> <h3>Flowing text around figures in LaTeX</h3> <p>There are several LaTeX packages that purport to do this, but they -all have their limitations because the TeX machine isn'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: <p><dl> @@ -14,22 +14,24 @@ conducted a survey of the available packages; he recommends: figure contents \end{floatingfigure} </pre> - |\end{floatingfigure}| + <p>There is a (more or less similar) <code>floatingtable</code> environment. <p>The tables or figures can be set left or right, or alternating on even/odd pages in a double-sided document. -<p>The package works with the <code>multicol</code> package, but doesn'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: -<p><pre> -\begin{wrapfigure}[height of figure in lines]{l|r}[overhang]{width} +<p><blockquote> +<pre> +\begin{wrapfigure}[height of figure in lines]{l|r,...}[overhang]{width} figure, caption, etc. \end{wrapfigure} </pre> - |\end{wrapfigure}| -<p> The syntax of the <code>wraptable</code> environment is similar. +</blockquote><p> + + The syntax of the <code>wraptable</code> environment is similar. <p> Height can be omitted, in which case it will be calculated by the package; the package will use the greater of the specified and the actual width. The <code>{l</code><em>,</em><code>r</code><em>,etc</em>.<code>}</code> parameter can @@ -44,17 +46,15 @@ LaTeX document). <dt><code>picins</code><dd> <i>Picins</i> is part of a large bundle that allows inclusion of pictures (e.g., with shadow boxes, various MSDOS formats, etc.). The command is: -<p> <code>\parpic(width,height)(x-off,y-off)[Options][Position]{Picture}</code><br> - \emph{Paragraph text} +<p> <blockquote> + <code>\parpic(width,height)(x-off,y-off)[Options][Position]{Picture}</code><br> + </blockquote><p> + <em>Paragraph text</em> + <p> All parameters except the <em>Picture</em> are optional. The picture can be positioned left or right, boxed with a rectangle, oval, shadowbox, dashed box, and a caption can be given which will be included in the list of figures. -<p> - - - - <p> Unfortunately (for those of us whose understanding of German is not good), the documentation is in German. Piet van Oostrum has written an English summary. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textrace.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textrace.html index 404849cc665..420ce39eee7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textrace.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textrace.html @@ -3,27 +3,27 @@ </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 +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 @@ -31,9 +31,9 @@ are increasingly being used to provide Type 1 fonts to the public domain. <p>The <i>MetaType1</i> system aims to use Metafont font sources, by way of MetaPost and a bunch of scripts and so on, to produce high-quality Type 1 fonts. The first results, the -<a href="FAQ-type1T1.html"><i>Latin Modern</i> fonts</a>, are pretty -impressive, and it is known that the team that produced the system are -developing new work using the system. +<a href="FAQ-type1T1.html"><i>Latin Modern</i> fonts</a>, are now +well-established, and a bunch of existing designs have been reworked +in MetaType1 format. <dl> <dt><tt><i>MetaType1</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/metatype1.zip">fonts/utilities/metatype1</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/metatype1.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/metatype1/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-the-commands.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-the-commands.html index 8cfc2570342..4525754246e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-the-commands.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-the-commands.html @@ -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 definining 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 @@ -24,7 +24,7 @@ find yourself redefining things left, right and centre. Rather, use the standard techniques for <a href="FAQ-seccntfmt.html">adjusting the presentation of section numbers</a>. <p>Or, suppose you want the page number to appear at the bottom of each -page surrounded by dashes ("<code>-</code><code>- nnn -</code><code>-</code>"). Would you want to +page surrounded by dashes (“<code>-</code><code>- nnn -</code><code>-</code>”). Would you want to achieve this by redefining <code>\</code><code>thepage</code>, given the likely appearance of the table of contents with the dashes attached every page number, or of the modified <code>\</code><code>pageref</code> references. In this case, the diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-thesis.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-thesis.html index 45a6acb6fab..578a461e79a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-thesis.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-thesis.html @@ -2,14 +2,14 @@ <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-spacing, you may care to refer to <a href="FAQ-linespace.html">the relevant question</a>. If you want to write your own, a good place to start is the University -of California style, but it's not worth going to a lot of trouble. (If -officials won't allow standard typographic conventions, you won't be +of California style, but it’s not worth going to a lot of trouble. (If +officials won’t allow standard typographic conventions, you won’t be able to produce an æsthetically pleasing document anyway!) <dl> <dt><tt><i>UC thesis style</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ucthesis.zip">macros/latex/contrib/ucthesis</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ucthesis.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ucthesis/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-time.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-time.html index 694c95e8b53..1747975ce30 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-time.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-titlsty.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-titlsty.html index eb84e5fc3df..d0e4440b3a3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-titlsty.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-tmupfl.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tmupfl.html index f11015f353f..44c8a404516 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tmupfl.html +++ b/Master/texmf-doc/doc/english/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="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toascii.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toascii.html index 35df57f7ee9..c42cb70514b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toascii.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toascii.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label toascii</title> </head><body> -<h3>Conversion from (La)TeX to plain ASCII</h3> +<h3>Conversion from (La)TeX to plain text</h3> <p>The aim here is to emulate the Unix <i>nroff</i>, which formats text as best it can for the screen, from the same input as the Unix typesetting program <i>troff</i>. @@ -9,16 +9,20 @@ input as the Unix typesetting program <i>troff</i>. techniques; sometimes the simple conversion provides a good enough response. Options are: <ul> -<li> <i>dvi2tty</i> (one of the earliest) -<li> <i>crudetype</i> -<li> <i>catdvi</i>, which is also capable of generating Latin-1 - or UTF-8 encoded output. <i>Catdvi</i> was conceived as - a replacement for <i>dvi2tty</i>, but can't (quite) be - recommended as a complete replacement yet. +<li> <i>dvi2tty</i> (one of the earliest), +<li> <i>crudetype</i> and +<li> <i>catdvi</i>, which is capable of generating Latin-1 + (ISO 8859-1) or UTF-8 encoded output. <i>Catdvi</i> was + conceived as a replacement for <i>dvi2tty</i>, but can’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 +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>, @@ -26,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-doc/doc/english/FAQ-en/html/FAQ-tocbibind.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocbibind.html index 07e29769786..94604f49f27 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocbibind.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocbibind.html @@ -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 @@ -18,7 +18,7 @@ or <i>book</i>, for example), the text: \bibliography{frooble} \addcontentsline{toc}{chapter}{Bibliography} </pre> -</blockquote> +</blockquote><p> will produce the <em>wrong</em> answer if the bibliography is more than one page long. Instead, one should say: <blockquote> @@ -27,9 +27,9 @@ one page long. Instead, one should say: \addcontentsline{toc}{chapter}{Bibliography} \bibliography{frooble} </pre> -</blockquote> +</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>The common solution, therefore, is to use the <i>tocbibind</i> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloft.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloft.html index f22e29ab133..e09250a0d02 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloft.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloft.html @@ -7,8 +7,8 @@ controlled by a number of internal commands (discussed in section 2.3 of <a href="FAQ-books.html"><em>The LaTeX Companion</em></a>. The commands <code>\</code><code>@pnumwidth</code>, <code>\</code><code>@tocrmarg</code> and <code>\</code><code>@dotsep</code> control the space for page numbers, the indentation of the right-hand margin, and the -seperation of the dots in the dotted leaders, respectively. The -series of commands named <code>\</code><code>l@<em>xxx</em></code>, where <code><em>xxx</em></code> +separation of the dots in the dotted leaders, respectively. The +series of commands named <code>\</code><code>l@<em>xxx</code></em>, where <code><em>xxx</em></code> is the name of a sectional heading (such as <code>chapter</code> or <code>section</code>, ...) control the layout of the corresponding heading, including the space for section numbers. All these internal @@ -21,7 +21,7 @@ of Figures and List of Tables, the layout of these sections may be controlled in the same way. <p>The <i>KOMA-Script</i> classes provides an optional variant structure for the table of contents, and calculates the space needed for the -numbers automatically. The <i>memoir</i> includes the functionality +numbers automatically. The <i>memoir</i> class includes the functionality of <i>tocloft</i>. <dl> <dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloftwrong.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloftwrong.html index 8433c169f41..883710a4caa 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloftwrong.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloftwrong.html @@ -8,11 +8,11 @@ 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 <a href="FAQ-tocloft.html">re-designing the tables</a> and those techniques can be employed to make the numbers fit. -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloftwrong">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloftwrong</a> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloftwrong">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloftwrong</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toodeep.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toodeep.html index e27ee288241..47c1b59cf28 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toodeep.html +++ b/Master/texmf-doc/doc/english/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: @@ -27,7 +27,7 @@ their own private levels of nesting. Consider this example: ... \end{enumerate} </pre> -</blockquote> +</blockquote><p> In the example, <ul> <li> the first <code>enumerate</code> has labels as for a @@ -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-doc/doc/english/FAQ-en/html/FAQ-topgraph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-topgraph.html index e3906b52dd2..f2ca26d9665 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-topgraph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-topgraph.html @@ -18,9 +18,9 @@ code does this: }% } </pre> -</blockquote> +</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 @@ -35,8 +35,18 @@ as in: }% } </pre> -</blockquote> -The fact is, <em>you</em> may choose where the base-line ends up. This +</blockquote><p> +A more LaTeX-y way of doing the job (somewhat innefficiently) uses +the <i>calc</i> package: +<blockquote> +<pre> +\usepackage{calc} +... +\raisebox{1ex-\height}{\includegraphics{figure}} +</pre> +</blockquote><p> +(this has the same effect as the text-align version, above). +<p>The fact is, <em>you</em> may choose where the base-line ends up. This answer merely shows you sensible choices you might make. <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=topgraph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=topgraph</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tradesyms.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tradesyms.html index e3fc7c0eff5..1b56e248067 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tradesyms.html +++ b/Master/texmf-doc/doc/english/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>). @@ -24,7 +24,7 @@ errors: you <em>must</em> use <pre> \textsuperscript{\textregistered} </pre> -</blockquote> +</blockquote><p> <p> <p><p><p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tradesyms">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tradesyms</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-triptrap.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-triptrap.html index ec0c6eed9e9..951d14392bc 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-triptrap.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-triptrap.html @@ -1,25 +1,28 @@ <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, 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 -reasonably be distributed as a working version. +in principe be distributed as a working version. (In practice, any +distributor would test new versions against “real” documents or +fonts, too; <code>trip</code> and <code>trap</code> don’t actually test any +for real world problems. <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-doc/doc/english/FAQ-en/html/FAQ-tutbitslatex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tutbitslatex.html new file mode 100644 index 00000000000..f1a62ae86f5 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tutbitslatex.html @@ -0,0 +1,92 @@ +<head> +<title>UK TeX FAQ -- question label tutbitslatex</title> +</head><body> +<h3>Specialised (La)TeX tutorials</h3> +<p>The AMS publishes a “Short Math Guide for LaTeX”, which is +available (in several formats) via +<a href="http://www.ams.org/tex/short-math-guide.html">http://www.ams.org/tex/short-math-guide.html</a> +<p>Herbert Voss is developing a parallel document, that is also very +useful; it’s 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> +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 + + + “<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>Kjell Magne Fauske offers a set of examples of the use of the drawing +packages +<a href="FAQ-drawing.html">PGF and TikZ</a>; the +<a href="http://www.fauskes.net/pgftikzexamples/">examples catalogue</a> +includes examples (with output) from the package documentation as well +as code written by the author himself. +<p>Vincent Zoonekynd provides a set of excellent (and graphic) tutorials +on the programming of +<a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_title/0.html">title page styles</a>, +<a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_chapter/0.html">chapter heading styles</a> +and +<a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_section/0.html">section heading styles</a>. +In each file, there is a selection of graphics representing an output +style, and for each style, the code that produces it is shown. +<p>An invaluable step-by-step setup guide for establishing a “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 +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 +complete kit is available on CTAN (distributed with the +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 + +<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) +in his + + + “<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 +existing documentation into HTML, for example the INFO +documentation of the (La)TeX installation, of which a sample is the +LaTeX documentation available at +<a href="http://www.tac.dk/cgi-bin/info2www?(latex)">http://www.tac.dk/cgi-bin/info2www?(latex)</a> +<p>More ambitiously, some university departments have enthusiastic +documenters who +make public record of their (La)TeX support. For example, Tim Love +(of Cambridge University Engineering Department) maintains his +deparment’s pages at +<a href="http://www-h.eng.cam.ac.uk/help/tpl/textprocessing/">http://www-h.eng.cam.ac.uk/help/tpl/textprocessing/</a> + + + + + +<dl> +<dt><tt><i>Graphics in LaTeX2e</i></tt><dd>the + document is available in PostScript and PDF formats as + <a href="ftp://cam.ctan.org/tex-archive/info/epslatex/english/epslatex.ps">info/epslatex/english/epslatex.ps</a> and <a href="ftp://cam.ctan.org/tex-archive/info/epslatex/english/epslatex.pdf">info/epslatex/english/epslatex.pdf</a> respectively +<dt><tt><i>testflow</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/IEEEtran/testflow/">macros/latex/contrib/IEEEtran/testflow/</a> +<dt><tt><i>Herbert Voss’s Maths tutorial</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/math/voss/mathmode/Mathmode.pdf">info/math/voss/mathmode/Mathmode.pdf</a> +</dl> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutbitslatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutbitslatex</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tutorials.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tutorials.html deleted file mode 100644 index 5c200b65e71..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tutorials.html +++ /dev/null @@ -1,154 +0,0 @@ -<head> -<title>UK TeX FAQ -- question label tutorials</title> -</head><body> -<h3>(La)TeX Tutorials, etc.</h3> -<p>Some very fine tutorials have been written, over the years. Michael -Doob's splendid 'Gentle Introduction' to Plain TeX (available on -CTAN) has been stable for a very long time. Another contender -in the same game is from one D. R. Wilkins, available on the web at -<a href="http://www.ntg.nl/doc/wilkins/pllong.pdf">http://www.ntg.nl/doc/wilkins/pllong.pdf</a> -<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 -versions in the some of the many languages it has been translated -into. -<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>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' -<a href="http://www.mcs.vuw.ac.nz/~david/latex/">documentation page</a> is a -useful collection of links in itself. -<p>Peter Flynn's "Beginner's LaTeX" (which also started as course -material) is a pleasing read. A complete copy may be found on -CTAN, but it may also be browsed over the web -(<a href="http://www.tex.ac.uk/tex-archive/info/beginlatex/html/">http://www.tex.ac.uk/tex-archive/info/beginlatex/html/</a>). -<p>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. -<p><a href="http://www.comp.leeds.ac.uk/andyr/misc/latex/index.html">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>Another item, not quite FAQ, not quite tutorial, is Herbert -Voss's excellent -<a href="http://texnik.de/">LaTeX tips and tricks</a>. -<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 -tutorial is available from CTAN as a PDF file (though -the source is also available). -<p>The AMS publishes a "Short Math Guide for LaTeX", which is -available (in several formats) via -<a href="http://www.ams.org/tex/short-math-guide.html">http://www.ams.org/tex/short-math-guide.html</a> -<p>Herbert Voss is developing a parallel document, that is also very -useful; it's part of his "tips and tricks" mentioned above and is -also available on CTAN. - -<p>Keith Reckdahl's "Using Imported Graphics in LaTeX2e" is an -excellent introduction to graphics use, though it's slightly dated in -not discussing anything other than the <i>dvips</i> route. -Available on CTAN, but again without sources. -<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 -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 -complete kit is available on CTAN (distributed with the -author's macros for papers submitted for IEEE publications). -<p> - - -For Plain TeX 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. -<p>Special-purpose tutorials are always useful, and an example is set by -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>Some university departments make their local documentation available -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 -<a href="http://www.tac.dk/cgi-bin/info2www?(latex)">http://www.tac.dk/cgi-bin/info2www?(latex)</a> -<p>More ambitiously, some university departments have enthusiastic -documenters who -make public record of their (La)TeX support. For example, Tim Love -(of Cambridge University Engineering Department) maintains his -deparment'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>, and Mimi -Burbank (of the School of Computer Science & Information Technology -at the University of Florida) manages her department's at -<a href="http://www.csit.fsu.edu/~mimi/tex/">http://www.csit.fsu.edu/~mimi/tex/</a> - both sets are fine -examples of good practice. -<p> - - - -<p>People have long argued for (La)TeX books to be made available on -the web, and -Victor Eijkhout's excellent "TeX by Topic" (previously published -by Addison-Wesley, but long out of print) was offered in this way at -Christmas 2001. The book is currently -available at <a href="http://www.eijkhout.net/tbt/">http://www.eijkhout.net/tbt/</a>; -it's not a beginner's tutorial but it's a fine reference -(contributions are invited, and the book is well -worth the suggested contribution). -<p>Addison-Wesley have also released the copyright of "TeX for the -Impatient" by Paul W. Abrahams, Karl Berry and Kathryn A. Hargreaves, -another book whose unavailability many have lamented. The authors -have re-released the book under the GNU general documentation -licence, and it is available from CTAN. -<p>Norm Walsh's "Making TeX Work" 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. -<p>The book was an excellent resource in its day, but is now somewhat -dated; nevertheless, it still has its uses, and is a welcome addition -to the list of on-line resources. A project to update it is believed -to be under way. -<p>Jim Hefferon maintains a web page - -"<a href="http://www.ctan.org/installationadvice/">Managing a one-person TeX system</a>" -which provides a useful introduction to those who find they need to -manage a TeX system on a personal machine. It covers much of the -matters discussed in answers such as -"<a href="FAQ-wherefiles.html">Where to put new files</a>", -and thereby covers the gap left by the (possibly temporary) lack of -"<em>Making TeX work</em>". -<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>". -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 -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 -contain its Rutgers-local matter) is a fine introduction to the issues -of producing readable documents. -<dl> -<dt><tt><i>Beginner's LaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/beginlatex/beginlatex-3.6.pdf">info/beginlatex/beginlatex-3.6.pdf</a> -<dt><tt><i>Gentle Introduction</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/gentle/gentle.pdf">info/gentle/gentle.pdf</a> -<dt><tt><i>l2tabu</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/l2tabu/english/l2tabuen.pdf">info/l2tabu/english/l2tabuen.pdf</a>; source also available: <a href="ftp://cam.ctan.org/tex-archive/info/l2tabu/english/l2tabuen.tex">info/l2tabu/english/l2tabuen.tex</a> -<dt><tt><i>Graphics in LaTeX2e</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/epslatex.pdf">info/epslatex.pdf</a>; the - document is also available in PostScript format as <a href="ftp://cam.ctan.org/tex-archive/info/epslatex.ps">info/epslatex.ps</a> -<dt><tt><i>Making TeX Work</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/makingtexwork/mtw-1.0.1-html.tar.gz">info/makingtexwork/mtw-1.0.1-html.tar.gz</a> -<dt><tt><i>Not so Short Introduction</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/lshort/english/lshort.pdf">info/lshort/english/lshort.pdf</a> - (in English, or browse for sources and other language versions at - <a href="http://www.tex.ac.uk/tex-archive/info/lshort/">info/lshort/</a>) -<dt><tt><i>Simplified LaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/simplified-latex/simplified-intro.ps">info/simplified-latex/simplified-intro.ps</a> -<dt><tt><i>TeX for the Impatient</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/impatient.zip">info/impatient</a> (<a href="ftp://cam.ctan.org/tex-archive/info/impatient.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/impatient/">browse</a>) -<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' Maths tutorial</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/math/voss/Voss-Mathmode.pdf">info/math/voss/Voss-Mathmode.pdf</a> -</dl> -<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-doc/doc/english/FAQ-en/html/FAQ-tutorialstar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tutorialstar.html new file mode 100644 index 00000000000..efa17ba88f2 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tutorialstar.html @@ -0,0 +1,25 @@ +<head> +<title>UK TeX FAQ -- question label tutorials*</title> +</head><body> +<h3>(La)TeX Tutorials, etc.</h3> +<p>From a situation where every (La)TeX user <em>had</em> to buy a book +if she was not to find herself groping blindly along, we now have what +almost amounts to an embarrassment of riches of online documentation. +The following answers attempt to create lists of sources “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>, +each of which concentrates on a single LaTeX topic. +<p>A couple of reference documents (it would be good to have more) are +listed in an <a href="FAQ-ref-doc.html">answer of their own</a>. +<p>Next comes the (rather new) field of +<a href="FAQ-doc-wiki.html">TeX-related WIKIs</a>. +<p>A rather short list gives us a +<a href="FAQ-typo-style.html">Typography style tutorial</a>. +<p>Finally, we have a set of links to +<a href="FAQ-doc-dirs.html">Directories of (La)TeX information</a>, and details +of some “<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-doc/doc/english/FAQ-en/html/FAQ-twooptarg.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-twooptarg.html index 0284486d9c6..16c3aae2ed0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-twooptarg.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-twooptarg.html @@ -2,8 +2,8 @@ <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>". +<p>If you’ve already read +“<a href="FAQ-moren9.html">breaking the 9-argument limit</a>”. you can probably guess the solution to this problem: command relaying. <p>LaTeX allows commands with a single optional argument thus: <pre> @@ -29,24 +29,24 @@ 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, again in -"<a href="FAQ-moren9.html">breaking the 9-argument limit</a>". -which offer an alternative way forward. +see the comments on the use of the <i>keyval</i> package, in +“<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> package; provides a <code>\</code><code>optparams</code> command that you use as an intermediate in defining commands with up to nine optional arguments. The documentation shows examples of commands with four optional arguments (and this from an author who has his own key-value package!). -<p>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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-type1T1.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-type1T1.html index cb0438aacd2..e4b473f275d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-type1T1.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-type1T1.html @@ -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,37 +45,38 @@ 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>e</code>". However, since this involves two characters being +“<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 -as <code>eth</code> and <code>thorn</code> (used in, for example, in Icelandic), but the -<i>aecompl</i> package works with the <i>ae</i> fonts to provide -the missing characters from the EC fonts (i.e., as bitmaps). +as <code>eth</code> and <code>thorn</code> (used in, for example, in +Icelandic), but the <i>aecompl</i> package works with the +<i>ae</i> fonts to provide the missing characters from the +EC fonts (i.e., as bitmaps). <p>The sole remaining commercial CM-like 8-bit font comes from Micropress, who offer the complete EC set in Type 1 format, as part of their range of outline versions of fonts that were originally distributed in Metafont format. See -<a href="FAQ-commercial.html">"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 @@ -85,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="ftp://cam.ctan.org/tex-archive/fonts/ae.zip">fonts/ae</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ae.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ae/">browse</a>) <dt><tt><i>aecompl.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/fonts/ae.zip">fonts/ae</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ae.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ae/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typebooks.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typebooks.html index ba2f51053ca..62aa732d656 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typebooks.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typebooks.html @@ -14,7 +14,7 @@ Of these, Bringhurst seems to be the one most often recommended. <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 - (Strathmore Press, 1995, ISBN 0-9624891-5-8) + (Strathmore Press, 2006, ISBN 1-875750-22-3) <dt>The Design of Books<dd>by Adrian Wilson (Chronicle Books, 1993, ISBN 0-8118-0304-X) <dt>Optical Letter Spacing<dd>by David Kindersley and Lida Cardozo Kindersley @@ -45,7 +45,7 @@ a more interesting overall view of types in general and some of their history. 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-doc/doc/english/FAQ-en/html/FAQ-typend.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typend.html index dcd0810d1b7..7111e0d217c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typend.html +++ b/Master/texmf-doc/doc/english/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 - +<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 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-doc/doc/english/FAQ-en/html/FAQ-typo-style.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typo-style.html new file mode 100644 index 00000000000..e0e65e0f561 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typo-style.html @@ -0,0 +1,25 @@ +<head> +<title>UK TeX FAQ -- question label typo-style</title> +</head><body> +<h3>Typography tutorials</h3> +<p>There’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>”. +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 +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 +contain its Rutgers-local matter) is a fine introduction to the issues +of producing readable documents. +<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. +<dl> +<dt><tt><i>memoir distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) +</dl> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typo-style">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typo-style</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underline.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underline.html index bb6dd4f2928..122b9ca74c5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underline.html +++ b/Master/texmf-doc/doc/english/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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underscore.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underscore.html index 18a251c7cf0..3db463adced 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underscore.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underscore.html @@ -2,35 +2,37 @@ <title>UK TeX FAQ -- question label underscore</title> </head><body> <h3>How to use the underscore character</h3> -<p>The underscore character <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> in the course of ordinary text, TeX will -complain. If you're writing a document which will contain a large +<code>_</code> in the course of ordinary text, TeX will +complain. If you’re writing a document which will contain a large number of underscore characters, the prospect of typing -<code>\</code><code> (or, worse, <code>\</code><code>textunderscore</code>) for every one of +<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> 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 fuller encoding, such as T1, which has an underscore character in every font. <p>If the requirement is only for occasional uses of underscores, it may be acceptable to use the following construct: +<blockquote> <pre> \def\us{\char`\_} ... \texttt{create\us process} </pre> -The construction isn't in the least robust (in the normal English +</blockquote><p> +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="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/underscore.sty">macros/latex/contrib/misc/underscore.sty</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-unkgrfextn.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-unkgrfextn.html index c0cc7ca74e3..9626ce6f63a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-unkgrfextn.html +++ b/Master/texmf-doc/doc/english/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,11 +18,11 @@ 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 <i>.bedroom.eps</i>, and will complain. To get around this limitation, you have three 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> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uploads.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uploads.html index 540b8751f9f..b7b308ee26c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uploads.html +++ b/Master/texmf-doc/doc/english/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://www.tex.ac.uk/tex-archive/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://www.tex.ac.uk/tex-archive/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); best is a PDF file of the package documentation, prepared for screen @@ -17,16 +17,16 @@ 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>, get yourself a copy of the file <i>README.uploads</i> from any @@ -34,7 +34,7 @@ the file <i>README.uploads</i> from any 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 principle 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 @@ -43,11 +43,11 @@ process, showing you the information you need to supply. <a href="mailto:ctan@dante.de">CTAN management</a>: if the worst comes to the worst, it may be possible to mail a contribution. -<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 <code>ftp</code>, and of course the -directory structure on your archive must 'fit'. +directory structure on your archive must ‘fit’. <dl> <dt><tt><i>README.uploads</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/README.uploads">README.uploads</a> </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-upquot.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-upquot.html index 96766b54de6..541f1c1994d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-upquot.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-useMF.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-useMF.html index 543388de7c5..6a07528d172 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-useMF.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-useMF.html @@ -9,11 +9,11 @@ fonts needs a mode associated with it. Modes are defined using the <code>mode_def</code> convention described on page 94 of <em>The Metafontbook</em> (see <a href="FAQ-books.html">TeX-related books</a>). You will need a file, which conventionally called <i>local.mf</i>, containing all the -<code>mode_def</code>s you will be using. If <i>local.mf</i> doesn't already -exist, Karl Berry's collection of modes (<i>modes.mf</i>) +<code>mode_def</code>s you will be using. If <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 'big -enough' implementation of Metafont). Lists of +(it can be used as a ‘<i>local.mf</i>’ without modification in a ‘big +enough’ 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 @@ -36,9 +36,9 @@ similar; for example, it will be <i>PLAIN.BAS</i> on MSDOS systems) which should be moved to the directory containing the base files on your system (note that some systems have two or more -such directories, one for each 'size' of Metafont used). +such directories, one for each ‘size’ of Metafont used). <p>Now you need to make sure Metafont loads this new base when it starts up. If -Metafont loads the <code>plain</code> base by default on your system, then you're +Metafont loads the <code>plain</code> base by default on your system, then you’re ready to go. Under Unix (using the default <i>web2c</i> distribution ) @@ -52,15 +52,15 @@ it with the line \mode=<mode name>; mag=<magnification>; input <font file name> </pre> in -response to the '**' prompt or on the Metafont command line. (If -<code><mode name></code> is unknown or omitted, the mode defaults to 'proof' and +response to the ‘**’ prompt or on the Metafont command line. (If +<code><mode name></code> is unknown or omitted, the mode defaults to ‘proof’ and Metafont will produce an output file called -<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 +<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 would type <pre> @@ -71,7 +71,7 @@ escaped, so this would typically look something like <pre> mf '\mode=epson; mag=magstep 1; input cmr10' </pre> -<p>If you don't have <i>inimf</i> or need a special mode that isn't +<p>If you don’t have <i>inimf</i> or need a special mode that isn’t in the base, you can put its commands in a file (<em>e.g.</em>, <i>ln03.mf</i>) and invoke it on the fly with the <code>\smode</code> command. For example, to create <i>cmr10.300gf</i> for an LN03 printer, using @@ -92,10 +92,10 @@ type <pre> mf \smode="ln03"; input cmr10 </pre> -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 mentioned in <a href="FAQ-mfptutorials.html">Metafont and MetaPost Tutorials</a>. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usebibtex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usebibtex.html index b9d64831588..62e7c62c1d0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usebibtex.html +++ b/Master/texmf-doc/doc/english/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> @@ -22,23 +22,23 @@ Alice struggles~\cite{Carroll:1865}. ... \bibliography{mybooks} </pre> -</blockquote> +</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> <pre> latex myfile </pre> -</blockquote> +</blockquote><p> As LaTeX processes the file, the <code>\</code><code>bibliographystyle</code> command writes a note of the style to the <code>.aux</code> file; each <code>\</code><code>cite</code> command writes a note of the citation to the <code>.aux</code> file, and the <code>\</code><code>bibliography</code> command writes a note of which <code>.bib</code> file is to be used, to the <code>.aux</code> file. -<p>Note that, at this stage, LaTeX isn'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. @@ -49,13 +49,13 @@ further warning of undefined references. <pre> bibtex myfile </pre> -</blockquote> -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 +</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 <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,7 +67,7 @@ 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 +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 diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uselmfonts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uselmfonts.html index f8aebe3fcc5..604f8e5530f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uselmfonts.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uselmfonts.html @@ -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,29 +34,29 @@ 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://www.miktex.org/manual/psfonts.html">online documentation</a>. + <a href="http://docs.miktex.org/manual/psfonts.html#chgupdmapcfg">online documentation</a>. Then execute the command <code>initexmf --mkmaps</code>, and the job is done. </ul> <p>To use the fonts in a LaTeX document, you should <blockquote> <code>\</code><code>usepackage{lmodern}</code> -</blockquote> +</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> +</blockquote><p> for text, and <blockquote> <code>\</code><code>usepackage{textcomp}</code> -</blockquote> +</blockquote><p> if you want to use any of the TS1-encoding symbols. There is no support for using fonts according to the OT1 encoding. <dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepictex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepictex.html index 5016fbd29c0..0ea68358b47 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepictex.html +++ b/Master/texmf-doc/doc/english/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: @@ -16,42 +16,42 @@ message: <pre> ! No room for a new \dimen. </pre> -</blockquote> +</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-NTS.html">e-TeX</a> and <a href="FAQ-omega.html">Omega</a> both do this, as - does <a href="FAQ-commercial.html">MicroPress Inc's VTeX</a>. + <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>. -<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 Schell's <i>pictexwd</i> and related +<p>Alternatively, Andreas Schell’s <i>pictexwd</i> and related packages replace PiCTeX with a version that uses 33 fewer <code>\</code><code>dimen</code> registers; so use <i>pictexwd</i> in place of <i>pictex</i> (either as a LaTeX package, or as a file to read into Plain TeX). <p>And how does one use PiCTeX anyway, given that the manual is so <a href="FAQ-docpictex.html">hard to come by</a>? -Fortunately for MSDOS and Windows users, the <i>MathsPic</i> +Fortunately for us all, the <i>MathsPic</i> system may be used to translate a somewhat different language into PiCTeX commands; and the <i>MathsPic</i> manual is free (and -part of the distribution). <i>MathsPic</i> is written in -<i>Basic</i>; a version written in <i>Perl</i> is under -development, and should be available soon. +part of the distribution). <i>MathsPic</i> is available either as +a <i>Basic</i> program for DOS, or as a <i>Perl</i> +program for other systems (including Windows, nowadays). <dl> <dt><tt><i>m-pictex.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/context/current/cont-tmf.zip">macros/context/current/cont-tmf.zip</a> <dt><tt><i>m-pictex.tex</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/context/current/cont-tmf.zip">macros/context/current/cont-tmf.zip</a> -<dt><tt><i>MathsPic</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/pictex/mathspic.zip">graphics/pictex/mathspic</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pictex/mathspic.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pictex/mathspic/">browse</a>) +<dt><tt><i>MathsPic</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/mathspic.zip">graphics/mathspic</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/mathspic.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/mathspic/">browse</a>) <dt><tt><i>pictexwd.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/graphics/pictex/addon.zip">graphics/pictex/addon</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pictex/addon.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pictex/addon/">browse</a>) </dl> <p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepictex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepictex</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepsfont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepsfont.html index 41770ae767d..4314ad333d2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepsfont.html +++ b/Master/texmf-doc/doc/english/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 @@ -21,13 +21,13 @@ roman, sans-serif and typewriter fonts; <em>e.g</em>., the <i>Roman</i> as the main text font (and introduces mechanisms to typeset mathematics using <i>Times</i> and various more-or-less matching fonts), while package <i>avant</i> changes the sans-serif -family to <i>AvantGarde</i>, and <i>Courier</i> changes the +family to <i>AvantGarde</i>, and <i>courier</i> changes the typewriter font to <i>Courier</i>. To go with these packages, you need the font metric files and font description (<i>.fd</i>) files for each font family you want to use. For convenience, -metrics for the '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,14 +36,14 @@ 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 +<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="ftp://cam.ctan.org/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="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss/lw35nfss.zip">macros/latex/required/psnfss/lw35nfss.zip</a> <dt><tt><i>lollipop</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/macros/lollipop.zip">nonfree/macros/lollipop</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/macros/lollipop.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/macros/lollipop/">browse</a>) <dt><tt><i>psnfss</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss.zip">macros/latex/required/psnfss</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/psnfss/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidcol.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidcol.html new file mode 100644 index 00000000000..b7fa1c548c9 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidcol.html @@ -0,0 +1,61 @@ +<head> +<title>UK TeX FAQ -- question label varwidcol</title> +</head><body> +<h3>Variable-width columns in tables</h3> +<p>This is a slightly different take on the problem addressed in +“<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 +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 +the column may end up pretty narrow in every row of the table, or it +may be wide enough that the table would run over the edge of the page; +however, we don’t want to make the column as wide as possible “just +in case”, by defining a fixed size for the table. We would like the +column to be as small as possible, but have the possibility to spread +to a maximum width and (if even that width is exceeded) turn into a +<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” +<i>array</i> package, i.e.: +<blockquote> +<pre> +\usepackage{array} +\usepackage{varwidth} +</pre> +</blockquote><p> +<i>varwidth</i> defines a new column-type “<code>V</code>”, which you +can use as follows: +<blockquote> +<pre> +\begin{tabular}{l V{3.5cm} r} + foo & blah & bar \\ + foo & blah blah & bar \\ +\end{tabular} +</pre> +</blockquote><p> +when the second column ends up less than 3.5cm wide; +or you can use it as follows: +<blockquote> +<pre> +\begin{tabular}{l V{3.5cm} r} + foo & blah & bar \\ + foo & blah blah & bar \\ + foo & blah blah blah blah blah blah + & bar \\ +\end{tabular} +</pre> +</blockquote><p> +where the second column will end up noticeably wider, and will wrap to +a second line in the third row. +<dl> +<dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) +<dt><tt><i>varwidth.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/varwidth.sty">macros/latex/contrib/misc/varwidth.sty</a> +</dl> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidcol">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidcol</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidth.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidth.html index 6738a5496d6..2ea18c72591 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidth.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidth.html @@ -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}{text</em><code>}</code> (which looks (almost) +<code>\</code><code>settominwidth[</code><em>min</em><code>]{</code><em>length</em><code>}{</code><em>text</em><code>}</code> (which looks (almost) like the standard <code>\</code><code>settowidth</code> command), and a <code>\</code><code>widthofpbox</code> function analagous to the <code>\</code><code>widthof</code> command for use with the <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> @@ -38,7 +38,7 @@ drawn from a joke <em>curriculum vitae</em>: \eqparbox{title}{\textbf{Lead Engineer}} \hfill \eqparbox{dates}{\textbf{9/92--12/94}} </pre> -</blockquote> +</blockquote><p> The code makes the three items on each of the heading lines have exactly the same width, so that the lines as a whole produce a regular pattern down the page. A command <code>\</code><code>eqboxwidth</code> allows you to use @@ -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-doc/doc/english/FAQ-en/html/FAQ-verbfile.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbfile.html index 75137f91bb4..ce82fb7b42c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbfile.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbfile.html @@ -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>\verbatiminput</code> that takes a file name as argument: <blockquote> @@ -11,10 +11,10 @@ argument: ... \verbatiminput{verb.txt} </pre> -</blockquote> +</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> @@ -24,14 +24,14 @@ finds: \input{verb.txt} \end{alltt} </pre> -</blockquote> +</blockquote><p> of course, this is little use for inputting (La)TeX source code... <p>The <i>moreverb</i> package extends the <i>verbatim</i> package, providing a <code>listing</code> environment and a <code>\</code><code>listinginput</code> command, which line-number the text of the file. The package also has a <code>\</code><code>verbatimtabinput</code> command, that honours TAB characters in -the input (the package'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): @@ -41,7 +41,7 @@ to the facilities of the <i>verbatim</i> package): ... \verbinput{verb.txt} </pre> -</blockquote> +</blockquote><p> <p>The <i>fancyvrb</i> package offers configurable implementations of everything <i>verbatim</i>, <i>sverb</i> and <i>moreverb</i> have, and more besides. It is nowadays the package of choice for the diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbwithin.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbwithin.html index 7f6a82228dc..988287f42ce 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbwithin.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbwithin.html @@ -1,47 +1,66 @@ <head> <title>UK TeX FAQ -- question label verbwithin</title> </head><body> -<h3>Why doesn't <code>\</code><code>verb</code> 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> has to assume that it is -getting the first look at its parameter text; if it isn't, TeX has -already assigned category codes so that <code>\</code><code>verb</code> doesn't have a +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 chance. For example: <blockquote> <pre> \verb+\error+ </pre> -</blockquote> -will work (typesetting '<code>\</code><code>error</code>'), but +</blockquote><p> +will work (typesetting ‘<code>\</code><code>error</code>’), but <blockquote> <pre> \newcommand{\unbrace}[1]{#1} \unbrace{\verb+\error+} </pre> -</blockquote> +</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 '<code>\</code><code>verb</code> -illegal in command argument'. +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> +\ifthenelse{\boolean{foo}}{% +\begin{verbatim} +foobar +\end{verbatim} +}{% +\begin{verbatim} +barfoo +\end{verbatim} +} +</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 +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> package will help: it doesn't suffer from the problems - of <code>\</code><code>verb</code>. -<li> If you're putting <code>\</code><code>verb</code> into the argument of a boxing + <a href="FAQ-setURL.html"><i>url</i> package</a> will help: it doesn’t suffer + from the problems of <code>\</code><code>verb</code>. +<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> @@ -53,7 +72,7 @@ necessary?". \end{lrbox} \fbox{\usebox{\mybox}} </pre> -</blockquote> +</blockquote><p> </ul> <p>Otherwise, there are three partial solutions to the problem. <ul> @@ -77,23 +96,23 @@ necessary?". (robust) command which expands to the verbatim argument given. <li> If you have a single character that is giving trouble (in its absence you could simply use <code>\</code><code>texttt</code>), consider using - <code>\</code><code>string</code>. <code>\</code><code>texttt{my<code>\</code><code>string</code>_</code>name} + <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: <blockquote> <pre> -\chardef\bs=`\_ +\chardef\us=`\_ ... -\section{... \texttt{my\bs name}} +\section{... \texttt{my\us name}} </pre> - </blockquote> - Such a definition is 'naturally' robust; the construction - "<<i>back-tick</i>><code>\</code><code><<i>char</i>></code>" may be used for any - troublesome character (though it's plainly not necessary for things + </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 like percent signs for which (La)TeX already provides robust macros). </ul> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertposfp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertposfp.html index 054d3f74454..0f2b1b7afb7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertposfp.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertposfp.html @@ -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 @@ -35,12 +35,12 @@ page, is a simple thing to do: \setlength{\@fptop}{0pt} \makeatother </pre> -</blockquote> +</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><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-doc/doc/english/FAQ-en/html/FAQ-vertspacefloat.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertspacefloat.html index fdd57cc787e..96ce6729283 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertspacefloat.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertspacefloat.html @@ -5,23 +5,26 @@ <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 surroundings; so if we have: +<blockquote> <pre> \begin{figure} \begin{center} \includegraphics{...} - \caption{...} + \caption{...} \end{center} \end{figure} </pre> +</blockquote><p> or worse still: +<blockquote> <pre> \begin{figure} \begin{center} @@ -30,20 +33,24 @@ or worse still: \caption{...} \end{figure} </pre> +</blockquote><p> unwarranted vertical space is going to appear. <p>The solution is to let the float and the objects in it position -themselves, and to use "generic" layout commands rather than their +themselves, and to use “generic” layout commands rather than their list-based encapsulations. +<blockquote> <pre> \begin{figure} - \centering \includegraphics{...} - \caption{...} + \centering + \includegraphics{...} + \caption{...} \end{figure} </pre> +</blockquote><p> (which even involves less typing). <p>This alternative code will work with any LaTeX package. It will not work with obsolete (pre-LaTeX2e) packages such as -<i>psfig</i> or <i>epsf</i> - 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-doc/doc/english/FAQ-en/html/FAQ-virtualfonts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-virtualfonts.html index 9a5416e4886..2e370d305c5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-virtualfonts.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-virtualfonts.html @@ -5,41 +5,58 @@ <p>Virtual fonts for TeX were first implemented by David Fuchs in the early days of TeX, but for most people they date from when Knuth redefined the format, and wrote some support software, in 1989 (he -published an article in <i>TUGboat</i> at the time, and a copy is -available on CTAN). -Virtual fonts provide a way of telling TeX about something more +published an article in <i>TUGboat</i> at the time, and a plain text +copy is available on CTAN). +<p>Virtual fonts provide a way of telling TeX about something more complicated than just a one-to-one character mapping. The entities you define in a virtual font look like characters to TeX (they appear with their sizes in a font metric file), but the DVI processor may -expand them to something quite different. You can use this facility -just to remap characters, to make a composite font with glyphs drawn -from several sources, or to build up an effect in arbitrarily -complicated ways - a virtual font may contain anything which is -legal in a DVI file. A "how to", describing how to generate -virtual fonts from scratch, is available. -<p>In practice, however, the most common use of virtual fonts is to remap -PostScript fonts (see <a href="FAQ-metrics.html">font metrics</a>). Other -interesting uses have been to build 'fake' maths fonts (by bundling -glyphs from several fonts together), and (utilising the facility to -use bits of DVI) to build useful subsets of the T1 fonts -using nothing but the PostScript Type 1 versions of Knuth's Computer Modern fonts. -<p>It is important to realise that TeX itself does <em>not</em> see -virtual fonts; for every virtual font read by the DVI driver there -is a corresponding TFM file read by TeX. Virtual fonts are normally -created in a single ASCII <code>vpl</code> (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. The -commonest way (nowadays) of generating <code>vpl</code> files is to use the +expand them to something quite different. +<p>Specifically, TeX itself only looks at a TFM file that +contains details of how the virtual font will appear: but of course, +TeX only cares about the metrics of a character, so its demands are +pretty small. The acro{DVI} processor, however, has to understand the +details of what is in the virtual font, so as to know “what to draw, +where”. So, for every virtual font read by a DVI driver, +there has to be a TFM file to be read by TeX. +(PDFTeX, of course, needs both the TFM and the +translation of the virtual font, since it does the whole job in the +one program.) +<p>You can use a virtual font: +<ul> +<li> simply just to remap the glyphs of a single font, +<li> to make a composite font with glyphs drawn from several + different onts, or +<li> to build up an effect in arbitrarily complicated ways (since a + virtual font may contain anything which is legal in a DVI + file). +</ul> +<p>In practice, the most common use of virtual fonts is to remap +Adobe Type 1 fonts (see <a href="FAQ-metrics.html">font metrics</a>), +though there has also been useful useful work building ‘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” versions 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, +describes the endless hours of fun that may be had, doing the job by +hand. Despite the pleasures to be had of the manual method, the +commonest way (nowadays) of generating VPL files is to use the <i>fontinst</i> package, which is described in detail together with the discussion of <a href="FAQ-metrics.html">PostScript font metrics</a>. -<i>qdtexvpl</i> is another utility for creating ad-hoc virtual -fonts. +<i>Qdtexvpl</i> is another utility for creating ad-hoc virtual +fonts (it uses TeX to parse a description of the virtual font, and +<i>qdtexvpl</i> itself processes the resulting DVI file). <dl> <dt><tt><i>fontinst</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.zip">fonts/utilities/fontinst</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/fontinst/">browse</a>) -<dt><tt><i>Knuth on virtual fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/virtual-fonts.knuth">info/virtual-fonts.knuth</a> -<dt><tt><i>Virtual fonts "how to"</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/virtualfontshowto/virtualfontshowto.txt">info/virtualfontshowto/virtualfontshowto.txt</a> +<dt><tt><i>Knuth on virtual fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/knuth/virtual-fonts">info/knuth/virtual-fonts</a> +<dt><tt><i>Virtual fonts “how to”</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/virtualfontshowto/virtualfontshowto.txt">info/virtualfontshowto/virtualfontshowto.txt</a> <dt><tt><i>qdtexvpl</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/qdtexvpl.zip">fonts/utilities/qdtexvpl</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/qdtexvpl.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/qdtexvpl/">browse</a>) </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=virtualfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=virtualfonts</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-watermark.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-watermark.html index 2059d454496..d04725819e0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-watermark.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-watermark.html @@ -1,29 +1,41 @@ <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 +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 +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 +<i>everypage</i> package to provide a simple interface for adding +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>, part of -Martin Schröder's <i>ms</i> bundle. <i>Eso-pic</i> attaches a +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>The <i>wallpaper</i> package builds, as above, on -<i>eso-pic</i>. Apart from the single-image backdrops described -above ("wallpapers", of course, to this package), the package -provides facilities for tiling images. All its commands come in -pairs: on for "general" use, and one applying to the current page only. +<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>draftcopy.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/draftcopy.zip">macros/latex/contrib/draftcopy</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/draftcopy.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/draftcopy/">browse</a>) +<dt><tt><i>draftwatermark.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/draftwatermark.zip">macros/latex/contrib/draftwatermark</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/draftwatermark.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/draftwatermark/">browse</a>) <dt><tt><i>eso-pic.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/eso-pic.zip">macros/latex/contrib/eso-pic</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/eso-pic.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/eso-pic/">browse</a>) +<dt><tt><i>everypage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/everypage.zip">macros/latex/contrib/everypage</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/everypage.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/everypage/">browse</a>) <dt><tt><i>everyshi.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse</a>) <dt><tt><i>wallpaper.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/wallpaper.zip">macros/latex/contrib/wallpaper</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/wallpaper.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/wallpaper/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wdnohyph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wdnohyph.html index 69af7d9e2c1..9eb25cbd83a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wdnohyph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wdnohyph.html @@ -2,33 +2,39 @@ <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> <pre> - \mbox{oddword} +\mbox{oddword} </pre> +</blockquote><p> (Plain TeX users should use <code>\</code><code>hbox</code>, and take care at the start of paragraphs.) However, boxing the word is not really advisable unless you are sure it only occurs once. <p>If the word occurs commonly, the best choice is to assert a non-hyphenation for it: +<blockquote> <pre> - \hyphenation{oddword} +\hyphenation{oddword} </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> <pre> - \usepackage[french,english]{babel} - \selectlanguage{english} - \hyphenation{oddword} - \selectlanguage{french} - \hyphenation{oddword} +\usepackage[french,english]{babel} +\selectlanguage{english} +\hyphenation{oddword} +\selectlanguage{french} +\hyphenation{oddword} </pre> +</blockquote><p> (note that <i>babel</i> will select the default language for the -document - English, in this case - at <code>\</code><code>begin{document}</code>.) +document — English, in this case — at <code>\</code><code>begin{document}</code>.) <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-doc/doc/english/FAQ-en/html/FAQ-webpkgs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-webpkgs.html index eb10baaef5a..3e471cbff85 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-webpkgs.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-webpkgs.html @@ -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-doc/doc/english/FAQ-en/html/FAQ-weirdhyphen.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-weirdhyphen.html index c9c1020324d..e1d747e3803 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-weirdhyphen.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-whatTeX.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatTeX.html index a992f2aea34..105c1eb31db 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatTeX.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatTeX.html @@ -7,21 +7,18 @@ 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 - and especially for books that contain a lot of mathematics</em>". +“<em>intended for the creation of beautiful books — and especially for books that contain a lot of mathematics</em>”. <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, +<p>Knuth developed a system of +‘<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 +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, @@ -35,7 +32,7 @@ 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. +When people say they’re “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=whatTeX">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatTeX</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatbst.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatbst.html new file mode 100644 index 00000000000..237543fb78f --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatbst.html @@ -0,0 +1,55 @@ +<head> +<title>UK TeX FAQ -- question label whatbst</title> +</head><body> +<h3>Choosing a bibliography style</h3> +<p>A large proportion of people are satisfied with one of Patashnik’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 +fields; but there are a very large number of contributed styles +available, that <em>do</em> support the format. +<p>(Note that author-date styles arose because the simple and clear +citation style that <i>plain</i> produces is so awkward in a +traditional manuscript preparation scenario. However, TeX-based +document production does away with all those difficulties, leaving us +free once again to use the simple option.) +<p>Fortunately, help is at hand, on the Web, with this problem: +<ul> +<li> a sample text, showing the sorts of style choices available, can + be found on + + + <a href="http://www.cs.stir.ac.uk/~kjt/software/latex/showbst.html">Ken Turner’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>”. +</ul> +<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 +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 +<i>my-style.bst</i>, the simple LaTeX document: +<blockquote> +<pre> +\documentclass{article} +\begin{document} +\bibliographystyle{my-style} +\nocite{*} +\bibliography{xampl} +\end{document} +</pre> +</blockquote><p> +will produce a representative sample of the citations the style will +produce. (Because <i>xampl.bib</i> is so extreme in some of its +“examples”, the BibTeX run will also give you an interesting +selection of BibTeX’s error messages\dots) +<dl> +<dt><tt><i>xampl.bib</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/distribs/doc/xampl.bib">biblio/bibtex/distribs/doc/xampl.bib</a> +</dl> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatbst">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatbst</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatenc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatenc.html index 63939eba348..aa0b55306ac 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatenc.html +++ b/Master/texmf-doc/doc/english/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>e</code>" has been input +command sequence “<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-doc/doc/english/FAQ-en/html/FAQ-whatpdftex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatpdftex.html new file mode 100644 index 00000000000..016b068fa76 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatpdftex.html @@ -0,0 +1,30 @@ +<head> +<title>UK TeX FAQ -- question label whatpdftex</title> +</head><body> +<h3>What is PDFTeX?</h3> +<p>PDFTeX has entered the main stream of TeX distributions: most +LaTeX and ConTeXt users nowadays use PDFTeX whether they know +it or not (more precisely, they use an amalgam of PDFTeX and +<a href="FAQ-etex.html">e-TeX</a>). So what is PDFTeX? +<p>PDFTeX is a development of TeX that is capable of generating +typeset PDF output in place of DVI. PDFTeX has +other capabilities, most notably in the area of fine typographic +detail (for example, its support for + <a href="FAQ-overfull.html">optimising line breaks</a>), + +but its greatest impact to date has been in the area of +PDF output. +<p>PDFTeX started as a topic for +Han The Thanh’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 +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 +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 +to maintain a stable platform for general use. +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatpdftex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatpdftex</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whereFAQ.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whereFAQ.html index b666a014a5e..f44d8ba7a39 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whereFAQ.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whereFAQ.html @@ -2,43 +2,60 @@ <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 auld lang syne. <p> + The sources of the present FAQ are available from CTAN. +<p>This FAQ and others are regularly mentioned, on +<i>comp.text.tex</i> and elsewhere, in a “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. +This is a document with (mostly rubbish) text formatted so as to +highlight things we discuss here, and providing Acrobat hyper-links to +the relevant answers in this FAQ on the Web. The visual +FAQ is provided in PDF format, on CTAN; it works +best using Adobe Acrobat Reader 7 (or later); some features are +missing with other readers, or with earlier versions of Acrobat Reader <p>Another excellent information source, available in English, is the <a href="http://tex.loria.fr">(La)TeX navigator</a>. <p>Both the Francophone TeX usergroup Gutenberg and the Czech/Slovak usergroup 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> -<p>Other non-English FAQs are available: +<p>Other non-English FAQs are available (off-CTAN): <dl> <dt>German<dd>Posted regularly to <i>de.comp.tex</i>, and archived on CTAN; the FAQ also appears at <a href="http://www.dante.de/faq/de-tex-faq/">http://www.dante.de/faq/de-tex-faq/</a> -<dt>French<dd>Posted regularly to <i>fr.comp.text.tex</i>, and - archived on CTAN. +<dt>French<dd>An interactive (full-screen!) FAQ may be found at + <a href="http://www.frenchpro6.com/screen.pdf/FAQscreen.pdf">http://www.frenchpro6.com/screen.pdf/FAQscreen.pdf</a>, and a copy + for printing at <a href="http://frenchle.free.fr/FAQ.pdf">http://frenchle.free.fr/FAQ.pdf</a>; + A FAQ used to be posted regularly to + <i>fr.comp.text.tex</i>, and is archived on CTAN — + sadly, that effort seems to have fallen by the wayside. <dt>Spanish<dd>See <a href="http://apolo.us.es/CervanTeX/FAQ/">http://apolo.us.es/CervanTeX/FAQ/</a> <dt>Czech<dd>See <a href="http://www.fi.muni.cz/cstug/csfaq/">http://www.fi.muni.cz/cstug/csfaq/</a> </dl> +<p>Resources available on CTAN are: <dl> <dt><tt><i>Dante FAQ</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/help/de-tex-faq.zip">help/de-tex-faq</a> (<a href="ftp://cam.ctan.org/tex-archive/help/de-tex-faq.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/de-tex-faq/">browse</a>) <dt><tt><i>French FAQ</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/help/LaTeX-FAQ-francaise.zip">help/LaTeX-FAQ-francaise</a> (<a href="ftp://cam.ctan.org/tex-archive/help/LaTeX-FAQ-francaise.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/LaTeX-FAQ-francaise/">browse</a>) <dt><tt><i>Sources of this FAQ</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.zip">help/uk-tex-faq</a> (<a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/">browse</a>) <dt><tt><i>Obsolete <code>comp.text.tex</code> FAQ</i></tt><dd> <a href="ftp://cam.ctan.org/tex-archive/obsolete/help/TeX,_LaTeX,_etc.:_Frequently_Asked_Questions_with_Answers">obsolete/help/TeX,_LaTeX,_etc.:_Frequently_Asked_Questions_with_Answers</a> +<dt><tt><i>The visual FAQ</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/visualFAQ/visualFAQ.pdf">info/visualFAQ/visualFAQ.pdf</a> </dl> <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whereFAQ">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whereFAQ</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wherefiles.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wherefiles.html index 95e890fa1ad..a3c090f3880 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wherefiles.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wherefiles.html @@ -5,7 +5,7 @@ <p>Where precisely you put files that you have downloaded does depend on what TeX distribution you have. However, assuming that you have one of the modern TDS-compliant -distributions (such as teTeX, fpTeX or mikTeX) there are +distributions (such as teTeX or MiKTeX) there are some general rules that you can follow: <p> @@ -17,7 +17,7 @@ tree. The root directory will be named something like: teTeX: /usr/share/texmf-local/ or /usr/local/share/texmf/ fpTeX: c:\Programs\TeXLive\texmf-local\ - mikTeX: c:\localtexmf\ + MiKTeX: c:\localtexmf\ </pre> (In fact, a teTeX system can be asked to tell you what its local root is; on a Unix system, the command to use is: @@ -25,9 +25,9 @@ root is; on a Unix system, the command to use is: <pre> kpsewhich -expand-var "\$TEXMFLOCAL" </pre> -</blockquote> +</blockquote><p> the output being the actual path.) -<p>Let's write <code>$TEXMF</code> for this root, whatever it is for your system. +<p>Let’s write <code>$TEXMF</code> for this root, whatever it is for your system. <p> (2) In your local texmf tree, imitate the directory structure in your main tree. Here are some examples of where files of given extensions @@ -41,33 +41,34 @@ should go: .afm: $TEXMF/fonts/afm/<supplier>/<font>/ .pfb: $TEXMF/fonts/type1/<supplier>/<font>/ .ttf: $TEXMF/fonts/truetype/<supplier>/<font>/ +.pool, .fmt, .base or .mem: $TEXMF/web2c </pre> -and for modern systems (teTeX 3.0, and the like, using TDS -v1.1 format): +and for modern systems (distributed in 2005 or later, such as +teTeX 3.0, using TDS v1.1 layouts): <pre> .map: $TEXMF/fonts/map/<syntax>/<bundle>/ .enc: $TEXMF/fonts/enc/<syntax>/<bundle>/ </pre> Where of course <<i>package</i>>, <<i>font</i>> and <<i>supplier</i>> depend -upon what's appropriate for the individual file. The <<i>syntax</i>> +upon what’s appropriate for the individual file. The <<i>syntax</i>> (for <code>.map</code> and <code>.enc</code> files) is a categorisation based -on the way the files are written; typically, it's the name of a +on the way the files are written; typically, it’s the name of a program such as <i>dvips</i> or <i>pdftex</i>. -<p>"Straight" (La)TeX input can take other forms than the <code>.sty</code>, +<p>“Straight” (La)TeX input can take other forms than the <code>.sty</code>, <code>.cls</code> or <code>.fd</code> listed above, too. Examples are <code>.sto</code> and <code>.clo</code> for package and class options, <code>.cfg</code> for configuration information, and so on. <p>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>Some packages have configuration files (commonly with file suffix <code>.cfg</code>), and occasionally other run-time files. The package documentation <em>should</em> mention these things, but sometimes -doesn't. A common exception is the <code>.drv</code> file, used by some +doesn’t. A common exception is the <code>.drv</code> file, used by some packages as part of the documentation building process; this is a hang-over from the pre-LaTeX2e predecessor of the package documentation process. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wholerow.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wholerow.html index bbd705eaba6..56c88778cb5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wholerow.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wholerow.html @@ -21,8 +21,8 @@ than columns. So, we set things up by: #1\ignorespaces } </pre> -</blockquote> -Now, we put '<code>$</code>' before the first column specifier; and we put '<code>^</code>' +</blockquote><p> +Now, we put ‘<code>$</code>’ before the first column specifier; and we put ‘<code>^</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> @@ -37,10 +37,10 @@ the start of each row we want to modify: Meek & mild & entry \\ \hline \end{tabular} </pre> -</blockquote> +</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="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-why-inp-font.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-why-inp-font.html index 25dc57c68af..84e67750a80 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-why-inp-font.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-whyfree.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whyfree.html index e29c1a339e0..1eacd739f63 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whyfree.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-widefigs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widefigs.html index 99e73381c25..8dc654619f7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widefigs.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-widows.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widows.html index e499936e390..d6275c61b16 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widows.html +++ b/Master/texmf-doc/doc/english/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-doc/doc/english/FAQ-en/html/FAQ-wordcount.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wordcount.html index 116a7e58116..009eb58bd82 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wordcount.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wordcount.html @@ -13,21 +13,21 @@ 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... <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 </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. -<p>Simply stripping (La)TeX markup isn't entirely reliable, however: +<p>Simply stripping (La)TeX markup isn’t entirely reliable, however: that markup itself may contribute typeset words, and this could be a problem. The <i>wordcount</i> package contains a Bourne shell (i.e., typically Unix) script for running a diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-writecls.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-writecls.html index bb3d69069d1..846e1509a5e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-writecls.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-writecls.html @@ -2,17 +2,17 @@ <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 -<a href="FAQ-tutorials.html">TeX by topic</a> are relevant. With good TeX +<a href="FAQ-ol-books.html">TeX by topic</a> are relevant. With good TeX knowledge it is possible to use the documented source of LaTeX as reference material (dedicated authors will acquaint themselves with the source as a matter of course). A complete set of the documented @@ -20,13 +20,18 @@ source of LaTeX may be prepared by processing the file <i>source2e.tex</i> in the LaTeX distribution, but individual files in the distribution may be processed separately with LaTeX, like any well-constructed <a href="FAQ-dtx.html"><code>.dtx</code> file</a>. -<p>Writing good classes is not easy; it'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://www.tug.org/pracjourn/2006-4/flynn/flynn.pdf">annotated version of <i>article</a></i>, +as it appears in <i>classes.dtx</i>, was published in the PracTeX +Journal 2006, No. 4. The article is by Peter Flynn, and offers a +slightly easier way in to understanding <i>classes.dtx</i> <dl> <dt><tt><i>classes.dtx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/base/classes.dtx">macros/latex/base/classes.dtx</a> <dt><tt><i>ltxguide.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/base/ltxguide.cls">macros/latex/base/ltxguide.cls</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wrongpn.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wrongpn.html index 6e6a7177610..6eb4a8d9fe4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wrongpn.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wrongpn.html @@ -3,37 +3,37 @@ </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 set its value +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> <pre> Here is page \thepage{}. </pre> -</blockquote> +</blockquote><p> you should write: <blockquote> <pre> Here is page \pageref{here}\label{here}. </pre> -</blockquote> +</blockquote><p> (note: no space between the <code>\</code><code>pageref</code> and the <code>\</code><code>label</code>, since that could potentially end up as a page-break space itself, which rather defeats the purpose of the exercise!). -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wrongpn">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wrongpn</a> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wrongpn">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wrongpn</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xetex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xetex.html index 6a172fd554c..8e28391e537 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xetex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xetex.html @@ -5,19 +5,11 @@ <p>XeTeX (by Jonathan Kew) is a successor to the shareware TeX/GX program. It is a Unicode-based (UTF-8) TeX implementation which is able to make use of Mac OS X AAT (Apple Advanced Typography) -<code>.dfonts</code> and OpenType fonts. It uses Apple's Quartz system +<code>.dfonts</code> and OpenType fonts. It uses Apple’s Quartz system (which facilitates the afore-mentioned font access) to generate PDF output. -<p>XeTeX requires Mac OS {X} 10.3 "Panther" or later (although -there has been some success using earlier versions). It is -especially oriented towards multi-lingual typography, taking advantage -of Apple's keyboard input systems and system font support for various -languages. -<p>The system is able to make use of Gerben Wierda's TeX for -Mac OS X setup, but a minimal set of TeX support files is -also available, making an attractive proposition for those with -limited bandwidth who are inclined to use Plain TeX. It can be -installed using Apple's Installer, or as an i-Installer package. +<p>A Linux version has been announced (2006); that version of course +can’t use AAT fonts, and relies on OpenType fonts alone. <p>The project has a <a href="http://scripts.sil.org/xetex">web site</a> for the user who wants more than this simple answer, and you can also sign up to a <a href="http://www.tug.org/mailman/listinfo/xetex">mailing list</a>. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xspace.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xspace.html index a7d0593c9d0..e3cc9c77a6a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xspace.html +++ b/Master/texmf-doc/doc/english/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> @@ -38,17 +38,17 @@ usage would of course be completely pointless; but you can incorporate and we find \restenergy available to us... </pre> -</blockquote> +</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="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-y2k.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-y2k.html index b5fc2cd1ff3..db789c10e78 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-y2k.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-y2k.html @@ -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> @@ -35,8 +35,7 @@ system that is not itself Y2K compliant. <dt>Macros:<dd> TeX macros can in principle perform calculations on the basis of the value of <code>\</code><code>year</code>. - The <a href="FAQ-latex.html">LaTeX</a> suite - + The <a href="FAQ-latex.html">LaTeX suite</a> performs such calculations in a small number of places; the calculations performed in the current (supported) version of LaTeX are known to be Y2K compliant. @@ -44,5 +43,5 @@ <dt>External software:<dd> Software such as DVI translators needs to be individually checked. </dl> -<p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=y2k">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=y2k</a> +<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=y2k">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=y2k</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-zerochap.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-zerochap.html index 131d3b9f649..fc4378c261a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-zerochap.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-zerochap.html @@ -3,16 +3,16 @@ </head><body> <h3>Why are my sections numbered 0.1 ...?</h3> <p>This happens when your document is using the standard <i>book</i> or -<i>report</i> class (or one similar), and you'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-doc/doc/english/FAQ-en/html/index.html b/Master/texmf-doc/doc/english/FAQ-en/html/index.html index ebf0394140e..5af2930d83c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/index.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/index.html @@ -1,21 +1,47 @@ - -<h1 align="center">Welcome to the UK List of<br> - TeX Frequently Asked Questions</h1> <h2>Introduction</h2> -<p>This FAQ was originated by the Committee of the UK TeX -Users' Group (UK TUG) as a development of a regular +<p>This is a set of Frequently Asked Questions (FAQ) for +English-speaking users of TeX. The questions answered here cover a +wide range of topics, but the actual typesetting issues are mostly +covered from the viewpoint of a LaTeX user. +<p>You may use the FAQ +<ul> +<li> by reading a printed document, +<li> by browsing a PDF file: copies, with hyperlinks to assist + browsing, are to be found on CTAN at <a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq/newfaq.pdf">help/uk-tex-faq/newfaq.pdf</a> + (formatted for A4 paper) or at <a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq/letterfaq.pdf">help/uk-tex-faq/letterfaq.pdf</a> (formatted for + North American “letter” paper), 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 \CTANhref{visualFAQ}{Visual FAQ}. +</ul> +<p> +<b>Caveat: Acquiring files</b> +<p>Most answers in this FAQ provide links for downloading +software; a large proportion of these links direct you to entire +directories on the CTAN archives. Unfortunately, some browsers +issue a sequence of commands that causes CTAN servers to deny +the existence of compressed archive files of the directory, that the +server would be happy to create “on the fly”. The FAQ +therefore offers three possible links for downloading directories +(that aren’t already designated “browse only”): the links give you +<code>.zip</code> and <code>.tar.gz</code> archives, and a link for browsing +the directory. +<p>Fortunately, CTAN is switching to statically-generated +directory archive files; many directories mentioned in this FAQ +will also exist as <code>.zip</code> files on the archives, and won’t fall +foul of the browser problem. Of course, if the <code>.zip</code> file +does not exist, and the browser is playing up, you will need to use +the “browse” link. +<p> +<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 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 remains. -<p> -<p>An alternative HTML version of the FAQ may -be found in <a href="FAQ-CD.html">TeX Live</a>. -<p> A copy of the complete FAQ, in PDF with hyperlinks to - assist browsing, may be found on - <a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq/newfaq.pdf">help/uk-tex-faq/newfaq.pdf</a> (formatted for A4 paper) or - <a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq/letterfaq.pdf">help/uk-tex-faq/letterfaq.pdf</a> (formatted for North American "letter" - paper). +original, and little of Bodenheimer’s work now remains. <p>Most members of the committee of UK TUG, over the years since 1994, have contributed to this FAQ to some extent. The following people, who have never been members of the committee, have @@ -28,8 +54,10 @@ Charles Cameron, Damian Cugley, Michael Dewey, Michael Downes, +Jean-Pierre Drucbert, Thomas Esser, Ulrike Fischer, + Anthony Goreham, Norman Gray, Eitan Gurari, @@ -41,7 +69,8 @@ Berthold Horn, Ian Hutchinson, Werner Icking, Regnor Jernsletten, -David Kastrup, +David Kastrup, +Oleg Katsitadze, Isaac Khabaza, Ulrich Klauer, Markus Kohm, @@ -50,6 +79,8 @@ Daniel Luecking, Sanjoy Mahajan, Andreas Matthias, Brooks Moses, +Iain Murray, +Vilar Camara Neto, Ted Nieland, Hans Nordhaug, @@ -58,6 +89,7 @@ Heiko Oberdiek, Piet van Oostrum, Scott Pakin, Oren Patashnik, +Steve Peter, Philip Ratcliffe, José Carlos Santos, Walter Schmidt, @@ -71,36 +103,19 @@ Chris Walker, Peter Wilson, Rick Zaccone and Reinhard Zierke. -<p><p> -<b>Caveat: Acquiring files</b> -<p>Most answers in this FAQ provide links for downloading -software; a large proportion of these links direct you to entire -directories on the CTAN archives. Unfortunately, some browsers -issue a sequence of commands that causes CTAN servers to deny -the existence of compressed archive files of the directory, that the -server would be happy to create "on the fly". The FAQ -therefore offers three possible links for downloading directories -(that aren't already designated "browse only"): the links give you -<code>.zip</code> and <code>.tar.gz</code> archives, and a link for browsing -the directory. -<p>Fortunately, CTAN is switching to statically-generated -directory archive files; many directories mentioned in this FAQ -will also exist as <code>.zip</code> files on the archives, and won't fall -foul of the browser problem. Of course, if the <code>.zip</code> file -does not exist, and the browser is playing up, you will need to use -the "browse" link. -<p> <p> <p><h3>The Background</h3><ul> <li><a href="FAQ-whatTeX.html">What is TeX?</a> -<li><a href="FAQ-TeXpronounce.html">How should I pronounce "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-triptrap.html">How can I be sure it's really TeX?</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> @@ -108,7 +123,7 @@ the "browse" link. <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> @@ -117,35 +132,45 @@ the "browse" link. <li><a href="FAQ-books.html">Books on TeX and its relations</a> <li><a href="FAQ-typebooks.html">Books on Type</a> <li><a href="FAQ-whereFAQ.html">Where to find FAQs</a> -<li><a href="FAQ-maillists.html">Where to get help</a> +<li><a href="FAQ-gethelp.html">How to get help</a> +<li><a href="FAQ-mailliststar.html">Specialist mailing lists</a> <li><a href="FAQ-askquestion.html">How to ask a question</a> -<li><a href="FAQ-minxampl.html">How to make a "minimum example"</a> -<li><a href="FAQ-tutorials.html">(La)TeX Tutorials, etc.</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> +<li><a href="FAQ-tutbitslatex.html">Specialised (La)TeX tutorials</a> +<li><a href="FAQ-ref-doc.html">Reference documents</a> +<li><a href="FAQ-doc-wiki.html">WIKI pages for TeX and friends</a> +<li><a href="FAQ-typo-style.html">Typography tutorials</a> +<li><a href="FAQ-doc-dirs.html">Directories of (La)TeX information</a> +<li><a href="FAQ-ol-books.html">Freely available (La)TeX books</a> <li><a href="FAQ-pkgdoc.html">Documentation of packages</a> <li><a href="FAQ-writecls.html">Learning to write LaTeX classes and packages</a> <li><a href="FAQ-mfptutorials.html">Metafont and MetaPost Tutorials</a> <li><a href="FAQ-BibTeXing.html">BibTeX Documentation</a> <li><a href="FAQ-symbols.html">Where can I find the symbol for ...</a> <li><a href="FAQ-docpictex.html">The PiCTeX manual</a> -</ul><h3>Bits and pieces of TeX</h3><ul> +</ul><h3>Bits and pieces of (La)TeX</h3><ul> <li><a href="FAQ-dvi.html">What is a DVI file?</a> <li><a href="FAQ-driver.html">What is a driver?</a> <li><a href="FAQ-pk.html">What are PK files?</a> <li><a href="FAQ-tfm.html">What are TFM files?</a> <li><a href="FAQ-virtualfonts.html">Virtual fonts</a> <li><a href="FAQ-specials.html"><code>\</code><code>special</code> commands</a> +<li><a href="FAQ-hyphen.html">How does hyphenation work in TeX?</a> +<li><a href="FAQ-clsvpkg.html">What are LaTeX classes and packages?</a> <li><a href="FAQ-dtx.html">Documented LaTeX sources (<code>.dtx</code> files)</a> <li><a href="FAQ-whatenc.html">What are encodings?</a> -<li><a href="FAQ-hyphen.html">How does hyphenation work in TeX?</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"</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-nonfree.html">What's the CTAN <code>nonfree</code> tree?</a> +<li><a href="FAQ-nonfree.html">What’s the CTAN <code>nonfree</code> tree?</a> <li><a href="FAQ-uploads.html">Contributing a file to the archives</a> <li><a href="FAQ-findfiles.html">Finding (La)TeX files</a> <li><a href="FAQ-findfont.html">Finding new fonts</a> @@ -157,7 +182,7 @@ the "browse" link. </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> @@ -169,7 +194,7 @@ the "browse" link. <li><a href="FAQ-lit.html">What is Literate Programming?</a> <li><a href="FAQ-webpkgs.html">WEB systems for various languages</a> </ul><h3>Format conversions</h3><ul> -<li><a href="FAQ-toascii.html">Conversion from (La)TeX to plain ASCII</a> +<li><a href="FAQ-toascii.html">Conversion from (La)TeX to plain text</a> <li><a href="FAQ-SGML2TeX.html">Conversion from SGML or HTML to TeX</a> <li><a href="FAQ-LaTeX2HTML.html">Conversion from (La)TeX to HTML</a> <li><a href="FAQ-fmtconv.html">Other conversions to and from (La)TeX</a> @@ -179,9 +204,9 @@ the "browse" link. </ul><h3>Installing (La)TeX files</h3><ul> <li><a href="FAQ-instpackages.html">Installing a new package</a> <li><a href="FAQ-wherefiles.html">Where to put new files</a> -<li><a href="FAQ-miktexinst.html">Installing MiKTeX "known packages"</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-miktexinst.html">Installing MiKTeX “known packages”</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> @@ -192,37 +217,41 @@ the "browse" link. <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> <li><a href="FAQ-psfontprob.html">Deploying Type 1 fonts</a> <li><a href="FAQ-psfchoice.html">Choice of scalable outline fonts</a> <li><a href="FAQ-charshift.html">Weird characters in <i>dvips</i> output</a> +</ul><h4>Macros for using fonts</h4><ul> +<li><a href="FAQ-fonts-pln.html">Using non-standard fonts in Plain TeX</a> </ul><h4>Particular font families</h4><ul> -<li><a href="FAQ-concrete.html">Using the "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> -<li><a href="FAQ-acrobat.html">Making Acrobat documents from LaTeX</a> +<li><a href="FAQ-acrobat.html">Making Acrobat PDF documents from (La)TeX</a> <li><a href="FAQ-dvips-pdf.html">Quality of PDF from PostScript</a> <li><a href="FAQ-fuzzy-type3.html">The wrong type of fonts in PDF</a> <li><a href="FAQ-fuzzy-gs.html">Fuzzy fonts because <i>Ghostscript</i> too old</a> <li><a href="FAQ-fuzzy-T1.html">Fonts go fuzzy when you switch to T1</a> <li><a href="FAQ-distill-prob.html">Characters missing from PDF output</a> -<li><a href="FAQ-type1T1.html">Finding '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> </ul><h3>Graphics</h3><ul> <li><a href="FAQ-impgraph.html">How to import graphics into (La)TeX documents</a> <li><a href="FAQ-dvipsgraphics.html">Imported graphics in <i>dvips</i></a> <li><a href="FAQ-pdftexgraphics.html">Imported graphics in PDFLaTeX</a> <li><a href="FAQ-dvipdfmgraphics.html">Imported graphics in <i>dvipdfm</i></a> -<li><a href="FAQ-graphicspath.html">Importing graphics from "somewhere else"</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> <li><a href="FAQ-topgraph.html">Top-aligning imported graphics</a> -<li><a href="FAQ-mpprologues.html">Making MetaPost output display in <i>ghostscript</i></a> +<li><a href="FAQ-mpprologues.html">Displaying MetaPost output in <i>ghostscript</i></a> <li><a href="FAQ-drawing.html">Drawing with TeX</a> <li><a href="FAQ-drawFeyn.html">Drawing Feynman diagrams in LaTeX</a> <li><a href="FAQ-labelfig.html">Labelling graphics</a> @@ -232,15 +261,16 @@ the "browse" link. <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">Transcribed 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> <li><a href="FAQ-bibinline.html">Putting bibliography entries in text</a> @@ -249,8 +279,9 @@ the "browse" link. <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> <li><a href="FAQ-nocitestar.html">Listing all your BibTeX entries</a> <li><a href="FAQ-htmlbib.html">Making HTML of your Bibliography</a> @@ -258,12 +289,13 @@ the "browse" link. </ul><h4>Alternative document classes</h4><ul> <li><a href="FAQ-replstdcls.html">Replacing the standard classes</a> <li><a href="FAQ-slidecls.html">Producing slides</a> +<li><a href="FAQ-poster.html">Creating posters with LaTeX</a> <li><a href="FAQ-thesis.html">Formatting a thesis in LaTeX</a> <li><a href="FAQ-journalpaper.html">Setting papers for journals</a> -<li><a href="FAQ-multidoc.html">A 'report' from lots of 'article's</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> @@ -277,15 +309,18 @@ the "browse" link. <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">Printer paper sizes</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-nopageno.html">How to get rid of page numbers</a> <li><a href="FAQ-psatempty.html"><code>\pagestyle{empty}</code> on first page in LaTeX</a> <li><a href="FAQ-crop.html">How to create crop marks</a> -<li><a href="FAQ-watermark.html">'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> @@ -312,7 +347,7 @@ the "browse" link. <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> @@ -334,6 +369,7 @@ the "browse" link. <li><a href="FAQ-limits.html">Sub- and superscript positioning for operators</a> <li><a href="FAQ-mathstext.html">Text inside maths</a> <li><a href="FAQ-reuseq.html">Re-using an equation</a> +<li><a href="FAQ-brkinline.html">Line-breaking in in-line maths</a> </ul><h4>Lists</h4><ul> <li><a href="FAQ-enumerate.html">Fancy enumeration lists</a> <li><a href="FAQ-complist.html">How to reduce list spacing</a> @@ -341,6 +377,7 @@ the "browse" link. </ul><h4>Tables, figures and diagrams</h4><ul> <li><a href="FAQ-destable.html">The design of tables</a> <li><a href="FAQ-fixwidtab.html">Fixed-width tables</a> +<li><a href="FAQ-varwidcol.html">Variable-width columns in tables</a> <li><a href="FAQ-struttab.html">Spacing lines in tables</a> <li><a href="FAQ-longtab.html">Tables longer than a single page</a> <li><a href="FAQ-tabcellalign.html">How to alter the alignment of tabular cells</a> @@ -362,22 +399,22 @@ the "browse" link. <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> </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 <i>Subversion</i></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> @@ -392,14 +429,14 @@ the "browse" link. <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> </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-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> @@ -411,36 +448,38 @@ the "browse" link. <li><a href="FAQ-empty.html">Detecting that something is empty</a> <li><a href="FAQ-ifpdf.html">Am I using PDFTeX?</a> <li><a href="FAQ-subverttoks.html">Subverting a token register</a> +<li><a href="FAQ-isdef.html">Is this command defined?</a> </ul><h4>LaTeX macro tools and techniques</h4><ul> <li><a href="FAQ-plninltx.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> -</ul><h4>LaTeX macro techniques</h4><ul> -<li><a href="FAQ-fixnam.html">How to change LaTeX's "fixed names"</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-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> </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-missssymb.html">Missing symbol commands</a> <li><a href="FAQ-msxy.html">Where are the <code>msx</code> and <code>msy</code> fonts?</a> @@ -449,56 +488,59 @@ the "browse" link. </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 <code>\</code><code>verb</code> 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-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-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> </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> -</ul><h4>Why shouldn't I?</h4><ul> +<li><a href="FAQ-gutter.html">Why is the inside margin so narrow?</a> +</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-2letterfontcmd.html">What’s wrong with <code>\</code><code>bf</code>, <code>\</code><code>it</code>, etc.?</a> +<li><a href="FAQ-newfont.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-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-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-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> @@ -507,33 +549,31 @@ the "browse" link. <li><a href="FAQ-manymathalph.html">Too many math alphabets</a> <li><a href="FAQ-ouparmd.html">Not in outer par mode</a> <li><a href="FAQ-errmissitem.html">Perhaps a missing <code>\</code><code>item</code>?</a> +<li><a href="FAQ-errparnum.html">Illegal parameter number in definition</a> +<li><a href="FAQ-fllost.html">Float(s) lost</a> +<li><a href="FAQ-optionclash.html">Option clash for package</a> </ul><h3>Current TeX-related projects</h3><ul> <li><a href="FAQ-LaTeX3.html">The LaTeX3 project</a> -<li><a href="FAQ-omega.html">The Omega project</a> -<li><a href="FAQ-NTS.html">The <i>NTS</i> project</a> -<li><a href="FAQ-pdftex.html">The PDFTeX project</a> -<li><a href="FAQ-mathml.html">Future WEB technologies and (La)TeX</a> +<li><a href="FAQ-mathml.html">Future WWW technologies and (La)TeX</a> <li><a href="FAQ-textrace.html">Making outline fonts from Metafont</a> <li><a href="FAQ-WYGexpts.html">The TeX document preparation environment</a> <li><a href="FAQ-ant.html">The ANT typesetting system</a> -<li><a href="FAQ-aleph.html">The Aleph project</a> <li><a href="FAQ-extex.html">The ExTeX project</a> +<li><a href="FAQ-omegaleph.html">Omega and Aleph</a> +<li><a href="FAQ-luatex.html">PDFTeX becomes LUATeX</a> <li><a href="FAQ-xetex.html">The XeTeX project</a> -</ul><h3>You're still stuck?</h3><ul> -<li><a href="FAQ-noans.html">You don't understand the answer</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> </ul> <hr><address> - Maintenance of the - <a href="http://www.tex.ac.uk/faq">TeX FAQ</a> - is coordinated by Robin Fairbairns.<p> Comments, suggestions, or error reports? -- see "<a href="FAQ-noans.html">Improving the FAQ</a>" or "<a href="FAQ-newans.html">Extending the FAQ</a>". <p> - This is FAQ version 3.14a, last modified on 2005/07/07. + This is FAQ version 3.16c, last modified on 2006-12-11. </address> diff --git a/Master/texmf-doc/doc/english/FAQ-en/newfaq.aux b/Master/texmf-doc/doc/english/FAQ-en/newfaq.aux index 515b174ce23..29097f8aa7d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/newfaq.aux +++ b/Master/texmf-doc/doc/english/FAQ-en/newfaq.aux @@ -33,8 +33,8 @@ \newlabel{Q-AMSpkg}{{15}{8}} \@writefile{toc}{\contentsline {question}{\numberline {16}What is Eplain{}?}{8}} \newlabel{Q-eplain}{{16}{8}} -\@writefile{toc}{\contentsline {question}{\numberline {17}What is Lollipop?}{8}} -\newlabel{Q-lollipop}{{17}{8}} +\@writefile{toc}{\contentsline {question}{\numberline {17}What is Lollipop?}{9}} +\newlabel{Q-lollipop}{{17}{9}} \@writefile{toc}{\contentsline {question}{\numberline {18}What is Texinfo?}{9}} \newlabel{Q-texinfo}{{18}{9}} \@writefile{toc}{\contentsline {question}{\numberline {19}If \TeX {} is so good, how come it's free?}{9}} @@ -43,8 +43,8 @@ \newlabel{Q-TeXfuture}{{20}{9}} \@writefile{toc}{\contentsline {question}{\numberline {21}Reading (La)\TeX {} files}{9}} \newlabel{Q-readtex}{{21}{9}} -\@writefile{toc}{\contentsline {question}{\numberline {22}Why is \TeX {} not a \WYSIWYG {} system?}{9}} -\newlabel{Q-notWYSIWYG}{{22}{9}} +\@writefile{toc}{\contentsline {question}{\numberline {22}Why is \TeX {} not a \WYSIWYG {} system?}{10}} +\newlabel{Q-notWYSIWYG}{{22}{10}} \@writefile{toc}{\contentsline {question}{\numberline {23}\TeX {} User Groups}{10}} \newlabel{Q-TUG*}{{23}{10}} \@writefile{toc}{\contentsline {section}{\numberline {C}Documentation and Help}{10}} @@ -90,11 +90,11 @@ \newlabel{Q-BibTeXing}{{43}{17}} \@writefile{toc}{\contentsline {question}{\numberline {44}Where can I find the symbol for\,\dots {}}{17}} \newlabel{Q-symbols}{{44}{17}} -\@writefile{toc}{\contentsline {question}{\numberline {45}The PiC\TeX {} manual}{17}} -\newlabel{Q-docpictex}{{45}{17}} -\@writefile{toc}{\contentsline {section}{\numberline {D}Bits and pieces of (La)\TeX {}}{17}} -\@writefile{toc}{\contentsline {question}{\numberline {46}What is a \acro {DVI} file?}{17}} -\newlabel{Q-dvi}{{46}{17}} +\@writefile{toc}{\contentsline {question}{\numberline {45}The PiC\TeX {} manual}{18}} +\newlabel{Q-docpictex}{{45}{18}} +\@writefile{toc}{\contentsline {section}{\numberline {D}Bits and pieces of (La)\TeX {}}{18}} +\@writefile{toc}{\contentsline {question}{\numberline {46}What is a \acro {DVI} file?}{18}} +\newlabel{Q-dvi}{{46}{18}} \@writefile{toc}{\contentsline {question}{\numberline {47}What is a driver?}{18}} \newlabel{Q-driver}{{47}{18}} \@writefile{toc}{\contentsline {question}{\numberline {48}What are \acro {PK} files?}{18}} @@ -103,8 +103,8 @@ \newlabel{Q-tfm}{{49}{18}} \@writefile{toc}{\contentsline {question}{\numberline {50}Virtual fonts}{18}} \newlabel{Q-virtualfonts}{{50}{18}} -\@writefile{toc}{\contentsline {question}{\numberline {51}\csx {special} commands}{18}} -\newlabel{Q-specials}{{51}{18}} +\@writefile{toc}{\contentsline {question}{\numberline {51}\csx {special} commands}{19}} +\newlabel{Q-specials}{{51}{19}} \@writefile{toc}{\contentsline {question}{\numberline {52}How does hyphenation work in \TeX {}?}{19}} \newlabel{Q-hyphen}{{52}{19}} \@writefile{toc}{\contentsline {question}{\numberline {53}What are La\TeX {} classes and packages?}{19}} @@ -121,8 +121,8 @@ \newlabel{Q-eps}{{58}{21}} \@writefile{toc}{\contentsline {question}{\numberline {59}Adobe font formats}{21}} \newlabel{Q-adobetypen}{{59}{21}} -\@writefile{toc}{\contentsline {question}{\numberline {60}What are ``resolutions''}{21}} -\newlabel{Q-resolns}{{60}{21}} +\@writefile{toc}{\contentsline {question}{\numberline {60}What are ``resolutions''}{22}} +\newlabel{Q-resolns}{{60}{22}} \@writefile{toc}{\contentsline {question}{\numberline {61}What is the ``Berry naming scheme''}{22}} \newlabel{Q-fontname}{{61}{22}} \@writefile{toc}{\contentsline {section}{\numberline {E}Acquiring the Software}{22}} @@ -130,14 +130,14 @@ \newlabel{Q-archives}{{62}{22}} \@writefile{toc}{\contentsline {question}{\numberline {63}What's the \acro {CTAN} \texttt {nonfree} tree?}{22}} \newlabel{Q-nonfree}{{63}{22}} -\@writefile{toc}{\contentsline {question}{\numberline {64}Contributing a file to the archives}{22}} -\newlabel{Q-uploads}{{64}{22}} +\@writefile{toc}{\contentsline {question}{\numberline {64}Contributing a file to the archives}{23}} +\newlabel{Q-uploads}{{64}{23}} \@writefile{toc}{\contentsline {question}{\numberline {65}Finding (La)\TeX {} files}{23}} \newlabel{Q-findfiles}{{65}{23}} \@writefile{toc}{\contentsline {question}{\numberline {66}Finding new fonts}{23}} \newlabel{Q-findfont}{{66}{23}} -\@writefile{toc}{\contentsline {question}{\numberline {67}The \TeX {}\nobreakspace {}Live distribution}{23}} -\newlabel{Q-CD}{{67}{23}} +\@writefile{toc}{\contentsline {question}{\numberline {67}The \TeX {}\nobreakspace {}Live distribution}{24}} +\newlabel{Q-CD}{{67}{24}} \@writefile{toc}{\contentsline {section}{\numberline {F}\TeX {} Systems}{24}} \@writefile{toc}{\contentsline {question}{\numberline {68}(La)\TeX {} for different machines}{24}} \newlabel{Q-TeXsystems}{{68}{24}} @@ -154,8 +154,8 @@ \newlabel{Q-otherprinters}{{73}{27}} \@writefile{toc}{\contentsline {question}{\numberline {74}\acro {DVI} previewers}{27}} \newlabel{Q-previewers}{{74}{27}} -\@writefile{toc}{\contentsline {question}{\numberline {75}Generating bitmaps from \acro {DVI}}{27}} -\newlabel{Q-dvi-bmp}{{75}{27}} +\@writefile{toc}{\contentsline {question}{\numberline {75}Generating bitmaps from \acro {DVI}}{28}} +\newlabel{Q-dvi-bmp}{{75}{28}} \@writefile{toc}{\contentsline {section}{\numberline {H}Support Packages for \TeX {}}{28}} \@writefile{toc}{\contentsline {question}{\numberline {76}Fig, a (La)\TeX {}-friendly drawing package}{28}} \newlabel{Q-fig}{{76}{28}} @@ -163,8 +163,8 @@ \newlabel{Q-texcad}{{77}{28}} \@writefile{toc}{\contentsline {question}{\numberline {78}Spelling checkers for work with \TeX {}}{28}} \newlabel{Q-spell}{{78}{28}} -\@writefile{toc}{\contentsline {question}{\numberline {79}How many words have you written?}{28}} -\newlabel{Q-wordcount}{{79}{28}} +\@writefile{toc}{\contentsline {question}{\numberline {79}How many words have you written?}{29}} +\newlabel{Q-wordcount}{{79}{29}} \@writefile{toc}{\contentsline {section}{\numberline {I}Literate programming}{29}} \@writefile{toc}{\contentsline {question}{\numberline {80}What is Literate Programming?}{29}} \newlabel{Q-lit}{{80}{29}} @@ -181,31 +181,31 @@ \newlabel{Q-fmtconv}{{85}{31}} \@writefile{toc}{\contentsline {question}{\numberline {86}Using \TeX {} to read \acro {SGML} or \acro {XML} directly}{31}} \newlabel{Q-readML}{{86}{31}} -\@writefile{toc}{\contentsline {question}{\numberline {87}Retrieving (La)\TeX {} from \acro {DVI}, etc.}{31}} -\newlabel{Q-recovertex}{{87}{31}} +\@writefile{toc}{\contentsline {question}{\numberline {87}Retrieving (La)\TeX {} from \acro {DVI}, etc.}{32}} +\newlabel{Q-recovertex}{{87}{32}} \@writefile{toc}{\contentsline {question}{\numberline {88}Translating La\TeX {} to Plain \TeX {}}{32}} \newlabel{Q-LaTeXtoPlain}{{88}{32}} \@writefile{toc}{\contentsline {section}{\numberline {K}Installing (La)\TeX {} files}{32}} \@writefile{toc}{\contentsline {question}{\numberline {89}Installing a new package}{32}} \newlabel{Q-instpackages}{{89}{32}} -\@writefile{toc}{\contentsline {question}{\numberline {90}Where to put new files}{32}} -\newlabel{Q-wherefiles}{{90}{32}} +\@writefile{toc}{\contentsline {question}{\numberline {90}Where to put new files}{33}} +\newlabel{Q-wherefiles}{{90}{33}} \@writefile{toc}{\contentsline {question}{\numberline {91}Installing MiKTeX{} ``known packages''}{33}} \newlabel{Q-miktexinst}{{91}{33}} \@writefile{toc}{\contentsline {question}{\numberline {92}``Temporary'' installation of (La)\TeX {} files}{33}} \newlabel{Q-tempinst}{{92}{33}} \@writefile{toc}{\contentsline {question}{\numberline {93}``Private'' installations of files}{34}} \newlabel{Q-privinst}{{93}{34}} -\@writefile{toc}{\contentsline {question}{\numberline {94}Installing a new font}{34}} -\newlabel{Q-instfont}{{94}{34}} +\@writefile{toc}{\contentsline {question}{\numberline {94}Installing a new font}{35}} +\newlabel{Q-instfont}{{94}{35}} \@writefile{toc}{\contentsline {question}{\numberline {95}Installing a font provided as \MF {} source}{35}} \newlabel{Q-instmffont}{{95}{35}} \@writefile{toc}{\contentsline {question}{\numberline {96}Installing a PostScript{} printer built-in font}{35}} \newlabel{Q-instprinterfont}{{96}{35}} \@writefile{toc}{\contentsline {question}{\numberline {97}Installing the Bluesky versions of the CM\nobreakspace {}fonts}{35}} \newlabel{Q-inst1cm}{{97}{35}} -\@writefile{toc}{\contentsline {question}{\numberline {98}Installing a Type\nobreakspace {}1 font}{35}} -\newlabel{Q-instt1font}{{98}{35}} +\@writefile{toc}{\contentsline {question}{\numberline {98}Installing a Type\nobreakspace {}1 font}{36}} +\newlabel{Q-instt1font}{{98}{36}} \@writefile{toc}{\contentsline {section}{\numberline {L}Fonts}{36}} \@writefile{toc}{\contentsline {subsection}{\numberline {L.1}\MF {} fonts}{36}} \@writefile{toc}{\contentsline {question}{\numberline {99}Getting \MF {} to do what you want}{36}} @@ -214,15 +214,15 @@ \newlabel{Q-keepfonts}{{100}{37}} \@writefile{toc}{\contentsline {question}{\numberline {101}Acquiring bitmap fonts}{37}} \newlabel{Q-getbitmap}{{101}{37}} -\@writefile{toc}{\contentsline {subsection}{\numberline {L.2}Adobe Type\nobreakspace {}1 (``PostScript{}'') fonts}{37}} -\@writefile{toc}{\contentsline {question}{\numberline {102}Using PostScript{} fonts with \TeX {}}{37}} -\newlabel{Q-usepsfont}{{102}{37}} +\@writefile{toc}{\contentsline {subsection}{\numberline {L.2}Adobe Type\nobreakspace {}1 (``PostScript{}'') fonts}{38}} +\@writefile{toc}{\contentsline {question}{\numberline {102}Using PostScript{} fonts with \TeX {}}{38}} +\newlabel{Q-usepsfont}{{102}{38}} \@writefile{toc}{\contentsline {question}{\numberline {103}Previewing files using Type 1 fonts}{38}} \newlabel{Q-PSpreview}{{103}{38}} \@writefile{toc}{\contentsline {question}{\numberline {104}\TeX {} font metric files for PostScript{} fonts}{38}} \newlabel{Q-metrics}{{104}{38}} -\@writefile{toc}{\contentsline {question}{\numberline {105}Deploying Type 1 fonts}{38}} -\newlabel{Q-psfontprob}{{105}{38}} +\@writefile{toc}{\contentsline {question}{\numberline {105}Deploying Type 1 fonts}{39}} +\newlabel{Q-psfontprob}{{105}{39}} \@writefile{toc}{\contentsline {question}{\numberline {106}Choice of scalable outline fonts}{39}} \newlabel{Q-psfchoice}{{106}{39}} \@writefile{toc}{\contentsline {question}{\numberline {107}Weird characters in \ProgName {dvips} output}{42}} @@ -230,9 +230,9 @@ \@writefile{toc}{\contentsline {subsection}{\numberline {L.3}Macros for using fonts}{42}} \@writefile{toc}{\contentsline {question}{\numberline {108}Using non-standard fonts in Plain \TeX {}}{42}} \newlabel{Q-fonts-pln}{{108}{42}} -\@writefile{toc}{\contentsline {subsection}{\numberline {L.4}Particular font families}{42}} -\@writefile{toc}{\contentsline {question}{\numberline {109}Using the ``Concrete'' fonts}{42}} -\newlabel{Q-concrete}{{109}{42}} +\@writefile{toc}{\contentsline {subsection}{\numberline {L.4}Particular font families}{43}} +\@writefile{toc}{\contentsline {question}{\numberline {109}Using the ``Concrete'' fonts}{43}} +\newlabel{Q-concrete}{{109}{43}} \@writefile{toc}{\contentsline {question}{\numberline {110}Using the Latin Modern fonts}{43}} \newlabel{Q-uselmfonts}{{110}{43}} \@writefile{toc}{\contentsline {section}{\numberline {M}Hypertext and \acro {PDF}}{43}} @@ -285,16 +285,16 @@ \newlabel{Q-drawFeyn}{{133}{52}} \@writefile{toc}{\contentsline {question}{\numberline {134}Labelling graphics}{52}} \newlabel{Q-labelfig}{{134}{52}} -\@writefile{toc}{\contentsline {section}{\numberline {O}Bibliographies and citations}{52}} -\@writefile{toc}{\contentsline {subsection}{\numberline {O.1}Creating bibliographies}{52}} -\@writefile{toc}{\contentsline {question}{\numberline {135}Creating a Bib\TeX {} bibliography file}{52}} -\newlabel{Q-buildbib}{{135}{52}} +\@writefile{toc}{\contentsline {section}{\numberline {O}Bibliographies and citations}{53}} +\@writefile{toc}{\contentsline {subsection}{\numberline {O.1}Creating bibliographies}{53}} +\@writefile{toc}{\contentsline {question}{\numberline {135}Creating a Bib\TeX {} bibliography file}{53}} +\newlabel{Q-buildbib}{{135}{53}} \@writefile{toc}{\contentsline {question}{\numberline {136}Creating a bibliography style}{53}} \newlabel{Q-custbib}{{136}{53}} \@writefile{toc}{\contentsline {question}{\numberline {137}Capitalisation in Bib\TeX {}}{53}} \newlabel{Q-capbibtex}{{137}{53}} -\@writefile{toc}{\contentsline {question}{\numberline {138}Accents in bibliographies}{53}} -\newlabel{Q-bibaccent}{{138}{53}} +\@writefile{toc}{\contentsline {question}{\numberline {138}Accents in bibliographies}{54}} +\newlabel{Q-bibaccent}{{138}{54}} \@writefile{toc}{\contentsline {question}{\numberline {139}`String too long' in Bib\TeX {}}{54}} \newlabel{Q-bibstrtl}{{139}{54}} \@writefile{toc}{\contentsline {question}{\numberline {140}Bib\TeX {} doesn't understand lists of names}{54}} @@ -314,8 +314,8 @@ \newlabel{Q-usebibtex}{{146}{56}} \@writefile{toc}{\contentsline {question}{\numberline {147}Choosing a bibliography style}{56}} \newlabel{Q-whatbst}{{147}{56}} -\@writefile{toc}{\contentsline {question}{\numberline {148}Separate bibliographies per chapter?}{56}} -\newlabel{Q-chapbib}{{148}{56}} +\@writefile{toc}{\contentsline {question}{\numberline {148}Separate bibliographies per chapter?}{57}} +\newlabel{Q-chapbib}{{148}{57}} \@writefile{toc}{\contentsline {question}{\numberline {149}Multiple bibliographies?}{57}} \newlabel{Q-multbib}{{149}{57}} \@writefile{toc}{\contentsline {question}{\numberline {150}Putting bibliography entries in text}{58}} @@ -324,8 +324,8 @@ \newlabel{Q-citesort}{{151}{58}} \@writefile{toc}{\contentsline {question}{\numberline {152}Multiple citations}{58}} \newlabel{Q-mcite}{{152}{58}} -\@writefile{toc}{\contentsline {question}{\numberline {153}References from the bibliography to the citation}{58}} -\newlabel{Q-backref}{{153}{58}} +\@writefile{toc}{\contentsline {question}{\numberline {153}References from the bibliography to the citation}{59}} +\newlabel{Q-backref}{{153}{59}} \@writefile{toc}{\contentsline {question}{\numberline {154}Sorting lists of citations}{59}} \newlabel{Q-sortbib}{{154}{59}} \@writefile{toc}{\contentsline {question}{\numberline {155}Reducing spacing in the bibliography}{59}} @@ -345,27 +345,27 @@ \@writefile{toc}{\contentsline {subsection}{\numberline {P.1}Alternative document classes}{60}} \@writefile{toc}{\contentsline {question}{\numberline {161}Replacing the standard classes}{60}} \newlabel{Q-replstdcls}{{161}{60}} -\@writefile{toc}{\contentsline {question}{\numberline {162}Producing slides}{60}} -\newlabel{Q-slidecls}{{162}{60}} +\@writefile{toc}{\contentsline {question}{\numberline {162}Producing slides}{61}} +\newlabel{Q-slidecls}{{162}{61}} \@writefile{toc}{\contentsline {question}{\numberline {163}Creating posters with La\TeX {}}{61}} \newlabel{Q-poster}{{163}{61}} -\@writefile{toc}{\contentsline {question}{\numberline {164}Formatting a thesis in La\TeX {}}{61}} -\newlabel{Q-thesis}{{164}{61}} +\@writefile{toc}{\contentsline {question}{\numberline {164}Formatting a thesis in La\TeX {}}{62}} +\newlabel{Q-thesis}{{164}{62}} \@writefile{toc}{\contentsline {question}{\numberline {165}Setting papers for journals}{62}} \newlabel{Q-journalpaper}{{165}{62}} \@writefile{toc}{\contentsline {question}{\numberline {166}A `report' from lots of `article's}{62}} \newlabel{Q-multidoc}{{166}{62}} \@writefile{toc}{\contentsline {question}{\numberline {167}\emph {Curriculum Vitae} (R\'esum\'e)}{62}} \newlabel{Q-cv}{{167}{62}} -\@writefile{toc}{\contentsline {question}{\numberline {168}Letters and the like}{62}} -\newlabel{Q-letterclass}{{168}{62}} +\@writefile{toc}{\contentsline {question}{\numberline {168}Letters and the like}{63}} +\newlabel{Q-letterclass}{{168}{63}} \@writefile{toc}{\contentsline {question}{\numberline {169}Other ``document font'' sizes?}{63}} \newlabel{Q-extsizes}{{169}{63}} \@writefile{toc}{\contentsline {subsection}{\numberline {P.2}Document structure}{63}} \@writefile{toc}{\contentsline {question}{\numberline {170}The style of document titles}{63}} \newlabel{Q-titlsty}{{170}{63}} -\@writefile{toc}{\contentsline {question}{\numberline {171}The style of section headings}{63}} -\newlabel{Q-secthead}{{171}{63}} +\@writefile{toc}{\contentsline {question}{\numberline {171}The style of section headings}{64}} +\newlabel{Q-secthead}{{171}{64}} \@writefile{toc}{\contentsline {question}{\numberline {172}Appendixes}{64}} \newlabel{Q-appendix}{{172}{64}} \@writefile{toc}{\contentsline {question}{\numberline {173}Indent after section headings}{65}} @@ -374,20 +374,20 @@ \newlabel{Q-subsubsub}{{174}{65}} \@writefile{toc}{\contentsline {question}{\numberline {175}The style of captions}{65}} \newlabel{Q-captsty}{{175}{65}} -\@writefile{toc}{\contentsline {question}{\numberline {176}Alternative head- and footlines in La\TeX {}}{65}} -\newlabel{Q-fancyhdr}{{176}{65}} -\@writefile{toc}{\contentsline {question}{\numberline {177}Wide figures in two-column documents}{65}} -\newlabel{Q-widefigs}{{177}{65}} +\@writefile{toc}{\contentsline {question}{\numberline {176}Alternative head- and footlines in La\TeX {}}{66}} +\newlabel{Q-fancyhdr}{{176}{66}} +\@writefile{toc}{\contentsline {question}{\numberline {177}Wide figures in two-column documents}{66}} +\newlabel{Q-widefigs}{{177}{66}} \@writefile{toc}{\contentsline {question}{\numberline {178}1-column abstract in 2-column document}{66}} \newlabel{Q-onecolabs}{{178}{66}} \@writefile{toc}{\contentsline {question}{\numberline {179}Really blank pages between chapters}{66}} \newlabel{Q-reallyblank}{{179}{66}} -\@writefile{toc}{\contentsline {question}{\numberline {180}Balancing columns at the end of a document}{66}} -\newlabel{Q-balance}{{180}{66}} +\@writefile{toc}{\contentsline {question}{\numberline {180}Balancing columns at the end of a document}{67}} +\newlabel{Q-balance}{{180}{67}} \@writefile{toc}{\contentsline {question}{\numberline {181}My section title is too wide for the page header}{67}} \newlabel{Q-runheadtoobig}{{181}{67}} -\@writefile{toc}{\contentsline {question}{\numberline {182}Page numbering ``\ensuremath {\delimiter "426830A }\emph {n}\ensuremath {\delimiter "526930B } of \ensuremath {\delimiter "426830A }\emph {m}\ensuremath {\delimiter "526930B }''}{67}} -\newlabel{Q-nofm}{{182}{67}} +\@writefile{toc}{\contentsline {question}{\numberline {182}Page numbering ``\ensuremath {\delimiter "426830A }\emph {n}\ensuremath {\delimiter "526930B } of \ensuremath {\delimiter "426830A }\emph {m}\ensuremath {\delimiter "526930B }''}{68}} +\newlabel{Q-nofm}{{182}{68}} \@writefile{toc}{\contentsline {question}{\numberline {183}Page numbering by chapter}{68}} \newlabel{Q-pagebychap}{{183}{68}} \@writefile{toc}{\contentsline {subsection}{\numberline {P.3}Page layout}{68}} @@ -395,479 +395,481 @@ \newlabel{Q-papersize}{{184}{68}} \@writefile{toc}{\contentsline {question}{\numberline {185}Changing the margins in La\TeX {}}{68}} \newlabel{Q-changemargin}{{185}{68}} -\@writefile{toc}{\contentsline {question}{\numberline {186}Packages to set up page designs}{68}} -\newlabel{Q-marginpkgs}{{186}{68}} +\@writefile{toc}{\contentsline {question}{\numberline {186}Packages to set up page designs}{69}} +\newlabel{Q-marginpkgs}{{186}{69}} \@writefile{toc}{\contentsline {question}{\numberline {187}How to set up page layout ``by hand''}{69}} \newlabel{Q-marginmanual}{{187}{69}} \@writefile{toc}{\contentsline {question}{\numberline {188}Changing margins ``on the fly''}{69}} \newlabel{Q-chngmargonfly}{{188}{69}} -\@writefile{toc}{\contentsline {question}{\numberline {189}How to get rid of page numbers}{69}} -\newlabel{Q-nopageno}{{189}{69}} +\@writefile{toc}{\contentsline {question}{\numberline {189}How to get rid of page numbers}{70}} +\newlabel{Q-nopageno}{{189}{70}} \@writefile{toc}{\contentsline {question}{\numberline {190}\psatempty {} on first page in La\TeX {}}{70}} \newlabel{Q-ps@empty}{{190}{70}} \@writefile{toc}{\contentsline {question}{\numberline {191}How to create crop marks}{70}} \newlabel{Q-crop}{{191}{70}} -\@writefile{toc}{\contentsline {question}{\numberline {192}`Watermarks' on every page}{70}} -\newlabel{Q-watermark}{{192}{70}} +\@writefile{toc}{\contentsline {question}{\numberline {192}`Watermarks' on every page}{71}} +\newlabel{Q-watermark}{{192}{71}} \@writefile{toc}{\contentsline {question}{\numberline {193}Typesetting things in landscape orientation}{71}} \newlabel{Q-landscape}{{193}{71}} \@writefile{toc}{\contentsline {question}{\numberline {194}Putting things at fixed positions on the page}{71}} \newlabel{Q-abspos}{{194}{71}} -\@writefile{toc}{\contentsline {question}{\numberline {195}Preventing page breaks between lines}{71}} -\newlabel{Q-nopagebrk}{{195}{71}} +\@writefile{toc}{\contentsline {question}{\numberline {195}Preventing page breaks between lines}{72}} +\newlabel{Q-nopagebrk}{{195}{72}} \@writefile{toc}{\contentsline {question}{\numberline {196}Parallel setting of text}{72}} \newlabel{Q-parallel}{{196}{72}} -\@writefile{toc}{\contentsline {question}{\numberline {197}Typesetting epigraphs}{72}} -\newlabel{Q-epigraph}{{197}{72}} +\@writefile{toc}{\contentsline {question}{\numberline {197}Typesetting epigraphs}{73}} +\newlabel{Q-epigraph}{{197}{73}} \@writefile{toc}{\contentsline {question}{\numberline {198}(La)\TeX {} \acro {PDF} output prints at wrong size}{73}} \newlabel{Q-outszwrng}{{198}{73}} -\@writefile{toc}{\contentsline {subsection}{\numberline {P.4}Spacing of characters and lines}{73}} -\@writefile{toc}{\contentsline {question}{\numberline {199}Double-spaced documents in La\TeX {}}{73}} -\newlabel{Q-linespace}{{199}{73}} -\@writefile{toc}{\contentsline {question}{\numberline {200}Changing the space between letters}{73}} -\newlabel{Q-letterspace}{{200}{73}} +\@writefile{toc}{\contentsline {subsection}{\numberline {P.4}Spacing of characters and lines}{74}} +\@writefile{toc}{\contentsline {question}{\numberline {199}Double-spaced documents in La\TeX {}}{74}} +\newlabel{Q-linespace}{{199}{74}} +\@writefile{toc}{\contentsline {question}{\numberline {200}Changing the space between letters}{74}} +\newlabel{Q-letterspace}{{200}{74}} \@writefile{toc}{\contentsline {question}{\numberline {201}Setting text ragged right}{74}} \newlabel{Q-ragright}{{201}{74}} \@writefile{toc}{\contentsline {question}{\numberline {202}Cancelling \csx {ragged} commands}{74}} \newlabel{Q-flushboth}{{202}{74}} -\@writefile{toc}{\contentsline {subsection}{\numberline {P.5}Typesetting specialities}{74}} -\@writefile{toc}{\contentsline {question}{\numberline {203}Including a file verbatim in La\TeX {}}{74}} -\newlabel{Q-verbfile}{{203}{74}} +\@writefile{toc}{\contentsline {subsection}{\numberline {P.5}Typesetting specialities}{75}} +\@writefile{toc}{\contentsline {question}{\numberline {203}Including a file verbatim in La\TeX {}}{75}} +\newlabel{Q-verbfile}{{203}{75}} \@writefile{toc}{\contentsline {question}{\numberline {204}Including line numbers in typeset output}{75}} \newlabel{Q-linenos}{{204}{75}} \@writefile{toc}{\contentsline {question}{\numberline {205}Code listings in La\TeX {}}{75}} \newlabel{Q-codelist}{{205}{75}} -\@writefile{toc}{\contentsline {question}{\numberline {206}Typesetting pseudocode in La\TeX {}}{75}} -\newlabel{Q-algorithms}{{206}{75}} -\@writefile{toc}{\contentsline {question}{\numberline {207}Generating an index in (La)\TeX {}}{76}} -\newlabel{Q-makeindex}{{207}{76}} +\@writefile{toc}{\contentsline {question}{\numberline {206}Typesetting pseudocode in La\TeX {}}{76}} +\newlabel{Q-algorithms}{{206}{76}} +\@writefile{toc}{\contentsline {question}{\numberline {207}Generating an index in (La)\TeX {}}{77}} +\newlabel{Q-makeindex}{{207}{77}} \@writefile{toc}{\contentsline {question}{\numberline {208}Typesetting \acro {URL}s}{77}} \newlabel{Q-setURL}{{208}{77}} \@writefile{toc}{\contentsline {question}{\numberline {209}Typesetting music in \TeX {}}{77}} \newlabel{Q-music}{{209}{77}} -\@writefile{toc}{\contentsline {question}{\numberline {210}Zero paragraph indent}{77}} -\newlabel{Q-parskip}{{210}{77}} +\@writefile{toc}{\contentsline {question}{\numberline {210}Zero paragraph indent}{78}} +\newlabel{Q-parskip}{{210}{78}} \@writefile{toc}{\contentsline {question}{\numberline {211}Big letters at the start of a paragraph}{78}} \newlabel{Q-dropping}{{211}{78}} \@writefile{toc}{\contentsline {question}{\numberline {212}The comma as a decimal separator}{78}} \newlabel{Q-dec_comma}{{212}{78}} -\@writefile{toc}{\contentsline {question}{\numberline {213}Breaking boxes of text}{78}} -\newlabel{Q-breakbox}{{213}{78}} -\@writefile{toc}{\contentsline {question}{\numberline {214}Overstriking characters}{78}} -\newlabel{Q-overstrike}{{214}{78}} -\@writefile{toc}{\contentsline {question}{\numberline {215}Realistic quotes for verbatim listings}{78}} -\newlabel{Q-upquot}{{215}{78}} +\@writefile{toc}{\contentsline {question}{\numberline {213}Breaking boxes of text}{79}} +\newlabel{Q-breakbox}{{213}{79}} +\@writefile{toc}{\contentsline {question}{\numberline {214}Overstriking characters}{79}} +\newlabel{Q-overstrike}{{214}{79}} +\@writefile{toc}{\contentsline {question}{\numberline {215}Realistic quotes for verbatim listings}{79}} +\newlabel{Q-upquot}{{215}{79}} \@writefile{toc}{\contentsline {question}{\numberline {216}Printing the time}{79}} \newlabel{Q-time}{{216}{79}} \@writefile{toc}{\contentsline {question}{\numberline {217}Redefining counters' \csx {the-}commands}{79}} \newlabel{Q-the-commands}{{217}{79}} -\@writefile{toc}{\contentsline {subsection}{\numberline {P.6}Tables of contents and indexes}{79}} -\@writefile{toc}{\contentsline {question}{\numberline {218}The format of the Table of Contents, etc.}{79}} -\newlabel{Q-tocloft}{{218}{79}} -\@writefile{toc}{\contentsline {question}{\numberline {219}Unnumbered sections in the Table of Contents}{79}} -\newlabel{Q-secnumdep}{{219}{79}} +\@writefile{toc}{\contentsline {subsection}{\numberline {P.6}Tables of contents and indexes}{80}} +\@writefile{toc}{\contentsline {question}{\numberline {218}The format of the Table of Contents, etc.}{80}} +\newlabel{Q-tocloft}{{218}{80}} +\@writefile{toc}{\contentsline {question}{\numberline {219}Unnumbered sections in the Table of Contents}{80}} +\newlabel{Q-secnumdep}{{219}{80}} \@writefile{toc}{\contentsline {question}{\numberline {220}Bibliography, index, etc., in \acro {TOC}}{80}} \newlabel{Q-tocbibind}{{220}{80}} -\@writefile{toc}{\contentsline {question}{\numberline {221}Table of contents, etc., per chapter}{80}} -\newlabel{Q-minitoc}{{221}{80}} -\@writefile{toc}{\contentsline {question}{\numberline {222}Multiple indexes}{80}} -\newlabel{Q-multind}{{222}{80}} -\@writefile{toc}{\contentsline {subsection}{\numberline {P.7}Labels and references}{81}} -\@writefile{toc}{\contentsline {question}{\numberline {223}Referring to things by their name}{81}} -\newlabel{Q-nameref}{{223}{81}} +\@writefile{toc}{\contentsline {question}{\numberline {221}Table of contents, etc., per chapter}{81}} +\newlabel{Q-minitoc}{{221}{81}} +\@writefile{toc}{\contentsline {question}{\numberline {222}Multiple indexes}{81}} +\newlabel{Q-multind}{{222}{81}} +\@writefile{toc}{\contentsline {subsection}{\numberline {P.7}Labels and references}{82}} +\@writefile{toc}{\contentsline {question}{\numberline {223}Referring to things by their name}{82}} +\newlabel{Q-nameref}{{223}{82}} \@writefile{toc}{\contentsline {question}{\numberline {224}Referring to labels in other documents}{82}} \newlabel{Q-extref}{{224}{82}} \@writefile{toc}{\contentsline {section}{\numberline {Q}How do I do\dots {}?}{82}} \@writefile{toc}{\contentsline {subsection}{\numberline {Q.1}Mathematics}{82}} \@writefile{toc}{\contentsline {question}{\numberline {225}Proof environment}{82}} \newlabel{Q-proof}{{225}{82}} -\@writefile{toc}{\contentsline {question}{\numberline {226}Roman theorems}{82}} -\newlabel{Q-theoremfmt}{{226}{82}} -\@writefile{toc}{\contentsline {question}{\numberline {227}Defining a new log-like function in La\TeX {}}{82}} -\newlabel{Q-newfunction}{{227}{82}} +\@writefile{toc}{\contentsline {question}{\numberline {226}Roman theorems}{83}} +\newlabel{Q-theoremfmt}{{226}{83}} +\@writefile{toc}{\contentsline {question}{\numberline {227}Defining a new log-like function in La\TeX {}}{83}} +\newlabel{Q-newfunction}{{227}{83}} \@writefile{toc}{\contentsline {question}{\numberline {228}Set specifications and Dirac brackets}{83}} \newlabel{Q-braket}{{228}{83}} \@writefile{toc}{\contentsline {question}{\numberline {229}Cancelling terms in maths expressions}{83}} \newlabel{Q-cancellation}{{229}{83}} \@writefile{toc}{\contentsline {question}{\numberline {230}Adjusting maths font sizes}{83}} \newlabel{Q-mathsize}{{230}{83}} -\@writefile{toc}{\contentsline {question}{\numberline {231}Ellipses}{83}} -\newlabel{Q-mathlips}{{231}{83}} +\@writefile{toc}{\contentsline {question}{\numberline {231}Ellipses}{84}} +\newlabel{Q-mathlips}{{231}{84}} \@writefile{toc}{\contentsline {question}{\numberline {232}Sub- and superscript positioning for operators}{84}} \newlabel{Q-limits}{{232}{84}} \@writefile{toc}{\contentsline {question}{\numberline {233}Text inside maths}{84}} \newlabel{Q-mathstext}{{233}{84}} \@writefile{toc}{\contentsline {question}{\numberline {234}Re-using an equation}{85}} \newlabel{Q-reuseq}{{234}{85}} -\@writefile{toc}{\contentsline {question}{\numberline {235}Line-breaking in in-line maths}{85}} -\newlabel{Q-brkinline}{{235}{85}} -\@writefile{toc}{\contentsline {subsection}{\numberline {Q.2}Lists}{85}} -\@writefile{toc}{\contentsline {question}{\numberline {236}Fancy enumeration lists}{85}} -\newlabel{Q-enumerate}{{236}{85}} +\@writefile{toc}{\contentsline {question}{\numberline {235}Line-breaking in in-line maths}{86}} +\newlabel{Q-brkinline}{{235}{86}} +\@writefile{toc}{\contentsline {subsection}{\numberline {Q.2}Lists}{86}} +\@writefile{toc}{\contentsline {question}{\numberline {236}Fancy enumeration lists}{86}} +\newlabel{Q-enumerate}{{236}{86}} \@writefile{toc}{\contentsline {question}{\numberline {237}How to reduce list spacing}{86}} \newlabel{Q-complist}{{237}{86}} \@writefile{toc}{\contentsline {question}{\numberline {238}Interrupting enumerated lists}{87}} \newlabel{Q-interruptlist}{{238}{87}} -\@writefile{toc}{\contentsline {subsection}{\numberline {Q.3}Tables, figures and diagrams}{87}} -\@writefile{toc}{\contentsline {question}{\numberline {239}The design of tables}{87}} -\newlabel{Q-destable}{{239}{87}} +\@writefile{toc}{\contentsline {subsection}{\numberline {Q.3}Tables, figures and diagrams}{88}} +\@writefile{toc}{\contentsline {question}{\numberline {239}The design of tables}{88}} +\newlabel{Q-destable}{{239}{88}} \@writefile{toc}{\contentsline {question}{\numberline {240}Fixed-width tables}{88}} \newlabel{Q-fixwidtab}{{240}{88}} -\@writefile{toc}{\contentsline {question}{\numberline {241}Variable-width columns in tables}{88}} -\newlabel{Q-varwidcol}{{241}{88}} +\@writefile{toc}{\contentsline {question}{\numberline {241}Variable-width columns in tables}{89}} +\newlabel{Q-varwidcol}{{241}{89}} \@writefile{toc}{\contentsline {question}{\numberline {242}Spacing lines in tables}{89}} \newlabel{Q-struttab}{{242}{89}} -\@writefile{toc}{\contentsline {question}{\numberline {243}Tables longer than a single page}{89}} -\newlabel{Q-longtab}{{243}{89}} +\@writefile{toc}{\contentsline {question}{\numberline {243}Tables longer than a single page}{90}} +\newlabel{Q-longtab}{{243}{90}} \@writefile{toc}{\contentsline {question}{\numberline {244}How to alter the alignment of tabular cells}{90}} \newlabel{Q-tabcellalign}{{244}{90}} -\@writefile{toc}{\contentsline {question}{\numberline {245}The thickness of rules in La\TeX {} tables}{90}} -\newlabel{Q-rulethk}{{245}{90}} +\@writefile{toc}{\contentsline {question}{\numberline {245}The thickness of rules in La\TeX {} tables}{91}} +\newlabel{Q-rulethk}{{245}{91}} \@writefile{toc}{\contentsline {question}{\numberline {246}Flowing text around figures in La\TeX {}}{91}} \newlabel{Q-textflow}{{246}{91}} -\@writefile{toc}{\contentsline {question}{\numberline {247}Diagonal separation in corner cells of tables}{91}} -\newlabel{Q-slashbox}{{247}{91}} -\@writefile{toc}{\contentsline {question}{\numberline {248}How to change a whole row of a table}{91}} -\newlabel{Q-wholerow}{{248}{91}} +\@writefile{toc}{\contentsline {question}{\numberline {247}Diagonal separation in corner cells of tables}{92}} +\newlabel{Q-slashbox}{{247}{92}} +\@writefile{toc}{\contentsline {question}{\numberline {248}How to change a whole row of a table}{92}} +\newlabel{Q-wholerow}{{248}{92}} \@writefile{toc}{\contentsline {question}{\numberline {249}Merging cells in a column of a table}{92}} \newlabel{Q-multirow}{{249}{92}} -\@writefile{toc}{\contentsline {subsection}{\numberline {Q.4}Floating tables, figures, etc.}{92}} -\@writefile{toc}{\contentsline {question}{\numberline {250}Floats on their own on float pages}{92}} -\newlabel{Q-floatpages}{{250}{92}} +\@writefile{toc}{\contentsline {subsection}{\numberline {Q.4}Floating tables, figures, etc.}{93}} +\@writefile{toc}{\contentsline {question}{\numberline {250}Floats on their own on float pages}{93}} +\newlabel{Q-floatpages}{{250}{93}} \@writefile{toc}{\contentsline {question}{\numberline {251}Extra vertical space in floats}{93}} \newlabel{Q-vertspacefloat}{{251}{93}} \@writefile{toc}{\contentsline {question}{\numberline {252}Placing two-column floats at bottom of page}{93}} \newlabel{Q-2colfloat}{{252}{93}} -\@writefile{toc}{\contentsline {question}{\numberline {253}Floats in multicolumn setting}{93}} -\newlabel{Q-mcfloat}{{253}{93}} -\@writefile{toc}{\contentsline {question}{\numberline {254}Facing floats on 2-page spread}{93}} -\newlabel{Q-dpfloat}{{254}{93}} -\@writefile{toc}{\contentsline {question}{\numberline {255}Vertical layout of float pages}{93}} -\newlabel{Q-vertposfp}{{255}{93}} +\@writefile{toc}{\contentsline {question}{\numberline {253}Floats in multicolumn setting}{94}} +\newlabel{Q-mcfloat}{{253}{94}} +\@writefile{toc}{\contentsline {question}{\numberline {254}Facing floats on 2-page spread}{94}} +\newlabel{Q-dpfloat}{{254}{94}} +\@writefile{toc}{\contentsline {question}{\numberline {255}Vertical layout of float pages}{94}} +\newlabel{Q-vertposfp}{{255}{94}} \@writefile{toc}{\contentsline {subsection}{\numberline {Q.5}Footnotes}{94}} \@writefile{toc}{\contentsline {question}{\numberline {256}Footnotes in tables}{94}} \newlabel{Q-footintab}{{256}{94}} -\@writefile{toc}{\contentsline {question}{\numberline {257}Footnotes in La\TeX {} section headings}{94}} -\newlabel{Q-ftnsect}{{257}{94}} -\@writefile{toc}{\contentsline {question}{\numberline {258}Footnotes in captions}{94}} -\newlabel{Q-ftncapt}{{258}{94}} +\@writefile{toc}{\contentsline {question}{\numberline {257}Footnotes in La\TeX {} section headings}{95}} +\newlabel{Q-ftnsect}{{257}{95}} +\@writefile{toc}{\contentsline {question}{\numberline {258}Footnotes in captions}{95}} +\newlabel{Q-ftncapt}{{258}{95}} \@writefile{toc}{\contentsline {question}{\numberline {259}Footnotes whose texts are identical}{95}} \newlabel{Q-repfootnote}{{259}{95}} -\@writefile{toc}{\contentsline {question}{\numberline {260}More than one sequence of footnotes}{95}} -\newlabel{Q-multfoot}{{260}{95}} -\@writefile{toc}{\contentsline {question}{\numberline {261}Footnotes numbered ``per page''}{95}} -\newlabel{Q-footnpp}{{261}{95}} +\@writefile{toc}{\contentsline {question}{\numberline {260}More than one sequence of footnotes}{96}} +\newlabel{Q-multfoot}{{260}{96}} +\@writefile{toc}{\contentsline {question}{\numberline {261}Footnotes numbered ``per page''}{96}} +\newlabel{Q-footnpp}{{261}{96}} \@writefile{toc}{\contentsline {subsection}{\numberline {Q.6}Document management}{96}} \@writefile{toc}{\contentsline {question}{\numberline {262}What's the name of this file}{96}} \newlabel{Q-filename}{{262}{96}} -\@writefile{toc}{\contentsline {question}{\numberline {263}All the files used by this document}{96}} -\newlabel{Q-filesused}{{263}{96}} +\@writefile{toc}{\contentsline {question}{\numberline {263}All the files used by this document}{97}} +\newlabel{Q-filesused}{{263}{97}} \@writefile{toc}{\contentsline {question}{\numberline {264}Marking changed parts of your document}{97}} \newlabel{Q-changebars}{{264}{97}} -\@writefile{toc}{\contentsline {question}{\numberline {265}Conditional compilation and ``comments''}{97}} -\newlabel{Q-conditional}{{265}{97}} +\@writefile{toc}{\contentsline {question}{\numberline {265}Conditional compilation and ``comments''}{98}} +\newlabel{Q-conditional}{{265}{98}} \@writefile{toc}{\contentsline {question}{\numberline {266}Bits of document from other directories}{99}} \newlabel{Q-docotherdir}{{266}{99}} -\@writefile{toc}{\contentsline {question}{\numberline {267}Version control using \acro {RCS}, \acro {CVS} or \ProgName {Subversion}}{99}} -\newlabel{Q-RCS}{{267}{99}} -\@writefile{toc}{\contentsline {question}{\numberline {268}Makefiles for La\TeX {} documents}{99}} -\newlabel{Q-make}{{268}{99}} +\@writefile{toc}{\contentsline {question}{\numberline {267}Version control using \acro {RCS}, \acro {CVS} or \ProgName {Subversion}}{100}} +\newlabel{Q-RCS}{{267}{100}} +\@writefile{toc}{\contentsline {question}{\numberline {268}Makefiles for La\TeX {} documents}{100}} +\newlabel{Q-make}{{268}{100}} \@writefile{toc}{\contentsline {question}{\numberline {269}How many pages are there in my document?}{100}} \newlabel{Q-howmanypp}{{269}{100}} -\@writefile{toc}{\contentsline {question}{\numberline {270}Including Plain \TeX {} files in La\TeX {}}{100}} -\newlabel{Q-inclplain}{{270}{100}} -\@writefile{toc}{\contentsline {subsection}{\numberline {Q.7}Hyphenation}{100}} -\@writefile{toc}{\contentsline {question}{\numberline {271}My words aren't being hyphenated}{100}} -\newlabel{Q-nohyph}{{271}{100}} +\@writefile{toc}{\contentsline {question}{\numberline {270}Including Plain \TeX {} files in La\TeX {}}{101}} +\newlabel{Q-inclplain}{{270}{101}} +\@writefile{toc}{\contentsline {subsection}{\numberline {Q.7}Hyphenation}{101}} +\@writefile{toc}{\contentsline {question}{\numberline {271}My words aren't being hyphenated}{101}} +\newlabel{Q-nohyph}{{271}{101}} \@writefile{toc}{\contentsline {question}{\numberline {272}Weird hyphenation of words}{101}} \newlabel{Q-weirdhyphen}{{272}{101}} -\@writefile{toc}{\contentsline {question}{\numberline {273}(Merely) peculiar hyphenation}{101}} -\newlabel{Q-oddhyphen}{{273}{101}} -\@writefile{toc}{\contentsline {question}{\numberline {274}Accented words aren't hyphenated}{101}} -\newlabel{Q-hyphenaccents}{{274}{101}} -\@writefile{toc}{\contentsline {question}{\numberline {275}Using a new language with Babel}{101}} -\newlabel{Q-newlang}{{275}{101}} +\@writefile{toc}{\contentsline {question}{\numberline {273}(Merely) peculiar hyphenation}{102}} +\newlabel{Q-oddhyphen}{{273}{102}} +\@writefile{toc}{\contentsline {question}{\numberline {274}Accented words aren't hyphenated}{102}} +\newlabel{Q-hyphenaccents}{{274}{102}} +\@writefile{toc}{\contentsline {question}{\numberline {275}Using a new language with Babel}{102}} +\newlabel{Q-newlang}{{275}{102}} \@writefile{toc}{\contentsline {question}{\numberline {276}Stopping all hyphenation}{102}} \newlabel{Q-hyphoff}{{276}{102}} -\@writefile{toc}{\contentsline {question}{\numberline {277}Preventing hyphenation of a particular word}{102}} -\newlabel{Q-wdnohyph}{{277}{102}} +\@writefile{toc}{\contentsline {question}{\numberline {277}Preventing hyphenation of a particular word}{103}} +\newlabel{Q-wdnohyph}{{277}{103}} \@writefile{toc}{\contentsline {question}{\numberline {278}Hyphenation exceptions}{103}} \newlabel{Q-hyphexcept}{{278}{103}} -\@writefile{toc}{\contentsline {subsection}{\numberline {Q.8}Odds and ends}{103}} -\@writefile{toc}{\contentsline {question}{\numberline {279}Typesetting all those \TeX {}-related logos}{103}} -\newlabel{Q-logos}{{279}{103}} -\@writefile{toc}{\contentsline {question}{\numberline {280}How to do bold-tt or bold-sc}{103}} -\newlabel{Q-bold-extras}{{280}{103}} +\@writefile{toc}{\contentsline {subsection}{\numberline {Q.8}Odds and ends}{104}} +\@writefile{toc}{\contentsline {question}{\numberline {279}Typesetting all those \TeX {}-related logos}{104}} +\newlabel{Q-logos}{{279}{104}} +\@writefile{toc}{\contentsline {question}{\numberline {280}How to do bold-tt or bold-sc}{104}} +\newlabel{Q-bold-extras}{{280}{104}} \@writefile{toc}{\contentsline {question}{\numberline {281}Automatic sizing of \texttt {minipage}}{104}} \newlabel{Q-varwidth}{{281}{104}} -\@writefile{toc}{\contentsline {section}{\numberline {R}Symbols, etc.}{104}} -\@writefile{toc}{\contentsline {question}{\numberline {282}Symbols for the number sets}{104}} -\newlabel{Q-numbersets}{{282}{104}} -\@writefile{toc}{\contentsline {question}{\numberline {283}Better script fonts for maths}{105}} -\newlabel{Q-scriptfonts}{{283}{105}} -\@writefile{toc}{\contentsline {question}{\numberline {284}Setting bold Greek letters in La\TeX {}}{105}} -\newlabel{Q-boldgreek}{{284}{105}} +\@writefile{toc}{\contentsline {section}{\numberline {R}Symbols, etc.}{105}} +\@writefile{toc}{\contentsline {question}{\numberline {282}Symbols for the number sets}{105}} +\newlabel{Q-numbersets}{{282}{105}} +\@writefile{toc}{\contentsline {question}{\numberline {283}Better script fonts for maths}{106}} +\newlabel{Q-scriptfonts}{{283}{106}} +\@writefile{toc}{\contentsline {question}{\numberline {284}Setting bold Greek letters in La\TeX {}}{106}} +\newlabel{Q-boldgreek}{{284}{106}} \@writefile{toc}{\contentsline {question}{\numberline {285}The Principal Value Integral symbol}{106}} \newlabel{Q-prinvalint}{{285}{106}} \@writefile{toc}{\contentsline {question}{\numberline {286}How to use the underscore character}{106}} \newlabel{Q-underscore}{{286}{106}} -\@writefile{toc}{\contentsline {question}{\numberline {287}How to type an `@' sign?}{106}} -\newlabel{Q-atsign}{{287}{106}} -\@writefile{toc}{\contentsline {question}{\numberline {288}Typesetting the Euro sign}{106}} -\newlabel{Q-euro}{{288}{106}} +\@writefile{toc}{\contentsline {question}{\numberline {287}How to type an `@' sign?}{107}} +\newlabel{Q-atsign}{{287}{107}} +\@writefile{toc}{\contentsline {question}{\numberline {288}Typesetting the Euro sign}{107}} +\newlabel{Q-euro}{{288}{107}} \@writefile{toc}{\contentsline {question}{\numberline {289}How to get copyright, trademark, etc.}{107}} \newlabel{Q-tradesyms}{{289}{107}} -\@writefile{toc}{\contentsline {section}{\numberline {S}Macro programming}{107}} -\@writefile{toc}{\contentsline {subsection}{\numberline {S.1}``Generic'' macros and techniques}{107}} -\@writefile{toc}{\contentsline {question}{\numberline {290}Finding the width of a letter, word, or phrase}{107}} -\newlabel{Q-findwidth}{{290}{107}} -\@writefile{toc}{\contentsline {question}{\numberline {291}Patching existing commands}{107}} -\newlabel{Q-patch}{{291}{107}} +\@writefile{toc}{\contentsline {section}{\numberline {S}Macro programming}{108}} +\@writefile{toc}{\contentsline {subsection}{\numberline {S.1}``Generic'' macros and techniques}{108}} +\@writefile{toc}{\contentsline {question}{\numberline {290}Finding the width of a letter, word, or phrase}{108}} +\newlabel{Q-findwidth}{{290}{108}} +\@writefile{toc}{\contentsline {question}{\numberline {291}Patching existing commands}{108}} +\newlabel{Q-patch}{{291}{108}} \@writefile{toc}{\contentsline {question}{\numberline {292}Comparing the ``job name''}{108}} \newlabel{Q-compjobnam}{{292}{108}} \@writefile{toc}{\contentsline {question}{\numberline {293}Is the argument a number?}{108}} \newlabel{Q-isitanum}{{293}{108}} \@writefile{toc}{\contentsline {question}{\numberline {294}Defining macros within macros}{109}} \newlabel{Q-hash}{{294}{109}} -\@writefile{toc}{\contentsline {question}{\numberline {295}Spaces in macros}{109}} -\newlabel{Q-spinmacro}{{295}{109}} +\@writefile{toc}{\contentsline {question}{\numberline {295}Spaces in macros}{110}} +\newlabel{Q-spinmacro}{{295}{110}} \@writefile{toc}{\contentsline {question}{\numberline {296}How to break the 9-argument limit}{110}} \newlabel{Q-moren9}{{296}{110}} -\@writefile{toc}{\contentsline {question}{\numberline {297}Defining characters as macros}{110}} -\newlabel{Q-activechars}{{297}{110}} -\@writefile{toc}{\contentsline {question}{\numberline {298}Active characters in command arguments}{111}} -\newlabel{Q-actinarg}{{298}{111}} -\@writefile{toc}{\contentsline {question}{\numberline {299}Defining a macro from an argument}{111}} -\newlabel{Q-csname}{{299}{111}} -\@writefile{toc}{\contentsline {question}{\numberline {300}Transcribing La\TeX {} command definitions}{112}} -\newlabel{Q-cvtlatex}{{300}{112}} -\@writefile{toc}{\contentsline {question}{\numberline {301}Detecting that something is empty}{112}} -\newlabel{Q-empty}{{301}{112}} +\@writefile{toc}{\contentsline {question}{\numberline {297}Defining characters as macros}{111}} +\newlabel{Q-activechars}{{297}{111}} +\@writefile{toc}{\contentsline {question}{\numberline {298}Active characters in command arguments}{112}} +\newlabel{Q-actinarg}{{298}{112}} +\@writefile{toc}{\contentsline {question}{\numberline {299}Defining a macro from an argument}{112}} +\newlabel{Q-csname}{{299}{112}} +\@writefile{toc}{\contentsline {question}{\numberline {300}Transcribing La\TeX {} command definitions}{113}} +\newlabel{Q-cvtlatex}{{300}{113}} +\@writefile{toc}{\contentsline {question}{\numberline {301}Detecting that something is empty}{113}} +\newlabel{Q-empty}{{301}{113}} \@writefile{toc}{\contentsline {question}{\numberline {302}Am I using PDF\TeX {}?}{113}} \newlabel{Q-ifpdf}{{302}{113}} -\@writefile{toc}{\contentsline {question}{\numberline {303}Subverting a token register}{113}} -\newlabel{Q-subverttoks}{{303}{113}} -\@writefile{toc}{\contentsline {subsection}{\numberline {S.2}La\TeX {} macro tools and techniques}{113}} -\@writefile{toc}{\contentsline {question}{\numberline {304}Using Plain or primitive commands in La\TeX {}}{113}} -\newlabel{Q-plninltx}{{304}{113}} -\@writefile{toc}{\contentsline {question}{\numberline {305}\csx {@} and \texttt {@} in macro names}{114}} -\newlabel{Q-atsigns}{{305}{114}} -\@writefile{toc}{\contentsline {question}{\numberline {306}What's the reason for `protection'?}{114}} -\newlabel{Q-protect}{{306}{114}} -\@writefile{toc}{\contentsline {question}{\numberline {307}\csx {edef} does not work with \csx {protect}}{115}} -\newlabel{Q-edef}{{307}{115}} -\@writefile{toc}{\contentsline {question}{\numberline {308}The definitions of La\TeX {} commands}{115}} -\newlabel{Q-ltxcmds}{{308}{115}} -\@writefile{toc}{\contentsline {question}{\numberline {309}Optional arguments like \csx {section}}{116}} -\newlabel{Q-oarglikesect}{{309}{116}} -\@writefile{toc}{\contentsline {question}{\numberline {310}More than one optional argument}{116}} -\newlabel{Q-twooptarg}{{310}{116}} -\@writefile{toc}{\contentsline {question}{\numberline {311}Commands defined with * options}{116}} -\newlabel{Q-cmdstar}{{311}{116}} -\@writefile{toc}{\contentsline {question}{\numberline {312}La\TeX {} internal ``abbreviations'', etc.}{117}} -\newlabel{Q-ltxabbrv}{{312}{117}} -\@writefile{toc}{\contentsline {question}{\numberline {313}Defining La\TeX {} commands within other commands}{117}} -\newlabel{Q-ltxhash}{{313}{117}} -\@writefile{toc}{\contentsline {subsection}{\numberline {S.3}La\TeX {} macro programming}{117}} -\@writefile{toc}{\contentsline {question}{\numberline {314}How to change La\TeX {}'s ``fixed names''}{117}} -\newlabel{Q-fixnam}{{314}{117}} -\@writefile{toc}{\contentsline {question}{\numberline {315}Changing the words \ProgName {babel} uses}{118}} -\newlabel{Q-latexwords}{{315}{118}} -\@writefile{toc}{\contentsline {question}{\numberline {316}Running equation, figure and table numbering}{118}} -\newlabel{Q-running-nos}{{316}{118}} -\@writefile{toc}{\contentsline {question}{\numberline {317}Making labels from a counter}{118}} -\newlabel{Q-labelctr}{{317}{118}} -\@writefile{toc}{\contentsline {question}{\numberline {318}Finding if you're on an odd or an even page}{118}} -\newlabel{Q-oddpage}{{318}{118}} -\@writefile{toc}{\contentsline {question}{\numberline {319}How to change the format of labels}{119}} -\newlabel{Q-labelformat}{{319}{119}} -\@writefile{toc}{\contentsline {question}{\numberline {320}Adjusting the presentation of section numbers}{119}} -\newlabel{Q-seccntfmt}{{320}{119}} -\@writefile{toc}{\contentsline {question}{\numberline {321}There's a space added after my environment}{120}} -\newlabel{Q-spaftend}{{321}{120}} -\@writefile{toc}{\contentsline {question}{\numberline {322}Finding if a label is undefined}{120}} -\newlabel{Q-labundef}{{322}{120}} -\@writefile{toc}{\contentsline {question}{\numberline {323}Master and slave counters}{120}} -\newlabel{Q-addtoreset}{{323}{120}} -\@writefile{toc}{\contentsline {section}{\numberline {T}Things are Going Wrong\dots {}}{121}} -\@writefile{toc}{\contentsline {subsection}{\numberline {T.1}Getting things to fit}{121}} -\@writefile{toc}{\contentsline {question}{\numberline {324}Enlarging \TeX {}}{121}} -\newlabel{Q-enlarge}{{324}{121}} -\@writefile{toc}{\contentsline {question}{\numberline {325}Why can't I load PiC\TeX {}?}{121}} -\newlabel{Q-usepictex}{{325}{121}} -\@writefile{toc}{\contentsline {subsection}{\numberline {T.2}Making things stay where you want them}{121}} -\@writefile{toc}{\contentsline {question}{\numberline {326}Moving tables and figures in La\TeX {}}{121}} -\newlabel{Q-floats}{{326}{121}} -\@writefile{toc}{\contentsline {question}{\numberline {327}Underlined text won't break}{122}} -\newlabel{Q-underline}{{327}{122}} -\@writefile{toc}{\contentsline {question}{\numberline {328}Controlling widows and orphans}{122}} -\newlabel{Q-widows}{{328}{122}} -\@writefile{toc}{\contentsline {subsection}{\numberline {T.3}Things have ``gone away''}{123}} -\@writefile{toc}{\contentsline {question}{\numberline {329}Old La\TeX {} font references such as \csx {tenrm}}{123}} -\newlabel{Q-oldfontnames}{{329}{123}} -\@writefile{toc}{\contentsline {question}{\numberline {330}Missing symbol commands}{123}} -\newlabel{Q-missssymb}{{330}{123}} -\@writefile{toc}{\contentsline {question}{\numberline {331}Where are the \texttt {msx} and \texttt {msy} fonts?}{123}} -\newlabel{Q-msxy}{{331}{123}} -\@writefile{toc}{\contentsline {question}{\numberline {332}Where are the \texttt {am} fonts?}{123}} -\newlabel{Q-amfonts}{{332}{123}} -\@writefile{toc}{\contentsline {section}{\numberline {U}Why does it \emph {do} that?}{123}} -\@writefile{toc}{\contentsline {subsection}{\numberline {U.1}Common errors}{123}} -\@writefile{toc}{\contentsline {question}{\numberline {333}La\TeX {} gets cross-references wrong}{123}} -\newlabel{Q-crossref}{{333}{123}} -\@writefile{toc}{\contentsline {question}{\numberline {334}Start of line goes awry}{124}} -\newlabel{Q-newlineargs}{{334}{124}} -\@writefile{toc}{\contentsline {question}{\numberline {335}Why doesn't verbatim work within\,\dots {}?}{124}} -\newlabel{Q-verbwithin}{{335}{124}} -\@writefile{toc}{\contentsline {question}{\numberline {336}No line here to end}{125}} -\newlabel{Q-noline}{{336}{125}} -\@writefile{toc}{\contentsline {question}{\numberline {337}Two-column float numbers out of order}{125}} -\newlabel{Q-2colfltorder}{{337}{125}} -\@writefile{toc}{\contentsline {question}{\numberline {338}Accents misbehave in \texttt {tabbing}}{126}} -\newlabel{Q-tabacc}{{338}{126}} -\@writefile{toc}{\contentsline {question}{\numberline {339}Package reports ``command already defined''}{126}} -\newlabel{Q-alreadydef}{{339}{126}} -\@writefile{toc}{\contentsline {question}{\numberline {340}Why are my sections numbered 0.1\,\dots {}?}{126}} -\newlabel{Q-zerochap}{{340}{126}} -\@writefile{toc}{\contentsline {question}{\numberline {341}Link text doesn't break at end line}{126}} -\newlabel{Q-breaklinks}{{341}{126}} -\@writefile{toc}{\contentsline {question}{\numberline {342}Page number is wrong at start of page}{127}} -\newlabel{Q-wrongpn}{{342}{127}} -\@writefile{toc}{\contentsline {question}{\numberline {343}My brackets don't match}{127}} -\newlabel{Q-matchbrak}{{343}{127}} -\@writefile{toc}{\contentsline {subsection}{\numberline {U.2}Common misunderstandings}{127}} -\@writefile{toc}{\contentsline {question}{\numberline {344}What's going on in my \csx {include} commands?}{127}} -\newlabel{Q-include}{{344}{127}} -\@writefile{toc}{\contentsline {question}{\numberline {345}Why does it ignore paragraph parameters?}{128}} -\newlabel{Q-paraparam}{{345}{128}} -\@writefile{toc}{\contentsline {question}{\numberline {346}Case-changing oddities}{128}} -\newlabel{Q-casechange}{{346}{128}} -\@writefile{toc}{\contentsline {question}{\numberline {347}Why does La\TeX {} split footnotes across pages?}{128}} -\newlabel{Q-splitfoot}{{347}{128}} -\@writefile{toc}{\contentsline {question}{\numberline {348}Getting \csx {marginpar} on the right side}{129}} -\newlabel{Q-marginparside}{{348}{129}} -\@writefile{toc}{\contentsline {question}{\numberline {349}Where have my characters gone?}{129}} -\newlabel{Q-misschar}{{349}{129}} -\@writefile{toc}{\contentsline {question}{\numberline {350}``Rerun'' messages won't go away}{129}} -\newlabel{Q-rerun}{{350}{129}} -\@writefile{toc}{\contentsline {question}{\numberline {351}Commands gobble following space}{129}} -\newlabel{Q-xspace}{{351}{129}} -\@writefile{toc}{\contentsline {question}{\numberline {352}(La)\TeX {} makes overfull lines}{130}} -\newlabel{Q-overfull}{{352}{130}} -\@writefile{toc}{\contentsline {question}{\numberline {353}Maths symbols don't scale up}{131}} -\newlabel{Q-exscale}{{353}{131}} -\@writefile{toc}{\contentsline {question}{\numberline {354}Why doesn't \csx {linespread} work?}{131}} -\newlabel{Q-linespread}{{354}{131}} -\@writefile{toc}{\contentsline {question}{\numberline {355}Only one \csx {baselineskip} per paragraph}{131}} -\newlabel{Q-baselinepar}{{355}{131}} -\@writefile{toc}{\contentsline {question}{\numberline {356}Numbers too large in table of contents, etc.}{132}} -\newlabel{Q-tocloftwrong}{{356}{132}} -\@writefile{toc}{\contentsline {question}{\numberline {357}Why is the inside margin so narrow?}{132}} -\newlabel{Q-gutter}{{357}{132}} -\@writefile{toc}{\contentsline {subsection}{\numberline {U.3}Why shouldn't I?}{132}} -\@writefile{toc}{\contentsline {question}{\numberline {358}Why use \ProgName {fontenc} rather than \ProgName {t1enc}?}{132}} -\newlabel{Q-t1enc}{{358}{132}} -\@writefile{toc}{\contentsline {question}{\numberline {359}Why bother with \ProgName {inputenc} and \ProgName {fontenc}?}{132}} -\newlabel{Q-why-inp-font}{{359}{132}} -\@writefile{toc}{\contentsline {question}{\numberline {360}Why not use \texttt {eqnarray}?}{132}} -\newlabel{Q-eqnarray}{{360}{132}} -\@writefile{toc}{\contentsline {question}{\numberline {361}Why use \csx {[}\,\dots {}\csx {]} in place of \texttt {\$\$}\,\dots {}\texttt {\$\$}?}{133}} -\newlabel{Q-dolldoll}{{361}{133}} -\@writefile{toc}{\contentsline {question}{\numberline {362}What's wrong with \csx {bf}, \csx {it}, etc.?}{133}} -\newlabel{Q-2letterfontcmd}{{362}{133}} -\@writefile{toc}{\contentsline {question}{\numberline {363}What's wrong with \csx {newfont}?}{134}} -\newlabel{Q-newfont}{{363}{134}} -\@writefile{toc}{\contentsline {section}{\numberline {V}The joy of \TeX {} errors}{134}} -\@writefile{toc}{\contentsline {question}{\numberline {364}How to approach errors}{134}} -\newlabel{Q-erroradvice}{{364}{134}} -\@writefile{toc}{\contentsline {question}{\numberline {365}The structure of \TeX {} error messages}{135}} -\newlabel{Q-errstruct}{{365}{135}} -\@writefile{toc}{\contentsline {question}{\numberline {366}An extra `\texttt {\char 125\relax {}}'??}{135}} -\newlabel{Q-extrabrace}{{366}{135}} -\@writefile{toc}{\contentsline {question}{\numberline {367}Capacity exceeded [semantic nest\,\dots {}]}{135}} -\newlabel{Q-semanticnest}{{367}{135}} -\@writefile{toc}{\contentsline {question}{\numberline {368}No room for a new `\emph {thing}'}{136}} -\newlabel{Q-noroom}{{368}{136}} -\@writefile{toc}{\contentsline {question}{\numberline {369}\texttt {epsf} gives up after a bit}{136}} -\newlabel{Q-epsf}{{369}{136}} -\@writefile{toc}{\contentsline {question}{\numberline {370}Improper \csx {hyphenation} will be flushed}{136}} -\newlabel{Q-badhyph}{{370}{136}} -\@writefile{toc}{\contentsline {question}{\numberline {371}``Too many unprocessed floats''}{136}} -\newlabel{Q-tmupfl}{{371}{136}} -\@writefile{toc}{\contentsline {question}{\numberline {372}\csx {spacefactor} complaints}{137}} -\newlabel{Q-atvert}{{372}{137}} -\@writefile{toc}{\contentsline {question}{\numberline {373}\csx {end} occurred inside a group}{137}} -\newlabel{Q-endingroup}{{373}{137}} -\@writefile{toc}{\contentsline {question}{\numberline {374}``Missing number, treated as zero''}{137}} -\newlabel{Q-nonum}{{374}{137}} -\@writefile{toc}{\contentsline {question}{\numberline {375}``Please type a command or say \csx {end}''}{138}} -\newlabel{Q-typend}{{375}{138}} -\@writefile{toc}{\contentsline {question}{\numberline {376}``Unknown graphics extension''}{138}} -\newlabel{Q-unkgrfextn}{{376}{138}} -\@writefile{toc}{\contentsline {question}{\numberline {377}``Missing \texttt {\$} inserted''}{138}} -\newlabel{Q-nodollar}{{377}{138}} -\@writefile{toc}{\contentsline {question}{\numberline {378}Warning: ``Font shape \dots {}\ not available''}{139}} -\newlabel{Q-fontunavail}{{378}{139}} -\@writefile{toc}{\contentsline {question}{\numberline {379}Unable to read an entire line}{139}} -\newlabel{Q-buffovl}{{379}{139}} -\@writefile{toc}{\contentsline {question}{\numberline {380}``Fatal format file error; I'm stymied''}{139}} -\newlabel{Q-formatstymy}{{380}{139}} -\@writefile{toc}{\contentsline {question}{\numberline {381}Non-\acro {PDF} special ignored!}{140}} -\newlabel{Q-nonpdfsp}{{381}{140}} -\@writefile{toc}{\contentsline {question}{\numberline {382}Mismatched mode ljfour and resolution 8000}{140}} -\newlabel{Q-8000}{{382}{140}} -\@writefile{toc}{\contentsline {question}{\numberline {383}``Too deeply nested''}{140}} -\newlabel{Q-toodeep}{{383}{140}} -\@writefile{toc}{\contentsline {question}{\numberline {384}Capacity exceeded\nobreakspace {}--- input levels}{141}} -\newlabel{Q-inputlev}{{384}{141}} -\@writefile{toc}{\contentsline {question}{\numberline {385}PDF\TeX {} destination \dots {} ignored}{141}} -\newlabel{Q-hyperdupdest}{{385}{141}} -\@writefile{toc}{\contentsline {question}{\numberline {386}Alignment tab changed to \csx {cr}}{141}} -\newlabel{Q-altabcr}{{386}{141}} -\@writefile{toc}{\contentsline {question}{\numberline {387}Graphics division by zero}{141}} -\newlabel{Q-divzero}{{387}{141}} -\@writefile{toc}{\contentsline {question}{\numberline {388}Missing \csx {begin}\texttt {\char 123\relax {document}\char 125\relax }}{142}} -\newlabel{Q-missbegdoc}{{388}{142}} -\@writefile{toc}{\contentsline {question}{\numberline {389}\csx {normalsize} not defined}{142}} -\newlabel{Q-normalszmiss}{{389}{142}} -\@writefile{toc}{\contentsline {question}{\numberline {390}Too many math alphabets}{142}} -\newlabel{Q-manymathalph}{{390}{142}} -\@writefile{toc}{\contentsline {question}{\numberline {391}Not in outer par mode}{142}} -\newlabel{Q-ouparmd}{{391}{142}} -\@writefile{toc}{\contentsline {question}{\numberline {392}Perhaps a missing \csx {item}?}{143}} -\newlabel{Q-errmissitem}{{392}{143}} -\@writefile{toc}{\contentsline {question}{\numberline {393}Illegal parameter number in definition}{143}} -\newlabel{Q-errparnum}{{393}{143}} -\@writefile{toc}{\contentsline {question}{\numberline {394}Float(s) lost}{143}} -\newlabel{Q-fllost}{{394}{143}} -\@writefile{toc}{\contentsline {question}{\numberline {395}Option clash for package}{143}} -\newlabel{Q-optionclash}{{395}{143}} -\@writefile{toc}{\contentsline {section}{\numberline {W}Current \TeX {}-related projects}{144}} -\@writefile{toc}{\contentsline {question}{\numberline {396}The La\TeX {}3 project}{144}} -\newlabel{Q-LaTeX3}{{396}{144}} -\@writefile{toc}{\contentsline {question}{\numberline {397}Future \acro {WWW} technologies and (La)\TeX {}}{144}} -\newlabel{Q-mathml}{{397}{144}} -\@writefile{toc}{\contentsline {question}{\numberline {398}Making outline fonts from \MF {}}{145}} -\newlabel{Q-textrace}{{398}{145}} -\@writefile{toc}{\contentsline {question}{\numberline {399}The \TeX {} document preparation environment}{145}} -\newlabel{Q-WYGexpts}{{399}{145}} -\@writefile{toc}{\contentsline {question}{\numberline {400}The \textsf {ANT} typesetting system}{146}} -\newlabel{Q-ant}{{400}{146}} -\@writefile{toc}{\contentsline {question}{\numberline {401}The Ex\TeX {} project}{146}} -\newlabel{Q-extex}{{401}{146}} -\@writefile{toc}{\contentsline {question}{\numberline {402}Omega and Aleph}{147}} -\newlabel{Q-omegaleph}{{402}{147}} -\@writefile{toc}{\contentsline {question}{\numberline {403}PDF\TeX {} becomes \acro {LUA}\TeX {}}{147}} -\newlabel{Q-luatex}{{403}{147}} -\@writefile{toc}{\contentsline {question}{\numberline {404}The XeTeX project}{147}} -\newlabel{Q-xetex}{{404}{147}} -\@writefile{toc}{\contentsline {section}{\numberline {X}You're still stuck?}{147}} -\@writefile{toc}{\contentsline {question}{\numberline {405}You don't understand the answer}{147}} -\newlabel{Q-noans}{{405}{147}} -\@writefile{toc}{\contentsline {question}{\numberline {406}Submitting new material for the \acro {FAQ}}{147}} -\newlabel{Q-newans}{{406}{147}} -\@writefile{toc}{\contentsline {question}{\numberline {407}Reporting a La\TeX {} bug}{147}} -\newlabel{Q-latexbug}{{407}{147}} -\@writefile{toc}{\contentsline {question}{\numberline {408}What to do if you find a bug}{148}} -\newlabel{Q-bug}{{408}{148}} -\newlabel{lastquestion}{{408}{148}} +\@writefile{toc}{\contentsline {question}{\numberline {303}Subverting a token register}{114}} +\newlabel{Q-subverttoks}{{303}{114}} +\@writefile{toc}{\contentsline {question}{\numberline {304}Is this command defined?}{114}} +\newlabel{Q-isdef}{{304}{114}} +\@writefile{toc}{\contentsline {subsection}{\numberline {S.2}La\TeX {} macro tools and techniques}{115}} +\@writefile{toc}{\contentsline {question}{\numberline {305}Using Plain or primitive commands in La\TeX {}}{115}} +\newlabel{Q-plninltx}{{305}{115}} +\@writefile{toc}{\contentsline {question}{\numberline {306}\csx {@} and \texttt {@} in macro names}{115}} +\newlabel{Q-atsigns}{{306}{115}} +\@writefile{toc}{\contentsline {question}{\numberline {307}What's the reason for `protection'?}{116}} +\newlabel{Q-protect}{{307}{116}} +\@writefile{toc}{\contentsline {question}{\numberline {308}\csx {edef} does not work with \csx {protect}}{116}} +\newlabel{Q-edef}{{308}{116}} +\@writefile{toc}{\contentsline {question}{\numberline {309}The definitions of La\TeX {} commands}{116}} +\newlabel{Q-ltxcmds}{{309}{116}} +\@writefile{toc}{\contentsline {question}{\numberline {310}Optional arguments like \csx {section}}{117}} +\newlabel{Q-oarglikesect}{{310}{117}} +\@writefile{toc}{\contentsline {question}{\numberline {311}More than one optional argument}{117}} +\newlabel{Q-twooptarg}{{311}{117}} +\@writefile{toc}{\contentsline {question}{\numberline {312}Commands defined with * options}{118}} +\newlabel{Q-cmdstar}{{312}{118}} +\@writefile{toc}{\contentsline {question}{\numberline {313}La\TeX {} internal ``abbreviations'', etc.}{118}} +\newlabel{Q-ltxabbrv}{{313}{118}} +\@writefile{toc}{\contentsline {question}{\numberline {314}Defining La\TeX {} commands within other commands}{118}} +\newlabel{Q-ltxhash}{{314}{118}} +\@writefile{toc}{\contentsline {subsection}{\numberline {S.3}La\TeX {} macro programming}{119}} +\@writefile{toc}{\contentsline {question}{\numberline {315}How to change La\TeX {}'s ``fixed names''}{119}} +\newlabel{Q-fixnam}{{315}{119}} +\@writefile{toc}{\contentsline {question}{\numberline {316}Changing the words \ProgName {babel} uses}{119}} +\newlabel{Q-latexwords}{{316}{119}} +\@writefile{toc}{\contentsline {question}{\numberline {317}Running equation, figure and table numbering}{119}} +\newlabel{Q-running-nos}{{317}{119}} +\@writefile{toc}{\contentsline {question}{\numberline {318}Making labels from a counter}{120}} +\newlabel{Q-labelctr}{{318}{120}} +\@writefile{toc}{\contentsline {question}{\numberline {319}Finding if you're on an odd or an even page}{120}} +\newlabel{Q-oddpage}{{319}{120}} +\@writefile{toc}{\contentsline {question}{\numberline {320}How to change the format of labels}{120}} +\newlabel{Q-labelformat}{{320}{120}} +\@writefile{toc}{\contentsline {question}{\numberline {321}Adjusting the presentation of section numbers}{121}} +\newlabel{Q-seccntfmt}{{321}{121}} +\@writefile{toc}{\contentsline {question}{\numberline {322}There's a space added after my environment}{121}} +\newlabel{Q-spaftend}{{322}{121}} +\@writefile{toc}{\contentsline {question}{\numberline {323}Finding if a label is undefined}{121}} +\newlabel{Q-labundef}{{323}{121}} +\@writefile{toc}{\contentsline {question}{\numberline {324}Master and slave counters}{122}} +\newlabel{Q-addtoreset}{{324}{122}} +\@writefile{toc}{\contentsline {section}{\numberline {T}Things are Going Wrong\dots {}}{122}} +\@writefile{toc}{\contentsline {subsection}{\numberline {T.1}Getting things to fit}{122}} +\@writefile{toc}{\contentsline {question}{\numberline {325}Enlarging \TeX {}}{122}} +\newlabel{Q-enlarge}{{325}{122}} +\@writefile{toc}{\contentsline {question}{\numberline {326}Why can't I load PiC\TeX {}?}{123}} +\newlabel{Q-usepictex}{{326}{123}} +\@writefile{toc}{\contentsline {subsection}{\numberline {T.2}Making things stay where you want them}{123}} +\@writefile{toc}{\contentsline {question}{\numberline {327}Moving tables and figures in La\TeX {}}{123}} +\newlabel{Q-floats}{{327}{123}} +\@writefile{toc}{\contentsline {question}{\numberline {328}Underlined text won't break}{124}} +\newlabel{Q-underline}{{328}{124}} +\@writefile{toc}{\contentsline {question}{\numberline {329}Controlling widows and orphans}{124}} +\newlabel{Q-widows}{{329}{124}} +\@writefile{toc}{\contentsline {subsection}{\numberline {T.3}Things have ``gone away''}{124}} +\@writefile{toc}{\contentsline {question}{\numberline {330}Old La\TeX {} font references such as \csx {tenrm}}{124}} +\newlabel{Q-oldfontnames}{{330}{124}} +\@writefile{toc}{\contentsline {question}{\numberline {331}Missing symbol commands}{124}} +\newlabel{Q-missssymb}{{331}{124}} +\@writefile{toc}{\contentsline {question}{\numberline {332}Where are the \texttt {msx} and \texttt {msy} fonts?}{125}} +\newlabel{Q-msxy}{{332}{125}} +\@writefile{toc}{\contentsline {question}{\numberline {333}Where are the \texttt {am} fonts?}{125}} +\newlabel{Q-amfonts}{{333}{125}} +\@writefile{toc}{\contentsline {section}{\numberline {U}Why does it \emph {do} that?}{125}} +\@writefile{toc}{\contentsline {subsection}{\numberline {U.1}Common errors}{125}} +\@writefile{toc}{\contentsline {question}{\numberline {334}La\TeX {} gets cross-references wrong}{125}} +\newlabel{Q-crossref}{{334}{125}} +\@writefile{toc}{\contentsline {question}{\numberline {335}Start of line goes awry}{125}} +\newlabel{Q-newlineargs}{{335}{125}} +\@writefile{toc}{\contentsline {question}{\numberline {336}Why doesn't verbatim work within\,\dots {}?}{126}} +\newlabel{Q-verbwithin}{{336}{126}} +\@writefile{toc}{\contentsline {question}{\numberline {337}No line here to end}{126}} +\newlabel{Q-noline}{{337}{126}} +\@writefile{toc}{\contentsline {question}{\numberline {338}Two-column float numbers out of order}{127}} +\newlabel{Q-2colfltorder}{{338}{127}} +\@writefile{toc}{\contentsline {question}{\numberline {339}Accents misbehave in \texttt {tabbing}}{127}} +\newlabel{Q-tabacc}{{339}{127}} +\@writefile{toc}{\contentsline {question}{\numberline {340}Package reports ``command already defined''}{128}} +\newlabel{Q-alreadydef}{{340}{128}} +\@writefile{toc}{\contentsline {question}{\numberline {341}Why are my sections numbered 0.1\,\dots {}?}{128}} +\newlabel{Q-zerochap}{{341}{128}} +\@writefile{toc}{\contentsline {question}{\numberline {342}Link text doesn't break at end line}{128}} +\newlabel{Q-breaklinks}{{342}{128}} +\@writefile{toc}{\contentsline {question}{\numberline {343}Page number is wrong at start of page}{128}} +\newlabel{Q-wrongpn}{{343}{128}} +\@writefile{toc}{\contentsline {question}{\numberline {344}My brackets don't match}{129}} +\newlabel{Q-matchbrak}{{344}{129}} +\@writefile{toc}{\contentsline {subsection}{\numberline {U.2}Common misunderstandings}{129}} +\@writefile{toc}{\contentsline {question}{\numberline {345}What's going on in my \csx {include} commands?}{129}} +\newlabel{Q-include}{{345}{129}} +\@writefile{toc}{\contentsline {question}{\numberline {346}Why does it ignore paragraph parameters?}{129}} +\newlabel{Q-paraparam}{{346}{129}} +\@writefile{toc}{\contentsline {question}{\numberline {347}Case-changing oddities}{130}} +\newlabel{Q-casechange}{{347}{130}} +\@writefile{toc}{\contentsline {question}{\numberline {348}Why does La\TeX {} split footnotes across pages?}{130}} +\newlabel{Q-splitfoot}{{348}{130}} +\@writefile{toc}{\contentsline {question}{\numberline {349}Getting \csx {marginpar} on the right side}{130}} +\newlabel{Q-marginparside}{{349}{130}} +\@writefile{toc}{\contentsline {question}{\numberline {350}Where have my characters gone?}{131}} +\newlabel{Q-misschar}{{350}{131}} +\@writefile{toc}{\contentsline {question}{\numberline {351}``Rerun'' messages won't go away}{131}} +\newlabel{Q-rerun}{{351}{131}} +\@writefile{toc}{\contentsline {question}{\numberline {352}Commands gobble following space}{131}} +\newlabel{Q-xspace}{{352}{131}} +\@writefile{toc}{\contentsline {question}{\numberline {353}(La)\TeX {} makes overfull lines}{131}} +\newlabel{Q-overfull}{{353}{131}} +\@writefile{toc}{\contentsline {question}{\numberline {354}Maths symbols don't scale up}{132}} +\newlabel{Q-exscale}{{354}{132}} +\@writefile{toc}{\contentsline {question}{\numberline {355}Why doesn't \csx {linespread} work?}{133}} +\newlabel{Q-linespread}{{355}{133}} +\@writefile{toc}{\contentsline {question}{\numberline {356}Only one \csx {baselineskip} per paragraph}{133}} +\newlabel{Q-baselinepar}{{356}{133}} +\@writefile{toc}{\contentsline {question}{\numberline {357}Numbers too large in table of contents, etc.}{133}} +\newlabel{Q-tocloftwrong}{{357}{133}} +\@writefile{toc}{\contentsline {question}{\numberline {358}Why is the inside margin so narrow?}{133}} +\newlabel{Q-gutter}{{358}{133}} +\@writefile{toc}{\contentsline {subsection}{\numberline {U.3}Why shouldn't I?}{134}} +\@writefile{toc}{\contentsline {question}{\numberline {359}Why use \ProgName {fontenc} rather than \ProgName {t1enc}?}{134}} +\newlabel{Q-t1enc}{{359}{134}} +\@writefile{toc}{\contentsline {question}{\numberline {360}Why bother with \ProgName {inputenc} and \ProgName {fontenc}?}{134}} +\newlabel{Q-why-inp-font}{{360}{134}} +\@writefile{toc}{\contentsline {question}{\numberline {361}Why not use \texttt {eqnarray}?}{134}} +\newlabel{Q-eqnarray}{{361}{134}} +\@writefile{toc}{\contentsline {question}{\numberline {362}Why use \csx {[}\,\dots {}\csx {]} in place of \texttt {\$\$}\,\dots {}\texttt {\$\$}?}{134}} +\newlabel{Q-dolldoll}{{362}{134}} +\@writefile{toc}{\contentsline {question}{\numberline {363}What's wrong with \csx {bf}, \csx {it}, etc.?}{135}} +\newlabel{Q-2letterfontcmd}{{363}{135}} +\@writefile{toc}{\contentsline {question}{\numberline {364}What's wrong with \csx {newfont}?}{135}} +\newlabel{Q-newfont}{{364}{135}} +\@writefile{toc}{\contentsline {section}{\numberline {V}The joy of \TeX {} errors}{136}} +\@writefile{toc}{\contentsline {question}{\numberline {365}How to approach errors}{136}} +\newlabel{Q-erroradvice}{{365}{136}} +\@writefile{toc}{\contentsline {question}{\numberline {366}The structure of \TeX {} error messages}{136}} +\newlabel{Q-errstruct}{{366}{136}} +\@writefile{toc}{\contentsline {question}{\numberline {367}An extra `\texttt {\char 125\relax {}}'??}{137}} +\newlabel{Q-extrabrace}{{367}{137}} +\@writefile{toc}{\contentsline {question}{\numberline {368}Capacity exceeded [semantic nest\,\dots {}]}{137}} +\newlabel{Q-semanticnest}{{368}{137}} +\@writefile{toc}{\contentsline {question}{\numberline {369}No room for a new `\emph {thing}'}{137}} +\newlabel{Q-noroom}{{369}{137}} +\@writefile{toc}{\contentsline {question}{\numberline {370}\texttt {epsf} gives up after a bit}{138}} +\newlabel{Q-epsf}{{370}{138}} +\@writefile{toc}{\contentsline {question}{\numberline {371}Improper \csx {hyphenation} will be flushed}{138}} +\newlabel{Q-badhyph}{{371}{138}} +\@writefile{toc}{\contentsline {question}{\numberline {372}``Too many unprocessed floats''}{138}} +\newlabel{Q-tmupfl}{{372}{138}} +\@writefile{toc}{\contentsline {question}{\numberline {373}\csx {spacefactor} complaints}{138}} +\newlabel{Q-atvert}{{373}{138}} +\@writefile{toc}{\contentsline {question}{\numberline {374}\csx {end} occurred inside a group}{139}} +\newlabel{Q-endingroup}{{374}{139}} +\@writefile{toc}{\contentsline {question}{\numberline {375}``Missing number, treated as zero''}{139}} +\newlabel{Q-nonum}{{375}{139}} +\@writefile{toc}{\contentsline {question}{\numberline {376}``Please type a command or say \csx {end}''}{139}} +\newlabel{Q-typend}{{376}{139}} +\@writefile{toc}{\contentsline {question}{\numberline {377}``Unknown graphics extension''}{140}} +\newlabel{Q-unkgrfextn}{{377}{140}} +\@writefile{toc}{\contentsline {question}{\numberline {378}``Missing \texttt {\$} inserted''}{140}} +\newlabel{Q-nodollar}{{378}{140}} +\@writefile{toc}{\contentsline {question}{\numberline {379}Warning: ``Font shape \dots {}\ not available''}{140}} +\newlabel{Q-fontunavail}{{379}{140}} +\@writefile{toc}{\contentsline {question}{\numberline {380}Unable to read an entire line}{141}} +\newlabel{Q-buffovl}{{380}{141}} +\@writefile{toc}{\contentsline {question}{\numberline {381}``Fatal format file error; I'm stymied''}{141}} +\newlabel{Q-formatstymy}{{381}{141}} +\@writefile{toc}{\contentsline {question}{\numberline {382}Non-\acro {PDF} special ignored!}{141}} +\newlabel{Q-nonpdfsp}{{382}{141}} +\@writefile{toc}{\contentsline {question}{\numberline {383}Mismatched mode ljfour and resolution 8000}{142}} +\newlabel{Q-8000}{{383}{142}} +\@writefile{toc}{\contentsline {question}{\numberline {384}``Too deeply nested''}{142}} +\newlabel{Q-toodeep}{{384}{142}} +\@writefile{toc}{\contentsline {question}{\numberline {385}Capacity exceeded\nobreakspace {}--- input levels}{142}} +\newlabel{Q-inputlev}{{385}{142}} +\@writefile{toc}{\contentsline {question}{\numberline {386}PDF\TeX {} destination \dots {} ignored}{142}} +\newlabel{Q-hyperdupdest}{{386}{142}} +\@writefile{toc}{\contentsline {question}{\numberline {387}Alignment tab changed to \csx {cr}}{143}} +\newlabel{Q-altabcr}{{387}{143}} +\@writefile{toc}{\contentsline {question}{\numberline {388}Graphics division by zero}{143}} +\newlabel{Q-divzero}{{388}{143}} +\@writefile{toc}{\contentsline {question}{\numberline {389}Missing \csx {begin}\texttt {\char 123\relax {document}\char 125\relax }}{143}} +\newlabel{Q-missbegdoc}{{389}{143}} +\@writefile{toc}{\contentsline {question}{\numberline {390}\csx {normalsize} not defined}{143}} +\newlabel{Q-normalszmiss}{{390}{143}} +\@writefile{toc}{\contentsline {question}{\numberline {391}Too many math alphabets}{144}} +\newlabel{Q-manymathalph}{{391}{144}} +\@writefile{toc}{\contentsline {question}{\numberline {392}Not in outer par mode}{144}} +\newlabel{Q-ouparmd}{{392}{144}} +\@writefile{toc}{\contentsline {question}{\numberline {393}Perhaps a missing \csx {item}?}{144}} +\newlabel{Q-errmissitem}{{393}{144}} +\@writefile{toc}{\contentsline {question}{\numberline {394}Illegal parameter number in definition}{145}} +\newlabel{Q-errparnum}{{394}{145}} +\@writefile{toc}{\contentsline {question}{\numberline {395}Float(s) lost}{145}} +\newlabel{Q-fllost}{{395}{145}} +\@writefile{toc}{\contentsline {question}{\numberline {396}Option clash for package}{145}} +\newlabel{Q-optionclash}{{396}{145}} +\@writefile{toc}{\contentsline {section}{\numberline {W}Current \TeX {}-related projects}{146}} +\@writefile{toc}{\contentsline {question}{\numberline {397}The La\TeX {}3 project}{146}} +\newlabel{Q-LaTeX3}{{397}{146}} +\@writefile{toc}{\contentsline {question}{\numberline {398}Future \acro {WWW} technologies and (La)\TeX {}}{146}} +\newlabel{Q-mathml}{{398}{146}} +\@writefile{toc}{\contentsline {question}{\numberline {399}Making outline fonts from \MF {}}{147}} +\newlabel{Q-textrace}{{399}{147}} +\@writefile{toc}{\contentsline {question}{\numberline {400}The \TeX {} document preparation environment}{147}} +\newlabel{Q-WYGexpts}{{400}{147}} +\@writefile{toc}{\contentsline {question}{\numberline {401}The \textsf {ANT} typesetting system}{148}} +\newlabel{Q-ant}{{401}{148}} +\@writefile{toc}{\contentsline {question}{\numberline {402}The Ex\TeX {} project}{148}} +\newlabel{Q-extex}{{402}{148}} +\@writefile{toc}{\contentsline {question}{\numberline {403}Omega and Aleph}{148}} +\newlabel{Q-omegaleph}{{403}{148}} +\@writefile{toc}{\contentsline {question}{\numberline {404}PDF\TeX {} becomes \acro {LUA}\TeX {}}{148}} +\newlabel{Q-luatex}{{404}{148}} +\@writefile{toc}{\contentsline {question}{\numberline {405}The XeTeX project}{149}} +\newlabel{Q-xetex}{{405}{149}} +\@writefile{toc}{\contentsline {section}{\numberline {X}You're still stuck?}{149}} +\@writefile{toc}{\contentsline {question}{\numberline {406}You don't understand the answer}{149}} +\newlabel{Q-noans}{{406}{149}} +\@writefile{toc}{\contentsline {question}{\numberline {407}Submitting new material for the \acro {FAQ}}{149}} +\newlabel{Q-newans}{{407}{149}} +\@writefile{toc}{\contentsline {question}{\numberline {408}Reporting a La\TeX {} bug}{149}} +\newlabel{Q-latexbug}{{408}{149}} +\@writefile{toc}{\contentsline {question}{\numberline {409}What to do if you find a bug}{150}} +\newlabel{Q-bug}{{409}{150}} +\newlabel{lastquestion}{{409}{150}} diff --git a/Master/texmf-doc/doc/english/FAQ-en/newfaq.pdf b/Master/texmf-doc/doc/english/FAQ-en/newfaq.pdf Binary files differindex 583563b0903..7e8364d48f2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/newfaq.pdf +++ b/Master/texmf-doc/doc/english/FAQ-en/newfaq.pdf diff --git a/Master/texmf-doc/doc/english/FAQ-en/newfaq.tex b/Master/texmf-doc/doc/english/FAQ-en/newfaq.tex index 2fa06b3ea00..a7e20206566 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/newfaq.tex +++ b/Master/texmf-doc/doc/english/FAQ-en/newfaq.tex @@ -33,9 +33,13 @@ The article is also available via the World Wide Web. \end{quotation} -\begin{multicols}{2} -\tableofcontents -\end{multicols} +\ifsinglecolumn + \tableofcontents +\else + \begin{multicols}{2} + \tableofcontents + \end{multicols} +\fi \Dings @@ -48,9 +52,13 @@ \input{filectan} %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -\begin{multicols}{2} -\input{faqbody} -\end{multicols} +\ifsinglecolumn + \input{faqbody} +\else + \begin{multicols}{2} + \input{faqbody} + \end{multicols} +\fi \typeout{*** That makes \thequestion\space questions ***} \end{document} |