diff options
| author | Karl Berry <karl@freefriends.org> | 2011-09-06 23:43:29 +0000 |
|---|---|---|
| committer | Karl Berry <karl@freefriends.org> | 2011-09-06 23:43:29 +0000 |
| commit | e00717e4e1360cacff3625cb7dfd81215968c8a7 (patch) | |
| tree | 152e579b4e78a299dc607c68f6796e5be508a84c | |
| parent | 86431735f0e1623beae96cd8a9f0fcd809fe08bf (diff) | |
FAQ-en 3.23 (6sep11)
git-svn-id: svn://tug.org/texlive/trunk@23849 c570f23f-e606-0410-a88d-b1316a301751
27 files changed, 1182 insertions, 420 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.23 b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.23 new file mode 100644 index 00000000000..47449bc1255 --- /dev/null +++ b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.23 @@ -0,0 +1,50 @@ +Changes since version 3.22 + +New answers: + +Label book-lists: redirector to the dismembered parts of old "label books" + +Label ctan: summary of the salient points of the archives + +Label catalogue: outline of the CTAN catalogue + +Label latex-books: the LaTeX part of old "label books" + +Label other-books: the miscellanea from old "label books" + +Label subdepth: getting even subscripts in your maths + +Label tex-books: TeX and Plain TeX part of old "label books" + +Label type-books: typesetting part of old "label books" + +Relabelled answers: + <none> + +Revised answers: + +Label altabcr: error can be caused by insufficient columns in a matrix + +Label clsvpkg: rewritten with a LaTeX 2e perspective (rather than 2.09) + +Label context: add detail following Hans Hagen's outline in Tugboat 100 + +Label destable: more details of caption above table + +Label doc-dirs: correct link to TUG India tutorials page + +Label drawing: link to intro doc on pgf/TikZ, and sparse docs of DraTeX + +Label gethelp: rewritten for (slightly) improved clarity + +Label hyphen: LuaTeX's hyphenation pattern loading is different + +Label keyval: references to expl3, xpackages replaced with l3* versions + keyval: mention getoptk + +Label labelfig: mention pst-layout; mention that pgf/TikZ is also capable + +Label latex2e: mention "frozen" state + +Label latex3: references to expl3, xpackages replaced with l3* versions + +Label latexqual: mention lacheck + +Label luatex: "clarify" statement about future changes to PDFTeX + luatex: updated versions mentioned; MikTeX now offers LuaTeX + +Label MF: mention sidelining of Metafont in the modern world + +Label patch: use letltxmacro where necessary + +Label RCS: mention gitinfo + +Label texthings: clarify description of luatex + +Label tfm: XeTeX and LuaTeX don't need TFM files + +Label underscore: \_ in OT1 encoding is bad news + +Label useMF: a step in removing archaic baggage from this answer + +Deleted answers: + +Label books: dismembered to produce the new *-books above (the + label is now redirected to book-lists) + +Web interface, etc.: + A small change to the HTML generation has (to the author's eye) + improved the appearance of pages on the web. There remain problems + in this area, despite the improvement. + +Robin Fairbairns diff --git a/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog b/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog index 70cc9cf84cc..568630f16fc 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog +++ b/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog @@ -1,5 +1,283 @@ +2011-09-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + *** Release 3.23 *** + + * texfaq2html, texfaq2html-beta: change "last modified" to "released" + in question footers + + * gather-faqbody.tex: change version, date + + * texfaq2html: minor change from -beta + +2011-09-04 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-fonts.tex (q-usemf): further attempts to drag it into c.21 + (q-keepfonts): modernise and tidy to today's standards + (q-getbitmap): modernisation, again + +2011-09-01 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-backgrnd.tex (q-mp): reword the initial discussion (which had + multiple concepts in the same clause, at one point) + +2011-08-30 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-projects.tex (q-latex3): add l3experimental + + * dirctan.tex: add gitinfo, l3experimental + + * faq-how-do-i.tex (q-rcs): mention gitinfo + +2011-08-19 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-font-fmts): to replace q-adobetypen -- starts + with its content (ha ha) + + * faq-bits+pieces.tex (q-adobetypen): editorial + + * faq-how-do-i.tex (q-destable): editorial + + * faq-backgrnd.tex (q-latex2e): describe frozen state; editorial stuff + +2011-08-17 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-symbols.tex (q-scriptfonts): correct typo + + * faq.sty: add \latexo (all lc) + + * faq-symbols.tex (q-underscore): editorial+ref q-activechars + +2011-08-16 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-symbols.tex (q-underscore): drop stuff about \us, add spiel about + using T1 and \textunderscore + (q-atsign): @ was a special character rather than command + +2011-07-21 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * filectan.tex: remove screensty, add cat link for vf-howto + + * faq-fmt-conv.tex (q-toascii): editorial on catdvi, remove screen.sty + +2011-07-19 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-docs.tex (q-pkgdoc): memoir doc not typo tutorial any more, + mention pgf as an example of separately-written stuff + (q-writecls): bit of editorial + +2011-07-14 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-optclash): new answer about package options + +2011-07-13 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-backgrnd.tex (q-etex): correct ref to luatex in disc of context + (q-eplain): minute editorial + +2011-07-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-bits+pieces.tex (q-clsvpkg): rewrite + +2011-07-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-bits+pieces.tex (q-whatmacros): minor editorial + + * faq-projects.tex (q-luatex): update versions, miktex now has luatex + + * faq-bits+pieces.tex (q-tfm): mention xetex and luatex don't need 'em + +2011-07-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-mac-prog.tex (q-keyval): add getoptk + +2011-07-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-how-do-i.tex (q-destable): clarify caption package details for + captions above tables + +2011-07-06 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-jot-err.tex (q-altabcr): mention limit to sizes of matrices + +2011-07-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-backgrnd.tex (q-whyfree): twiddle discussion of gpl + (q-texfuture): reword statement of luatex's release goal + + * faq-docs.tex (q-latex-books): math into latex -> more <ditto> + +2011-07-05 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-bits+pieces.tex (q-write): editorial + (q-spawnprog): correct typo (epstopf), add cat link for epstopdf at end + + * filectan.tex: add cat link to vf-howto + +2011-07-03 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-backgrnd.tex (q-mf): caveat about the "modern" sidelining of mf + +2011-07-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-bits+pieces.tex (q-ctan): minor editorial + (q-dvi): tidy contorted xref + (q-ok): preparatory work (may not come to anything) + + * faq-docs.tex (q-symbols): only pdf of symbol list, now + + * filectan.tex: add cat link for metafp + +2011-06-29 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-docs.tex (q-doc-dirs): correct tug india link + +2011-06-29 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-mac-prog.tex (q-patch): recommend letltxcmd for macros with + opt arguments + +2011-06-21 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-long-outer): mention getting round \outer w/csname + (q-outer-err): new answer pointing to q-long-outer + +2011-06-16 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-includeother): new jot-err answer + +2011-06-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-backgrnd.tex (q-context): explain difference between mkii and + mkiv (from hans' article in tb100) + +2011-06-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-projects.tex (q-latex3): replace expl3, xpackages with l3kernel, + l3packages + + * faq-mac-prog.tex (q-keyval): replace expl3, xpackages with l3kernel, + l3packages + + * dirctan.tex: remove expl3, xpackages; add l3kernel, l3packages + +2011-06-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-bits+pieces.tex (q-hyphen): mention luatex's more relaxed table + loading + +2011-06-03 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-graphics.tex (q-drawing): typos, plus hack on text about dratex + +2011-06-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-mac-prog.tex (q-fontsize): mention cmdunh, cmfib missing from + fix-cm + +2011-06-02 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: add pst-layout + + * faq-graphics.tex (q-drawing): link to cremeronline intro tutorial + (q-labelfig): mention pst-layout, and make reference to similar + power of pgf, capable of anything pstricks can do for this problem + + * dirctan.tex: add multido (again...note, different machine) + +2011-06-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * add-general.tex (q-repetition): add multido + + * dirctan.tex: add multido + +2011-06-01 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-how-do-i.tex,faq-fonts.tex.tex,faq-graphics.tex,faq-jot-err.tex, + faq-jot-err.tex,faq-wdidt.tex,faq-backgrnd.tex,faq-adj-types.tex, + faq-bits+pieces.tex,faq-docs (throughout): replace q-books refs as + appropriate + + * faq-docs.tex (q-book-lists,q-tex-books,q-latex-books,q-other-books): + formed by dismembering the old q-books + +2011-05-31 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-how-do-i.tex (q-subdepth): new, slightly edited from add-general + + * faq-images.tex: new, for snippets to be served as images + + * sanitize-beta.pl (sanitize_line): add exptl \includegraphics + +2011-05-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-projects.tex (q-luatex): minor editorial to match q-texthings + + * faq-backgrnd.tex (q-texthings): tidy and tweak xetex, rewrite luatex + a bit + +2011-05-27 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-docs.tex (q-gethelp): identify stack exchange before referring to + it; don't link to latex project team when saying that the user + shouldn't contact them + +2011-05-24 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: add unicode + + * add-general.tex (q-inputenc,q-fontenc): new, from q-whatenc + (q-unicode) skeleton only, so far + + * faq-bits+pieces.tex (q-hyphen): editorial + (q-whatenc): minor editorial, preparing for split + + * dirctan.tex: add cat link for lacheck + + * faq-mac-prog.tex (q-latexqual): mention lacheck + +2011-05-22 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * add-general.tex (q-sansmath): add hfbright to list of things + + * dirctan.tex: add cmbright + +2011-05-20 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-sansmath): currently just a placeholder + +2011-05-19 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-subheight): typo + + * faq-bits+pieces.tex (q-ctan,q-catalogue): new, from add-general + + * faq-docs.tex (q-gethelp): complete replacement from add-general + q-gethelp* + +2011-05-10 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-projects.tex (q-luatex): clarification on "no changes to pdftex" + statement + +2011-05-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * add-general.tex (q-gethelp*): (new) rewriting q-gethelp for the "new + philosophy" + (q-catalogue): further knocking into shape + +2011-05-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * sanitize-beta.pl: html list-alike environments issue <p/> their end, + to cause paragraph style to be invoked + + * faq.sty: require pdf14.sty since thumbpdf has problems otherwise + 2011-05-04 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + * faq-fmt-conv.tex (q-latextoplain): undo mess in ctanrefs on web + + *** Release 3.22 *** + * faq-support.tex (q-xfigetc): add \LastEdit * faq-how-do-i.tex (q-struttab): add \LastEdit diff --git a/Master/texmf-dist/doc/generic/FAQ-en/FAQ-html.tar.gz b/Master/texmf-dist/doc/generic/FAQ-en/FAQ-html.tar.gz Binary files differindex 9d0d99292cd..d54bcd15760 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/FAQ-html.tar.gz +++ b/Master/texmf-dist/doc/generic/FAQ-en/FAQ-html.tar.gz diff --git a/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex b/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex index e6ae193cf35..6d1159275e1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex @@ -1,4 +1,4 @@ -% $Id: dirctan.tex,v 1.269 2011/05/04 06:40:43 rf10 Exp rf10 $ +% $Id: dirctan.tex,v 1.275 2011/09/03 18:56:20 rf10 Exp rf10 $ % % protect ourself against being read twice \csname readCTANdirs\endcsname @@ -193,6 +193,7 @@ \CTANdirectory{cmactex}{systems/mac/cmactex}[cmactex] \CTANdirectory{cmap}{macros/latex/contrib/cmap} \CTANdirectory{cmastro}{fonts/cmastro} +\CTANdirectory{cmbright}{fonts/cmbright}[cmbright] \CTANdirectory{cmcyralt}{macros/latex/contrib/cmcyralt} %[fonts/cmcyralt] \CTANdirectory{cmfrak}{fonts/gothic/cmfrak} @@ -359,7 +360,6 @@ \CTANdirectory{excerpt}{web/spiderweb/tools/excerpt} \CTANdirectory{excludeonly}{macros/latex/contrib/excludeonly}[excludeonly] \CTANdirectory{expdlist}{macros/latex/contrib/expdlist} -\CTANdirectory{expl3}{macros/latex/contrib/expl3}[expl3] \CTANdirectory{extract}{macros/latex/contrib/extract}[extract] \CTANdirectory{extsizes}{macros/latex/contrib/extsizes}[extsizes] % cat links to here @@ -412,8 +412,10 @@ \CTANdirectory{genfam}{support/genfam} \CTANdirectory{geometry}{macros/latex/contrib/geometry}[geometry] \CTANdirectory{germbib}{biblio/bibtex/contrib/germbib} +\CTANdirectory{getoptk}{macros/plain/contrib/getoptk}[getoptk] \CTANdirectory{gfs}{info/examples/FirstSteps} % gratzer's \CTANdirectory*{ghostscript}{support/ghostscript/GPL}[ghostscript-GPL] +\CTANdirectory{gitinfo}{macros/latex/contrib/gitinfo}[gitinfo] \CTANdirectory{glo+idxtex}{indexing/glo+idxtex}[idxtex] \CTANdirectory{gmp}{macros/latex/contrib/gmp}[gmp] \CTANdirectory{gnuplot}{graphics/gnuplot} @@ -514,7 +516,7 @@ \CTANdirectory{labelcas}{macros/latex/contrib/labelcas}[labelcas] \CTANdirectory{labels}{macros/latex/contrib/labels} \CTANdirectory{labtex}{macros/generic/labtex} -\CTANdirectory{lacheck}{support/lacheck} +\CTANdirectory{lacheck}{support/lacheck}[lacheck] \CTANdirectory{lametex}{support/lametex} \CTANdirectory{lamstex}{macros/lamstex} \CTANdirectory{lastpage}{macros/latex/contrib/lastpage}[lastpage] @@ -633,6 +635,7 @@ \CTANdirectory{multenum}{macros/latex/contrib/multenum}[multenum] \CTANdirectory{multibbl}{macros/latex/contrib/multibbl}[multibbl] \CTANdirectory{multibib}{macros/latex/contrib/multibib}[multibib] +\CTANdirectory{multido}{macros/generic/multido}[multido] \CTANdirectory{multirow}{macros/latex/contrib/multirow}[multirow] \CTANdirectory{musictex}{macros/musictex}[musictex] \CTANdirectory{musixtex-egler}{obsolete/macros/musixtex/egler} @@ -716,6 +719,9 @@ \CTANdirectory{plttopic}{support/plttopic} \CTANdirectory{pmtex}{systems/os2/pmtex} \CTANdirectory{pmx}{support/pmx} +\CTANdirectory{l3experimental}{macros/latex/contrib/l3experimental}[l3experimental] +\CTANdirectory{l3kernel}{macros/latex/contrib/l3kernel}[l3kernel] +\CTANdirectory{l3packages}{macros/latex/contrib/l3packages}[l3packages] \CTANdirectory{polish}{language/polish} \CTANdirectory{polyglossia}{macros/xetex/latex/polyglossia}[polyglossia] \CTANdirectory{poorman}{fonts/poorman} @@ -751,6 +757,7 @@ \CTANdirectory{psnfssx-mathtime}{macros/latex/contrib/psnfssx/mathtime} \CTANdirectory{pspicture}{macros/latex/contrib/pspicture}[pspicture] \CTANdirectory{psprint}{dviware/psprint} +\CTANdirectory{pst-layout}{graphics/pstricks/contrib/pst-layout}[pst-layout] \CTANdirectory{pst-pdf}{macros/latex/contrib/pst-pdf}[pst-pdf] \CTANdirectory{pstoedit}{support/pstoedit}[pstoedit] \CTANdirectory{pstricks}{graphics/pstricks}[pstricks] @@ -875,6 +882,7 @@ \CTANdirectory{ulem}{macros/latex/contrib/ulem}[ulem] \CTANdirectory{umrand}{macros/generic/umrand} \CTANdirectory{underscore}{macros/latex/contrib/underscore}[underscore] +\CTANdirectory{unicode}{macros/latex/contrib/unicode}[unicode] \CTANdirectory{unicode-math}{macros/latex/contrib/unicode-math}[unicode-math] \CTANdirectory{unix}{systems/unix} \CTANdirectory{unpacked}{macros/latex/unpacked} @@ -915,7 +923,6 @@ \CTANdirectory{xits}{fonts/xits}[xits] \CTANdirectory{xkeyval}{macros/latex/contrib/xkeyval}[xkeyval] \CTANdirectory{xmltex}{macros/xmltex/base}[xmltex] -\CTANdirectory{xpackages}{macros/latex/contrib/xpackages}[xpackages] \CTANdirectory*{xpdf}{support/xpdf}[xpdf] \CTANdirectory{xtab}{macros/latex/contrib/xtab}[xtab] \CTANdirectory{yagusylo}{macros/latex/contrib/yagusylo}[yagusylo] diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex index 9ca0d1863e2..473d6d4b4dc 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex @@ -1,4 +1,4 @@ -% $Id: faq-adj-types.tex,v 1.31 2011/04/13 09:45:46 rf10 Exp $ +% $Id: faq-adj-types.tex,v 1.33 2011/06/01 19:57:21 rf10 Exp rf10 $ \section{Adjusting the typesetting} @@ -588,11 +588,11 @@ headings must be centred, in small capitals, and subsection headings ragged right in italic, but that you don't want to get involved in the sort of programming described in section 2.2 of \emph{The \LaTeX{} Companion} \begin{narrowversion} % really non-hyper - (\Qref{}{Q-books}; the programming itself is discussed in + (\Qref{}{Q-latex-books}; the programming itself is discussed in \Qref[question]{}{Q-atsigns}). \end{narrowversion} \begin{wideversion} % really hyper - (see \Qref{\TeX{}-related books}{Q-books}; the + (see \Qref{\latex{} books}{Q-latex-books}; the \Qref{programming}{Q-atsigns} itself is discussed elsewhere in this \acro{FAQ}). \end{wideversion} @@ -664,6 +664,7 @@ them to their own \LaTeX{} use. \item[titlesec.sty]\CTANref{titlesec} \item[tocbibind.sty]\CTANref{tocbibind} \end{ctanrefs} +\LastEdit{2011-06-01} \Question[Q-appendix]{Appendixes} @@ -825,12 +826,13 @@ defined in terms of the internal \csx{@startsection} command, which takes 6~arguments. Before attempting this sort of work, you are well advised to read the \LaTeX{} sources (\File{ltsect.dtx} in the \LaTeX{} distribution) and the source of the standard packages -(\File{classes.dtx}). The \Qref*{\LaTeX{} Companion}{Q-books} +(\File{classes.dtx}). The \Qref*{\LaTeX{} Companion}{Q-latex-books} discusses use of \csx{@startsection} for this sort of thing. \begin{ctanrefs} \item[\nothtml{\rmfamily}\LaTeX{} source]\CTANref{latex} \item[titlesec.sty]\CTANref{titlesec} \end{ctanrefs} +\LastEdit{2011-06-01} \Question[Q-captsty]{The style of captions} @@ -1523,7 +1525,7 @@ So you're eager to do it yourself, notwithstanding the cautions It's important that you first start by familiarising yourself with LaTeX's page layout parameters. For example, see section C.5.3 of the \LaTeX{} manual (pp.~181-182), or corresponding sections in many of the other -good \LaTeX{} manuals (see \Qref[question]{\LaTeX{} books}{Q-books}). +good \LaTeX{} manuals (see \Qref[question]{\LaTeX{} books}{Q-latex-books}). \LaTeX{} controls the page layout with a number of parameters, which allow you to change the distance from the edges of a page to the left @@ -1638,6 +1640,7 @@ work. \item[addlines.sty]\CTANref{addlines} \item[changepage.sty]\CTANref{changepage} \end{ctanrefs} +\LastEdit{2011-06-01} \Question[Q-nopageno]{How to get rid of page numbers} \AliasQuestion{ps@empty} @@ -1677,6 +1680,8 @@ problem with the following ``grubby little patch'', on \makeatother \end{verbatim} \end{quote} +Fortunately, that patch has now been incorporated in a small package +\Package{nonumonpart} (a difficult name\dots) Both the \Class{KOMA-script} classes and \Class{memoir} have separate page styles for the styles of various ``special'' pages, so, in a @@ -1716,9 +1721,11 @@ you are using \cmdinvoke{pagestyle}{plain} \item[fancyhdr.sty]\CTANref{fancyhdr} \item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script} \item[memoir.cls]\CTANref{memoir} +\item[nonumonpart.sty]\CTANref{nonumonpart} \item[nopageno.sty]\CTANref{nopageno} \item[scrpage2.sty]Distributed as part of \CTANref{koma-script} \end{ctanrefs} +\LastEdit{2011-04-16} \Question[Q-crop]{How to create crop marks} @@ -3176,7 +3183,7 @@ best done by redefining the page style itself, perhaps using The formats of entries in the table of contents (\acro{TOC}) are controlled by a number of internal commands (discussed in section~2.3 -of \Qref*{\emph{The \LaTeX{} Companion}}{Q-books}. The commands +of \Qref*{\emph{The \LaTeX{} Companion}}{Q-latex-books}. The commands \csx{@pnumwidth}, \csx{@tocrmarg} and \csx{@dotsep} control the space for page numbers, the indentation of the right-hand margin, and the separation of the dots in the dotted leaders, respectively. The @@ -3202,6 +3209,7 @@ of \Package{tocloft}. \item[memoir.cls]\CTANref{memoir} \item[tocloft.sty]\CTANref{tocloft} \end{ctanrefs} +\LastEdit{2011-06-01} \Question[Q-secnumdep]{Unnumbered sections in the Table of Contents} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex index f893036d0bf..2b1853c9fa8 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex @@ -1,4 +1,4 @@ -% $Id: faq-backgrnd.tex,v 1.19 2011/04/14 18:34:15 rf10 Exp rf10 $ +% $Id: faq-backgrnd.tex,v 1.27 2011/09/03 18:56:20 rf10 Exp $ \section{The Background} @@ -45,7 +45,7 @@ for \latex{}, see % ! line break \TeX{} is a typesetting system written by \href{http://sunburn.stanford.edu/~knuth/}{Donald E. Knuth}, who says in the Preface to his book on \TeX{} -(see \Qref[question]{books about TeX}{Q-books}) that it is +(see \Qref[question]{books about TeX}{Q-tex-books}) that it is %% !line wrap avoided by two commands ``\emph{intended for the creation of beautiful books~---} \emph{and especially for books that contain a lot of mathematics}''. @@ -89,6 +89,7 @@ program may be found in the % ! line break \item[\nothtml{\rmfamily}Knuth's source distribution]\CTANref{knuth-dist} \item[\nothtml{\rmfamily}Knuth's sources in \acro{TDS} layout]\CTANref{knuth-tds} \end{ctanrefs} +\LastEdit{2011-06-01} \Question[Q-plaintex]{What's ``writing in \TeX{}''?} @@ -143,21 +144,26 @@ between two fonts that belong to the same (or related) families. Knuth (and others) have designed a fair range of fonts using \MF{}, but font design using \MF{} is much more of a minority skill (even) than is -\TeX{} macro-writing. The complete \TeX{}-user nevertheless needs to -be aware of \MF{}, and may even be required run \MF{} to generate personal -copies of Meta-fonts that come her way. -\LastEdit{2011-03-10} +\TeX{} macro-writing. +What is more, it is a dying art: few new \tex{}-related fonts are +produced using \MF{}, nowadays. Indeed, several of the major font +families (that originated in \MF{} designs) are now seldom used in any +other way than their conversion to an outline font format. +%% The complete \TeX{}-user nevertheless needs to +%% be aware of \MF{}, and may even be required run \MF{} to generate personal +%% copies of Meta-fonts that come her way. +\LastEdit{2011-07-03} \Question[Q-MP]{What is \MP{}?} The \MP{} system (by John Hobby) implements a picture-drawing language -very much like that of \MF{} except that it outputs Encapsulated \PS{} -files instead of run-length-encoded bitmaps. \MP{} is a powerful -language for producing figures for documents to be printed on \PS{} -printers, either directly or embedded in \AllTeX{} documents. It -includes facilities for directly integrating \TeX{} text and -mathematics with the graphics. (Knuth tells us that he uses nothing -but \MP{} for diagrams in text that he is writing.) +very much like that of \MF{}; the difference is that \MP{} outputs +Encapsulated \PS{} files instead of run-length-encoded bitmaps. \MP{} +is a powerful language for producing figures for documents to be +printed on \PS{} printers, either directly or embedded in \AllTeX{} +documents. \MP{} is able to integrate text and mathematics, marked up +for use with \TeX{}, within the graphics. (Knuth tells us that he +uses nothing but \MP{} for diagrams in text that he is writing.) Although \PDFLaTeX{} cannot ordinarily handle \PS{} graphics, the output of \MP{} is sufficiently simple and regular that \PDFLaTeX{} @@ -184,6 +190,7 @@ A mailing list discussing \MP{} is available; \end{hyperversion} The \acro{TUG} website also hosts a % ! line break \href{http://tug.org/metapost.html}{\MP{} summary page}. +\LastEdit{2011-09-01} %**** \Question[Q-texthings]{Things with ``\TeX{}'' in the name} @@ -231,7 +238,7 @@ that you are likely to encounter: \begin{description} \item[Plain \TeX{} (executable: \ProgName{tex})] See - \Qref[questions]{Books on \TeX{} and its relations}{Q-books}, + \Qref[questions]{Books on \TeX{} and \plaintex{}}{Q-tex-books}, \Qref[]{Online introductions: \TeX{}}{Q-man-tex}, \Qref[]{Should I use Plain \TeX{} or \LaTeX{}?}{Q-plainvltx} and \Qref[]{Freely available \AllTeX{} books}{Q-ol-books}. @@ -242,7 +249,7 @@ that you are likely to encounter: \item[\LaTeX{} (executable: \ProgName{latex})] See - \Qref[questions]{Books on \TeX{} and its relations}{Q-books}, + \Qref[questions]{Books on \TeX{} and its relations}{Q-latex-books}, \Qref[]{\AllTeX{} Tutorials, etc.}{Q-tutorials*}, \Qref[]{Online introductions: \LaTeX{}}{Q-man-latex}, \Qref[]{Specialized \AllTeX{} tutorials}{Q-tutbitslatex} and @@ -292,12 +299,7 @@ the \TeX{} engine with some additional useful features: \Qref[question]{What is \PDFTeX{}?}{Q-whatpdftex}. \item[\xetex{} (executable: \ProgName{xetex})] -% \TeX{} not only predates all major font technologies in use today -% (e.g.,~TrueType, OpenType, and PostScript Type~1) but also predates -% the notion that fonts be included with an operating system. -% Consequently, \TeX{} uses its own font formats, which are -% incompatible with anything a user is likely to have preinstalled. - \xetex{} uses \acro{UTF}-8 encoded Unicode input, and extends + \xetex{} reads \acro{UTF}-8 encoded Unicode input, and extends \TeX{}'s font support to include `modern' formats such as TrueType and OpenType; these extensions to its capabilities make it well-suited to multi-lingual texts covering different writing @@ -306,8 +308,10 @@ the \TeX{} engine with some additional useful features: \item[\LuaTeX{} (executable: \ProgName{luatex})] \TeX{} is programmed in its own arcane, integrated, macro-based programming language. \LuaTeX{} adds a second programming engine - which operates alongside \tex{} using a modern scripting language, - Lua. See \Qref[question]{What is \LuaTeX{}?}{Q-luatex}. + using a modern scripting language, Lua, which is `embedded' in a + \tex{}-alike engine; it too reads \acro{UTF}-8 and uses TrueType + OpenType fonts. See % ! line break + \Qref[question]{What is \LuaTeX{}?}{Q-luatex}. \item[\eTeX{} (executable: \ProgName{etex})] \eTeX{} is an extension of \tex{}'s programming interface; as such @@ -374,17 +378,17 @@ name like ``blah\tex{}''. The subject matter covered by this answer is also addressed in a page on the \acro{TUG} site, % ! line break ``\href{http://tug.org/levels.html}{the Levels of \tex{}}''. -\LastEdit{2011-03-11} +\LastEdit{2011-06-01} \Question[Q-triptrap]{How can I be sure it's really \TeX{}?} \TeX{} (and \MF{} and \MP{}) are written in a -\begin{narrowversion} % really "non-hyper" - `literate' programming language called Web (\Qref{}{Q-lit}) -\end{narrowversion} -\begin{wideversion} - \Qref{`literate' programming}{Q-lit} language called Web -\end{wideversion} +\begin{flatversion} % really "non-hyper" + `literate' programming language called \ProgName{Web} (\Qref{}{Q-lit}) +\end{flatversion} +\begin{hyperversion} + \Qref{`literate' programming}{Q-lit} language called \ProgName{Web} +\end{hyperversion} which is designed to be portable across a wide range of computer systems. How, then, is a new version of \TeX{} checked? @@ -408,7 +412,7 @@ any distributor would test new versions against ``real'' documents or fonts, too; while \Package{trip} and \Package{trap} test bits of pathways within the program, they don't actually test for any real world problem.) - +\LastEdit{2011-05-28} \Question[Q-y2k]{Are \TeX{} and friends Y2K compliant?} @@ -422,7 +426,7 @@ world problem.) since the only use of the date format file is to produce the log output, and the log file is designed for human readers only. - Knuth announced in 1998 that implementors could + Knuth announced in 1998 that implementors would be permitted alter this code without fear of being accused of non-compliance. Nearly all implementations that are being actively maintained had been modified to generate 4-digit years in the format file and the @@ -435,7 +439,7 @@ world problem.) means that \TeX{} can, in principle, be implemented on platforms that don't make the value of the clock available to user programs). The \emph{\TeX{}book} (see - \Qref[question]{TeX-related books}{Q-books}) defines \csx{year} as + \Qref[question]{TeX-related books}{Q-tex-books}) defines \csx{year} as ``the current year of our Lord'', which is the only correct meaning for \csx{year} for those implementations which can supply a meaningful value, which is to say nearly all of them. @@ -461,6 +465,7 @@ world problem.) \item[External software:] Software such as \acro{DVI} translators needs to be individually checked. \end{description} +\LastEdit{2011-06-01} \Question[Q-etex]{What is \eTeX{}?} @@ -491,7 +496,7 @@ programming support. \Qref*{\CONTeXT{}}{Q-context} has required \eTeX{} for its operation for some time, though development is now focused on the use of -\Qref*{\luatex}{Q-luatex}. +\Qref*{\luatex{}}{Q-luatex}. Some \LaTeX{} packages already specify the use of \eTeX{}. Some such packages may not work at all on a non-\eTeX{} system; others will @@ -502,7 +507,7 @@ individually contributed) may require \eTeX{} for optimum performance. \begin{ctanrefs} \item[\eTeX{}]\CTANref{etex} \end{ctanrefs} -\LastEdit{2011-04-13} +\LastEdit{2011-07-13} \Question[Q-whatpdftex]{What is \PDFTeX{}?} @@ -510,25 +515,25 @@ One can reasonably say that \PDFTeX{} is (today) the main stream of \TeX{} distributions: most \LaTeX{} and many \CONTeXT{} users nowadays use \PDFTeX{} whether they know it or not (more precisely, they use \PDFTeX{} extended by -\begin{wideversion} +\begin{hyperversion} \Qref*{\eTeX{}}{Q-etex}). -\end{wideversion} -\begin{narrowversion} +\end{hyperversion} +\begin{flatversion} \eTeX{}~--- \Qref{}{Q-etex}). -\end{narrowversion} +\end{flatversion} So what is \PDFTeX{}? \PDFTeX{} is a development of \TeX{} that is capable of generating typeset \acro{PDF} output in place of \acro{DVI}. \PDFTeX{} has other capabilities, most notably in the area of fine typographic detail (for example, its support for % ! line break -\begin{wideversion} +\begin{hyperversion} \Qref{optimising line breaks}{Q-overfull}), -\end{wideversion} -\begin{narrowversion} +\end{hyperversion} +\begin{flatversion} % ( <- dummy for paren balancing optimising line breaks~--- \Qref{}{Q-overfull}), -\end{narrowversion} +\end{flatversion} but its greatest impact to date has been in the area of \acro{PDF} output. @@ -539,14 +544,16 @@ Russia). While the world was making good use of ``pre-releases'' of \PDFTeX{}, Th\`anh used it as a test-bed for the micro-typography which was the -prime subject of his Ph.D. research. Since Th\`anh was finally +prime subject of his Ph.D.~research. Since Th\`anh was finally awarded his Ph.D., day-to-day maintenance and development of \PDFTeX{}~1.0 (and later) has been in the hands of a group of \PDFTeX{} maintainers (which includes Th\`anh); the group has managed to maintain a stable platform for general use. -Development of \PDFTeX{} has (in essence) stopped: the brave new world -is to be \Qref*{\LuaTeX{}}{Q-luatex}. +Development of \PDFTeX{} has mostly stopped (only bug fixes, and +occasional small development items are processed): future development +is focused on \Qref*{\LuaTeX{}}{Q-luatex}. +\LastEdit{2011-05-28} \Question[Q-latex]{What is \LaTeX{}?} @@ -577,7 +584,7 @@ from the later days of \LaTeXo{}. The ``e'' of the name is (in the % the \relax allows sanitize to cope with the line. just don't ask... a single-stroke epsilon (\latexhtml{\ensuremath{\varepsilon}}{ε}, supposedly -indicative of no more than a small change. +indicative of no more than a small change). \LaTeXe{} has several enhancements over \LaTeXo{}, but they were all rather minor, with a view to continuity and stability rather than the @@ -589,10 +596,15 @@ file). Differences between \LaTeXe{} and \LaTeXo{} are outlined in a series of `guide' files that are available in every \LaTeX{} distribution (the same directory also contains ``news'' about each new release of \LaTeXe{}). + +Note that, now, \latexe{} is ``feature frozen'' (the only allowed +changes come from bug reports); this, too, is in pursuit of stability, +and is a driving force for many of the efforts to contribute \latex{} +packages. \begin{ctanrefs} \item[\nothtml{\rmfamily}\LaTeX{} guides and news]\CTANref{latexdoc} \end{ctanrefs} -\LastEdit{2009-06-07} +\LastEdit{2011-08-19} \Question[Q-latexpronounce]{How should I pronounce ``\LaTeX{}(\twee{})''?} @@ -657,7 +669,8 @@ answer about \Qref*{translating to \plaintex{}}{Q-LaTeXtoPlain}. \Question[Q-context]{What is \CONTeXT{}?} \href{http://www.pragma-ade.com/}{\CONTeXT{}} is a macro package -developed by Hans Hagen of Pragma-Ade. \CONTeXT{} is a +developed by Hans Hagen of Pragma-Ade; it started as a production tool +for Pragma (which is a publishing company). \CONTeXT{} is a document-production system based, like \LaTeX{}, on the \TeX{} typesetting system. Whereas \LaTeX{} insulates the writer from typographical details, \CONTeXT{} takes a complementary approach by @@ -680,21 +693,29 @@ engines (\PDFTeX{}, Xe\TeX{}, Aleph and \LuaTeX{}) without changing the user interface. \CONTeXT{} continues to develop, often in response to requests from the user community. -\CONTeXT{} doesn't yet have quite such a large developer community as -does \LaTeX{}, but those developers who are active seem to have +\CONTeXT{} has been bound to the development of +\Qref*{\luatex{}}{Q-luatex}, almost from the start of that project. +Nowadays, it is distributed in two versions~--- mark two (files with +extension \extension{mkii} (which runs on \pdftex{} but is not under +active development) and mark four files with extension +\extension{mkiv} (which runs on \luatex{} and is where development +happens). + +\CONTeXT{} has a large developer community (though possibly not as +large as that of latex{}), but those developers who are active seem to have prodigious energy. Support is available via a % ! line break \href{http://contextgarden.net}{\acro{WIKI} site} and via the \href{http://www.ntg.nl/mailman/listinfo/ntg-context}{mailing list}. \begin{ctanrefs} \item[\nothtml{\rmfamily}\CONTeXT{} distribution]\CTANref{context} \end{ctanrefs} -\LastEdit{2010-12-08} +\LastEdit{2011-06-12} \Question[Q-AMSpkg]{What are the \acro{AMS} packages (\AMSTeX{}, \emph{etc}.)?} \AMSTeX{} is a \TeX{} macro package, originally written by Michael Spivak for the American Mathematical Society (\acro{AMS}) during 1983--1985 and -is described in the book ``\Qref*{The Joy of \TeX{}}{Q-books}''. +is described in the book ``\Qref*{The Joy of \TeX{}}{Q-tex-books}''. It is based on \plaintex{}, and provides many features for producing more professional-looking maths formulas with less burden on authors. It pays attention to the finer details of @@ -714,6 +735,7 @@ its authors to use \AMSLaTeX{} instead. \item[\nothtml{\rmfamily}\AMSTeX{} distribution]\CTANref{amstex} \item[\nothtml{\rmfamily}\AMSLaTeX{} distribution]\CTANref{amslatex} \end{ctanrefs} +\LastEdit{2011-06-01} \Question[Q-eplain]{What is \Eplain{}?} @@ -738,7 +760,7 @@ On the other hand, almost everyone would like capabilities such as cross-referencing by labels, so that you don't have to put actual page numbers in the manuscript. The authors of \Eplain{} believe it is the only generally available macro package that does not force its -typographic style on an author, and yet provides these such capabilities. +typographic style on an author, and yet provides these capabilities. Another useful feature of \Eplain{} is the ability to create PDF files with hyperlinks. The cross-referencing macros can implicitly generate @@ -761,14 +783,14 @@ known to work with \Eplain{}: \Package{graphics}, \Package{graphicx}, \Package{psfrag}, and \Package{url}. \href{http://tug.org/docs/html/eplain}{\Eplain{} documentation} is -available online (and there's a \acro{PDF} copy in the \acro{CTAN} +available online (there's a \acro{PDF} copy in the \acro{CTAN} package as well), and there's also a mailing list~--- sign up, or browse the list archives, via \URL{http://tug.org/mailman/listinfo/tex-eplain} \begin{ctanrefs} \item[\nothtml{\rmfamily}\Eplain{} distribution]\CTANref{eplain} \end{ctanrefs} -\LastEdit{2011-04-13} +\LastEdit{2011-07-13} \Question[Q-texinfo]{What is Texinfo?} @@ -805,12 +827,13 @@ Finally, of course, you can also print the files, or convert them to \Question[Q-whyfree]{If \TeX{} is so good, how come it's free?} -It's free because Knuth chose to make it so. He is nevertheless -apparently happy -that others should earn money by selling \TeX{}-based services and -products. While several valuable \TeX{}-related tools and packages are -offered subject to restrictions imposed by the \acro{GNU} General Public -Licence (`Copyleft'), \TeX{} itself is not subject to Copyleft. +It's free because Knuth chose to make it so (he makes money from +royalties on his \TeX{} books, which all sell well. He is nevertheless +apparently happy that others should earn money by selling \TeX{}-based +services and products. While several valuable \TeX{}-related tools and +packages are offered subject to restrictions imposed by the \acro{GNU} +General Public Licence (\acro{GPL}, sometimes referred to as +`Copyleft'), \TeX{} itself is not subject to \acro{GPL}. There are commercial versions of \TeX{} available; for some users, it's reassuring to have paid support. What is more, some of the @@ -821,6 +844,7 @@ not available commercially.) This \acro{FAQ} concentrates on `free' distributions of \TeX{}, but we do at least list the \Qref*{major vendors}{Q-commercial}. +\LastEdit{2011-07-06} \Question[Q-TeXfuture]{What is the future of \TeX{}?} @@ -855,9 +879,10 @@ all the results they are likely to deliver, is the related % ! line break \Qref*{Omega and Aleph}{Q-omegaleph}. The % ! line break \Qref*{\xetex{} system}{Q-xetex} is in principle still under development, but is widely used, and the % ! line break -\Qref*{\LuaTeX{} project}{Q-luatex} (though with another two years of -development scheduled) has already delivered a system that is quite -useful. +\Qref*{\LuaTeX{} project}{Q-luatex} (though not scheduled to produce +its final product until end 2012) has already delivered a system that +is quite useful. +\LastEdit{2011-07-06} \Question[Q-readtex]{Reading \AllTeX{} files} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-bits+pieces.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-bits+pieces.tex index 78ff04ea751..b8fade922fa 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-bits+pieces.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-bits+pieces.tex @@ -1,13 +1,109 @@ -% $Id: faq-bits+pieces.tex,v 1.9 2011/02/22 19:13:11 rf10 Exp $ +% $Id: faq-bits+pieces.tex,v 1.18 2011/08/28 10:13:19 rf10 Exp rf10 $ \section{Bits and pieces of \AllTeX{}} +\Question[Q-ctan]{What is \acro{CTAN}?} + +The acronym stands for ``Comprehensive \tex{} Archive Network'', which +more-or-less specifies what it's \emph{for}: +\begin{itemize} +\item The aim is to offer a comprehensive collection of \tex{} resources. +\item The content is to be made publicly accessible, via the internet. +\item \acro{CTAN} is a \emph{network} of archives, which strive to + stay in step with one another. +\end{itemize} +The basic framework was developed by a \acro{TUG} working group set up +to resolve the (then existing) requirement for users to \emph{know} on +which archive site a particular package might be found. + +Actual implementation offers three distinct types of host: +\begin{description} +\item[\emph{Core} archives]Which form a small, tightly-coupled set of + machines, which perform management functions as well as serving + files, and +\item[\emph{Mirror} archives]Which do no more than take regular copies + of core archives. +\item[Archive selector]Which is a meta-service, which routes requests + to an apparently ``local'' source (mirror or archive). +\end{description} +Note that there is nothing to prevent any archive from supporting +other functions, so a \acro{CTAN} mirror may also operate as a +\acro{CPAN} (Perl) mirror and as a SourceForge (general free software) +mirror, and \dots{} + +Functions that distinguish core archives are: +\begin{itemize} +\item Uploads: users may submit new (or updated) material, and + significant changes to the archive are reported via the mailing list + \Email{ctan-ann@dante.de} +\item Weak consistency: changes to the content of the archives are + rapidly distributed to all core archives. +\item Providing distribution (\texlive{} and \miktex{}) support. +\item Catalogue maintenance. +\item Mirror monitoring. +\end{itemize} +Not all core archives offer all of these functions. + +Users may contact the maintainers of the core archives via the mailing +list \mailto{ctan@dante.de} + +Users who have new material for the archive may submit it using the +\href{http://dante.ctan.org/upload/}{German} or +\href{http://www.tex.ac.uk/upload/}{UK} archive. + +Users should ordinarily download material from \acro{CTAN} via the +\href*{http://mirror.ctan.org/}{archive selector}: this uses the +mirror monitor's database, and uses the caller's geographical location to +offer an efficient choice of ``sufficiently up-to-date'' mirror site for +you to connect to. Note that all the download links, given in the web +representation of these \acro{FAQ}s, are set up to use the mirror +selector. +\LastEdit*{2011-04-21} + +\Question[Q-catalogue]{The (\acro{CTAN}) catalogue} + +Finding stuff on networks was always difficult, but in recent years, +search engines have become amazingly good at digging out unconsidered +trifles from the myriad items of information available on the net. + +Sadly, in the \tex{} context, search engines seem to excel in locating +out-of-date material, while the service users need a means of finding +relevant material on \acro{CTAN}~--- on the grounds that such material +is most likely to be up-to-date. The need to find such items, thus +alleviating tendency to end up with out-of-date \alltex{} material, +was the motivation for developing a specialised information source: +the \acro{CTAN} catalogue. The aim is that they contain enough +relevant information that they will appear early in a search engine's +evaluation. + +The basis of the catalogue is a collection of small +articles; each shows basic information about a package on \acro{CTAN}, +and includes pointers to download address, documentation and related +packages. Every \acro{CTAN} mirror holds a copy of the catalogue, +presented as a series of web pages; indexes (both alphabetic and +category-based) are provided. + +The core \acro{CTAN} sites also offer a simple text search of the +catalogue. This is a tolerable means of finding a package you need, +but it is not really a substitute for a good information retrieval +system: the problem of providing such a system has not yet been solved. +\begin{ctanrefs} +\item[\nothtml{\rmfamily}The CTAN catalogue]\CTANref{Catalogue} +\end{ctanrefs} +\LastEdit*{2011-05-19} + \Question[Q-dvi]{What is a \acro{DVI} file?} A \acro{DVI} file (that is, a file with the type or extension \extension{dvi}) is \TeX{}'s main output file, when we use -``original'' \TeX{} (later \TeX{} systems, such as \PDFTeX{}~--- see -\Qref[question]{\PDFTeX{}}{Q-whatpdftex} may use other formats). +``original'' \TeX{} (later \TeX{} systems, such as +\begin{flatversion} + \PDFTeX{}~--- see \Qref[question]{\PDFTeX{}}{Q-whatpdftex}~--- +\end{flatversion} +\begin{hyperversion} + \Qref{\PDFTeX{}}{Q-whatpdftex} +\end{hyperversion} +may use other formats). `\acro{DVI}' is supposed to be an acronym for \acro{D}e\acro{V}ice-\acro{I}ndependent, meaning @@ -31,12 +127,18 @@ as its name implies, was to view the content of a \acro{DVI} file). \begin{ctanrefs} \item[dvitype]\CTANref{dvitype} \end{ctanrefs} +\LastEdit{2011-07-01} \Question[Q-driver]{What is a \acro{DVI} driver?} -A \acro{DVI} driver is a program that takes as input a \acro{DVI} file -(\Qref{\acro{DVI} files}{Q-dvi}) and -(usually) produces a file that can be sent to a typographic +A \acro{DVI} driver is a program that takes as input a +\begin{flatversion} + \acro{DVI} file (see \Qref[question]{}{Q-dvi}) +\end{flatversion} +\begin{hyperversion} + \Qref{\acro{DVI} file}{Q-dvi} +\end{hyperversion} +and (usually) produces a file that can be sent to a typographic output device (which we will call a printer, for short), or to another format. @@ -49,7 +151,7 @@ As well as the \acro{DVI} file, the driver also needs font information. Font information may be held as bitmaps or as outlines, or simply as a set of pointers into the fonts that the printer itself `has'. Each driver will expect the font information in -a particular form. For more information on the forms of fonts, +a particular form. For more information on the forms of font information, see \Qref[questions]{\acro{PK} files}{Q-pk}, % ! line break \Qref[]{\acro{TFM} files}{Q-tfm}, @@ -85,6 +187,12 @@ contrast, \acro{TFM} files are not, in principle, needed by the \acro{DVI} driver, which only needs to know about the glyphs that each character selects, so as to print or display them. +Note that TrueType and OpenType fonts contain the necessary metrics, +so that \Qref{\xetex{}}{Q-xetex} and \Qref{\luatex{}}{Q-luatex}, using +such fonts, have no need of \acro{TFM} files. A corollary of this is +that setting up fonts for use by these engines is far \emph{easier}. +\LastEdit{2011-07-10} + \Question[Q-virtualfonts]{Virtual fonts} Virtual fonts provide a means of collecting bits and pieces together @@ -198,23 +306,34 @@ bits of the macro expansion: \begin{verbatim} \def\foo#1{This is a #1 bar} ... -\foo{2/4} +\foo{2/4}. \end{verbatim} \end{quote} +which produces: +\begin{quote} + This is a 2/4 bar. +\end{quote} or, in \LaTeX{} speak: \begin{quote} \begin{verbatim} \newcommand{\foo}[1]{This is a #1 bar} ... -\foo{3/4} +\foo{3/4}. \end{verbatim} \end{quote} +which produces: +\begin{quote} + This is 3/4 bar. +\end{quote} +(\latex{} users waltz through life, perhaps?) + Macro writing can get very complicated, very quickly. If you are a beginner \AllTeX{} programmer, you are well advised to read something -along the lines of the \Qref*{\TeX{}book}{Q-books}; once you're under +along the lines of the \Qref*{\TeX{}book}{Q-tex-books}; once you're under way, \Qref*{\TeX{} by Topic}{Q-ol-books} is possibly a more satisfactory choice. Rather a lot of the answers in these \acro{FAQ}s tell you about various issues of how to write macros. +\LastEdit{2011-07-10} \Question[Q-specials]{\csx{special} commands} @@ -285,12 +404,12 @@ Which brings us to the reason for that \csx{terminal}. \TeX{} can ``\csx{write}'' up to 16 streams simultaneously, and that argument to \csx{write} says which is to be used. Macro packages provide the means of allocating streams for your use: \plaintex{} provides a macro -\csx{newwrite}\csx{streamname}, which sets \csx{streamname} as -the stream number. In fact, \csx{terminal} (or its equivalent) is the -first output stream ever set up (in most macro packages): it is never -attached to a file, and if \tex{} is asked to write to \emph{any} -stream that isn't attached to a file it will send the output to the -terminal (and the log). +\csx{newwrite} (used as ``\csx{newwrite}\csx{streamname}'', which sets +\csx{streamname} as the stream number). In fact, \csx{terminal} (or +its equivalent) is the first output stream ever set up (in most macro +packages): it is never attached to a file, and if \tex{} is asked to +write to \emph{any} stream that isn't attached to a file it will send +the output to the terminal (and the log). \Question[Q-spawnprog]{Spawning programs from \AllTeX{}: \csx{write18}} @@ -302,11 +421,11 @@ numbered 0--15. More recently, a special ``stream 18'' has been implemented: it is not writing to a file, but rather tells TeX to ask the operating system to do something. To run a command, we put it as the argument to \csx{write18}. So to run the \progname{epstopdf} -program on a file with name stored as \csx{epsfilename}, we would +utility on a file with name stored as \csx{epsfilename}, we would write: \begin{quote} \begin{verbatim} -\write18{epstopf \epsfilename} +\write18{epstopdf \epsfilename} \end{verbatim} \end{quote} When using something like the \Package{epstopdf} package, the `stream' @@ -362,7 +481,7 @@ This is pdfTeX, Version 3.1415926-1.40.11 when it starts. \begin{ctanrefs} \item[epstopdf.sty]Distributed with Heiko Oberdiek's packages - \CTANref{oberdiek} + \CTANref{oberdiek}[epstopdf-pkg] \end{ctanrefs} \Question[Q-hyphen]{How does hyphenation work in \TeX{}?} @@ -380,13 +499,13 @@ hyphenation rules from time to time. \TeX{} uses a pretty good system for hyphenation (originally designed by Frank Liang~--- you may view his % ! line break -\href{http://tug.org/docs/liang/}{Ph.D.\ thesis} online), and while +\href{http://tug.org/docs/liang/}{Ph.D.\ thesis} online) and while it's capable of missing ``sensible'' hyphenation points, it seldom selects grossly wrong ones. The algorithm matches candidates for hyphenation against a set of ``hyphenation patterns''. The candidates for hyphenation must be sequences of letters (or other single characters that \TeX{} may be -persuaded to think of as letters)~--- things such as \TeX{}'s +persuaded to think of as letters); things such as \TeX{}'s \csx{accent} primitive interrupt hyphenation. Sets of hyphenation patterns are usually derived from analysis of @@ -395,7 +514,9 @@ called \Package{patgen}, is not ordinarily a participatory sport). The patterns for the languages a \TeX{} system is going to deal with may only be loaded when the system is installed. To change the set of -languages, a \Qref*{partial reinstallation}{Q-newlang} is necessary. +hyphenation patterns recognised by a \tex{}-based or \xetex{} system, +a \Qref*{partial reinstallation}{Q-newlang} is necessary (note that +\Qref*{\luatex{}}{Q-luatex} relaxes this constraint). \TeX{} provides two ``user-level'' commands for control of hyphenation: \csx{language} (which selects a hyphenation style), and @@ -410,38 +531,61 @@ it is very thoroughly managed by the \Package{babel} package; use of \end{wideversion} % beware line wrap \Qref[question]{hyphenation failure}{Q-nohyph}. +\LastEdit{2011-06-06} \Question[Q-clsvpkg]{What are \LaTeX{} classes and packages?} -Current \LaTeX{} makes a distinction between the macros that define the -overall layout of a document, and the macros that tweak that layout -(to one extent or another) to provide what the author \emph{really} -wants. - -The distinction was not very clear in \LaTeXo{}, and after some -discussion (in the later stages of development of current \LaTeX{}) -the names ``class'' and ``package'' were applied to the two concepts. - -The idea is that a document's \emph{class} tells \LaTeX{} what sort of -document it's dealing with, while the \emph{packages} the document -loads ``refine'' that overall specification. - -On the disc, the files only appear different by virtue of their name -``extension''~--- class files are called \texttt{*.cls} while package -files are called \texttt{*.sty}. Thus we find that the \LaTeX{} +\latex{} aims to be a general-purpose document processor. Such an aim +could be achieved by a selection of instructions which would enable +users to use \tex{} primitives, but such a procedure is considered too +inflexible (and probably too daunting for ordinary users), and so the +designers of \latex{} created a model which offered an +\emph{abstraction} of the design of documents. Obviously, not all +documents can look the same (even with the defocussed eye of +abstraction), so the model uses \emph{classes} of document. Base +\latex{} offers five classes of document: \Class{book}, +\Class{report}, \Class{report}, \Class{article} and \Class{letter}. +For each class, \latex{} provides a \emph{class file}; the user +arranges to use it via a \csx{documentclass} command at the top of the +document. So a document starting +\begin{quote} + \cmdinvoke{documentclass}{article} +\end{quote} +may be called ``an \emph{article} document''. + +This is a good scheme, but it has a glaring flaw: the actual +typographical designs provided by the \latex{} class files aren't +widely liked. The way around this is to \emph{refine} the class. To +refine a class, a programmer may write a new class file that loads an +existing class, and then does its own thing with the document design. + +If the user finds such a refined class, all is well, but if not, the +common way is to load a \emph{package} (or several). + +\latex{} provides rather few package files, but there are lots of them +to be found on the archives by a wide variety of authors; several +packages are designed just to adjust the design of a document~--- +using such packages achieves what the programmer might have achieved +by refining the class. + +Other packages provide new facilities: for example, the +\Package{graphics} package (actually provided by the \latex{} team) +allows the user to load externally-provided graphics into a document, +and the \Package{hyperref} package enables the user to construct +hyper-references within a document. + +On disc, class and package files only appear different by virtue of +their name ``extension''~--- class files are called \File{*.cls} while +package files are called \File{*.sty}. Thus we find that the \LaTeX{} standard \Class{article} class is represented on disc by a file called -\File{article.cls}, while the \Package{footmisc} package (which -refines \Class{article}'s definition of footnotes) is represented on -disc by a file called \File{footmisc.sty}. - -The user defines the class of his document with the -\csx{documentclass} command (typically the first command in a -document), and loads packages with the \csx{usepackage} command. A -document may have several \csx{usepackage} commands, but it may have -only one \csx{documentclass} command. (Note that there are -programming-interface versions of both commands, since a class may -choose to load another class to refine its capabilities, and both -classes and packages may choose to load other packages.) +\File{article.cls}, while the \Package{hyperref} package is +represented on disc by a file called \File{hyperref.sty}. + +The class vs.~package distinction was not clear in \LaTeXo{}~--- +everything was called a style (``document style'' or ``document style +option''). It doesn't really matter that the nomenclature has +changed: the important requirement is to understand what other people +are talking about. \Question[Q-dtx]{Documented \LaTeX{} sources (\extension{dtx} files)} @@ -462,7 +606,7 @@ out by the \extension{ins} file), with conditional sections, and there are facilities for indexes of macros, etc. Anyone can write \extension{dtx} files; the format is explained in -\Qref*{The \LaTeX{} Companion}{Q-books}, and a tutorial is available +\Qref*{The \LaTeX{} Companion}{Q-latex-books}, and a tutorial is available from \acro{CTAN} (which comes with skeleton \extension{dtx} and \extension{ins} files). @@ -509,6 +653,7 @@ thus permitting documented distribution of bundles containing code for \item[makedtx]\CTANref{makedtx} \item[sty2dtx]\CTANref{sty2dtx} \end{ctanrefs} +\LastEdit{2011-06-01} \Question[Q-whatenc]{What are encodings?} @@ -532,19 +677,19 @@ between a set of numbers and a set of things to be represented. \TeX{} of course deals in encoded characters all the time: the characters presented to it in its input are encoded, and it emits -encoded characters in its \acro{DVI} (or \acro{PDF}) output. These +encoded characters in its \acro{DVI} or \acro{PDF} output. These encodings have rather different properties. The \TeX{} input stream was pretty unruly back in the days when Knuth first implemented the language. Knuth himself prepared documents on terminals that produced all sorts of odd characters, and as a result -\TeX{} contains some provision for translating the input encoding to -something regular. Nowadays, +\TeX{} contains some provision for translating its input (however +encoded) to something regular. Nowadays, the operating system translates keystrokes into a code appropriate for -the user's language: the encoding used is 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 +the user's language: the encoding used is usually a national or +international standard, though some operating systems use ``code +pages'' (as defined by Microsoft). These standards and code pages often +contain characters that may not appear in the \TeX{} system's input stream. Somehow, these characters have to be dealt with~--- so an input character like ``\'e'' needs to be interpreted by \TeX{} in a way that that at least mimics the way it interprets ``\csx{'}\texttt{e}''. @@ -748,16 +893,16 @@ Adobe has specified a number of formats for files to represent fonts in \PS{} files; this question doesn't attempt to be encyclopaedic, so we only discuss the two formats most commonly encountered in the \AllTeX{} context, types~1 and 3. In particular, we don't discuss the -OpenType format, whose many advantages have only in the last year -or two been readily accessible to most \AllTeX{} users (by means of -\begin{wideversion} +OpenType format, whose many advantages now becoming accessible to most +\AllTeX{} users (by means of +\begin{hyperversion} the widely-used \Qref{\xetex{}}{Q-xetex} and the more experimental \Qref{\LuaTeX{}}{Q-luatex}). -\end{wideversion} -\begin{narrowversion} +\end{hyperversion} +\begin{flatversion} the widely-used \xetex{}~--- see \Qref[question]{}{Q-xetex}~--- and the more experimental \LuaTeX{}~--- see \Qref[question]{}{Q-luatex}). -\end{narrowversion} +\end{flatversion} Adobe Type~1 format specifies a means to represent outlines of the glyphs in a font. The `language' used is closely restricted, to ensure that diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex index e69cd7e186f..95e7330c269 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex @@ -1,11 +1,30 @@ -% $Id: faq-docs.tex,v 1.16 2011/03/02 19:56:12 rf10 Exp $ +% $Id: faq-docs.tex,v 1.24 2011/07/19 18:58:57 rf10 Exp $ \section{Documentation and Help} -\Question[Q-books]{Books on \TeX{} and its relations} +\Question[Q-book-lists]{Books relevant to \tex{} and friends} -While Knuth's book is the definitive reference for \TeX{}, there are -other books covering \TeX{}: +There are too many books for them all to appear in a single list, so +the following answers aim to cover ``related'' books, with subject +matter as follows: +\begin{itemize} +\item \Qref*{\tex{} itself and \plaintex{}}{Q-tex-books} +\item \Qref*{\latex{}}{Q-latex-books} +\item \Qref*{Books on other \tex{}-related matters}{Q-other-books} +\item \Qref*{Books on Type}{Q-type-books} +\end{itemize} + +These lists only cover books in English: notices of new books, or +warnings that books are now out of print are always welcome. However, +these \acro{FAQ}s do \emph{not} carry reviews of current published +material. +\LastEdit*{2011-06-01} + +\Question[Q-tex-books]{Books on \TeX{}, \plaintex{} and relations} +\AliasQuestion{Q-books} + +While Knuth's book is the definitive reference for both \TeX{} and +\plaintex{}, there are many books covering these topics: \begin{booklist} \item[The \TeX{}book]by Donald Knuth (Addison-Wesley, 1984, \ISBN{0-201-13447-0}, paperback \ISBN{0-201-13448-9}) @@ -22,7 +41,7 @@ other books covering \TeX{}: Krantz (CRC Press, 1994, \ISBN{0-849-37159-7}) \item[\TeX{} by Topic]by Victor Eijkhout (Addison-Wesley, 1992, \ISBN{0-201-56882-9}~--- now out of print, but see - \Qref[question]{online books}{Q-ol-books}; you can now buy a copy + \Qref[question]{online books}{Q-ol-books}; you can also now buy a copy printed, on demand, by Lulu~--- see \url{http://www.lulu.com/content/2555607}) \item[\TeX{} for the Beginner]by Wynter Snow (Addison-Wesley, 1992, @@ -38,10 +57,10 @@ other books covering \TeX{}: Vol.~2: \ISBN{0-387-97596-9}, % (3-540-97596-9) Vol.~3: \ISBN{0-387-97597-7}, and % (3-540-97597-7) Vol.~4: \ISBN{0-387-97598-5})% (3-540-97598-5) -\htmlignore +\begin{typesetversion} \item[\TeX{}: Starting from \sqfbox{1}\,\footnotemark]% \footnotetext{That's `Starting from Square One'}% -\endhtmlignore +\end{typesetversion} \begin{htmlversion} \item[\TeX{}: Starting from Square One] \end{htmlversion} @@ -66,7 +85,10 @@ A collection of Knuth's publications about typography is also available: (Addison-Wesley, 2001, \ISBN{0-201-73416-8}). \end{booklist} \checked{rf}{2000/02/12 -- http://cseng.aw.com/book/0,3828,0201734168,00.html} -For \LaTeX{}, see: +\LastEdit*{2011-06-01} + +\Question[Q-latex-books]{Books on \latex{}} + \begin{booklist} \item[\LaTeX{}, a Document Preparation System]by Leslie Lamport (second edition, Addison Wesley, 1994, \ISBN{0-201-52983-1}) @@ -87,10 +109,14 @@ For \LaTeX{}, see: \emph{\LaTeX{} and \TeX{} strategies for fonts, graphics, and more} by Alan Hoenig (Oxford University Press, 1998, \ISBN{0-19-509685-1} hardback, \ISBN{0-19-509686-X} paperback) -\item[Math into \LaTeX{}:]\emph{An Introduction to \LaTeX{} and \AMSLaTeX{}} - by George Gr\"atzer (third edition Birkh\"auser and Springer Verlag, - 2000, \ISBN{0-8176-4431-9}, \ISBN{3-7643-4131-9}) -\checked{RF}{2001/01/16} +% \item[Math into \LaTeX{}:]\emph{An Introduction to \LaTeX{} and \AMSLaTeX{}} +% by George Gr\"atzer (third edition Birkh\"auser and Springer Verlag, +% 2000, \ISBN{0-8176-4431-9}, \ISBN{3-7643-4131-9}) +% \checked{RF}{2001/01/16} +\item[More Math into \latex{}:]\emph{An Introduction to \LaTeX{} and + \AMSLaTeX{}}by George Gr\"atzer (fourth edition Springer Verlag, + 2007, \ISBN{978-0-387-32289-6} +\checked{RF}{2011-07-06} %% gr\"atzer's home page %% http://www.maths.umanitoba.ca/homepages/gratzer.html/LaTeXBooks.html \item[Digital Typography Using \LaTeX{}]Incorporating some @@ -112,10 +138,20 @@ For \LaTeX{}, see: \end{booklist} A sample of George Gr\"atzer's ``Math into \LaTeX{}'', in Adobe Acrobat format, and example files -%for von Bechtolsheim's ``\TeX{} in Practice'', for the three \LaTeX{} Companions, and for Gr\"atzer's ``First Steps in \LaTeX{}'', are all available on \acro{CTAN}. +\begin{ctanrefs} +\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}First Steps in \LaTeX{}]\CTANref{gfs} +\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\LaTeX{} Companion]\CTANref{tlc2} +\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\LaTeX{} Graphics Companion]\CTANref{lgc} +\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\LaTeX{} Web Companion]\CTANref{lwc} +%\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\TeX{} in Practice]\CTANref{tip} +\item[\nothtml{\rmfamily}Sample of \nothtml{\upshape}Math into \LaTeX{}]\CTANref{mil} +\end{ctanrefs} +\LastEdit*{2011-07-06} + +\Question[Q-other-books]{Books on other \tex{}-related matters} There's a nicely-presented list of of ``recommended books'' to be had on the web: \URL{http://www.macrotex.net/texbooks/} @@ -137,21 +173,9 @@ maintenance) is: The book is decidedly dated, and is now out of print, but a copy is available via \texttt{sourceforge} and on \acro{CTAN}, and we list it under ``\Qref*{online books}{Q-ol-books}''. +\LastEdit*{2011-06-01} - -This list only covers books in English: notices of new books, or -warnings that books are now out of print are always welcome. However, -this \acro{FAQ} does \emph{not} carry reviews of current published material. -\begin{ctanrefs} -\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}First Steps in \LaTeX{}]\CTANref{gfs} -\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\LaTeX{} Companion]\CTANref{tlc2} -\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\LaTeX{} Graphics Companion]\CTANref{lgc} -\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\LaTeX{} Web Companion]\CTANref{lwc} -%\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\TeX{} in Practice]\CTANref{tip} -\item[\nothtml{\rmfamily}Sample of \nothtml{\upshape}Math into \LaTeX{}]\CTANref{mil} -\end{ctanrefs} - -\Question[Q-typebooks]{Books on Type} +\Question[Q-type-books]{Books on Type} The following is a partial listing of books on typography in general. Of these, Bringhurst seems to be the one most often recommended. @@ -200,6 +224,7 @@ a more interesting overall view of types in general and some of their history. The above lists are limited to books published in English. Typographic styles are somewhat language-dependent, and similarly the `interesting' fonts depend on the particular writing system involved. +\LastEdit{2011-06-01} \Question[Q-whereFAQ]{Where to find \acro{FAQ}s} @@ -277,67 +302,92 @@ Resources available on \acro{CTAN} are: \item[\nothtml{\rmfamily}The visual \acro{FAQ}]\CTANref{visualFAQ} \end{ctanrefs} -\Question[Q-gethelp]{How to get help} +\Question[Q-gethelp]{Getting help online} -So you've looked at all relevant \Qref*{\acro{FAQ}s}{Q-whereFAQ} you -can find, you've looked in any \Qref*{books}{Q-books} you have, and -scanned relevant \Qref*{tutorials}{Q-tutorials*}\dots{} and still you -don't know what to do. +We assume, here, that you have looked at all relevant +\Qref*{\acro{FAQ} answers}{Q-whereFAQ} you can find, you've looked in +any \Qref*{books}{Q-book-lists} you have, and scanned relevant +\Qref*{tutorials}{Q-tutorials*}\dots{} and still you don't know what +to do. -If you are seeking a particular package or program, look on your own -system first: you might already have it~--- the better \TeX{} -distributions contain a wide range of supporting material. The -\acro{CTAN} Catalogue can also identify packages that might help: you -can \href{http://www.tex.ac.uk/search}{search it}, or you can browse it +There are two more steps you can take before formulating a question to +the \tex{} world at large. + +First, (if you are seeking a particular package or program), start by +looking on your own system: you might already have what you seek~--- +the better \TeX{} distributions provide a wide range of supporting +material. The \Qref*{\acro{CTAN} Catalogue}{Q-catalogue} can also +identify packages that might help: you can % ! line break +\href{http://www.tex.ac.uk/search}{search it}, or you can browse it \begin{hyperversion} % !!!! line break ``\href{http://mirrors.ctan.org/help/Catalogue/bytopic.html}{by topic}''. \end{hyperversion} -\begin{dviversion} -``by topic'' at \url{http://mirrors.ctan.org/help/Catalogue/bytopic.html} -\end{dviversion} +\begin{flatversion} +``by topic'' at +\url{http://mirrors.ctan.org/help/Catalogue/bytopic.html} +\end{flatversion} Each catalogue entry has a brief description of the package, and links to -any known documentation on the net. In fact, a large proportion of +known documentation on the net. In fact, a large proportion of \acro{CTAN} package directories now include documentation, so it's often worth looking at the catalogue entry for a package you're considering using (where possible, each package link in the main body of these \acro{FAQ}s \hyperflat{has a link to}{shows the \acro{URL} of} the relevant catalogue entry). -Failing all that, look to see if anyone else has had the problem -before; there are two places where people ask: browse or search the -newsgroup \Newsgroup{comp.text.tex} via -\href{http://groups.google.com/group/comp.text.tex}{Google groups}, -and the mailing list \texttt{texhax} via its -\href{http://tug.org/pipermail/texhax/}{archive}, or (as a long shot) -the archives of its ancient posts on \acro{CTAN}. - -If those ``back question'' searches fail, you'll have to ask the world -at large. To ask a question on \Newsgroup{comp.text.tex}, you can use -your own news client (if you have one), or use the ``start a new -topic'' button on \URL{http://groups.google.com/group/comp.text.tex}. -To ask a question on \texttt{texhax}, you may simply send mail to -\mailto{texhax@tug.org}, but it's probably better to subscribe to the -list (via \URL{http://tug.org/mailman/listinfo/texhax}) % ! no ~ on this line -first~--- not everyone will answer to you as well as to the list. - -Other alternative sources are the % ! line break -\href{http://www.latex-community.org/}{``\LaTeX{} community'' site} or -\href{http://tex.stackexchange.com/}{\TeX{}, \LaTeX{} and friends Q\&A site}. -Neither of these is particularly long-established (the ``friends'' -site is still in \latexhtml{\ensuremath{\beta}-state}{beta state} at -the time of writing), but they're already popular and helpful. - -Do \textbf{not} try mailing the % ! line break -\Qref*{\LaTeX{} project team}{Q-LaTeX3}, -the maintainers of the \texlive{} or \miktex{} distributions -or the maintainers of these \acro{FAQ}s -for help; while all these addresses reach experienced \AllTeX{} -users, no small group can possibly have expertise in every area of -usage so that the ``big'' lists are a far better bet. +Failing that, look to see if anyone has solved the problem before; +places where people ask are: +\begin{enumerate} +\item newsgroup \Newsgroup{comp.text.tex}, whose ``historical posts'' + are accessible via + \href{http://groups.google.com/group/comp.text.tex}{Google groups}, + and +\item the mailing list \texttt{texhax} via its + \href{http://tug.org/pipermail/texhax/}{archive}, or via the `Gmane' + newsgroup \Newsgroup{gmane.comp.tex.texhax}, which holds a + \emph{very} long history of the list. A long shot would be to + search the archives of the mailing list's ancient posts on + \acro{CTAN}, which go back to the days when it was a digest: in + those days, a question asked in one issue would only ever be + answered in the next one. +\end{enumerate} +If the ``back question'' searches fail, you must ask the world at +large. + +So, how do you like to ask questions?~--- the three available +mechanisms are: +\begin{enumerate} +\item Mailing lists: there are various specialist mailing lists, but + the place for `general' \alltex{} queries is the \texttt{texhax} + mailing list. Mail to \mailto{texhax@tug.org} to ask a question, + but it's probably better to subscribe to the list + (via \URL{http://tug.org/mailman/listinfo/texhax}) % ! no ~ allowed + first~--- not everyone will answer to you as well as to the list. +\item Newsgroup: to ask a question on \Newsgroup{comp.text.tex}, you + can use your own news client (if you have one), or use the ``+ new + post'' button on + \URL{http://groups.google.com/group/comp.text.tex}. +\item Web forum: alternatives are: the % ! line break + \href{http://www.latex-community.org/}{``\LaTeX{} community'' site}, + which offers a variety of `categories' to place your query, and the + % the next line will tend to break if you add _anything_ to it! + \href{http://tex.stackexchange.com/}{\TeX{}, \LaTeX{} and friends Q\&A site} + (``Stack exchange''). + + Stack exchange has a scheme for voting on the quality of answers (and + hence of those who offer support). This arrangement is supposed to + enable you to rank any answers that are posted. +\end{enumerate} +Do \textbf{not} try mailing the \LaTeX{} project team, the maintainers +of the \texlive{} or \miktex{} distributions or the maintainers of +these \acro{FAQ}s for help; while all these addresses reach +experienced \AllTeX{} users, no small group can possibly have +expertise in every area of usage so that the ``big'' lists and forums +are a far better bet. \begin{ctanrefs} \item[texhax \nothtml{\rmfamily}`back copies']\CTANref{texhax} \end{ctanrefs} +\LastEdit{2011-05-27} \Question[Q-maillists*]{Specialist mailing lists} @@ -658,7 +708,7 @@ a copy is maintained on \acro{CTAN}. Two documents written more than ten years apart about font usage in \TeX{} are worth reading: % ! line breaks, next 3 lines -\href{href='http://www.tug.org/TUGboat/Articles/tb14-2/tb39rahtz-nfss.pdf}{Essential NFSS} +\href{http://www.tug.org/TUGboat/Articles/tb14-2/tb39rahtz-nfss.pdf}{Essential NFSS} by Sebastian Rahtz, and \href{http://tug.org/pracjourn/2006-1/schmidt/schmidt.pdf}{Font selection in LaTeX}, cast in the form of an \acro{FAQ}, by Walter Schmidt. A general @@ -680,15 +730,20 @@ monolithic document). Keith Reckdahl's ``Using Imported Graphics in \LaTeXe{}'' is an excellent introduction to graphics use. It's available on -\acro{CTAN}, but the sources aren't available (promised ``some time -soon''). +\acro{CTAN}, but the sources aren't available (though they were +promised some time back, they've not appeared, so the package is not +available in \texlive{} or \miktex{}). 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.texample.net/tikz/examples/}{examples catalogue} includes examples (with output) from the package documentation as well -as code written by the author himself. +as code written by the author himself. The compendious +\acro{PGF}/\acro{T}ik\acro{Z} manual is clear, but is bewildering for +some beginners. The ! line break +\href{http://cremeronline.com/LaTeX/minimaltikz.pdf}{`minimal' introduction} +has helped at least the present author. Vincent Zoonekynd provides a set of excellent (and graphic) tutorials on the programming of % !line breaks, ... @@ -822,7 +877,7 @@ is also worth a read: among other things, it provides copies of the ``guidelines'' document in a wide variety of primary fonts, for comparison purposes. The author is careful to explain that he has no ambition to supplant such excellent books as -\Qref*{Bringhurst's}{Q-typebooks}, but the document (though it does +\Qref*{Bringhurst's}{Q-type-books}, but the document (though it does contain its Rutgers-local matter) is a fine introduction to the issues of producing readable documents. \begin{ctanrefs} @@ -833,7 +888,7 @@ of producing readable documents. T\acro{UG} India is developing a series of online \LaTeX{} tutorials which can be strongly recommended: select single chapters at a time -from \URL{http://www.tug.org.in/tutorials.html}\nobreakspace--- the +from \URL{http://www.tug.org/tutorials/tugindia}\nobreakspace--- the set comprises two parts, ``Text'' and ``Graphics'', so far. Once, there were other links like that, but all the others have faded @@ -870,6 +925,7 @@ to update it is believed to be under way. \item[\nothtml{\rmfamily}\TeX{} by Topic]\CTANref{texbytopic} \item[\nothtml{\rmfamily}\TeX{} for the Impatient]\CTANref{TftI} \end{ctanrefs} +\LastEdit{2011-06-29} \Question[Q-pkgdoc]{Documentation of packages} @@ -923,10 +979,11 @@ Another common form is the separate documentation file; particularly if a package is ``conceptually large'' (and therefore needs a lot of documentation), the documentation would prove a cumbersome extension to the \extension{dtx} file. Examples of such cases are the \Class{memoir} -class (whose documentation, \File{memman}, is widely praised as an -introduction to typesetting concepts), the \Class{KOMA-script} bundle +class, the \Class{KOMA-script} bundle (whose developers take the trouble to produce detailed documentation -in both German and English), and the \Package{fancyhdr} package (whose +in both German and English), the \Package{pgf} documentation (which +would make a substantial book in its own right) +and the \Package{fancyhdr} package (whose documentation derives from a definitive tutorial in a mathematical journal). Even if the documentation is not separately identified in a \texttt{README} file, it should not be too difficult to recognise its @@ -947,6 +1004,7 @@ to write, it should be hard to use'' philosophy). Most ordinary mortals will seek support from some more experienced user at this stage, though it \emph{is} possible to proceed in the way that the original author apparently expected\dots{}by reading his code. +\LastEdit{2011-07-19} \Question[Q-writecls]{Learning to write \LaTeX{} classes and packages} @@ -960,7 +1018,7 @@ sophistication. Some details of \LaTeX{} commands for the job are to be found in `\LaTeXe{} for class and package writers' (\File{clsguide}, part of the \LaTeX{} documentation distribution). Beyond this, a good knowledge of \TeX{} itself is valuable: thus books -such as the \Qref*{\TeX{}book}{Q-books} or % ! line break +such as the \Qref*{\TeX{}book}{Q-tex-books} or % ! line break \Qref*{\TeX{} by topic}{Q-ol-books} are relevant. With good \TeX{} knowledge it is possible to use the documented source of \LaTeX{} as reference material (dedicated authors will acquaint themselves with the @@ -984,7 +1042,7 @@ technique may be seen in \Package{ltxguide.cls} An % !! line break \href{http://tug.org/TUGboat/Articles/tb28-1/tb88flynn.pdf}{annotated version of \Class{article}}, as it appears in \File{classes.dtx}, was published in -\TUGboat{} 28(1). The article, by Peter Flynn, which is some help in +\TUGboat{} 28(1). The article, by Peter Flynn, is a good guide to understanding \File{classes.dtx} \begin{ctanrefs} \item[classes.dtx]\CTANref{latex-classes} @@ -994,6 +1052,7 @@ understanding \File{classes.dtx} \item[\nothtml{\rmfamily}\LaTeX{} documentation]\CTANref{latexdoc} \item[source2e.tex]\CTANref{latex-source} \end{ctanrefs} +\LastEdit{2011-07-19} \Question[Q-mfptutorials]{\MF{} and \MP{} Tutorials} @@ -1054,7 +1113,7 @@ The document ``\bibtex{}ing'', in the \bibtex{} distribution (look for \File{btxdoc}), expands on the chapter in Lamport's book. \emph{The \LaTeX{} Companion} also has information on \bibtex{} and writing \bibtex{} style files. -(See \Qref[question]{TeX-related books}{Q-books} for details of both +(See \Qref[question]{\latex{} books}{Q-latex-books} for details of both books.) The document ``Designing \bibtex{} Styles'', also in the \bibtex{} @@ -1107,9 +1166,9 @@ trying more than once. Given the huge size of the symbol list, this tool can be very helpful. \begin{ctanrefs} \item[Symbol List]Browse \CTANref{symbols}; there are processed - versions in both \PS{} and \acro{PDF} forms for both A4 and - letter paper. + versions \acro{PDF} form for both A4 and letter paper. \end{ctanrefs} +\LastEdit{2011-07-01} \Question[Q-docpictex]{The \PiCTeX{} manual} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex index ccb4e406086..9ad13a1ee2e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex @@ -1,4 +1,4 @@ -% $Id: faq-fmt-conv.tex,v 1.5 2011/02/08 22:17:17 rf10 Exp $ +% $Id: faq-fmt-conv.tex,v 1.7 2011/07/21 19:16:13 rf10 Exp rf10 $ \section{Format conversions} @@ -16,8 +16,9 @@ response. Options are: \item \ProgName{crudetype} and \item \ProgName{catdvi}, which is capable of generating Latin-1 (ISO~8859-1) or \acro{UTF}-8 encoded output. \ProgName{Catdvi} was - conceived as a replacement for \ProgName{dvi2tty}, but can't (quite) - be recommended as a complete replacement yet. + conceived as a replacement for \ProgName{dvi2tty}, but development + seems to have stopped before the authors were willing to declare the + work complete. \end{itemize} A common problem is the hyphenation that \TeX{} inserts when typesetting something: since the output is inevitably viewed using @@ -26,8 +27,7 @@ silly. Ralph Droms provides a \Package{txt} bundle of things in support of \acro{ASCII} generation, -but it doesn't do a good job with tables and mathematics. An -alternative is the \Package{screen} package. +but it doesn't do a good job with tables and mathematics. Another possibility is to use the \LaTeX{}-to-\acro{ASCII} conversion program, \ProgName{l2a}, @@ -58,10 +58,10 @@ and then to use a browser such as \ProgName{lynx} to dump the resulting \item[detex]\CTANref{detex} \item[dvi2tty]\CTANref{dvi2tty} \item[l2a]\CTANref{l2a} -\item[screen.sty]\CTANref{screensty} \item[tex2mail]\CTANref{tex2mail} \item[txt]\CTANref{txtdist} \end{ctanrefs} +\LastEdit{2011-07-21} \Question[Q-SGML2TeX]{Conversion from \acro{SGML} or \acro{HTML} to \protect\TeX{}} @@ -436,9 +436,9 @@ an alternative target of translation, though it undoubtedly gives the user more than the ``bare minimum'' that \plaintex{} is designed to offer.) \begin{ctanrefs} -\item[\latexhtml{\textrm{The}}{The} eplain \nothtml{\rmfamily}system]% +\item[\nothtml{\begingroup\rmfamily}The\nothtml{\endgroup} eplain \nothtml{\rmfamily}system]% \CTANref{eplain} -\item[\latexhtml{\textrm{`\plaintex{}'}}{\plaintex{}} graphics]% +\item[\nothtml{\begingroup\rmfamily`}\plaintex{}\nothtml{'\endgroup} graphics]% \CTANref{graphics-plain} \end{ctanrefs} - +\LastEdit{2011-05-04}
\ No newline at end of file diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex index 2f649fb9ae2..364bae81c4b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex @@ -1,4 +1,4 @@ -% $Id: faq-fonts.tex,v 1.15 2011/04/13 09:45:46 rf10 Exp $ +% $Id: faq-fonts.tex,v 1.17 2011/09/04 10:03:23 rf10 Exp $ \section{Fonts} @@ -120,7 +120,7 @@ error-prone); or you change the encoding of the font (easier than you might think); or you use \Qref*{virtual fonts}{Q-virtualfonts} to \emph{pretend} to \TeX{} that the encoding is the same as it is used to. \LaTeXe{} has facilities for dealing with fonts in different -encodings; read the \Qref*{\emph{\LaTeX{} Companion}}{Q-books} for +encodings; read the \Qref*{\emph{\LaTeX{} Companion}}{Q-latex-books} for more details. In practice, if you do much non-English (but Latin script) typesetting, you are strongly recommended to use the \Package{fontenc} package with option `\pkgoption{T1}' to select @@ -159,6 +159,7 @@ software, and is available on \acro{CTAN}. \item[fontinst]\CTANref{fontinst} \item[LY1 support]\CTANref{ly1} \end{ctanrefs} +\LastEdit{2011-06-01} \Question[Q-psfontprob]{Deploying Type 1 fonts} @@ -896,9 +897,10 @@ Now, incorporate the fonts in the set searched by \PDFLaTeX{}, previewers and Type~1-to-\acro{PK} conversion programs, by \begin{itemize} \item On a te\TeX{} system earlier than version~2.0, edit the file - \File{$TEXMF/dvips/config/updmap} and insert an absolute path for - the \File{lm.map} just after the line that starts - \texttt{extra\_modules="} (and before the closing quotes). + \File{$TEXMF/dvips/config/updmap} %$ + and insert an absolute path for the \File{lm.map} just after the + line that starts \texttt{extra\_modules="} (and before the closing + quotes). \item On a te\TeX{} version~2.0 (or later), execute the command \begin{quote} \begin{verbatim} @@ -950,18 +952,20 @@ unlike \TeX{}, requires customisation for each output device: such customisation is conventionally held in a ``mode'' associated with the device. Modes are commonly defined using the \texttt{mode\_def} convention described on page~94 of \emph{The \MF{}book} % ! line break -(see \Qref[question]{\TeX{}-related books}{Q-books}). You will need +(see \Qref[question]{\TeX{}-related books}{Q-other-books}). Your +distribution should provide a file, conventionally called \File{local.mf}, containing all the \texttt{mode\_def}s you will be using. In the unlikely event that \File{local.mf} doesn't already exist, Karl Berry's collection of modes (\File{modes.mf}) is a good starting point (it can be used as a `\File{local.mf}' without modification in a -typical modern implementation of \MF{}). Lists of -settings for various output devices are also published periodically in -\textsl{TUGboat} (see \Qref[question]{\acro{TUG}}{Q-TUG*}). Now create +modern implementation of \MF{}). +Settings for new output devices are added to \File{modes.mf} as they +become available. + +Now create a \texttt{plain} base file using \ProgName{mf} (in ``initialisation'' mode), \texttt{plain.mf}, and \texttt{local.mf}: -\begin{htmlversion} \begin{quote} \begin{verbatim} % mf -ini @@ -975,24 +979,10 @@ Beginning to dump on file plain... (output) \end{verbatim} \end{quote} -\end{htmlversion} -\htmlignore -\begin{list}{}{}\item\relax - \texttt{\% mf -ini}\\ - This is METAFONT\dots{}\\{} - \fullline{**\texttt{plain}\hss you type `\texttt{plain}'} - (\emph{output})\\{} - \fullline{*\texttt{input local}\hss you type this} - (\emph{output})\\{} - \fullline{*\texttt{dump}\hss you type this} - Beginning to dump on file plain\dots{}\\{} - (\emph{output}) -\end{list}\par -\endhtmlignore -This will create a base file named \File{plain.base} -(or something similar; for example, it will be \File{PLAIN.BAS} -on \MSDOS{} systems). Move the file to the directory containing -the base files on your system. +This will create a base file named \File{plain.base} (or something +similar; for example, it will be \File{PLAIN.BAS} on \MSDOS{} +systems). Move the file to the directory containing the base files on +your system, and run \ProgName{texhash} as necessary. Now you need to make sure \MF{} loads this new base when it starts up. If \MF{} loads the \texttt{plain} base by default on your system, then you're @@ -1029,11 +1019,14 @@ in response to the `\texttt{**}' prompt or on the \MF{} command line. (If \texttt{<mode name>} is unknown or omitted, the mode defaults to `proof' mode and \MF{} will produce an output file called % ! line break \File{<font file name>.2602gf}) -The \texttt{<magnification>} is a floating point number or -`magstep' (magsteps are defined in \emph{The \MF{}book} and -\emph{The \TeX{}book}). +The \texttt{<magnification>} is a floating point number or a +`magstep' (magsteps define sizes by stating how many times you need to +multiply a base size by \texttt{1.2}, so for a base size of +\texttt{10}, \texttt{magstep 1} is \texttt{12}, \texttt{magstep 2} is +\texttt{14.4} If \texttt{mag=<magnification>} is omitted, then the default -is 1~(magstep 0). For example, to generate cmr10 at 12pt for an Epson +is \texttt{1}~(\texttt{magstep 0}). For example, to generate +\FontName{cmr10} at \texttt{12pt} for an Epson, printer you might type \begin{quote} \begin{verbatim} @@ -1083,6 +1076,7 @@ Other sources of help are discussed in our list of % ! line break \begin{ctanrefs} \item[modes.mf]\CTANref{modes-file} \end{ctanrefs} +\LastEdit{2011-09-04} \Question[Q-keepfonts]{Which font files should be kept} @@ -1090,11 +1084,8 @@ Other sources of help are discussed in our list of % ! line break generic font (\acro{GF}) file, and a log file; all of these files have the same base name as does the input (\emph{e.g.}, if the input file was \File{cmr10.mf}, the outputs will be \File{cmr10.tfm}, -\File{cmr10.nnngf}% -\begin{footnoteenv} - Note that the file name may be transmuted by such operating systems - as \MSDOS{}, which don't permit long file names -\end{footnoteenv} +\File{cmr10.nnngf} (the file name may be mangled if you are using an +operating system which doesn't permit long file names) and \File{cmr10.log}). For \TeX{} to use the font, you need a \acro{TFM} file, so you need @@ -1105,14 +1096,18 @@ all the same, so you only need to keep one of them. To preview or to produce printed output, the \acro{DVI} processor will need a font raster file; this is what the \acro{GF} file provides. However, while -there used (once upon a time) to be \acro{DVI} processors that could use -\acro{GF} files, modern processors use packed raster (\acro{PK}) files. +there used (once upon a time) to be \acro{DVI} processors that could use +\acro{GF} files, modern processors use +packed raster (\acro{PK}) files (incidentally, \pdftex{} also uses +\acro{PK} files if nothing ``better'' is available, but +see \Qref[]{fuzzy fonts in \acro{PDF}}{Q-fuzzy-type3}). Therefore, you need to generate a \acro{PK} file from the \acro{GF} file; the program \ProgName{gftopk} does this for you, and once you've done that you may throw the \acro{GF} file away. -The log file should never need to be used, unless there was some sort -of problem in the \MF{} run, and need not be ordinarily kept. +The log file should never be needed again, unless there was some sort +of problem in the \MF{} run, and need not therefore be kept. +\LastEdit{2011-09-04} \Question[Q-getbitmap]{Acquiring bitmap fonts} @@ -1122,15 +1117,15 @@ Modern bitmap fonts for this resolution are available on \acro{CTAN}. (There are separate sets for write-black and write-white printers, as well as sets at 120~dpi and 240~dpi.) -Over the years, there have been regular requests that \acro{CTAN} should hold +There used to regular requests that \acro{CTAN} should hold a wider range of resolutions, but they were resisted for two reasons: \begin{itemize} \item The need to decide which printers to generate fonts for. The broad-brush approach taken for 300~dpi printers was (more or less) justified back then, given the dominance of certain printer `engines', but nowadays one could not make any such assumption. -\item Given the above, justifying the space taken up by a huge array - of bitmap fonts. +\item Given the above, it has been near-impossible to justify the + space that would be required by a huge array of bitmap fonts. \end{itemize} Fortunately, \AllTeX{} distribution technology has put a stop to these arguments: most (if not all) current distributions generate bitmap @@ -1154,8 +1149,8 @@ advised to use the \Package{bluesky} set except when \Package{bakoma} is for some reason absolutely unavoidable. In recent years, several other `\MF{}' fonts have been converted to Type~1 format; it's uncommon ever to need to generate bitmap fonts for any purpose other -than previewing (see % ! line wrap -\Qref*{``previewing documents with Type~1 fonts''}{Q-PSpreview}), +than previewing~--- see % ! line wrap +\Qref*{``previewing documents with Type~1 fonts''}{Q-PSpreview}~--- if even then. More modern fonts may be used in place of the Computer Modern set. The @@ -1171,3 +1166,4 @@ wider ranges of glyphs to offer. \item[\nothtml{\rmfamily}EC fonts (Type 1 format)]\CTANref{cm-super} \item[\nothtml{\rmfamily}Latin Modern fonts]\CTANref{lm} \end{ctanrefs} +\LastEdit{2011-09-4} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex index 5540c9a5af5..7b7af0a55bc 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex @@ -1,4 +1,4 @@ -% $Id: faq-getit.tex,v 1.8 2011/04/29 15:17:40 rf10 Exp rf10 $ +% $Id: faq-getit.tex,v 1.9 2011/05/08 10:16:43 rf10 Exp $ \section{Acquiring the Software} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex index ae795e5e529..9e063a72408 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex @@ -1,4 +1,4 @@ -% $Id: faq-graphics.tex,v 1.17 2011/04/13 09:45:46 rf10 Exp $ +% $Id: faq-graphics.tex,v 1.20 2011/06/03 18:01:31 rf10 Exp rf10 $ \section{Graphics} @@ -714,7 +714,7 @@ of drawing, and setup, here are a few systems you may consider: \csx{special}s aren't available, the \Package{eepicemu} will do the business, far less efficiently. \item \Package{pict2e}; this was advertised in % !line break - \Qref*{the \LaTeX{} manual}{Q-books}, but didn't appear for nearly + \Qref*{the \LaTeX{} manual}{Q-latex-books}, but didn't appear for nearly ten years after publication of the book! It removes all the petty restrictions that surround the use of the \environment{picture} environment. It therefore suffers \emph{only} from the rather @@ -752,7 +752,10 @@ of drawing, and setup, here are a few systems you may consider: bet for you. While \acro{PDF} has (in essence) the same graphical capabilities as \PS{}, it isn't programmable; \Package{pgf} provides common \LaTeX{} commands that will utilise the graphical - capabilities of both \PS{} and \acro{PDF} equally. + capabilities of both \PS{} and \acro{PDF} equally. The + \Package{pgf} manual is enormous, but a simple introduction which + allows the user to get a feel for the capabilities of the system, is + available at \url{http://cremeronline.com/LaTeX/minimaltikz.pdf} \item \MP{}; you liked \MF{}, but never got to grips with font files? Try \Qref*{\MP{}}{Q-MP}~--- all the power of \MF{}, but it generates \PS{} figures; \MP{} @@ -762,16 +765,19 @@ of drawing, and setup, here are a few systems you may consider: Note that you can % ! line break \Qref*{``embed'' \MP{} source in your document}{Q-inlgrphapp} (i.e., keep it in-line with your \latex{} code). -\item \ProgName{Mfpic}; you liked \MF{}, but can't understand the - language? The package makes up \MF{} or \MP{} code for you - within using familiar-looking \TeX{} macros. Not \emph{quite} the - full power of \MP{}, but a friendlier interface; of course, with - \MP{} output, the results can be used equally well in either - \LaTeX{} or \PDFLaTeX{}. +\item You liked \MF{} (or \MP{}), but find the language difficult? + \ProgName{Mfpic} makes up \MF{} or \MP{} code for you using + familiar-looking \AllTeX{} macros. Not \emph{quite} the full power + of \MF{} or \MP{}, but a friendlier interface, and with \MP{} output + the results can be used equally well in either \LaTeX{} or \PDFLaTeX{}. \item You liked \PiCTeX{} but don't have enough memory or time? Look - at Eitan Gurari's \Package{dratex}: it is just as powerful, but is - an entirely new implementation which is not as hard on memory, is - much more readable (and is fully documented). + at the late Eitan Gurari's \Package{dratex}: it is just as powerful, + but is an entirely new implementation which is not as hard on + memory, is much more readable and is (admittedly sparsely) documented at + \url{http://www.cse.ohio-state.edu/~gurari/tpf/html/README.html}, + as well as in the author's book ``TeX and LATeX: Drawing and + Literate Programming'', which remains available from on-line + booksellers. \end{itemize} In addition, there are several means of generating code for your @@ -792,9 +798,9 @@ see \Qref{question}{Q-inlgrphapp}. \item[pict2e.sty]\CTANref{pict2e} \item[pictex.sty]\CTANref{pictex} \item[pstricks]\CTANref{pstricks} -\item[tikz.sty]Distributed with \CTANref{pgf} +\item[tikz.sty]Distributed as part of \CTANref{pgf} \end{ctanrefs} -\LastEdit{2011-04-08} +\LastEdit{2011-06-03} \Question[Q-inlgrphapp]{In-line source for graphics applications} @@ -947,9 +953,16 @@ graphic for you): within the environment you may use the command \csx{lbl} to position \latex{} material at appropriate places over the graphic. -\Package{Pstricks} can of course do everything that \Package{overpic} -or \Package{lpic} -can, with all the flexibility of \PS{} programming that it offers +\Package{Pstricks} can of course do everything +that \Package{overpic} or \Package{lpic} +can, with all the flexibility of \PS{} programming that it offers. +This capability is exemplified by the \Package{pst-layout} package, +which seems to be a superset of both \Package{overpic} and +\Package{lpic}. + +Similarly, \Package{pgf/TikZ} has all the power needed, but no +explicit package has been released. + The \Package{pstricks} web site has a page with several % ! line break \href{http://pstricks.tug.org/main.cgi?file=Examples/overlay}{examples of labelling} which will get you started; if \Package{pstricks} is % ! line break @@ -962,6 +975,7 @@ are plainly little more than a convenience over what is achievable with the do-it-yourself approach. \begin{ctanrefs} \item[auto-pst-pdf.sty]\CTANref{auto-pst-pdf} +\item[pgf.sty]\CTANref{pgf} \item[iTe]\CTANref{ite} \item[laprint]Distributed with \CTANref{psfragx} \item[lpic.sty]\CTANref{lpic} @@ -969,6 +983,7 @@ with the do-it-yourself approach. \item[psfrag.sty]\CTANref{psfrag} \item[psfragx.sty]\CTANref{psfragx} \item[pstricks.sty]\CTANref{pstricks} +\item[pst-layout.sty]\CTANref{pst-layout} \item[pst-pdf.sty]\CTANref{pst-pdf} \end{ctanrefs} - +\LastEdit{2011-06-02} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex index 34aae1174b7..bcac3f260d8 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex @@ -1,4 +1,4 @@ -% $Id: faq-how-do-i.tex,v 1.28 2011/05/04 06:40:43 rf10 Exp rf10 $ +% $Id: faq-how-do-i.tex,v 1.34 2011/09/03 18:56:20 rf10 Exp rf10 $ \section{How do I do\dots{}?} @@ -200,7 +200,7 @@ declare what size fonts are to be used in mathematics with it. This is done by declaring \csx{textfont}, \csx{scriptfont} and \csx{scriptscriptfont} for the maths families you're using; all such things are described in chapter~17 of the % line wrap! -\Qref*{\TeX{}book}{Q-books} and in other books and +\Qref*{\TeX{}book}{Q-tex-books} and in other books and \Qref*{tutorials}{Q-man-tex} that discuss \plaintex{} in sufficient detail. @@ -251,6 +251,7 @@ they contain those internal abbreviations, they need to be treated as \item[fontdef.dtx]\CTANref{fontdef} \item[fontmath.ltx]\CTANref{fontmath} \end{ctanrefs} +\LastEdit{2011-06-01} \Question[Q-mathlips]{Ellipses} \keywords{\csx{dots} \csx{cdots} \csx{vdots} \csx{ddots}} @@ -605,6 +606,54 @@ details of how to make references when the switch is in effect. \item[mathtools.sty]Distributed as part of \CTANref{mh}[mathtools] \end{ctanrefs} +\Question[Q-subheight]{Even subscript height} + +Other things being equal, \TeX{} will aim to position subscripts and +superscripts in places that ``look good''. Unfortunately, it only +does this for the sub- and superscripts of each atom at a time, so if +you have +\begin{quote} +\begin{verbatim} +$ X^{1}_{2} X_{2} $ +\end{verbatim} +\end{quote} +the second subscript will appear higher, since the first has moved +down to avoid the superscript; +the effect can be noticeably distracting: +\begin{quote} +\begin{typesetversion} + $ X^{1}_{2} X_{2} $ +\end{typesetversion} +\begin{htmlversion} + \includegraphics{faq-images1.png} +\end{htmlversion} +\end{quote} + +You can avoid the problem, for a single instance, by +\begin{quote} +\begin{verbatim} +$ X^{1}_{2} X^{}_{2} $ +\end{verbatim} +\end{quote} +here, the dummy superscript has the requisite ``pushing down'' effect: +\begin{quote} +\begin{typesetversion} + $ X^{1}_{2} X^{}_{2} $ +\end{typesetversion} +\begin{htmlversion} + \includegraphics{faq-images2.png} +\end{htmlversion} +\end{quote} + +While this technique does what is necessary, it is tedious and +potentially error-prone. So, for more than one or two equations +in a document, the \LaTeX{} user is advised to use the +\Package{subdepth} package, which forces the lower position for all +subscripts. +\begin{ctanrefs} +\item[subdepth.sty]\CTANref{subdepth} +\end{ctanrefs} + \subsection{Lists} \Question[Q-enumerate]{Fancy enumeration lists} @@ -692,7 +741,7 @@ The \Class{memoir} class includes functions that match those in the %% \renewcommand{\labelenumi}{\theenumi/} %% \end{verbatim} %% The possible styles of numbering are given in Section~6.3 of Lamport's -%% book (see \Qref[question]{\TeX{}-related books}{Q-books}). Both +%% book (see \Qref[question]{\TeX{}-related books}{Q-book-lists}). Both %% \csx{theenumi} and \csx{labelenumi} must be changed, since %% \csx{theenumi} is used in cross-references to the list. %% @@ -709,7 +758,7 @@ The \Class{memoir} class includes functions that match those in the \Question[Q-complist]{How to adjust list spacing} -\Qref*{Lamport's book}{Q-books} lists various +\Qref*{Lamport's book}{Q-latex-books} lists various parameters for the layout of list (things like \csx{topsep}, \csx{itemsep} and \csx{parsep}), but fails to mention that they're set automatically within the list itself. This happens because each list @@ -820,6 +869,7 @@ more ``basic'' (and therefore more flexible) manner than the % ! line break \item[paralist.sty]\CTANref{paralist} \item[savetrees.sty]\CTANref{savetrees} \end{ctanrefs} +\LastEdit{2011-06-01} \Question[Q-interruptlist]{Interrupting enumerated lists} @@ -971,7 +1021,7 @@ hardly satisfactory. \Question[Q-destable]{The design of tables} In recent years, several authors have argued that the examples, set -out by Lamport in his \Qref*{\LaTeX{} manual}{Q-books}, have cramped +out by Lamport in his \Qref*{\LaTeX{} manual}{Q-latex-books}, have cramped authors' style and have led to extremely poor table design. It is in fact difficult even to work out what many of the examples in Lamport's book ``mean''. @@ -1021,13 +1071,22 @@ The \Class{KOMA-script} classes provide a similar command \csx{captionabove}; they also have a class option \pkgoption{tablecaptionabove} which arranges that \csx{caption} \emph{means} \csx{captionabove}, in table environments. The -\Package{caption} (from the release of 23 January, 2004) may be loaded +\Package{caption} package may be loaded with an option that has the same effect: \begin{quote} \begin{verbatim} \usepackage[tableposition=top]{caption} \end{verbatim} \end{quote} +or the effect may be established after the package has been loaded: +\begin{quote} +\begin{verbatim} +\usepackage{caption} +\captionsetup[table]{position=above} +\end{verbatim} +\end{quote} +(Note that the two ``position'' options are different: actually, +``above'' and ``top'' in these contexts mean the same thing.) Doing the job yourself is pretty easy: \Package{topcapt} switches the values of the \LaTeXe{} parameters \csx{abovecaptionskip} (default @@ -1045,13 +1104,16 @@ value \texttt{10pt}) and \csx{belowcaptionskip} (default value \end{table} \end{verbatim} \end{quote} -does the job. (The package itself is very slightly more elaborate\dots{}) +does the job (if the length values are right; the package and classes +are more careful!). \begin{ctanrefs} \item[booktabs.sty]\CTANref{booktabs} +\item[caption.sty]\CTANref{caption} \item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script} \item[memoir.cls]\CTANref{memoir} \item[topcapt.sty]\CTANref{topcapt} \end{ctanrefs} +\LastEdit{2011-08-19} \Question[Q-fixwidtab]{Fixed-width tables} @@ -3126,8 +3188,8 @@ following minimal solution: \begin{wideversion} \begin{verbatim} \def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}} -\RCS$Revision: 1.28 $ % or any RCS keyword -\RCS$Date: 2011/05/04 06:40:43 $ +\RCS$Revision: 1.34 $ % or any RCS keyword +\RCS$Date: 2011/09/03 18:56:20 $ ... \date{Revision \RCSRevision, \RCSDate} \end{verbatim} @@ -3137,17 +3199,16 @@ following minimal solution: \def\RCS$#1: #2 ${\expandafter \def\csname RCS#1\endcsname{#2}% } -\RCS$Revision: 1.28 $ % or any RCS keyword -\RCS$Date: 2011/05/04 06:40:43 $ +\RCS$Revision: 1.34 $ % or any RCS keyword +\RCS$Date: 2011/09/03 18:56:20 $ ... \date{Revision \RCSRevision, \RCSDate} \end{verbatim} \end{narrowversion} \end{quote} -If you've entered the brave new world of \ProgName{Subversion}, the -package \Package{svn} may be for you. It has explicit cleverness -about dealing with dates: +If you are a user of \ProgName{Subversion}, the package \Package{svn} +may be for you. It has explicit cleverness about dealing with dates: \begin{quote} \csx{documentclass}\texttt{\{\meta{foo}\}}\\ \texttt{...}\\ @@ -3180,15 +3241,19 @@ reliably than any of the packages mentioned above. The \Package{vc} bundle supports \ProgName{Bazaar}, \ProgName{Git} and \ProgName{Subversion} usage and works with both \LaTeX{} and \plaintex{}. Note that \Package{vc} is the only option that -currently claims to support \ProgName{Bazaar}- and -\ProgName{Git}-controlled repositories. +currently claims to support \ProgName{Bazaar}-controlled repositories. + +Finally, for now, the \Package{gitinfo} package supports +\ProgName{Git}-controlled documents. \begin{ctanrefs} +\item[gitinfo.sty]\CTANref{gitinfo} \item[rcs.sty]\CTANref{rcs} \item[rcsinfo.sty]\CTANref{rcsinfo} \item[svn.sty]\CTANref{svn} \item[svninfo.sty]\CTANref{svninfo} \item[vc]\CTANref{vc} \end{ctanrefs} +\LastEdit{2011-08-31} \Question[Q-make]{Makefiles for \LaTeX{} documents} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex index a0f3d4961fa..85856d8cf1c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex @@ -1,4 +1,4 @@ -% $Id: faq-intro.tex,v 1.20 2011/03/09 21:02:45 rf10 Exp rf10 $ +% $Id: faq-intro.tex,v 1.21 2011/05/25 18:57:21 rf10 Exp $ % this environment is for the benefit of new-style file generation \begin{introduction} @@ -127,6 +127,7 @@ Uwe L\"uck, % correction of typo Daniel Luecking, Aditya Mahajan, % rewrite of q-context Sanjoy Mahajan, +Diego Andres Alvarez Marin, % suggestion of lacheck Andreas Matthias, Steve Mayer, % proof reading Brooks Moses, % editorial suggestion diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex index 9853fec565c..9eec4396699 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex @@ -1,4 +1,4 @@ -% $Id: faq-jot-err.tex,v 1.7 2010/10/06 20:51:19 rf10 Exp $ +% $Id: faq-jot-err.tex,v 1.9 2011/07/06 23:09:00 rf10 Exp rf10 $ \section{The joy of \TeX{} errors} @@ -43,7 +43,7 @@ perplexing) errors that you may encounter. There's a long list of the trace can lead you quickly to the source of a problem. You need to have read the \TeX{}book (see % beware line break - \Qref[question]{books about \TeX{}}{Q-books}) in some detail, fully + \Qref[question]{books about \TeX{}}{Q-tex-books}) in some detail, fully to understand the trace. The command \csx{tracingall} sets up maximum tracing; it also sets @@ -71,6 +71,7 @@ report full backtraces (see |errorcontextlines| above) and so on. \begin{ctanrefs} \item[trace.sty]Distributed as part of \CTANref{2etools}[trace] \end{ctanrefs} +\LastEdit{2011-06-01} \Question[Q-errstruct]{The structure of \TeX{} error messages} @@ -697,7 +698,7 @@ number. Usually the problem will become clear using the Two \LaTeX{}-specific errors are commonly aired on the newsgroups. The commonest arises from attempting to use an example from the -\Qref*{\emph{The \LaTeX{} Companion} (first edition)}{Q-books}, and is +\Qref*{\emph{The \LaTeX{} Companion} (first edition)}{Q-latex-books}, and is exemplified by the following error text: \begin{verbatim} ! Missing number, treated as zero. @@ -734,6 +735,7 @@ text rather better. \item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\LaTeX{} Companion]\CTANref{tlc2} \item[The psnfss bundle]\CTANref{psnfss} \end{ctanrefs} +\LastEdit{2011-06-01} \Question[Q-typend]{``Please type a command or say \csx{end}''} @@ -1353,8 +1355,8 @@ solve the problem, you need to \Qref*{seek further help}{Q-gethelp}. This is an error you may encounter in \LaTeX{} when a tabular environment is being processed. ``Alignment tabs'' are the -\texttt{\&} signs that separate the columns of a tabular; so the error -message +\texttt{\&} signs that separate the columns of a \environment{tabular} +(or \environment{array} or matrix) environment; so the error message \begin{quote} \begin{narrowversion} \begin{verbatim} @@ -1428,9 +1430,22 @@ Get rid of the error in the way described in % ! linebreak \Qref[question]{tabular cell alignment}{Q-tabcellalign}~--- either use \csx{tabularnewline} explicitly, or use the \csx{RBS} trick described there. + +The \Package{amsmath} package adds a further twist; when typesetting +a matrix (the package provides many matrix environments), it has a +fixed maximum number of columns in a matrix~--- exceed that maximum, +and the error will appear. By default, the maximum is set to 10, but +the value is stored in counter \texttt{MaxMatrixCols} and may be +changed (in the same way as any counter): +\begin{quote} +\begin{verbatim} +\setcounter{MaxMatrixCols}{20} +\end{verbatim} +\end{quote} \begin{ctanrefs} \item[array.sty]Distributed as part of \CTANref{2etools}[array] \end{ctanrefs} +\LastEdit{2011-07-06} \Question[Q-divzero]{Graphics division by zero} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-lab-ref.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-lab-ref.tex index a23cd70dba7..d1629fd7b7c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-lab-ref.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-lab-ref.tex @@ -1,4 +1,4 @@ -% $Id: faq-lab-ref.tex,v 1.3 2011/03/09 21:02:45 rf10 Exp rf10 $ +% $Id: faq-lab-ref.tex,v 1.4 2011/05/08 10:16:43 rf10 Exp $ \subsection{Labels and references} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex index a3799f9bf03..ddde1de0ab1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex @@ -1,4 +1,4 @@ -% $Id: faq-mac-prog.tex,v 1.17 2011/03/17 21:18:43 rf10 Exp $ +% $Id: faq-mac-prog.tex,v 1.23 2011/07/10 22:51:12 rf10 Exp rf10 $ \section{Macro programming} @@ -225,7 +225,7 @@ would naturally write: \end{quote} However, this would not work: a call to \csx{splat} would execute \csx{mumble}, and the call the redefined \csx{splat} again; this is an -unterminated recursion, that will quickly exhaust \TeX{}'s memory. +`unterminated recursion', that will quickly exhaust \TeX{}'s memory. Fortunately, the \TeX{} primitive \csx{let} command comes to our rescue; it allows us to take a ``snapshot'' of the current state of a @@ -238,8 +238,9 @@ So: \end{verbatim} \end{quote} effects the required patch, safely. Adding things at the end of a -command works similarly. If \csx{smooth} takes arguments, one must -pass them on: +command works similarly. + +If \csx{smooth} takes arguments, one must pass them on: \begin{quote} \begin{wideversion} \begin{verbatim} @@ -256,6 +257,35 @@ pass them on: \end{narrowversion} \end{quote} +The situation is more difficult still if \csx{smooth} takes an +optional argument; the structure of the command is so complex that the +simple \csx{let} command does not retain the necessary detail. In +this case, we need the \Package{letltxmacro} package which knows about all +sorts of \latex{} commands and how to replicate them. Suppose we have +a command defined as: +\begin{quote} +\begin{verbatim} +\newcommand{\rough}[1][\default]{...} +\end{verbatim} +\end{quote} +with an optional argument (substituted with \csx{default} if it's not +present) as well as an ordinary one. In this case we copy it using +\begin{quote} +\begin{verbatim} +\LetLtxMacro{\NewRough}{\rough} +\end{verbatim} +\end{quote} +and then repeat the technique we had above, with one extension: +\begin{quote} +\begin{verbatim} +\renewcommand{\rough}[1][\newdef]% + {\mumble\OldRough[{#1}]{#2}} +\end{verbatim} +\end{quote} +We see here that (for tedious argument-matching reasons) it is +necessary to provide braces arround the optional argument that is +being passed on. + The general case may be achieved in two ways. First, one can use the \LaTeX{} command \csx{CheckCommand}; this compares an existing command with the definition you give it, and issues a warning if two don't @@ -340,10 +370,12 @@ command thus amended. Unless you can't do your job any other way, \Package{patch} is best avoided. \begin{ctanrefs} \item[etoolbox.sty]\CTANref{etoolbox} +\item[letltxmacro.sty]Distributed as part of \CTANref{oberdiek}[letltxmacro] \item[patch.doc]\CTANref{patch} \item[patchcommand.sty]\CTANref{patchcmd} \item[ted.sty]\CTANref{ted} \end{ctanrefs} +\LastEdit{2011-06-29} \Question[Q-compjobnam]{Comparing the ``job name''} @@ -831,6 +863,8 @@ accurately. \item[keyval.sty]Distributed as part of \CTANref{graphics}[keyval] \end{ctanrefs} + * faq-mac-prog.tex (q-keyval): tweak words about getoptk + \Question[Q-keyval]{Key-value input for macros and package options} When we discussed % !line break @@ -841,10 +875,10 @@ position, aren't very kind to the user, and that a package such as consider the packages that the macro programmer might use, to create such a user interface. -The simplest key-value processor remains \Package{keyval}; it has a -command \csx{define@key} to declare a key and a \emph{handler} to -process it, and a macro \csx{setkeys} to offer values to the handler -of one or more keys. Thus: +The simplest key-value processor (for \latex{}, at least) remains +\Package{keyval}; it has a command \csx{define@key} to declare a key +and a \emph{handler} to process it, and a macro \csx{setkeys} to offer +values to the handler of one or more keys. Thus: \begin{quote} \begin{verbatim} \define@key{my}{foo}{Foo is #1\par} @@ -971,15 +1005,15 @@ isn't available with the other keys packages. However, there seems to be no mechanism for using \Package{pgfkeys} keys as part of the options of another package, in the way that \Package{kvoptions} does. -The \Package{expl3} programming layer for \Qref*{\LaTeX{}3}{Q-LaTeX3} +The \Package{l3kernel} programming layer for \Qref*{\LaTeX{}3}{Q-LaTeX3} includes the \Package{l3keys} module. Inspired by \Package{pgfkeys}, it provides a keyval-based method for the programmer to create keys. As with keyval and derivatives, \Package{l3keys} uses separate macros -for defining and setting keys. There is also a support package, -\Package{l3keys2e}, available to allow \LaTeXe{} package and class -options to be processed using \Package{l3keys}. The \Package{expl3} +for defining and setting keys. The package \Package{l3keys2e} makes +it possible for \latexe{} class and package +options to be processed using \Package{l3keys}. \Package{L3kernel} code can be used within existing LaTeX2e documents, so -\Package{l3keys} is available to the \LaTeXe{} programmer. +\Package{l3keys} is also available to the \latexe{} programmer `direct'. Another key-value system that's part of larger set of macros is \Package{scrbase}, which uses the facilities of \Package{keyval} to @@ -1003,16 +1037,46 @@ This brief summary was guided by input from two sources: a draft article for \textsl{TUGboat} by Joseph Wright, and the partial translation of the documentation of package \Package{scrbase} prepared by Philipp Stephani. + +All the above are (at least) aimed at \latex{} programming; there is +one package, \Package{getoptk}, aimed at the \plaintex{} programmer. +\Package{Getoptk} uses syntax inspired by that offered by \tex{} +primitives such as \csx{hrule} and \csx{hbox}, so we are offered +syntax such as: +\begin{wideversion} +\begin{quote} +\begin{verbatim} +\begindisplay file {chapter1} literal offset 20pt +\end{verbatim} +\end{quote} +(taken from the package manual). +\end{wideversion} +\begin{narrowversion} +\begin{quote} +\begin{verbatim} +\begindisplay file {chapter1} % + literal offset 20pt +\end{verbatim} +\end{quote} +(taken from the package manual, but wrapped to fit into narrow +columns). +\end{narrowversion} + +There are (we know) people who would swear that such syntax is +wonderful (the present author wouldn't), but the package earns its +place as the only stand-alone key-value macros that will work in \plaintex{}. \begin{ctanrefs} +\item[getoptk.tex]\CTANref{getoptk} \item[keyval.sty]Distributed as part of \CTANref{graphics}[keyval] \item[kvoptions.sty]Distributed as part of \CTANref{oberdiek}[kvoptions] \item[kvsetkeys.sty]Distributed as part of \CTANref{oberdiek}[kvsetkeys] -\item[l3keys.sty]Distributed as part of \CTANref{expl3} -\item[l3keys2e.sty]Distributed as part of \CTANref{xpackages} +\item[l3keys.sty]Distributed as part of \CTANref{l3kernel} +\item[l3keys2e.sty]Distributed as part of \CTANref{l3packages} \item[pgfkeys.sty]Distributed as part of \CTANref{pgf} \item[scrbase.sty]Distributed as part of \CTANref{koma-script} \item[xkeyval.sty]\CTANref{xkeyval} \end{ctanrefs} +\LastEdit{2011-09-06} \Question[Q-activechars]{Defining characters as macros} @@ -1774,7 +1838,7 @@ command. If you're using a fragment of a package or class, you may well feel confused: books such as the first edition of the % ! line break -\Qref*{The \LaTeX{} Companion}{Q-books} +\Qref*{The \LaTeX{} Companion}{Q-latex-books} are full of fragments of packages as examples for you to employ. The second edition of the \emph{Companion} makes clearer how you should use these fragments, and in addition, the code of @@ -1802,6 +1866,7 @@ that \LaTeX{} internal code is expected, which often looks `tidier'. \begin{ctanrefs} \item[\nothtml{\rmfamily}Examples from the Companion]\CTANref{tlc2} \end{ctanrefs} +\LastEdit{2011-06-01} \Question[Q-protect]{What's the reason for `protection'?} @@ -1813,7 +1878,7 @@ are all arguments that may go into table of contents, list of figures, read in later. Other places are those data that might appear in head- or footlines. Section headings and figure captions are the most prominent examples; there's a complete list in Lamport's book -(see \Qref[question]{\TeX{}-related books}{Q-books}). +(see \Qref[question]{\TeX{}-related books}{Q-latex-books}). What's going on really, behind the scenes? The commands in moving arguments are normally expanded to their internal structure during the @@ -1890,6 +1955,7 @@ a long-term aim of the team to remove all need for \csx{protect}ion. \item[makerobust.sty]Distributed as part of Heiko Oberdiek's bundle \CTANref{oberdiek}[makerobust] \end{ctanrefs} +\LastEdit{2011-06-01} \Question[Q-edef]{\csx{edef} does not work with \csx{protect}} @@ -2320,7 +2386,7 @@ abbreviation's \emph{name} and its \emph{value}, which provide most of what a user needs to know. The table also lists the abbreviation's \emph{type}, which is a trickier concept: if you need to know, the only real confusion is that the abbreviations labelled `defn' are -defined using an \csx{\emph{xxx}def} command. +defined using an \csx{\emph{xxxx}def} command. \begin{tabular}{lll} Name \tbamp Type \tbamp Value \tbeol @@ -3040,7 +3106,9 @@ the packages \Package{type1cm} (for \acro{CM} fonts) and If \Package{fix-cm} doesn't do the job for you, try one of the other two; \Package{fix-cm} has one or two omissions~--- fonts the \latex{} -team considered not useful, or something\dots{} +team did not consider useful, or something; the CM dunhill fonts (as +CM, but with stretched ascenders) and the CM fibonacci (which is only +available in 8-point design size) are certainly missing. A further alternative might be to switch to the \Qref*{\FontName{Latin} \FontName{Modern} fonts}{Q-uselmfonts} (which @@ -3056,6 +3124,7 @@ distribution, and don't therefore need any such trick as the above. the \CTANref{cm-super} distribution, but it works happily in the absence of the scaled fonts) \end{ctanrefs} +\LastEdit{2011-06-02} \Question[Q-latexqual]{The quality of your \LaTeX{}} @@ -3088,14 +3157,18 @@ Package nag Warning: Command \bf is an old \end{quote} \begin{wideversion} (the package provides a demo file which contains most of the sorts - of errors you might make~--- this is one of them). + of errors you might make~--- the example is one of them). \end{wideversion} \begin{narrowversion} - (the two error lines both wrapped above; the package provides a demo - file which contains most of the sorts of errors you might make~--- - this is one of them). + (the error lines above represent two lines which have been wrapped; + the package provides a demo file which contains most of the sorts of + errors you might make~--- the example is one of them). \end{narrowversion} +The \ProgName{lacheck} program analyses your source and comments on +it; its view of what is ``bad'' is \emph{very} subjective (the +documentation says), but it can be useful. + There's also a web site \href{http://www.kohm.name/markus/texidate.html}{TeXidate} which will do a static analysis of your document (unfortunately, you @@ -3106,6 +3179,7 @@ draconian. \begin{ctanrefs} \item[l2tabu]Browse \CTANref{l2tabu} for a copy in a language that's convenient for you +\item[lacheck]\CTANref{lacheck} \item[nag.sty]\CTANref{nag} \end{ctanrefs} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex index a5704253353..2a6ee5c0bc9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex @@ -1,4 +1,4 @@ -% $Id: faq-projects.tex,v 1.19 2011/04/13 09:45:46 rf10 Exp $ +% $Id: faq-projects.tex,v 1.24 2011/09/03 18:56:20 rf10 Exp rf10 $ \section{Current \TeX{}-related projects} @@ -26,10 +26,12 @@ on the project web site (\URL{http://www.latex-project.org/papers/}), as is some of the project's experimental code (see \URL{http://www.latex-project.org/code.html}, which allows you to read the project's source repository). Snapshots of two major collections -from the code, \Package{expl3} (supporting \LaTeX{}3 coding -conventions in a \LaTeXe{} environment) and and \Package{xpackages} (a -first cut of a ``document designer's interface'') are available on -\acro{CTAN}. \Package{Expl3} introduces a coding structure quite +from the code, \Package{l3kernel} (supporting \LaTeX{}3 coding +conventions in a \LaTeXe{} environment), \Package{l3packages} (a +first cut of a ``document designer's interface'') and +\Package{l3experimental} (new stuff that's still under development) +are all available on +\acro{CTAN}. \Package{L3kernel} introduces a coding structure quite different from earlier \latex{} code, but several authors are nevertheless using it in their development work. @@ -39,11 +41,12 @@ through the mailing list \texttt{latex-l}; some development work by sending a message `\texttt{subscribe latex-l <\emph{your name}>}' to \mailto{listserv@urz.Uni-Heidelberg.de} \begin{ctanrefs} -\item[expl3 \nothtml{\rmfamily}bundle]\CTANref{expl3} +\item[l3experimental \nothtml{\rmfamily}bundle]\CTANref{l3experimental} +\item[l3kernel \nothtml{\rmfamily}bundle]\CTANref{l3kernel} \item[\nothtml{\rmfamily}\LaTeX{} project publications]\CTANref{ltx3pub} -\item[xpackages \nothtml{\rmfamily}bundle]\CTANref{xpackages} +\item[l3packages \nothtml{\rmfamily}bundle]\CTANref{l3packages} \end{ctanrefs} -\LastEdit{2011-03-09} +\LastEdit{2011-08-30} \Question[Q-mathml]{Future \acro{WWW} technologies and \AllTeX{}} @@ -382,19 +385,21 @@ collection of other information is to be found in a set of % ! line break \Question[Q-luatex]{\PDFTeX{} and \LuaTeX{}} As is said elsewhere in these \acro{FAQ}s, development of -\Qref*{\PDFTeX{}}{Q-whatpdftex} is ``in essence'' complete~--- -no new facilities are being developed at the time of writing. The -\PDFTeX{} team has -announced that they have frozen \PDFTeX{} in its current state -(version 1.40.11), and that nothing but bug corrections will be -provided up to the time of the final release, \PDFTeX{} 1.50.0. +\Qref*{\PDFTeX{}}{Q-whatpdftex} is ``in essence'' complete~--- no new +facilities are being developed at the time of writing. The \PDFTeX{} +team has announced that they have frozen \PDFTeX{}'s specification in +its current state (version 1.40.11), and that nothing but bug +corrections will be provided up to the time of the final release, +\PDFTeX{} 1.50.0. (The interpretation of the statement seems to allow +sensible changes that are beyond any reasonable definition of +\emph{bug}\dots) In parallel with the running-down of \PDFTeX{} development, development of a new system, \LuaTeX{} is under way. \href{http://www.lua.org/}{\ProgName{Lua}} is a script language, designed to offer an interpreter that may be incorporated into other applications. \LuaTeX{} consists of a \TeX{}-like engine -with a \ProgName{lua} interpreter built into it; the \ProgName{lua} +with a \ProgName{lua} interpreter `embedded' in it; the \ProgName{lua} interpreter has access to many of the data structures used for typesetting, and the user may also interpolate chunks of \ProgName{lua} code into their \AllTeX{} macros, or as `call-backs' @@ -412,13 +417,13 @@ current projects have in their sights, notably Unicode character representations and support for OpenType fonts. The intention is to integrate the extensions pioneered by \Qref*{Aleph}{Q-omegaleph}. -The current version (Beta 0.60.1, in April 2010) of \LuaTeX{} is supposed -at least to demonstrate the final functionality. This stability was -declared with version 0.50.0, released near the end of December 2009. -Much work remains to be done, and this remains a beta-release. -\texlive{} 2009 incorporates (at the time of writing) \LuaTeX{} -version 0.44.0, but the latest \miktex{} (version 2.8) still doesn't -offer it. +The current released version (Beta 0.70.1, in June 2011) of \LuaTeX{} +is supposed at least to demonstrate the final functionality. This +stability was declared with version 0.50.0, released near the end of +December 2009. Much work remains to be done, and this remains a +beta-release. \texlive{} 2010 incorporates (at the time of writing) +\LuaTeX{} version 0.60.2, and current \miktex{} (version 2.9) +offers version 0.70.0. \CONTeXT{} `Mark 4' can already make use of \LuaTeX{}; much of its code already appears in two forms~--- a \TeX{}-based version @@ -430,6 +435,7 @@ re-implementations of existing \context{} code). \item[\nothtml{\rmfamily}\luatex{} snapshot]\CTANref{luatex} \item[\nothtml{\rmfamily}\pdftex{} distribution]\CTANref{pdftex} \end{ctanrefs} +\LastEdit{2011-07-10} \Question[Q-ant]{The \textsf{ANT} typesetting system} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-support.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-support.tex index e9ffd1e4417..b874e907e61 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-support.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-support.tex @@ -1,4 +1,4 @@ -% $Id: faq-support.tex,v 1.4 2011/05/04 06:40:43 rf10 Exp rf10 $ +% $Id: faq-support.tex,v 1.5 2011/05/08 10:16:43 rf10 Exp $ \section{Support Packages for \TeX{}} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex index 1a1cf1d9757..f12b9a0c254 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex @@ -1,4 +1,4 @@ -% $Id: faq-symbols.tex,v 1.9 2011/04/13 09:45:46 rf10 Exp $ +% $Id: faq-symbols.tex,v 1.11 2011/08/28 10:13:19 rf10 Exp rf10 $ \section{Symbols, etc.} @@ -221,8 +221,8 @@ catalogue entries. \item[eucal.sty]Distributed as part of \CTANref{amsfonts} \item[euler fonts]Distributed as part of \CTANref{amsfonts} \item[ghostscript]Browse \CTANref{ghostscript} -\item[mathabx]\CTANref{mathabx} -\item[mathabx \nothtml{rmfamily}in Type 1 format]\CTANref{mathabx-type1} +\item[mathabx \nothtml{\rmfamily}as \MF{}]\CTANref{mathabx} +\item[mathabx \nothtml{\rmfamily}in Type 1 format]\CTANref{mathabx-type1} \item[mathrsfs.sty]Distributed as part of \CTANref{jknappen-macros}[mathrsfs] \item[mnsymbol \nothtml{\rmfamily}fonts]\CTANref{mnsymbol} \item[rsfs \nothtml{\rmfamily}fonts]\CTANref{rsfs} @@ -231,7 +231,7 @@ catalogue entries. \item[urwchancal]\CTANref{urwchancal}[urwchancal] \item[URW Chancery L]Distributed as part of \CTANref{urw-base35} \end{ctanrefs} -\LastEdit{2011-03-30} +\LastEdit{2011-08-17} \Question[Q-boldgreek]{Setting bold Greek letters in \LaTeX{}} @@ -319,18 +319,26 @@ created by use of the following macros: \csx{dashint} gives a single-dashed integral sign, \csx{ddashint} a double-dashed one. -\Question[Q-underscore]{How to use the underscore character} +\Question[Q-underscore]{How to typeset an underscore character} -The underscore character `\texttt{\_}' is ordinarily used in -\TeX{} to indicate a subscript in maths mode; if you type -\texttt{\_}, on its own, in the course of ordinary text, \TeX{} will -complain. If you're writing a document which will contain a large -number of underscore characters, the prospect of typing -\csx{\_} (or, worse, \csx{textunderscore}) for every one of -them will daunt most ordinary people. +The underscore character `\texttt{\_}' is ordinarily used in \TeX{} to +indicate a subscript in maths mode; if you type \texttt{\_}, on its +own, in the course of ordinary text, \TeX{} will complain. The +``proper'' \latex{} command for underscore is \csx{textunderscore}, +but the \latexo{} command \csx{\_} is an established alias. Even so, +if you're writing a document which will contain a large number of +underscore characters, the prospect of typing \csx{\_} for every one +of them will daunt most ordinary people. Moderately skilled macro programmers can readily generate a quick hack -to permit typing `\texttt{\_}' to mean `text underscore'. +to permit typing `\texttt{\_}' to mean `text underscore' (the answer in +\begin{hyperversion} + ``\Qref{defining characters as macros}{Q-activechars}'' +\end{hyperversion} +\begin{flatversion} + \Qref[question]{}{Q-activechars} +\end{flatversion} +uses this example to illustrate its techniques). However, the code \emph{is} somewhat tricky, and more importantly there are significant points where it's easy to get it wrong. There is therefore a package \Package{underscore} which provides a general @@ -338,38 +346,50 @@ solution to this requirement. There is a problem, though: \acro{OT}1 text fonts don't contain an underscore character, unless they're in the typewriter version of the -encoding (used by fixed-width fonts such as \texttt{cmtt}). So either -you must ensure that your underscore characters only occur in text set -in a typewriter font, or you must use a more modern encoding, such as -\acro{T}1, which has the same layout for every font, and thus an -underscore in every font. - -If the requirement is only for occasional uses of underscores, it may -be acceptable to use the following construct: +encoding (used by fixed-width fonts such as \texttt{cmtt}). In place +of such a character, \latex{} (in \acro{OT}1 encoding) uses a short rule +for the command \csx{textunderscore}, but this poses problems +for systems that interpret \acro{PDF}~--- for example those +\acro{PDF}-to-voice systems used by those who find reading difficult. + +So either you must ensure that your underscore characters only occur +in text set in a typewriter font, or you must use a more modern +encoding, such as \acro{T}1, which has the same layout for every font, +and thus an underscore in every font. + +A stable procedure to achieve this is: \begin{quote} \begin{verbatim} -\def\us{\char`\_} -... -\texttt{create\us process} +% (1) choose a font that is available as T1 +% for example: +\usepackage{lmodern} + +% (2) specify encoding +\usepackage[T1]{fontenc} + +% (3) load symbol definitions +\usepackage{textcomp} \end{verbatim} \end{quote} -The construction isn't in the least robust (in the normal English -sense of the word), but it \emph{is} robust under expansion (i.e., the -\LaTeX{} sense of the word); so use it with care, but don't worry -about section headings and the like. +which will provide a command \csx{textunderscore} which robustly +selects the right character. The \Package{underscore} package, +mentioned above, will use this command. \begin{ctanrefs} \item[underscore.sty]\CTANref{underscore} \end{ctanrefs} +\LastEdit{2011-08-17} \Question[Q-atsign]{How to type an `@' sign?} -Long ago, some packages used to use the `@' sign as a command, so that -special measures were needed to type it. While those packages are -still in principle available, few people use them, and those that do -use them have ready access to rather good documentation. +Long ago, some packages used to use the `@' sign as a special +character, so that special measures were needed to type it. While +those packages are still in principle available, few people use them, +and those that do use them have ready access to rather good +documentation. Ordinary people (such as the author of this \acro{FAQ}) need only type `@'. +\LastEdit{2011-08-16} \Question[Q-euro]{Typesetting the Euro sign} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex index 730207665e1..0d033a2c319 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex @@ -1,4 +1,4 @@ -% $Id: faq-wdidt.tex,v 1.11 2011/03/09 21:02:45 rf10 Exp $ +% $Id: faq-wdidt.tex,v 1.12 2011/06/01 19:57:21 rf10 Exp rf10 $ \section{Why does it \emph{do} that?} @@ -303,7 +303,8 @@ so you've written (for example): \end{description} \end{verbatim} \end{quote} -|\|{}|\| is actually a rather bad command to use in this case (even if +% ridiculous coding for sanitize.pl -- careful! +\bsbs {} is actually a rather bad command to use in this case (even if it worked), since it would force the `paragraph' that's made up of the text of the item to terminate a line which has nothing on it but the label. This would lead to an ``|Underfull \hbox|'' warning message @@ -314,9 +315,9 @@ purpose. The proper solution to the problem is to write a new sort of \environment{description} environment, that does just what you're after. (The -\nothtml{\emph{\LaTeX{} Companion}~--- see }% ! line wrap -\Qref[question]{\emph{\LaTeX{} Companion}}{Q-books}\nothtml{~---} offers a -rather wide selection of variants of these things.) +\nothtml{\emph{\LaTeX{} Companion}~--- see }% ! line wrap, and next line +\Qref[question]{\emph{\LaTeX{} Companion}}{Q-latex-books}\nothtml{~---} +offers a rather wide selection of variants of these things.) The quick-and-easy solution, which avoids the warning, is to write: \begin{quote} @@ -362,6 +363,7 @@ be had by saying: \item[expdlist.sty]\CTANref{expdlist} \item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}[mdwlist] \end{ctanrefs} +\LastEdit{2011-06-01} % other instances: \[no]linebreak in vertical mode diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq.sty b/Master/texmf-dist/doc/generic/FAQ-en/faq.sty index 7a562c4e25d..8cb9690d2c4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq.sty +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq.sty @@ -1,4 +1,4 @@ -% $Id: faq.sty,v 1.129 2011/03/12 09:24:22 rf10 Exp $ +% $Id: faq.sty,v 1.131 2011/08/28 10:13:19 rf10 Exp rf10 $ % % This is the LaTeX package that deals with the eccentricities of mark % up of the UK TeX FAQ. @@ -164,13 +164,15 @@ \let\textlogo\textmd % % define substitutes for stupid_names -\newcommand\LaTeXo{\LaTeX\,2.09} +\newcommand\LaTeXo{\latex\,2.09} + \newcommand\latexo{\latex\,2.09} \newcommand\AMSTeX{AMS\TeX} -\newcommand\AMSLaTeX{AMS\LaTeX} +\newcommand\AMSLaTeX{AMS\latex} + \newcommand\amslatex{AMS\latex} \newcommand\BibTeX{Bib\TeX} -\newcommand\bibtex{Bib\TeX} + \newcommand\bibtex{Bib\TeX} \newcommand\PiCTeX{PiC\TeX} -\newcommand\texlive{\TeX{} Live} + \newcommand\texlive{\TeX{} Live} % and... % % ifthenelse for the undefined references diff --git a/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex b/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex index 9c44ef3da25..40366d463eb 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex @@ -1,4 +1,4 @@ -% $Id: filectan.tex,v 1.135 2011/03/17 10:23:19 rf10 Exp rf10 $ +% $Id: filectan.tex,v 1.138 2011/07/21 19:16:13 rf10 Exp rf10 $ % % protect ourself against being read twice \csname readCTANfiles\endcsname @@ -58,7 +58,7 @@ \CTANfile{mathscript}{info/symbols/math/scriptfonts.pdf} \CTANfile{mathsurvey.html}{info/Free_Math_Font_Survey/en/survey.html} \CTANfile{mathsurvey.pdf}{info/Free_Math_Font_Survey/en/survey.pdf} -\CTANfile{metafp-pdf}{info/metafont/metafp/metafp.pdf} +\CTANfile{metafp-pdf}{info/metafont/metafp/metafp.pdf}[metafp] \CTANfile{mf-beginners}{info/metafont/beginners/metafont-for-beginners.pdf}[metafont-beginners] \CTANfile{mf-list}{info/metafont-list} \CTANfile{miktex-portable}{systems/win32/miktex/setup/miktex-portable.exe} @@ -80,7 +80,6 @@ \CTANfile{removefr}{macros/latex/contrib/fragments/removefr.tex}[removefr] \CTANfile{resume}{obsolete/macros/latex209/contrib/resume/resume.sty} \CTANfile{savesym}{macros/latex/contrib/savesym/savesym.sty}[savesym] -\CTANfile{screensty}{macros/latex209/contrib/misc/screen.sty}[screen] \CTANfile{selectp}{macros/latex/contrib/misc/selectp.sty}[selectp] \CTANfile{setspace}{macros/latex/contrib/setspace/setspace.sty}[setspace] \CTANfile{simpl-latex}{info/simplified-latex/simplified-intro.pdf}[simplified-latex] @@ -103,7 +102,7 @@ \CTANfile{varwidth}{macros/latex/contrib/misc/varwidth.sty}[varwidth] \CTANfile{version}{macros/latex/contrib/misc/version.sty}[version] \CTANfile{versions}{macros/latex/contrib/versions/versions.sty}[versions] -\CTANfile{vf-howto}{info/virtualfontshowto/virtualfontshowto.txt} +\CTANfile{vf-howto}{info/virtualfontshowto/virtualfontshowto.txt}[vf-howto] \CTANfile{vf-knuth}{info/knuth/virtual-fonts}[vf-knuth] \CTANfile{visualFAQ}{info/visualFAQ/visualFAQ.pdf}[visualfaq] \CTANfile{voss-mathmode}{info/math/voss/mathmode/Mathmode.pdf} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex b/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex index ae1d03d3473..5febe506021 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex @@ -1,4 +1,4 @@ -\def\faqfileversion{3.22} \def\faqfiledate{2011-04-27} +\def\faqfileversion{3.23} \def\faqfiledate{2011-09-06} % % The above line defines the file version and date, and must remain % the first line with any `assignment' in the file, or things will diff --git a/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf b/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf Binary files differindex 8499988d1cb..92069cb2b0e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf +++ b/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf diff --git a/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf Binary files differindex 8c9ee0cb079..ca9d685bafa 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf +++ b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf diff --git a/Master/texmf-dist/doc/generic/FAQ-en/newfaq.workers b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.workers deleted file mode 100644 index 2781140734d..00000000000 --- a/Master/texmf-dist/doc/generic/FAQ-en/newfaq.workers +++ /dev/null @@ -1,5 +0,0 @@ -This file contains (will contain) a list of people working on the new -FAQ, and of the questions they're working on. - -Mail rf10@cam.ac.uk to book a question, thus avoiding wasted effort. - |