From 3f1971c9b7717818766692c9aa497e20e7472f2c Mon Sep 17 00:00:00 2001
From: Karl Berry
Date: Wed, 7 Apr 2010 22:47:28 +0000
Subject: FAQ-en 3.19d (7apr10)
git-svn-id: svn://tug.org/texlive/trunk@17742 c570f23f-e606-0410-a88d-b1316a301751
---
Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.19d | 34 +++
Master/texmf-dist/doc/generic/FAQ-en/ChangeLog | 225 ++++++++++++++++
Master/texmf-dist/doc/generic/FAQ-en/Makefile | 7 +-
Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex | 33 ++-
.../doc/generic/FAQ-en/faq-adj-types.tex | 145 +++++++---
.../texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex | 77 ++++--
.../texmf-dist/doc/generic/FAQ-en/faq-biblio.tex | 6 +-
Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex | 4 +-
Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex | 2 +-
.../texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex | 2 +-
Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex | 6 +-
Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex | 2 +-
.../texmf-dist/doc/generic/FAQ-en/faq-graphics.tex | 7 +-
.../texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex | 155 +++++------
.../texmf-dist/doc/generic/FAQ-en/faq-install.tex | 2 +-
Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex | 55 ++--
.../texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex | 15 +-
.../texmf-dist/doc/generic/FAQ-en/faq-lab-ref.tex | 10 +-
.../texmf-dist/doc/generic/FAQ-en/faq-litprog.tex | 2 +-
.../texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex | 129 ++++-----
.../texmf-dist/doc/generic/FAQ-en/faq-projects.tex | 11 +-
.../texmf-dist/doc/generic/FAQ-en/faq-symbols.tex | 10 +-
.../texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex | 6 +-
.../texmf-dist/doc/generic/FAQ-en/faq-texsys.tex | 8 +-
.../texmf-dist/doc/generic/FAQ-en/faq-the-end.tex | 2 +-
Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex | 8 +-
Master/texmf-dist/doc/generic/FAQ-en/faq.sty | 12 +-
Master/texmf-dist/doc/generic/FAQ-en/filectan.tex | 22 +-
.../doc/generic/FAQ-en/gather-faqbody.tex | 2 +-
.../doc/generic/FAQ-en/html/FAQ-2colfloat.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-2colfltorder.html | 12 +-
.../generic/FAQ-en/html/FAQ-2letterfontcmd.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-8000.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-AMSpkg.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-BibTeXing.html | 10 +-
.../texmf-dist/doc/generic/FAQ-en/html/FAQ-CD.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-ECfonts.html | 30 +--
.../doc/generic/FAQ-en/html/FAQ-HPdrivers.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-LaTeX3.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-LaTeXandPlain.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-LaTeXtoPlain.html | 8 +-
.../texmf-dist/doc/generic/FAQ-en/html/FAQ-MF.html | 6 +-
.../texmf-dist/doc/generic/FAQ-en/html/FAQ-MP.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-PSpreview.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-RCS.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-SGML2TeX.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-TUGstar.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-TeXfuture.html | 21 +-
.../doc/generic/FAQ-en/html/FAQ-TeXpronounce.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-TeXsystems.html | 34 +--
.../doc/generic/FAQ-en/html/FAQ-WYGexpts.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-abspos.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-acroantics.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-acrobat.html | 26 +-
.../doc/generic/FAQ-en/html/FAQ-actinarg.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-activechars.html | 57 ++--
.../doc/generic/FAQ-en/html/FAQ-addtoreset.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-adobetypen.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-algorithms.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-alreadydef.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-altabcr.html | 28 +-
.../doc/generic/FAQ-en/html/FAQ-amfonts.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-ant.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-appendix.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-archives.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-askquestion.html | 46 ++--
.../doc/generic/FAQ-en/html/FAQ-atsign.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-atsigns.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-atvert.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-backref.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-badhyph.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-balance.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-baselinepar.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-bibaccent.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-bibinline.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-biblatex.html | 30 +--
.../doc/generic/FAQ-en/html/FAQ-bibprefixsort.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-bibstrtl.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-bibtocorder.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-bibtranscinit.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-bold-extras.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-boldgreek.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-books.html | 44 +--
.../doc/generic/FAQ-en/html/FAQ-braket.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-breakbox.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-breaklinks.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-brkinline.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-buffovl.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-bug.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-buildbib.html | 26 +-
.../doc/generic/FAQ-en/html/FAQ-cancellation.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-capbibtex.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-captsty.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-casechange.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-changebars.html | 28 +-
.../doc/generic/FAQ-en/html/FAQ-changemargin.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-chapbib.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-charshift.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-checksum.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-chngmargonfly.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-citeURL.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-citesort.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-clsvpkg.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-cmdstar.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-codelist.html | 19 +-
.../doc/generic/FAQ-en/html/FAQ-commercial.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-compactbib.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-compjobnam.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-complist.html | 36 +--
.../doc/generic/FAQ-en/html/FAQ-concrete.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-conditional.html | 56 ++--
.../doc/generic/FAQ-en/html/FAQ-context.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-crop.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-csname.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-custbib.html | 8 +-
.../texmf-dist/doc/generic/FAQ-en/html/FAQ-cv.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-cvtlatex.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-dec_comma.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-destable.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-distill-prob.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-divzero.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-doc-dirs.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-doc-wiki.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-docotherdir.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-dolldoll.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-dpfloat.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-drawFeyn.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-drawing.html | 26 +-
.../doc/generic/FAQ-en/html/FAQ-driver.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-dropping.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-dtx.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-dvi-bmp.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-dvi.html | 8 +-
.../generic/FAQ-en/html/FAQ-dvipdfmgraphics.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-dvips-pdf.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-dvips.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-dvipsgraphics.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-edef.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-editors.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-empty.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-emptynum.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-endingroup.html | 34 +--
.../doc/generic/FAQ-en/html/FAQ-enlarge.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-entercompmode.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-enumerate.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-epigraph.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-eplain.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-eps.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-epsf.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-eqnarray.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-errmissitem.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-erroradvice.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-errparnum.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-errstruct.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-etex.html | 11 +-
.../doc/generic/FAQ-en/html/FAQ-euro.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-exscale.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-extex.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-extrabrace.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-extref.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-extsizes.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-fancyhdr.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-figurehere.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-filename.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-filesused.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-findfiles.html | 26 +-
.../doc/generic/FAQ-en/html/FAQ-findfont.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-findwidth.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-fixnam.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-fixwidtab.html | 28 +-
.../doc/generic/FAQ-en/html/FAQ-fllost.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-floatpages.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-floats.html | 44 +--
.../doc/generic/FAQ-en/html/FAQ-flushboth.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-fmtconv.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-fontname.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-fonts-pln.html | 38 +--
.../doc/generic/FAQ-en/html/FAQ-fontsize.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-fontunavail.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-footintab.html | 40 +--
.../doc/generic/FAQ-en/html/FAQ-footnpp.html | 29 +-
.../doc/generic/FAQ-en/html/FAQ-formatstymy.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-formbiblabel.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-ftncapt.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-ftnsect.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-fuzzy-T1.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-fuzzy-gs.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-fuzzy-type3.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-getbitmap.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-gethelp.html | 30 +--
.../doc/generic/FAQ-en/html/FAQ-graph-pspdf.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-graphicspath.html | 34 +--
.../doc/generic/FAQ-en/html/FAQ-grffilenames.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-grmaxwidth.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-gutter.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-hash.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-howmanypp.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-htmlbib.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-hyper.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-hyperdupdest.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-hyphen.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-hyphenaccents.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-hyphexcept.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-hyphoff.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-i18nbib.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-ifpdf.html | 27 +-
.../doc/generic/FAQ-en/html/FAQ-impgraph.html | 39 ++-
.../doc/generic/FAQ-en/html/FAQ-inclplain.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-include.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-inputlev.html | 2 +-
.../generic/FAQ-en/html/FAQ-inst-miktexstar.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-inst-tds-zip.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-inst-tidy.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-inst-wlcf.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-inst1cm.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-install-doc.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-install-find.html | 8 +-
.../generic/FAQ-en/html/FAQ-install-unpack.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-install-where.html | 44 +--
.../doc/generic/FAQ-en/html/FAQ-installthings.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-instfont.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-instmffont.html | 8 +-
.../generic/FAQ-en/html/FAQ-instprinterfont.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-instt1font.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-interruptlist.html | 48 ++--
.../doc/generic/FAQ-en/html/FAQ-isdef.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-isitanum.html | 44 +--
.../doc/generic/FAQ-en/html/FAQ-journalpaper.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-keepfonts.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-keyval.html | 62 ++---
.../doc/generic/FAQ-en/html/FAQ-labelctr.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-labelfig.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-labelformat.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-labundef.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-landscape.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-latex.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-latex2e.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-latexbug.html | 22 +-
.../generic/FAQ-en/html/FAQ-latexpronounce.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-latexqual.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-latexwords.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-letterclass.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-letterspace.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-limits.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-linenos.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-linespace.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-linespread.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-linmacnames.html | 40 +--
.../doc/generic/FAQ-en/html/FAQ-lit.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-logos.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-lollipop.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-longtab.html | 38 +--
.../doc/generic/FAQ-en/html/FAQ-ltxabbrv.html | 26 +-
.../doc/generic/FAQ-en/html/FAQ-ltxcmds.html | 44 +--
.../doc/generic/FAQ-en/html/FAQ-ltxhash.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-luatex.html | 23 +-
.../doc/generic/FAQ-en/html/FAQ-mailliststar.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-make.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-makebib.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-makeindex.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-man-latex.html | 44 +--
.../doc/generic/FAQ-en/html/FAQ-man-tex.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-manyauthor.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-manymathalph.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-marginmanual.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-marginparside.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-marginpkgs.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-matchbrak.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-mathlips.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-mathml.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-mathonlyref.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-mathsize.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-mathstext.html | 41 ++-
.../doc/generic/FAQ-en/html/FAQ-mcfloat.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-mcite.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-metrics.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-mfptutorials.html | 28 +-
.../doc/generic/FAQ-en/html/FAQ-minitoc.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-minxampl.html | 38 +--
.../doc/generic/FAQ-en/html/FAQ-missbegdoc.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-misschar.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-misssymb.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-moren9.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-mpprologues.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-msxy.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-multbib.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-multfoot.html | 3 +-
.../doc/generic/FAQ-en/html/FAQ-multidoc.html | 85 ++++--
.../doc/generic/FAQ-en/html/FAQ-multind.html | 28 +-
.../doc/generic/FAQ-en/html/FAQ-multirow.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-music.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-nameref.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-newans.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-newfontstar.html | 26 +-
.../doc/generic/FAQ-en/html/FAQ-newfunction.html | 11 +-
.../doc/generic/FAQ-en/html/FAQ-newlang.html | 38 +--
.../doc/generic/FAQ-en/html/FAQ-newlineargs.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-noans.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-nocitestar.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-nodollar.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-nofm.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-nohyph.html | 36 +--
.../doc/generic/FAQ-en/html/FAQ-noline.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-nonfree.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-nonpdfsp.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-nonum.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-nopagebrk.html | 28 +-
.../doc/generic/FAQ-en/html/FAQ-nopageno.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-noroom.html | 26 +-
.../doc/generic/FAQ-en/html/FAQ-notWYSIWYG.html | 34 +--
.../doc/generic/FAQ-en/html/FAQ-numbersets.html | 30 +--
.../doc/generic/FAQ-en/html/FAQ-oarglikesect.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-oddhyphen.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-oddpage.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-ol-books.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-oldfontnames.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-omegaleph.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-onecolabs.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-optionclash.html | 30 +--
.../doc/generic/FAQ-en/html/FAQ-osf.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-otherprinters.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-ouparmd.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-overfull.html | 80 +++---
.../doc/generic/FAQ-en/html/FAQ-overstrike.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-pagebychap.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-papergeom.html | 32 +--
.../doc/generic/FAQ-en/html/FAQ-papersize.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-parallel.html | 29 +-
.../doc/generic/FAQ-en/html/FAQ-paraparam.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-parskip.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-patch.html | 28 +-
.../doc/generic/FAQ-en/html/FAQ-pdf-fig-chars.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-pdfpagelabels.html | 18 +-
.../generic/FAQ-en/html/FAQ-pdftexgraphics.html | 36 +--
.../doc/generic/FAQ-en/html/FAQ-pkfix.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-pkgdoc.html | 26 +-
.../doc/generic/FAQ-en/html/FAQ-plaintex.html | 19 ++
.../doc/generic/FAQ-en/html/FAQ-plainvltx.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-plninltxstar.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-poster.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-prept1font.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-previewers.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-prinvalint.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-privinst.html | 34 +--
.../doc/generic/FAQ-en/html/FAQ-proof.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-protect.html | 30 +--
.../doc/generic/FAQ-en/html/FAQ-psfchoice.html | 78 +++---
.../doc/generic/FAQ-en/html/FAQ-psfontprob.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-ragright.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-readML.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-readtex.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-reallyblank.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-recovertex.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-ref-doc.html | 26 +-
.../doc/generic/FAQ-en/html/FAQ-repeatgrf.html | 30 +--
.../doc/generic/FAQ-en/html/FAQ-repfootnote.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-replstdcls.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-rerun.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-resolns.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-reuseq.html | 7 +-
.../doc/generic/FAQ-en/html/FAQ-rulethk.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-run-fn-nos.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-runheadtoobig.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-running-nos.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-scriptfonts.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-seccntfmt.html | 55 ++--
.../doc/generic/FAQ-en/html/FAQ-secindent.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-secnumdep.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-secthead.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-semanticnest.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-setURL.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-slashbox.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-slidecls.html | 28 +-
.../doc/generic/FAQ-en/html/FAQ-sortbib.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-spaftend.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-specials.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-spell.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-spinmacro.html | 36 +--
.../doc/generic/FAQ-en/html/FAQ-splitfoot.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-srchpdf.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-struttab.html | 30 +--
.../doc/generic/FAQ-en/html/FAQ-subsubsub.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-subverttoks.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-symbols.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-t1enc.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-tabacc.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-tabcellalign.html | 31 +--
.../doc/generic/FAQ-en/html/FAQ-tds-zip.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-tds.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-tempinst.html | 34 +--
.../doc/generic/FAQ-en/html/FAQ-texinfo.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-texorpdf.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-textflow.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-texthings.html | 40 +--
.../doc/generic/FAQ-en/html/FAQ-textrace.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-tfm.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-the-commands.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-theoremfmt.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-thesis.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-time.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-titlsty.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-tmupfl.html | 26 +-
.../doc/generic/FAQ-en/html/FAQ-toascii.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-tocbibind.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-tocloft.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-tocloftwrong.html | 2 +-
.../doc/generic/FAQ-en/html/FAQ-toodeep.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-topgraph.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-tradesyms.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-triptrap.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-tutbitslatex.html | 48 ++--
.../doc/generic/FAQ-en/html/FAQ-tutorialstar.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-twooptarg.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-type1T1.html | 48 ++--
.../doc/generic/FAQ-en/html/FAQ-typebooks.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-typend.html | 32 +--
.../doc/generic/FAQ-en/html/FAQ-typo-style.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-underline.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-underscore.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-unkgrfextn.html | 21 +-
.../doc/generic/FAQ-en/html/FAQ-uploads.html | 30 +--
.../doc/generic/FAQ-en/html/FAQ-upquot.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-useMF.html | 44 +--
.../doc/generic/FAQ-en/html/FAQ-usebibtex.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-uselmfonts.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-usepictex.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-usepsfont.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-usesymb.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-varwidcol.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-varwidth.html | 16 +-
.../doc/generic/FAQ-en/html/FAQ-verbfile.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-verbwithin.html | 56 ++--
.../doc/generic/FAQ-en/html/FAQ-vertposfp.html | 6 +-
.../generic/FAQ-en/html/FAQ-vertspacefloat.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-virtualfonts.html | 18 +-
.../doc/generic/FAQ-en/html/FAQ-watermark.html | 34 ++-
.../doc/generic/FAQ-en/html/FAQ-wdnohyph.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-webpkgs.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-weirdhyphen.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-what-TDS.html | 48 ++--
.../doc/generic/FAQ-en/html/FAQ-whatTeX.html | 42 +--
.../doc/generic/FAQ-en/html/FAQ-whatbst.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-whatenc.html | 32 +--
.../doc/generic/FAQ-en/html/FAQ-whatmacros.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-whatpdftex.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-whereFAQ.html | 14 +-
.../doc/generic/FAQ-en/html/FAQ-wholerow.html | 12 +-
.../doc/generic/FAQ-en/html/FAQ-why-inp-font.html | 22 +-
.../doc/generic/FAQ-en/html/FAQ-whyfree.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-widefigs.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-wideflt.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-widows.html | 20 +-
.../doc/generic/FAQ-en/html/FAQ-wordcount.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-writecls.html | 8 +-
.../doc/generic/FAQ-en/html/FAQ-wrongpn.html | 10 +-
.../doc/generic/FAQ-en/html/FAQ-xfigetc.html | 6 +-
.../doc/generic/FAQ-en/html/FAQ-xspace.html | 24 +-
.../doc/generic/FAQ-en/html/FAQ-y2k.html | 4 +-
.../doc/generic/FAQ-en/html/FAQ-zerochap.html | 12 +-
.../texmf-dist/doc/generic/FAQ-en/html/index.html | 299 +++++++--------------
Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf | Bin 3649477 -> 3654575 bytes
Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf | Bin 3558874 -> 3563675 bytes
463 files changed, 4398 insertions(+), 4048 deletions(-)
create mode 100644 Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.19d
create mode 100644 Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plaintex.html
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.19d b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.19d
new file mode 100644
index 00000000000..f447a03924f
--- /dev/null
+++ b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.19d
@@ -0,0 +1,34 @@
+Changes in version 3.19d
+
+This file lists changes since its most recent release (with version 3.19c
+of the FAQ).
+
+New answers:
+ +Label plaintex: explains "writing in tex", was part of Label whattex
+
+Relabelled answers:
+
+
+Revised answers:
+ +Label codelist: mention the minted package
+ +Label docs: single reference to epslatex (via catalogue)
+ +Label etex: add ctan link
+ +Label filesused: rewrite to clarify the issue with \input
+ +Label luatex: now version 0.60.0
+ +Label fonts-pln: replace some complete gibberish (undoing mis-edits, I guess)
+ +Label parallel: mention the pdfcolparcolumns package
+ +Label seccntfmt: remove superfluous \expandafter in programming, tidy text
+ +Label tabcellalign: editorial on \PBS macro discussion
+ +Label texfuture: rehashed, in light of today's situation
+ +Label whattex: simplified by removal of material for Label plaintex
+
+Deleted answers:
+
+
+Web interface:
+ Extension of links to catalogue, to packages "distributed as part of..."
+ Abbreviate header text (omitting long list of "helpers" -- which will
+ ultimately be available in a separate file online)
+ Convert all alphabetic SGML entities to use numeric equivalents
+
+Robin Fairbairns
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog b/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog
index 2f5e03f7698..5f199c96636 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog
+++ b/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog
@@ -1,3 +1,228 @@
+2010-04-06 Robin Fairbairns
+
+ * sanitize-beta.pl (sanitize_line): massive shambles in [lr]brace
+
+ * faq-mac-prog.tex (subsection{"Generic" macros and techniques}):
+ correct ref to shortvrb in ctanrefs of q-activechars, and tidy
+ verbatim stuff in 2nd para of answer
+
+2010-04-05 Robin Fairbairns
+
+ * faq-adj-types.tex (subsection{Alternative document classes}): add
+ example structures for combine and subfiles alternatives in q-multidoc
+
+2010-04-04 Robin Fairbairns
+
+ * faq-projects.tex (section{Current TeX-related projects}): accommodate
+ luatex 0.60.0 in scribble about luatex
+
+2010-04-02 Robin Fairbairns
+
+ * gather-faqbody.tex: v3.19d, today (to be revised ;-)
+
+ * faq-intro.tex: omit unnecessary stuff in html mode (looks a bit bare
+ now, but ought to improve if/when i can sort out a css for the output)
+
+2010-04-01 Robin Fairbairns
+
+ * faq-intro.tex: minute delta-comment in list of helpers
+
+ * faq-how-do-i.tex: correct typo in q-hyphoff
+
+2010-03-26 Robin Fairbairns
+
+ * faq-graphics.tex,faq-biblio.tex,faq-lab-ref.tex,faq-how-do-i.tex,
+ faq-symbols.tex,faq-mac-prog.tex,faq-t-g-wr.tex,faq-wdidt.tex,
+ faq-jot-err.tex,faq-projects.tex (throughout): add individual cat
+ links for "distributed as part of" ctanrefs
+
+2010-03-24 Robin Fairbairns
+
+ * faq-fonts.tex (Macros for using fonts): editorial on some rubbish in
+ q-fonts-pln
+
+2010-03-23 Robin Fairbairns
+
+ * faq-adj-types.tex (Page Layout): mention pdfcolparcolumns in
+ q-parallel
+ (throughout): add individual cat links for "as part of" ctanrefs
+
+ * dirctan.tex: add minted
+
+ * faq-adj-types.tex (Typesetting specialities): add minted in q-codelist
+
+ * sanitize-beta.pl (sanitize_line): add flatversion in the $ignoring
+ twiddling at the end
+
+ * faq.sty: add flatversion env (== non-hyperversion)
+
+2010-03-22 Robin Fairbairns
+
+ * dirctan.tex: add vruler
+
+ * filectan.tex: remove vruler
+
+ * faq-adj-types.tex (Page Layout): editorial in q-parallel, add own cat
+ entry for pdfcolparallel
+
+2010-03-18 Robin Fairbairns
+
+ * dirctan.tex: add fncylab, ifmtarg, import (hypernat was here already)
+
+ * filectan.tex: remove fncylab, hypernat, ifmtarg, import
+
+2010-03-15 Robin Fairbairns
+
+ * faq-docs.tex: epslatex one ref only, now, relying on catalogue
+
+ * sanitize-beta.pl (generate_CTAN_ref, etc.): generate per reference
+ catalogue entries if opt argument of \CTANref
+
+ * dirctan.tex: add cat link for everypage
+
+ * faq-texsys.tex: editorial to avoid multiple \ctanref per line
+
+ * faq-graphics.tex: single reference to epslatex (doc from catalogue)
+
+ * filectan.tex: remove epslatex_(ps|pdf)
+
+ * dirctan.tex: add epslatex
+
+ * faq.sty: have \CTANref check for following optional argument (and
+ ignore it)
+
+ * faq-adj-types.tex: mention atbegshi in q-watermark
+
+2010-03-10 Robin Fairbairns
+
+ * dirctan.tex: add framed, verbdef (despite believing it already done!)
+
+ * faq-biblio.tex (subsection{Creating citations}): qualify ctanref for
+ chapterbib in q-chapbib
+
+2010-03-08 Robin Fairbairns
+
+ * dirctan.tex: add threeparttable
+ correct directory for bigstrut (it's multirow)
+
+ * filectan.tex: remove threeparttable
+
+2010-03-02 Robin Fairbairns
+
+ * faq-how-do-i.tex (subsection{Document management}): try to clear
+ ambiguity about \input in q-filesused
+
+ * Makefile: make "index" opt come out in help
+
+ * dirctan.tex: add framed, verbdef dirs
+
+ * filectan.tex: removed framed, verbdef
+
+2010-02-28 Robin Fairbairns
+
+ * filectan.tex: remove excludeonly
+
+ * dirctan.tex: add bigstrut, excludeonly
+
+ * faq-how-do-i.tex (subsection{Tables, figures and diagrams}): remark
+ about docs of tabls and bigstrut now not needed; bigstrut now has own
+ registered directory
+
+2010-02-27 Robin Fairbairns
+
+ * dirctan.tex: add tabls qua directory
+
+ * filectan.tex: remove tabls
+
+2010-02-26 Robin Fairbairns
+
+ * faq-how-do-i.tex (subsection{Tables, figures and diagrams}): correct
+ incompletely edited reference to \PBS in q-tabcellalign
+
+2010-02-24 Robin Fairbairns
+
+ * Makefile: add web-index target to updated (dir|file)ctan for when
+ ctan structure is changing
+
+2010-02-23 Robin Fairbairns
+
+ * faq-how-do-i.tex (subsection{Floating tables, figures, etc.}): remove
+ mention of docs of dpfloat
+
+ * faq-wdidt.tex (subsection{Common errors}): use fix2col package
+ direct, rather than ref to carlisle bundle
+
+ * filectan.tex: remove anonchap, bold-extra, braket, cancel, chngcntr,
+ dblfloatfix
+
+ * dirctan.tex: add anonchap, bold-extra, braket, cancel, chngcntr,
+ fix2col, dblfloatfix
+
+2010-02-18 Robin Fairbairns
+
+ * faq-intro.tex (section improvement; general typos): add enrico
+ gregorio (help with q-seccntfmt)
+
+ * faq-mac-prog.tex (subsection{LaTeX macro programming}): redo
+ switching code in q-seccntfmt
+
+2010-02-12 Robin Fairbairns
+
+ * texfaq2html-beta: convert (rather smaller number of) entities
+
+ * sanitize-beta.pl (sanitize_line): convert all alphabetic entities to
+ numerical entities
+
+2010-02-08 Robin Fairbairns
+
+ * faq-backgrnd.tex (section{The Background}): rehash q-texfuture, as
+ suggested by karl berry
+
+2010-02-07 Robin Fairbairns
+
+ * sanitize-beta.pl (sanitize_line): scrunge hyperversion
+
+ * faq.sty: add a hyperversion env
+
+ * dirctan.tex: add knuth-dist
+
+ * faq-backgrnd.tex (section{The Background}): split q-plaintex from
+ q-whattex (controversial?)
+
+ * filectan.tex: add knuth-tds
+
+2010-02-05 Robin Fairbairns
+
+ * faq-backgrnd.tex (section{The Background}): add ctan link in q-etex
+
+ * dirctan.tex: add etex
+
+2010-02-05 Robin Fairbairns
+
+ * texfaq2html-beta: an even more abstruse grep command for registering
+ labels than was the old for registering question nos (do we really
+ need to convert + to space? are user-generated questions significant?
+ -- because if not there never will be "xxx + yyy")
+
+2010-02-03 Robin Fairbairns
+
+ * dirctan.tex: add ulem "stand-alone"
+
+ * filectan.tex: remove ulem
+
+2010-02-02 Robin Fairbairns
+
+ * faq-mac-prog.tex (subsection{LaTeX macro programming}): remove
+ superflous \expandafter in q-seccntfmt, and tidy text a bit
+
+2010-02-02 Robin Fairbairns
+
+ * add-general.tex (subsection{"Generic" macros and techniques}): move
+ q-ovwtsym and q-long-outer to start of text
+ add q-detknize
+
+RELEASE 3.19c
+
2010-01-26 Robin Fairbairns
* mk-makefile: deal with CHANGES files
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/Makefile b/Master/texmf-dist/doc/generic/FAQ-en/Makefile
index c261a5f276a..717708568a3 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/Makefile
+++ b/Master/texmf-dist/doc/generic/FAQ-en/Makefile
@@ -29,7 +29,8 @@ CTAN_HOME = help/uk-tex-faq
#h web install files required for web access
#h (must be run on the machine that hosts
#h the CGI script)
-#h web-beta ditto, except beta distribution
+#h web-index web access files, just (dir|file)ctan
+#h web-beta as web, except beta distribution
#h
#h inst-perl install texfaq2html and sanitize.pl
#h in the cgi-bin directory
@@ -149,6 +150,8 @@ faqbody.tex: $(SUBDOCS) gather-faqbody.tex
web: $(WEB)/dirctan.tex $(WEB)/filectan.tex $(WEB)/faqbody.tex $(WEB)/newfaq.aux $(WEB)/archive.list
+web-index: $(WEB)/dirctan.tex $(WEB)/filectan.tex
+
$(WEB)/dirctan.tex: dirctan.tex
$(WEB)/filectan.tex: filectan.tex
$(WEB)/faqbody.tex: faqbody.tex
@@ -212,7 +215,7 @@ html-tar: html
html-gamma: $(HTMLDIR_GAMMA)/index.html
-$(HTMLDIR_GAMMA)/index.html: $(BODY) newfaq.aux
+$(HTMLDIR_GAMMA)/index.html: $(BODY) newfaq.aux faqbody.tex
./texfaq2file -2 -w
cp -p $(HTMLDIR_GAMMA)/* $(GAMMADIR)/
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex b/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex
index 3821a10c949..2b951fa65a9 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex
@@ -1,4 +1,4 @@
-% $Id: dirctan.tex,v 1.216 2010/01/23 00:41:09 rf10 Exp rf10 $
+% $Id: dirctan.tex,v 1.223 2010/03/23 18:39:39 rf10 Exp rf10 $
%
% protect ourself against being read twice
\csname readCTANdirs\endcsname
@@ -43,6 +43,7 @@
\CTANdirectory{amspell}{support/amspell}
\CTANdirectory{amsrefs}{macros/latex/contrib/amsrefs}[amsrefs]
\CTANdirectory{amstex}{macros/amstex}[amstex]
+\CTANdirectory{anonchap}{macros/latex/contrib/anonchap}[anonchap]
\CTANdirectory{answers}{macros/latex/contrib/answers}[answers]
\CTANdirectory{ant}{systems/ant}[ant]
\CTANdirectory{apl}{fonts/apl}
@@ -105,6 +106,7 @@
\CTANdirectory{bibunits}{macros/latex/contrib/bibunits}[bibunits]
\CTANdirectory{bibview}{biblio/bibtex/utils/bibview}
\CTANdirectory{bigfoot}{macros/latex/contrib/bigfoot}[bigfoot]
+\CTANdirectory{bigstrut}{macros/latex/contrib/multirow}[bigstrut]
\CTANdirectory{bit2spr}{graphics/bit2spr}
\CTANdirectory{black}{fonts/cm/utilityfonts/black}
\CTANdirectory{blackboard}{info/symbols/blackboard}[blackboard]
@@ -115,9 +117,11 @@
\CTANdirectory{bmeps}{support/bmeps}[bmeps]
\CTANdirectory{boites}{macros/latex/contrib/boites}[boites]
\CTANdirectory{bold}{fonts/cm/mf-extra/bold}
+\CTANdirectory{bold-extra}{macros/latex/contrib/bold-extra}[bold-extra]
\CTANdirectory{bonus}{systems/msdos/emtex-contrib/bonus}
\CTANdirectory{booktabs}{macros/latex/contrib/booktabs}[booktabs]
\CTANdirectory{borceux}{macros/generic/diagrams/borceux}
+\CTANdirectory{braket}{macros/latex/contrib/braket}[braket]
\CTANdirectory{breakurl}{macros/latex/contrib/breakurl}[breakurl]
\CTANdirectory{bridge}{macros/plain/contrib/bridge}
\CTANdirectory{brief_t}{support/brief_t}
@@ -139,6 +143,7 @@
\CTANdirectory{calendar}{macros/plain/contrib/calendar}
\CTANdirectory{calligra}{fonts/calligra}
\CTANdirectory{calrsfs}{macros/latex/contrib/calrsfs}
+\CTANdirectory{cancel}{macros/latex/contrib/cancel}[cancel]
\CTANdirectory{capt-of}{macros/latex/contrib/capt-of}[capt-of]
\CTANdirectory{caption}{macros/latex/contrib/caption}[caption]
\CTANdirectory{carlisle}{macros/latex/contrib/carlisle}[carlisle]
@@ -167,6 +172,7 @@
\CTANdirectory{chi2tex}{support/chi2tex}
\CTANdirectory{china2e}{macros/latex/contrib/china2e}
\CTANdirectory{chinese}{language/chinese}
+\CTANdirectory{chngcntr}{macros/latex/contrib/chngcntr}[chngcntr]
\CTANdirectory{circ}{macros/generic/diagrams/circ}
\CTANdirectory{circuit_macros}{graphics/circuit_macros}
\CTANdirectory{cirth}{fonts/cirth}
@@ -230,6 +236,7 @@
\CTANdirectory{datetime}{macros/latex/contrib/datetime}
\CTANdirectory{davelove}{web/noweb/contrib/davelove}
\CTANdirectory{db2tex}{support/db2tex}
+\CTANdirectory{dblfloatfix}{macros/latex/contrib/dblfloatfix}[dblfloatfix]
\CTANdirectory{dbtex}{support/dbtex}
\CTANdirectory{dc-latex}{language/hyphen-accent/dc-latex}
\CTANdirectory{dc-nfss}{language/hyphen-accent/dc-nfss}
@@ -318,6 +325,7 @@
\CTANdirectory{epigraph}{macros/latex/contrib/epigraph}[epigraph]
\CTANdirectory{eplain}{macros/eplain}[eplain]
\CTANdirectory{epmtex}{systems/os2/epmtex}
+\CTANdirectory{epslatex}{info/epslatex}[epslatex]
\CTANdirectory{epson}{dviware/epson}
\CTANdirectory*{epstopdf}{support/epstopdf}[epstopdf]
\CTANdirectory{eqparbox}{macros/latex/contrib/eqparbox}[eqparbox]
@@ -325,6 +333,7 @@
\CTANdirectory{errata}{systems/knuth/dist/errata}
\CTANdirectory{eso-pic}{macros/latex/contrib/eso-pic}[eso-pic]
\CTANdirectory{et}{support/et}
+\CTANdirectory{etex}{systems/e-tex}[etex]
\CTANdirectory{ethiopia}{language/ethiopia}
\CTANdirectory{ethtex}{language/ethiopia/ethtex}
\CTANdirectory{etoolbox}{macros/latex/contrib/etoolbox}[etoolbox]
@@ -335,10 +344,11 @@
\CTANdirectory{eurofont}{macros/latex/contrib/eurofont}
\CTANdirectory{europecv}{macros/latex/contrib/europecv}
\CTANdirectory{eurosym}{fonts/eurosym}
-\CTANdirectory{everypage}{macros/latex/contrib/everypage}
+\CTANdirectory{everypage}{macros/latex/contrib/everypage}[everypage]
\CTANdirectory{excalibur}{systems/mac/support/excalibur}
\CTANdirectory{excel2latex}{support/excel2latex}
\CTANdirectory{excerpt}{web/spiderweb/tools/excerpt}
+\CTANdirectory{excludeonly}{macros/latex/contrib/excludeonly}[excludeonly]
\CTANdirectory{expdlist}{macros/latex/contrib/expdlist}
\CTANdirectory{expl3}{macros/latex/contrib/expl3}[expl3]
\CTANdirectory{extract}{macros/latex/contrib/extract}[extract]
@@ -357,6 +367,7 @@
\CTANdirectory{figflow}{macros/plain/contrib/figflow}[figflow]
\CTANdirectory{fink}{macros/latex/contrib/fink}[fink]
\CTANdirectory{first-latex-doc}{info/first-latex-doc}
+\CTANdirectory{fix2col}{macros/latex/contrib/fix2col}[fix2col]
\CTANdirectory{fixfoot}{macros/latex/contrib/fixfoot}[fixfoot]
\CTANdirectory{float}{macros/latex/contrib/float}[float]
\CTANdirectory{floatflt}{macros/latex/contrib/floatflt}[floatflt]
@@ -364,6 +375,7 @@
\CTANdirectory{flowfram}{macros/latex/contrib/flowfram}[flowfram]
\CTANdirectory{fnbreak}{macros/latex/contrib/fnbreak}[fnbreak]
\CTANdirectory{fncychap}{macros/latex/contrib/fncychap}[fncychap]
+\CTANdirectory{fncylab}{macros/latex/contrib/fncylab}
\CTANdirectory{foiltex}{macros/latex/contrib/foiltex}[foiltex]
\CTANdirectory{font-change}{macros/plain/contrib/font-change}[font-change]
\CTANdirectory{fontch}{macros/plain/contrib/fontch}[fontch]
@@ -377,6 +389,7 @@
\CTANdirectory{for_tex}{biblio/bibtex/contrib/germbib/for_tex}
\CTANdirectory{fourier}{fonts/fourier-GUT}[fourier]
\CTANdirectory{fouriernc}{fonts/fouriernc}[fouriernc]
+\CTANdirectory{framed}{macros/latex/contrib/framed}[framed]
\CTANdirectory{frankenstein}{macros/latex/contrib/frankenstein}[frankenstein]
\CTANdirectory{french-faq}{help/LaTeX-FAQ-francaise}
\CTANdirectory{funnelweb}{web/funnelweb}
@@ -432,6 +445,7 @@
\CTANdirectory{hyacc-cm}{macros/generic/hyacc-cm}
\CTANdirectory{hyper}{macros/latex/contrib/hyper}
\CTANdirectory{hyperbibtex}{biblio/bibtex/utils/hyperbibtex}
+\CTANdirectory{hypernat}{macros/latex/contrib/hypernat}[hypernat]
\CTANdirectory{hyperref}{macros/latex/contrib/hyperref}[hyperref]
\CTANdirectory{hyphen-accent}{language/hyphen-accent}
\CTANdirectory{hyphenat}{macros/latex/contrib/hyphenat}[hyphenat]
@@ -439,10 +453,12 @@
\CTANdirectory{ibygrk}{fonts/greek/ibygrk}
\CTANdirectory{iching}{fonts/iching}
\CTANdirectory{icons}{support/icons}
+\CTANdirectory{ifmtarg}{macros/latex/contrib/ifmtarg}[ifmtarg]
\CTANdirectory{ifmslide}{macros/latex/contrib/ifmslide}[ifmslide]
\CTANdirectory{ifxetex}{macros/generic/ifxetex}[ifxetex]
\CTANdirectory{imaketex}{support/imaketex}
\CTANdirectory{impact}{web/systems/mac/impact}
+\CTANdirectory{import}{macros/latex/contrib/import}[import]
\CTANdirectory{index}{macros/latex/contrib/index}[index]
\CTANdirectory{indian}{language/indian}
\CTANdirectory{infpic}{macros/generic/infpic}
@@ -472,9 +488,9 @@
\CTANdirectory{knit}{web/knit}
\CTANdirectory{knot}{fonts/knot}
\CTANdirectory{knuth}{systems/knuth}
+\CTANdirectory{knuth-dist}{systems/knuth/dist}[knuth-dist]
\CTANdirectory{koma-script}{macros/latex/contrib/koma-script}
\CTANdirectory{korean}{fonts/korean}
-%[language/korean]
\CTANdirectory{kpfonts}{fonts/kpfonts}[kpfonts]
\CTANdirectory{kyocera}{dviware/kyocera}
\CTANdirectory{l2a}{support/l2a}[l2a]
@@ -577,6 +593,7 @@
\CTANdirectory{midnight}{macros/generic/midnight}
\CTANdirectory{minionpro}{fonts/minionpro}[minionpro]
\CTANdirectory{minitoc}{macros/latex/contrib/minitoc}[minitoc]
+\CTANdirectory{minted}{macros/latex/contrib/minted}[minted]
\CTANdirectory{mma2ltx}{graphics/mma2ltx}
\CTANdirectory{mnsymbol}{fonts/mnsymbol}[mnsymbol]
\CTANdirectory{mnu}{support/mnu}
@@ -762,6 +779,7 @@
\CTANdirectory{svninfo}{macros/latex/contrib/svninfo}[svninfo]
\CTANdirectory{swebib}{biblio/bibtex/contrib/swebib}
\CTANdirectory*{symbols}{info/symbols/comprehensive}[comprehensive]
+\CTANdirectory{tabls}{macros/latex/contrib/tabls}[tabls]
\CTANdirectory{tabulary}{macros/latex/contrib/tabulary}[tabulary]
\CTANdirectory{talk}{macros/latex/contrib/talk}[talk]
\CTANdirectory{tds}{tds}[tds]
@@ -791,6 +809,7 @@
\CTANdirectory{textures_figs}{systems/mac/textures_figs}
\CTANdirectory{texutils}{systems/atari/texutils}
\CTANdirectory{tgrind}{support/tgrind}[tgrind]
+\CTANdirectory{threeparttable}{macros/latex/contrib/threeparttable}[threeparttable]
\CTANdirectory{threeparttablex}{macros/latex/contrib/threeparttablex}[threeparttablex]
\CTANdirectory{tib}{biblio/tib}[tib]
\CTANdirectory{tiny_c2l}{support/tiny_c2l}[tinyc2l]
@@ -817,6 +836,7 @@
\CTANdirectory{type1cm}{macros/latex/contrib/type1cm}[type1cm]
\CTANdirectory{ucthesis}{macros/latex/contrib/ucthesis}[ucthesis]
\CTANdirectory{uktex}{digests/uktex}
+\CTANdirectory{ulem}{macros/latex/contrib/ulem}[ulem]
\CTANdirectory{umrand}{macros/generic/umrand}
\CTANdirectory{unix}{systems/unix}
\CTANdirectory{unpacked}{macros/latex/unpacked}
@@ -827,10 +847,12 @@
\CTANdirectory{utopia}{fonts/utopia}[utopia]
\CTANdirectory{varisize}{macros/plain/contrib/varisize}[varisize]
\CTANdirectory{vc}{support/vc}[vc]
+\CTANdirectory{verbdef}{macros/latex/contrib/verbdef}
\CTANdirectory{vita}{macros/latex/contrib/vita}[vita]
\CTANdirectory{vmargin}{macros/latex/contrib/vmargin}[vmargin]
\CTANdirectory{vmspell}{support/vmspell}[vmspell]
\CTANdirectory{vpp}{support/view_print_ps_pdf}[vpp]
+\CTANdirectory{vruler}{macros/latex/contrib/vruler}[vruler]
\CTANdirectory{vtex-common}{systems/vtex/common}
\CTANdirectory{vtex-linux}{systems/vtex/linux}[vtex-free]
\CTANdirectory{vtex-os2}{systems/vtex/os2}[vtex-free]
@@ -860,8 +882,3 @@
\CTANdirectory{ziffer}{macros/latex/contrib/ziffer}[ziffer]
\CTANdirectory{zoon-mp-eg}{info/metapost/examples}[metapost-examples]
\endinput
-
-%%% Local Variables:
-%%% mode: plain-tex
-%%% TeX-master: "faqbody"
-%%% End:
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex
index 2ae04418a38..c2b15511a78 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex
@@ -1,4 +1,4 @@
-% $Id: faq-adj-types.tex,v 1.4 2010/01/05 18:54:24 rf10 Exp rf10 $
+% $Id: faq-adj-types.tex,v 1.9 2010/04/06 18:35:09 rf10 Exp rf10 $
\section{Adjusting the typesetting}
@@ -194,7 +194,7 @@ route):
\begin{ctanrefs}
\item[a0poster.cls]\CTANref{a0poster}
\item[flowfram.sty]\CTANref{flowfram}
-\item[multicol.sty]Distributed as part of \CTANref{2etools}
+\item[multicol.sty]Distributed as part of \CTANref{2etools}[multicol]
\item[sciposter.cls]\CTANref{sciposter}
\item[textpos.sty]\CTANref{textpos}
\end{ctanrefs}
@@ -251,14 +251,61 @@ The nearest things to canned solutions are Peter Wilson's
\Class{Combine} defines the means to `\csx{import}' entire documents,
and provides means of specifying significant features of the layout of
-the document, as well as a global table of contents, and so on. An
-auxiliary package, \Package{combinet}, allows use of the \csx{title}s
-and \csx{author}s (etc.\@) of the \csx{import}ed documents to appear in
-the global table of contents.
-
-\Class{Subfiles} is used in the component files of a multi-file
-project, and the corresponding \Package{subfiles} is used in the
-master file; arrangements may be made so that the component files will
+the document, as well as a global table of contents, and so on. The
+complete set of facilities is pretty complex. An auxiliary package,
+\Package{combinet}, allows use of the \csx{title}s and \csx{author}s
+(etc.\@) of the \csx{import}ed documents to appear in the global table
+of contents. The basic structure of a combined document would be:
+\begin{quote}
+\begin{verbatim}
+\documentclass[...]{combine}
+...
+\begin{document}
+...
+
+...
+\begin{papers}
+% title and author of first article,
+% to go the the main ToC
+\coltoctitle{...}
+\coltocauthor{...}
+\label{art1}
+\import{art1}
+...
+\end{papers}
+...
+
+...
+\end{document}
+\end{verbatim}
+\end{quote}
+
+The \Class{subfiles} class is used in the component files of a multi-file
+project, and the corresponding \Package{subfiles} package is used in the
+master file; so the structure of the master file looks like:
+\begin{quote}
+\begin{verbatim}
+\documentclass{}
+...
+\usepackage{subfiles}
+...
+\begin{document}
+...
+\subfile{subfile_name}
+...
+\end{document}
+\end{verbatim}
+\end{quote}
+while a subfile has the structure:
+\begin{quote}
+\begin{verbatim}
+\documentclass[mainfile_name]{subfiles}
+\begin{document}
+...
+\end{document}
+\end{verbatim}
+\end{quote}
+Arrangements may be made so that the component files will
be typeset using different page format, etc., parameters than those
used when they are typeset as a part of the main file.
@@ -292,8 +339,8 @@ of the included pages.
\item[combinet.sty]\CTANref{combine}
\item[includex.sty]Distributed in the ``unsupported'' part of
\CTANref{frankenstein}
-\item[moredefs.sty]Distributed as part of \CTANref{frankenstein}
-\item[newclude.sty]Distributed as part of \CTANref{frankenstein}
+\item[moredefs.sty]Distributed as part of \CTANref{frankenstein}[moredefs]
+\item[newclude.sty]Distributed as part of \CTANref{frankenstein}[newclude]
\item[pdfpages.sty]\CTANref{pdfpages}
\item[subfiles.cls, etc.]\CTANref{subfiles}
\end{ctanrefs}
@@ -661,7 +708,7 @@ The \Package{indentfirst} package
suppresses the mechanism, so that the first paragraph is
indented.
\begin{ctanrefs}
-\item[indentfirst.sty]Distributed as part of \CTANref{2etools}
+\item[indentfirst.sty]Distributed as part of \CTANref{2etools}[indentfirst]
\end{ctanrefs}
\Question[Q-subsubsub]{How to create a \csx{subsubsubsection}}
@@ -984,9 +1031,9 @@ It is this difficulty (what's required in any instance can't really be
expressed in current \LaTeX{}) that led the author of
\Package{multicol} to suppress single-column-wide floats.
\begin{ctanrefs}
-\item[balance.sty]Distributed as part of \CTANref{preprint}
-\item[flushend.sty]Distributed as part of \CTANref{sttools}
-\item[multicol.sty]Distributed as part of \CTANref{2etools}
+\item[balance.sty]Distributed as part of \CTANref{preprint}[balance]
+\item[flushend.sty]Distributed as part of \CTANref{sttools}[flushend]
+\item[multicol.sty]Distributed as part of \CTANref{2etools}[multicol]
\end{ctanrefs}
@@ -1287,7 +1334,7 @@ output that specifies the necessary paper size.
\begin{ctanrefs}
\item[geometry.sty]\CTANref{geometry}
\item[memoir.cls]\CTANref{memoir}
-\item[typearea.sty]Distributed as part of \CTANref{koma-script}
+\item[typearea.sty]Distributed as part of \CTANref{koma-script}[typearea]
\end{ctanrefs}
\Question[Q-changemargin]{Changing the margins in \LaTeX{}}
@@ -1353,9 +1400,9 @@ two-sided printing.
\begin{ctanrefs}
\item[geometry.sty]\CTANref{geometry}
\item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script}
-\item[layout.sty]Distributed as part of \CTANref{2etools}
+\item[layout.sty]Distributed as part of \CTANref{2etools}[layout]
\item[memoir.cls]\CTANref{memoir}
-\item[typearea.sty]Distributed as part of \CTANref{koma-script}
+\item[typearea.sty]Distributed as part of \CTANref{koma-script}[typearea]
\item[vmargin.sty]\CTANref{vmargin}
\end{ctanrefs}
@@ -1619,15 +1666,26 @@ commands for placing things at certain useful points (like ``text
upper left'' or ``text centre'') in the picture, but you're at liberty
to do what you like.
+\Package{Eso-pic} is, in turn, built upon the package
+\Package{atbegshi}. That package has the capability to produce
+watermarks \emph{on top of} the other material on the page; this
+doesn't sound very ``watermark-like'', but can be useful on pages
+where the watermark would otherwise be hidden by graphics or the
+like. The \Package{atbegshi} command that \Package{eso-pic} uses is
+\csx{AtBeginShipoutUpperLeft}; \csx{AtBeginShipoutUpperLeftForeground}
+is what's needed instead to place the material on top of the rest of
+the content of the page.
+
\Package{Everypage} allows you to add ``something'' to every page, or
to a particular page; you therefore need to construct your own
apparatus for anything complicated.
\begin{ctanrefs}
+\item[atbegshi.sty]Distributed as part of \CTANref{oberdiek}[atbegshi]
\item[draftcopy.sty]\CTANref{draftcopy}
\item[draftwatermark.sty]\CTANref{draftwatermark}
\item[eso-pic.sty]\CTANref{eso-pic}
\item[everypage.sty]\CTANref{everypage}
-\item[everyshi.sty]Distributed as part of \CTANref{ms}
+\item[everyshi.sty]Distributed as part of \CTANref{ms}[everyshi]
\item[wallpaper.sty]\CTANref{wallpaper}
\end{ctanrefs}
@@ -1705,11 +1763,11 @@ to view these `final' forms with an appropriate viewer.
\begin{ctanrefs}
\item[geometry.sty]\CTANref{geometry}
\item[graphics.sty]Distributed as part of \CTANref{graphics}
-\item[longtable.sty]Distributed as part of \CTANref{2etools}
-\item[lscape.sty]Distributed as part of \CTANref{graphics}
+\item[longtable.sty]Distributed as part of \CTANref{2etools}[longtable]
+\item[lscape.sty]Distributed as part of \CTANref{graphics}[lscape]
\item[memoir.cls]\CTANref{memoir}
\item[pdflscape.sty]Distributed with Heiko Oberdiek's packages
- \CTANref{oberdiek}
+ \CTANref{oberdiek}[pdflscape]
\item[rotating.sty]\CTANref{rotating}
\item[rotfloat.sty]\CTANref{rotfloat}
\item[supertabular.sty]\CTANref{supertabular}
@@ -1745,7 +1803,7 @@ must therefore also be available.)
% problem.
\begin{ctanrefs}
\item[eso-pic.sty]\CTANref{eso-pic}
-\item[everyshi.sty]Distributed as part of \CTANref{ms}
+\item[everyshi.sty]Distributed as part of \CTANref{ms}[everyshi]
\item[textpos.sty]\CTANref{textpos}
\end{ctanrefs}
@@ -1887,8 +1945,8 @@ as simple as
\end{quote}
\Package{Parallel} can get terribly confused with colour changes, in
\PDFTeX{}; the indefatigable Heiko Oberdiek has a patch for this
-issue~--- the \Package{pdfcolparallel}, which maintains separate
-colour stacks for the columns.
+issue~--- the \Package{pdfcolparallel} package, which maintains
+separate colour stacks for the columns.
The \Package{parcolumns} package can (in principle) deal with any
number of columns: the documentation shows its use with three
@@ -1908,7 +1966,9 @@ though there is of course a ``number of columns to specify'':
\end{verbatim}
\end{quote}
The \meta{options} can specify the widths of the columns, whether to
-place rules between the columns, whether to set the columns sloppy, etc.
+place rules between the columns, whether to set the columns sloppy,
+etc. Again, there are issues with colours, which are addressed by the
+\Package{pdfcolparcolumns} package.
The \Package{ledpar} package is distributed with (and integrated with)
the \Qref{\Package{ledmac} package}{Q-linenos}. It provides parallel
@@ -1918,8 +1978,9 @@ the `base' text of the document.
\begin{ctanrefs}
\item[ledpar.sty]Distributed with \CTANref{ledmac}
\item[parallel.sty]\CTANref{parallel}
-\item[parcolumns.sty]Distributed as part of \CTANref{sauerj}
-\item[pdfcolparallel.sty]Distributed as part of \CTANref{oberdiek}
+\item[parcolumns.sty]Distributed as part of \CTANref{sauerj}[parcolumns]
+\item[pdfcolparallel.sty]Distributed as part of \CTANref{oberdiek}[pdfcolparallel]
+\item[pdfcolparcolumns.sty]pdfcolparcolumns]
\end{ctanrefs}
\Question[Q-epigraph]{Typesetting epigraphs}
@@ -2138,7 +2199,7 @@ transformations of the \LaTeX{} kernel originals. The documentation
discusses the issues and explains the significance of the various
parameters of \Package{ragged2e}'s operation.
\begin{ctanrefs}
-\item[ragged2e.sty]Distributed as part of \CTANref{ms}
+\item[ragged2e.sty]Distributed as part of \CTANref{ms}[ragged2e]
\end{ctanrefs}
\Question[Q-flushboth]{Cancelling \csx{ragged} commands}
@@ -2172,7 +2233,7 @@ package has a \csx{justifying} command to match its % ! line break
package also provides a \environment{justify} environment, which
permits areas of justified text in a larger area which is ragged.
\begin{ctanrefs}
-\item[ragged2e.sty]Distributed as part of \CTANref{ms}
+\item[ragged2e.sty]Distributed as part of \CTANref{ms}[ragged2e]
\end{ctanrefs}
% this package hasn't materialised, for some reason i don't now
% remember...
@@ -2245,8 +2306,8 @@ The \Class{memoir} class includes the relevant functionality of the
\item[fancyvrb.sty]\CTANref{fancyvrb}
\item[memoir.cls]\CTANref{memoir}
\item[moreverb.sty]\CTANref{moreverb}
-\item[sverb.sty]Distributed as part of \CTANref{mdwtools}
-\item[verbatim.sty]Distributed as part of \CTANref{2etools}
+\item[sverb.sty]Distributed as part of \CTANref{mdwtools}[sverb]
+\item[verbatim.sty]Distributed as part of \CTANref{2etools}[verbatim]
\end{ctanrefs}
\Question[Q-linenos]{Including line numbers in typeset output}
@@ -2295,12 +2356,12 @@ the typesetting of dissertations by computer science and other
students who are expected to write programs. Simple verbatim listings
of programs are commonly useful, as well.
-\begin{wideversion} % really hyper
+\begin{hyperversion}
\Qref{Verbatim listings}{Q-verbfile} are dealt with elsewhere,
-\end{wideversion}
-\begin{narrowversion}
+\end{hyperversion}
+\begin{flatversion}
Verbatim listings are dealt with elsewhere (\Qref{}{Q-verbfile}),
-\end{narrowversion}
+\end{flatversion}
as is the problem of % ! line break
\Qref*{typesetting algorithm specifications}{Q-algorithms}.
@@ -2354,6 +2415,11 @@ and \acro{XSL}-\acro{FO} representations of your program listing.
Documentation is available on the % ! line break
\href{http://www.andre-simon.de/}{\ProgName{highlight} project site}.
+The \Package{minted} package is a relatively recent addition. It
+requires that documents be pre-processed using an external
+(\ProgName{python}) script, % ! line break
+\href{http://pygments.org/}{\ProgName{Pygments}}.
+
The \ProgName{lgrind} system is another well-established pre-compiler,
with all the facilities one might need and a wide repertoire of
languages; it is derived from the very long-established
@@ -2376,6 +2442,7 @@ program (implicitly) claims to be ``self-documenting''.
\item[highlight]\CTANref{highlight}
\item[lgrind]\CTANref{lgrind}
\item[listings.sty]\CTANref{listings}
+\item[minted.sty]\CTANref{listings}
\item[tgrind]\CTANref{tgrind}
\item[tiny\_c2l]\CTANref{tiny_c2l}
\end{ctanrefs}
@@ -2641,7 +2708,7 @@ Documentation of both package \Package{path} and package \Package{url}
is in the package files.
\begin{ctanrefs}
\item[hyperref.sty]\CTANref{hyperref}
-\item[miniltx.tex]Distributed as part of \CTANref{graphics-plain}
+\item[miniltx.tex]Distributed as part of \CTANref{graphics-plain}[miniltx]
\item[path.sty]\CTANref{path}
\item[url.sty]\CTANref{url}
\end{ctanrefs}
@@ -2816,7 +2883,7 @@ group the digits of very `long' numbers), but is inevitably less
convenient than \Package{icomma} or \Package{ziffer} if you are typing a
lot of numbers.
\begin{ctanrefs}
-\item[icomma.sty]Distributed as part of \CTANref{was}
+\item[icomma.sty]Distributed as part of \CTANref{was}[icomma]
\item[numprint.sty]\CTANref{numprint}
\item[ziffer.sty]\CTANref{ziffer}
\end{ctanrefs}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex
index 9719b0ad108..3612c0209ed 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex
@@ -1,4 +1,4 @@
-% $Id: faq-backgrnd.tex,v 1.2 2009/12/10 20:38:28 rf10 Exp $
+% $Id: faq-backgrnd.tex,v 1.5 2010/02/08 22:24:15 rf10 Exp $
\section{The Background}
@@ -26,23 +26,48 @@ Knuth developed a system of % ! line breaks
`\Qref*{literate programming}{Q-lit}' to write \TeX{},
and he provides the literate (\acro{WEB}) source of \TeX{} free of charge,
together with tools for processing the |web| source into something
-that can be compiled and something that can be printed; there's never
-any mystery about what \TeX{} does. Furthermore, the \acro{WEB} system
-provides mechanisms to port \TeX{} to new operating systems and
-computers; and in order that one may have some confidence in the ports,
-Knuth supplied a \Qref*{test}{Q-triptrap} by
+that can be compiled and something that can be printed; there is (in
+principle) never any mystery about what \TeX{} does. Furthermore, the
+\acro{WEB} system provides mechanisms to port \TeX{} to new operating
+systems and computers; and in order that one may have some confidence
+in the ports, Knuth supplied a \Qref*{test}{Q-triptrap} by
means of which one may judge the fidelity of a \TeX{} system. \TeX{}
and its documents are therefore highly portable.
+For the interested programmer, the distribution of \TeX{} has some
+fascination: it's nothing like the way one would construct such a
+program nowadays, yet it has lasted better than most, and has been
+ported to many different computer architectures and operating
+systems~--- the sorts of attributes that much modern programming
+practice aims for. The processed `readable' source of \TeX{} the
+program may be found in the % ! line break
+\begin{hyperversion}
+ \Qref*{\acro{TDS} structured version}{Q-tds} of the distribution.
+\end{hyperversion}
+\begin{dviversion}
+ \Qref*{\acro{TDS} structured version of the distribution}{Q-tds}.
+\end{dviversion}
+\begin{ctanrefs}
+\item[\nothtml{\rmfamily}Knuth's source distribution]\CTANref{knuth-dist}
+\item[\nothtml{\rmfamily}Knuth's sources in \acro{TDS} layout]\CTANref{knuth-tds}
+\end{ctanrefs}
+
+\Question[Q-plaintex]{What's ``writing in \TeX{}''?}
+
\TeX{} is a macro processor, and offers its users a powerful
-programming capability. For this reason, \TeX{} on its own is a
-pretty difficult beast to deal with, so Knuth provided a package of
-macros for use with \TeX{} called \plaintex{}; \plaintex{} is
-effectively the minimum set of macros one can usefully employ with
-\TeX{}, together with some demonstration versions of higher-level
-commands (the latter are better regarded as models than used as-is).
-When people say they're ``programming in \TeX{}'', they usually mean
-they're programming in \plaintex{}.
+programming capability. To produce a document, you write macros and
+text interleaved with each other. The macros define an environment in
+which the text is to be typeset.
+
+However, the basic \TeX{} engine is pretty
+basic, and is a pretty difficult beast to deal with. Recognising this
+(and not wanting to write the same things at the start of every
+document, himself) Knuth provided a package of macros for use with
+\TeX{}, called \plaintex{}; \plaintex{} is a useful minimum set of
+macros that can be used with \TeX{}, together with some demonstration
+versions of higher-level commands. When people say they're ``writing
+(or programming) in \TeX{}'', they usually mean they're programming in
+\plaintex{}.
\Question[Q-TeXpronounce]{How should I pronounce ``\TeX{}''?}
@@ -416,6 +441,9 @@ work, but not as well as on an \eTeX{} system. The % ! line break
\Qref*{\LaTeX{} team}{Q-LaTeX3} has announced that future \LaTeX{}
packages (specifically those from the team, as opposed to those
individually contributed) may require \eTeX{} for optimum performance.
+\begin{ctanrefs}
+\item[\eTeX{}]\CTANref{etex}
+\end{ctanrefs}
\Question[Q-whatpdftex]{What is \PDFTeX{}?}
@@ -807,17 +835,16 @@ projects: see, for example,
%\Qref[and]{and the SGML work}{Q-SGML})
to build substantial
new macro packages based on \TeX{}. For the even longer term, there
-are various projects to build a \emph{successor} to \TeX{}; see, for example,
-the
-\begin{narrowversion}
- \LuaTeX{}, Omega/Aleph and \ExTeX{} projects (questions
-\end{narrowversion}
-\Qref[\nothtml]{\LuaTeX{}}{Q-luatex},
-\Qref[\nothtml]{Omega/Aleph}{Q-omegaleph} and
-\Qref[\nothtml]{\ExTeX{}}{Q-extex}\narrowonly{).}
-\begin{wideversion}
- projects.
-\end{wideversion}
+are various projects to build a \emph{successor} to \TeX{}. The
+\Qref*{\eTeX{}}{Q-etex} extension to \TeX{} itself arose from such a
+project (\acro{NTS}). Another pair of projects, which have delivered
+all the results they are likely to deliver, is the related % ! line break
+\Qref*{Omega and Aleph}{Q-omegaleph}. The % ! line break
+\Qref*{\xetex{} system}{Q-xetex} is in principle still under
+development, but is widely used, and the % ! line break
+\Qref*{\LuaTeX{} project}{Q-luatex} (though with another two years of
+development scheduled) has already delivered a system that is quite
+useful.
\Question[Q-readtex]{Reading \AllTeX{} files}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-biblio.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-biblio.tex
index ba0271365c5..f946b1459a2 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-biblio.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-biblio.tex
@@ -1,4 +1,4 @@
-% $Id: faq-biblio.tex,v 1.5 2010/01/05 18:54:24 rf10 Exp rf10 $
+% $Id: faq-biblio.tex,v 1.7 2010/03/26 22:48:51 rf10 Exp rf10 $
\section{Bibliographies and citations}
@@ -829,7 +829,7 @@ within the document: the package will deal with chapters and sections
(as defined by \LaTeX{} itself) and also defines a \environment{bibunit}
environment so that users can select their own structuring.
\begin{ctanrefs}
-\item[chapterbib.sty]\CTANref{cite}
+\item[chapterbib.sty]distributed as part of \CTANref{cite}[chapterbib]
\item[bibunits.sty]\CTANref{bibunits}
\end{ctanrefs}
@@ -1227,7 +1227,7 @@ its other actions, and have it provide you a compressed bibliography
\emph{only}.
\begin{ctanrefs}
\item[compactbib.sty]\CTANref{compactbib}
-\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}
+\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}[mdwlist]
\item[natbib.sty]\CTANref{natbib}
\item[savetrees.sty]\CTANref{savetrees}
\end{ctanrefs}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex
index 29411a3984d..7614f0b02f5 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex
@@ -733,9 +733,7 @@ deparment's pages at
%% \URL{http://www.csit.fsu.edu/~mimi/tex/}\nobreakspace--- both sets are fine
%% examples of good practice.
\begin{ctanrefs}
-\item[\nothtml{\rmfamily}Graphics in \LaTeXe{}]the
- document is available in \PS{} and \acro{PDF} formats as
- \CTANref{epslatex_ps} and \CTANref{epslatex_pdf} respectively
+\item[\nothtml{\rmfamily}Graphics in \LaTeXe{}]\CTANref{epslatex}
\item[testflow]\CTANref{testflow}
\item[\nothtml{\rmfamily}Herbert Vo\ss{}'s Maths tutorial]\CTANref{voss-mathmode}
\end{ctanrefs}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex
index 5537fd2b3dc..030a0452b1d 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex
@@ -1,4 +1,4 @@
-% $Id: faq-dvi.tex,v 1.1 2009/06/13 20:56:38 rf10 Exp rf10 $
+% $Id: faq-dvi.tex,v 1.1 2009/06/13 20:56:38 rf10 Exp $
\section{\acro{DVI} Drivers and Previewers}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex
index 9ea9dd55dbd..d4005502fd0 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex
@@ -1,4 +1,4 @@
-% $Id: faq-fmt-conv.tex,v 1.1 2009/06/13 20:56:40 rf10 Exp rf10 $
+% $Id: faq-fmt-conv.tex,v 1.1 2009/06/13 20:56:40 rf10 Exp $
\section{Format conversions}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex
index b2bbbfdbf1f..8bcb94aaaee 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex
@@ -1,4 +1,4 @@
-% $Id: faq-fonts.tex,v 1.4 2010/01/19 22:44:39 rf10 Exp rf10 $
+% $Id: faq-fonts.tex,v 1.6 2010/03/24 23:30:44 rf10 Exp $
\section{Fonts}
@@ -920,8 +920,8 @@ versions), which should be available in any recent \TeX{} distribution.
fancy with fonts: it sets up the fonts that Knuth found he needed when
writing the package, and leaves you to do the rest.
-To use something other than Knuth's default, the default mechanism is
-to use the \csx{font} primitive:
+To use something other than Knuth's default, you can use Knuth's
+mechanism, the \csx{font} primitive:
\begin{quote}
\begin{verbatim}
\font\foo=nonstdfont
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex
index c4324e520a4..1460716a822 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex
@@ -1,4 +1,4 @@
-% $Id: faq-getit.tex,v 1.4 2010/01/19 22:44:39 rf10 Exp rf10 $
+% $Id: faq-getit.tex,v 1.4 2010/03/24 23:27:59 rf10 Exp rf10 $
\section{Acquiring the Software}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex
index 45270301eb1..8fbc6e7e5ef 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex
@@ -1,4 +1,4 @@
-% $Id: faq-graphics.tex,v 1.2 2009/06/18 23:13:04 rf10 Exp rf10 $
+% $Id: faq-graphics.tex,v 1.4 2010/03/26 22:48:51 rf10 Exp rf10 $
\section{Graphics}
@@ -105,8 +105,7 @@ but may also be
\begin{ctanrefs}
\item[epsf.tex]\CTANref{epsf}
\item[epsfig.sty]Part of the \CTANref{graphics} bundle
-\item[epslatex.pdf]\CTANref{epslatex_pdf}; the document is also available
- in \PS{} format as \CTANref{epslatex_ps}
+\item[epslatex.pdf]\CTANref{epslatex}
\item[graphics.sty]\CTANref{graphics}
\item[graphicx.sty]Part of the \CTANref{graphics} bundle
\item[miniltx.tex]\CTANref{graphics-plain}
@@ -329,7 +328,7 @@ sufficiently recent version of \PDFTeX{}, in \acro{PDF} mode~--- and
even then it won't work for \MP{} files, which are read as \TeX{}
input, and therefore use the standard input mechanism).
\begin{ctanrefs}
-\item[grffile.sty]Distributed as part of \CTANref{oberdiek}
+\item[grffile.sty]Distributed as part of \CTANref{oberdiek}[grffile]
\end{ctanrefs}
\Question[Q-graphicspath]{Importing graphics from ``somewhere else''}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex
index 40d334a538d..af25715e63a 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex
@@ -1,4 +1,4 @@
-% $Id: faq-how-do-i.tex,v 1.7 2010/01/19 22:44:39 rf10 Exp rf10 $
+% $Id: faq-how-do-i.tex,v 1.13 2010/04/02 18:20:00 rf10 Exp rf10 $
\section{How do I do\dots{}?}
@@ -37,7 +37,7 @@ The \cmdinvoke{tag*}{\csx{qedhere}} construction may be used in any of
\AMSLaTeX{}'s numbering environments.
\begin{ctanrefs}
\item[amsthm.sty]Distributed as part of the \AMSLaTeX{} bundle
- \CTANref{amslatex}
+ \CTANref{amslatex}[amsthm]
\item[ntheorem.sty]\CTANref{ntheorem}
\end{ctanrefs}
@@ -71,9 +71,9 @@ Alternatively, the following sets up an environment
The \Package{ntheorem} package provides control of the fonts used by
theorems, directly.
\begin{ctanrefs}
-\item[amsthm.sty]Distributed as part of \CTANref{amslatex}
+\item[amsthm.sty]Distributed as part of \CTANref{amslatex}[amsthm]
\item[ntheorem.sty]\CTANref{ntheorem}
-\item[theorem.sty]Distributed as part of \CTANref{2etools}
+\item[theorem.sty]Distributed as part of \CTANref{2etools}[theorem]
\end{ctanrefs}
\Question[Q-newfunction]{Defining a new log-like function in \LaTeX{}}
@@ -136,7 +136,8 @@ As with \csx{DeclareMathOperator} there's a starred version
(It should be noted that ``log-like'' was reportedly a \emph{joke} on
Lamport's part; it is of course clear what was meant.)
\begin{ctanrefs}
-\item[amsopn.sty]In the \AMSLaTeX{} distribution \CTANref{amslatex}
+\item[amsopn.sty]Distributed as part of the \AMSLaTeX{} distribution
+ \CTANref{amslatex}[amsopn]
\end{ctanrefs}
\Question[Q-braket]{Set specifications and Dirac brackets}
@@ -484,19 +485,13 @@ signs):
\end{flalign}
\end{verbatim}
\end{quote}
-
-Comprehensive documentation of \AMSLaTeX{} is to be found in
-\File{amsldoc}, in the distribution; it is also available on the web
-at \URL{ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf}
\begin{ctanrefs}
-\item[amsldoc.tex]Distributed as part of \AMSLaTeX{}
- \CTANref{amslatex}
\item[amsmath.sty]Distributed as part of \AMSLaTeX{}
- \CTANref{amslatex}
+ \CTANref{amslatex}[amsmath]
\item[amstext.sty]Distributed as part of \AMSLaTeX{}
- \CTANref{amslatex}
+ \CTANref{amslatex}[amstext]
\item[mathtools.sty]Distributed as part of the \Package{mh} bundle
- \CTANref{mh}
+ \CTANref{mh}[mathtools]
\end{ctanrefs}
\Question[Q-reuseq]{Re-using an equation}
@@ -523,15 +518,9 @@ Remember that
Here, the second instance of \ensuremath{a=b} will be
typeset with a copy, made by the \csx{tag} command, of the label of the
first instance.
-
-Comprehensive documentation of \AMSLaTeX{} is to be found in
-\File{amsldoc}, in the distribution; it is also available on the web
-at \URL{ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf}
\begin{ctanrefs}
-\item[amsldoc.tex]Distributed as part of \AMSLaTeX{}
- \CTANref{amslatex}
\item[amsmath.sty]Distributed as part of \AMSLaTeX{}
- \CTANref{amslatex}
+ \CTANref{amslatex}[amsmath]
\end{ctanrefs}
\Question[Q-brkinline]{Line-breaking in in-line maths}
@@ -608,7 +597,7 @@ operation, only those equations to which you make reference will be
numbered in the final output. See the package's documentation for
details of how to make references when the switch is in effect.
\begin{ctanrefs}
-\item[mathtools.sty]Distributed as part of \CTANref{mh}
+\item[mathtools.sty]Distributed as part of \CTANref{mh}[mathtools]
\end{ctanrefs}
\subsection{Lists}
@@ -707,7 +696,7 @@ The \Class{memoir} class includes functions that match those in the
%% larger than the default, you should also change \csx{leftmargini},
%% \csx{leftmarginii}, \emph{etc}.
\begin{ctanrefs}
-\item[enumerate.sty]Distributed as part of \CTANref{2etools}
+\item[enumerate.sty]Distributed as part of \CTANref{2etools}[enumerate]
\item[enumitem.sty]\CTANref{enumitem}
\item[memoir.cls]\CTANref{memoir}
\item[paralist.sty]\CTANref{paralist}
@@ -817,11 +806,11 @@ to set spacing between items and between paragraphs within items.
more ``basic'' (and therefore more flexible) manner than the % ! line break
\Qref*{\Package{enumerate} package}{Q-enumerate} does.
\begin{ctanrefs}
-\item[enumerate.sty]Distributed as part of \CTANref{2etools}
+\item[enumerate.sty]Distributed as part of \CTANref{2etools}[enumitem]
\item[enumitem.sty]\CTANref{enumitem}
\item[expdlist.sty]\CTANref{expdlist}
\item[memoir.cls]\CTANref{memoir}
-\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}
+\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}[mdwlist]
\item[multenum.sty]\CTANref{multenum}
\item[paralist.sty]\CTANref{paralist}
\item[savetrees.sty]\CTANref{savetrees}
@@ -966,10 +955,10 @@ However, the `nested comment' interpolated in the nested enumeration
appears as if it were a second paragraph to ``outer item 2'', which is
hardly satisfactory.
\begin{ctanrefs}
-\item[enumerate.sty]Distributed as part of \CTANref{2etools}
+\item[enumerate.sty]Distributed as part of \CTANref{2etools}[enumerate]
\item[enumitem.sty]\CTANref{enumitem}
\item[expdlist.sty]\CTANref{expdlist}
-\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}
+\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}[mdwlist]
\end{ctanrefs}
\subsection{Tables, figures and diagrams}
@@ -1115,8 +1104,8 @@ should process using \LaTeX{}. Processing will give you a \File{.sty}
file as well as the \File{.dvi} or \File{.pdf} output containing the
documentation.
\begin{ctanrefs}
-\item[ltxtable.sty]Distributed as part of \CTANref{carlisle}
-\item[tabularx.sty]Distributed as part of \CTANref{2etools}
+\item[ltxtable.sty]Distributed as part of \CTANref{carlisle}[ltxtable]
+\item[tabularx.sty]Distributed as part of \CTANref{2etools}[tabularx]
\item[tabulary.sty]\CTANref{tabulary}
\end{ctanrefs}
@@ -1177,7 +1166,7 @@ or you can use it as follows:
where the second column will end up noticeably wider, and will wrap to
a second line in the third row.
\begin{ctanrefs}
-\item[array.sty]Distributed as part of \CTANref{2etools}
+\item[array.sty]Distributed as part of \CTANref{2etools}[array]
\item[varwidth.sty]\CTANref{varwidth}
\end{ctanrefs}
@@ -1254,12 +1243,9 @@ interesting. The package provides rule commands to support the
author's scheme, but deals with inter-row spacing too. The most
recent release of \Package{booktabs} sports compatibility with
packages such as \Package{longtable}.
-
-Documentation of both \Package{bigstrut} and \Package{tabls} may be
-found as comments in the package files themselves.
\begin{ctanrefs}
-\item[array.sty]Distributed as part of \CTANref{2etools}
-\item[bigstrut.sty]Distributed as part of \CTANref{multirow}
+\item[array.sty]Distributed as part of \CTANref{2etools}[array]
+\item[bigstrut.sty]\CTANref{bigstrut}
\item[booktabs.sty]\CTANref{booktabs}
\item[cellspace.sty]\CTANref{cellspace}
\item[tabls.sty]\CTANref{tabls}
@@ -1329,10 +1315,10 @@ the head- and footline capabilities of the major packages.
Documentation of \Package{ltablex} is to be found in the package file.
\begin{ctanrefs}
-\item[longtable.sty]Distributed as part of \CTANref{2etools}
+\item[longtable.sty]Distributed as part of \CTANref{2etools}[longtable]
\item[ltablex.sty]\CTANref{ltablex}
\item[ltxtable.sty]Generate by running \CTANref{ltxtable}
-\item[stabular.sty]Distributed as part of \CTANref{sttools}
+\item[stabular.sty]Distributed as part of \CTANref{sttools}[stabular]
\item[supertabular.sty]\CTANref{supertabular}
\item[xtab.sty]\CTANref{xtab}
\end{ctanrefs}
@@ -1358,17 +1344,16 @@ arises in the last cell of a row: since each cell is set into a box,
its settings are lost at the \texttt{\&} (or \texttt{\bsbs }) that
terminates it.
-
-The technique using \csx{PBS} was developed in the days of \LaTeXo{}
-because the actual value of \texttt{\bsbs } that the \environment{tabular}
-environment uses was only available as an internal command. Nowadays,
-the value is a public command, and you can in principle use it
-explicitly:
+In the old days, the actual value of \texttt{\bsbs } that the
+\environment{tabular} environment uses was only available as an
+internal command. Nowadays, the value is a public command, and you
+can in principle use it explicitly:
\begin{quote}
\begin{verbatim}
... & \centering blah ... \tabularnewline
\end{verbatim}
\end{quote}
+(but that's a rather verbose way of doing things).
The \Package{array} package provides a command \csx{arraybackslash}
which restores \texttt{\bsbs } to its correct (within table) meaning;
@@ -1393,8 +1378,9 @@ specifications:
The \csx{tabularnewline} and \csx{arraybackslash} commands are
(somewhat) modern additions to \LaTeX{} and the \Package{array}
-package, respectively. If neither is available, the user may try the
-(old) solution which preserves the meaning of \texttt{\bsbs }:
+package, respectively. In the unlikely event that neither is
+available, the user may try the (old) solution which preserves the
+meaning of \texttt{\bsbs }:
\begin{quote}
\begin{verbatim}
\newcommand\PBS[1]{\let\temp=\\%
@@ -1416,7 +1402,7 @@ or in the preamble as:
\end{verbatim}
\end{quote}
\begin{ctanrefs}
-\item[array.sty]Distributed as part of \CTANref{2etools}
+\item[array.sty]Distributed as part of \CTANref{2etools}[array]
\end{ctanrefs}
\nothtml{\vskip 0pt plus 4ex}
@@ -1700,7 +1686,7 @@ The \Package{array} package works with several other
example \environment{longtable}), but unfortunately this trick won't
always work.
\begin{ctanrefs}
-\item[array.sty]Distributed as part of \CTANref{2etools}
+\item[array.sty]Distributed as part of \CTANref{2etools}[array]
\end{ctanrefs}
\Question[Q-multirow]{Merging cells in a column of a table}
@@ -1814,7 +1800,7 @@ rows in the multi-row have been opened up with \csx{bigstrut}.
The documentation of both \Package{multirow} and \Package{bigstrut} is
to be found, as comments, in the package files themselves.
\begin{ctanrefs}
-\item[bigstrut.sty]Distributed as part of \CTANref{multirow}
+\item[bigstrut.sty]\CTANref{bigstrut}
\item[multirow.sty]\CTANref{multirow}
\end{ctanrefs}
@@ -1984,8 +1970,8 @@ float is set \emph{before} any single column floats).
something approximating the effect it would have.)
\begin{ctanrefs}
\item[dblfloatfix.sty]\CTANref{dblfloatfix}
-\item[stfloats.sty, midfloat.sty]Distributed as part of
- \CTANref{sttools}
+\item[midfloat.sty]Distributed as part of \CTANref{sttools}[midfloat]
+\item[stfloats.sty]Distributed as part of \CTANref{sttools}[stfloats]
\end{ctanrefs}
\Question[Q-mcfloat]{Floats in multicolumn setting}
@@ -2018,7 +2004,7 @@ running off the end of the column at the end of the
\environment{multicols} environment).
\begin{ctanrefs}
\item[float.sty]\CTANref{float}
-\item[multicol.sty]Distributed as part of \CTANref{2etools}
+\item[multicol.sty]Distributed as part of \CTANref{2etools}[multicol]
\end{ctanrefs}
\Question[Q-dpfloat]{Facing floats on 2-page spread}
@@ -2043,9 +2029,6 @@ this: the construction to use is:
\end{quote}
The construction has no effect unless the standard class option
\pkgoption{twoside} is in effect.
-
-Full documentation of the package (such as it is) is to be found in
-\File{README.dpfloat}
\begin{ctanrefs}
\item[dpfloat.sty]\CTANref{dpfloat}
\end{ctanrefs}
@@ -2173,7 +2156,7 @@ and the sequence of float numbers is all correct.
\item[caption.sty]\CTANref{caption}
\item[float.sty]\CTANref{float}
\item[here.sty]\CTANref{here}
-\item[perpage.sty]Distributed as part \CTANref{bigfoot}
+\item[perpage.sty]Distributed as part \CTANref{bigfoot}[perpage]
\end{ctanrefs}
\subsection{Footnotes}
@@ -2237,12 +2220,12 @@ in ordinary text. The author of this \acro{FAQ} answer doesn't actually
recommend any of them, believing that table notes are the way to go\dots{}
\begin{ctanrefs}
\item[ctable.sty]\CTANref{ctable}
-\item[footnote.sty]Distributed as part of \CTANref{mdwtools}
-\item[longtable.sty]Distributed as part of \CTANref{2etools}
-\item[mdwtab.sty]Distributed as part of \CTANref{mdwtools}
+\item[footnote.sty]Distributed as part of \CTANref{mdwtools}[footnote]
+\item[longtable.sty]Distributed as part of \CTANref{2etools}[longtable]
+\item[mdwtab.sty]Distributed as part of \CTANref{mdwtools}[mdwtab]
\item[threeparttable.sty]\CTANref{threeparttable}
\item[threeparttablex.sty]\CTANref{threeparttablex}
-\item[tabularx.sty]Distributed as part of \CTANref{2etools}
+\item[tabularx.sty]Distributed as part of \CTANref{2etools}[tabularx]
\end{ctanrefs}
\Question[Q-ftnsect]{Footnotes in \LaTeX{} section headings}
@@ -2449,8 +2432,7 @@ also designed to support typesetting critical editions.
\item[edmac]\CTANref{edmac}
\item[ednotes]\CTANref{ednotes}
\item[ledmac]\CTANref{ledmac}
-\item[manyfoot.sty]Distributed as part of the \CTANref{ncctools}
- bundle
+\item[manyfoot.sty]Distributed as part of \CTANref{ncctools}[manyfoot]
\end{ctanrefs}
\Question[Q-footnpp]{Footnotes numbered ``per page''}
@@ -2491,15 +2473,14 @@ the one package to achieve your ends.
The \Package{footnpag} package also does per-page footnotes (and
nothing else). With the competition from \Package{perpage}, it's
-probably not particularly useful any more. (Documentation is
-\File{footnpag-user.pdf} in the distribution.)
+probably not particularly useful any more.
\begin{ctanrefs}
\item[footmisc.sty]\CTANref{footmisc}
\item[footnpag.sty]\CTANref{footnpag}
-\item[perpage.sty]Distributed as part \CTANref{bigfoot}
-\item[zref.sty]Distributed as a collection member in \CTANref{oberdiek}
-\item[zref-perpage.sty]Distributed as a collection member in
- \CTANref{oberdiek}
+\item[perpage.sty]Distributed as part \CTANref{bigfoot}[perpage]
+\item[zref.sty]Distributed as part of \CTANref{oberdiek}[zref]
+\item[zref-perpage.sty]Distributed as part of \Package{zref} in
+ \CTANref{oberdiek}[zref]
\end{ctanrefs}
\Question[Q-run-fn-nos]{Not resetting footnote numbers per chapter}
@@ -2643,13 +2624,19 @@ be used as a check-list in case that problems arise.
Note that \csx{listfiles} only registers things that are input by the
``standard'' \LaTeX{} mechanisms (\csx{documentclass}, \csx{usepackage},
-\csx{input}, \csx{include}, \csx{includegraphics} and so on). But if you
-use \TeX{} primitive syntax, as in
+\csx{include}, \csx{includegraphics} and so on).
+The \csx{input} command, as modified by \LaTeX{} and used, with
+\LaTeX{} syntax, as:
+\begin{verbatim}
+ \input{mymacros}
+\end{verbatim}
+records file details for \File{mymacros.tex}, but if you use \TeX{}
+primitive syntax for \csx{input}, as:
\begin{verbatim}
\input mymacros
\end{verbatim}
-\File{mymacros.tex} \emph{won't} be listed by \csx{listfiles}, since
-you've bypassed the mechanism that records its use.
+\File{mymacros.tex} \emph{won't} be recorded, and so won't listed by
+\csx{listfiles}~--- you've bypassed the mechanism that records its use.
The \Package{snapshot} package helps the owner of a \LaTeX{} document
obtain a list of the external dependencies of the document, in a form
@@ -2923,21 +2910,19 @@ including (numeric or labelled) ranges of environments to extract, and
an \environment{extract} environment which you can use to create complete
ready-to-run \LaTeX{} documents with stuff you've extracted.
\begin{ctanrefs}
-\item[askinclude.sty]Distributed with Heiko Oberdiek's packages~---
- \CTANref{oberdiek}
+\item[askinclude.sty]Distributed as part of \CTANref{oberdiek}[askinclude]
\item[comment.sty]\CTANref{comment}
\item[excludeonly.sty]\CTANref{excludeonly}
\item[extract.sty]\CTANref{extract}
\item[memoir.cls]\CTANref{memoir}
\item[optional.sty]\CTANref{optional}
-\item[pagesel.sty]Distributed with Heiko Oberdiek's packages~---
- \CTANref{oberdiek}
+\item[pagesel.sty]Distributed as part of \CTANref{oberdiek}[pagesel]
\item[pdfpages.sty]\CTANref{pdfpages}
\item[selectp.sty]\CTANref{selectp}
-\item[verbatim.sty]Distributed as part of \CTANref{2etools}
+\item[verbatim.sty]Distributed as part of \CTANref{2etools}[verbatim]
\item[version.sty]\CTANref{version}
\item[versions.sty]\CTANref{versions}
-\item[xcomment.sty]Distributed as part of \CTANref{seminar}
+\item[xcomment.sty]Distributed as part of \CTANref{seminar}[xcomment]
\end{ctanrefs}
\Question[Q-docotherdir]{Bits of document from other directories}
@@ -3031,8 +3016,8 @@ following minimal solution:
\begin{wideversion}
\begin{verbatim}
\def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}}
-\RCS$Revision: 1.7 $ % or any RCS keyword
-\RCS$Date: 2010/01/19 22:44:39 $
+\RCS$Revision: 1.13 $ % or any RCS keyword
+\RCS$Date: 2010/04/02 18:20:00 $
...
\date{Revision \RCSRevision, \RCSDate}
\end{verbatim}
@@ -3042,8 +3027,8 @@ following minimal solution:
\def\RCS$#1: #2 ${\expandafter
\def\csname RCS#1\endcsname{#2}%
}
-\RCS$Revision: 1.7 $ % or any RCS keyword
-\RCS$Date: 2010/01/19 22:44:39 $
+\RCS$Revision: 1.13 $ % or any RCS keyword
+\RCS$Date: 2010/04/02 18:20:00 $
...
\date{Revision \RCSRevision, \RCSDate}
\end{verbatim}
@@ -3188,8 +3173,8 @@ to the equivalent of the \texttt{LastPage} label and the
Both \Package{count1to} and \Package{totpages} need the support of
the \Package{everyshi} package.
\begin{ctanrefs}
-\item[count1to.sty \nothtml{\bgroup\rmfamily}and\nothtml{\egroup} everyshi.sty]% line break!!
- Distributed in \CTANref{ms}
+\item[count1to.sty]Distributed as part of \CTANref{ms}[count1to]
+\item[everyshi.sty]Distributed as part of \CTANref{ms}[everyshi]
\item[lastpage.sty]\CTANref{lastpage}
\item[memoir.cls]\CTANref{memoir}
\item[totpages.sty]\CTANref{totpages}
@@ -3221,7 +3206,7 @@ The package is known to fail, for example, with documents that use
All these things can be overcome (although it's not often easy), but
the environment saves a lot of work on many occasions.
\begin{ctanrefs}
-\item[plain.sty]Distributed as part of \CTANref{carlisle}
+\item[plain.sty]Distributed as part of \CTANref{carlisle}[plain-ltx]
\end{ctanrefs}
\subsection{Hyphenation}
@@ -3519,7 +3504,7 @@ and the \Package{hyphenat} package uses this technique for its
\csx{nohyphens} command which sets its argument without any
hyphenation. You can load \Package{hyphenat} with the command
\begin{quote}
- \cmdinvoke{usepckage}[none]{hyphenat}
+ \cmdinvoke{usepackage}[none]{hyphenat}
\end{quote}
to prevent any hyphenation in a single-language document. The
technique cannot work in a document in which \Package{babel} controls
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex
index 1ed5d96e3bc..cd2341c6cd2 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex
@@ -1,4 +1,4 @@
-% $Id: faq-install.tex,v 1.8 2009/12/25 00:29:51 rf10 Exp rf10 $
+% $Id: faq-install.tex,v 1.8 2009/12/25 00:29:51 rf10 Exp $
\section{Installing \AllTeX{} files}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex
index 5d0fcecc358..8e6477eaca9 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex
@@ -1,4 +1,4 @@
-% $Id: faq-intro.tex,v 1.8 2009/12/28 23:20:40 rf10 Exp rf10 $
+% $Id: faq-intro.tex,v 1.10 2010/04/02 19:11:38 rf10 Exp rf10 $
% this environment is for the benefit of new-style file generation
\begin{introduction}
@@ -15,40 +15,56 @@ You may use the \acro{FAQ}
\begin{itemize}
\item by reading a printed document,
\item by viewing a \acro{PDF} file, with hyperlinks to assist
- browsing: copies are available formatted for printing on
- \CTANhref{faq-a4}{A4 paper} or on % ! line break
- \CTANhref{faq-letter}{North American ``letter'' paper}, or
+ browsing: copies are available formatted so that they could be
+ printed on \CTANhref{faq-a4}{A4 paper} or on % ! line break
+ \CTANhref{faq-letter}{North American ``letter'' paper}, \htmlonly{or}
+\htmlignore
\item by using the \acro{FAQ}'s web interface (base \acro{URL}:
\URL{http://www.tex.ac.uk/faq}); this version provides simple
search capabilities, as well as a link to Google for a more
sophisticated search restricted to the \acro{FAQ} itself, or
+\endhtmlignore
\item via Scott Pakin's \CTANhref{visualFAQ}{Visual FAQ}, which shows
- \LaTeX{} constructions with links to \acro{FAQ} details of how they
- were created.
+ \LaTeX{} constructions with links to \acro{FAQ} explanations of how
+ they may be created.
\end{itemize}
\subsection{Finding the Files}
+\begin{typesetversion}
Unless otherwise specified, all files mentioned in this \acro{FAQ}
are available from a \acro{CTAN} archive, or from a mirror of
\acro{CTAN}~--- see \Qref[question]{later discussion}{Q-archives}% ! space
\narrowonly{, which gives details} of the \acro{CTAN}
archives\wideonly{ and}\narrowonly{, including} how to retrieve files
-from them. If you don't have access to the internet, the
-\Qref*{\texlive{} distribution}{Q-CD} offers off-line snapshots of the
-archives.
+from them.
+%% If you don't have access to the internet, the
+%% \Qref*{\texlive{} distribution}{Q-CD} offers off-line snapshots of the
+%% archives.
-The reader should also note that the first directory name of the
-path name of every file on \acro{CTAN} is omitted from what
-follows, for the simple reason that, while it's always the same
+The reader should also note that the first directory name of the path
+name of every file on \acro{CTAN} is omitted from what follows, for
+the simple reason that, while it's always the same
(\path{tex-archive/}) on the main sites, mirror sites often choose
something else.
-To avoid confusion, we also omit the full stop from the end of
-any sentence whose last item is a path name (such sentences are
-rare, and only occur at the end of paragraphs). Though the path
-names are set in a different font from running text, it's not easy
-to distinguish the font of a single dot!
+To avoid confusion, we also omit the full stop from the end of any
+sentence whose last item is a path name (such sentences are rare, and
+only occur at the end of paragraphs). Though the path names are set
+in a different font from running text, it's not easy to distinguish
+the font of a single dot!
+\end{typesetversion}
+\begin{htmlversion}
+Almost all files suggested in answers in these \acro{FAQ}s are
+available from \Qref{\acro{CTAN} archives}{Q-archives}, and may be
+reached via links in the file list at the end of the answer. In
+particular, documentation (when available) is linked from the
+\acro{CTAN} Catalogue entry, which is also listed in the file list.
+
+Unless doing so is unavoidable, the answers do not mention things not
+on the archive. An obvious exception is web resources such as
+supplementary documents, etc.
+\end{htmlversion}
\latexhtml{\subsection*{Origins}}{\textbf{Origins}}
@@ -60,6 +76,7 @@ Bodenheimer. The first \acro{UK} version was much re-arranged and
corrected from the original, and little of Bodenheimer's work now
remains.
+\htmlignore
The following people (at least~--- there are almost certainly others
whose names weren't correctly recorded) have contributed help or
advice on the development of the \acro{FAQ}: Donald Arseneau,
@@ -79,6 +96,7 @@ Ulrike Fischer, % spotted boondoggle in q-tabcellalign
% args like \section improvement; general typos
Anthony Goreham,
Norman Gray,
+Enrico Gregorio, % new definition for q-seccntfmt
Eitan Gurari, % (RIP) comparative html translators
William Hammond, % lots of work on xml-related answers
John Harper, % patient help with q-robust ;-)
@@ -124,7 +142,7 @@ Oren Patashnik,
Manuel P\'egouri\'e-Gonnard, % improvement of q-luatex
Steve Peter, % comprehensive review, lots of typos etc
Sebastian Rahtz, % without whom there would be no...
-Philip Ratcliffe, % help with a bibtex oddity
+Philip Ratcliffe, % help with a bibtex oddity, editorial comment
Chris Rowley, % founding father
Jos\'e Carlos Santos, % assiduous reader of new versions
Walter Schmidt,
@@ -146,4 +164,5 @@ That list does \emph{not} cover the many people whose ideas I have
encountered on various lists, newsgroups or (lately) web forums. Many
such people have helped me, perhaps simply to alert me to an area in
which I need to work.
+\endhtmlignore
\end{introduction}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex
index 7bf27aba3fa..e0fb8436c7c 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex
@@ -1,4 +1,4 @@
-% $Id: faq-jot-err.tex,v 1.3 2009/12/10 20:38:28 rf10 Exp $
+% $Id: faq-jot-err.tex,v 1.4 2010/03/26 22:48:51 rf10 Exp rf10 $
\section{The joy of \TeX{} errors}
@@ -69,7 +69,7 @@ appeal to the \Qref*[question]{wider public}{Q-gethelp}
for assistance, but if you do, be sure to
report full backtraces (see |errorcontextlines| above) and so on.
\begin{ctanrefs}
-\item[trace.sty]Distributed as part of \CTANref{2etools}
+\item[trace.sty]Distributed as part of \CTANref{2etools}[trace]
\end{ctanrefs}
\Question[Q-errstruct]{The structure of \TeX{} error messages}
@@ -659,7 +659,7 @@ The diagnostic not only tells us where the group started, but also the
\csx{bgroup}, and the two are not distinguishable at the \TeX{}-engine
level).
\begin{ctanrefs}
-\item[checkend.sty]Distributed as part of \CTANref{bezos}
+\item[checkend.sty]Distributed as part of \CTANref{bezos}[checkend]
\end{ctanrefs}
\Question[Q-nonum]{``Missing number, treated as zero''}
@@ -705,7 +705,7 @@ incorporates \FontName{Times}-like mathematics, and a sans-serif face
based on \FontName{Helvetica}, but scaled to match \FontName{Times}
text rather better.
\begin{ctanrefs}
-\item[calc.sty]Distributed as part of \CTANref{2etools}
+\item[calc.sty]Distributed as part of \CTANref{2etools}[calc]
\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\LaTeX{} Companion]\CTANref{tlc2}
\item[The psnfss bundle]\CTANref{psnfss}
\end{ctanrefs}
@@ -823,7 +823,8 @@ unsatisfactory alternatives:
\end{wideversion}
\end{itemize}
\begin{ctanrefs}
-\item[grffile.sty]Distributed as part of the \CTANref{oberdiek} collection
+\item[grffile.sty]Distributed as part of the Oberdiek collection
+ \CTANref{oberdiek}[grffile]
\end{ctanrefs}
\Question[Q-nodollar]{``Missing \texttt{\$} inserted''}
@@ -1403,7 +1404,7 @@ Get rid of the error in the way described in % ! linebreak
\csx{tabularnewline} explicitly, or use the \csx{RBS} trick described
there.
\begin{ctanrefs}
-\item[array.sty]Distributed as part of \CTANref{2etools}
+\item[array.sty]Distributed as part of \CTANref{2etools}[array]
\end{ctanrefs}
\Question[Q-divzero]{Graphics division by zero}
@@ -1564,7 +1565,7 @@ and then steadily reduce the bold families, starting with
\end{quote}
until (with a bit of luck) the error goes away.
\begin{ctanrefs}
-\item[bm.sty]Distributed as part of \CTANref{2etools}
+\item[bm.sty]Distributed as part of \CTANref{2etools}[bm]
\end{ctanrefs}
\Question[Q-ouparmd]{Not in outer par mode}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-lab-ref.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-lab-ref.tex
index 5f7f2cea0af..2958f541444 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-lab-ref.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-lab-ref.tex
@@ -1,4 +1,4 @@
-% $Id: faq-lab-ref.tex,v 1.1 2009/06/13 20:56:44 rf10 Exp rf10 $
+% $Id: faq-lab-ref.tex,v 1.2 2010/03/26 22:48:51 rf10 Exp rf10 $
\subsection{Labels and references}
@@ -68,7 +68,7 @@ define a short-name variant.)
\item[nameref.sty]Distributed with \CTANref{hyperref}
\item[smartref.sty]\CTANref{smartref}
\item[titleref.sty]\CTANref{titleref}
-\item[zref.sty]Distributed as part of \CTANref{oberdiek}
+\item[zref.sty]Distributed as part of \CTANref{oberdiek}[zref]
\end{ctanrefs}
\Question[Q-extref]{Referring to labels in other documents}
@@ -176,9 +176,9 @@ The module provides all the facilities of the older packages, and can
deal both with ``traditional'' \LaTeX{} labels and with
\Package{zref}'s style of labels.
\begin{ctanrefs}
-\item[xr.sty]Distributed as part of \CTANref{2etools}
-\item[xr-hyper.sty]Distributed with \CTANref{hyperref}
+\item[xr.sty]Distributed as part of \CTANref{2etools}[xr]
+\item[xr-hyper.sty]Distributed with \CTANref{hyperref}[xr-hyper]
\item[zref \nothtml{\rmfamily\itshape}bundle]Distributed as part of
- \CTANref{oberdiek}
+ \CTANref{oberdiek}[zref]
\end{ctanrefs}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-litprog.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-litprog.tex
index 277796e5969..06b0c348412 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-litprog.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-litprog.tex
@@ -1,4 +1,4 @@
-% $Id: faq-litprog.tex,v 1.1 2009/06/13 20:56:39 rf10 Exp rf10 $
+% $Id: faq-litprog.tex,v 1.1 2009/06/13 20:56:39 rf10 Exp $
\section{Literate programming}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex
index 69e5e655dda..d421044660e 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex
@@ -1,4 +1,4 @@
-% $Id: faq-mac-prog.tex,v 1.6 2009/11/01 23:23:26 rf10 Exp rf10 $
+% $Id: faq-mac-prog.tex,v 1.10 2010/04/06 18:35:09 rf10 Exp rf10 $
\section{Macro programming}
@@ -782,7 +782,7 @@ doesn't have to remember that argument twelve is |soiltype|, and so
on: the commands may be copied from field notes quickly and
accurately.
\begin{ctanrefs}
-\item[keyval.sty]Distributed as part of \CTANref{graphics}
+\item[keyval.sty]Distributed as part of \CTANref{graphics}[keyval]
\end{ctanrefs}
\Question[Q-keyval]{Key-value input for macros and package options}
@@ -958,11 +958,11 @@ for \textsl{TUGboat} by Joseph Wright, and the partial translation of the
documentation of package \Package{scrbase} prepared by Philipp
Stephani.
\begin{ctanrefs}
-\item[keyval.sty]Distributed as part of \CTANref{graphics}
-\item[kvoptions.sty]Distributed as part of \CTANref{oberdiek}
-\item[kvsetkeys.sty]Distributed as part of \CTANref{oberdiek}
+\item[keyval.sty]Distributed as part of \CTANref{graphics}[keyval
+\item[kvoptions.sty]Distributed as part of \CTANref{oberdiek}[kvoptions]
+\item[kvsetkeys.sty]Distributed as part of \CTANref{oberdiek}[kvsetkeys]
\item[l3keys.sty]Distributed as part of \CTANref{expl3}
-\item[l3keys2e.sty]Distributed as part of \CTANref{expl3}
+\item[l3keys2e.sty]Distributed as part of \CTANref{xpackages}
\item[pgfkeys.sty]Distributed as part of \CTANref{pgf}
\item[scrbase.sty]Distributed as part of \CTANref{koma-script}
\item[xkeyval.sty]\CTANref{xkeyval}
@@ -975,19 +975,27 @@ Single characters can act as macros (defined commands), and both
``\texttt{\textasciitilde}'' as a ``non-breakable space''. A
character is made definable, or ``active'', by setting its
\emph{category code} (catcode) to be \csx{active} (13):
-|\catcode`_=\active|.
-
+\begin{quote}
+\begin{verbatim}
+\catcode`\_=\active
+\end{verbatim}
+\end{quote}
Any character could, in principle, be activated this way and defined
-as a macro (\csx{def}\texttt{\_\{}\csx{\_}\texttt{\}}~--- the simple answer to
-% beware line break
-\Qref[question]{using underscores}{Q-underscore}), but you must be
+as a macro:
+\begin{quote}
+\begin{verbatim}
+\def_{\_}
+\end{verbatim}
+\end{quote}
+which could be characterised as an over-simple answer to % ! line break
+\Qref[question]{using underscores}{Q-underscore}. However, you must be
wary: whereas people expect an active tilde, other active characters
may be unexpected and interact badly with other macros. Furthermore,
by defining an active character, you preclude the character's use for
other purposes, and there are few characters ``free'' to be subverted
in this way.
-To define the character ``|z|'' as a command, one would say something
+To define the character ``\texttt{z}'' as a command, one would say something
like:
\begin{quote}
\begin{verbatim}
@@ -1086,8 +1094,8 @@ made active~--- the definition of the command persists even if the
character's catcode reverts to its original value; the definition
becomes accessible again if the character once again becomes active.
\begin{ctanrefs}
-\item[doc.sty]Distributed as part of the source of \LaTeX{}, \CTANref{latex}
-\item[shortvrb.sty]Distributed as part of \CTANref{2etools}
+\item[doc.sty]Part of the \LaTeX{} distribution \CTANref{latex}[doc]
+\item[shortvrb.sty]Part of the \LaTeX{} distribution \CTANref{latex}[shortvrb]
\end{ctanrefs}
@@ -1450,9 +1458,10 @@ the ``\TeX{} project'' answers covering % ! line break
\Qref[\xetex{}~--- question]{\xetex{}}{Q-xetex}, and
\Qref[\LuaTeX{}~--- question]{\LuaTeX{}}{Q-luatex}).
\begin{ctanrefs}
-\item[ifpdf.sty]Distributed with Heiko Oberdiek's packages \CTANref{oberdiek}
-\item[ifluatex.sty]Distributed with Heiko Oberdiek's packages
- \CTANref{oberdiek}
+\item[ifpdf.sty]Distributed as part Heiko Oberdiek's bundle
+ \CTANref{oberdiek}[ifpdf]
+\item[ifluatex.sty]Distributed as part of Heiko Oberdiek's bundle
+ \CTANref{oberdiek}[ifluatex]
\item[ifxetex.sty]\CTANref{ifxetex}
\end{ctanrefs}
@@ -1808,8 +1817,8 @@ protection of some things, but the techniques available in
current \LaTeX{} mean that this is an expensive exercise. It remains
a long-term aim of the team to remove all need for \csx{protect}ion.
\begin{ctanrefs}
-\item[makerobust.sty]Distributed with Heiko Oberdiek's packages
- \CTANref{oberdiek}
+\item[makerobust.sty]Distributed as part of Heiko Oberdiek's bundle
+ \CTANref{oberdiek}[makerobust]
\end{ctanrefs}
\Question[Q-edef]{\csx{edef} does not work with \csx{protect}}
@@ -2074,8 +2083,8 @@ the command to be defined. The command requires that a
\ProgName{Python} interpreter (etc.\@) be installed on your computer.
\begin{ctanrefs}
\item[newcommand.py]\CTANref{newcommand}
-\item[optparams.sty]Distributed as part of \CTANref{sauerj}
-\item[twoopt.sty]Distributed as part of \CTANref{oberdiek}
+\item[optparams.sty]Distributed as part of \CTANref{sauerj}[optparams]
+\item[twoopt.sty]Distributed as part of \CTANref{oberdiek}[twoopt]
\item[xargs.sty]\CTANref{xargs}
\item[xkeyval.sty]\CTANref{xkeyval}
\end{ctanrefs}
@@ -2182,7 +2191,7 @@ definition like:
\end{quote}
\begin{ctanrefs}
\item[ifthen.sty]Part of the \LaTeX{} distribution
-\item[suffix.sty]Distributed as part of \CTANref{bigfoot}
+\item[suffix.sty]Distributed as part of \CTANref{bigfoot}[suffix]
\end{ctanrefs}
\nothtml{\hrule height 0pt \nobreak\vskip0pt plus2.5in\vskip 0pt\relax}
@@ -2493,7 +2502,7 @@ numbered per chapter, try:
\item[removefr.tex]\CTANref{removefr} (note, this is constructed as a
``fragment'' for use within other packages: load by
\cmdinvoke{input}{removefr})
-\item[remreset.sty]Distributed as part of \CTANref{carlisle}
+\item[remreset.sty]Distributed as part of \CTANref{carlisle}[remreset]
\end{ctanrefs}
\Question[Q-labelctr]{Making labels from a counter}
@@ -2657,79 +2666,57 @@ number appears in the heading, and some such people don't mind writing
out a few macros. This answer is for \emph{them}.
The section number is typeset using the
-\begin{narrowversion}
+\begin{dviversion}
\LaTeX{} internal
-\end{narrowversion}
-\begin{wideversion}
+\end{dviversion}
+\begin{hyperversion}
\Qref{\LaTeX{} internal}{Q-atsigns}
-\end{wideversion}
+\end{hyperversion}
\csx{@seccntformat} command, which is given the ``name'' (section,
subsection, \dots{}) of the heading, as argument. Ordinarily,
\csx{@seccntformat}
-merely outputs the section number, and then a \csx{quad} of space.
-Suppose you want to put a stop after every section (subsection,
-subsubsection, \dots{}) number, a trivial change may be implemented by
-simple modification of the command:
+merely outputs the section number, and then a \csx{quad} of space:
\begin{quote}
\begin{verbatim}
\renewcommand*{\@seccntformat}[1]{%
- \csname the#1\endcsname.\quad
+ \csname the#1\endcsname\quad
}
\end{verbatim}
\end{quote}
-
-Many people (for some reason) want a stop after a section number, but
-not after a subsection number, or any of the others.
-To do this, one must make \csx{@seccntformat} switch according to its
-argument. The following technique for doing the job is slightly
-wasteful, but is efficient enough for a relatively rare operation:
-\begin{wideversion}
+Suppose you want to put a stop after every section (subsection,
+subsubsection, \dots{}) number, a trivial change may be implemented by
+simple modification of the command:
\begin{quote}
\begin{verbatim}
-\let\@@seccntformat\@seccntformat
\renewcommand*{\@seccntformat}[1]{%
- \expandafter\ifx\csname @seccntformat@#1\endcsname\relax
- \expandafter\@@seccntformat
- \else
- \expandafter
- \csname @seccntformat@#1\expandafter\endcsname
- \fi
- {#1}%
+ \csname the#1\endcsname.\quad
}
\end{verbatim}
\end{quote}
-\end{wideversion}
-\begin{narrowversion}
+However, many people want to modify section numbers, but not
+subsection numbers, or any of the others. To do this, one must make
+\csx{@seccntformat} switch according to its argument. The following
+technique for doing the job is slightly wasteful, but is efficient
+enough for a relatively rare operation:
\begin{quote}
\begin{verbatim}
-\let\@@seccntformat\@seccntformat
\renewcommand*{\@seccntformat}[1]{%
- \expandafter\ifx
- \csname @seccntformat@#1\endcsname
- \relax
- \expandafter\@@seccntformat
- \else
- \expandafter
- \csname @seccntformat@#1\expandafter
- \endcsname
- \fi
- {#1}%
+ \csname the#1\endcsname
+ \csname adddot@#1\endcsname\quad
}
\end{verbatim}
\end{quote}
-\end{narrowversion}
-which looks to see if a second-level command has been defined, and
-uses it if so; otherwise it uses the original. The second-level
-command to define stops after section numbers (only) has the same
-definition as the original ``all levels alike'' version:
+which uses a second-level command to provide the dot, if it has been
+defined; otherwise it merely appends \csx{relax} (which does nothing
+in this context). The definition of the second-level command (the
+version for the \texttt{section}, here) specifies what to put after a
+section number, but it could be used to put anything after it:
\begin{quote}
\begin{verbatim}
-\newcommand*{\@seccntformat@section}[1]{%
- \csname the#1\endcsname.\quad
-}
+\newcommand*{\adddot@section}{.}
\end{verbatim}
\end{quote}
-Note that all the command definitions of this answer are dealing in
+Note that all the command definitions above are dealing in
\Qref*{\LaTeX{} internal commands}{Q-atsigns}, so the above
code should be in a package file, for preference.
@@ -2871,7 +2858,7 @@ to stabilise counter values~--- \LaTeX{} will generate the usual
warnings about labels changing.
\begin{ctanrefs}
\item[chngcntr.sty]\CTANref{chngcntr}
-\item[perpage.sty]Distributed as part \CTANref{bigfoot}
+\item[perpage.sty]Distributed as part \CTANref{bigfoot}[perpage]
\end{ctanrefs}
\Question[Q-fontsize]{Fonts at arbitrary sizes}
@@ -2917,7 +2904,7 @@ December 2003 edition of \LaTeX{}; if you have an older distribution,
the packages \Package{type1cm} (for \acro{CM} fonts) and
\Package{type1ec} (for \acro{EC} fonts) are available.
\begin{ctanrefs}
-\item[fix-cm.sty]Distributed as part of \CTANref{latex} (an unpacked
+\item[fix-cm.sty]Distributed as part of \CTANref{latex}[fix-cm] (an unpacked
version is available at \CTANref{fix-cm})
\item[type1cm.sty]\CTANref{type1cm}
\item[type1ec.sty]\CTANref{type1ec} (the package is actually part of
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex
index c01f64e5be0..02f5e3ab5a7 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex
@@ -1,4 +1,4 @@
-% $Id: faq-projects.tex,v 1.7 2009/12/25 10:31:28 rf10 Exp rf10 $
+% $Id: faq-projects.tex,v 1.9 2010/04/06 18:35:09 rf10 Exp rf10 $
\section{Current \TeX{}-related projects}
@@ -297,7 +297,7 @@ separate window), degree of correspondence of the display to the final
output, and the balance they strike between visual aid and visual
distraction.
\begin{ctanrefs}
-\item[preview-latex]Distributed as part of \CTANref{auctex}
+\item[preview-latex]Distributed as part of \CTANref{auctex}[preview-latex]
\item[texmacs]Browse \CTANref{texmacs}
\end{ctanrefs}
@@ -389,9 +389,10 @@ current projects have in their sights, notably Unicode character
representations and support for OpenType fonts. The intention is
to integrate the extensions pioneered by \Qref*{Aleph}{Q-omegaleph}.
-Version 0.50.0 of \LuaTeX{} is intended to at least demonstrate the final
-functionality; it was released near the end of December 2009. Much
-work remains to be done, and this remains a beta-release.
+The current version (0.60.0, in April 2010) of \LuaTeX{} is supposed
+at least to demonstrate the final functionality. This stability was
+declared with version 0.50.0, released near the end of December 2009.
+Much work remains to be done, and this remains a beta-release.
\texlive{} 2009 incorporates (at the time of writing) \LuaTeX{}
version 0.44.0, but the latest \miktex{} (version 2.8) still doesn't
offer it.
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex
index b08e2ab44ac..ed06d60b0a0 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex
@@ -1,4 +1,4 @@
-% $Id: faq-symbols.tex,v 1.2 2009/06/30 18:44:15 rf10 Exp $
+% $Id: faq-symbols.tex,v 1.3 2010/03/26 22:48:51 rf10 Exp rf10 $
\section{Symbols, etc.}
@@ -187,7 +187,7 @@ Examples of the available styles are available on \acro{CTAN}.
\item[eucal.sty]Distributed as part of \CTANref{amsfonts}
\item[euler fonts]Distributed as part of \CTANref{amsfonts}
\item[ghostscript]Browse \CTANref{ghostscript}
-\item[mathrsfs.sty]Distributed as part of \CTANref{jknappen-macros}
+\item[mathrsfs.sty]Distributed as part of \CTANref{jknappen-macros}[mathrsfs]
\item[rsfs fonts]\CTANref{rsfs}
\item[Script font examples]\CTANref{mathscript}
\item[URW Chancery L]Distributed as part of \CTANref{urw-base35}
@@ -233,10 +233,10 @@ These problems may be addressed by using a bold mathematics package.
All these solutions cover all mathematical symbols, not merely Greek
letters.
\begin{ctanrefs}
-\item[bm.sty]Distributed as part of \CTANref{2etools}
-\item[amsbsy.sty]Distributed as part of \AMSLaTeX{} \CTANref{amslatex}
+\item[bm.sty]Distributed as part of \CTANref{2etools}[bm]
+\item[amsbsy.sty]Distributed as part of \AMSLaTeX{} \CTANref{amslatex}[amsbsy]
\item[amsmath.sty]Distributed as part of \AMSLaTeX{}
- \CTANref{amslatex}
+ \CTANref{amslatex}[amsmath]
\end{ctanrefs}
\Question[Q-prinvalint]{The Principal Value Integral symbol}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex
index b89d2a25b94..8eb21040059 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex
@@ -1,4 +1,4 @@
-% $Id: faq-t-g-wr.tex,v 1.4 2010/01/21 21:01:42 rf10 Exp rf10 $
+% $Id: faq-t-g-wr.tex,v 1.5 2010/03/26 22:48:51 rf10 Exp rf10 $
\section{Things are Going Wrong\dots{}}
@@ -102,7 +102,7 @@ program for other systems (including Windows, nowadays).
\item[m-pictex.sty]Distributed as part of \CTANref{context-tmf}
\item[m-pictex.tex]Distributed as part of \CTANref{context-tmf}
\item[MathsPic]\CTANref{mathspic}
-\item[pictexwd.sty]Distributed as part of \CTANref{pictex-addon}
+\item[pictexwd.sty]Distributed as part of \CTANref{pictex-addon}[pictexwd]
\end{ctanrefs}
\subsection{Making things stay where you want them}
@@ -187,7 +187,7 @@ equally well to tables, or to ``non-standard'' floats defined by the
the job for you.
\end{itemize}
\begin{ctanrefs}
-\item[afterpage.sty]Distributed as part of \CTANref{2etools}
+\item[afterpage.sty]Distributed as part of \CTANref{2etools}[afterpage]
\item[endfloat.sty]\CTANref{endfloat}
\item[flafter.sty]Part of the \LaTeX{} distribution
\item[float.sty]\CTANref{float}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-texsys.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-texsys.tex
index c0f0b1aff6c..fbbcbcf83ef 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-texsys.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-texsys.tex
@@ -1,4 +1,4 @@
-% $Id: faq-texsys.tex,v 1.2 2009/12/18 01:06:03 rf10 Exp rf10 $
+% $Id: faq-texsys.tex,v 1.3 2010/03/17 21:59:55 rf10 Exp $
\section{\TeX{} Systems}
@@ -128,9 +128,9 @@ see \Qref{}{Q-commercial} for details of commercial packages.
\TeX{}, which further the focus.
\begin{ctanrefs}
\item[bakoma]\CTANref{bakoma-tex}
- \item[miktex]\CTANref{miktex}; acquire \CTANref{miktex-setup} (also
- available from the \miktex{} web site), and read installation
- instructions from % ! line break
+ \item[miktex]\CTANref{miktex}; % ! line break so only on \CTANref on line
+ acquire \CTANref{miktex-setup} (also available from the \miktex{}
+ web site), and read installation instructions from % ! line break
\href{http://www.miktex.org/2.8/setup}{the \miktex{} installation page}
\item[\nothtml{\bgroup\rmfamily}Portable\nothtml{\egroup} miktex]\CTANref{miktex-portable}
\item[protext.exe]\CTANref{protext}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-the-end.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-the-end.tex
index 80f62200f31..7e6feabdb31 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-the-end.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-the-end.tex
@@ -1,4 +1,4 @@
-% $Id: faq-the-end.tex,v 1.1 2009/06/13 20:56:49 rf10 Exp rf10 $
+% $Id: faq-the-end.tex,v 1.1 2009/06/13 20:56:49 rf10 Exp $
\section{You're still stuck?}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex
index ddcbfa84c1c..161e96497de 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex
@@ -1,4 +1,4 @@
-% $Id: faq-wdidt.tex,v 1.2 2009/10/09 18:20:46 rf10 Exp rf10 $
+% $Id: faq-wdidt.tex,v 1.4 2010/03/26 22:48:51 rf10 Exp rf10 $
\section{Why does it \emph{do} that?}
@@ -332,7 +332,7 @@ be had by saying:
\end{quote}
\begin{ctanrefs}
\item[expdlist.sty]\CTANref{expdlist}
-\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}
+\item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}[mdwlist]
\end{ctanrefs}
% other instances: \[no]linebreak in vertical mode
@@ -366,7 +366,7 @@ whole requirement is to patch the output routine; no extra commands
are needed.
\begin{ctanrefs}
\item[dblfloatfix.sty]\CTANref{dblfloatfix}
-\item[fix2col.sty]Distributed as part of \CTANref{carlisle}
+\item[fix2col.sty]\CTANref{fix2col}
\item[fixltx2e.sty]Part of the \LaTeX{} distribution
\end{ctanrefs}
@@ -1119,7 +1119,7 @@ which can be confusing, notably to a collaborating author
don't). Of course, no command built into \LaTeX{} or into any
``standard'' class or package will use \csx{xspace}.
\begin{ctanrefs}
-\item[xspace.sty]Distributed as part of \CTANref{2etools}
+\item[xspace.sty]Distributed as part of \CTANref{2etools}[xspace]
\end{ctanrefs}
\Question[Q-overfull]{\AllTeX{} makes overfull lines}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq.sty b/Master/texmf-dist/doc/generic/FAQ-en/faq.sty
index ff33448b021..8e8e47fb805 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq.sty
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq.sty
@@ -170,11 +170,15 @@
\ifpdf
\includecomment{pdfversion}
\includecomment{wideversion}
+ \includecomment{hyperversion}
+ \excludecomment{flatversion}
\excludecomment{dviversion}
\excludecomment{narrowversion}
\else
\excludecomment{pdfversion}
\excludecomment{wideversion}
+ \excludecomment{hyperversion}
+ \includecomment{flatversion} % non-hyper
\includecomment{dviversion}
\includecomment{narrowversion}
\fi
@@ -628,12 +632,16 @@
\newcounter{CTAN@replabs}%
%
% the command itself
-\DeclareRobustCommand{\CTANref}[1]{\@ifundefined{ctan-#1}{%
+\newcommand{\CTANref}[1]{\@ifundefined{ctan-#1}{%
\PackageWarning{CTAN}{Undefined reference: #1}%
\stepcounter{CTAN@unrefs}%
}{%
\csname ctan-#1\endcsname
-}}
+}\futurelet\@let@token\faq@check@trailing@opt}
+\newcommand\faq@check@trailing@opt{\ifx\@let@token[%
+ \expandafter\@gobble@opt\fi
+}
+\def\@gobble@opt[#1]{}
%
% href to a ctan package
\ifpdf
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex b/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex
index b5912c8b754..b5a12a76e48 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex
@@ -1,4 +1,4 @@
-% $Id: filectan.tex,v 1.117 2010/01/23 00:41:09 rf10 Exp rf10 $
+% $Id: filectan.tex,v 1.125 2010/03/23 18:39:39 rf10 Exp rf10 $
%
% protect ourself against being read twice
\csname readCTANfiles\endcsname
@@ -15,45 +15,32 @@
\CTANfile{T1instguide}{info/Type1fonts/fontinstallationguide/fontinstallationguide.pdf}
\CTANfile{TeX-FAQ}{obsolete/help/TeX,_LaTeX,_etc.:_Frequently_Asked_Questions_with_Answers}
\CTANfile{abstract-bst}{biblio/bibtex/utils/bibtools/abstract.bst}
-\CTANfile{anonchap}{macros/latex/contrib/misc/anonchap.sty}[anonchap]
\CTANfile{backgrnd}{macros/generic/misc/backgrnd.tex}[backgrnd]
\CTANfile{bbl2html}{biblio/bibtex/utils/misc/bbl2html.awk}[bbl2html]
\CTANfile{beginlatex-pdf}{info/beginlatex/beginlatex-3.6.pdf}[beginlatex]
\CTANfile{belleek}{fonts/belleek/belleek.zip}[belleek]
\CTANfile{bibtex-faq}{biblio/bibtex/contrib/doc/btxFAQ.pdf}
\CTANfile{bidstobibtex}{biblio/bibtex/utils/bids/bids.to.bibtex}[bidstobibtex]
-\CTANfile{bold-extra}{macros/latex/contrib/misc/bold-extra.sty}
-\CTANfile{braket}{macros/latex/contrib/misc/braket.sty}[braket]
\CTANfile{btxmactex}{macros/eplain/tex/eplain/btxmac.tex}[eplain]
-\CTANfile{cancel}{macros/latex/contrib/misc/cancel.sty}[cancel]
\CTANfile{catalogue}{help/Catalogue/catalogue.html}
\CTANfile{cat-licences}{help/Catalogue/licenses.html}
-\CTANfile{chngcntr}{macros/latex/contrib/misc/chngcntr.sty}
\CTANfile{clsguide}{macros/latex/doc/clsguide.pdf}[clsguide]
\CTANfile{compactbib}{macros/latex/contrib/compactbib/compactbib.sty}[compactbib]
%\CTANfile{compan-ctan}{info/companion.ctan}
\CTANfile{context-tmf}{macros/context/current/cont-tmf.zip}[context]
-\CTANfile{dblfloatfix}{macros/latex/contrib/misc/dblfloatfix.sty}[dblfloatfix]
\CTANfile{dvitype}{systems/knuth/dist/texware/dvitype.web}[dvitype]
\CTANfile{edmetrics}{systems/mac/textures/utilities/EdMetrics.sea.hqx}[edmetrics]
\CTANfile{epsf}{macros/generic/epsf/epsf.tex}[epsf]
-\CTANfile{epslatex_pdf}{info/epslatex/english/epslatex.pdf}[epslatex]
-\CTANfile{epslatex_ps}{info/epslatex/english/epslatex.ps}
-\CTANfile{excludeonly}{macros/latex/contrib/misc/excludeonly.sty}[excludeonly]
\CTANfile{figsinlatex}{obsolete/info/figsinltx.ps}
\CTANfile{finplain}{biblio/bibtex/contrib/misc/finplain.bst}
\CTANfile{fix-cm}{macros/latex/unpacked/fix-cm.sty}[fix-cm]
-\CTANfile{fncylab}{macros/latex/contrib/misc/fncylab.sty}
\CTANfile{fntguide.pdf}{macros/latex/doc/fntguide.pdf}[fntguide]
\CTANfile{fontdef}{macros/latex/base/fontdef.dtx}
\CTANfile{fontmath}{macros/latex/unpacked/fontmath.ltx}
-\CTANfile{framed}{macros/latex/contrib/misc/framed.sty}[framed]
\CTANfile{gentle}{info/gentle/gentle.pdf}[gentle]
\CTANfile{gkpmac}{systems/knuth/local/lib/gkpmac.tex}[gkpmac]
-\CTANfile{hypernat}{macros/latex/contrib/misc/hypernat.sty}[hypernat]
-\CTANfile{ifmtarg}{macros/latex/contrib/misc/ifmtarg.sty}[ifmtarg]
-\CTANfile{import}{macros/latex/contrib/misc/import.sty}[import]
\CTANfile{ispell}{support/ispell/ispell-3.2.06.tar.gz}[ispell]
+\CTANfile{knuth-tds}{macros/latex/contrib/latex-tds/knuth.tds.zip}
\CTANfile{l2tabuen}{info/l2tabu/english/l2tabuen.pdf}[l2tabu-english]
\CTANfile{l2tabuen.src}{info/l2tabu/english/l2tabuen.tex}[l2tabu-english]
\CTANfile{latex209-base}{obsolete/macros/latex209/distribs/latex209.tar.gz}[latex209]
@@ -106,7 +93,6 @@
\CTANfile{setspace}{macros/latex/contrib/setspace/setspace.sty}[setspace]
\CTANfile{simpl-latex}{info/simplified-latex/simplified-intro.ps}[simplified-latex]
\CTANfile{sober}{macros/latex209/contrib/misc/sober.sty}[sober]
-\CTANfile{tabls}{macros/latex/contrib/misc/tabls.sty}[tabls]
\CTANfile{tex2bib}{biblio/bibtex/utils/tex2bib/tex2bib}[tex2bib]
\CTANfile{tex2bib-doc}{biblio/bibtex/utils/tex2bib/README}
\CTANfile{tex4ht}{support/TeX4ht/tex4ht-all.zip}[tex4ht]
@@ -114,7 +100,6 @@
\CTANfile{texlive-windows}{systems/texlive/tlnet/install-tl.zip}
\CTANfile{texnames}{info/biblio/texnames.sty}
\CTANfile{texsis-index}{macros/texsis/index/index.tex}
-\CTANfile{threeparttable}{macros/latex/contrib/misc/threeparttable.sty}[threeparttable]
\CTANfile{titleref}{macros/latex/contrib/misc/titleref.sty}[titleref]
\CTANfile{topcapt}{macros/latex/contrib/misc/topcapt.sty}[topcapt]
\CTANfile{tracking}{macros/latex/contrib/tracking/tracking.sty}[tracking]
@@ -124,10 +109,8 @@
\CTANfile{upquote}{macros/latex/contrib/upquote/upquote.sty}[upquote]
\CTANfile{faq-a4}{help/uk-tex-faq/newfaq.pdf}
\CTANfile{faq-letter}{help/uk-tex-faq/letterfaq.pdf}
-\CTANfile{ulem}{macros/latex/contrib/misc/ulem.sty}[ulem]
\CTANfile{underscore}{macros/latex/contrib/misc/underscore.sty}[underscore]
\CTANfile{varwidth}{macros/latex/contrib/misc/varwidth.sty}[varwidth]
-\CTANfile{verbdef}{macros/latex/contrib/misc/verbdef.sty}[verbdef]
\CTANfile{version}{macros/latex/contrib/misc/version.sty}[version]
\CTANfile{versions}{macros/latex/contrib/versions/versions.sty}[versions]
\CTANfile{vertbars}{macros/latex/contrib/misc/vertbars.sty}[vertbars]
@@ -135,7 +118,6 @@
\CTANfile{vf-knuth}{info/knuth/virtual-fonts}[vf-knuth]
\CTANfile{visualFAQ}{info/visualFAQ/visualFAQ.pdf}[visualfaq]
\CTANfile{voss-mathmode}{info/math/voss/mathmode/Mathmode.pdf}
-\CTANfile{vruler}{macros/latex/contrib/misc/vruler.sty}[vruler]
\CTANfile{wujastyk-txh}{digests/texhax/txh/wujastyk.txh}
\CTANfile{xampl-bib}{biblio/bibtex/distribs/doc/xampl.bib}
\CTANfile{xtexcad}{graphics/xtexcad/xtexcad-2.4.1.tar.gz}
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex b/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex
index 6216173ea85..625797b2b9e 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex
@@ -1,4 +1,4 @@
-\def\faqfileversion{3.19c} \def\faqfiledate{2010-01-08}
+\def\faqfileversion{3.19d} \def\faqfiledate{2010-04-02}
%
% The above line defines the file version and date, and must remain
% the first line with any `assignment' in the file, or things will
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfloat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfloat.html
index 319fa4e9f9b..073004c06e4 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfloat.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfloat.html
@@ -2,13 +2,13 @@
UK TeX FAQ -- question label 2colfloat
Placing two-column floats at bottom of page
-You specified placement ‘[htbp]
’ for your full-width figure or
-table, but they always get placed at the top of the page… Well,
+You specified placement ‘[htbp]
’ for your full-width figure or
+table, but they always get placed at the top of the page… Well,
it is what the documentation says: LaTeX, unadorned, only
allows full-width floats at the top of a page, or occupying (part of) a
float page.
The stfloats package ameliorates the situation somewhat, and
-makes LaTeX honour ‘[b]’ placement as well; the
+makes LaTeX honour ‘[b]’ placement as well; the
dblfloatfix package combines a tidied version of the changes
made in stfloats with the
@@ -18,17 +18,17 @@ made in stfloats with the
is that the float will appear, at its earliest, on the page after it
is specified. This has two undesirable side-effects: first, there may
be no bottom float on the first page of a document, and second, float
-numbers may become “entangled” (particularly if you’re using
+numbers may become “entangled” (particularly if you’re using
dblfloatfix that ensures that the early-specified bottom
float is set before any single column floats).
-(The FAQ team doesn’t know of any package that will make
-LaTeX honour ‘[h]’ placement of double-column floats, but the
+(The FAQ team doesn’t know of any package that will make
+LaTeX honour ‘[h]’ placement of double-column floats, but the
midfloat package can be pressed into service to provide
something approximating the effect it would have.)
-- dblfloatfix.sty
- macros/latex/contrib/misc/dblfloatfix.sty
-
- stfloats.sty, midfloat.sty
- Distributed as part of
- macros/latex/contrib/sttools (or browse the directory)
+
- dblfloatfix.sty
- macros/latex/contrib/dblfloatfix (or browse the directory)
+
- midfloat.sty
- Distributed as part of macros/latex/contrib/sttools (or browse the directory); catalogue entry
+
- stfloats.sty
- Distributed as part of macros/latex/contrib/sttools (or browse the directory); catalogue entry
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfloat
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfltorder.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfltorder.html
index 2e26817db6b..d396d5ff00c 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfltorder.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2colfltorder.html
@@ -2,9 +2,9 @@
UK TeX FAQ -- question label 2colfltorder
Two-column float numbers out of order
-When LaTeX can’t place a float immediately, it places it on one of
-several “defer” lists. If another float of the same type comes
-along, and the “defer” list for that type still has something in it,
+When LaTeX can’t place a float immediately, it places it on one of
+several “defer” lists. If another float of the same type comes
+along, and the “defer” list for that type still has something in it,
the later float has to wait for everything earlier in the list.
Now, standard LaTeX has different lists for single-column floats,
and double-column floats; this means that single-column figures can
@@ -13,7 +13,7 @@ figures appear in the document before early ones. The same is true,
of course, for tables, or for any user-defined float.
The LaTeX team recognise the problem, and provides a package
(fixltx2e) to deal with it. Fixltx2e amalgamates
-the two defer lists, so that floats don’t get out of order.
+the two defer lists, so that floats don’t get out of order.
For those who are still running an older LaTeX distribution, the
package fix2col should serve. This package (also by a
member of the LaTeX team) was the basis of the relevant part of
@@ -24,8 +24,8 @@ at [b]
placement.
whole requirement is to patch the output routine; no extra commands
are needed.
-- dblfloatfix.sty
- macros/latex/contrib/misc/dblfloatfix.sty
-
- fix2col.sty
- Distributed as part of macros/latex/contrib/carlisle (or browse the directory)
+
- dblfloatfix.sty
- macros/latex/contrib/dblfloatfix (or browse the directory)
+
- fix2col.sty
- macros/latex/contrib/fix2col (or browse the directory)
- fixltx2e.sty
- Part of the LaTeX distribution
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfltorder
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2letterfontcmd.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2letterfontcmd.html
index c84861521e0..ee10b070a16 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2letterfontcmd.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-2letterfontcmd.html
@@ -1,7 +1,7 @@
UK TeX FAQ -- question label 2letterfontcmd
-What’s wrong with \
bf
, \
it
, etc.?
+What’s wrong with \
bf
, \
it
, etc.?
The font-selection commands of LaTeX 2.09 were \
rm
, \
sf
,
\
tt
, \
it
, \
sl
, \
em
and \
bf
; they were modal
commands, so you used them as:
@@ -41,10 +41,10 @@ LaTeX2e font selections with the old style commands:
ignores the \
textbf
that encloses the text, and produces
typewriter text at medium weight.
-
So why are these commands deprecated? — it is because of confusions
+So why are these commands deprecated? — it is because of confusions
such as that in the last example. The alternative (LaTeX2e)
commands are discussed in the rest of this answer.
-LaTeX2e’s font commands come in two forms: modal commands and
+LaTeX2e’s font commands come in two forms: modal commands and
text-block commands. The default set of modal commands offers weights
\
mdseries
and \
bfseries
, shapes \
upshape
,
\
itshape
, \
scshape
and \
slshape
, and families
@@ -68,7 +68,7 @@ in the default Computer Modern fonts), or
(note the italic correction needed on slanted fonts, too).
-
LaTeX2e’s text block commands take the first two letters of the
+LaTeX2e’s text block commands take the first two letters of the
modal commands, and form a \
text
xx
command from
them. Thus \
bfseries
becomes \
textbf{
text}
,
\
itshape
becomes \
textit{
text}
, and \
ttfamily
@@ -98,19 +98,19 @@ for a bold slanted instance of the current family (note the italic
correction applied at the end of the modal command group, again).
The new commands (as noted above) override commands of the same type.
In almost all cases, this merely excludes ludicrous ideas such as
-“upright slanted” fonts, or “teletype roman” fonts. There are a
+“upright slanted” fonts, or “teletype roman” fonts. There are a
couple of immediate oddities, though. The first is the conflict
between \
itshape
(or \
slshape
) and \
scshape
: while many
claim that an italic small-caps font is typographically unsound, such
-fonts do exist. Daniel Taupin’s smallcap package enables
+fonts do exist. Daniel Taupin’s smallcap package enables
use of the instances in the EC fonts, and
similar techniques could be brought to bear on many other font sets.
The second is the conflict between \
upshape
and \
itshape
:
Knuth actually offers an upright-italic font which LaTeX uses for
-the “£” symbol in the default font set. The combination is
-sufficiently weird that, while there’s a defined font shape, no
+the “£” symbol in the default font set. The combination is
+sufficiently weird that, while there’s a defined font shape, no
default LaTeX commands exist; to use the shape, the (eccentric) user
-needs LaTeX’s simplest font selection commands:
+needs LaTeX’s simplest font selection commands:
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-8000.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-8000.html
index 77549595a86..38664125d46 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-8000.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-8000.html
@@ -2,23 +2,23 @@
UK TeX FAQ -- question label 8000
Mismatched mode ljfour and resolution 8000
-You’re running dvips, and you encounter a stream of error
-messages, starting with “Mismatched mode
”. The mode is the
-default used in your installation — it’s set in the dvips
-configuration file, and ljfour
is commonest (since it’s the
+You’re running dvips, and you encounter a stream of error
+messages, starting with “Mismatched mode
”. The mode is the
+default used in your installation — it’s set in the dvips
+configuration file, and ljfour
is commonest (since it’s the
default in most distributions), but not invariable.
The problem is that dvips has encountered a font for which
-it must generate a bitmap (since it can’t find it in Type 1 format),
+it must generate a bitmap (since it can’t find it in Type 1 format),
and there is no proforma available to provide instructions to give to
Metafont.
-So what to do? The number 8000 comes from the ‘-Ppdf
’ option
+So what to do? The number 8000 comes from the ‘-Ppdf
’ option
to dvips, which you might have found from the answer
-“wrong type of fonts”. The obvious
-solution is to switch to the trivial substitute ‘-Pwww
’,
+“wrong type of fonts”. The obvious
+solution is to switch to the trivial substitute ‘-Pwww
’,
which selects the necessary type 1 fonts for PDF generation,
but nothing else: however, this will leave you with undesirable bitmap
-fonts in your PDF file. The “proper” solution is to find a
+fonts in your PDF file. The “proper” solution is to find a
way of expressing what you want to do, using type 1 fonts.
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=8000
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-AMSpkg.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-AMSpkg.html
index 2f1467c4829..810472f8285 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-AMSpkg.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-AMSpkg.html
@@ -3,8 +3,8 @@
What are the AMS packages (AMSTeX, etc.)?
AMSTeX is a TeX macro package, originally written by Michael Spivak for
-the American Mathematical Society (AMS) during 1983–1985 and
-is described in the book “The Joy of TeX”.
+the American Mathematical Society (AMS) during 1983–1985 and
+is described in the book “The Joy of TeX”.
It is based on Plain TeX, and provides many
features for producing more professional-looking maths formulas with
less burden on authors. It pays attention to the finer details of
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-BibTeXing.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-BibTeXing.html
index c5029e60f5b..53aa29d2a40 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-BibTeXing.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-BibTeXing.html
@@ -4,13 +4,13 @@
BibTeX Documentation
BibTeX, a program originally designed to produce bibliographies in
conjunction with LaTeX, is explained in Section 4.3 and Appendix B
-of Leslie Lamport’s LaTeX manual.
-The document “BibTeXing”, contained in the file btxdoc.tex,
-expands on the chapter in Lamport’s book. The LaTeX Companion
+of Leslie Lamport’s LaTeX manual.
+The document “BibTeXing”, contained in the file btxdoc.tex,
+expands on the chapter in Lamport’s book. The LaTeX Companion
also has information on BibTeX and writing BibTeX style files.
(See TeX-related books for details of both
books.)
-The document “Designing BibTeX Styles”, contained in the file
+The document “Designing BibTeX Styles”, contained in the file
btxhak.tex, explains the postfix stack-based language used to
write BibTeX styles (.bst files). The file btxbst.doc
is the template for the four standard styles (plain,
@@ -18,7 +18,7 @@ is the template for the four standard styles (plain,
contains their documentation. The complete BibTeX documentation
set (including all the files above) is available on CTAN.
A useful tutorial of the whole process of using BibTeX is Nicolas
-Markey’s “Tame the BeaST (The B to X of BibTeX)”, which
+Markey’s “Tame the BeaST (The B to X of BibTeX)”, which
may also be found on CTAN. A summary and FAQ
(btxFAQ), by Michael Shell and David Hoadley, is also to be
recommended.
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-CD.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-CD.html
index 893c7410cfa..f13024d1208 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-CD.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-CD.html
@@ -2,7 +2,7 @@
UK TeX FAQ -- question label CD
The TeX collection
-If you don’t have access to the Internet, there are obvious
+If you don’t have access to the Internet, there are obvious
attractions to TeX collections on a disc. Even those with net
access will find large quantities of TeX-related files to hand a
great convenience.
@@ -18,7 +18,7 @@ is distributed on DVD, and contains:
the TeXShop front-end
and other Mac-specific tools;
ProTeXt: an easy to install TeX system for Windows, based
- on MiKTeX, and including an ‘active’ document to guide
+ on MiKTeX, and including an ‘active’ document to guide
installation; and
A snapshot of CTAN.
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ECfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ECfonts.html
index e299fe90683..279d0c38daf 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ECfonts.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ECfonts.html
@@ -8,18 +8,18 @@ the encoding is used as an index into tables within the font. For
various reasons, Knuth chose deeply eccentric encodings for his
Computer Modern family of fonts; in particular, he chose different
encodings for different fonts, so that the application using the fonts
-has to remember which font of the family it’s using before selecting a
+has to remember which font of the family it’s using before selecting a
particular glyph.
When TeX version 3 arrived, most of the excuses for the
-eccentricity of Knuth’s encodings went away, and at TUG’s Cork
+eccentricity of Knuth’s encodings went away, and at TUG’s Cork
meeting, an encoding for a set of 256 glyphs, for use in TeX text,
-was defined. The intention was that these glyphs should cover ‘most’
+was defined. The intention was that these glyphs should cover ‘most’
European languages that use Latin alphabets, in the sense of including
-all accented letters needed. (Knuth’s CMR fonts missed things
+all accented letters needed. (Knuth’s CMR fonts missed things
necessary for Icelandic and Polish, for example, but the Cork
-fonts have them. Even Cork’s coverage isn’t complete: it misses
+fonts have them. Even Cork’s coverage isn’t complete: it misses
letters from Romanian, Eastern and Northern Sami, and Welsh, at
-least. The Cork encoding does contain “NG” glyphs that
+least. The Cork encoding does contain “NG” glyphs that
allows it to support Southern Sami.) LaTeX refers to the
Cork encoding as T1, and
provides the means to use fonts thus encoded to avoid problems with
@@ -28,7 +28,7 @@ the interaction of accents and hyphenation
The only Metafont-fonts that conform to the Cork encoding are the
EC fonts. They look CM-like, though their metrics
differ from CM-font metrics in several areas. The fonts are
-now regarded as ‘stable’ (in the same sense that the CM fonts
+now regarded as ‘stable’ (in the same sense that the CM fonts
are stable: their metrics are unlikely ever to change). Their serious
disadvantages for the casual user are their size (each EC font
is roughly twice the size of the corresponding CM font), and
@@ -38,26 +38,26 @@ versions of the fonts, but EC or EC-equivalent fonts in
Type 1 or TrueType form (the latter only from
commercial suppliers).
-Free auto-traced versions — the CM-super
+Free auto-traced versions — the CM-super
and the LGC fonts, and the Latin Modern series (rather
directly generated from Metafont sources), are available.
-Note that the Cork encoding doesn’t cover mathematics (and neither do
-“T1-encoded” font families, of course). If you’re using
-Computer-Modern-alike fonts, this doesn’t actually matter: your system
+Note that the Cork encoding doesn’t cover mathematics (and neither do
+“T1-encoded” font families, of course). If you’re using
+Computer-Modern-alike fonts, this doesn’t actually matter: your system
will have the original Computer Modern mathematical fonts (or the those
-distributed with the Latin Modern set), which cover ‘basic’
+distributed with the Latin Modern set), which cover ‘basic’
TeX mathematics; more advanced mathematics are likely to need
separate fonts anyway. Suitable mathematics fonts for use with other
font families are discussed in
-“choice of scalable fonts”.
+“choice of scalable fonts”.
The EC fonts are distributed with a
-set of ‘Text Companion’ (TC) fonts that provide glyphs for
+set of ‘Text Companion’ (TC) fonts that provide glyphs for
symbols commonly used in text. The TC fonts are encoded
according to the LaTeX TS1 encoding, and are not viewed as
-‘stable’ in the same way as are the EC fonts are.
+‘stable’ in the same way as are the EC fonts are.
The Cork encoding is also implemented by virtual fonts provided in the
PSNFSS system, for Adobe Type 1 fonts, and
also by most other such fonts that have been developed (or otherwise
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-HPdrivers.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-HPdrivers.html
index 2ba04cf2681..4e82d3ae841 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-HPdrivers.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-HPdrivers.html
@@ -7,7 +7,7 @@ contains a driver for the LaserJet, dvihplj.
Version 2.10 of the Beebe drivers supports the LaserJet. These drivers
will compile under Unix, VMS, and on the Atari ST and
DEC-20s.
-For Unix systems, Karl Berry’s dviljk uses the same
+For Unix systems, Karl Berry’s dviljk uses the same
path-searching library as web2c.
- Beebe drivers
- dviware/beebe (or browse the directory)
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html
index 10fc2d614f4..5d229b72974 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html
@@ -6,30 +6,30 @@
documents. However, it is important to realize the difference
between page layout and functional markup. TeX is capable of
extremely detailed page layout; HTML is not, because HTML is a
-functional markup language not a page layout language. HTML’s exact
+functional markup language not a page layout language. HTML’s exact
rendering is not specified by the document that is published but is, to
some degree, left to the discretion of the browser. If you require your
readers to see an exact replication of what your document looks like
to you, then you cannot use HTML and you must use some other
publishing format such as PDF. That is true for any HTML
authoring tool.
-TeX’s excellent mathematical capabilities remain a challenge in the
+TeX’s excellent mathematical capabilities remain a challenge in the
business of conversion to HTML. There are only two generally
reliable techniques for generating mathematics on the web: creating
-bitmaps of bits of typesetting that can’t be translated, and using
+bitmaps of bits of typesetting that can’t be translated, and using
symbols and table constructs. Neither technique is entirely
satisfactory. Bitmaps lead to a profusion of tiny files, are slow to
load, and are inaccessible to those with visual disabilities. The
symbol fonts offer poor coverage of mathematics, and their use
requires configuration of the browser. The future of mathematical
-browsing may be brighter — see
+browsing may be brighter — see
future Web technologies.
For today, possible packages are:
- LaTeX2HTML
- a Perl script package that
supports LaTeX only, and generates mathematics (and other
- “difficult” things) using bitmaps. The original version was
+ “difficult” things) using bitmaps. The original version was
written by Nikos Drakos for Unix systems, but the package now sports
an illustrious list of co-authors and is also available for Windows
systems. Michel Goossens and Janne Saarela published a detailed
@@ -48,8 +48,8 @@ browsing may be brighter — see
bitmaps for mathematics, but can also use other technologies where
appropriate. Written by Eitan Gurari, it parses the DVI
file generated when you run (La)TeX over your file with
- tex4ht’s macros included. As a result, it’s pretty
- robust against the macros you include in your document, and it’s
+ tex4ht’s macros included. As a result, it’s pretty
+ robust against the macros you include in your document, and it’s
also pretty fast.
- plasTeX
- a Python-based LaTeX document processing
framework. It gives DOM-like access to a LaTeX document, as
@@ -62,7 +62,7 @@ browsing may be brighter — see
- Hevea
- a compiled program that supports LaTeX
only, and uses the font/table technique for equations (indeed its
entire approach is very similar to TtH). It is written
- in Objective CAML by Luc Maranget. Hevea isn’t
+ in Objective CAML by Luc Maranget. Hevea isn’t
archived on CTAN; details (including download points) are
available via http://pauillac.inria.fr/~maranget/hevea/
@@ -70,8 +70,8 @@ An interesting set of samples, including conversion of the same text
by the four free programs listed above, is available at
http://www.mayer.dial.pipex.com/samples/example.htm; a linked
page gives lists of pros and cons, by way of comparison.
-The World Wide Web Consortium maintains a list of “filters” to
-HTML, with sections on (La)TeX and BibTeX — see
+The World Wide Web Consortium maintains a list of “filters” to
+HTML, with sections on (La)TeX and BibTeX — see
http://www.w3.org/Tools/Word_proc_filters.html
- latex2html
- Browse support/latex2html/
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX3.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX3.html
index 496ff116c8c..2323bf667f5 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX3.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX3.html
@@ -9,27 +9,27 @@ principles pioneered by Leslie Lamport in the current LaTeX. The
new system is (provisionally) called LaTeX3; it
will remain freely available and it will be fully documented at
all levels.
-The LaTeX team’s first product (LaTeX2e) was delivered in 1994
-(it’s now properly called “LaTeX”, since no other version is current).
+The LaTeX team’s first product (LaTeX2e) was delivered in 1994
+(it’s now properly called “LaTeX”, since no other version is current).
LaTeX2e was intended as a consolidation exercise, unifying several
-sub-variants of LaTeX while changing nothing whose change wasn’t
+sub-variants of LaTeX while changing nothing whose change wasn’t
absolutely necessary. This has permitted the team to support a single
version of LaTeX, in parallel with development of LaTeX3.
Some of the older discussion papers about directions for LaTeX3 are
to be found on CTAN; other (published) articles are to be found
on the project web site (http://www.latex-project.org/papers/),
-as is some of the project’s experimental code (see
+as is some of the project’s experimental code (see
http://www.latex-project.org/code.html, which allows you to read
-the project’s source repository). Snapshots of two major collections
+the project’s source repository). Snapshots of two major collections
from the code, expl3 (supporting LaTeX3 coding
conventions in a LaTeX2e environment) and and xpackages (a
-first cut of a “document designer’s interface”) are available on
+first cut of a “document designer’s interface”) are available on
CTAN. Several developers are known to be working on their own
code using expl3, but all
Anyone may participate in discussions of the future of LaTeX
through the mailing list
latex-l
; some development work
(outside the project) is discussed on the list. Subscribe to the list
-by sending a message ‘subscribe latex-l <your name>
’
+by sending a message ‘subscribe latex-l <your name>
’
to listserv@urz.Uni-Heidelberg.de
- expl3 bundle
- macros/latex/contrib/expl3 (or browse the directory)
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXandPlain.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXandPlain.html
index ab94f60b823..edd9d9414c7 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXandPlain.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXandPlain.html
@@ -4,11 +4,11 @@
How does LaTeX relate to Plain TeX?
LaTeX is a program written in the programming language TeX. (In
the same sense, any LaTeX document is also a program, which is
-designed to run ‘alongside’, or ‘inside’ LaTeX, whichever metaphor
+designed to run ‘alongside’, or ‘inside’ LaTeX, whichever metaphor
you prefer.)
Plain TeX is also a program written in the programming language
TeX.
-Both exist because writing your documents in ‘raw’ TeX would
+Both exist because writing your documents in ‘raw’ TeX would
involve much reinventing of wheels for every document. They both
serve as convenient aids to make document writing more pleasant:
LaTeX is a far more extensive aid.
@@ -18,7 +18,7 @@ minor modifications (though some will require substantial work).
Interpretation of any (La)TeX program involves some data-driven
elements, and LaTeX has a wider range of such elements than does
Plain TeX. As a result, the mapping from LaTeX to Plain TeX
-is far less clear than that in the other direction — see a later
+is far less clear than that in the other direction — see a later
answer about translating to Plain TeX.
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeXandPlain
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXtoPlain.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXtoPlain.html
index ac18ce88ac6..b0eb3ad36c4 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXtoPlain.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeXtoPlain.html
@@ -2,9 +2,9 @@
UK TeX FAQ -- question label LaTeXtoPlain
Translating LaTeX to Plain TeX
-Unfortunately, no “general”, simple, automatic process is likely to
+Unfortunately, no “general”, simple, automatic process is likely to
succeed at this task. See
-“How does LaTeX relate to Plain TeX”
+“How does LaTeX relate to Plain TeX”
for further details.
Translating a document designed to work with LaTeX into one
designed to work with Plain TeX is likely to amount to carefully
@@ -17,12 +17,12 @@ LaTeX graphics package to Plain TeX. However, while
Eplain system a useful source of code. (In fact,
a light-weight system such as Eplain might reasonably be adopted as
an alternative target of translation, though it undoubtedly gives the
-user more than the “bare minimum” that Plain TeX is designed to
+user more than the “bare minimum” that Plain TeX is designed to
offer.)
- \latexhtml{\textrm{The}}{The} eplain system
-
macros/eplain (or browse the directory)
-
- \latexhtml{\textrm{‘Plain TeX’}}{Plain TeX} graphics
-
+
- \latexhtml{\textrm{‘Plain TeX’}}{Plain TeX} graphics
-
macros/plain/graphics (or browse the directory)
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MF.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MF.html
index 45a0be06dd8..373eadc5088 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MF.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MF.html
@@ -5,13 +5,13 @@
Metafont was written by Knuth as a companion to TeX; whereas TeX
defines the layout of glyphs on a page, Metafont defines the shapes of
the glyphs and the relations between them. Metafont details the sizes of
-glyphs, for TeX’s benefit, and details the rasters used to
+glyphs, for TeX’s benefit, and details the rasters used to
represent the glyphs, for the benefit of programs that will produce
printed output as post processes after a run of TeX.
-Metafont’s language for defining fonts permits the expression of several
+Metafont’s language for defining fonts permits the expression of several
classes of things: first (of course), the simple geometry of the
glyphs; second, the properties of the print engine for which the
-output is intended; and third, ‘meta’-information which can
+output is intended; and third, ‘meta’-information which can
distinguish different design sizes of the same font, or the difference
between two fonts that belong to the same (or related) families.
Knuth (and others) have designed a fair range of fonts using Metafont,
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MP.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MP.html
index c4ccf432443..46d8c42e3a4 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MP.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-MP.html
@@ -12,10 +12,10 @@ mathematics with the graphics. (Knuth tells us that he uses nothing
but MetaPost for diagrams in text that he is writing.)
Although PDFLaTeX cannot ordinarily handle PostScript graphics, the
output of MetaPost is sufficiently simple and regular that PDFLaTeX
-can handle it direct, using code borrowed from ConTeXt — see
+can handle it direct, using code borrowed from ConTeXt — see
graphics in PDFLaTeX.
-Much of MetaPost’s source code was copied from Metafont’s sources, with
-Knuth’s permission.
+Much of MetaPost’s source code was copied from Metafont’s sources, with
+Knuth’s permission.
A mailing list discussing MetaPost is available;
subscribe via the
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-PSpreview.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-PSpreview.html
index a04b2b25ff3..496b537cdf1 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-PSpreview.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-PSpreview.html
@@ -12,7 +12,7 @@ displaying bitmap PK fonts, but current versions of
Other (free) previewers of the current generation offer automatic
generation of the requisite PK files (using gsftopk,
-or similar, behind the scenes). If your previewer isn’t capable of
+or similar, behind the scenes). If your previewer isn’t capable of
this, you have three options:
- Convert the DVI file to PostScript and use a
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-RCS.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-RCS.html
index f8a079ed388..768c9223799 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-RCS.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-RCS.html
@@ -20,14 +20,14 @@ following minimal solution:
\def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}}
-\RCS$Revision: 1.7 $ % or any RCS keyword
-\RCS$Date: 2010/01/19 22:44:39 $
+\RCS$Revision: 1.13 $ % or any RCS keyword
+\RCS$Date: 2010/04/02 18:20:00 $
...
\date{Revision \RCSRevision, \RCSDate}
-
If you’ve entered the brave new world of Subversion, the
+If you’ve entered the brave new world of Subversion, the
package svn may be for you. It has explicit cleverness
about dealing with dates:
@@ -51,8 +51,8 @@ cause \
maketitle
use the date that has been written in
svn but with a rather different focus. Svninfo
does the date trick that svn performs (controlled by a
package option), and can set up page foot-lines using
-package fancyhdr. There isn’t much to
-choose between the two packages: you should read the packages’
+package fancyhdr. There isn’t much to
+choose between the two packages: you should read the packages’
documentation to see which suits you best.
An alternative script-based approach to version control has been taken
by the vc bundle, that in certain situations might work more
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-SGML2TeX.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-SGML2TeX.html
index c24234e51a2..9e1cb205a95 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-SGML2TeX.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-SGML2TeX.html
@@ -10,7 +10,7 @@ transformations and formatting,
but this has not yet been widely implemented. Some SGML authoring
systems (e.g., SoftQuad Author/Editor) have formatting
abilities, and
-there are high-end specialist SGML typesetting systems (e.g., Miles33’s
+there are high-end specialist SGML typesetting systems (e.g., Miles33’s
Genera). However, the majority of SGML users probably transform
the source to an existing typesetting system when they want to print.
TeX is a good candidate for this. There are three approaches to writing a
@@ -24,7 +24,7 @@ translator:
They are expensive, but powerful, incorporating SGML query and
transformation abilities as well as simple translation.
- Build a translator on top of an existing SGML parser. By far
- the best-known (and free!) parser is James Clark’s
+ the best-known (and free!) parser is James Clark’s
nsgmls, and this produces a much simpler output format,
called ESIS, which can be parsed quite straightforwardly (one also
has the benefit of an SGML parse against the DTD). Two
@@ -32,25 +32,25 @@ translator:
-
- David Megginson’s
+ David Megginson’s
sgmlspm,
written in Perl 5.
-
- Joachim Schrod and Christine Detig’s
+ Joachim Schrod and Christine Detig’s
STIL,
- (‘SGML Transformations in Lisp’).
+ (‘SGML Transformations in Lisp’).
- Both of these allow the user to write ‘handlers’ for every SGML
+ Both of these allow the user to write ‘handlers’ for every SGML
element, with plenty of access to attributes, entities, and
information about the context within the document tree.
- If these packages don’t meet your needs for an average SGML
+ If these packages don’t meet your needs for an average SGML
typesetting job, you need the big commercial stuff.
Since HTML is simply an example of SGML, we do not need a specific
system for HTML. However, Nathan Torkington developed
-html2latex from the HTML parser in NCSA’s
+html2latex from the HTML parser in NCSA’s
Xmosaic package.
The program takes an HTML file and generates a LaTeX file from it.
The conversion code is subject to NCSA restrictions, but the whole
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TUGstar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TUGstar.html
index f33711fd008..61aecddd166 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TUGstar.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TUGstar.html
@@ -8,23 +8,23 @@ journal TUGboat continues in regular publication
with articles about TeX, Metafont and related technologies, and about
document design, processing and production. TUG holds a yearly
conference, whose proceedings are published in TUGboat.
-TUG’s web site is a valuable
+TUG’s web site is a valuable
resource for all sorts of
TeX-related matters, such as details of TeX software, and lists
of TeX vendors and TeX consultants. Back articles from
TUGboat are slowly (subject to copyright issues, etc.)
making their way to the site, too.
-Some time ago, TUG established a “technical council”, whose
+Some time ago, TUG established a “technical council”, whose
task was to oversee the development of TeXnical projects. Most
such projects nowadays go on their way without any support from
-TUG, but TUG’s web site lists its
+TUG, but TUG’s web site lists its
Technical Working Groups (TWGs).
TUG has a reasonable claim to be considered a world-wide
organisation, but there are many national and regional user groups,
-too; TUG’s web site maintains a list of
+too; TUG’s web site maintains a list of
-“local user groups” (LUGs).
+“local user groups” (LUGs).
Contact TUG itself via:
TeX Users Group
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXfuture.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXfuture.html
index 5d40b681695..46cd3d122b4 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXfuture.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXfuture.html
@@ -7,10 +7,10 @@ he will continue to fix any bugs that are reported to him (though
bugs are rare). This decision was made soon after
TeX version 3.0 was released; at each bug-fix release
the version number acquires one more digit, so that it tends to the
-limit pi (at the time of writing, Knuth’s latest release
+limit pi (at the time of writing, Knuth’s latest release
is version 3.1415926). Knuth wants TeX to be frozen at
version pi when he dies; thereafter, no further changes
-may be made to Knuth’s source. (A similar rule is applied to Metafont;
+may be made to Knuth’s source. (A similar rule is applied to Metafont;
its version number tends to the limit e, and currently
stands at 2.718281.)
Knuth explains his decision, and exhorts us all to respect it, in a
@@ -24,12 +24,15 @@ projects: see, for example,
to build substantial
new macro packages based on TeX. For the even longer term, there
-are various projects to build a successor to TeX; see, for example,
-the
-
-LuaTeX,
-Omega/Aleph and
-ExTeX
- projects.
+are various projects to build a successor to TeX. The
+e-TeX extension to TeX itself arose from such a
+project (NTS). Another pair of projects, which have delivered
+all the results they are likely to deliver, is the related
+Omega and Aleph. The
+XeTeX system is in principle still under
+development, but is widely used, and the
+LuaTeX project (though with another two years of
+development scheduled) has already delivered a system that is quite
+useful.
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXfuture
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXpronounce.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXpronounce.html
index 2da01c865cf..b9b8ad7b430 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXpronounce.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXpronounce.html
@@ -1,19 +1,19 @@
UK TeX FAQ -- question label TeXpronounce
-How should I pronounce “TeX”?
-The ‘X’ is “really” the Greek letter
+How should I pronounce “TeX”?
+The ‘X’ is “really” the Greek letter
Chi, and is pronounced by
-English-speakers either a bit like the ‘ch’ in the Scots word ‘loch’
-([x] in the IPA) or (at a pinch, if you can’t do the Greek sound) like
-‘k’. It definitely is not pronounced ‘ks’ (the Greek letter with that
-sound doesn’t look remotely like the Latin alphabet ‘X’).
-This curious usage derives from Knuth’s explanation in the TeXbook
-that the name comes from the Greek word for ‘art’ or ‘craft’
-(‘techni’),
-which is the root of the English word ‘technology’. Knuth’s logo for TeX is
+English-speakers either a bit like the ‘ch’ in the Scots word ‘loch’
+([x] in the IPA) or (at a pinch, if you can’t do the Greek sound) like
+‘k’. It definitely is not pronounced ‘ks’ (the Greek letter with that
+sound doesn’t look remotely like the Latin alphabet ‘X’).
+This curious usage derives from Knuth’s explanation in the TeXbook
+that the name comes from the Greek word for ‘art’ or ‘craft’
+(‘techni’),
+which is the root of the English word ‘technology’. Knuth’s logo for TeX is
merely the uppercase version of the first three (Greek) letters of the
-word, jiggled about a bit; we don’t use that logo (and logos like it)
+word, jiggled about a bit; we don’t use that logo (and logos like it)
in this FAQ (see
Typesetting TeX-related logos).
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXpronounce
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXsystems.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXsystems.html
index 4c178a90300..d45900e5b89 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXsystems.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-TeXsystems.html
@@ -6,7 +6,7 @@
We list here the free or shareware packages;
another question addresses
- commercial TeX vendors’ products.
+ commercial TeX vendors’ products.
- Unix
- The only current distribution of TeX for Unix systems
(including GNU/Linux and other free Unix-like systems) is
@@ -15,11 +15,11 @@
Members of many TeX user groups receive copies of the collection
(on DVD), as part of their membership of the groups.
MacOS/X is also a Unix-based system; however users should refer to
- the information below, under item “Mac”.
- TeX Live may also be installed “over the network”; a network
+ the information below, under item “Mac”.
+ TeX Live may also be installed “over the network”; a network
installer is provided, and once you have a system, a manager
(tlmgr) can both keep your installation up-to-date and
- add packages you didn’t install at first.
+ add packages you didn’t install at first.
- texlive
- Browse systems/texlive/
- texlive installer (Unix)
- systems/texlive/tlnet/install-tl-unx.tar.gz
@@ -29,7 +29,7 @@
A free version of the commercial
VTeX extended TeX system is available
for use under Linux, which among other things specialises in direct
- production of PDF from (La)TeX input. Sadly, it’s no
+ production of PDF from (La)TeX input. Sadly, it’s no
longer supported, and the ready-built images are made for use with a
rather ancient Linux kernel.
In addition, the developer of MiKTeX has released a port of the
@@ -49,15 +49,15 @@
The current version is available for file-by-file download (the
HTML files in the directory offer hints on what you need to
get going). MiKTeX can automatically install packages that it
- “knows about”, but that aren’t in your system (it gets them over
+ “knows about”, but that aren’t in your system (it gets them over
the network). Furthermore, users may keep their installation
- up-to-date, over the network: the distribution contains a “package
- manager”, through which the user may select individual packages, or
+ up-to-date, over the network: the distribution contains a “package
+ manager”, through which the user may select individual packages, or
request that every extant update be retrieved.
MiKTeX may also be used in a configuration which involves no
- installation at all: its “portable” distribution may be unpacked
+ installation at all: its “portable” distribution may be unpacked
on a memory stick, and used on any windows computer without making
- any direct use of the hard drive. This is the first “official”
+ any direct use of the hard drive. This is the first “official”
release of such a setup, though a similar object has been available
on the net for some time.
The MiKTeX developers also provide a ready-to-run copy of the
@@ -83,7 +83,7 @@
Windows environment. Configuration is provided so that the
resulting set of programs runs out-of-the-box.
The (Japanese) W32TEX distribution was motivated by
- the needs of Japanese users (Japanese won’t fit in a “simple”
+ the needs of Japanese users (Japanese won’t fit in a “simple”
character set like ASCII, but TeX is based on a version of
ASCII). Despite its origins, W32TEX is said to
be a good bet for Western users, notably those whose disks are short
@@ -96,7 +96,7 @@
is available. If you run CygWin on your Windows machine, you have
the option of using TeX Live, too (you will need the X-server, to
run xdvi). Of course, TeX Live components will look like
- Unix applications (of course, that’s presumably what you wanted),
+ Unix applications (of course, that’s presumably what you wanted),
but TeX under CygWin also reputedly somewhat slower than native
Win32 implementations such as MiKTeX or XEmTeX. The (now
obsolete) teTeX distribution is provided as part of the CygWin
@@ -108,9 +108,9 @@
TeX, which further the focus.
- bakoma
- systems/win32/bakoma/
-
- miktex
- systems/win32/miktex (or browse the directory); acquire systems/win32/miktex/setup/setup.exe (also
- available from the MiKTeX web site), and read installation
- instructions from
+
- miktex
- systems/win32/miktex (or browse the directory);
+ acquire systems/win32/miktex/setup/setup.exe (also available from the MiKTeX
+ web site), and read installation instructions from
the MiKTeX installation page
- Portable miktex
- systems/win32/miktex/setup/miktex-portable.exe
- protext.exe
- systems/win32/protext/
@@ -128,7 +128,7 @@
A version of emTeX, packaged to use a
TDS directory structure, is separately available as
- an emTeX ‘contribution’. Note that neither emTeX itself, nor
+ an emTeX ‘contribution’. Note that neither emTeX itself, nor
emTeXTDS, is maintained. Most users of Microsoft
operating systems, who want an up-to-date (La)TeX system, need to
migrate to Win32-based systems.
@@ -184,7 +184,7 @@
A useful
resource for Mac users
- has a news and ‘help’ section, as well as details of systems and
+ has a news and ‘help’ section, as well as details of systems and
tools.
The MacTeX-on-OSX mailing list is a useful resource for users;
mail MacOSX-TeX-on@email.esm.psu.edu to subscribe.
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-WYGexpts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-WYGexpts.html
index aaa3fbd52d7..6b8ef37b23c 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-WYGexpts.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-WYGexpts.html
@@ -2,16 +2,16 @@
UK TeX FAQ -- question label WYGexpts
The TeX document preparation environment
-“Why TeX is not WYSIWYG”
+“Why TeX is not WYSIWYG”
outlines the reasons (or excuses) for the huge disparity of user
-interface between “typical” TeX environments and commercial word
+interface between “typical” TeX environments and commercial word
processors.
Nowadays, at last, there is a range of tools available that try either
to bridge or to close the gap. One range modestly focuses on
providing the user with a legible source document. At the other
extreme we have TeXmacs,
a document processor using
-TeX’s algorithms and fonts for both editor display and printing.
+TeX’s algorithms and fonts for both editor display and printing.
TeXmacs does not use the TeX
language itself (though among other formats, LaTeX may be exported
and imported). A bit closer to LaTeX is
@@ -41,7 +41,7 @@ screen.
A different type of tool focuses on making update and access to
previews of the typeset document more immediate. A recent addition
in several viewers, editors and TeX executables are so-called
-‘source specials’ for cross-navigation. When TeX compiles a
+‘source specials’ for cross-navigation. When TeX compiles a
document, it will upon request insert special markers for every input
line into the typeset output. The markers are interpreted by the DVI
previewer which can be made to let its display track the page
@@ -74,7 +74,7 @@ buffer but uses actual previews rendered by LaTeX.
system is only available on request from its author;
it continuously updates its screen with the help of a special version
of TeX dumping its state in a compressed format at each page and
-using hooks into TeX’s line breaking mechanism for reformatting
+using hooks into TeX’s line breaking mechanism for reformatting
paragraphs on the fly. That way, it can render the output from the
edited TeX code with interactive speed on-screen, and it offers the
possibility of editing directly in the preview window.
@@ -89,7 +89,7 @@ separate window), degree of correspondence of the display to the final
output, and the balance they strike between visual aid and visual
distraction.
-- preview-latex
- Distributed as part of support/auctex/
+
- preview-latex
- Distributed as part of support/auctex/; catalogue entry
- texmacs
- Browse systems/unix/TeXmacs/
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=WYGexpts
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-abspos.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-abspos.html
index fbfb5c43e07..2e4d1601672 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-abspos.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-abspos.html
@@ -2,7 +2,7 @@
UK TeX FAQ -- question label abspos
Putting things at fixed positions on the page
-TeX’s model of the world is (broadly speaking) that the author
+TeX’s model of the world is (broadly speaking) that the author
writes text, and TeX and its macros decide how it all fits on the
page. This is not good news for the author who has, from whatever
source, a requirement that certain things go in exactly the right
@@ -11,9 +11,9 @@ place on the page.
and two LaTeX packages allow you position things relative to such
points, thus providing a means of absolute positioning.
The textpos package aids the construction of pages from
-“blobs”, dotted around over the page (as in a poster); you give it
+“blobs”, dotted around over the page (as in a poster); you give it
the location, and it places your typeset box accordingly.
-The eso-pic defines a “shipout picture” that covers the
+The eso-pic defines a “shipout picture” that covers the
page. The user may add picture
-mode commands to this
picture, which of course can include box placements as well as the
other rather stilted commands of picture
-mode.
@@ -27,7 +27,7 @@ must therefore also be available.)
- eso-pic.sty
- macros/latex/contrib/eso-pic (or browse the directory)
-
- everyshi.sty
- Distributed as part of macros/latex/contrib/ms (or browse the directory)
+
- everyshi.sty
- Distributed as part of macros/latex/contrib/ms (or browse the directory); catalogue entry
- textpos.sty
- macros/latex/contrib/textpos (or browse the directory)
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=abspos
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acroantics.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acroantics.html
index 53b0f91abaa..ec423373a26 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acroantics.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acroantics.html
@@ -2,27 +2,27 @@
UK TeX FAQ -- question label acroantics
Adobe Reader messing with print size
-Printing from Adobe Reader shrinks the page “to fit”
-(by default). Unfortunately, its calculation doesn’t consider
+Printing from Adobe Reader shrinks the page “to fit”
+(by default). Unfortunately, its calculation doesn’t consider
the existing margins of the document, so that it shrinks what it
believes is your whole page onto what it believes is its output page.
The effect typically looks as if your margins have expanded.
-Solve this problem by adjusting the Reader’s default in the
+Solve this problem by adjusting the Reader’s default in the
print dialogue; unfortunately, this dialogue varies from one version
to the next:
- Reader version 7:
- Page Scaling (default: “Fit to printer margins”) — change to
- “None”, and
- Scale (default 95textpercent of Normal size) — change to
- “100%”.
+ Page Scaling (default: “Fit to printer margins”) — change to
+ “None”, and
+ Scale (default 95textpercent of Normal size) — change to
+ “100%”.
- Adobe Reader 6:
- in the print dialogue, on the “copies & pages” pane, you’ll find a
- popup menu/drop-down list titled “Page Scaling” — change to “None”.
+ in the print dialogue, on the “copies & pages” pane, you’ll find a
+ popup menu/drop-down list titled “Page Scaling” — change to “None”.
- Windows, Linux Acrobat (Reader) 5.0:
- In the print dialog, make sure the “Shrink oversized pages to fit”
+ In the print dialog, make sure the “Shrink oversized pages to fit”
checkbox is unchecked. It may also be useful to uncheck the
- “Expand small pages to fit paper size” checkbox as well.
+ “Expand small pages to fit paper size” checkbox as well.
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=acroantics
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acrobat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acrobat.html
index 85f7456945e..59fd0cdb317 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acrobat.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acrobat.html
@@ -2,13 +2,13 @@
UK TeX FAQ -- question label acrobat
Making Acrobat PDF documents from (La)TeX
-There are three general routes to PDF output: Adobe’s original
-‘distillation’ route (via PostScript output), conversion of a
+There are three general routes to PDF output: Adobe’s original
+‘distillation’ route (via PostScript output), conversion of a
DVI file, and the use of a direct PDF generator such as
PDFTeX) or
-MicroPress’s VTeX (which comes both as a
+MicroPress’s VTeX (which comes both as a
commercial version for Windows PCs, and as a
-‘free’ version) for OS/2 and Linux systems).
+‘free’ version) for OS/2 and Linux systems).
For simple documents (with no hyper-references), you can either
- process the document in the normal way, produce PostScript
@@ -32,15 +32,15 @@ links, you need a LaTeX package to suitably redefine
the internal commands. There are two of these for LaTeX, both
capable of conforming to the
HyperTeX specification:
-Heiko Oberdiek’s hyperref, and Michael Mehlich’s
+Heiko Oberdiek’s hyperref, and Michael Mehlich’s
hyper. (In practice, almost everyone uses
-hyperref; hyper hasn’t been updated since 2000.)
+hyperref; hyper hasn’t been updated since 2000.)
Hyperref can often determine how it should generate
hypertext from its environment, but there is a wide set of
configuration options you can give via
\
usepackage
. The package
can operate using PDFTeX primitives, the hyperTeX
\
special
s, or DVI driver-specific \
special
commands.
-Both dvips and Y&Y’s DVIPSONE can
+Both dvips and Y&Y’s DVIPSONE can
translate the DVI with these \
special
commands into
PostScript acceptable to Distiller, and
dvipdfm and dvipdfmx have \
special
commands of
@@ -50,22 +50,22 @@ help you create PDF documents with hyper-references.
It can operate using PDFTeX primitives, or \
special
commands
for the dvipdfm/dvipdfmx DVI drivers.
While there is no free implementation of all of Adobe
-Distiller’s
+Distiller’s
functionality, any but the very oldest versions of Ghostscript
provide pretty reliable distillation (but beware of the problems with
dvips output for distillation).
-For viewing (and printing) the resulting files, Adobe’s
+For viewing (and printing) the resulting files, Adobe’s
Acrobat Reader is available for a fair range of
-platforms; for those for which Adobe’s reader is unavailable, remotely
+platforms; for those for which Adobe’s reader is unavailable, remotely
current versions of ghostscript combined with
gv or GSview can display and print PDF
files, as can xpdf.
In many circumstances, Ghostscript combined with a viewer
application is actually preferable to Acrobat Reader. For example, on
-Windows Acrobat Reader locks the .pdf
file it’s displaying: this
+Windows Acrobat Reader locks the .pdf
file it’s displaying: this
makes the traditional (and highly effective) (La)TeX development
-cycle of “Edit-> Process-> Preview” become
-rather clumsy — GSview doesn’t make the same
+cycle of “Edit-> Process-> Preview” become
+rather clumsy — GSview doesn’t make the same
mistake.
- Acrobat Reader
- browse
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-actinarg.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-actinarg.html
index 7d024d8dd5c..6ad40bc2d04 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-actinarg.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-actinarg.html
@@ -2,7 +2,7 @@
UK TeX FAQ -- question label actinarg
Active characters in command arguments
-Occasionally, it’s nice to make one or two characters active in the
+Occasionally, it’s nice to make one or two characters active in the
argument of a command, to make it easier for authors to code the
arguments.
Active characters can be used safely in such situations; but
@@ -15,7 +15,7 @@ in a macro for specifying chords.
elsewhere in TeX (to say the least!), so that the characters can
only be made active while the command is executing.
Using the techniques discussed in
-“characters as commands”,
+“characters as commands”,
we can define:
@@ -37,7 +37,7 @@ and:
The second problem is one of timing: the command has to make each
character active before its arguments are read: this means that
-the command can’t actually “have” arguments itself, but must be
+the command can’t actually “have” arguments itself, but must be
split in two. So we write:
@@ -59,18 +59,18 @@ and we can use the command as \
chord{F#}
or
-
\
begingroup
in \
chord
opens a group that is closed by
\
endgroup
in \
Xchord
; this group limits the change of
- category codes, which is the raison d’être of the whole
+ category codes, which is the raison d’être of the whole
exercise.
- - Although
#
is active while \
Xchord
is executed, it’s
- not active when it’s being defined, so that the use of #1
- doesn’t require any special attention.
+ - Although
#
is active while \
Xchord
is executed, it’s
+ not active when it’s being defined, so that the use of #1
+ doesn’t require any special attention.
Note that the technique used in such macros as \
chord
, here, is
analogous to that used in such commands as \
verb
; and, in just the
same way as \
verb
(see
-“\
verb
doesn’t work in arguments”),
-\
chord
won’t work inside the argument of another command (the
+“\
verb
doesn’t work in arguments”),
+\
chord
won’t work inside the argument of another command (the
error messages, if they appear at all, will probably be rather odd).
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=actinarg
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-activechars.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-activechars.html
index 8ceaf24df9b..0308ebb2596 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-activechars.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-activechars.html
@@ -4,20 +4,29 @@
Defining characters as macros
Single characters can act as macros (defined commands), and both
Plain TeX and LaTeX define the character
-“~
” as a “non-breakable space”. A
-character is made definable, or “active”, by setting its
+“~
” as a “non-breakable space”. A
+character is made definable, or “active”, by setting its
category code (catcode) to be \
active
(13):
-\catcode‘_=\active
.
-Any character could, in principle, be activated this way and defined
-as a macro (\
def
_{
\
_
}
— the simple answer to
-
-using underscores), but you must be
+
+
+\catcode`\_=\active
+
+
+Any character could, in principle, be activated this way and defined
+as a macro:
+
+
+\def_{\_}
+
+
+which could be characterised as an over-simple answer to
+using underscores. However, you must be
wary: whereas people expect an active tilde, other active characters
may be unexpected and interact badly with other macros. Furthermore,
-by defining an active character, you preclude the character’s use for
-other purposes, and there are few characters “free” to be subverted
+by defining an active character, you preclude the character’s use for
+other purposes, and there are few characters “free” to be subverted
in this way.
-
To define the character “z
” as a command, one would say something
+To define the character “z
” as a command, one would say something
like:
@@ -25,10 +34,10 @@ like:
\def z{Yawn, I'm tired}%
-and each subsequent “z
” in the text would become a yawn. This would be
+and each subsequent “z
” in the text would become a yawn. This would be
an astoundingly bad idea for most documents, but might have special
-applications. (Note that, in “\def z
”, “z
” is no longer interpreted as
-a letter; the space is therefore not necessary — “\defz
” would do; we
+applications. (Note that, in “\def z
”, “z
” is no longer interpreted as
+a letter; the space is therefore not necessary — “\defz
” would do; we
choose to retain the space, for what little clarity we can manage.)
Some LaTeX packages facilitate such definitions. For example, the
shortvrb package with its \
MakeShortVerb
command.
@@ -42,17 +51,17 @@ purposes (the \
verb
command does this), then the alter
characters will not be interpreted properly when they appear in the
argument to another command (as, for example, in
-“\
verb
in command arguments”).
+“\
verb
in command arguments”).
An exemplary case is the doc package, which processes .dtx
files using the shortvrb package to define
-|…|
as a shorthand for
-\
verb
|…|
. But |
is
+|…|
as a shorthand for
+\
verb
|…|
. But |
is
also used in the preambles of tabular environments, so that tables in
.dtx
files can only have vertical line separation between
columns by employing special measures of some sort.
Another consequence is that catcode assignments made
-in macros often don’t work as expected
-(see “Active characters in command arguments”).
+in macros often don’t work as expected
+(see “Active characters in command arguments”).
For example, the definition
@@ -77,10 +86,10 @@ use:
\endgroup
-The alternative (“tricksy”) way of creating such an isolated
+The alternative (“tricksy”) way of creating such an isolated
definition depends on the curious properties of \
lowercase
, which
changes characters without altering their catcodes. Since there is
-always one active character (“~
”), we
+always one active character (“~
”), we
can fool \
lowercase
into patching up a definition without ever
explicitly changing a catcode:
@@ -109,12 +118,12 @@ special active maths code, as with
The special character does not need to be redefined whenever it is
-made active — the definition of the command persists even if the
-character’s catcode reverts to its original value; the definition
+made active — the definition of the command persists even if the
+character’s catcode reverts to its original value; the definition
becomes accessible again if the character once again becomes active.
-- doc.sty
- Distributed as part of the source of LaTeX, macros/latex/base (or browse the directory)
-
- shortvrb.sty
- Distributed as part of macros/latex/required/tools (or browse the directory)
+
- doc.sty
- Part of the LaTeX distribution macros/latex/base (or browse the directory); catalogue entry
+
- shortvrb.sty
- Part of the LaTeX distribution macros/latex/base (or browse the directory); catalogue entry
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=activechars
Master and slave counters
-It’s common to have things numbered “per chapter” (for example, in
+It’s common to have things numbered “per chapter” (for example, in
the standard book and report classes, figures, tables
and footnotes are all numbered thus). The process of resetting is
-done automatically, when the “master” counter is stepped (when the
+done automatically, when the “master” counter is stepped (when the
\
chapter
command that starts chapter <n> happens, the
chapter
counter is stepped, and all the dependent counters are set
to zero).
How would you do that for yourself? You might want to number
algorithms per section, or corollaries per theorem, for example. If
-you’re defining these things by hand, you declare the relationship
+you’re defining these things by hand, you declare the relationship
when you define the counter in the first place:
\
newcounter{
new-name}[
master]
@@ -19,7 +19,7 @@ when you define the counter in the first place:
says that every time counter <master> is stepped, counter
<new-name> will be reset.
But what if you have an uncooperative package, that defines the
-objects for you, but doesn’t provide a programmer interface to make
+objects for you, but doesn’t provide a programmer interface to make
the counters behave as you want?
The \
newcounter
command uses a LaTeX internal command, and you
can also use it:
@@ -44,14 +44,14 @@ command without its asterisk:
will do the same, and also redefine \
thecorollary
as
<theorem number>.<corollary number>, which is a good scheme
-if you ever want to refer to the corollaries — there are potentially
-many “corollary 1” in any document, so it’s as well to tie its number
+if you ever want to refer to the corollaries — there are potentially
+many “corollary 1” in any document, so it’s as well to tie its number
to the counter of the theorem it belongs to. This is true of pretty
-much any such counter-within-another; if you’re not using the
+much any such counter-within-another; if you’re not using the
chngcntr, refer to the answer to
-redefining counters’ \
the-
commands for
+redefining counters’ \
the-
commands for
the necessary techniques.
-
Note that the technique doesn’t work if the master counter is page
,
+Note that the technique doesn’t work if the master counter is page
,
the number of the current page. The page
counter is stepped deep
inside the output routine, which usually gets called some time after
the text for the new page has started to appear: so special
@@ -64,11 +64,11 @@ may be applied to any counter. The command:
will cause <counter> to be reset for each page. The package uses
a label-like mechanism, and may require more than one run of LaTeX
-to stabilise counter values — LaTeX will generate the usual
+to stabilise counter values — LaTeX will generate the usual
warnings about labels changing.
-- chngcntr.sty
- macros/latex/contrib/misc/chngcntr.sty
-
- perpage.sty
- Distributed as part macros/latex/contrib/bigfoot (or browse the directory)
+
- chngcntr.sty
- macros/latex/contrib/chngcntr (or browse the directory)
+
- perpage.sty
- Distributed as part macros/latex/contrib/bigfoot (or browse the directory); catalogue entry
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=addtoreset
Typesetting pseudocode in LaTeX
-There is no consensus on the ‘right’ way to typeset pseudocode.
+There is no consensus on the ‘right’ way to typeset pseudocode.
Consequently, there are a variety of LaTeX packages to choose from
-for producing æsthetically pleasing pseudocode listings.
+for producing æsthetically pleasing pseudocode listings.
Pseudocode differs from actual program listings in that it lacks
strict syntax and semantics. Also, because pseudocode is supposed to
be a clear expression of an algorithm it may need to incorporate
@@ -15,8 +15,8 @@ that do not appear in conventional programming languages.
You can certainly create your own environment for typesetting
pseudocode using, for example, the tabbing
or
-list
environments — it’s not difficult, but it may
-prove boring. So it’s worth trying the following packages, all
+list
environments — it’s not difficult, but it may
+prove boring. So it’s worth trying the following packages, all
designed specifically for typesetting pseudocode.
The algorithms bundle (which contains packages
algorithm and algorithmic, both of which are
@@ -29,7 +29,7 @@ for adding new primitives. Typesetting the pseudocode itself is
performed in algorithmic; the algorithms package
uses the facilities of the float package to number
algorithms sequentially, enable algorithms to float like figures or
-tables, and support including a List of Algorithms in a document’s
+tables, and support including a List of Algorithms in a document’s
front matter.
Packages in the algorithmicx bundle are similar both in
concept and output form to algorithmic but additionally
@@ -48,23 +48,23 @@ floating algorithm environment with all of the ensuing niceties.
algorithms, makes it easy to add new constructs.
The newalg package has a somewhat similar interface to
algorithms, but its output is designed to mimic the rather
-pleasant typesetting used in the book “Introduction to Algorithms”
+pleasant typesetting used in the book “Introduction to Algorithms”
by Corman, Leiserson, Rivest and Stein. Unfortunately,
newalg does not support a floating environment or any
customisation of the output.
-“Bona fide” use of the style of “Introduction to
-Algorithms” may be achieved with Cormen’s own clrscode:
+“Bona fide” use of the style of “Introduction to
+Algorithms” may be achieved with Cormen’s own clrscode:
this is the package as used in the second edition of the book.
Similarly, the style of
-“Combinatorial Algorithms: Generation, Enumeration and Search”
+“Combinatorial Algorithms: Generation, Enumeration and Search”
is supported by the pseudocode package, written by the
-authors of the book. It has the common ‘Pascal-like’ style, and has
+authors of the book. It has the common ‘Pascal-like’ style, and has
some interesting constructs for what one thinks of as Pascal blocks.
The algorithm2e is of very long standing, and is widely used
and recommended. It loads the float package to provide the
option of floating algorithm descriptions, but you can always use the
-“H
” option of float to have the algorithm appear
-“where you write it”.
+“H
” option of float to have the algorithm appear
+“where you write it”.
The usage of the program package is a little different from
that of the other packages. It typesets programs in maths mode
instead of text mode; and linebreaks are significant.
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-alreadydef.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-alreadydef.html
index 31442c04f3a..97819cbd730 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-alreadydef.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-alreadydef.html
@@ -1,7 +1,7 @@
UK TeX FAQ -- question label alreadydef
-Package reports “command already defined”
+Package reports “command already defined”
You load a pair of packages, and the second reports that one of the
commands it defines is already present. For example, both the
txfonts and amsmath define a command \
iint
@@ -23,21 +23,21 @@ produces a string of error messages of the form:
As a general rule, things that amsmath defines, it defines
well; however, there is a good case for using the txfonts
-version of \
iint
— the associated tx fonts have a
-double integral symbol that doesn’t need to be “faked” in the way
+version of \
iint
— the associated tx fonts have a
+double integral symbol that doesn’t need to be “faked” in the way
amsmath does. In the case that you are loading several
symbol packages, every one of which defines the same symbol, you are
likely to experience the problem in a big way (\
euro
is a common
victim).
-
There are similar cases where one package redefines another’s command,
-but no error occurs because the redefining package doesn’t use
+There are similar cases where one package redefines another’s command,
+but no error occurs because the redefining package doesn’t use
\
newcommand
. Often, in such a case, you only notice the change
because you assume the definition given by the first package. The
-amsmath–txfonts packages are just such a pair;
-txfonts doesn’t provoke errors.
+amsmath–txfonts packages are just such a pair;
+txfonts doesn’t provoke errors.
You may deal with the problem by saving and restoring the command.
Macro programmers may care to do this for themselves; for the rest of
-us, there’s the package savesym. The sequence:
+us, there’s the package savesym. The sequence:
\usepackage{savesym}
@@ -50,7 +50,7 @@ us, there’s the package savesym. The sequence:
does the job; restoring the amsmath version of the command,
and making the txfonts version of the command available as
\
TXFiint
.
-Documentation of savesym doesn’t amount to much: the only
+Documentation of savesym doesn’t amount to much: the only
commands are \
savesymbol
and \
restoresymbol
, as noted above.
- amsmath.sty
- Part of macros/latex/required/amslatex (or browse the directory)
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-altabcr.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-altabcr.html
index 7bf9dbcb782..6b018e33a48 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-altabcr.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-altabcr.html
@@ -3,8 +3,8 @@
Alignment tab changed to \
cr
This is an error you may encounter in LaTeX when a tabular
-environment is being processed. “Alignment tabs” are the
-&
signs that separate the columns of a tabular; so the error
+environment is being processed. “Alignment tabs” are the
+&
signs that separate the columns of a tabular; so the error
message
@@ -21,10 +21,10 @@ could arise from a simple typo, such as:
\end{tabular}
-where the second &
in the first line of the table is more than the
+where the second &
in the first line of the table is more than the
two-column ll
column specification can cope with. In this
-case, an extra “l
” in that solves the problem. (If you
-continue from the error in this case, “jim
” will be moved
+case, an extra “l
” in that solves the problem. (If you
+continue from the error in this case, “jim
” will be moved
to a row of his own.) Another simple typo that can provoke the error
is:
@@ -35,7 +35,7 @@ is:
\end{tabular}
-where the ‘\\
’ has been missed from the first line of the table.
+where the ‘\\
’ has been missed from the first line of the table.
In this case, if you continue from the error, you will find that
LaTeX has made a table equivalent to:
@@ -48,12 +48,12 @@ LaTeX has made a table equivalent to:
(with the second line of the table having only one cell).
Rather more difficult to spot is the occurrence of the error when
-you’re using alignment instructions in a “p
” column:
+you’re using alignment instructions in a “p
” column:
\usepackage{array}
...
-\begin{tabular}{l>{\raggedright}p{2in}}
+\begin{tabular}{l>{\raggedright}p{2in}}
here & we are again \\
happy & as can be
\end{tabular}
@@ -62,16 +62,16 @@ happy & as can be
the problem here (as explained in
tabular cell alignment) is that the
\
raggedright
command in the column specification has overwritten
-tabular
’s definition of \\
, so that
-“happy
” appears in a new line of the second column, and the
-following &
appears to LaTeX just like the second
-&
in the first example above.
+tabular
’s definition of \\
, so that
+“happy
” appears in a new line of the second column, and the
+following &
appears to LaTeX just like the second
+&
in the first example above.
Get rid of the error in the way described in
-tabular cell alignment — either use
+tabular cell alignment — either use
\
tabularnewline
explicitly, or use the \
RBS
trick described
there.
-- array.sty
- Distributed as part of macros/latex/required/tools (or browse the directory)
+
- array.sty
- Distributed as part of macros/latex/required/tools (or browse the directory); catalogue entry
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=altabcr
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html
index e4abccf5f8a..9aa1632b47f 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-amfonts.html
@@ -3,13 +3,13 @@
Where are the am
fonts?
One still occasionally comes across a request for the am
-series of fonts. The initials stood for ‘Almost [Computer] Modern’,
+series of fonts. The initials stood for ‘Almost [Computer] Modern’,
and they were the predecessors of the Computer Modern fonts that we
all know and love (or hate)
.
-There’s not a lot one can do with these
+There’s not a lot one can do with these
fonts; they are (as their name implies) almost (but not quite) the
-same as the cm series; if you’re faced with a document that requests
+same as the cm series; if you’re faced with a document that requests
them, the only reasonable approach is to edit the document to replace
am* font names with cm*.
The appearance of DVI files that request them is sufficiently
@@ -18,10 +18,10 @@ translation of them by means of virtual fonts.
You therefore have to fool the system into using cm* fonts
where the original author specified am*.
One option is the font substitutions that many
-DVI drivers provide via their configuration file —
+DVI drivers provide via their configuration file —
specify that every am font should be replaced by its
corresponding cm font.
-Alternatively, one may try DVI editing — packages
+Alternatively, one may try DVI editing — packages
dtl (DVI Text Language) and dviasm
(DVI assembler) can both provide round trips from DVI to
text and back to DVI. One therefore edits font names
@@ -44,7 +44,7 @@ about through the body, so:
python dviasm.py -o
<edited.dvi> <edited.txt>
Both routes seem acceptable ways forward; it is a matter of taste
-which any particular user may choose (it’s not likely that it will be
+which any particular user may choose (it’s not likely that it will be
necessary very often...).
- dviasm.py
- dviware/dviasm (or browse the directory)
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ant.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ant.html
index e8a9ce4eb1f..8eb489fb375 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ant.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ant.html
@@ -2,18 +2,18 @@
UK TeX FAQ -- question label ant
The ANT typesetting system
-Achim Blumensath’s ANT project
+Achim Blumensath’s ANT project
aims not to replicate TeX with a different implementation
technique, but rather to provide a replacement for TeX which uses
TeX-like typesetting algorithms in a very different programming
environment. ANT remains under development, but it is now
approaching the status of a usable typesetting system.
-ANT’s markup language is immediately recognisable to the
+ANT’s markup language is immediately recognisable to the
(La)TeX user, but the scheme of implementing design in
-ANT’s own implementation language (presently
+ANT’s own implementation language (presently
OCaml) comes as a pleasant surprise to the jaded FAQ
writer. This architecture holds the promise of a system that avoids a
-set of serious problems with TeX’s user interface: those that
+set of serious problems with TeX’s user interface: those that
derive from the design language being the same as the markup language.
- ANT
- systems/ant (or browse the directory)
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-appendix.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-appendix.html
index a7f5e70c768..e82a599ea64 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-appendix.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-appendix.html
@@ -24,16 +24,16 @@ to alphabetic. So:
would be typeset (in an article document) something like:
1 My inspiration
-…
+…
2 Developing the inspiration
-…
+…
A How I became inspired
-…
+…
which is quite enough for many ordinary purposes. Note that, once
-you’ve switched to typesetting appendixes, LaTeX provides you with
-no way back — once you’ve had an appendix, you can no longer have an
-“ordinary” \
section
or \
chapter
.
+you’ve switched to typesetting appendixes, LaTeX provides you with
+no way back — once you’ve had an appendix, you can no longer have an
+“ordinary” \
section
or \
chapter
.
The appendix provides several ways of elaborating on this
simple setup. Straightforward use of the package allows you to have a
separate heading, both in the body of the document and the table of
@@ -47,10 +47,10 @@ contents; this would be achieved by
\addappheadtotoc
-The \
appendixpage
command adds a separate title “Appendices”
+The \
appendixpage
command adds a separate title “Appendices”
above the first appendix, and \
addappheadtotoc
adds a similar
title to the table of contents. These simple modifications cover many
-people’s needs about appendixes.
+people’s needs about appendixes.
The package also provides an appendices
environment,
which provides for fancier use. The environment is best controlled by
package options; the above example would be achieved by
@@ -65,7 +65,7 @@ package options; the above example would be achieved by
The great thing that the appendices
environment gives
you, is that once the environment ends, you can carry on with sections
-or chapters as before — numbering isn’t affected by the intervening
+or chapters as before — numbering isn’t affected by the intervening
appendixes.
The package provides another alternative way of setting appendixes, as
inferior divisions in the document. The subappendices
@@ -90,11 +90,11 @@ as \
section
s. So one might write:
Which will produce output something like:
1 My inspiration
-…
+…
1.A How I became inspired
-…
+…
2 Developing the inspiration
-…
+…
There are many other merry things one may do with the package; the
user is referred to the package documentation for further details.
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-archives.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-archives.html
index 6769c5d998c..0ee7334befc 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-archives.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-archives.html
@@ -28,8 +28,8 @@ or mirror closest to you. A complete and current list of CTAN sites
and known mirrors is available as file CTAN.sites on the
archives themselves.
Better still, the script behind http://mirror.ctan.org/ will
-cunningly choose a “nearby” mirror for you, using information from
-the database ‘behind’ CTAN.sites; at present it uses
+cunningly choose a “nearby” mirror for you, using information from
+the database ‘behind’ CTAN.sites; at present it uses
ftp
protocol for transfers, but the intention is to convert
it to using http
(web) protocol in the near future.
To access a particular thing through the mirror.ctan.org
@@ -37,10 +37,10 @@ mechanism, simply place the CTAN path after the base
URL; so
http://mirror.ctan.org/macros/latex/contrib/footmisc/ will
connect you to the footmisc directory at some CTAN
-site (or a mirror) — note that the tex-archive part of the
-CTAN path isn’t needed.
+site (or a mirror) — note that the tex-archive part of the
+CTAN path isn’t needed.
For details of how to find files at CTAN sites, see
-“finding (La)TeX files”.
+“finding (La)TeX files”.
The TeX user who has no access to any sort of
network may buy a copy of the archive as part of the
TeX Live distribution.
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-askquestion.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-askquestion.html
index c6e66a4cc52..83c665a58dc 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-askquestion.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-askquestion.html
@@ -2,51 +2,51 @@
UK TeX FAQ -- question label askquestion
How to ask a question
-You want help from the community at large; you’ve decided where you’re
+You want help from the community at large; you’ve decided where you’re
going to ask your question, but how do you
phrase it?
-Excellent “general” advice (how to ask questions of anyone) is
+Excellent “general” advice (how to ask questions of anyone) is
contained in
-Eric Raymond’s article on the topic.
-Eric’s an extremely self-confident person, and this comes through in
+Eric Raymond’s article on the topic.
+Eric’s an extremely self-confident person, and this comes through in
his advice; but his guidelines are very good, even for us in the
-un-self-confident majority. It’s important to remember that you don’t
+un-self-confident majority. It’s important to remember that you don’t
have a right to advice from the world, but that if you express
yourself well, you will usually find someone who will be pleased to
help.
-So how do you express yourself in the (La)TeX world? There aren’t
+So how do you express yourself in the (La)TeX world? There aren’t
any comprehensive rules, but a few guidelines may help in the
application of your own common sense.
-- Make sure you’re asking the right people. Don’t ask in a TeX
+
- Make sure you’re asking the right people. Don’t ask in a TeX
forum about printer device drivers for the Foobar
operating system. Yes, TeX users need printers, but no, TeX
users will typically not be Foobar systems
managers.
Similarly, avoid posing a question in a language that the majority
- of the group don’t use: post in Ruritanian to
+ of the group don’t use: post in Ruritanian to
de.comp.text.tex and you may have a long wait before a
German- and Ruritanian-speaking TeX expert notices your
question.
- If your question is (or may be) TeX-system-specific, report
- what system you’re using, or intend to use: “I can’t install
- TeX” is as good as useless, whereas “I’m trying to install the
+ what system you’re using, or intend to use: “I can’t install
+ TeX” is as good as useless, whereas “I’m trying to install the
mumbleTeX distribution on the Grobble
- operating system” gives all the context a potential respondent
+ operating system” gives all the context a potential respondent
might need. Another common situation where this information is
- important is when you’re having trouble installing something new in
- your system: “I want to add the glugtheory package to my
+ important is when you’re having trouble installing something new in
+ your system: “I want to add the glugtheory package to my
mumbleTeX v12.0 distribution on the Grobble 2024
- operating system”.
+ operating system”.
- If you need to know how to do something, make clear what your
- environment is: “I want to do x in Plain TeX”, or “I
+ environment is: “I want to do x in Plain TeX”, or “I
want to do y in LaTeX running the boggle
- class”. If you thought you knew how, but your attempts are
- failing, tell us what you’ve tried: “I’ve already tried installing
+ class”. If you thought you knew how, but your attempts are
+ failing, tell us what you’ve tried: “I’ve already tried installing
the elephant in the minicar directory, and it
- didn’t work, even after refreshing the filename database”.
-
- If something’s going wrong within (La)TeX, pretend you’re
+ didn’t work, even after refreshing the filename database”.
+
- If something’s going wrong within (La)TeX, pretend you’re
submitting a LaTeX bug report,
and try to generate a minimum failing example.
If your example
@@ -55,12 +55,12 @@ application of your own common sense.
resource can be obtained.
- Figures are special, of course. Sometimes the figure itself is
really needed, but most problems may be demonstrated with a
- “figure substitute” in the form of a
+ “figure substitute” in the form of a
\
rule{
width}{
height}
command, for some value of
<width> and <height>. If the (real) figure is needed,
- don’t try posting it: far better to put it on the web somewhere.
- - Be as succinct as possible. Your helpers don’t usually need to
- know why you’re doing something, just what you’re
+ don’t try posting it: far better to put it on the web somewhere.
+
- Be as succinct as possible. Your helpers don’t usually need to
+ know why you’re doing something, just what you’re
doing and where the problem is.
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsign.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsign.html
index 7f2c267226b..3b7a442b92a 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsign.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsign.html
@@ -1,12 +1,12 @@
UK TeX FAQ -- question label atsign
-How to type an ‘@’ sign?
-Long ago, some packages used to use the ‘@’ sign as a command, so that
+How to type an ‘@’ sign?
+Long ago, some packages used to use the ‘@’ sign as a command, so that
special measures were needed to type it. While those packages are
still in principle available, few people use them, and those that do
use them have ready access to rather good documentation.
Ordinary people (such as the author of this FAQ) need only type
-‘@’.
+‘@’.
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsign
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html
index e31404b1b9d..6610dd321d8 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atsigns.html
@@ -3,9 +3,9 @@
\
@
and @
in macro names
Macro names containing @
are internal to LaTeX, and
-without special treatment just don’t work in ordinary use. A nice
+without special treatment just don’t work in ordinary use. A nice
example of the problems caused is discussed in
-\
@
in vertical mode”.
+\
@
in vertical mode”.
The problems users see are caused by copying bits of a class
(.cls
file) or
package (.sty
file) into a document, or by including a class or
@@ -16,10 +16,10 @@ avoid clashes between its internal names and names that we would
normally use in our documents. In order that these commands may work
at all, \
documentclass
and \
usepackage
play around with the
meaning of @
.
-If you’ve included a file some other way (for example, using
+If you’ve included a file some other way (for example, using
\
input
), you can probably solve the problem by using the correct
command.
-If you’re using a fragment of a package or class, you may well feel
+If you’re using a fragment of a package or class, you may well feel
confused: books such as the first edition of the
The LaTeX Companion
are full of fragments of packages as examples for you to employ.
@@ -44,7 +44,7 @@ second edition.)
The alternative is to treat all these fragments as a package proper,
bundling them up into a .sty
file and including them with
\
usepackage
; this way you hide your LaTeX internal code somewhere
-that LaTeX internal code is expected, which often looks ‘tidier’.
+that LaTeX internal code is expected, which often looks ‘tidier’.
- Examples from the Companion
- info/examples/tlc2 (or browse the directory)
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atvert.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atvert.html
index f1761290a2d..0d150b9def6 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atvert.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atvert.html
@@ -5,13 +5,13 @@
The errors
! You can't use `\spacefactor' in vertical mode.
-\@->\spacefactor
+\@->\spacefactor
\@m
or
! You can't use `\spacefactor' in math mode.
-\@->\spacefactor
+\@->\spacefactor
\@m
or simply
@@ -20,9 +20,9 @@ or simply
...
bites the LaTeX programmer who uses an internal command without taking
-“precautions”. The problem is discussed in detail in
+“precautions”. The problem is discussed in detail in
-“@
in macro names”,
+“@
in macro names”,
together with solutions.
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atvert
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-backref.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-backref.html
index 8e6e7b78a87..4b61797ecdf 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-backref.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-backref.html
@@ -10,12 +10,12 @@ citing command, is often useful in large documents.
command.
Citeref is the older, and seems to rely on rather simpler
(and therefore possibly more stable) code; it produces a list of page
-references, only. It doesn’t interact well with other citation
+references, only. It doesn’t interact well with other citation
packages (for example, cite), which probably reflects its
-antiquity (it’s derived from a LaTeX 2.09 package).
+antiquity (it’s derived from a LaTeX 2.09 package).
Neither collapses
-lists of pages (“5, 6, 7
” comes out as such, rather than as
-“5–7
”), but neither package repeats the reference to a page that
+lists of pages (“5, 6, 7
” comes out as such, rather than as
+“5–7
”), but neither package repeats the reference to a page that
holds multiple citations. (The failure to collapse lists is of course
forgiveable in the case of the hyperref-related
backref, since the concept of multiple hyperlinks from the
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-badhyph.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-badhyph.html
index 4ca66686b50..50363583052 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-badhyph.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-badhyph.html
@@ -5,31 +5,31 @@
For example
! Improper \hyphenation will be flushed.
-\'#1->{
+\'#1->{
\accent 19 #1}
-<*> \hyphenation{Ji-m\'e
+<*> \hyphenation{Ji-m\'e
-nez}
(in Plain TeX) or
! Improper \hyphenation will be flushed.
-\leavevmode ->\unhbox
+\leavevmode ->\unhbox
\voidb@x
-<*> \hyphenation{Ji-m\'e
+<*> \hyphenation{Ji-m\'e
-nez}
in LaTeX.
-As mentioned in “hyphenation failures”,
+As mentioned in “hyphenation failures”,
words with accents in them may not be hyphenated. As a result, any
such word is deemed improper in a \
hyphenation
command.
The solution is to use a font that contains the character in question,
and to express the \
hyphenation
command in terms of that
-character; this “hides” the accent from the hyphenation mechanisms.
+character; this “hides” the accent from the hyphenation mechanisms.
LaTeX users can be achieved this by use of the fontenc
package (part of the LaTeX distribution). If you select an 8-bit
font with the package, as in \
usepackage[T1]{fontenc}
,
-accented-letter commands such as the \’
e
in
-\hyphenation{Ji-m\’
e-nez}
automatically become the single accented
+accented-letter commands such as the \’
e
in
+\hyphenation{Ji-m\’
e-nez}
automatically become the single accented
character by the time the hyphenation gets to look at it.
This question on the Web: http://www.tex.ac.uk/cgi-bin/texfaq2html?label=badhyph