diff options
451 files changed, 7819 insertions, 7515 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/00readme b/Master/texmf-doc/doc/english/FAQ-en/00readme deleted file mode 100644 index 87b8967515e..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/00readme +++ /dev/null @@ -1,59 +0,0 @@ -If you believe you need to process this FAQ, stop; it can be tedious. - -1) Do you have a 300dpi or 600dpi PostScript printer? -- if so, try - newfaq.300ps or newfaq.ps (these were made for CanonCX and - Laserjet4 engines, respectively) -2) Do you need PostScript output at some other resolution? -- if so, - process newfaq.dvi (you'll need the font set required by psnfss, at - least for Times, Helvetica and Symbol fonts; you'll also need the - logo* fonts -- the mostly likely oddity is logod10, the .mf for - which is to be found on CTAN in tex-archive in - tex-archive/systems/knuth/local/lib/logod10.mf) -3) Do you need non-PostScript output? -- if so, process newfaq-cm.dvi - (this only needs the logo* fonts) -4) Do you use (North American) letter paper? -- if so, modify the - above recommendations to use letterfaq instead of newfaq. - -I've not dissuaded you? - -Well, you need a production LaTeX2e (i.e., at the very least -1994/06/01, though the development work is done using the latest -version of LaTeX2e (1995/12/01 at the time of writing), and no -guarantees are offered that the code will process using anything -earlier), and you should process newfaq.tex (for A4 paper) or -letterfaq.tex (for letter paper). You should download every file in -the CTAN directory (except things like ChangeLog [boring] and Makefile -[mine: may not even be there, but not intended for your use]) ----- -Package and class use (breathe deep) - -newfaq.tex and letterfaq.tex use class faq, which passes all its -options to article.cls, and then loads packages faq (in the CTAN -directory) and multicol (part of the LaTeX2e tools set) - -faq.sty loads - - times and pifont (from the PSNFSS package) if the default faqfont.cfg - (in the CTAN directory) isn't there - mflogo (which implies loading Ulogo.fd) (but both of those are in the - CTAN directory) - texnames (which is in the CTAN directory) - ifthen (from the 2e distribution) - comment (from tex-archive/macros/latex209/contrib/misc/) - -newfaq.tex and letterfaq.tex also load - - faqbody.tex the questions - -The fonts I have (over and above the default) are logod10 at magsteps -0, 1 and 2 (thus I have a logod10.300pk,360pk,432pk for making the .ps -file in the CTAN directory, and .600pk,720pk and 864pk for use on the -LJ4 printers here). The source for logod10 is in -tex-archive/systems/knuth/local/lib (it uses logo.mf, which should be -in your distribution). ----- -Robin Fairbairns -UKTUG honorary victim, - production of the new FAQ -rf@cl.cam.ac.uk (please address comments on the document, or on - anything related, to me) diff --git a/Master/texmf-doc/doc/english/FAQ-en/CHANGES-3.11 b/Master/texmf-doc/doc/english/FAQ-en/CHANGES-3.11 deleted file mode 100644 index d1961422c2b..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/CHANGES-3.11 +++ /dev/null @@ -1,73 +0,0 @@ -Changes in version 3.11 - -Documentation and help: - - added another example of university department help pages - - link to Herbert Voss's excellent stuff - - remove reference to bausum's plain tex list (since it's no longer available) - - remove reference to the ltx-2 latex 2.09 equivalent to bausum's list - - more entries in list of mf/mp tutorials - - link to Matsusaka University Japanese with Omega howto - -Graphics: - - mention mptopdf in "mp output in ghostscript" - -Document structure (and similar places): - - list places where memoir/KOMA-script classes can help answer questions - (thanks to Peter Wilson and Markus Kohm for extensive support here) - - change back to recommending caption rather than caption2 - - improvements and extensions to - -Installing (La)TeX files: - - changes for new fptex release - -Tables of contents and indexes: - - correct egregious error in example of use of multind package; other - developments on that answer - -Creating bibliographies: - - correct @preamble defining \noopsort - -New or revised packages (or just ones never before mentioned): - - caption (no extra "c" or "2") revision to supersede caption2 - - capt-of - - dblfloatfix for float* positioning - - ednotes - - eqparbox - - ledmac - - pbox - - pict2e - - tabulary for fixed-width tables - - varwidth - -New answers: -section{Installing (La)TeX files}: - label privinst - installing files in a private TEXMF tree - label instt1font - installing type 1 fonts (the ones not already covered) -section{Bits and pieces of TeX}: - label resolns - what's meant by printer resolution statements and how they - affect tex and friends - label fontname - the berry font naming scheme -section{Graphics}: - label dvipdfmgraphics - to go with dvipsgraphics and pdftexgraphics -subsection{Tables of contents and indexes}: - label minitoc - tables of contents per chapter -subsection{Common errors}: - label tabacc - accents in tabbing environments - label alreadydef - "command already defined" errors from packages -subsection{Common misunderstandings}: - label linespread - understanding \linespread - label baselinepar - \baselineskip changes within a paragraph -subsection{Odds and ends}: - label varwidth - "variable width \parboxes" -subsection{Creating bibliographies}: - label bibtranscinit - transcribed initials in bibliographies -subsection{Creating citations}: - label sortbib - why isn't my thebibliography environment sorted? -section{The joy of TeX errors}: - label inputlev - input too deeply nested - label hyperdupdest - duplicated destinations in pdftex, refres to - label pdfpagelabels -section{Hypertext and PDF}: - label pdfpagelabels - commonest way of avoiding duplicated destinations -subsection{Why shouldn't I?}: - label 2letterfontcmd - what's wrong with \tt, \bf, etc diff --git a/Master/texmf-doc/doc/english/FAQ-en/CHANGES-3.16 b/Master/texmf-doc/doc/english/FAQ-en/CHANGES-3.16 deleted file mode 100644 index 110e1addcd6..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/CHANGES-3.16 +++ /dev/null @@ -1,87 +0,0 @@ -Changes in version 3.16 - -These are changes from 3.15a, which incorporated a couple of -minor corrections made on the day 3.15 was uploaded - -New answers: - Label chngmargonfly: changing the document's margins "on the fly" - Label doc-wiki: catalogue of known tex-related WIKIs - Label fonts-pln: "sophisticated" font selection macros in Plain TeX - Label gutter: the problem with two-sided document margins - Label marginmanual: setting up the document's margins "by hand" - Label marginpkgs: packages for setting up the document's margins - Label matchbrak: matching "[]" in optional arguments, etc. - Label newfont: why shouldn't I use \newfont in LaTeX? - Label poster: summary of the inadequate state of support for posters - Label repeatgrf: repeated graphics in documents - Label whatbst: choosing a BibTeX style - Label whatpdftex: "PDFTeX has entered the mainstream" (actually, it did some - time ago, but I've now "recognised" that in the FAQ) - -Answers removed: - Label pdftex: I think pdftex is no longer "research" -- see label whatpdftex - -Revised answers: - Label ant: correct home page reference - Label changemargin: rehashed as intro and list of links to (new) - "instruction" answers marginpkgs, marginmanual - and chngmargonfly - Label complist: mention multenum package - Label cv: europecv has improved, and there's a new class moderncv - Label dvipsgraphics: extend discussion of bitmap graphics in dvips - Label drawing: correct URL for pstricks site - Label findfiles: remove mention of the (long dead) quote site index, - add the catalogue bytopic.html - Label fmtconv: troff-to-latex no longer available - Label newfunction: mention \operatorname command - Label labundef: mention labelcas package - Label labelfig: mention iTe editor, correct URL on pstricks page - Label man-tex: correct URL for Andy Roberts' page - Label man-latex: add Chris Harrison's web manual - Label rotating: mention rotfloat package - Label seccntformat: correction of suggested code - Label secthead: remove 2.09 font commands from "simple" example - Label struttab: mention new cellspace package - Label texsystems: mention w32tex (from japan) -- capable of being a "minimal" - system - Label tutbitslatex: correct URL for the pTeX description, add link to Smith's - "LaTeX for logicians" - Label usepictex: correct stuff about mathspic package - Label verbwithin: make clear problems apply to verbatim environment, too - Label xetex: simplify the answer (the details are all on the web - site, anyway), and mention the new linux port - -Presentation: - LaTeX ``...'' quotes in the source used to be converted to the ascii - double-quote character in the HTML; this is changed to use the HTML - entities for "typographic" quotes (similarly for single quotes and - apostrophes). - - A minor change to html generation has been made, inserting paragraph - elements after block quotes: this makes CSS-controlled display more - regular (a CSS sheet is used in the code generated for the new CGI - engine -- see below). - - Building the FAQ now requires e-TeX (or rather [pdf-]e-LaTeX); this - should not be a problem unless your TeX distribution is a bit aged. - -Future releases: - This release is wildly overdue (even making allowance for my - extended illness). If I can find the time to do so, I intend in - future to release anything that's available, around the end of each - month. Full releases, with batches of new questions, may still be - long delayed, but I hope not. - -Coming up (still): - I have a far more efficient CGI engine for serving answers to the web; - those of a strong constitution may view the experimental testbed at: - URL http://www.tex.ac.uk/cgi-bin/texfaq2html-gamma - It is missing a search engine, various links and topping and tailing - of answers; it uses Cambridge University's "default" CSS sheet in a - non-standard way; and, crucially it lacks **SUPPORT**. I welcome - suggestions for improving the way I do things, but I can't claim it - will always work. - - Mechanisms whereby I can point to the CTAN catalogue from FAQ - answers remains as a "background task"; I suggested several ways - (last time) in which such links would be valuable. diff --git a/Master/texmf-doc/doc/english/FAQ-en/CHANGES-3.16a b/Master/texmf-doc/doc/english/FAQ-en/CHANGES-3.16a deleted file mode 100644 index a2425ca3147..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/CHANGES-3.16a +++ /dev/null @@ -1,17 +0,0 @@ -Changes in version 3.16a - -Revised answers: - Label filename: extend macro definitions, hopefully expanding the - usefulness and usability of the answer - -Bugfixes: - Label cmdstar: part of the example code was just wrong - Label enumerate: unclarity in text caused by a typo - Bug in "introduction=yes" code corrected - -Future releases: - I'm still aiming for (approximately) monthly "bugfix" releases. - There are no current plans for a major release. - -Robin Fairbairns -2006-08-03 diff --git a/Master/texmf-doc/doc/english/FAQ-en/CHANGES-3.17 b/Master/texmf-doc/doc/english/FAQ-en/CHANGES-3.17 new file mode 100644 index 00000000000..c5c26c2c451 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/CHANGES-3.17 @@ -0,0 +1,58 @@ +Changes in version 3.16d + +This file incorporates the changes from version 3.16 that previously +appeared in file CHANGES-3.16a, -3.16b and -3.16c; new changes for +this release (3.16d) are marked with a plus ("+") sign. + + +New answers: + +Label biblatex: discusses BibTeX replacements (amsrefs, biblatex) + +Label checksum: "checksum error in font" message + +Label figurehere: how to avoid floating figures/tables altogether + +Label entercompmode: "entering compatibility mode" message + +Label fontsize: how to program arbitrary font sizes in LaTeX + +Label latexqual: assessing the quality of your LaTeX + +Label mathonlyref: only referenced equations are numbered + +Label run-fn-nos: running footnote numbers when class numbers per chapter + +Revised answers: + +Label altabcr: extended examples and tidied a bit + +Label BibTeXing: add reference to Shell & Hoadley's btxFAQ + +Label books mention LaTeX Graphics Companion 2nd edition; use ISBN-13 + +Label CD: now couched in terms of the TeX collection + +Label changebar: mention changes.sty + +Label commercial:update details of Textures + +Label dec_comma: mention numprint as possible way to get things right + +Label docpictex: mention PiCTeX summary now on CTAN + +Label fonts-pln: mention pdcmac bundle + +Label ftnsect: rewrite to make recommendations clearer + +Label getbitmap: reworded to suggest that bitmaps aren't standard any more + +Label LaTeXtoPlain: suggest ways forward for aspiring translators + +Label make: mention autolatex + +Label man-latex: mention Grätzer's "short course" + +Label minxampl: editorial work, including (perhaps) clarifying web version + +Label newfont*: was newfont; content rearranged between this, plninltx* and + the new label fontsize + +Label newfunction: expand description + +Label ol-books: TeX by Topic now available from CTAN + +Label papersize: mention Acrobat Reader's default scaling + +Label plninltx*: was plninltx; content rearranged between this, newfont* and + the new fontsize + +Label protect: clarify lists of commands known to be fragile, etc + +Label psfchoice: add links to papers about maths fonts in tex; add fouriernc, + mathdesign/FS Garamond, kpfonts, minionpro and mnsymbol + +Label running-nos: rearrange to emphasise package chngctr + +Label tabcellalign: rationalised, reduced range of recommendations + +Label tocbibind: mention \phantomsection for when doing the job "by hand" + +Label twooptarg: mention the xargs package + +Label unkgrfextn: mention grffile package + +Label wdnohyph: mention \uchyph (not that it's much use) + +Bugfixes: + +Future releases: + There are no current plans for a major release, though work on the + new web-based version continues. + +Robin Fairbairns +2007-10-?? diff --git a/Master/texmf-doc/doc/english/FAQ-en/ChangeLog b/Master/texmf-doc/doc/english/FAQ-en/ChangeLog index 5312bc941b9..17b958dc5a0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/ChangeLog +++ b/Master/texmf-doc/doc/english/FAQ-en/ChangeLog @@ -1,5 +1,759 @@ +2007-11-07 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{Documentation and Help}): extend reference to + nlct's tutorials page in q-man-latex + + * faq.sty: change pdfpagemode to UseNone (but mailing ho for assurance) + + * faqbody.tex (section{Bits and pieces of (La)TeX}): typo in q-pk + +2007-11-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (section{Documentation and Help}): update german minimal + example link + +2007-11-05 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex: v3.17, today + + * sanitize.pl,texfaq2html: bring forward changes from -beta + + * faqbody.tex (throughout): ensure all \dots have empty arg + +2007-11-01 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * dirctan.tex: add xargs, xkeyval + + * faqbody.tex (subsection{LaTeX macro tools and techniques}): discuss + xargs in q-twooptarg + +2007-10-31 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{"Generic" macros and techniques}): reword + q-empty for clarity + +2007-10-30 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (section{DVI Drivers and Previewers}): editorial diddles + with q-dvi-bmp + + * dirctan.tex: restore dviljk; pretend ghostscript is on free tree + (it will be, it will); make gv browse-only + + * faqbody.tex (section{TeX Systems}): editorial work in q-editors + (section{TeX Systems}): two minor changes in q-commercial + (section{DVI Drivers and Previewers}): dviljk has reappeared + +2007-10-30 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{TeX Systems}): link to latest unsatisfactory + source for xemtex + (section{TeX Systems}): elide the mail address from atari listing in + q-texsystems + + * filectan.tex: remove the protext entry (moved to dirctan for + symmetry reasons...) + + * dirctan.tex: * the mactex entry, add protext + + * faqbody.tex (section{Acquiring the Software}): rehash q-findfont + (section{Acquiring the Software}): mention ctan copies in q-cd + +2007-10-29 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{Documentation and Help}): new link for troy + henderson's previewer in q-mfptutorials + (section{Documentation and Help}): and delete link to the metafun + tutorial, which seems to have vanished from the web :-( + (intro): today's date, add troy henderson + +2007-10-24 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{Document management}): ref new askinclude in + q-conditional + (section{Acquiring the Software}): micro-edit of q-uploads + + * filectan.tex: remove askinclude + +2007-10-23 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{Adobe Type 1 fonts}): update mtpro stuff for + mtpro2, incl providing working web link + + * sanitize-beta.pl (sanitize_line): translate \par (one instance only!) + + * faqbody.tex (section{Acquiring the Software}): add link to catalogue + set of licences in q-nonfree (rms' suggestion) + + * filectan.tex: add cat-licences + + * dirctan.tex: add kpfonts, minionpro, mnsymbol + + * faqbody.tex (subsection{Adobe Type 1 fonts}): add kpfonts and + minionpro/mnsymbol + +2007-10-22 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * dirctan.tex: add fouriernc + + * faqbody.tex (subsection*{Origins}): extend the list to members of the + committee, thus reducing the confusion (in my mind) about who is/was + and who isn't/wasn't + (subsection{Adobe Type 1 fonts}): add web location for berthold horn's + paper, add thierry bouche, similarly, in q-psfchoice + (subsection{Adobe Type 1 fonts}): add fouriernc to list; add fontsite + garamond to the list of mathdesign fonts, in q-psfchoice + +2007-10-17 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (section{Acquiring the Software}): edit q-uploads + +2007-10-17 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * sanitize-beta.pl (sanitize_line): remove \xxx|...| forms of + \ProgName, \FontName, \Package, \Class, \Email, \mailto, \File and + \Newsgroup + + * faqbody.tex (section{The joy of TeX errors}): remove last two + instances of \ProgName|...|, in q-8000 + (throughout): remove last three instances of \Email|...| + + * sanitize-beta.pl (sanitize_line): implement \ISBN* + + * faq.sty: add \ISBN* (2 args) version, for ISBN10+ISBN13 + + * faqbody.tex (section{Documentation and Help}): use \ISBN* for tlc2 + and tlgc2 (latter newly converted from original tlgc entry) + +2007-10-16 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{Bits and pieces of (La)TeX}): bits of editorial + work in q-adobetypen, q-resolns, q-fontname + (section{Acquiring the Software}): mention mirror.ctan.org in + q-archives + +2007-10-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (section{Bits and pieces of (La)TeX}): hack at q-dtx + (have asked dak about dtx in emacs...) + (section{Bits and pieces of (La)TeX}): minor editorial on q-whatenc and + q-ecfonts + (section{Bits and pieces of (La)TeX}): work on q-eps + +2007-10-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (section{Bits and pieces of (La)TeX}): rehash q-special + (section{Bits and pieces of (La)TeX}): minor editorial to q-hyphen + +2007-10-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * add-general.tex (subsection{LaTeX macro tools and techniques}): bit + more work on q-printvar + + * faqbody.tex (subsection{LaTeX macro tools and techniques}): yet more + twiddling with q-protect + +2007-10-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (section{Bits and pieces of (La)TeX}): lots of hacking of + q-virtualfonts + +2007-10-12 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * add-general.tex (subsection{LaTeX macro tools and techniques}): new + q-printvar contributed by gernot hassenpflug + + * faqbody.tex (subsection{LaTeX macro tools and techniques}): change to + q-protect developed from john harper's contribution + intro: v3.16z-4, today; add john harper to list of helpers + +2007-10-11 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * dirctan.tex: add texbytopic + + * faqbody.tex (subsection{Hyphenation}): tidy up alternatives at the + end of q-hyphoff + (subsection{Hyphenation}): mention \uchyph in q-wdnohyph + (section{Documentation and Help}): tex by topic now ctan in q-ol-books + +2007-10-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (section{The Background}): remove latexhtml around + thanh's full name in q-whatpdftex + (section{The Background}): link to q-latextoplain from q-latexandplain + (section{The Background}): tidy up references to other projects, + add luatex in q-texfuture + (section{The Background}): replace last para of q-readtex + (section{The Background}): add \href to tug's web site in q-tug* + (section{The Background}): correct a couple of \luatex (capitalised) + + * sanitize-beta.pl (sanitize_line): add def of \The (for thanh) + +2007-10-08 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * dirctan.tex: add autolatex + + * faqbody.tex (section{TeX Systems}): refer to makefile question in + q-editors, rather than just mentioning latexmk (not the only thing + wrong with that answer) + (subsection{Document management}): mention autolatex in q-make + +2007-10-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (subsection{Spacing of characters and lines}): sanity + adjustment in q-flushboth ("latest version" was 2003) + +2007-10-04 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{Current TeX-related projects}): q-biblatex from + add-general + (section{Current \TeX{}-related projects}): minor edit to q-luatex + + * dirctan.tex: amsrefs now on m/l/c + + * add-general.tex (subsection{Current TeX-related projects}): declare + that amsrefs is currently supported; while this seems true (as a + phenomenon) i wonder whether it's a good thing to rely on... + + * faqbody.tex (section{Current TeX-related projects}): diddle with + q-xetex + +2007-09-25 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * dirctan.tex: add dir excel2latex + + * filectan.tex: remove the .zip distro of excel2latex + + * faqbody.tex (section{Installing (La)TeX files}): reword text about + readme files in q-install-unpack + +2007-09-24 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (throughout): correct references to new installation qs + +2007-09-18 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex: v3.16z-1, today + (section{Installing (La)TeX files}): bunch of answers from add-general, + replacing most of the section + +2007-09-13 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{You're still stuck?}): "carefule" corrected ;-) + + * add-general.tex (subsection{Installing (La)TeX files}): lots of work + on q-what-tds and q-install-where, to clarify what's going on + +2007-09-04 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{Documentation and Help}): more emphasis on ctan + supply of documentation, in q-gethelp + (subsection{Document management}): a bit extra on changes.sty in + q-changebar (whole question needs reviewing) + (section{Documentation and Help}): ctan supply of docs, again, in + q-man-latex + +2007-08-24 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (section{The joy of TeX errors}): new q-entercompmode + and q-checksum from add-general + +2007-08-19 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (section{TeX Systems}): updated uk address for sciword + +2007-08-17 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{Documentation and Help}): add a warning about + mailing inappropriate people in q-gethelp + (section{Current \TeX{}-related projects}): the project is latex, not + latex3 -- correct some of the text of q-latex3 + (subsection{Tables of contents and indexes}): mention the use of + \phantomsection in q-tocbibind + + * dirctan.tex: amslatex-primer moved to info/amslatex/primer, now + +2007-08-16 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * add-general.tex (subsection{Odds and ends}): add ref to mathpazo on + ctan, in q-osf + + * faqbody.tex (subsection{Floating tables, figures, etc.}): new + q-figurehere from add-general + +2007-07-27 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{Bits and pieces of AllTeX}): restored "\" to + "acro" in q-virtualfonts + +2007-07-25 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{Tables, figures and diagrams}): typo in + q-struttab, spotted by karl b + +2007-07-23 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{The joy of TeX errors}): extend typo examples, + and tidy coding, in q-altabcr + (subsection{Tables, figures and diagrams}): rationalise, reduce range + of overlapping recommendations in q-tabcellalign + +2007-07-16 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * dirctan.tex: add cmolddig, eco + + * add-general.tex (subsection{Current TeX-related projects}): write + more on biblatex in q-biblatex + (subsection{Odds and ends}): mention vf access in q-osf + +2007-07-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * add-general.tex (subsection{Current TeX-related projects}): first + stab at new q-biblatex + + * dirctan.tex: add biblatex and amsrefs; remove dvi2xx and dvilj4, + correct lollipop + +2007-07-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (section{Documentation and Help}): editorial tidies of + q-writecls, mention clsguide.pdf + +2007-07-03 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex: v3.16c-17, today; add axel sommerfeldt to list + (section{The joy of TeX errors}): add further text in q-hyperdupdest, + as suggested by axel sommerfeldt + +2007-06-29 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * add-general.tex (subsection{Odds and ends}): new q-osf + +2007-06-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex: v 3-16c-15, today; mention neto's input on numprint in + list of helpers + + * dirctan.tex: add numprint + + * faqbody.tex (subsection{Typesetting specialities}): mention numprint + in q-dec_comma + +2007-06-13 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * dirctan.tex: add texlive + + * faqbody.tex (section{TeX Systems}): add details of a mactex mailing + list in q-texsystems + +2007-06-11 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{Common errors}): mention fragility of \url in + q-verbwithin + (subsection{Typesetting specialities}): mention lack of robustness in + q-seturl, and explain use of \urldef to deal with the problem + +2007-06-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq.sty: yet another small typo (in the fail branch, this time) + + * filectan.tex: add mil-short (gratzer's offering) + + * faqbody.tex (section{Documentation and Help}): add gratzer's short + course to q-man-latex + +2007-06-06 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{The joy of TeX errors}): editorial correction + of q-optionclash + +2007-06-05 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faq.sty: check for etex + + * add-general.tex (subsection{Installing (La)TeX files}): add some + actual text to q-inst-tidy and q-what-tds + (subsection{The Joy of TeX errors}): new q-entercompmode + +2007-06-04 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * add-general.tex (subsection{Installing (La)TeX files}): editorial + in q-install-where and q-inst-wlcf + + * dirctan.tex: correct fptex link (even though nothing now uses it...) + +2007-06-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (section{Documentation and Help}): flynn's classes.dtx + article now rev., in tub (q-writecls) + +2007-06-01 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{TeX Systems}): mention texshop in mactex distr, + in q-editors + (section{TeX Systems}): deal with oztex and cmactex's relation to os/x + (so far as i understand what's going on) in q-texsystems + +2007-05-31 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * add-general.tex (subsection{Generic macros and techniques}): complete + and clarify q-ovwtsym + +2007-05-30 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * sanitize-beta.pl (sanitize_line): add \xetex + + * faq.sty: add \xetex + + * faqbody.tex: v3.16c-15, today + (section{Current TeX-related projects}): xetex is available in texlive + and will be in miktex 2.7, mention bidi capabilities in q-xetex + +2007-05-29 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{Format conversions}): extend and make less + abrupt the stuff of q-latextoplain + + * add-general.tex (subsection{Installing (La)TeX files}): trying to bed + this set of answers down -- work on several of the questions + +2007-05-24 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex: v3.16c-14, today + (section{Documentation and Help}): attempt to clarify q-minxampl + +2007-05-23 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{Documentation and Help}): tidy the two + references to nicola talbot in q-man-latex + +2007-05-21 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex: v3.16c-13, today + (subsection{Metafont fonts}): hack at q-getbitmap to hint that bitmap + fonts aren't really the world's prime concern any more + +2007-05-14 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{Labels and references}): list zref's options + in q-nameref + (section{The joy of TeX errors}): correct error in q-errmissitem + (inserted yesterday at home :-( ) + +2007-05-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (section{The joy of TeX errors}): discuss lists inside + tables, in q-errmissitem + +2007-05-11 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * add-general.tex (subsection{Installing (La)TeX files}): miktex stuff + given a bit of a going-over in q-install-where (plus a few + consequential changes + + * sanitize-beta.pl (sanitize_line): add \textbackslash{} + +2007-05-10 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{Lists}): expand details of enumitem in + q-complist + +2007-05-09 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{Lists}): expand on enumitem stuff in + q-interruptlist (it _does_ allow nested interruptions ... sort of + +2007-05-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex: v3.16c-12, today + (subsection{LaTeX macro programming}): new q-latexqual from add-general + (subsection{Mathematics}): new q-mathonlyref from add-general + +2007-05-08 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{Macros for using fonts}): mention that eplain + doesn't do font selection in q-fonts-pln + (subsection{LaTeX macro tools and techniques}): editorial on q-atsigns + +2007-05-05 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * texfaq2html-beta: use &[lr][sd]quo; in decorating text + + * dirctan.tex: add pdcmac + + * faqbody.tex (subsection{Macros for using fonts}): mention pdcmac in + q-fonts-pln + +2007-05-05 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * locations.mk: correct path to cgi, tidy + +2007-05-04 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * texfaq2html-beta: escape characters in keyword strings + + * sanitize-beta.pl (sanitize_line): add \extension + + * faqbody.tex (section{The joy of TeX errors}): mention grffile package + in q-unkgrfextn + + * faq.sty: add \extension command + + * faqbody.tex: v3.16c-11, today + +2007-05-03 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * texfaq2html-beta: redo decoding of % in code reading switches + + * faq.sty: correct typo + +2007-04-29 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * sanitize-beta.pl (sanitize_line): add pictex(!) and texlive + + * faq.sty: add def of \texlive + + * faqbody.tex: v3.16c-10, today + (subsection{Alternative document classes}): add a pointer to context + resources in q-slidecls + (throughout): typeset variants of texlive -> \texlive{} + +2007-04-27 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * dirctan.tex: remove tetex-beta, tetex to point at obsolete/ tree + + * filectan.tex: add bibtex-faq + + * faqbody.tex (subsection{Page layout}): mention ar scaling issues in + q-papersize, and tidy rest of text, too + (section{Documentation and Help}): remove unnecessary conditionals in + q-gethelp + (section{Documentation and Help}): tidy q-bibtexing, add reference to + btxfaq + +2007-04-25 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * Makefile (inst-perl[-beta]): everything on standard web server, use + cp -p instead of copy -t, adjust help + +2007-04-24 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex: version 3.16c-9, today + (subsection{Footnotes}): rewrite answer q-ftnsect + (section{TeX Systems}): update bluesky information in q-commercial + +2007-04-16 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * add-general.tex (subsection{Installing (La)TeX files}): stick some + text in q-install-doc + +2007-04-10 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * add-general.tex (subsection{Installing (La)TeX files}): further + clarification of options in q-install-find + (subsection{Installing (La)TeX files}): flesh out answer + q-install-unpack, elaborating on what appears in q-dtx + (subsection{Installing (La)TeX files}): new q-install-doc placeholder + + * faqbody.tex: v3.16c-8, today + (subsection{Tables, figures and diagrams}): tidy up refs to ltxtable in + q-fixwidtab + +2007-04-03 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * newfaq-patch.tex: add patch option to \documentclass + + * faq.cls: deal with option patch, produce different page footer if so + +2007-04-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (subsection{Footnotes}): mention bigfoot in q-multfoot + +2007-03-27 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{LaTeX macro tools and techniques}): correct + \dots (with no {}) in q-ltxabbrv + +2007-03-22 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex: v3.16c-7; remove all references to package web2c + +2007-03-21 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * dirctan.tex: remove web2c, web2c* + + * filectan.tex: remove unixtex.ftp, correct protext + +2007-03-20 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (section{TeX Systems}): tops-20 ftp link regularised + (section{Acquiring the Software}): redo description of ctan sites, + with alternative versions for hyper (wide) and non-hyper (narrow) + version in q-archives + + * sanitize-beta.pl (sanitize_line): \FTP to accept braced args only + +2007-03-19 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (section{TeX Systems}): another thrash at q-texsystems + +2007-03-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex: v3.16c, today + (throughout): remove traces of tetex, and rewrite as necessary + +2007-03-17 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (section{Acquiring the Software}): redo q-cd to talk + about the tex collection, rather than just tex live + (section{TeX Systems}): work (so far) on unix, linux and win32 + (win32 contains a line of "+++..." to follow on with) + +2007-03-16 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex: v3.16c-5, today + (section{The Background}): 2^16->2^15 in q-etex (!) + (subsection{Why shouldn't I?}): replace q-newfont with q-newfont* from + add-general + (subsection{LaTeX macro tools and techniques}): replace q-plninltx with + q-plninltx* from add-general + (subsection{LaTeX macro programming}): new q-fontsize from add-general + (subsection{Footnotes}): new q-run-fn-nos from add-general + +2007-03-15 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * texfaq2html-beta: attempts at introducing some sanity into the + search code; notably unsuccessful, to date + + * add-general.tex (subsection{Odds and ends}): proof-reading + corrections in q-run-fn-nos, q-newfont*, q-plninltx* and q-fontsize + +2007-03-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * texfaq2file: as for texfaq2html-beta + + * texfaq2html-gamma: as for texfaq2html-beta + + * texfaq2html-beta: add new *-names to %label_to_file + + * add-general.tex (subsection{Odds and ends}): new q-fontsize, + q-plninltx* and q-newfont* (three questions from the old 2 non-*) + +2007-03-09 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * CHANGES-3.16d: revised q-running-nos + + * faqbody.tex (subsection{LaTeX macro tools and techniques}): restore + commented-out hack above q-ltxabbrv; it's not clever and it's not + pretty, but the printed output is less awful than without the hack + +2007-03-08 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{LaTeX macro programming}): recommend chngctr + first, the two fragment alternatives second in q-running-nos + + * add-general.tex (subsection{Footnotes}): new q-run-fn-nos + +2007-03-02 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * texfaq2html-gamma: modest doodling + +2007-02-21 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * add-general.tex (subsection{Installing (La)TeX files}): odd tinkering + with answers in this section -- needs concerted attack + +2007-02-15 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * add-general.tex (subsection{Odds and ends}): new q-fontsize, to meld + with (new) q-plninltx* and q-newfont* + + * faqbody.tex (section{Current TeX-related projects}): make mention of + lua itself in q-luatex into a hyperref + +2007-02-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq.sty: add \LuaTeX + + * faqbody.tex: v3.16c-4, today + (section{The Background}): rewrite of q-context from Aditya Mahajan + (intro): Aditya Mahajan in list of helpers + (section{Current TeX-related projects}): tidy luatex thing a bit, add + link to luatex.org site + +2007-02-06 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex (subsection{Mathematics}): correct typo in q-limits + (introduced, but change not documented, on 2007-01-30) + + * add-general.tex (subsection{Mathematics}): new q-mathonlyref + +2007-01-30 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex: today's date + (subsection{Mathematics}): more detail about "ad hoc" operators in + q-newfunction + +2007-01-26 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex: today's date + (section{Introduction}): make links to pdf copies \CTANhref + +2007-01-24 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * dirctan.tex: add changes + remove nonfree from bakoma-tex, dvi2tty, foiltex + + * faqbody.tex: today's date + (subsection{Document management}): mention changes pkg in q-changebars + +2007-01-23 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * dirctan.tex: list listbib and biblist + + * faqbody.tex: today's date + (subsection{Manipulating whole bibliographies}): mention listbib and + biblist in q-nocite* + +2007-01-22 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * newfaq-patch.tex: input additions (!) + + * faqbody.tex (section{Documentation and Help}): correct ctan ref for + pictex-summary + +2007-01-22 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * faqbody.tex: v3.16c-3, today + (subsection{Spacing of characters and lines}): mention microtype's + letterspace.sty in q-letterspace + +2007-01-05 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + + * patchdates.tex: pl4.14, today + + * add-general.tex (subsection{The Joy of TeX errors}): new q-checksum + +2006-12-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * dirctan.tex: add pictex-summary + + * faqbody.tex: v3.16c-2, today + (section{Documentation and Help}): pictex summary in q-docpictex + +2006-12-20 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faqbody.tex (section{Support Packages for TeX}): correct text about + ispell vs. aspell + 2006-12-18 Robin Fairbairns <rf10@mole.cl.cam.ac.uk> + *** released *** + + * Makefile ($(WEB_BETA)*): use cp rather than copy (!) + + * sanitize.pl (sanitize_line): add \narrowonly, \wideonly + * faqbody.tex: v3.16c-1, today (for release) 2006-12-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> diff --git a/Master/texmf-doc/doc/english/FAQ-en/README.TEXLIVE b/Master/texmf-doc/doc/english/FAQ-en/README.TEXLIVE new file mode 100644 index 00000000000..d9a8ab7e600 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/README.TEXLIVE @@ -0,0 +1,7 @@ +The following files have been removed in the TeX Live installation of +the current package, typically due to duplication, lack of space, or +missing source code. You can find these files on CTAN. If questions or +concerns, email tex-live.org. + + letterfaq.pdf + newfaq.pdf diff --git a/Master/texmf-doc/doc/english/FAQ-en/Ulogo.fd b/Master/texmf-doc/doc/english/FAQ-en/Ulogo.fd deleted file mode 100644 index f2c1a22c715..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/Ulogo.fd +++ /dev/null @@ -1,47 +0,0 @@ -%% -%% This is file `Ulogo.fd', -%% generated with the docstrip utility. -%% -%% The original source files were: -%% -%% mflogo.dtx (with options: `Ulogo') -%% -%% Copyright (C) 1994,95 Ulrik Vieth -%% All rights reserved. -%% -%% This file is part of the mflogo package. -%% ---------------------------------------- -%% -%% This is a generated file. Permission is granted to customize the -%% declarations in this file to serve the needs of your installation. -%% However, no permission is granted to distribute a modified version -%% of this file under its original name. -%% -\ProvidesFile{Ulogo.fd} - [1995/12/04 v1.5c LaTeX font definitions for METAFONT logo fonts] -\DeclareFontFamily{U}{logo}{} -\DeclareFontShape{U}{logo}{m}{n}{ - <8> <9> gen * logo - <10> <10.95> <12> <14.4> <17.28> <20.74> <24.88> logo10 -}{} -\DeclareFontShape{U}{logo}{m}{it}{ - <8> <9> gen * logosl - <10> <10.95> <12> <14.4> <17.28> <20.74> <24.88> logosl10 -}{} -\DeclareFontShape{U}{logo}{m}{sl}{ - <-> ssub * logo/m/it -}{} -\DeclareFontShape{U}{logo}{sbc}{n}{ - <8> <9> sub * logo/m/n - <10> <10.95> <12> <14.4> <17.28> <20.74> <24.88> logobf10 -}{} -\DeclareFontShape{U}{logo}{b}{n}{ - <8> <9> sub * logo/m/n - <10> <10.95> <12> <14.4> <17.28> <20.74> <24.88> logod10 -}{} -\DeclareFontShape{U}{logo}{bx}{n}{ - <-> ssub * logo/b/n -}{} -\endinput -%% -%% End of file `Ulogo.fd'. diff --git a/Master/texmf-doc/doc/english/FAQ-en/dirctan.tex b/Master/texmf-doc/doc/english/FAQ-en/dirctan.tex index 126c9b051a1..91d2f5b4fb4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/dirctan.tex +++ b/Master/texmf-doc/doc/english/FAQ-en/dirctan.tex @@ -41,8 +41,9 @@ \CTANdirectory{amsfonts-latex}{fonts/amsfonts/latex} \CTANdirectory{amsfonts-plain}{fonts/amsfonts/plaintex} \CTANdirectory{amslatex}{macros/latex/required/amslatex} -\CTANdirectory{amslatex-primer}{info/amslatex-primer} +\CTANdirectory{amslatex-primer}{info/amslatex/primer} \CTANdirectory{amspell}{support/amspell} +\CTANdirectory{amsrefs}{macros/latex/contrib/amsrefs} \CTANdirectory{amstex}{macros/amstex} \CTANdirectory{answers}{macros/latex/contrib/answers} \CTANdirectory{ant}{systems/ant} @@ -63,6 +64,7 @@ \CTANdirectory{atob}{tools/atob} \CTANdirectory{atops}{support/atops} \CTANdirectory{auctex}{support/auctex} +\CTANdirectory{autolatex}{support/autolatex} \CTANdirectory{aweb}{web/ada/aweb} \CTANdirectory{awk}{web/spiderweb/src/awk} \CTANdirectory{axodraw}{graphics/axodraw} @@ -70,8 +72,8 @@ \CTANdirectory{babelbib}{biblio/bibtex/contrib/babelbib} \CTANdirectory{badge}{macros/plain/contrib/badge} \CTANdirectory{bakoma}{fonts/cm/ps-type1/bakoma} -\CTANdirectory{bakoma-tex}{nonfree/systems/win32/bakoma} -\CTANdirectory*{bakoma-texfonts}{nonfree/systems/win32/bakoma/fonts} +\CTANdirectory{bakoma-tex}{systems/win32/bakoma} +\CTANdirectory*{bakoma-texfonts}{systems/win32/bakoma/fonts} \CTANdirectory{barcodes}{fonts/barcodes} \CTANdirectory{bard}{fonts/bard} \CTANdirectory{barr}{macros/generic/diagrams/barr} @@ -96,7 +98,9 @@ \CTANdirectory{bibextract}{biblio/bibtex/utils/bibextract} \CTANdirectory{bibgerm}{biblio/bibtex/contrib/germbib} \CTANdirectory{bibindex}{biblio/bibtex/utils/bibindex} +\CTANdirectory{biblatex}{macros/latex/exptl/biblatex} \CTANdirectory{biblio}{info/biblio} +\CTANdirectory{biblist}{macros/latex209/contrib/biblist} \CTANdirectory{bibsort}{biblio/bibtex/utils/bibsort} \CTANdirectory{bibtex}{support/lsedit/bibtex} \CTANdirectory{bibtex-doc}{biblio/bibtex/distribs/doc} @@ -156,6 +160,7 @@ \CTANdirectory{cellular}{macros/plain/contrib/cellular} \CTANdirectory{cellspace}{macros/latex/contrib/cellspace} \CTANdirectory{changebar}{macros/latex/contrib/changebar} +\CTANdirectory{changes}{macros/latex/contrib/changes} \CTANdirectory{chappg}{macros/latex/contrib/chappg} \CTANdirectory{chapterfolder}{macros/latex/contrib/chapterfolder} \CTANdirectory{charconv}{support/charconv} @@ -190,6 +195,7 @@ %[fonts/cmcyralt] \CTANdirectory{cmfrak}{fonts/gothic/cmfrak} \CTANdirectory{cmoefont}{fonts/cmoefont} +\CTANdirectory{cmolddig}{fonts/cmolddig} \CTANdirectory{cmoutlines}{fonts/cm/cmoutlines} \CTANdirectory{cmpica}{fonts/cmpica} \CTANdirectory{cms_help_files}{macros/text1/cms_help_files} @@ -271,8 +277,7 @@ \CTANdirectory{dvi-augsburg}{dviware/dvi-augsburg} \CTANdirectory{dvi2bitmap}{dviware/dvi2bitmap} \CTANdirectory{dvi2pcl}{dviware/dvi2pcl} -\CTANdirectory{dvi2tty}{nonfree/dviware/dvi2tty} -\CTANdirectory{dvi2xx}{dviware/dvi2xx} +\CTANdirectory{dvi2tty}{dviware/dvi2tty} \CTANdirectory{dvibit}{dviware/dvibit} \CTANdirectory{dvibook}{dviware/dvibook} \CTANdirectory{dvichk}{dviware/dvichk} @@ -280,7 +285,7 @@ \CTANdirectory{dvidjc}{dviware/dvidjc} \CTANdirectory{dvidvi}{dviware/dvidvi} \CTANdirectory{dviimp}{dviware/dviimp} -\CTANdirectory{dvilj4}{systems/msdos/dviware/dvilj4} +\CTANdirectory{dviljk}{dviware/dviljk} \CTANdirectory{dvimerge}{dviware/dvimerge} \CTANdirectory{dvimfj}{systems/msdos/emtex-contrib/dvimfj} \CTANdirectory{dvipage}{dviware/dvipage} @@ -300,6 +305,7 @@ \CTANdirectory{ebib}{biblio/bibtex/utils/ebib} \CTANdirectory{ec}{fonts/ec} \CTANdirectory{ec-plain}{macros/ec-plain} +\CTANdirectory{eco}{fonts/eco} \CTANdirectory{economic}{biblio/bibtex/contrib/economic} \CTANdirectory{edmac}{macros/plain/contrib/edmac} \CTANdirectory{ednotes}{macros/latex/contrib/ednotes} @@ -341,6 +347,7 @@ \CTANdirectory{eurosym}{fonts/eurosym} \CTANdirectory{everypage}{macros/latex/contrib/everypage} \CTANdirectory{excalibur}{systems/mac/support/excalibur} +\CTANdirectory{excel2latex}{support/excel2latex} \CTANdirectory{excerpt}{web/spiderweb/tools/excerpt} \CTANdirectory{expdlist}{macros/latex/contrib/expdlist} \CTANdirectory{extracm}{fonts/amsfonts/sources/extracm} @@ -364,7 +371,7 @@ \CTANdirectory{flowfram}{macros/latex/contrib/flowfram} \CTANdirectory{fnbreak}{macros/latex/contrib/fnbreak} \CTANdirectory{fncychap}{macros/latex/contrib/fncychap} -\CTANdirectory{foiltex}{nonfree/macros/latex/contrib/foiltex} +\CTANdirectory{foiltex}{macros/latex/contrib/foiltex} \CTANdirectory{fontch}{macros/plain/contrib/fontch} \CTANdirectory{fontinst}{fonts/utilities/fontinst} \CTANdirectory{fontname}{info/fontname} @@ -374,6 +381,7 @@ \CTANdirectory{footnpag}{macros/latex/contrib/footnpag} \CTANdirectory{for_tex}{biblio/bibtex/contrib/germbib/for_tex} \CTANdirectory{fourier}{fonts/fourier-GUT} +\CTANdirectory{fouriernc}{fonts/fouriernc} \CTANdirectory{frankenstein}{macros/latex/contrib/frankenstein} \CTANdirectory{french-faq}{help/LaTeX-FAQ-francaise} \CTANdirectory{ftpd}{tools/ftpd} @@ -389,7 +397,7 @@ \CTANdirectory{german}{language/german} \CTANdirectory{germbib}{biblio/bibtex/contrib/germbib} \CTANdirectory{gfs}{info/examples/FirstSteps} % gratzer's -\CTANdirectory*{ghostscript}{nonfree/support/ghostscript} +\CTANdirectory*{ghostscript}{support/ghostscript} \CTANdirectory*{ghostview}{support/ghostscript/gnu/ghostview} \CTANdirectory{glo+idxtex}{indexing/glo+idxtex} \CTANdirectory{gnuplot}{graphics/gnuplot} @@ -406,7 +414,7 @@ \CTANdirectory{gsftopk}{fonts/utilities/gsftopk} \CTANdirectory*{gsview}{nonfree/support/ghostscript/ghostgum} \CTANdirectory{gut}{usergrps/gut} -\CTANdirectory{gv}{support/gv} +\CTANdirectory*{gv}{support/gv} \CTANdirectory{ha-prosper}{macros/latex/contrib/ha-prosper} \CTANdirectory{half}{fonts/cm/utilityfonts/half} \CTANdirectory{halftone}{fonts/halftone} @@ -478,6 +486,7 @@ \CTANdirectory{koma-script}{macros/latex/contrib/koma-script} \CTANdirectory{korean}{fonts/korean} %[language/korean] +\CTANdirectory{kpfonts}{fonts/kpfonts} \CTANdirectory{kyocera}{dviware/kyocera} \CTANdirectory{l2a}{support/l2a} \CTANdirectory{l2sl}{language/swedish/slatex/l2sl} @@ -515,9 +524,10 @@ \CTANdirectory{lgrind}{nonfree/support/lgrind} \CTANdirectory{lharc}{tools/lharc} \CTANdirectory{lineno}{macros/latex/contrib/lineno} +\CTANdirectory{listbib}{macros/latex/contrib/listbib} \CTANdirectory{listings}{macros/latex/contrib/listings} \CTANdirectory{lm}{fonts/lm} -\CTANdirectory{lollipop}{nonfree/macros/lollipop} +\CTANdirectory{lollipop}{macros/lollipop} \CTANdirectory{lookbibtex}{biblio/bibtex/utils/lookbibtex} \CTANdirectory{lsedit}{support/lsedit} \CTANdirectory*{lshort-parent}{info/lshort} @@ -529,7 +539,7 @@ \CTANdirectory{lwc}{info/examples/lwc} \CTANdirectory{ly1}{macros/latex/contrib/psnfssx/ly1} \CTANdirectory{machdr}{tools/macunpack/machdr} -\CTANdirectory{mactex}{systems/mac/mactex} +\CTANdirectory*{mactex}{systems/mac/mactex} \CTANdirectory{mactotex}{graphics/mactotex} \CTANdirectory{macunpack}{tools/macunpack} \CTANdirectory{macutils}{tools/macutils} @@ -577,10 +587,12 @@ \CTANdirectory{midnight}{macros/generic/midnight} \CTANdirectory{miktexppc}{obsolete/systems/win32/miktexppc} \CTANdirectory{miktex-AXP}{obsolete/systems/win32/miktex-AXP} +\CTANdirectory{minionpro}{fonts/minionpro} \CTANdirectory{minitoc}{macros/latex/contrib/minitoc} \CTANdirectory{mirror}{tools/mirror} \CTANdirectory{mixed}{tools/macutils/mixed} \CTANdirectory{mma2ltx}{graphics/mma2ltx} +\CTANdirectory{mnsymbol}{fonts/mnsymbol} \CTANdirectory{mnu}{support/mnu} \CTANdirectory{models}{macros/text1/models} \CTANdirectory{moderncv}{macros/latex/contrib/moderncv} @@ -619,6 +631,7 @@ \CTANdirectory{ntheorem}{macros/latex/contrib/ntheorem} \CTANdirectory{nts-l}{digests/nts-l} \CTANdirectory{nts}{systems/nts} +\CTANdirectory{numprint}{macros/latex/contrib/numprint} \CTANdirectory{nuweb}{web/nuweb} \CTANdirectory{nuweb0.87b}{web/nuweb/nuweb0.87b} \CTANdirectory{nuweb_ami}{web/nuweb/nuweb_ami} @@ -649,6 +662,7 @@ \CTANdirectory{pbmtopk}{graphics/pbmtopk} \CTANdirectory{pbox}{macros/latex/contrib/pbox} \CTANdirectory{pcwritex}{support/pcwritex} +\CTANdirectory{pdcmac}{macros/plain/contrib/pdcmac} \CTANdirectory{pdfpages}{macros/latex/contrib/pdfpages} \CTANdirectory{pdftex-graphics}{macros/pdftex/graphics} \CTANdirectory{pdftricks}{macros/latex/contrib/pdftricks} @@ -664,6 +678,7 @@ \CTANdirectory{pictex}{graphics/pictex} \CTANdirectory{pictex-addon}{graphics/pictex/addon} \CTANdirectory{pictex-converter}{support/pictex-converter} +\CTANdirectory{pictex-summary}{info/pictex/summary} \CTANdirectory{pkbbox}{fonts/utilities/pkbbox} \CTANdirectory{pkfix}{support/pkfix} \CTANdirectory{placeins}{macros/latex/contrib/placeins} @@ -685,6 +700,7 @@ \CTANdirectory{printsamples}{fonts/utilities/mf2ps/doc/printsamples} \CTANdirectory{program}{macros/latex/contrib/program} \CTANdirectory{proofs}{macros/generic/proofs} +\CTANdirectory*{protext}{systems/win32/protext} \CTANdirectory{ppower4}{support/ppower4} \CTANdirectory{ppr-prv}{macros/latex/contrib/ppr-prv} \CTANdirectory{prosper}{macros/latex/contrib/prosper} @@ -820,8 +836,7 @@ \CTANdirectory{telugu}{language/telugu} \CTANdirectory{tengwar}{fonts/tengwar} \CTANdirectory*{testflow}{macros/latex/contrib/IEEEtran/testflow} -\CTANdirectory*{tetex}{systems/unix/teTeX/current/distrib} -\CTANdirectory{tetex-beta}{systems/unix/teTeX-beta} +\CTANdirectory*{tetex}{obsolete/systems/unix/teTeX/current/distrib} \CTANdirectory{tex--xet}{systems/knuth/tex--xet} \CTANdirectory{tex-d-l}{digests/tex-d-l} \CTANdirectory{tex-implementors}{digests/tex-implementors} @@ -832,6 +847,7 @@ \CTANdirectory{tex2rtf}{support/tex2rtf} \CTANdirectory{tex88}{digests/tex88} \CTANdirectory{tex8fmts}{macros/generic/cptex/tex8fmts} +\CTANdirectory{texbytopic}{info/texbytopic} \CTANdirectory{texcalc}{support/texcalc} \CTANdirectory{texchord}{macros/generic/texchord} \CTANdirectory{texcnvfaq}{help/wp-conv} @@ -846,6 +862,7 @@ \CTANdirectory{texinfo}{macros/texinfo/texinfo} \CTANdirectory{texix}{macros/text1/texix} \CTANdirectory{texline}{digests/texline} +\CTANdirectory*{texlive}{systems/texlive} \CTANdirectory*{texmacs}{systems/unix/TeXmacs} \CTANdirectory*{texniccenter}{systems/win32/TeXnicCenter} \CTANdirectory{texpert}{systems/msdos/texpert} @@ -954,12 +971,10 @@ \CTANdirectory{wasysym}{macros/latex/contrib/wasysym} \CTANdirectory{wd2latex}{support/wd2latex} \CTANdirectory{web}{systems/knuth/web} -\CTANdirectory{web2c}{systems/web2c} -\CTANdirectory*{web2c*}{systems/web2c} \CTANdirectory{webtoc}{support/makeprog/webtoc} \CTANdirectory{whatstex}{info/whatstex} \CTANdirectory{williams}{macros/latex/contrib/williams} -\CTANdirectory{fptex}{systems/win32/fptex} +\CTANdirectory{fptex}{obsolete/systems/win32/fptex} \CTANdirectory{winw2ltx}{support/winw2ltx} \CTANdirectory{word2tex}{support/word2tex} \CTANdirectory{word_tex}{support/word_tex} @@ -967,6 +982,7 @@ \CTANdirectory{wp2latex}{support/wp2latex} \CTANdirectory{wrapfig}{macros/latex/contrib/wrapfig} \CTANdirectory{wsuipa}{fonts/wsuipa} +\CTANdirectory{xargs}{macros/latex/contrib/xargs} \CTANdirectory{xbibfile}{biblio/bibtex/utils/xbibfile} \CTANdirectory{xbin}{tools/xbin} \CTANdirectory{xcolor}{macros/latex/contrib/xcolor} @@ -975,6 +991,7 @@ \CTANdirectory{xettex}{language/xettex} \CTANdirectory{xfig}{graphics/xfig} \CTANdirectory*{xindy}{support/xindy} +\CTANdirectory{xkeyval}{macros/latex/contrib/xkeyval} \CTANdirectory{xmltex}{macros/xmltex/base} \CTANdirectory*{xpdf}{support/xpdf} \CTANdirectory{xtab}{macros/latex/contrib/xtab} diff --git a/Master/texmf-doc/doc/english/FAQ-en/faq.cls b/Master/texmf-doc/doc/english/FAQ-en/faq.cls index 30426099686..a5ae3cdf54e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/faq.cls +++ b/Master/texmf-doc/doc/english/FAQ-en/faq.cls @@ -4,6 +4,10 @@ \NeedsTeXFormat{LaTeX2e}[1995/12/01] +\newif\if@patchversion +\@patchversionfalse +\DeclareOption{patch}{\@patchversiontrue} + \DeclareOption*{\PassOptionsToClass{\CurrentOption}{article}} \ProcessOptions @@ -57,6 +61,25 @@ \footnotesep 6\p@ \skip\footins 19.5\p@ plus 12\p@ \@minus \p@ +% page footer: include date if patched version +\def\@twodigit#1{\ifnum#1<10\relax0\fi\number#1} +\def\faq@patched@date{\@arabic\year-\@twodigit\month-\@twodigit\day} +\if@patchversion + \renewcommand\ps@plain{% + \let\@mkboth\@gobbletwo + \let\@evenhead\@empty + \let\@oddhead\@empty + \def\@oddfoot{% + \reset@font + \hfil + \faq@patched@date\ : \thepage + \hfil + }% + \let\@evenfoot\@oddfoot + } + \let\ps@myplain\ps@plain + \pagestyle{myplain} +\fi % little patch generated in investigating a request from a user here % in cambridge \let\FAQ@@tableofcontents\tableofcontents diff --git a/Master/texmf-doc/doc/english/FAQ-en/faq.sty b/Master/texmf-doc/doc/english/FAQ-en/faq.sty index 0baf9badfdf..f855d6af3d8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/faq.sty +++ b/Master/texmf-doc/doc/english/FAQ-en/faq.sty @@ -2,7 +2,12 @@ % % uses production LaTeX 2e commands \NeedsTeXFormat{LaTeX2e}[1994/06/01]% at least! -\ProvidesPackage{faq}[2002/10/01 v2.3 English TeX FAQ macros] +\ProvidesPackage{faq}[2007/06/08 v2.4 English TeX FAQ macros] + +% this package new requires etex +\@ifundefined{eTeXversion}{% + \PackageError{faq}{This package requires e-TeX}{}% +}{} % % something affecting fonts: do we use only freely available fonts @@ -66,7 +71,7 @@ ,colorlinks% ,pdftitle=The\ UK\ TeX\ FAQ% ,linkcolor=blue% - ,pdfpagemode=None% + ,pdfpagemode=UseNone% ,pdfstartview=FitH% % ,bookmarks=false% ,bookmarksnumbered% @@ -149,6 +154,7 @@ \newcommand\AMSLaTeX{AMS\LaTeX} \newcommand\BibTeX{Bib\TeX} \newcommand\PiCTeX{PiC\TeX} +\newcommand\texlive{\TeX-live} % % ifthenelse for the undefined references \RequirePackage{ifthen} @@ -196,6 +202,7 @@ \providecommand\CDROM{\acro{CD-ROM}} \providecommand\elatex{e-LaTeX} \providecommand\miktex{MiKTeX} +\providecommand\xetex{XeTeX} % %% \providecommand\TeXXeT{\TeX-{}-X\lower.5ex\hbox{E}\kern-.1667emT\@} %\providecommand\MLTeX{ML-\TeX} @@ -293,6 +300,7 @@ \newcommand\ExTeX{Ex\TeX} \newcommand\NTS{NTS} \newcommand\PDFTeX{PDF\TeX} +\newcommand\LuaTeX{Lua\TeX} %\newcommand\TeXXeT{TeX-{}-XeT} \newcommand\AllTeX{(La)\TeX} @@ -548,7 +556,9 @@ % % ISBN references -\def\ISBN#1{\mbox{\acro{ISBN}}~#1} +\def\ISBN{\@ifstar\@ISBNstar\@ISBN} +\def\@ISBNstar#1#2{\acro{ISBN}-10~#1, \acro{ISBN}-13~#2} +\def\@ISBN#1{\acro{ISBN}-10~#1} % % Alan's code for CTAN references (now hacked to be capable of urls % for use in pdf output): @@ -1063,6 +1073,7 @@ % minuscule bit more structured markup... \def\environment#1{\texttt{#1}} \def\pkgoption#1{\texttt{#1}} +\def\extension#1{\texttt{.#1}} % deal with tabular: special defs to make texfaq2html doable \let\tbamp& diff --git a/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex b/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex index b0e724f163d..68efea3ebb0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex +++ b/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex @@ -1,4 +1,4 @@ -\def\faqfileversion{3.16c-1} \def\faqfiledate{2006-12-18} +\def\faqfileversion{3.17} \def\faqfiledate{2007-11-05} % % The above line defines the file version and date, and must remain % the first line with any `assignment' in the file, or things will @@ -26,10 +26,10 @@ covered from the viewpoint of a \LaTeX{} user. You may use the \acro{FAQ} \begin{itemize} \item by reading a printed document, -\item by browsing a \acro{PDF} file: copies, with hyperlinks to assist - browsing, are to be found on \acro{CTAN} at \CTANref{faq-a4} - (formatted for A4 paper) or at \CTANref{faq-letter} (formatted for - North American ``letter'' paper), or +\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 \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 @@ -49,13 +49,13 @@ the existence of compressed archive files of the directory, that the server would be happy to create ``on the fly''. The \acro{FAQ} therefore offers three possible links for downloading directories (that aren't already designated ``browse only''): the links give you -\texttt{.zip} and \texttt{.tar.gz} archives, and a link for browsing +\extension{zip} and \extension{tar.gz} archives, and a link for browsing the directory. Fortunately, \acro{CTAN} is switching to statically-generated directory archive files; many directories mentioned in this \acro{FAQ} -will also exist as \texttt{.zip} files on the archives, and won't fall -foul of the browser problem. Of course, if the \texttt{.zip} file +will also exist as \extension{zip} files on the archives, and won't fall +foul of the browser problem. Of course, if the \extension{zip} file does not exist, and the browser is playing up, you will need to use the ``browse'' link. \end{htmlversion} @@ -68,7 +68,7 @@ available from a \acro{CTAN} archive, or from one of their mirrors. \Qref[Question]{}{Q-archives} % this one doesn't need anchor text gives details of the \acro{CTAN} archives, and how to retrieve files from them. If you don't have access to the Internet, the -\Qref*{\TeX{}~Live distribution}{Q-CD} offers off-line snapshots of +\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 @@ -91,18 +91,18 @@ was maintained for some time by Bobby Bodenheimer. The first \acro{UK} version was much re-arranged and corrected from the original, and little of Bodenheimer's work now remains. -Most members of the committee of \acro{UK}~\acro{TUG}, over the years -since 1994, have contributed to this \acro{FAQ} to some extent. The -following people, who have never been members of the committee, have -also contributed help or advice: +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, +Rosemary Bailey, % lots of initial set of maths answers Barbara Beeton, % one of first reviewers outside cttee Karl Berry, Giuseppe Bilotta, Charles Cameron, Damian Cugley, Michael Dewey, -Michael Downes, % (RIP) on (ams)maths stuff +Michael Downes, % (RIP) on (ams\)maths stuff Jean-Pierre Drucbert, % corrected my interpretation of minitoc Thomas Esser, Ulrike Fischer, % spotted boondoggle in q-tabcellalign @@ -111,26 +111,31 @@ Anthony Goreham, Norman Gray, Eitan Gurari, % comparative html translators William Hammond, % lots of work on xml-related answers +John Hammond, % corrections to q-protect +Troy Henderson, % metapost tutorials update Hartmut Henkel, John Hobby, Morten H\textoslash gholm, % eagle eyes in search for problems Berthold Horn, % lots of stuff on fonts Ian Hutchinson, % comparative html translators Werner Icking, % (RIP) answer on tex-music +Alan Jeffrey, % another founding father Regnor Jernsletten, David Kastrup, % inter alia, suggested mention of lilypond Oleg Katsitadze, % revision of q-eplain Isaac Khabaza, % kindersley book Ulrich Klauer, % pointed out twaddle in TeXpronounce Markus Kohm, % help with functionality of Koma-script +Ryszard Kubiak, % comment about q-driver Simon Law, Daniel Luecking, +Aditya Mahajan, % rewrite of q-context Sanjoy Mahajan, Andreas Matthias, Brooks Moses, % editorial suggestion Iain Murray, % alternative solution in q-hyperdupdest -Vilar Camara Neto, % correct misunderstanding about breakurl pkg -%Dick Nickalls, % now a member of the committee +Vilar Camara Neto, % explain breakurl pkg, suggest use of numprint +Dick Nickalls, % now a member of the committee Ted Nieland, Hans Nordhaug, Pat Rau, @@ -139,12 +144,15 @@ Piet van Oostrum, Scott Pakin, Oren Patashnik, Steve Peter, % comprehensive review, lots of typos etc +Sebastian Rahtz, % without whom there would be no... Philip Ratcliffe, % help with a bibtex oddity +Chris Rowley, % founding father Jos\'e Carlos Santos, % very assiduous reader of new versions Walter Schmidt, Hans-Peter Schr\"ocker, Joachim Schrod, Maarten Sneep, % summary of c.t.t thread for outszwrng, inter alia +Axel Sommerfeldt, % suggested rewrite of q-hyperdupdest James Szinger, % who responded on c.t.t to request for answer Ulrik Vieth, Mike Vulis, @@ -233,7 +241,7 @@ Knuth (and others) have designed a fair range of fonts using \MF{}, but font design using \MF{} is much more of a minority skill than is \TeX{} macro-writing. The complete \TeX{}-user nevertheless needs to be aware of \MF{}, and to be able to run \MF{} to generate personal -copies of new fonts. +copies of Meta-fonts that come her way. \Question[Q-MP]{What is \MP{}?} @@ -370,8 +378,8 @@ are delivered with most formats built with an \eTeX{} system (for those who don't want them, \eTeX{}'s extensions can be disabled, leaving a functionally standard \TeX{} system). -The extensions range from the simple (increasing the number of -available registers from 256 to 65536) through to extremely subtle +The extensions range from the seemingly simple (increasing the number +of available registers from 256 to 32768) through to extremely subtle programming support. \Qref*{\CONTeXT{}}{Q-context} has required \eTeX{} for its operation @@ -405,8 +413,7 @@ detail (for example, its support for % ! line break but its greatest impact to date has been in the area of \acro{PDF} output. -\PDFTeX{} started as a topic for -\latexhtml{H\`an \The{} Th\`anh's}{Han The Thanh's} Master's~thesis, +\PDFTeX{} started as a topic for H\`an \The{} Th\`anh's Master's~thesis, and seems first to have been published in \TUGboat{} 18(4), in 1997 (though it was certainly discussed at the \acro{TUG}'96 conference in Russia). @@ -419,6 +426,9 @@ awarded his Ph.D., day-to-day maintenance and development of \PDFTeX{} maintainers (which includes Th\`anh); the group has managed to maintain a stable platform for general use. +Development of \PDFTeX{} has (in essence) stopped: the brave new world +is to be \Qref*{\LuaTeX{}}{Q-luatex}. + \Question[Q-latex]{What is \LaTeX{}?} \LaTeX{} is a \TeX{} macro package, originally written by Leslie Lamport, that @@ -515,29 +525,61 @@ minor modifications (though some will require substantial work). Interpretation of any \AllTeX{} program involves some data-driven elements, and \LaTeX{} has a wider range of such elements than does Plain \TeX{}. As a result, the mapping from \LaTeX{} to Plain \TeX{} -is far less clear than that in the other direction. +is far less clear than that in the other direction~--- see a later +answer about +\begin{wideversion} + \Qref{translating to Plain \TeX{}}{Q-LaTeXtoPlain}. +\end{wideversion} +\begin{narrowversion} + translating to Plain \TeX{} (\Qref{}{Q-LaTeXtoPlain}). +\end{narrowversion} \Question[Q-context]{What is \CONTeXT{}?} \href{http://www.pragma-ade.com/}{\CONTeXT{}} is a macro package -developed by Hans Hagen, originally to -serve the needs of his (Dutch) firm Pragma. It was designed with the -same general-purpose aims as \LaTeX{}, but (being younger) reflects -much more recent thinking about the structure of markup, etc. In -particular, \CONTeXT{} can customise its markup to an -author's language (customising modules for Dutch, English and German -are provided, at present). - -\CONTeXT{} is well integrated, in all of its structure, -with the needs of hypertext markup, and in particular with the -facilities offered by \Qref*{\PDFTeX{}}{Q-whatpdftex}. -The default installation employs a version of \PDFTeX{} built with the -\Qref*{\eTeX{} extensions}{Q-etex}, which allows further flexibility. +developed by Hans Hagen of Pragma-Ade. \CONTeXT{} is a +document-production system based, like \LaTeX{}, on the \TeX{} +typesetting system. Whereas \LaTeX{} insulates the writer from +typographical details, \CONTeXT{} takes a complementary approach by +providing structured interfaces for handling typography, including +extensive support for colors, backgrounds, hyperlinks, presentations, +figure-text integration, and conditional compilation. It gives the +user extensive control over formatting while making it easy to create +new layouts and styles without learning the \TeX{} macro +language. \CONTeXT{}'s unified design avoids the package clashes that +can happen with \LaTeX{}. + +\CONTeXT{} also integrates MetaFun, a superset of \MP{} and a powerful +system for vector graphics. MetaFun can be used as a stand-alone +system to produce figures, but its strength lies in enhancing +\CONTeXT{} documents with accurate graphic elements. + +\CONTeXT{} allows the users to specify formatting commands in English, +Dutch, German, French, or Italian, and to use different typesetting +engines (\PDFTeX{}, Xe\TeX{}, Aleph, and soon \LuaTeX{}) without +changing the user interface. \CONTeXT{} is developed rapidly, often in +response to requests from the user community. + +%%% RF's original version +%% developed by Hans Hagen, originally to +%% serve the needs of his (Dutch) firm Pragma. It was designed with the +%% same general-purpose aims as \LaTeX{}, but (being younger) reflects +%% much more recent thinking about the structure of markup, etc. In +%% particular, \CONTeXT{} can customise its markup to an +%% author's language (customising modules for Dutch, English and German +%% are provided, at present). +%% +%% \CONTeXT{} is well integrated, in all of its structure, +%% with the needs of hypertext markup, and in particular with the +%% facilities offered by \Qref*{\PDFTeX{}}{Q-whatpdftex}. +%% The default installation employs a version of \PDFTeX{} built with the +%% \Qref*{\eTeX{} extensions}{Q-etex}, which allows further flexibility. \CONTeXT{} doesn't yet have quite such a large developer community as does \LaTeX{}, but those developers who are active seem to have -prodigious energy. Some support is available via a % ! line break -\href{http://contextgarden.net/}{\acro{WIKI} site}. +prodigious energy. Support is available via a % ! line break +\href{http://contextgarden.net}{\acro{WIKI} site} and via the +\href{http://www.ntg.nl/mailman/listinfo/ntg-context}{mailing list}. \begin{ctanrefs} \item[\nothtml{\rmfamily}\CONTeXT{} distribution]\CTANref{context} \end{ctanrefs} @@ -647,7 +689,7 @@ it: The manual goes on to talk of ambitions to ``capture some of the \LaTeX{} market share''; it's a very witty package, but little sign of \htmlignore -it taking over from \LaTeX{} is detectable\dots\@ +it taking over from \LaTeX{} is detectable\dots{}\@ \endhtmlignore \begin{htmlversion} it taking over from \LaTeX{} is detectable\dots{} @@ -664,8 +706,8 @@ both on-line information and printed output. So instead of writing two different documents, one for the on-line help and the other for a typeset manual, you need write only one document source file. When the work is revised, you need only revise one document. By -convention, Texinfo source file names end with a \texttt{.texi} or -\texttt{.texinfo} extension. +convention, Texinfo source file names end with a \extension{texi} or +\extension{texinfo} extension. Texinfo is a macro language, somewhat similar to \LaTeX{}, but with slightly less expressive power. Its appearance is of course rather @@ -736,10 +778,14 @@ 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} - Omega/Aleph and \ExTeX{} projects (questions + \LuaTeX{}, Omega/Aleph and \ExTeX{} projects (questions \end{narrowversion} -\Qref[\nothtml]{Omega/Aleph}{Q-omegaleph} -\Qref[and]{\ExTeX{}}{Q-extex}\narrowonly{)}. +\Qref[\nothtml]{\LuaTeX}{Q-luatex}, +\Qref[\nothtml]{Omega/Aleph}{Q-omegaleph} and +\Qref[\nothtml]{\ExTeX{}}{Q-extex}\narrowonly{).} +\begin{wideversion} + projects. +\end{wideversion} \Question[Q-readtex]{Reading \AllTeX{} files} @@ -778,12 +824,10 @@ rivals the best commercial word processors in its responsiveness, what you type is usually \emph{markup}, which typically defines a logical (rather than a visual) view of what you want typeset. -However, in this context markup proves to be a blessing in disguise: a -good proportion of most \TeX{} documents is immediately readable in an -ordinary text editor. So, while you need to install a considerable -system to attain the full benefits of the \TeX{} document that you -were sent, the chances are you can understand quite a bit of it with -nothing more than the ordinary tools you already have on your computer. +So there's a balance between the simplicity of the original +(marked-up) document, which can more-or-less be read in \emph{any} +editor, and the really rather large investment needed to install a +system to read a document ``as intended''. \Question[Q-notWYSIWYG]{Why is \TeX{} not a \WYSIWYG{} system?} @@ -859,7 +903,8 @@ with articles about \TeX{}, \MF{} and related technologies, and about document design, processing and production. \acro{TUG} holds a yearly conference, whose proceedings are published in \textsl{TUGboat}. -\acro{TUG}'s web site is a valuable resource for all sorts of +\acro{TUG}'s \href{http://www.tug.org}{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 \textsl{TUGboat} are slowly (subject to copyright issues, etc.\@) @@ -982,11 +1027,12 @@ For \LaTeX{}, see: edition, Addison-Wesley, 2004, \ISBN{0-321-17385-6}) \item[The \LaTeX{} Companion]by Frank Mittelbach, Michel Goossens, Johannes Braams, David Carlisle and Chris Rowley (second edition, - Addison-Wesley, 2004, \ISBN{0-201-36299-6}) + Addison-Wesley, 2004, \ISBN*{0-201-36299-6}{978-0-201-36299-2}) \item[The \LaTeX{} Graphics Companion:]% \emph{Illustrating documents with \TeX{} and \PS{}} by Michel - Goossens, Sebastian Rahtz and Frank Mittelbach (Addison-Wesley, - 1997, \ISBN{0-201-85469-4}) + Goossens, Sebastian Rahtz, Frank Mittelbach, Denis Roegel and + Herbert Vo\ss{} (second edition, Addison-Wesley, 2007, + \ISBN*{0-321-50892-0}{978-0-321-50892-8}) \item[The \LaTeX{} Web Companion:]% \emph{Integrating \TeX{}, \acro{HTML} and \acro{XML}} by Michel Goossens and Sebastian Rahtz (Addison-Wesley, 1999, \ISBN{0-201-43311-7}) @@ -1190,20 +1236,18 @@ can find, you've looked in any \Qref*{books}{Q-books} you have, and scanned relevant \Qref*{tutorials}{Q-tutorials*}\dots{} and still you don't know what to do. - If you are seeking a particular package or program, look on your own +If you are seeking a particular package or program, look on your own system first: you might already have it~--- the better \TeX{} distributions contain a wide range of supporting material. The \acro{CTAN} Catalogue can also help: you can \href{http://www.tex.ac.uk/search}{search it}, or you can browse it -\begin{htmlversion} +% !!!! line break ``\href{http://www.tex.ac.uk/tex-archive/help/Catalogue/bytopic.html}{by topic}''. -\end{htmlversion} -\htmlignore -``by topic'' (see -\URL{http://www.tex.ac.uk/tex-archive/help/Catalogue/bytopic.html}). -\endhtmlignore -A catalogue entry has a description of the package, and links to any -documentation known on the net. \dots{} when the entry is up-to-date. +A catalogue entry has a brief description of the package, and links to +any known documentation on the net. In fact, a large proportion of +\acro{CTAN} package directoris now include documentation, so it's +often worth looking at the catalogue entry for a package you're considering +using. Failing all that, look to see if anyone else has had the problem before; there are two places where people ask: browse or search the @@ -1221,6 +1265,12 @@ To ask a question on \texttt{texhax}, you may simply send mail to list (via \URL{http://tug.org/mailman/listinfo/texhax}) % ! no ~ on this line first~--- not everyone will answer to you as well as to the list. +Do \textbf{not} try mailing the % ! line break +\Qref*{\LaTeX{} project team}{Q-LaTeX3} or the maintainers of these +\acro{FAQ}s for help; while both addresses reach experienced \AllTeX{} +users, no small group can possibly have expertise in every area of +usage so that the ``big'' lists are a far better bet. + \Question[Q-maillists*]{Specialist mailing lists} The previous question, ``\Qref*{getting help}{Q-gethelp}'', talked of @@ -1241,9 +1291,9 @@ subscribe metafont \end{quote} to \mailto{sympa@ens.fr} -Note that there's also a \MP{}-specific mailing list available via the +(Note that there's also a \MP{}-specific mailing list available via the \acro{TUG} lists; in fact there's little danger of becoming confused -by subscribing to both. +by subscribing to both.) Announcements of \TeX{}-related installations on the \acro{CTAN} archives are sent to the mailing list \texttt{ctan-ann}. Subscribe @@ -1327,15 +1377,17 @@ problem to a succinct demonstration of your problem. There are two valid approaches to this task: building up, and hacking down. -The ``building up'' process starts with a basic document structure +% ! line break +\latexhtml{The ``building up'' process}{\textbf{\emph{Building up}}} starts +with a basic document structure (for \LaTeX{}, this would have \csx{documentclass}, \cmdinvoke{begin}{document}, \cmdinvoke{end}{document}) and adds things. First to add is a paragraph or so around the actual point where the problem occurrs. (It may prove difficult to find the actual line that's provoking the problem. If the original problem is an error, reviewing % ! line break -\Qref[question]{the structure of \TeX{} errors}{Q-errstruct} may -help.) +\Qref[the answer to question]{``the structure of \TeX{} errors''}{Q-errstruct} +may help.) Note that there are things that can go wrong in one part of the document as a result of something in another part: the commonest is @@ -1346,13 +1398,16 @@ or whatever), or the list of \meta{something} (from something in a \environment{table} environment around it, but it \emph{doesn't} need the figure or table itself). -If this file you've built up collapses already, then you're done. +If this file you've built up shows the problem already, then you're done. Otherwise, try adding packages; the optimum is a file with only one -package in it, but you may find that the guilty package only works at -all with another package loaded (or only fails in the context of -another package). +package in it, but you may find that the guilty package won't even load +properly unless another package has been loaded. (Another common case +is that package \Package{A} only fails when package \Package{B} has been +loaded.) -The ``hacking down'' route starts with your entire document, and +% ! line break +\latexhtml{The ``hacking down'' route}{\textbf{\emph{Hacking down}}} starts +with your entire document, and removes bits until the file no longer fails (and then of course restores the last thing removed). Don't forget to hack out any unnecessary packages, but mostly, the difficulty is choosing what to @@ -1391,8 +1446,8 @@ All things considered, a good example file can save you a day, for perhaps half an hour's effort invested. The above advice, differently phrased, may also be read on the web at -\URL{http://www.latex-einfuehrung.de/mini-en.html}; source of that -article may be found at \URL{http://www.latex-einfuehrung.de/}, in +\URL{http://www.minimalbeispiel.de/mini-en.html}; source of that +article may be found at \URL{http://www.minimalbeispiel.de/}, in both German and English. \Question[Q-tutorials*]{\AllTeX{} Tutorials, etc.} @@ -1450,6 +1505,10 @@ Harvey Greenberg's `Simplified Introduction to \LaTeX{}' was written for a lecture course, and is also available on \acro{CTAN} (in \PS{} only, unfortunately). +The fourth edition of George Gr\"atzer's book ``Math into \LaTeX{}'' +contains a ``short course'' in \LaTeX{} itself, and that course has +been made publicly available on \acro{CTAN}. + Edith Hodgen's % beware line break \href{http://www.mcs.vuw.ac.nz/~david/latex/notes.pdf}{\LaTeX{}, a Braindump} starts you from the ground up~--- giving a basic tutorial in the use @@ -1471,13 +1530,12 @@ presents basic \LaTeX{} with useful hints for extensions Nicola Talbot's % ! line break \href{http://theoval.cmp.uea.ac.uk/~nlct/latex/novices/novices.html}{\LaTeX{} for complete novices} does what it claims: the author teaches \LaTeX{} at the University of -East Anglia. - -Nicola Talbot also provides a set of % ! line break +East Anglia. That is one of several of Nicola's % ! line break \href{http://theoval.cmp.uea.ac.uk/~nlct/latex/}{introductory tutorials}, -which include exercises (with solutions). The page was developed as -an extension to the \LaTeX{} course Nicola teaches at the University -of East Anglia. +which include exercises (with solutions). Other tutorials include +those for writing theses/dissertations with \LaTeX{}, and for using +\LaTeX{} in administrative work. (The page seems to be an adjunct to +her \LaTeX{} courses~--- fortunate people, the people of \acro{UEA}!). An interesting (and practical) tutorial about what \emph{not} to do is \Package{l2tabu}, or ``A list of sins of \LaTeXe{} users'' by Mark @@ -1490,6 +1548,7 @@ the source is also available). (in English, you may browse for sources and other language versions at \CTANref{lshort-parent}) \item[\nothtml{\rmfamily}Simplified \LaTeX{}]\CTANref{simpl-latex} +\item[\nothtml{\rmfamily}Short Course in \LaTeX{}]\CTANref{mil-short} % ! line break \item[\nothtml{\rmfamily}The sins of \LaTeX{} users]\CTANref{l2tabuen}; source also available: \CTANref{l2tabuen.src} @@ -1687,9 +1746,8 @@ the web, and until relatively recently this demand went un-answered. The first to appear was Victor Eijkhout's excellent ``\TeX{} by Topic'' in 2001 (it had been published by Addison-Wesley, but was long -out of print). The book is currently available at -\URL{http://www.eijkhout.net/tbt/}; it's not a beginner's tutorial but -it's a fine reference. +out of print). The book is now available on \acro{CTAN}; it's not a +beginner's tutorial but it's a fine reference. Addison-Wesley have also released the copyright of ``\TeX{} for the Impatient'' by Paul W.~Abrahams, Karl Berry and Kathryn A.~Hargreaves, @@ -1706,6 +1764,7 @@ and is a welcome addition to the list of on-line resources. A project to update it is believed to be under way. \begin{ctanrefs} \item[\nothtml{\rmfamily}Making \TeX{} Work]\CTANref{mtw} +\item[\nothtml{\rmfamily}\TeX{} by Topic]\CTANref{texbytopic} \item[\nothtml{\rmfamily}\TeX{} for the Impatient]\CTANref{TftI} \end{ctanrefs} @@ -1719,22 +1778,24 @@ is the poor user to find out what to do? If you're lucky, the package you need is already in your installation. If you're particularly lucky, you're using a distribution that gives access to package documentation and the documentation is available in -a form that can easily be shown. For example, on a te\TeX{}-based -system, the \ProgName{texdoc} command is usually useful, as in: +a form that can easily be shown. For example, on many current +distributions, the \ProgName{texdoc} command often helps, as in: \begin{quote} \begin{verbatim} texdoc footmisc \end{verbatim} \end{quote} -which opens an \ProgName{xdvi} window showing documentation of the +which opens a \acro{DVI} viewer window showing documentation of the \Package{footmisc} package. According to the type of file -\ProgName{texdoc} finds, it will launch \ProgName{xdvi}, -a \ProgName{ghostscript}-based \PS{} viewer or a \acro{PDF} reader. -If it can't find any documentation, it may launch a Web browser to -look at its copy of the \acro{CTAN} catalogue. The catalogue has an -entry for package documentation, and since \acro{CTAN} now -encourages authors to submit documentation of their packages, that -entry may provide a useful lead. +\ProgName{texdoc} finds, it will launch a \acro{DVI} or \PS{} viewer +or a \acro{PDF} reader. + +If \ProgName{texdoc} can't find any documentation, it may launch a Web +browser to look at its copy of the \acro{CTAN} catalogue. The +catalogue has an entry for package documentation, and since the +\acro{CTAN} team asks authors documentation of their packages (and +even occasionally generates documentation itself, you will more often +than not find documentation that way. If your luck (as defined above) doesn't hold out, you've got to find documentation by other means. This is where you need to exercise your @@ -1742,22 +1803,22 @@ intelligence: you have to find the documentation for yourself. What follows offers a range of possible techniques. The commonest form of documentation of \LaTeX{} add-ons is within the -\texttt{.dtx} file in which the code is distributed (see +\extension{dtx} file in which the code is distributed (see \Qref[answer]{documented \LaTeX{} sources}{Q-dtx}). Such files are supposedly processable by \LaTeX{} itself, but there are occasional hiccups on the way to readable documentation. Common problems are that the package itself is needed to process its own documentation (so must be unpacked before processing), and that the -\texttt{.dtx} file will \emph{not} in fact process with \LaTeX{}. In the -latter case, the \texttt{.ins} file will usually produce a \texttt{.drv} (or -similarly-named) file, which you process with \LaTeX{} instead. -(Sometimes the package author even thinks to mention this wrinkle in -a package \texttt{README} file.) +\extension{dtx} file will \emph{not} in fact process with \LaTeX{}. In the +latter case, the \extension{ins} file will usually produce a +\extension{drv} (or similarly-named) file, which you process with +\LaTeX{} instead. (Sometimes the package author even thinks to +mention this wrinkle in a package \texttt{README} file.) Another common form is the separate documentation file; particularly if a package is ``conceptually large'' (and therefore needs a lot of documentation), the documentation would prove a cumbersome extension -to the \texttt{.dtx} file. Examples of such cases are the \Class{memoir} +to the \extension{dtx} file. Examples of such cases are the \Class{memoir} class (whose documentation, \File{memman}, is widely praised as an introduction to typesetting concepts), the \Class{KOMA-script} bundle (whose developers take the trouble to produce detailed documentation @@ -1803,7 +1864,7 @@ source as a matter of course). A complete set of the documented source of \LaTeX{} may be prepared by processing the file \File{source2e.tex} in the \LaTeX{} distribution, but individual files in the distribution may be processed separately with \LaTeX{}, like -any well-constructed \Qref*{\texttt{.dtx} file}{Q-dtx}. +any well-constructed \Qref*{\extension{dtx} file}{Q-dtx}. Writing good classes is not easy; it's a good idea to read some established ones (\File{classes.dtx}, for example, is the documented @@ -1813,13 +1874,14 @@ distribution are commonly based on ones that are, and start by loading the standard class with \csx{LoadClass}~--- an example of this technique may be seen in \Package{ltxguide.cls} -An % !!! line break -\href{http://www.tug.org/pracjourn/2006-4/flynn/flynn.pdf}{annotated version of \Class{article}}, -as it appears in \File{classes.dtx}, was published in the Prac\TeX{} -Journal 2006, No.\,4. The article is by Peter Flynn, and offers a -slightly easier way in to understanding \File{classes.dtx} +An % !! line break +\href{http://tug.org/TUGboat/Articles/tb28-1/tb88flynn.pdf}{annotated version of \Class{article}}, +as it appears in \File{classes.dtx}, was published in +\TUGboat{} 28(1). The article, by Peter Flynn, which is some help in +understanding \File{classes.dtx} \begin{ctanrefs} \item[classes.dtx]\CTANref{latex-classes} +\item[clsguide.pdf]\CTANref{clsguide} \item[ltxguide.cls]\CTANref{ltxguide} \item[\nothtml{\rmfamily}\LaTeX{} documentation]\CTANref{latexdoc} \item[source2e.tex]\CTANref{latex-source} @@ -1844,22 +1906,22 @@ section describes how to use \MP{} illustrations in \LaTeX{} and \PDFLaTeX{} documents, with an emphasis on how to use appropriate fonts for any text or mathematics. -Hans Hagen (of \CONTeXT{} fame) offers a \MP{} tutorial called -MetaFun (which admittedly concentrates on the use of \MP{} within -\CONTeXT{}). It may be found on his company's % ! line break -\href{http://www.pragma-ade.com/metapost.htm}{\MP{} page}. +% Hans Hagen (of \CONTeXT{} fame) offers a \MP{} tutorial called +% MetaFun (which admittedly concentrates on the use of \MP{} within +% \CONTeXT{}). It may be found on his company's % ! line break +% \href{http://www.pragma-ade.com/metapost.htm}{\MP{} page}. Other \MP{} tutorials that have appeared are two in English by % ! line breaks \href{http://remote.science.uva.nl/~heck/Courses/mptut.pdf}{Andr\'e Heck} and \href{http://www.tlhiv.org/MetaPost/tutorial/}{Urs Oswald}, and one in French (listed here because it's clearly enough written -that this author understands it), by +that even this author understands it), by \href{http://pauillac.inria.fr/~cheno/metapost/metapost.pdf}{Laurent Ch\'eno}; both have been recommended for inclusion in the \acro{FAQ} -Urs Oswald's tutorial is accompanied by a super tool for testing -little bits of \MP{}, which is an invaluable aid to the learner: -\URL{http://www.tlhiv.org/cgi-bin/MetaPostPreviewer/index.cgi} +Urs Oswald's tutorial is accompanied by a super tool (by Troy +Henderson) for testing little bits of \MP{}, which is an invaluable +aid to the learner: \URL{http://www.tlhiv.org/mppreview} Vincent Zoonekynd's massive set of example \MP{} files is available on \acro{CTAN}; the set includes a \ProgName{Perl} script to convert the @@ -1880,28 +1942,31 @@ written more as a document, and presented in \acro{PDF}. \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 -(see \Qref[question]{TeX-related books}{Q-books}). +of Leslie Lamport's \LaTeX{} manual. The document ``\BibTeX{}ing'', contained in the file \File{btxdoc.tex}, expands on the chapter in Lamport's book. \emph{The \LaTeX{} Companion} -(see \Qref[question]{TeX-related books}{Q-books}) also -has information on \BibTeX{} and writing \BibTeX{} style files. +also has information on \BibTeX{} and writing \BibTeX{} style files. +(See \Qref[question]{TeX-related books}{Q-books} for details of both +books.) 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|, |abbrv|, |alpha|, |unsrt|). It -also contains their documentation. -The complete \BibTeX{} documentation set (including the files above) -is available on \acro{CTAN}. +\File{btxhak.tex}, explains the postfix stack-based language used to +write \BibTeX{} styles (\File{.bst} files). The file \File{btxbst.doc} +is the template for the four standard styles (\Package{plain}, +\Package{abbrv}, \Package{alpha}, and \Package{unsrt}). It also +contains their documentation. The complete \BibTeX{} documentation +set (including all the files above) is available on \acro{CTAN}. A useful tutorial of the whole process of using \BibTeX{} is Nicolas Markey's ``\emph{Tame the BeaST (The B to X of \BibTeX{})}'', which -may also be found on \acro{CTAN}. +may also be found on \acro{CTAN}. A summary and \acro{FAQ} +(\File{btxFAQ}), by Michael Shell and David Hoadley, is also to be +recommended. \begin{ctanrefs} \item[\nothtml{\rmfamily}\BibTeX{} documentation]\CTANref{bibtex-doc} \item[\nothtml{\rmfamily}\BibTeX{} documentation, in \acro{PDF}]% \CTANref{bibtex-doc-pdf} +\item[btxFAQ.pdf]\CTANref{bibtex-faq} \item[\nothtml{\rmfamily}Tame the BeaST]\CTANref{ttb-pdf} \end{ctanrefs} @@ -1940,8 +2005,13 @@ Unfortunately, \acro{TUG} is no longer able to supply copies of the manual (as it once did), and it is now available only through Personal \TeX{} Inc, the vendors of PC\TeX{} (\URL{http://www.pctex.com/}). The manual is \emph{not} available electronically. + +However, there \emph{is} a summary of \PiCTeX{} commands available on +\acro{CTAN}, which is a great aide-memoire for those who basically +know the package to start with. \begin{ctanrefs} \item[pictex]\CTANref{pictex} +\item[PiCTeX summary]\CTANref{pictex-summary} \end{ctanrefs} %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% @@ -1950,12 +2020,12 @@ manual is \emph{not} available electronically. \Question[Q-dvi]{What is a \acro{DVI} file?} -A \acro{DVI} file (that is, a file with the type or extension |.dvi|) is -\TeX{}'s main output file, using \TeX{} in its broadest sense to -include \LaTeX{}, etc. `\acro{DVI}' is supposed to be an acronym for -\acro{D}e\acro{V}ice-\acro{I}ndependent, meaning that the file can be -printed on almost any -kind of typographic output device. The \acro{DVI} file is designed to be +A \acro{DVI} file (that is, a file with the type or extension +\extension{dvi}) is \TeX{}'s main output file, using \TeX{} in its +broadest sense to include \LaTeX{}, etc. `\acro{DVI}' is supposed to +be an acronym for \acro{D}e\acro{V}ice-\acro{I}ndependent, meaning +that the file can be printed on most +kinds of typographic output device. The \acro{DVI} file is designed to be read by a driver (\Qref{DVI drivers}{Q-driver}) to produce further output designed specifically for a particular printer (e.g., a LaserJet) or to be used as input to a previewer for display on a @@ -1969,55 +2039,56 @@ possibly material to be introduced by means of \Qref*{\csx{special} commands}{Q-specials}. The canonical reference for the structure of a \acro{DVI} file is the -source of \ProgName{dvitype}. +source of Knuth's program \ProgName{dvitype} (whose original purpose, +as its name implies, was to view the content of a \acro{DVI} file). \begin{ctanrefs} \item[dvitype]\CTANref{dvitype} \end{ctanrefs} -\Question[Q-driver]{What is a driver?} +\Question[Q-driver]{What is a \acro{DVI} driver?} -A driver is a program that takes as input a \acro{DVI} file +A \acro{DVI} driver is a program that takes as input a \acro{DVI} file (\Qref{\acro{DVI} files}{Q-dvi}) and (usually) produces a file that can be sent to a typographic -output device, called a printer for short. +output device (which we will call a printer, for short), or to another +format. A driver will usually be specific to a particular printer, although any \PS{} printer ought to be able to print the output from a \PS{} driver. % (these are also called \PS{} conversion programs). -As well as the \acro{DVI} file, the driver needs font information. +As well as the \acro{DVI} file, the driver also needs font information. Font information may be held as bitmaps or as outlines, or simply as a set of pointers into the fonts that the printer itself `has'. Each driver will expect the font information in a particular form. For more information on the forms of fonts, see \Qref[questions]{\acro{PK} files}{Q-pk}, -% beware of fill-paragraph here!!!! +% ! line break \Qref[]{\acro{TFM} files}{Q-tfm}, \Qref[]{virtual fonts}{Q-virtualfonts} and \Qref[]{Using \PS{} fonts with \TeX{}}{Q-usepsfont}. - \Question[Q-pk]{What are \acro{PK} files?} -\acro{PK} files (packed raster) contain font bitmaps. The output -from -\htmlignore -\MF{} (\Qref{}{Q-useMF}) -\endhtmlignore -\begin{htmlversion} - \Qref{\MF{}}{Q-useMF} -\end{htmlversion} -includes a generic font (\acro{GF}) file and the +\acro{PK} files (packed raster) contain font bitmaps. The output +from \Qref*{\MF{}}{Q-useMF} includes a generic font (\acro{GF}) file +and the utility \ProgName{gftopk} produces the \acro{PK} file from that. There are a lot of \acro{PK} files, as one is needed for each font, that is each magnification (size) of each design (point) size for each weight for each family. Further, since the \acro{PK} files for one printer do not necessarily work well for another, the whole set needs to be -duplicated for each printer type at a site. As a result, they are -often held in an elaborate directory structure, or in `font library -files', to regularise access. - +duplicated for each printer type at a site. In a modern \TeX{} +distribution, files are arranged according to the \TeX{} directory +structure +\begin{narrowversion} +(\acro{TDS}~--- \Qref{}{Q-tds}), +\end{narrowversion} +\begin{wideversion} +(see \Qref{\acro{TDS}}{Q-tds}), +\end{wideversion} +which has provision for all this variety. \Question[Q-tfm]{What are \acro{TFM} files?} @@ -2025,48 +2096,49 @@ files', to regularise access. information about the sizes of the characters of the font in question, and about ligatures and kerns within that font. One \acro{TFM} file is needed for each font used by \TeX{}, that is for each design (point) -size for each weight for each family; one \acro{TFM} file serves for all -magnifications, so that there are (typically) fewer \acro{TFM} files than -there are \acro{PK} files. The important point is that \acro{TFM} files are -used by \TeX{} (\LaTeX{}, etc.), but are not, generally, needed by the -printer driver. - +size for each weight for each family; each \acro{TFM} file serves for all +magnifications of `its' font, so that there are (typically) fewer +\acro{TFM} files than there are \acro{PK} files. \TeX{} (\LaTeX{}, etc.\@) +itself needs only to know about the sizes of characters and their +interactions with each other, but not what characters look like. By +contrast, \acro{TFM} files are not, in principle, needed by the +\acro{DVI} driver, which needs to know about the glyphs that each +character selects, so as to print or display them. \Question[Q-virtualfonts]{Virtual fonts} -Virtual fonts for \TeX{} were first implemented by David Fuchs in the -early days of \TeX{}, but for most people they date from when Knuth -redefined the format, and wrote some support software, in 1989 (he +Virtual fonts provide a means of collecting bits and pieces together +to make the glyphs of a font: the bits and pieces may be other glyphs, +rules and other ``basic'' typesetting commands, and the positioning +information that specifies how everything comes together. + +Things that match the concept of virtual fonts for \TeX{} were first +implemented by David Fuchs in the very early days. However, for practical +purposes for the rest of us, virtual fonts date from when Knuth +specified a format and wrote some support software, in 1989 (he published an article in \textsl{TUGboat} at the time, and a plain text copy is available on \acro{CTAN}). Virtual fonts provide a way of telling \TeX{} about something more complicated than just a one-to-one character mapping. The entities you define in a virtual font look like characters to \TeX{} (they appear -with their sizes in a font metric file), but the \acro{DVI} processor may +with their sizes in a \acro{TFM} file), but the \acro{DVI} processor may expand them to something quite different. -Specifically, \TeX{} itself only looks at a \acro{TFM} file that -contains details of how the virtual font will appear: but of course, -\TeX{} only cares about the metrics of a character, so its demands are -pretty small. The acro{DVI} processor, however, has to understand the +From the virtual font file, the \acro{DVI} processor learns details of what is in the virtual font, so as to know ``what to draw, -where''. So, for every virtual font read by a \acro{DVI} driver, -there has to be a \acro{TFM} file to be read by \TeX{}. -(\PDFTeX{}, of course, needs both the \acro{TFM} and the -translation of the virtual font, since it does the whole job in the -one program.) - -You can use a virtual font: +where''. The virtual font may contain commands: \begin{itemize} -\item simply just to remap the glyphs of a single font, +\item just to remap the glyphs of a single font, \item to make a composite font with glyphs drawn from several - different onts, or + different fonts, or \item to build up an effect in arbitrarily complicated ways (since a virtual font may contain anything which is legal in a \acro{DVI} file). \end{itemize} +% !this has to be generated as a new paragraph by the translator, so +% leave the blank line in place In practice, the most common use of virtual fonts is to remap Adobe Type 1 fonts (see \Qref[question]{font metrics}{Q-metrics}), though there has also been useful useful work building `fake' maths @@ -2074,7 +2146,8 @@ fonts (by bundling glyphs from several fonts into a single virtual font). Virtual Computer Modern fonts, making a % ! line break \Qref*{Cork encoded}{Q-ECfonts} font from Knuth's originals by using remapping and fragments of \acro{DVI} for single-glyph `accented -characters', were the first ``Type~1 format'' versions available. +characters', were the first ``Type~1 format'' Cork-encoded Computer +Modern fonts available. Virtual fonts are normally created in a single \acro{ASCII} \acro{VPL} (Virtual Property List) file, which includes both sets of @@ -2106,16 +2179,20 @@ itself knows nothing about how to include \PS{} figures into documents, or how to set the colour of printed text; but some device drivers do. -Such things are introduced to your document by means of \csx{special} -commands; all that \TeX{} does with these commands is to expand their +Instructions for such things are introduced to your document by means +of \csx{special} commands; all that \TeX{} does with these commands is +to expand their arguments and then pass the command to the \acro{DVI} file. In most cases, there are macro packages provided (often with the driver) that -provide a comprehensible interface to the \csx{special}; for example, +provide a human-friendly interface to the \csx{special}; for example, there's little point including a figure if you leave no gap for it in your text, and changing colour proves to be a particularly fraught -operation that requires real wizardry. \LaTeXe{} +operation that requires real wizardry. \LaTeXe{} has standard graphics and colour packages that make figure inclusion, -rotation and scaling, and colour typesetting via \csx{special}s all easy. +rotation and scaling, and colour typesetting relatively +straightforward, despite the rather daunting \csx{special} commands +involved. (\CONTeXT{} provides similar support, though not by way of +packages.) The allowable arguments of \csx{special} depend on the device driver you're using. Apart from the examples above, there are \csx{special} @@ -2124,11 +2201,16 @@ commands in the em\TeX{} drivers (e.g., \ProgName{dvihplj}, \ProgName{dviscr}, commands in \ProgName{dvitoln03} that permit the page to be set in landscape orientation. +Note that \csx{special} provides rather different facilities in \PDFTeX{} +operation: since there is no device driver around, in this context. +In \PDFTeX{}, \csx{special} is only needed to generated \acro{PDF} for +which there is no existing defined \PDFTeX{} operation. + \Question[Q-hyphen]{How does hyphenation work in \TeX{}?} Everyone knows what hyphenation is: we see it in most books we read, -and (if we're alert) often spot ridiculous mis-hyphenation from time -to time (at one time, British newspapers were a fertile source). +and (if we're alert) will spot occasional ridiculous mis-hyphenation +(at one time, British newspapers were a fertile source). Hyphenation styles are culturally-determined, and the same language may be hyphenated differently in different countries~--- for example, @@ -2162,6 +2244,9 @@ engine, overriding the effect of the patterns). The ordinary \LaTeX{} user need not worry about \csx{language}, since it is very thoroughly managed by the \Package{babel} package; use of \csx{hyphenation} is discussed in +\begin{wideversion} + the context of +\end{wideversion} % beware line wrap \Qref[question]{hyphenation failure}{Q-nohyph}. @@ -2197,49 +2282,49 @@ programming-interface versions of both commands, since a class may choose to load another class to refine its capabilities, and both classes and packages may choose to load other packages.) -\Question[Q-dtx]{Documented \LaTeX{} sources (\texttt{.dtx} files)} +\Question[Q-dtx]{Documented \LaTeX{} sources (\extension{dtx} files)} \LaTeXe{}, and most contributed macro packages, are now written in a \Qref*{literate programming style}{Q-lit}, with source and documentation in the same file. This format, known as `doc', in fact originated before the days of the \LaTeX{} project as one of the ``Mainz'' series of -packages. The documented sources conventionally have the suffix -\texttt{.dtx}, and should normally be stripped of documentation -before use with \LaTeX{}. Alternatively you can run \LaTeX{} on a -\texttt{.dtx} file to produce a nicely formatted version of the -documented code. An installation script (with suffix -\texttt{.ins}) is usually provided, which needs the standard \LaTeXe{} -\ProgName{docstrip} package (among other things, the installation -process strips all the comments that make up the documentation for -speed when loading the file into a running \LaTeX{} system). Several -packages can be included in one \texttt{.dtx} file, with conditional -sections, and there facilities for indices of macros etc. Anyone can -write \texttt{.dtx} files; the format is explained in -\Qref*{The \LaTeX{} Companion}{Q-books}, and a tutorial is -available from \acro{CTAN} (which comes with skeleton \texttt{.dtx} and -\texttt{.ins} files). - -Composition of \texttt{.dtx} files is supported in \ProgName{emacs} by +packages. A documented source file conventionally has the suffix +\extension{dtx}, and will normally be `stripped' before use with +\LaTeX{}; an installation file (\extension{ins}) is normally provided, +to automate this process of removing comments for speed of loading. +To read the comments, you can run \LaTeX{} on the +\extension{dtx} file to produce a nicely formatted version of the +documented code. Several +packages can be included in one \extension{dtx} file (they're sorted +out by the \extension{ins} file), with conditional +sections, and there are facilities for indexes of macros, etc. + +Anyone can write \extension{dtx} files; the format is explained in +\Qref*{The \LaTeX{} Companion}{Q-books}, and a tutorial is available +from \acro{CTAN} (which comes with skeleton \extension{dtx} and +\extension{ins} files). + +Composition of \extension{dtx} files is supported in \ProgName{emacs} by Matt Swift's \ProgName{swiftex} system: it provides a -\environment{doc-tex} mode which treats \texttt{.dtx} files rather +\environment{doc-tex} mode which treats \extension{dtx} files rather better than \Qref*{\acro{AUC}-\TeX{}}{Q-editors} manages. -Another useful way of generating \texttt{.dtx} files is to write the +Another useful way of generating \extension{dtx} files is to write the documentation and the code separately, and then to combine them using the \ProgName{makedtx} system. This technique has particular value in that the documentation file can be used separately to generate \acro{HTML} output; it is often quite difficult to make % ! line break \Qref*{\LaTeX{} to \acro{HTML} conversion}{Q-LaTeX2HTML} tools deal -with \texttt{.dtx} files, since they use an unusual class file. +with \extension{dtx} files, since they use an unusual class file. -\texttt{.dtx} files are not used by \LaTeX{} after they have been -processed to produce \texttt{.sty} or \texttt{.cls} (or whatever) +The \extension{dtx} files are not used by \LaTeX{} after they have been +processed to produce \extension{sty} or \extension{cls} (or whatever) files. They need not be kept with the working system; however, for -many packages the \texttt{.dtx} file is the primary source of -documentation, so you may want to keep \texttt{.dtx} files elsewhere. +many packages the \extension{dtx} file is the primary source of +documentation, so you may want to keep \extension{dtx} files elsewhere. -An interesting sideline to the story of \texttt{.dtx} files is the +An interesting sideline to the story of \extension{dtx} files is the \Package{docmfp} package, which extends the model of the \Package{doc} package to \latexhtml{\MF{}}{\Qref{\MF{}}{Q-MF}} and % beware line break \latexhtml{\MP{} (\Qref[see questions]{}{Q-MF} and\Qref[]{}{Q-MP})}{\Qref{\MP{}}{Q-MP}}, @@ -2316,7 +2401,7 @@ interrupted by the \csx{accent} commands~--- see \Qref[question]{``how does hyphenation work''}{Q-hyphen}). To take advantage of the diacriticised characters represented in the fonts, it is necessary to arrange that whenever the -command sequence ``|\'||e|'' has been input +command sequence ``\csx{'}\texttt{e}'' has been input (explicitly, or implicitly via the sort of mapping of input mentioned above), the character that codes the position of the ``\'e'' glyph is used. @@ -2359,10 +2444,8 @@ least. The Cork encoding does contain ``\acro{NG}'' glyphs that allows it to support Southern Sami.) \LaTeX{} refers to the Cork encoding as \acro{T}1, and provides the means to use fonts thus encoded to avoid problems with -the interaction of accents and hyphenation -% beware!!! fill-paragraph!!! +the interaction of accents and hyphenation % ! line break (see \Qref[question]{hyphenation of accented words}{Q-hyphenaccents}). -% beware!!! fill-paragraph!!! The only \MF{}-fonts that conform to the Cork encoding are the \acro{EC} fonts. They look \acro{CM}-like, though their metrics @@ -2401,13 +2484,8 @@ according to the \LaTeX{} \acro{TS}1 encoding, and are not viewed as `stable' in the same way as are the \acro{EC} fonts are. The Cork encoding is also implemented by virtual fonts provided in the -\htmlignore -\acro{PSNFSS} system (\Qref{}{Q-usepsfont}), -\endhtmlignore -\begin{htmlversion} - \Qref{\acro{PSNFSS} system}{Q-usepsfont}, -\end{htmlversion} -for \PS{} fonts, and also by the \Package{txfonts} and +\Qref*{\acro{PSNFSS} system}{Q-usepsfont}, +for Adobe Type~1 fonts, and also by the \Package{txfonts} and \Package{pxfonts} font packages % beware line wrap (see \Qref[question]{``choice of scalable fonts''}{Q-psfchoice}). @@ -2455,10 +2533,11 @@ available on \acro{CTAN}. \Question[Q-eps]{What is ``Encapsulated \PS{}'' (``\acro{EPS}'')} -\PS{} has over the years become a \emph{lingua franca} of -powerful printers; since \PS{} is also a powerful graphical -programming language, it is commonly used as an output medium for -drawing (and other) packages. +\PS{} has been for many years a \emph{lingua franca} of powerful +printers (modern high-quality printers now tend to require some +constrained form of Adobe Acrobat, instead); since \PS{} is also a +powerful graphical programming language, it is commonly used as an +output medium for drawing (and other) packages. However, since \PS{} \emph{is} such a powerful language, some rules need to be imposed, so that the output drawing may be included @@ -2493,9 +2572,11 @@ don't know the rules. \keywords{type1 type3} Adobe has specified a number of formats for files to represent fonts -in \PS{} files; this question doesn't attempt to be encyclopaedic, but -we'll discuss the two formats most commonly encountered in the -\AllTeX{} context, types~1 and 3. +in \PS{} files; this question doesn't attempt to be encyclopaedic, so +we only discuss the two formats most commonly encountered in the +\AllTeX{} context, types~1 and 3. In particular, we don't discuss the +OpenType format, whose has many advantages are somewhat ahead of the +\TeX{} world's mainstream (at time of writing). Adobe Type~1 format specifies a means to represent outlines of the glyphs in a font. The `language' used is closely restricted, to ensure that @@ -2503,7 +2584,7 @@ the font is rendered as quickly as possible. (Or rather, as quickly as possible with Adobe's technology at the time the specification was written: the structure could well be different if it were specified now.) The format has long been the basis of the digital type-foundry -business, though things are showing signs of change. +business, though nowadays most new fonts are released in OpenType format. %% Type~1 fonts are directly supported by some operating system software, %% and at least one \TeX{} system, the commercial % line break! @@ -2514,10 +2595,10 @@ In the \AllTeX{} context, Type~1 fonts are extremely important. Apart from their simple availability (there are thousands of commercial Type~1 text fonts around), the commonest reader for \acro{PDF} files has long (in effect) \emph{insisted} on -their use (see \Qref[question]{\acro{PDF} quality}{Q-dvips-pdf}). +their use (see below). Type~3 fonts have a more forgiving specification. A wide range of -\PS{} operators is permissible, including bitmaps operators. Type~3 +\PS{} operators is permissible, including bitmap specifiers. Type~3 is therefore the natural format to be used for programs such as \ProgName{dvips} when they auto-generate something to represent \MF{}-generated fonts in a \PS{} file. It's Adobe Acrobat Viewer's @@ -2526,9 +2607,11 @@ inreasingly unattractive, in recent years. If you have a \acro{PDF} document in which the text looks fuzzy and uneven in Acrobat Reader, ask Reader for the \texttt{File}\arrowhyph{}% \texttt{Document Properties}\arrowhyph{}% -\texttt{Fonts ...}, and it will show some font or other as ``Type~3'' -(usually with encoding ``Custom''). (This problem has disappeared -with version 6 of Acrobat Reader.) +\texttt{Fonts ...}, and it will likely show some font or other as +``Type~3'' (usually with encoding ``Custom''). The problem has +disappeared with version 6 of Acrobat Reader. See % line break +\Qref[question]{\acro{PDF} quality}{Q-dvips-pdf} for a discussion of +the issue, and for ways of addressing it. Type~3 fonts should not entirely be dismissed, however. Acrobat Reader's failure with them is entirely derived from its failure to use @@ -2579,20 +2662,17 @@ Therefore, we need \acro{DVI} processors that will produce independence needs to extend to both forms of independence outlined above. -Resolution-independence of fonts is forced upon the world by the -feebleness of Adobe's \ProgName{Acrobat} \ProgName{Reader} at dealing -with bitmap files: a sequence of answers starting with one aiming at -the \Qref*{quality of \acro{PDF} from \PS{}}{Q-dvips-pdf} addresses +Resolution-independence of fonts was for a long time forced upon the +world by the feebleness of Adobe's \ProgName{Acrobat} +\ProgName{Reader} at dealing with bitmap files: a sequence of answers +starting with one aiming at the % ! line break +\Qref*{quality of \acro{PDF} from \PS{}}{Q-dvips-pdf} addresses the problems that arise. Resolution-independence of positioning is more troublesome: \ProgName{dvips} is somewhat notorious for insisting on positioning to the accuracy of the declared resolution of the printer. -%% ~--- the only -%% \PS{} driver the author \emph{knows} to be capable of doing the right -%% thing is \Qref*{\YandY{}'s \ProgName{DVIPSONE}}{Q-commercial}. -One -commonly-used approach is to declare a resolution of 8000 (``better +One commonly-used approach is to declare a resolution of 8000 (``better than any device''), and this is reasonably successful though it does have its \Qref*{problems}{Q-8000}. @@ -2619,7 +2699,7 @@ Thus arose the Berry naming scheme. The basis of the scheme is to encode the meanings of the various parts of the file's specification in an extremely terse way, so that enough -font names can be expressed even in impoverished file spaces. The +font names can be expressed even in impoverished file name-spaces. The encoding allocates one letter to the font ``foundry'', two to the typeface name, one to the weight, and so on. The whole scheme is outlined in the \Package{fontname} distribution, which includes @@ -2644,55 +2724,126 @@ in this \acro{FAQ} is archived at the \acro{CTAN} sites (see the lists of software at the end of each answer). -The \acro{CTAN} sites are currently \FTP{dante.ctan.org} (Germany), -\FTP{cam.ctan.org} (UK) and \FTP{tug.ctan.org} (USA). -The organisation of \TeX{} files on all -\acro{CTAN} sites is identical and starts at -\path{tex-archive/}. Each \acro{CTAN} node may also be accessed via +\begin{narrowversion} % non-hyper + The \acro{CTAN} sites are in Germany, the UK and the USA; the + directory layout is the same on each of the sites, starting from a + tree root of \path{tex-archive/} The sites are + \texttt{dante.ctan.org} (Dante, Germany), \texttt{cam.ctan.org} + (Cambridge, UK) and \texttt{tug.ctan.org} (TUG, USA). +\end{narrowversion} +\begin{wideversion} % hyper + The \acro{CTAN} sites are + \href{ftp://dante.ctan.org/tex-archive}{Dante (Germany)}, + \href{ftp://cam.ctan.org/tex-archive}{Cambridge (UK)} and + \href{ftp://tug.ctan.org/tex-archive}{TUG (USA)}; the links are to + the root of the \acro{CTAN} tree, above which the layout is + identical at each site. +\end{wideversion} + +The \TeX{} files at each \acro{CTAN} node may also be accessed via the Web at \acro{URL}s \URL{http://www.dante.de/tex-archive}, \URL{http://www.tex.ac.uk/tex-archive} and \URL{http://www.ctan.org/tex-archive} respectively, but not all \acro{CTAN} mirrors are Web-accessible. + As a matter of course, to reduce network load, please use the \acro{CTAN} site or mirror closest to you. A complete and current list of \acro{CTAN} sites and known mirrors is available as file \CTANref{CTAN-sites} on the archives themselves. +Better still, the script behind \URL{http://mirror.ctan.org/} will +cunningly choose a ``nearby'' mirror for you, using information from +the database `behind' \CTANref{CTAN-sites}; at present it uses +\texttt{ftp} protocol for transfers, but the intention is to convert +it to using \texttt{http} (web) protocol in the near future. + +To access a particular thing through the \texttt{mirror.ctan.org} +mechanism, simply place the \acro{CTAN} path after the base +\acro{URL}; so +\URL{http://mirror.ctan.org/macros/latex/contrib/footmisc/} will +connect you to the \Package{footmisc} directory~--- note that the +\File{tex-archive} part of the \acro{CTAN} path isn't needed. + For details of how to find files at \acro{CTAN} sites, see ``\Qref*{finding \AllTeX{} files}{Q-findfiles}''. The \TeX{} user who has no access to any sort of network may buy a copy of the archive as part of the -\Qref*{\TeX{}~Live distribution}{Q-CD}. +\Qref*{\texlive{} distribution}{Q-CD}. \Question[Q-nonfree]{What's the \acro{CTAN} \texttt{nonfree} tree?} -The \acro{CTAN} archives are currently restructuring their holdings -so that files that are `not free' are held in a separate tree. The -definition of what is `free' (for this purpose) is influenced by, but -not exactly the same as the -\begin{narrowversion} % really non-hyper version - Debian Free Software Guidelines (\acro{DFSG}: see - \URL{http://www.debian.org/social_contract#guidelines}). -\end{narrowversion} -\begin{wideversion} -% don't let the line wrap... -\href{http://www.debian.org/social_contract#guidelines}{Debian Free Software Guidelines (\acro{DFSG})}. -\end{wideversion} - -Material is placed on the \texttt{nonfree} tree if it is not -freely-usable (e.g., if the material is shareware, commercial, or if -its usage is not permitted in certain domains at all, or without -payment). Users of the archive should check that they are entitled to -use material they have retrieved from the \texttt{nonfree} tree. - -The Catalogue (one of the prime sources for finding \TeX{}-related -material via \nothtml{web search~--- }% -\Qref{web search}{Q-findfiles}) lists the licence details in each -entry in its lists. -For details of the licence categories, see its % !line break -\href{http://www.tex.ac.uk/tex-archive/help/Catalogue/licenses.html}{list of licences}. +When \acro{CTAN} was founded, in the 1990s, it was unusual to publish +the terms under which a \TeX{}-related package was distributed (or, at +any rate, to publish those terms formally). + +With the advent of the \TeX{} \emph{distributions}, however, people +started to realise the need for such information, to protect those who +create, distribute or sell the discs that hold the packages, etc. +With the licence information available, the distributors can decide +which packages may be distributed. + +The \acro{CTAN} team decided that it would be useful for users (and +distributors, not to say package authors) to separate packages that +were candidates for distribution, and those that were in some sense +``not free''. Thus was the \texttt{nonfree} tree born. + +From the start, the \texttt{nonfree} tree was controversial: the terms +under which a package would be placed on the tree were hotly +contested, and the \acro{CTAN} team were only able slowly to populate +the tree. It is now obvious to the team that the project would never +be completed. + +The \acro{CTAN} catalogue now records the nature of the licences of a +good proportion of the packages it describes (though there remain +several for which the licence is unknown, which is as good, for the +distributors, as a licence forbidding distribution). Since the +catalogue's coverage of \acro{CTAN} is good (and slowly improving), +the general rule for distributors has become +\begin{quote} +``if the package is listed in the catalogue, check there to see +whether you should distribute; if the package is not listed in the +catalogue, don't think of distributing it''. +\end{quote} + +(The catalogue only has a modest % ! line break +\CTANhref{cat-licences}{list of licences}, but it covers the set used +by packages on \acro{CTAN}, with a wild-card ``\texttt{other-free}'' +which covers packages that the \acro{CTAN} administrators believe to +be free even though the authors haven't used a standard licence.) + +In the light of the above, the \texttt{nonfree} tree is being +dismantled, and its contents moved to the main \acro{CTAN} tree. So +the answer to the question is, now, ``the nonfree tree is a part of +\acro{CTAN}, and is now being merged with the main tree''. + + +% The \acro{CTAN} archives are currently restructuring their holdings +% so that files that are `not free' are held in a separate tree. The +% definition of what is `free' (for this purpose) is influenced by, but +% not exactly the same as the +% \begin{narrowversion} % really non-hyper version +% Debian Free Software Guidelines (\acro{DFSG}: see +% \URL{http://www.debian.org/social_contract#guidelines}). +% \end{narrowversion} +% \begin{wideversion} +% % don't let the line wrap... +% \href{http://www.debian.org/social_contract#guidelines}{Debian Free Software Guidelines (\acro{DFSG})}. +% \end{wideversion} + +% Material is placed on the \texttt{nonfree} tree if it is not +% freely-usable (e.g., if the material is shareware, commercial, or if +% its usage is not permitted in certain domains at all, or without +% payment). Users of the archive should check that they are entitled to +% use material they have retrieved from the \texttt{nonfree} tree. + +% The Catalogue (one of the prime sources for finding \TeX{}-related +% material via \nothtml{web search~--- }% +% \Qref{web search}{Q-findfiles}) lists the licence details in each +% entry in its lists. +% For details of the licence categories, see its % !line break +% \href{http://www.tex.ac.uk/tex-archive/help/Catalogue/licenses.html}{list of licences}. \Question[Q-uploads]{Contributing a file to the archives} @@ -2705,9 +2856,9 @@ start, here's a check-list of things to sort out: \href{http://www.tex.ac.uk/tex-archive/help/Catalogue/licenses.html}{list of ``standard'' licence statements}. \item Documentation: it's good for users to be able to browse documentation before downloading a package. You need at least a - plain text \File{README} file (exactly that name); best is a + plain text \File{README} file (exactly that name); in addition a \acro{PDF} file of the package documentation, prepared for screen - reading. + reading, is highly desirable. \item Name: endless confusion is caused by name clashes. If your package has the same name as one already on \acro{CTAN}, or if your package installation generates files of the same name as something @@ -2724,33 +2875,41 @@ start, here's a check-list of things to sort out: aren't suitable. \end{enumerate} -If you are able to use anonymous \ProgName{ftp}, get yourself a copy of -the file \File{README.uploads} from any -\Qref*{\acro{CTAN} archive}{Q-archives}. The file tells you +If you are able to use anonymous \ProgName{ftp}, you can upload that +way. The file \File{README.uploads} on \acro{CTAN} tells you where to upload, what to upload, and how to notify the \acro{CTAN} management about what you want doing with your upload. -You may also upload via the Web: each of the principle \acro{CTAN} +You may also upload via the Web: each of the principal \acro{CTAN} sites offers an upload page~--- choose from \URL{http://www.ctan.org/upload.html}, \URL{http://www.dante.de/CTAN/upload.html} or \URL{http://www.tex.ac.uk/upload.html}; the pages lead you through the -process, showing you the information you need to supply. - -If you can use neither of these methods, ask advice of the +process, showing you the information you need to supply. This method +enforces one file per upload: if you had intended to upload lots of +files, you need to bundle them into an `archive' file of some sort; +acceptable formats are \extension{zip} and \extension{tar.gz} (or +\extension{tar.bz2}). + +If you can use neither of these methods, or if you find something +confusing, ask advice of the \begin{narrowversion} % really non-hyper version \acro{CTAN} management (\mailto{ctan@dante.de}): \end{narrowversion} \begin{wideversion} \href{mailto:ctan@dante.de}{\acro{CTAN} management}: \end{wideversion} -if the worst comes to the worst, it may be possible to mail a contribution. +if the worst comes to the worst, it may be possible to mail a +contribution. This really is a last-resort route: none of the +\acro{CTAN} sites is anyone's regular workstation, so if you mail to +one of the maintainers, that maintainer then has to upload to +\acro{CTAN}. If it's appropriate (if your package is large, or regularly updated), the \acro{CTAN} management can arrange to \ProgName{mirror} your contribution direct into the archive. At present this may only be -done if your contribution is available via |ftp|, and of course the -directory structure on your archive must `fit'. +done if your contribution is available via \ProgName{ftp}, and of +course the directory structure on your repository must `fit'. \begin{ctanrefs} \item[README.uploads]\CTANref{CTAN-uploads} \end{ctanrefs} @@ -2824,57 +2983,83 @@ updated only once a day, a nightly automatic download (perhaps using A comprehensive list of \MF{} fonts used to be posted to \Newsgroup{comp.fonts} and to \Newsgroup{comp.text.tex}, roughly -every six weeks, by Lee Quin. % (\Email|lee@sq.sq.com|) - -%The list contains details both of commercial fonts and of fonts -%available via anonymous |ftp|. Most of the fonts are available via -%anonymous |ftp| from the \acro{CTAN} archives -%(see \Qref[question]{sources of software}{Q-archives}). - +every six weeks, by Lee Quin. Nowadays, authors of new material in \MF{} are few and far between (and mostly designing highly specialised things with limited appeal to -ordinary users). Most new fonts that appear are prepared in some -scalable outline form or other (see -\Qref[question]{``choice of scalable fonts''}{Q-psfchoice}), and they -are almost all distributed under commercial terms. +ordinary users); as a result, no-one has taken over maintenance of the +list of fonts. If you need a font for some esoteric purpose, it may +be worth \Qref*{searching \acro{CTAN}}{Q-findfiles} using your purpose +as a search keyword. + +Most new fonts that appear are prepared in some scalable outline form +or other, and a large proportion is distributed under commercial +terms. However, once you have acquired such a font, converting it to +a form usable by your \AllTeX{} distribution is not (in principle) a +serious problem. + +The answer ``\Qref{choice of scalable fonts}{Q-psfchoice}'' discusses +fonts that are configured for general (both textual and mathematical) +use with \AllTeX{}. The list of such fonts is sufficiently short that +they \emph{can} all be discussed in one answer here. \begin{ctanrefs} \item[\nothtml{\rmfamily}\MF{} font list]\CTANref{mf-list} \end{ctanrefs} -\Question[Q-CD]{The \TeX{}~Live distribution} +\Question[Q-CD]{The \TeX{} collection} 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. -The \TeX{}~Live distribution provides this, together with -a ready-to-run \TeX{} system. The \TeX{}~Live installation disc offers -te\TeX{} for use on Unix-like systems, and Pro\TeX{}t for use on Windows -systems. There is also a `demonstration' disc and an archive snapshot -(all on \acro{CD}- or \acro{DVD}-\acro{ROM}s). \TeX{}-Live -was originally developed under the auspices of a consortium of User -Groups (notably \acro{TUG}, \acro{UK}~\acro{TUG} and -\acro{GUT}enberg). All members of several User Groups receive copies -free of charge. Some user groups will also sell additional copies: +The \TeX{} collection provides this, together with +ready-to-run \TeX{} systems for various architectures. Contents of +the collection are: +\begin{itemize} +\item The \texlive{} installation disc (a \acro{CD}) provides \TeX{} + systems for use on \acro{GNU}-Linux, MacOS/X and Win-32 + architectures; +\item The \texlive{} `Live' disc (a \acro{DVD}) providing \TeX{} for + a wider range of architectures; +\item Mac\TeX{}: an easy to install \TeX{} system for MacOS/X, based + on \texlive{}, and including the % ! line break + \href{http://www.uoregon.edu/~koch/texshop/}{texshop front-end} + and other tools; +\item Pro\TeX{}t: an easy to install \TeX{} system for Windows, based + on \miktex{}, and including an `active' document to guide + installation; and +\item A snapshot of \acro{CTAN}. +\end{itemize} +A fair number of national \TeX{} User Groups, as well as \acro{TUG}, +distribute copies to their members at no extra charge. Some user +groups are also able to sell additional copies: contact your local user group or \Qref*{\acro{TUG}}{Q-TUG*}. -Details of \TeX{}~Live are available from its own +You may also download disc images from \acro{CTAN}; the installation +disc, Pro\TeX{}t and Mac\TeX{} are all separately available. Beware: +they are all pretty large downloads. + +Moew details of the collection are available from its own \begin{wideversion} % this really ought to be "hyperversion" or summat - \href{http://www.tug.org/texlive.html}{web page} + \href{http://www.tug.org/texcollection/}{web page} on the \acro{TUG} site. \end{wideversion} \begin{narrowversion} % and non-hyperversion? web page on the - \acro{TUG} site \URL{http://www.tug.org/texlive.html} + \acro{TUG} site \URL{http://www.tug.org/texcollection/} \end{narrowversion} +\begin{ctanrefs} +\item[Mac\TeX{}]\CTANref{mactex} +\item[Pro\TeX{}t]\CTANref{protext} +\item[\TeX{}live install image]\CTANref{texlive} +\end{ctanrefs} %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \section{\TeX{} Systems} \Question[Q-TeXsystems]{\AllTeX{} for different machines} -\keywords{windows,macintosh,ms-dos,os/2,unix,linux} +\keywords{windows,macintosh,macos,ms-dos,os/2,unix,linux} We list here the free or shareware packages; \htmlignore @@ -2885,78 +3070,59 @@ see \Qref{}{Q-commercial} for details of commercial packages. \Qref{commercial \TeX{} vendors'}{Q-commercial} products. \end{htmlversion} \begin{description} -\item[Unix] Instructions for retrieving the \Package{web2c} Unix - \TeX{} distribution via anonymous |ftp| are to be found in - \File{unixtex.ftp}, though nowadays the sensible installer will - take (and possibly customise) one of the packaged distributions such - as te\TeX{}, or the \Qref*{\TeX{}~Live distribution}{Q-CD}. - - To compile and produce a complete te\TeX{} distribution, you need a - \texttt{.tar.gz} file for each of \texttt{teTeX-src}, - \texttt{teTeX-texmf} and \texttt{teTeX-texmfsrc}. - - No sets of te\TeX{} binaries are provided on \acro{CTAN}; however, - compilation of te\TeX{} is pretty stable, on a wide variety of - platforms. If you don't have the means to compile te\TeX{} - yourself, you will find that most ``support'' sites carry compiled - versions in their ``free area'', and the \TeX{}-live discs also - carry a wide range of binary distributions. - - There's a mailing list for te\TeX{} installation problems (and the - like): subscribe by sending mail to - \mailto{majordomo@dbs.uni-hannover.de} containing nothing more than - ``\texttt{subscribe tetex}''. The list is archived at - \URL{http://www.mail-archive.com/tetex@dbs.uni-hannover.de/}, and an - \acro{RSS} feed is available at the same site: - \URL{http://www.mail-archive.com/tetex@dbs.uni-hannover.de/maillist.xml} - - During periods when te\TeX{} is itself under development, a - ``te\TeX{}-beta'' is available. Before proceeding with the - \ensuremath{\beta}-release, check the \File{ANNOUNCE} files - in the two directories on \acro{CTAN}: it may well be that the - \ensuremath{\beta}-release doesn't offer you anything new, - that you need. - - Mac\acro{OS} \acro{X} users should refer to the information below, - under item ``Mac''. +\item[Unix] The only current distribution of \TeX{} for Unix systems + (including \acro{GNU}/Linux and other free Unix-like systems) is + \texlive{}, which is distributed as part of the % ! line break + \Qref*{\TeX{} collection}{Q-CD}. + + Members of many \TeX{} user groups receive copies of the collection + (on \acro{CD} and \acro{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''. \begin{ctanrefs} - \item[tetex]Browse \CTANref{tetex} - \item[tetex-beta]\CTANref{tetex-beta} - \item[unixtex.ftp]\CTANref{unixtexftp} - \item[web2c]\CTANref{web2c} + \item[texlive]Browse \CTANref{texlive} \end{ctanrefs} -\item[Linux] Linux users may use te\TeX{} (see above). +\item[Linux] GNU/Linux users are supported by \texlive{} (as noted + above). A free version of the commercial - \Qref*{V\TeX{}}{Q-commercial} is available, which among other - things, specialises in direct production of \acro{PDF} from - \AllTeX{} input. Unfortunately, it's no longer supported. + \Qref*{V\TeX{} extended \TeX{} system}{Q-commercial} is available + for use under Linux, which among other things specialises in direct + production of \acro{PDF} from \AllTeX{} input. Sadly, it's no + longer supported, and the ready-built images are made for use with a + rather ancient Linux kernel. \begin{ctanrefs} - \item[tetex]Browse \CTANref{tetex} + \item[texlive]Browse \CTANref{texlive} \item[vtex]\CTANref{vtex-linux} \item[vtex \nothtml{\rmfamily}required common files]\CTANref{vtex-common} \end{ctanrefs} -\item[\acro{PC}: Win32] - \miktex{}, by Christian Schenk, is also a comprehensive - distribution, developed separately from the te\TeX{} work. It has +\item[\acro{PC}: Windows post-95] + \miktex{}, by Christian Schenk, is a comprehensive distribution. It has its own previewer, \acro{YAP}, which is itself capable of printing, though the distribution also includes a port of \ProgName{dvips}. The current version is available for file-by-file download (the \acro{HTML} files in the directory offer hints on what you need to get going). The \miktex{} developers provide a - ready-to-run copy of the distribution, on \CDROM{} (for purchase) via the + ready-to-run copy of the distribution, on \acro{CD} (for purchase) via the \href{http://www.miktex.org/cd/}{\miktex{} web site}; otherwise the \File{setup} executable is available on \acro{CTAN}, together with all the optional packages. - \href{http://tug.org/protext/}{Pro\TeX{}t}, by Thomas Feuerstack, is + \href{http://tug.org/protext/}{Pro\TeX{}t}, part of the \TeX{} + collection by Thomas Feuerstack, is a further option for installing \miktex{}. It bundles a \miktex{} setup with some further useful utilities, together with a \acro{PDF} file which contains clickable links for the various installation - steps, along with explanations. It again it is freeware, and copies - are distributed with the \Qref*{\TeX{}-live \acro{CD} set}{Q-CD}. + steps, along with explanations. + + Windows users are also supported directly by the \texlive{} + distribution; a system is provided on the installation disc of the + \TeX{} collection (and it can, with some difficulty, be run ``from + the disc'' without installing \emph{anything}). - \href{https://xemtex.groups.foundry.supelec.fr/}{XEm\TeX{}}, by + \href{http://foundry.supelec.fr/projects/xemtex/}{XEm\TeX{}}, by Fabrice Popineau (he who created the excellent, but now defunct, fp\TeX{} distribution), is an integrated distribution of \TeX{}, \LaTeX{}, \CONTeXT{}, \ProgName{XEmacs} and friends for Windows. All programs @@ -2974,17 +3140,17 @@ see \Qref{}{Q-commercial} for details of commercial packages. \URL{http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/web2c75-e.html} A further (free) option arises from the - \href{http://www.cygwin.com}{``CygWin'' bundle}, which presents a + \href{http://www.cygwin.com}{CygWin bundle}, which presents a Unix-like environment over the Win32 interface; an X-windows server is available. If you run CygWin on your Windows machine, you have - the option of using te\TeX{}, too (you will need the X-server, to - run \ProgName{xdvi}). Of course, te\TeX{} components will look like - Unix applications (but that's presumably what you wanted), but it's - also reputedly somewhat slower than native Win32 implementations - such as \miktex{} or XEm\TeX{}. Te\TeX{} is available as part of the - CygWin distribution (in the same way that a version is available - with most Linux distributions, nowadays), and you may also build - your own copy from the current sources. + the option of using \texlive{}, too (you will need the X-server, to + run \ProgName{xdvi}). Of course, \texlive{} components will look like + Unix applications (of course, that's presumably what you wanted), + but \TeX{} under CygWin also reputedly somewhat slower than native + Win32 implementations such as \miktex{} or XEm\TeX{}. The (now + obsolete) te\TeX{} distribution is provided as part of the CygWin + distribution, and but you can build your own copy of \texlive{} from + the current sources. BaKoMa \TeX{}, by Basil Malyshev, is a comprehensive (shareware) distribution, which focuses on support of Acrobat. The distribution @@ -3026,56 +3192,54 @@ see \Qref{}{Q-commercial} for details of commercial packages. \begin{ctanrefs} \item[djgpp]\CTANref{djgpp} \end{ctanrefs} -\item[\acro{PC}: \acro{OS/}2] \acro{OS/}2 may also use a free version of the +\item[\acro{PC}: \acro{OS/}2] Em\TeX{}, by Eberhard Mattes (see + above), was actually developed under \acro{OS/}2, and lives happily + in that environment. + + \acro{OS/}2 users may also use a free version of the commercial \Qref*{V\TeX{}}{Q-commercial}, which specialises in direct production of \acro{PDF} from \AllTeX{} input. (This version is, like the Linux version, unfortunately no longer supported.) \begin{ctanrefs} + \item[emtex]\CTANref{emtex} + \item[emtexTDS]\CTANref{emtextds} \item[vtex]\CTANref{vtex-os2} \item[vtex \nothtml{\rmfamily}required common files]\CTANref{vtex-common} \end{ctanrefs} -\item[Windows \acro{NT}, other platforms] Ports of \miktex{} for - \acro{NT} on Power \acro{PC} and \acro{AXP} are available. Neither - version has been updated for version~1.2 (or later) of - \miktex{}~--- they may not be satisfactory. - \begin{ctanrefs} - \item[miktex for AXP]\CTANref{miktex-AXP} - \item[miktex for Power PC]\CTANref{miktexppc} - \end{ctanrefs} -\item[Mac] Oz\TeX{}, by Andrew Trevorrow, is a shareware version of +%% \item[Windows \acro{NT}, other platforms] Ports of \miktex{} for +%% \acro{NT} on Power \acro{PC} and \acro{AXP} are available. Neither +%% version has been updated for version~1.2 (or later) of +%% \miktex{}~--- they may not be satisfactory. +%% \begin{ctanrefs} +%% \item[miktex for AXP]\CTANref{miktex-AXP} +%% \item[miktex for Power PC]\CTANref{miktexppc} +%% \end{ctanrefs} +\item[Mac] \href{http://www.trevorrow.com/oztex/}{Oz\TeX{}}, by Andrew + Trevorrow, is a shareware version of \TeX{} for the Macintosh. A \acro{DVI} previewer and \PS{} - driver are also included. -% It should run on any Macintosh Plus, SE, II, or newer model, but -% will not work on a 128K or 512K Mac - - \acro{UK}~\acro{TUG} prepays the shareware fee for its members, so - that they may - acquire the software without further payment. Questions about - Oz\TeX{} may be directed to \mailto{oztex@midway.uchicago.edu} - - Another partly shareware program is \acro{CM}ac\TeX{}, put together - by Tom Kiffe. This is much closer - to the Unix \TeX{} setup (it uses \ProgName{dvips}, for instance). - \acro{CM}ac\TeX{} includes a port of a version of + driver are also included. (Members of \acro{UK}~\acro{TUG} may + acquire the software without further payment, as part of a + membership deal.) Oz\TeX{} does not run, natively, under MacOS/X, + but will run with a sufficiently recent CarbonLib (see + \URL{http://www.trevorrow.com/oztex/ozosx.html}). + Other questions about Oz\TeX{} itself may be directed to + \mailto{oztex@midway.uchicago.edu} + + Another partly shareware program is + \href{http://www.kiffe.com/cmactex.html}{CMac\TeX{}} , put together + by Tom Kiffe. CMac\TeX{} is much closer than Oz\TeX{} to the Unix + \TeX{} model of things (it uses \ProgName{dvips}, for instance). + CMac\TeX{} runs natively under includes a port of a version of \Qref*{Omega}{Q-omegaleph}. - Both Oz\TeX{} and \acro{CM}ac\TeX{} run on either Mac\acro{OS} - \acro{X} or on a sufficiently recent Mac\acro{OS} with CarbonLib - (v1.3~for Oz\TeX{}, v1.4~for \acro{CM}ac\TeX{}). + Both Oz\TeX{} and \acro{CM}ac\TeX{} run on either MacOS/X or on a + sufficiently recent MacOS with CarbonLib + (v1.3~for Oz\TeX{}, v1.4~for CMac\TeX{}). % beware line wrap - Mac\acro{OS}~\acro{X} users also have the option of - \href{http://www.rna.nl/tex.html}{gw\TeX{}}, by Gerben Wierda (which - is based on te\TeX{}). This is naturally usable from the - command line, just like any other Unix-based system, but it can also - be used Mac-style as the engine behind Richard Koch's (free) - \href{http://www.uoregon.edu/~koch/texshop/texshop.html}{TeXShop}, - which is an integrated \TeX{} editor and previewer. - - From its 2005 release, the \Qref*{\TeX{}-Live disc set}{Q-CD} - includes ``Mac\TeX{}'', a \CDROM{} image that contains - Mac\acro{OS}~\acro{X} te\TeX{} (the Gerben Wierda set mentioned - above), TeXshop, and \Qref*{XeTeX}{Q-xetex}. Details (and a - downloadable distribution set) may be found on the + + From its 2005 release, the \Qref*{\texlive{} disc set}{Q-CD} + includes Mac\TeX{}. Details (and a downloadable distribution set) + may be found on the % ! line break \href{http://tug.org/mactex}{\acro{TUG} web site}; the distribution is also on \acro{CTAN}. @@ -3090,26 +3254,20 @@ see \Qref{}{Q-commercial} for details of commercial packages. has a news and `help' section, as well as details of systems and tools. \end{wideversion} + The Mac\TeX{}-on-OSX mailing list is a useful resource for users; + mail \mailto{MacOSX-TeX-on@email.esm.psu.edu} to subscribe. \begin{ctanrefs} \item[cmactex]\CTANref{cmactex} \item[mactex]\CTANref{mactex} \item[oztex]\CTANref{oztex} - \item[MacOS X teTeX]\URL{ftp://ftp.nluug.nl/pub/comp/macosx/tex-gs/} - \item[TeXShop]\URL{http://darkwing.uoregon.edu/~koch/texshop/texshop.html} - \end{ctanrefs} -\item[Open\acro{VMS}] \TeX{} for Open\acro{VMS} is available. - -% Standard tape distribution is through \acro{DECUS} -% (see \Qref[question]{sources of software}{Q-archives}). - \checked{RF}{1994/10/11} +\end{ctanrefs} +\item[Open\acro{VMS}] \TeX{} for Open\acro{VMS} is available, though + it seems unlikely that the version on \acro{CTAN} is the latest + available. \begin{ctanrefs} \item[OpenVMS]\CTANref{OpenVMSTeX} \end{ctanrefs} -\item[Atari] \TeX{} is available for the Atari \acro{ST}. - - If anonymous |ftp| is not available to you, send a message - containing the line `|help|' to - \mailto{atari@atari.archive.umich.edu} +\item[Atari] \TeX{} for the Atari \acro{ST} is available from \acro{CTAN}. \begin{ctanrefs} \item[Atari TeX]\CTANref{atari} \end{ctanrefs} @@ -3121,8 +3279,8 @@ see \Qref{}{Q-commercial} for details of commercial packages. \item[\acro{TOPS}-20] \TeX{} was originally written on a \acro{DEC}-10 under \acro{WAITS}, and so was easily ported to \acro{TOPS}-20. A distribution that runs on - \acro{TOPS}-20 is available via anonymous |ftp| from \FTP|ftp.math.utah.edu| - in \path{pub/tex/pub/web} + \acro{TOPS}-20 is available via anonymous \texttt{ftp} from + \FTP{ftp.math.utah.edu} in \path{pub/tex/pub/web} \checked{RF}{2001/03/01} \end{description} @@ -3142,7 +3300,7 @@ personal selection: within the editor, and everything else like this that you can think of. Complex, but very powerful. - Many who fail to find the versions of \ProgName{emacs} attractive, prefer + Many who consider the versions of \ProgName{emacs} spawn of the devil, prefer \href{http://vim.sourceforge.net}{\ProgName{vim}}, a highly configurable editor (also available for Windows and Macintosh systems). Many plugins are available to support the needs of the \AllTeX{} user, @@ -3198,23 +3356,31 @@ personal selection: For MacOS~X users, the tool of choice appears to be \href{http://www.uoregon.edu/~koch/texshop/texshop.html}{TeXShop}, which combines an editor and a shell with a coherent philosophy of dealing - with \AllTeX{} in the OS~X environment. + with \AllTeX{} in the OS~X environment. TeXShop is distributed as + part of the MacTeX system, and will therefore be available out of + the box on machines on which MacTeX has been installed. - \ProgName{Vim} is available for use on Macintosh systems. + \ProgName{Vim} is also available for use on Macintosh systems. \end{description} Atari, Amiga and \acro{N}e\acro{XT} users also have nice environments. \LaTeX{} users looking for \ProgName{make}-like -facilities should try \ProgName{latexmk}. +facilities should review the answer on +\Qref*{Makefiles for \LaTeX{} documents}{Q-make}. While many \AllTeX{}-oriented editors can support work on \BibTeX{} files, there are many systems that provide specific ``database-like'' -access to your \BibTeX{} files~--- % ! line break -\htmlonly{see }\Qref{``creating a bibliography file''}{Q-buildbib}. +access to your \BibTeX{} files~--- +\begin{wideversion} + see ``\Qref{creating a bibliography file}{Q-buildbib}''. +\end{wideversion} +\begin{narrowversion} + these are discussed in % ! line break + ``\Qref*{creating a bibliography file}{Q-buildbib}''. +\end{narrowversion} \begin{ctanrefs} \item[alpha]\CTANref{alpha} \item[auctex]\CTANref{auctex} \item[epmtex]\CTANref{epmtex} -\item[latexmk]\CTANref{latexmk} \item[LaTeX4Jed]\CTANref{latex4jed} \item[Nedit LaTeX support]\CTANref{nedit-latex} \item[TeXnicCenter]\CTANref{texniccenter} @@ -3301,9 +3467,10 @@ also have email, and normal telephone and fax support. \begin{quote} Dr Christopher Mabb\\ Scientific Word Ltd.\\ - 20 Bankpark Crescent\\ - Tranent\\ - East Lothian, \acro{EH}33 1\acro{AS}\\ + 990 Anlaby Road,\\ + Hull,\\ + East Yorkshire,\\ + \acro{HU}4 6\acro{AT}\\ \acro{UK}\\[0.25\baselineskip] Tel: 0845 766\,0340 (within the \acro{UK}) \\ Fax: 0845 603\,9443 (within the \acro{UK}) \\ @@ -3321,22 +3488,25 @@ also have email, and normal telephone and fax support. Email: \mailto{info@mackichan.com}\\ Web: \URL{http://www.mackichan.com} \end{quote} - Source: Mail from Christopher Mabb, November 2004 + Source: Mail from Christopher Mabb, August 2007 \item[Macintosh; Textures] ``A \TeX{} system `for the rest of - us'\,''; also gives away a \MF{} implementation and some - font manipulation tools. + us'\,''. A beta release of Textures for MacOS/X is + available \URL{http://www.bluesky.com/news/220b.html} + + (Blue Sky also gives away a \MF{} implementation and some + font manipulation tools for Macs.) \begin{quote} Blue Sky Research\\ - 534 SW Third Avenue\\ - Portland, \acro{OR} 97204\\ + PO Box 80424\\ + Portland, \acro{OR} 97280\\ \acro{USA}\\[.25\baselineskip] Tel: 800-622-8398 (within the \acro{USA})\\ - Tel: +1 503-222-9571\\ - Fax: +1 503-222-1643\\ + Tel/Fax: +1 503-222-9571\\ + Fax: +1 503-246-4574\\ Email: \mailto{sales@bluesky.com}\\ Web: \URL{http://www.bluesky.com/} \end{quote} - Source: \TUGboat{} 15(1) (1994) + Source: Mail from Gordon Lee, April 2007 \item[Amiga\TeX{}] A full implementation for the Commodore Amiga, including full, on-screen and printing support for all \PS{} graphics and fonts, IFF raster graphics, automatic font generation, @@ -3369,7 +3539,7 @@ The best public domain \acro{DVI} to \PS{} conversion program, which runs under many operating systems, is Tom Rokicki's \ProgName{dvips}. \ProgName{dvips} is written in \acro{C} and ports easily. All current development is in the context of Karl Berry's \ProgName{kpathsea} -library, and sources are available from the \TeX{}~live repository, +library, and sources are available from the \texlive{} repository, and versions are available in all \TeX{} distributions that recognise the use of \PS{}. @@ -3393,18 +3563,17 @@ will compile under Unix, \acro{VMS}, and on the Atari ST and \acro{DEC}-20s. For Unix systems, Karl Berry's \ProgName{dviljk} uses the same -path-searching library as \ProgName{web2c}. \ProgName{dviljk} is no -longer distributed as a separate source, but the te\TeX{} distribution -holds a copy under the name \ProgName{dvilj}. +path-searching library as \ProgName{web2c}. \begin{ctanrefs} \item[\nothtml{\rmfamily}Beebe drivers]\CTANref{beebe} +\item[dviljk]\CTANref{dviljk} \end{ctanrefs} \Question[Q-otherprinters]{Output to ``other'' printers} In the early years of \TeX{}, there were masses of \acro{DVI} drivers for any (then) imaginable kind of printer, but the steam seems rather -to have gone out of the market for production of such drivers for +to have gone out of the market for production of drivers for printer-specific formats. There are several reasons for this, but the primary one is that few formats offer the flexibility available through \PS{}, and \ProgName{ghostscript} is \emph{so} good, and @@ -3434,10 +3603,8 @@ have good previewers for \acro{PC}s running Windows, or for Macintoshes. For Unix systems, there is one `canonical' viewer, \ProgName{xdvi}. \ProgName{Xdvik} is a version of \ProgName{xdvi} using the \ProgName{web2c} libraries; it is now built from the same distribution -as \ProgName{xdvi}. Unix \TeX{} distributions (such as -te\TeX{}) include a version of \ProgName{xdvik} -using the same version of \ProgName{web2c} as the rest of the -distribution. +as \ProgName{xdvi}. The \texlive{} distributions for Unix systems +include a version of \ProgName{xdvik}. Alternatives to previewing include \begin{itemize} @@ -3485,11 +3652,10 @@ very slow, and requires two or three steps) but it has served for a long time. \AllTeX{} users may now take advantage of two bitmap `drivers'. The -longest-established, \ProgName{dvi2bitmap}, will generate \acro{XBM} and +longer-established, \ProgName{dvi2bitmap}, will generate \acro{XBM} and \acro{XPM} formats, the long-deprecated \acro{GIF} format (which is -now obsolescent, but is -finally, in Summer 2003, to be relieved of the patent protection of -the \acro{LZW} compression it uses), and also +now obsolescent, but has finally been relieved of the patent +protection of the \acro{LZW} compression it uses), and also the modern (\acro{ISO}-standardised) \acro{PNG} format. Dvipng started out as a PNG renderer; from version 1.2 it can also @@ -3551,12 +3717,12 @@ A Unix port of the program (\ProgName{xtexcad}) has been made. \Question[Q-spell]{Spelling checkers for work with \TeX{}} -For Unix, \ProgName{ispell} has long the program of choice; it is well +For Unix, \ProgName{ispell} was long the program of choice; it is well integrated with \ProgName{emacs}, and deals with some \TeX{} syntax. -However, it is increasingly challenged by \ProgName{aspell}, which was -designed as a successor, and certainly performs better on most -metrics; there remains some question as to its performance with -\AllTeX{} sources. +However, it has more-or-less been replaced everywhere, by +\ProgName{aspell}, which was designed as a successor, and certainly +performs better on most metrics; there remains some question as to its +performance with \AllTeX{} sources. For Windows, there is a good spell checker incorporated into many of the \Qref*{shell/editor}{Q-editors} combinations that are available. @@ -3646,7 +3812,7 @@ D.~E.~Knuth during the development of \TeX{}. The ``documented \LaTeX{}'' style of programming (\Qref{}{Q-dtx}) \endhtmlignore \begin{htmlversion} - The \Qref{``documented \LaTeX{}''}{Q-dtx} style of programming + The ``\Qref{documented \LaTeX{}}{Q-dtx}'' style of programming \end{htmlversion} is regarded by some as a form of literate programming, though it only contains a subset of the constructs Knuth used. @@ -3835,7 +4001,7 @@ translator: Since \acro{HTML} is simply an example of \acro{SGML}, we do not need a specific system for \acro{HTML}. However, Nathan Torkington developed -% (\Email|Nathan.Torkington@vuw.ac.nz|) +% (\Email{Nathan.Torkington@vuw.ac.nz}) \ProgName{html2latex} from the \acro{HTML} parser in \acro{NCSA}'s Xmosaic package. The program takes an \acro{HTML} file and generates a \LaTeX{} file from it. @@ -3944,7 +4110,7 @@ The World Wide Web Consortium maintains a list of ``filters'' to % \Qref[question]{sources of software}{Q-archives}) % also contains a program which converts \ProgName{troff} to \TeX{}. -%\item[Scribe] Mark James (\Email|jamesm@dialogic.com|) has a copy of +%\item[Scribe] Mark James (\Email{jamesm@dialogic.com}) has a copy of % \ProgName{scribe2latex} he has been unable to test but which he will % let anyone interested have. The program was written by Van Jacobson % of Lawrence Berkeley Laboratory.% @@ -3996,7 +4162,7 @@ The World Wide Web Consortium maintains a list of ``filters'' to \acro{RTF} that \ProgName{Word} can read. \item[Excel] \ProgName{Excel2Latex} converts an \ProgName{Excel} file into a \LaTeX{} \environment{tabular} environment; it comes as a - |.xls| file which defines some \ProgName{Excel} macros to produce + \extension{xls} file which defines some \ProgName{Excel} macros to produce output in a new format. \end{description} @@ -4102,7 +4268,7 @@ to map to its standard Unicode representation. Unfortunately, no ``general'', simple, automatic process is likely to succeed at this task. See % ! line break -``\Qref{How does \LaTeX{} relate to Plain \TeX{}}{Q-LaTeXandPlain}'' +``\Qref*{How does \LaTeX{} relate to Plain \TeX{}}{Q-LaTeXandPlain}'' for further details. Translating a document designed to work with \LaTeX{} into one @@ -4110,145 +4276,299 @@ designed to work with Plain \TeX{} is likely to amount to carefully including (or otherwise re-implementing) all those parts of \LaTeX{}, beyond the provisions of Plain \TeX{}, which the document uses. +Some of this work is has (in a sense) been done, in the port of the +\LaTeX{} graphics package to Plain \TeX{}. However, while +\Package{graphics} is available, other complicated packages (notably +\Package{hyperref}) are not. The aspiring translator may find the +\Qref*{\Eplain{}}{Q-eplain} system a useful source of code. (In fact, +a light-weight system such as \Eplain{} might reasonably be adopted as +an alternative target of translation, though it undoubtedly gives the +user more than the ``bare minimum'' that Plain~\TeX{} is designed to +offer.) +\begin{ctanrefs} +\item[\latexhtml{\textrm{The}}{The} eplain \nothtml{\rmfamily}system]% + \CTANref{eplain} +\item[\latexhtml{\textrm{`Plain \TeX{}'}}{Plain \TeX{}} graphics]% + \CTANref{graphics-plain} +\end{ctanrefs} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \section{Installing \AllTeX{} files} -\Question[Q-instpackages]{Installing a new package} - -The first step in installing a new package for your \LaTeX{} system -is usually to \Qref*{find where it is}{Q-findfiles} -and then to get it, usually from \acro{CTAN}. However \miktex{}, -since version 2.1, offers a \Qref*{simpler procedure}{Q-miktexinst} -than that described here, for packages it knows about. - -Ordinarily, you should download the whole distribution directory; the -only occasion when this is not necessary is when you are getting -something from one of the \AllTeX{} contributed ``\File{misc}'' -directories on \acro{CTAN}; these directories contain collections of -single files, which are supposedly complete in themselves. - -A small package \meta{smallpack} might be just a single \texttt{.sty} file -(typically \File{smallpack.sty}) with the usage instructions either -included as comments in the file or in a separate user manual or -\File{README} file. More often a package \meta{pack} will come as -a pair of files, \File{pack.ins} and \File{pack.dtx}, written to be -used with the \LaTeX{} \Package{doc} system. The package code must be -extracted from these files. If there is a \File{README} file as part -of the package distribution, read it! - -In the \Package{doc} system, the user manual and documented package -code is in the |.dtx| file, and the |.ins| file contains \LaTeX{} -instructions on what code should be extracted from the |.dtx| file. To -unpack a \Package{doc} package \meta{pack}, do the following: +\Question[Q-installthings]{Installing things on a \AllTeX{} system} + +Installing (or replacing) things on your \AllTeX{} system has the +potential to be rather complicated; the following questions attempt to +provide a step-by-step approach, starting from the point where you've +decided what it is that you want to install: \begin{itemize} -\item Run latex on \Package{pack.ins}. This will generate one or more - files (normally a \Package{pack.sty} file but there may be others - depending on the particular package). -\item Run latex on \Package{pack.dtx} as a start to getting the user - manual and possibly a commented version of the package code. -\item Run latex again on \Package{pack.dtx}, which should resolve any - references and generate a Table of Contents if it was called for. -\item \LaTeX{} may have said ``\texttt{No file pack.ind}''; this is the - source for the command index; if you want the index, process the raw - material with: - \begin{quote} - \texttt{makeindex -s gind.ist pack} - \end{quote} - and run \LaTeX{} again. -\item Print and read \File{pack.dvi} +\item You must \Qref*{find the file you need}{Q-install-find}; +\item If you are going to install a \LaTeX{} package, you may need to + \Qref*{unpack the distributed files}{Q-install-unpack}; +\item It's probably a good idea to % ! line break + \Qref*{generate some documentation to read}{Q-install-doc}; +\item You need to % ! line break + \Qref*{decide where to install the files}{Q-install-where}; +\item You must now \Qref*{install the files}{Q-inst-wlcf}; and + finally +\item You may need to \Qref*{tidy up}{Q-inst-tidy} after the installation. \end{itemize} -Sometimes a user manual is supplied separately from the \File{.dtx} -file. Process this \emph{after} doing the above, just in case the user -manual uses the package it is describing. - -Almost the final stage of the installation is to put the package -file(s) \emph{`where \LaTeX{} can find them'}. Where the magic place -is, and how you put the files there depends on your particular -\LaTeX{} system and how it is set up (see -% beware line-breaking, next three lines -\Qref[question]{the \TeX{} directory structure standard}{Q-tds} for -general principles, -\Qref[question]{where to put files}{Q-wherefiles} for specific advice). - -The final stage is to tell \LaTeX{} that there is a new file, or -files, that it should be able to go and find. Most free \LaTeX{} systems -maintain a database of the names and locations of latex-related files -to enable faster searching. In these systems the database must be -updated, using the script or program provided with the distribution -for this purpose. -\begin{description} -\item[te\TeX{}] Run: \\ - \texttt{texhash} -\item[web2c] On a current \Package{web2c} distribution, \texttt{texhash} - ought to work; if it doesn't, run \texttt{mktexlsr} -\item[\miktex{}] On a \Package{\miktex{}} distribution earlier than v2.0, - click - \texttt{Start}\arrowhyph{}% - \texttt{Programs}\arrowhyph{}% - \texttt{\miktex{}}\arrowhyph{}% - \texttt{Maintenance}\arrowhyph{}% - \texttt{Refresh filename database} -% this sequence confirmed ok for miktex 1.20, 2000/09/14, by Michael -% Dewey of Nottingham University - or get a DOS window and run:\\ - \texttt{initexmf -\relax-update-fndb} +\Question[Q-install-find]{Finding packages to install} + +How did you find about the package? + +If you learned about your package in these \acro{FAQ}s, you should +already have a link to the file: +\begin{narrowversion} + copy that link into a browser, +\end{narrowversion} +\begin{wideversion} + click on that link, +\end{wideversion} +and you can get the file, one way or another. + +If you heard about the file somewhere else, it's possible that the +source told you where to look; if not, try the \acro{CTAN} searching +facilities, such as \URL{http://www.tex.ac.uk/search/}. That (rather +simple) search engine can return data from a search of the CTAN +catalogue (which covers most useful packages), or data from a search +of the names of files on the archive. + +Remember that you may want \File{foo.sty} but that file is distributed +in a \LaTeX{} documented source file \File{foo.dtx}; it's usually best +to search just for \emph{foo}~--- \File{foo.sty} won't be visible +anywhere on the archive or in the catalogue. + +Packages come in a variety of different styles of distribution; the +very simplest will offer just \File{package.sty}~--- in this case, +just download the file and % ! line break +\Qref*{get on with installation}{Q-inst-wlcf}. + +However, most packages occupy their own directory on the archive; in +this case, you should download the whole directory + +Having acquired the package distribution, see % ! line break +``\Qref*{unpacking \LaTeX{} packages}{Q-install-unpack}'' for your +next step. + +\Question[Q-install-unpack]{Unpacking \LaTeX{} packages} + +As discussed \Qref*{elsewhere}{Q-dtx}, the `ordinary' way to +distribute a \LaTeX{} package is as a pair of files \File{package.dtx} +and \File{package.ins}. If you've acquired such a pair, you simply +process \File{package.ins} with \LaTeX{}, and the files will appear, +ready for installation. + +Other sorts of provision should ordinarily be accompanied by a +\File{README} file, telling you what to do; we list a few example +configurations. + +Sometimes, a directory comes with a bunch of \File{.dtx} files, but +fewer (often only one) \File{.ins} files (\LaTeX{} itself comes +looking like this). The way to go, in this case is simply to process +the \File{.ins} file(s) one by one. + +If you're missing the \File{package.ins} altogether, you need to play +around until something works. Some \File{.dtx} files are +``self-extracting''~--- they do without a \File{.ins} file, and once +you've processed the \File{package.dtx}, \File{package.sty} has +automagically appeared. Various other oddities may appear, but the +archivists aim to have \File{README} file in every package, which +should document anything out of the ordinary with the distribution. + +\Question[Q-install-doc]{Generating package documentation} + +We are faced with a range of ``normal'' provision, as well as several +oddities. One should note that documentation of many packages is +available on \acro{CTAN}, without the need of any further effort by +the user~--- such documentation can usually be browsed \emph{in situ}. + +However, if you find a package that does not offer documentation on +the archive, or if you need the documentation in some other format +than the archive offers, you can usually generate the documentation +yourself from what you download from the archive. + +The standard mechanism, for \LaTeX{} packages, is simply to run +\LaTeX{} on the \File{package.dtx} file, as you would any ordinary +\LaTeX{} file (i.e., repeatedly until the warnings go away). + +A variant is that the unpacking process provides a file +\File{package.drv}; if such a thing appears, process it in preference +to the \File{package.dtx} (it seems that when the documented \LaTeX{} +source mechanism was first discussed, the \File{.drv} mechanism was +suggested, but it's not widely used nowadays). + +Sometimes, the \LaTeX{} run will complain that it can't find +\File{package.ind} (the code line index) and/or \File{package.gls} +(the list of change records). Both types of file are processed with +special \ProgName{makeindex} style files; appropriate commands are: +\begin{quote} +\begin{verbatim} +makeindex -s gind package +makeindex -s gglo -o package.gls package.glo +\end{verbatim} +\end{quote} +This author finds that the second (the change record) is generally of +limited utility when reading package documentation; it is, however, +valuable if you're part of the package development team. + +Another common (and reasonable) trick is to provide a separate file +\File{package-doc.tex} or even simply \File{manual.tex}; if the file +\File{package.dtx} doesn't help, simply look around for alternatives. +Such files are treated in the same way as any ``ordinary'' \LaTeX{} +file. + +\Question[Q-inst-wlcf]{Installing files ``where \AllTeX{} can find them''} + +In the past, package documentation used always to tell you to put your +files ``where \LaTeX{} can find them''; this was always unhelpful~--- +if you knew where that \emph{was}, you didn't need telling, but if you +\emph{didn't} know, you were completely stuck. + +It was from this issue that the whole idea of the \acro{TDS} sprang; +``where to put'' questions now come down to ``where's the \acro{TDS} +tree?''. + +We therefore answer the question by considering: +\begin{itemize} +\item \Qref*{what tree to use}{Q-what-TDS}, and +\item \Qref*{where in the tree to put the files}{Q-install-where}. +\end{itemize} + +Once we know the answer to both questions, and we've created any +directories that are needed, we simply copy files to their rightful +location. + +This has done what the old requirement specified: \LaTeX{} (or +whatever) \emph{can} (in principle) find the files. However, in order +that the software \emph{will} find the files, we need to update an +index file. - On a \Package{\miktex{}} distribution v2.0 or later, do:\\ +On a \miktex{} system, open the window \texttt{Start}\arrowhyph{}% - \texttt{Programs}\arrowhyph{}% - \texttt{\miktex{} 2}\arrowhyph{}% - \texttt{\miktex{} Options}, and press the - % beware line break - \texttt{Refresh now} button (\texttt{Update filename database} in - earlier versions of \miktex{}). -\end{description} + \texttt{All Programs}\arrowhyph{}% + \texttt{\miktex{} \meta{version}}\arrowhyph{}% + \texttt{Settings}, +and click on \texttt{Refresh FNDB}. +The job may also be done in a command window, using the command: +\begin{quote} +\begin{verbatim} +initexmf -u +\end{verbatim} +\end{quote} +See the \miktex{} documentation for further details about +\texttt{initexmf}. -Remember that a |\usepackage{pack}| command must be put in the preamble -of each document in which you want to use the \Package{pack} package. +On a te\TeX{} or \texlive{}-based system, use the command +\texttt{texhash} (or if that's not available, \texttt{mktexlsr}~--- +they ought to be different names for the same program). -\Question[Q-wherefiles]{Where to put new files} +Having done all this, the new package will be available for use. -Where precisely you put files that you have downloaded does -depend on what \TeX{} distribution you have. However, -assuming that you have one of the modern \acro{TDS}-compliant -distributions (such as te\TeX{} or \miktex{}) there are -some general rules that you can follow: +\Question[Q-what-TDS]{Which tree to use} -% we're sort-of emulating an enumerated list here, but avoiding the -% indentation normally associated with it. we can't afford the -% indentation, since the columns (in 2-column mode) are so narrow. -\htmlignore -\vspace{2pt} -\noindent -\endhtmlignore -(1) Always install new files in a local \File{texmf} -tree. The root directory will be named something like: +In almost all cases, new material that you install should go into the +``local'' tree of your \AllTeX{} installation. The root directory +will be named something like: +\begin{quote} \begin{verbatim} - teTeX: /usr/share/texmf-local/ or - /usr/local/share/texmf/ - fpTeX: c:\Programs\TeXLive\texmf-local\ - MiKTeX: c:\localtexmf\ +teTeX or TeX-live: /usr/share/texmf-local/ or + /usr/local/share/texmf/ +MiKTeX: c:\localtexmf\ \end{verbatim} -(In fact, a te\TeX{} system can be asked to tell you what its local -root is; on a Unix system, the command to use is: +\end{quote} +You can ask a Unix-alike system (such as te\TeX{} or \texlive{}) where +it believes a local tree should be: \begin{quote} \begin{verbatim} kpsewhich -expand-var "\$TEXMFLOCAL" \end{verbatim} \end{quote} -the output being the actual path.) +the output being the actual path, for example: +\begin{quote} +\begin{verbatim} +/usr/local/share/texmf +\end{verbatim} +\end{quote} +on the workstation the author is using today. -Let's write \texttt{\$TEXMF} for this root, whatever it is for your system. +In a \miktex{} installation, the location will in fact typically be +something you specified yourself when you installed \miktex{} in the +first place, but you may find you need to create one. The \miktex{} +``Settings'' window (% + \texttt{Start}\arrowhyph{}% + \texttt{Programs}\arrowhyph{}% + \texttt{\miktex{}}\arrowhyph{}% + \texttt{Settings}) +has a tab ``\texttt{Roots}''; that tab gives a list of current +\acro{TDS} roots (they're typically not called +\texttt{texmf}-anything). If there's not one there with +``\texttt{local}'' in its name, create an appropriate one (say +``\texttt{Local TeX Files}''), and register it using the window's +``\texttt{Add}'' button. The % ! line break +\href{http://docs.miktex.org/faq/maintenance.html}{Miktex \acro{FAQ}} +suggests that you should create +\texttt{C:\textbackslash{}Local TeX Files}, which is good if you +manage your own machine, but often not even possible in corporate, or +similar, environments where you will need to create a directory +somewhere \emph{you}, rather than the system, control). + +There are circumstances when you might not wish to do this: +\begin{itemize} +\item if the package, or whatever, is ``personal'' (for example, + something commercial that has been licensed to you alone, or + something you're developing yourself), the package should go in your + \Qref*{``home'' \acro{TEXMF} tree}{Q-privinst}; +\item if you have no privilege to write to the local tree, you are + again unlikely to be able to put the package anywhere other than + your home tree; or +\item if you \emph{know} that the package you are installing is a + replacement for the copy on the \acro{TEXMF} tree of your \AllTeX{} + distribution, you should replace the existing copy in the + \acro{TEXMF} tree. +\end{itemize} +The reason one would put things on a local tree is to avoid their +disappearance if the system is upgraded (or otherwise re-installed). -\htmlignore -\vspace{2pt} -\noindent -\endhtmlignore -(2) In your local texmf tree, imitate the directory structure in your -main tree. Here are some examples of where files of given extensions -should go: +The reason one might place upgrades the distribution's main tree is to +avoid confusion. Suppose you were to place the file on the local +tree, and then install a new version of the distribution~--- you might +have an effect like: +\begin{itemize} +\item distribution comes with package version \ensuremath{n}; +\item you install package version \ensuremath{n+1} on the local tree; and +\item the updated distribution comes with package version \ensuremath{n+2}. +\end{itemize} +In such a situation, you will find yourself using version +\ensuremath{n+1} (from the local tree) \emph{after} the new +distribution has been installed. + +If you install in the local tree, the only way to avoid such problems +is to carefully purge the local tree when installing a new +distribution. This is tedious, if you're maintaining a large +installation. + +\Question[Q-install-where]{Where to install packages} + +Where precisely you put files that you have downloaded depends on +what \TeX{} distribution you have. We will assume that you have one +of the modern \acro{TDS}-compliant distributions, and discuss the +general rules that you should follow. + +First, you must decide which tree to put your files into; this isn't +entirely trivial, and is discussed in % ! line break +``\Qref*{choosing a \acro{TDS} tree}{Q-what-TDS}''. + +We'll assume from here on, that you've decided on a directory tree, +and we will write \texttt{\$TEXMF} for it, whatever it is for your +system. + +The basic idea is to imitate the directory structure in your +existing tree(s). Here are some examples of where various sorts of +files should go: +\begin{quote} \begin{verbatim} .sty, .cls or .fd: $TEXMF/tex/latex/<package>/ .dvi, .ps or .pdf: $TEXMF/doc/latex/<package>/ @@ -4258,24 +4578,32 @@ should go: .afm: $TEXMF/fonts/afm/<supplier>/<font>/ .pfb: $TEXMF/fonts/type1/<supplier>/<font>/ .ttf: $TEXMF/fonts/truetype/<supplier>/<font>/ +.otf: $TEXMF/fonts/opentype/<supplier>/<font>/ .pool, .fmt, .base or .mem: $TEXMF/web2c \end{verbatim} -and for modern systems (distributed in 2005 or later, such as -te\TeX{}~3.0, using \acro{TDS} v1.1 layouts): +\end{quote} +and for modern systems (those distributed in 2005 or later, using \acro{TDS} +v1.1 layouts): +\begin{quote} \begin{verbatim} .map: $TEXMF/fonts/map/<syntax>/<bundle>/ .enc: $TEXMF/fonts/enc/<syntax>/<bundle>/ \end{verbatim} -Where of course \meta{package}, \meta{font} and \meta{supplier} depend -upon what's appropriate for the individual file. The \meta{syntax} -(for \texttt{.map} and \texttt{.enc} files) is a categorisation based +\end{quote} +(Map and encoding files went to directories under +\File{$TEXMF/dvips/}, in earlier distributions.) + +In the lists above, \meta{package}, \meta{font} and \meta{supplier} depend +upon what's appropriate for the individual file~--- the supplier +``public'' is commonly used for free fonts. The \meta{syntax} +(for \extension{map} and \extension{enc} files) is a categorisation based on the way the files are written; typically, it's the name of a program such as \ProgName{dvips} or \ProgName{pdftex}. -``Straight'' \AllTeX{} input can take other forms than the \texttt{.sty}, -\texttt{.cls} or \texttt{.fd} listed above, too. Examples are -\texttt{.sto} and \texttt{.clo} for package and class options, -\texttt{.cfg} for configuration information, and so on. +``Straight'' \AllTeX{} input can take other forms than the \extension{sty}, +\extension{cls} or \extension{fd} listed above, too. Examples are +\extension{sto} and \extension{clo} for package and class options, +\extension{cfg} for configuration information, and so on. Note that \meta{font} may stand for a single font or an entire family: for example, files for all of Knuth's Computer Modern fonts are to be @@ -4287,14 +4615,34 @@ fonts, \emph{public}'s directory holds fonts designed by others (originally, but no longer exclusively, in \MF{}). Some packages have configuration files (commonly with file suffix -\texttt{.cfg}), and occasionally other run-time files. The package +\extension{cfg}), and occasionally other run-time files. The package documentation \emph{should} mention these things, but sometimes -doesn't. A common exception is the \texttt{.drv} file, used by some -packages as part of the documentation building process; this is a -hang-over from the pre-\LaTeXe{} predecessor of the package -documentation process. +doesn't. An exception is the \extension{drv} file, used by some +packages as part of the documentation building process; this is +usually part of the package documentation process, and should not be +installed. + +\Question[Q-inst-tidy]{Tidying up after installation} + +There's not usually a lot to do after you've completed the steps +above~--- indeed, if you're merely installed files direct from the +archive, or whatever, there will be precisely nothing left, by way of +debris. + +Things you might care to clean up are: +\begin{itemize} +\item the archive file, if you retrieved your data from the archive + as a \extension{zip} file, or the like; +\item the \extension{dtx} and \extension{ins} files, if you chose not + to install them with the documentation; and +\item the \extension{aux}, \extension{log}, \extension{idx}, etc., + from building the documentation. +\end{itemize} +A simple way of achieving all this is to download to a working +directory that was created for the purpose, and then to delete that +directory and all its contents after you've finished installing. -\Question[Q-miktexinst]{Installing \miktex{} ``known packages''} +\Question[Q-inst-miktex]{Installing \miktex{} ``known packages''} \miktex{} 2.1 (and later) maintains a database of packages it ``knows about'', together with (coded) installation instructions that enable it to @@ -4328,14 +4676,14 @@ mpm --install=<package> your package). If \miktex{} \emph{doesn't} know about the package you're interested -in, you have to use the \Qref*{long-winded procedure}{Q-instpackages} -outlined elsewhere in this \acro{FAQ}. +in, you have to use the \Qref*{long-winded procedure}{Q-installthings} +outlined above. If necessary, repeat to select other packages, and then press ``\texttt{OK}''; \miktex{} tells you how many packages you have selected~--- if you're happy, press ``\texttt{OK}'' again. \miktex{} will go off, download the package (as a -\texttt{.cab} file), if necessary, install the files of the package, and then +\extension{cab} file), if necessary, install the files of the package, and then refresh the filename database so that the files will be found. \Question[Q-tempinst]{``Temporary'' installation of \AllTeX{} files} @@ -4352,7 +4700,7 @@ Modern \TeX{} implementations come with a bunch of search paths built in to them. In most circumstances these paths are adequate, but one sometimes needs to extend them to pick up files in strange places: for example, we may wish to try a new bundle of packages -before \Qref*{installing them `properly'}{Q-instpackages}. To do +before \Qref*{installing them `properly'}{Q-installthings}. To do this, we need to change the relevant path as \TeX{} perceives it. However, we don't want to throw away \TeX{}'s built-in path (all of a sudden, \TeX{} won't know how to deal with all sorts of things). @@ -4412,15 +4760,20 @@ private installation of \AllTeX{} which includes the new stuff you need; this is the ideal, but is not generally possible. So, since you can't install into the public \texttt{texmf} tree, you -have to install into a \File{texmf} of your own; fortunately, the -\acro{TDS} standard allows for this, and te\TeX{} 2.0 actually makes -provision for it, defining an internal variable \texttt{HOMETEXMF} -which points to the directory \File{$HOME/texmf}. (Te\TeX{} 1.0 had -the definition, but suppressed it with comment markers.) +have to install into a \File{texmf} tree of your own; fortunately, the +\acro{TDS} standard allows for this, and modern distributions allow +you to do it. The most modern distributions refer to the tree as +\texttt{\$TEXMFHOME}, but it used to be called \texttt{\$HOMETEXMF}; +so to check that your \TeX{} system does indeed support the mechanism +you should start with +\begin{verbatim} +kpsewhich -expand-var "\$TEXMFHOME" +\end{verbatim} -So, install your new package (or whatever) in the -\Qref*{correct place}{Q-wherefiles} in a tree based on -\File{$HOME/texmf}, and generate an index of that tree +If you can confirm that the technique does indeed work, install your +new package (or whatever) in the \Qref*{correct place}{Q-install-where} +in a tree based on \File{$HOME/texmf}, and generate an index of that +tree \begin{quote} \begin{verbatim} texhash $HOME/texmf @@ -4432,12 +4785,12 @@ since you don't, by hypothesis, have access to the main tree, and tree. There are two wrinkles to this simple formula: first, the installation -you're using may \emph{not} define \texttt{HOMETEXMF} (te\TeX{}~1.0 -didn't, for example), and second, there may be some obstruction to -using \File{$HOME/texmf} as the default name. In either case, a good -solution is to have your own \File{texmf.cnf}~--- an idea that sounds -more frightening that it actually is. The installation's existing -file may be located with the command: +you're using may \emph{not} define a home TEXMF directory, and second, +there may be some obstruction to using \File{$HOME/texmf} as the +default name. In either case, a good solution is to have your own +\File{texmf.cnf}~--- an idea that sounds more frightening that it +actually is. The installation's existing file may be located with the +command: \begin{quote} \begin{verbatim} kpsewhich texmf.cnf @@ -4469,9 +4822,8 @@ everything searches; the simplest form of the line is: TEXMF = !!$TEXMFMAIN \end{verbatim} \end{quote} -but, as te\TeX{}~1.0 is distributed, there are several alternative -settings behind comment markers (``\texttt{\textpercent}''), and the -person who +but, there are likely to be several alternative settings behind +comment markers (``\texttt{\textpercent}''), and the person who installed your system may have left them there. Whatever, you need to modify the line that's in effect: change the above to three lines: \begin{quote} @@ -4481,8 +4833,9 @@ TEXMF = {$HOMETEXMF,!!$TEXMFMAIN} % TEXMF = !!$TEXMFMAIN \end{verbatim} \end{quote} -the important point being that |$HOMETEXMF| must come before whatever -was there before, inside the braces. For example, if the original was +the important point being that \texttt{\$HOMETEXMF} must come before +whatever was there before, inside the braces. For example, if the +original was \begin{quote} \begin{verbatim} TEXMF = {!!$LOCALTEXMF,!!$TEXMFMAIN} @@ -4574,7 +4927,7 @@ learning from them what printer they were generated for, and naming schemes under different operating systems are another source of confusion. -``\Qref*{Where to install files}{Q-wherefiles}'' +``\Qref*{Where to install files}{Q-install-where}'' specifies where the files should go. Further confusion is introduced by font families whose authors devise rules @@ -4689,7 +5042,7 @@ loaded by the command \end{verbatim} Remember, after all such changes, the % beware line breaks -\Qref*{file-name database must be refreshed}{Q-instpackages}. +\Qref*{file-name database must be refreshed}{Q-inst-wlcf}. \begin{ctanrefs} \item[AMS fonts]Browse \CTANref{ams-AMStype1} \item[CM fonts]Browse \CTANref{bluesky} @@ -4737,7 +5090,7 @@ it may be separated into a modest set of stages. \Package{fontinst}: see the documentation for details. \Package{Fontinst} also generates map files, and \LaTeX{} font - definition (\texttt{.fd}) files. + definition (\extension{fd}) files. \item Install the files, in your \texttt{texmf} tree. All the strictures about installing non-standard things apply here: be sure to put the files in the local tree. The list gives reasonable @@ -4766,7 +5119,7 @@ it may be separated into a modest set of stages. .fd .../tex/latex/fontinst/<foundry>/<bname> \end{verbatim} \end{wideversion} - The irregular things being \texttt{.map} files: in te\TeX{} 3.0 and + The irregular things being \extension{map} files: in te\TeX{} 3.0 and later, these should be placed according to the revised \acro{TDS} as \begin{verbatim} .map .../fonts/map/dvips/<foundry> @@ -4776,7 +5129,7 @@ and in other (earlier) systems as .map .../dvips/fontinst/<foundry> \end{verbatim} \item Regenerate the file indexes (as described in - \Qref[question]{package installation}{Q-instpackages}). + \Qref[question]{package installation}{Q-inst-wlcf}). \item Update the \ProgName{dvips} and other maps: \begin{itemize} \item On a te\TeX{} system earlier than version~2.0, edit the file @@ -5013,28 +5366,37 @@ arguments: most (if not all) current distributions generate bitmap fonts as needed, and cache them for later re-use. The impatient user, who is determined that all bitmap fonts should be created once and for all, may be supported by scripts such as \ProgName{allcm} -(distributed with te\TeX{}, at least; otherwise such a person should -consult \Qref[question]{"the use of \MF{}"}{Q-useMF}). +(distributed with \texlive{}, at least; otherwise such a +person should consult ``\Qref*{the use of \MF{}}{Q-useMF})''. -If your output is to a \PS{}-capable device, you advised to switch to +If your output is to a \PS{}-capable device, or if your output is +destined to be converted to \acro{PDF}, you should switch to using Type~1 versions of the \acro{CM} fonts. Two free -sets are currently available; the older (\Package{bakoma}) is +sets are available; the older (\Package{bakoma}) is somewhat less well produced than the \Package{bluesky} fonts, which were originally professionally produced and sold, but were then donated to the public domain by their originators \YandY{} and Bluesky Research, -in association with the \acro{AMS}. Unfortunately, the coverage of -the sets is slightly different, but you are advised to use the +in association with the \acro{AMS}. The two sets contain slightly +different ranges of fonts, but you are advised to use the \Package{bluesky} set except when \Package{bakoma} is for some reason absolutely unavoidable. In recent years, several other `\MF{}' fonts have been converted to Type~1 format; it's common never to need to generate bitmap fonts for any purpose other than previewing (see % beware of line wrap -\Qref[question]{``previewing documents with Type~1 fonts''}{Q-PSpreview}). -\begin{ctanrefs} -\item[bakoma]\CTANref{bakoma} -\item[bluesky]Browse \CTANref{bluesky} -\item[cm fonts \nothtml{\rmfamily}(write-black printers)]\CTANref{pk300} -\item[cm fonts \nothtml{\rmfamily}(write-white printers)]\CTANref{pk300w} +\Qref*{``previewing documents with Type~1 fonts''}{Q-PSpreview}), +if even then. + +More modern fonts may be used in place of the Computer Modern set. The +\Qref*{\acro{EC} fonts}{Q-ECfonts} and the % ! line break +\Qref*{Latin Modern fonts}{Q-uselmfonts} are both close relatives of +Computer Modern with wider ranges of glyphs to offer. +\begin{ctanrefs} +\item[\nothtml{\rmfamily}BaKoMa fonts]\CTANref{bakoma} +\item[\nothtml{\rmfamily}Bluesky fonts]Browse \CTANref{bluesky} +\item[\nothtml{\rmfamily}CM fonts (write-black printers)]\CTANref{pk300} +\item[\nothtml{\rmfamily}CM fonts (write-white printers)]\CTANref{pk300w} +\item[\nothtml{\rmfamily}EC fonts (Type 1 format)]\CTANref{cm-super} +\item[\nothtml{\rmfamily}Latin Modern fonts]\CTANref{lm} \end{ctanrefs} \subsection{Adobe Type~1 (``\PS{}'') fonts} @@ -5121,9 +5483,11 @@ this, you have three options: (See \Qref[question]{}{Q-commercial} for details of these suppliers.) \end{narrowversion} +\typeout{after narrowversion, before wideversion} \begin{wideversion} - (See \Qref{commercial suppliers}{Q-commercial} for details.) + (See \Qref{commercial suppliers}{Q-commercial} for details.) \end{wideversion} +\typeout{after wideversion} \item If you have the \PS{} fonts in Type~1 format, use \ProgName{ps2pk} or \ProgName{gsftopk} (designed for use with the \ProgName{ghostscript} fonts) to make @@ -5232,8 +5596,20 @@ printer driver should support such fonts (\TeX{} itself \emph{only} cares about metrics, not the actual character programs). If you also need mathematics, then you are severely limited by the -demands that \TeX{} makes of maths fonts (for details, see the paper by B.K.P. -Horn in \TUGboat{} 14(3)). +demands that \TeX{} makes of maths fonts (for details, see the papers +by +\begin{wideversion} +% !! line break !! + \href{http://tug.org/TUGboat/Articles/tb14-3/tb40horn.pdf}{B.K.P. Horn in \TUGboat{} 14(3)}, + or by % ! line break + \href{http://tug.org/TUGboat/Articles/tb19-2/tb59bouc.pdf}{Thierry Bouche in \TUGboat{} 19(2)}). +\end{wideversion} +\begin{narrowversion} + B.K.P. Horn in \TUGboat{} 14(3) or by Thierry Bouche in \TUGboat{} + 19(2), available as + \URL{http://tug.org/TUGboat/Articles/tb14-3/tb40horn.pdf} or + \URL{http://tug.org/TUGboat/Articles/tb19-2/tb59bouc.pdf}, respectively). +\end{narrowversion} For maths, then, there are relatively few choices (though the list is at last growing). There are several font families available that are based on Knuth's original designs, and some that complement other @@ -5282,11 +5658,27 @@ mathematics include: fonts come with a \Package{fourier} package for use with \LaTeX{}; text support of \acro{OT}1 encoding is not provided~--- you are expected to use \acro{T}1. -\item[MathDesign](3 entire families\dots{}so far) Paul Pichareau\\ - This (very new: first release was in April 2005) set so far offers - mathematics fonts to match Adobe Utopia, URW Garamond and Bitstream - Charter (all of which are separately available, on \acro{CTAN}, in Type~1 - format). There has been a little comment on these fonts, but none +\item[Fourier/New Century Schoolbook]Michael Zedler\\ + \FontName{Fouriernc} is a configuration using the Fourier fonts in + the context of New Century Schoolbook text fonts. +\item[Kp-fonts]The Johannes Kepler project\\ + The \FontName{kp-fonts} family provides a comprehensive set of text + and maths fonts. The set includes replacement fixed-width and sans + fonts (though some reports have suggested that these are less + successful, and their use may be suppressed when loading the fonts' + \Package{kpfonts} \LaTeX{} support package). +\item[MathDesign](4 entire families\dots{}so far) Paul Pichareau\\ + This set so far offers mathematics fonts to match Adobe Utopia, URW + Garamond, Bitstream Charter (all of which are separately available, + on \acro{CTAN}, in Type~1 format) and Fontsite Garamond + (which is a commercial font, available from the % ! line wrap (twice) +\begin{wideversion} + \href{FontSite Web shop}{http://www.fontsite.com/Pages/FFDownloads.html}). +\end{wideversion} +\begin{narrowversion} + FontSite Web shop, \URL{http://www.fontsite.com/Pages/FFDownloads.html}). +\end{narrowversion} + There has been a little comment on these fonts, but none from actual users posted to the public forums. Users, particularly those who are willing to discuss their experiences, would obviously be welcome. Browse the \acro{CTAN} directory and see which you @@ -5302,9 +5694,8 @@ mathematics include: of the `intellectual' superiority of \MF{} to evaluations of why its adoption is so limited and what might be done about the problem, is to be found at \URL{http://truetex.com/belleek.pdf} (the paper is a - good read, but exhibits the problems discussed in % line wrap - \htmlonly{``}\Qref[question]{getting good \acro{PDF}}{Q-dvips-pdf}\htmlonly{''}~--- - don't try to read it on-screen in Acrobat reader). + good read, but is set with Bitmap fonts, and can be difficult + on-screen in Acrobat reader 5 or earlier). \item[mathptmx]Alan Jeffrey, Walter Schmidt and others.\\ This set contains maths italic, symbol, extension, and roman virtual fonts, built from Adobe Times, Symbol, Zapf Chancery, and the @@ -5420,8 +5811,7 @@ commercially, include: \acro{PSNFSS}, and pre-built metrics are also provided. \nothtml{\bgroup\raggedwithindent} - \acro{TUG} has recently (November 2005) acquired the right to distribute - these fonts; the web site + \acro{TUG} has the right to distribute these fonts; the web site \begin{narrowversion} \href{http://tug.org/lucida/}{``Lucida and TUG''} \end{narrowversion} @@ -5463,7 +5853,7 @@ commercially, include: %% \nothtml{\bgroup\raggedwithindent} %% For a sample, see \URL{http://www.YandY.com/download/mathplus.pdf} %% \nothtml{\par\egroup} -\item[MathTime Pro]Publish or Perish (Michael Spivak)\\ +\item[MathTime Pro2]Publish or Perish (Michael Spivak)\\ This latest instance of the MathTime family covers all the weights (medium, bold and heavy) and symbols of previous versions of MathTime. In addition it has a much extended range of symbols, and @@ -5471,10 +5861,19 @@ commercially, include: The fonts are supported under both Plain \TeX{} and \LaTeXe{}, and are exclusively available for purchase from \Qref*{Personal \TeX{} Inc}{Q-commercial}. - \par + \par{} \nothtml{\bgroup\raggedwithindent} - For a sample, see \URL{http://www.pctex.com/mtpdemo.pdf} + For further details and samples and fliers, see + \URL{http://www.pctex.com/mtpro2.html} \nothtml{\par\egroup} +\item[Minion Pro and MnSymbol]Adobe, \LaTeX{} support and packaging by + Achim Blumensath \emph{et al}.\\ + \FontName{Minion Pro} derives from the widely-available commercial + OpenType font of the same name by Adobe; scripts are provided to + convert relevant parts of it to Adobe Type~1 format. The + \Package{MinionPro} package will set up text and maths support using + \FontName{Minion Pro}, but a separate (free) font set + \FontName{MnSymbol} greatly extends the symbol coverage. \item[PA Math] PA~Math is a family of serif fonts loosely based on the Palatino (\acro{TM}) typeface. PA~Math comprises the fonts necessary for mathematical typesetting (maths @@ -5622,12 +6021,16 @@ print file (\PS{} or \acro{PDF}) for their output device. \CTANref{eulervm} \item[fourier \nothtml{\normalfont}(including metrics and other support for \nothtml{\itshape}utopia]% \CTANref{fourier} +\item[fouriernc]\CTANref{fouriernc} \item[hfbright \nothtml{\normalfont}collection]\CTANref{hfbright} \item[hvmath \nothtml{\normalfont\itshape}(free bitmapped version)]% \CTANref{hvmath} +\item[kpfonts \nothtml{\normalfont}family]\CTANref{kpfonts} \item[Lucida Bright/Math metrics]\CTANref{lucida} \item[Lucida PSNFSS support]\CTANref{lucida-psnfss} \item[MathDesign \nothtml{\normalfont}collection]\CTANref{mathdesign} +\item[Minion Pro support]\CTANref{minionpro} +\item[MnSymbol \nothtml{\normalfont}family]\CTANref{mnsymbol} \item[pxfonts]\CTANref{pxfonts} \item[tmmath \nothtml{\normalfont\itshape}(free bitmapped version)]% \CTANref{tmmath} @@ -5673,7 +6076,7 @@ Text set using nonstdfont ... \end{verbatim} \end{quote} The name you use (\texttt{nonstdfont}, above) is the name of the -\texttt{.tfm} file for the font you want. +\extension{tfm} file for the font you want. If you want to use an italic version of \csx{foo}, you need to use \csx{font} again: @@ -5719,9 +6122,9 @@ family, as well as size and face. The remaining packages all make provision for using encodings other than Knuth's \acro{OT}1. \Package{Plnfss} has a rather basic set of font family details; -however, it is capable of using font description (\texttt{.fd}) files +however, it is capable of using font description (\extension{fd}) files created for \LaTeX{}. (This is useful, since most modern mechanisms -for integrating outline fonts with \TeX{} generate \texttt{.fd} files +for integrating outline fonts with \TeX{} generate \extension{fd} files in their process.) \Package{Fontch} has special provision for \acro{T}1 and \acro{TS}1 @@ -5740,11 +6143,22 @@ alternatives, and can select more than one encoding: as well as Czech Republic and Slovakia. \Package{Ofs} also covers mathematical fonts, allowing you the dubious pleasure of using fonts such as the % ! line break \Qref*{\FontName{pxfonts} and \FontName{txfonts}}{Q-psfchoice}. + +The \Package{pdcmac} Plain \TeX{} macro package aims to be a complete +document preparation environment, like \Qref*{\Eplain{}}{Q-eplain}. One +of its components is a font selection scheme, \Package{pdcfsel}, which +is rather simple but adequately powerful for many uses. The package +doesn't preload fonts: the user is required to declare the fonts the +document is going to use, and the package provides commands to select +fonts as they're needed. The distribution includes a configuration to +use Adobe `standard' fonts for typesetting text. (\Eplain{} itself +seems not to offer a font selection scheme.) \begin{ctanrefs} \item[ec-plain]\CTANref{ec-plain} \item[fontch]\CTANref{fontch} \item[font_selection]\CTANref{font_selection} \item[ofs]\CTANref{ofs} +\item[pdcmac]\CTANref{pdcmac} \item[plnfss]\CTANref{plnfss} \end{ctanrefs} @@ -5836,7 +6250,7 @@ subtree really need not be copied (it's really a pair of sample files), but copy the other three into your existing Local |$TEXMF| tree, and % beware line break -\Qref*{update the filename database}{Q-instpackages}. +\Qref*{update the filename database}{Q-inst-wlcf}. Now, incorporate the fonts in the set searched by \PDFLaTeX{}, \ProgName{dvips}, \ProgName{dvipdfm}, your previewers and @@ -5997,7 +6411,7 @@ current versions of \ProgName{ghostscript} combined with In many circumstances, \ProgName{Ghostscript} combined with a viewer application is actually preferable to Acrobat Reader. For example, on -Windows Acrobat Reader locks the \texttt{.pdf} file it's displaying: this +Windows Acrobat Reader locks the \extension{pdf} file it's displaying: this makes the traditional (and highly effective) \AllTeX{} development cycle of ``Edit\arrowhyph{}Process\arrowhyph{}Preview'' become rather clumsy~--- \ProgName{GSview} doesn't make the same @@ -6077,8 +6491,8 @@ up in \ProgName{Reader}'s display as blurred blobs which are often not recognisable as the original letter, and are often not properly placed on the line. Nevertheless, even now, most \TeX{} systems have \ProgName{dvips} configured to use -\Qref*{\texttt{.pk} files}{Q-pk} in its output. Even -\PDFTeX{} will use \texttt{.pk} files if it can see no alternative for +\Qref*{\extension{pk} files}{Q-pk} in its output. Even +\PDFTeX{} will use \extension{pk} files if it can see no alternative for a font in the document it is processing. Our remedy is to use @@ -6560,8 +6974,8 @@ but may also be \Question[Q-dvipsgraphics]{Imported graphics in \ProgName{dvips}} \ProgName{Dvips}, as originally conceived, can only import a single -graphics format: \nothtml{encapsulated \PS{} (\texttt{.eps} files, }% -\Qref{encapsulated \PS{}}{Q-eps}\htmlonly{ (\texttt{.eps} files}). +graphics format: \nothtml{encapsulated \PS{} (\extension{eps} files, }% +\Qref{encapsulated \PS{}}{Q-eps}\htmlonly{ (\extension{eps} files}). \ProgName{Dvips} also deals with the slightly eccentric \acro{EPS} that is created by \Qref*{\MP{}}{Q-MP}. @@ -6600,10 +7014,10 @@ distributed by \miktex{}, comes with those patches built-in. \PDFTeX{} itself has a rather wide range of formats that it can ``natively'' incorporate into its output \acro{PDF} stream: -\acro{JPEG} (\texttt{.jpg} files) for photographs and similar images, +\acro{JPEG} (\extension{jpg} files) for photographs and similar images, \acro{PNG} files for artificial bitmap images, and \acro{PDF} for vector drawings. Old versions of \PDFTeX{} (prior to version~1.10a) -supported \acro{TIFF} (\texttt{.tif} files) format as an alternative +supported \acro{TIFF} (\extension{tif} files) format as an alternative to \acro{PNG} files; don't rely on this facility, even if you \emph{are} running an old enough version of \PDFTeX{}\dots{} @@ -6611,7 +7025,7 @@ In addition to the `native' formats, the standard \PDFLaTeX{} \Package{graphics} package setup causes Hans Hagen's \File{supp-pdf} macros to be loaded: these macros are capable of translating the output of \MP{} to \acro{PDF} ``on the fly''; thus \MP{} output -(\texttt{.mps} files) may also be included in \PDFLaTeX{} documents. +(\extension{mps} files) may also be included in \PDFLaTeX{} documents. The commonest problem users encounter, when switching from \TeX{}, is that there is no straightforward way to include \acro{EPS} files: @@ -6641,7 +7055,7 @@ An alternative solution is to use \ProgName{purifyeps}, a \ProgName{pstoedit} and of \MP{} to convert your Encapsulated \PS{} to ``Encapsulated \PS{} that comes out of \MP{}'', and can therefore be included directly. Sadly, \ProgName{purifyeps} doesn't work for all -\texttt{.eps} files. +\extension{eps} files. Good coverage of the problem is to be found in Herbert Vo\ss{}' \href{http://pstricks.tug.org/main.cgi?file=pdf/pdfoutput}{\acro{PDF} support page}, @@ -6669,7 +7083,7 @@ which is targeted at the use of \Package{pstricks} in permit the inclusion of bitmap and \acro{PDF} graphics, as does \Qref*{\PDFTeX{}}{Q-pdftexgraphics}, but is also capable of employing \ProgName{ghostscript} ``on the fly'' so as to be able to permit the -inclusion of encapsulated \PS{} (\texttt{.eps}) files by translating +inclusion of encapsulated \PS{} (\extension{eps}) files by translating them to \acro{PDF}. In this way, \ProgName{dvipdfm} combines the good qualities of \ProgName{dvips} and of \PDFTeX{} as a means of processing illustrated documents. @@ -6707,9 +7121,9 @@ code, above, to read: \end{verbatim} \end{quote} which makes the operation feel as simple as does including -\texttt{.eps} images in a \LaTeX{} file for processing with +\extension{eps} images in a \LaTeX{} file for processing with \ProgName{dvips}; the \Package{graphicx} package knows to look for a -\texttt{.bb} file if no bounding box is provided in the +\extension{bb} file if no bounding box is provided in the \csx{includegraphics} command. The one place where usage isn't quite so simple is the need to quote @@ -6806,13 +7220,13 @@ case. but the aspirant \acro{PDF}-maker may be using it for his output, before switching to the scheme). \item Use \cmdinvoke{includegraphics}[...]{filename} without - specifying the extension (i.e., neither \texttt{.eps} nor - \texttt{.pdf}). -\item For every \texttt{.eps} file you will be including, produce a - \texttt{.pdf} version, as described in % beware line break + specifying the extension (i.e., neither \extension{eps} nor + \extension{pdf}). +\item For every \extension{eps} file you will be including, produce a + \extension{pdf} version, as described in % beware line break \Qref[question]{Graphics in \PDFLaTeX{}}{Q-pdftexgraphics}. Having - done this, you will have two copies of each graphic (a \texttt{.eps} - and a \texttt{.pdf} file) in your directory. + done this, you will have two copies of each graphic (a \extension{eps} + and a \extension{pdf} file) in your directory. \item Use \PDFLaTeX{} (rather than \LaTeX{}--\ProgName{dvips}--distillation or \LaTeX{}--\ProgName{dvipdfm}) to produce your \acro{PDF} output. @@ -6991,7 +7405,7 @@ Error: /undefined in cmmi10 \end{verbatim} \end{quote} There is provision in \MP{} for avoiding this problem: issue the -command \texttt{prologues := 2;} at the start of the \texttt{.mp} file. +command \texttt{prologues := 2;} at the start of the \extension{mp} file. Unfortunately, the \PS{} that \MP{} inserts in its output, following this command, is incompatible with ordinary use of the @@ -7273,7 +7687,7 @@ commonly create a key that combines the (primary) author's name and the year of publication, possibly with a marker to distinguish publications in the same year. So, for example, the Dyson, Eddington, Davidson paper about deflection of starlight appears in my -experimental \texttt{.bib} file as \texttt{Dyson20.1}. +experimental \extension{bib} file as \texttt{Dyson20.1}. So, noting the rules of the style, you have `simply' to write a bibliography database. Fortunately, there are several tools to help @@ -7343,7 +7757,7 @@ If your style isn't too `far out', you can probably generate it by using the facilities of the \Package{custom-bib} bundle. This contains a file \File{makebst.tex}, which runs you through a text menu to produce a file of instructions, with which you can generate your -own \texttt{.bst} file. This technique doesn't offer entirely new styles +own \extension{bst} file. This technique doesn't offer entirely new styles of document, but the system's ``master \BibTeX{} styles'' already offer significantly more than the \BibTeX{} standard set. \begin{ctanrefs} @@ -7593,11 +8007,10 @@ Candidates are: You can also acquire new \BibTeX{} styles by use of Norman Gray's \Package{urlbst} system, which is based on a \ProgName{Perl} script that edits an existing \BibTeX{} style file to produce a new -style. The new style thus generated has a |webpage| entry type, and -also offers support for |url| and |lastchecked| fields in the other entry -types. The \ProgName{Perl} script comes with a set of converted -versions of the standard bibliography styles. Documentation is -distributed as \LaTeX{} source. +style. The new style thus generated has a \texttt{webpage} entry type, and +also offers support for \texttt{url} and \texttt{lastchecked} fields +in the other entry types. The \ProgName{Perl} script comes with a set +of converted versions of the standard bibliography styles. Another possibility is that some conventionally-published paper, technical report (or even book) is also available on the Web. In such @@ -7652,15 +8065,15 @@ information about \BibTeX{} itself. \item[eplain \nothtml{\rmfamily}system]\CTANref{eplain} \end{ctanrefs} -\Question[Q-makebib]{Reconstructing \texttt{.bib} files} +\Question[Q-makebib]{Reconstructing \extension{bib} files} -Perhaps you've lost the \texttt{.bib} file you generated your document from, +Perhaps you've lost the \extension{bib} file you generated your document from, or have been sent a document without one. Or even, you've realised the error of building a substantial document without the benefit of \BibTeX{}\dots{} The \ProgName{Perl} script, \Package{tex2bib} makes a reasonable job -of regenerating |.bib| files from \environment{thebibliography} +of regenerating \extension{bib} files from \environment{thebibliography} environments, provided that the original (whether automatically or manually generated) doesn't deviate too far from the ``standard'' styles. @@ -7849,7 +8262,7 @@ To create a bibliography for your document, you need to perform a sequence of steps, some of which seem a bit odd. If you choose to use \BibTeX{}, the sequence is: -First: you need a \BibTeX{} bibliography file (a |.bib| file)~--- see +First: you need a \BibTeX{} bibliography file (a \extension{bib} file)~--- see \nothtml{``creating a \BibTeX{} file'' (\Qref[question]{}{Q-buildbib}).} \begin{htmlversion} ``\Qref[question]{creating a \BibTeX{} file}{Q-buildbib}''. @@ -7882,10 +8295,10 @@ latex myfile \end{verbatim} \end{quote} As \LaTeX{} processes the file, the \csx{bibliographystyle} command -writes a note of the style to the |.aux| file; each \csx{cite} command -writes a note of the citation to the |.aux| file, and the -\csx{bibliography} command writes a note of which |.bib| file is to be -used, to the |.aux| file. +writes a note of the style to the \extension{aux} file; each +\csx{cite} command writes a note of the citation to the +\extension{aux} file, and the \csx{bibliography} command writes a note +of which \extension{bib} file is to be used, to the \extension{aux} file. Note that, at this stage, \LaTeX{} isn't ``resolving'' any of the citations: at every \csx{cite} command, \LaTeX{} will warn you of the @@ -7903,25 +8316,25 @@ bibtex myfile \end{quote} Don't try to tell \BibTeX{} anything but the file name: say \texttt{bibtex myfile.aux} (because you know it's going to read the -|.aux| file) and \BibTeX{} will blindly attempt to process +\extension{aux} file) and \BibTeX{} will blindly attempt to process \texttt{myfile.aux.aux}. -\BibTeX{} will scan the |.aux| file; it will find which bibliography +\BibTeX{} will scan the \extension{aux} file; it will find which bibliography style it needs to use, and will ``compile'' that style; it will note the citations; it will find which bibliography files it needs, and will run through them matching citations to entries in the bibliography; and finally it will sort the entries that have been cited (if the bibliography style specifies that they should be -sorted), and outputs the resulting details to a |.bbl| file. +sorted), and outputs the resulting details to a \extension{bbl} file. Fifth: you run \LaTeX{} again. It warns, again, that each citation is (still) undefined, but when it gets to the \csx{bibliography} command, -it finds a |.bbl| file, and reads it. As it encounters each +it finds a \extension{bbl} file, and reads it. As it encounters each \csx{bibitem} command in the file, it notes a definition of the citation. Sixth: you run \LaTeX{} yet again. This time, it finds values for all -the citations, in its |.aux| file. Other things being equal, you're +the citations, in its \extension{aux} file. Other things being equal, you're done\dots{} until you change the file. If, while editing, you change any of the citations, or add new ones, @@ -7994,7 +8407,7 @@ hand using this ``standard'' bibliography. For style will produce a representative sample of the citations the style will produce. (Because \Package{xampl.bib} is so extreme in some of its ``examples'', the \BibTeX{} run will also give you an interesting -selection of \BibTeX{}'s error messages\dots) +selection of \BibTeX{}'s error messages\dots{}) \begin{ctanrefs} \item[xampl.bib]\CTANref{xampl-bib} \end{ctanrefs} @@ -8076,7 +8489,7 @@ section or chapter (i.e., it patches \end{wideversion} (Note that the optional argument of \csx{cite} appears \emph{before} the new tag argument, and that the \csx{bibliography} commands may list -more than one \texttt{.bib} file~--- indeed all \csx{bibliography} commands +more than one \extension{bib} file~--- indeed all \csx{bibliography} commands may list the same set of files.) The \csx{bibliography} data goes into files whose names are @@ -8111,7 +8524,7 @@ bibliography commands. So one might write: \end{verbatim} \end{quote} Again, as for \Package{multibbl}, any \csx{bibliography...} command may -scan any list of \texttt{.bib} files. +scan any list of \extension{bib} files. \BibTeX{} processing with \Package{multibib} is much like that with \Package{multibbl}; with the above example, one needs: @@ -8152,7 +8565,7 @@ Note the different way of specifying a bibliographystyle: if you want a different style for a particular bibliography, you may give it as an optional argument to the \environment{btSect} environment. -Processing with \BibTeX{}, in this case, uses \texttt{.aux} files whose names +Processing with \BibTeX{}, in this case, uses \extension{aux} files whose names are derived from the name of the base document. So in this example you need to say: \begin{quote} @@ -8169,7 +8582,7 @@ database, this is equivalent to \LaTeX{} standard \cmdinvoke{nocite}{*}). However, the \emph{real} difference from \Package{miltibbl} and \Package{mltibib} is that selection of what appears in each bibliography section is determined in \Package{bibtopic} by what's in -the \texttt{.bib} files. +the \extension{bib} files. An entirely different approach is taken by the \Package{splitbib} package. You provide a \environment{category} environment, in the @@ -8205,7 +8618,7 @@ the entry appear in a footnote. Options for entries in running text are \begin{itemize} \item The package \Package{bibentry}, which puts slight restrictions - on the format of entry that your \texttt{.bst} file generates, but is + on the format of entry that your \extension{bst} file generates, but is otherwise undemanding of the bibliography style. \item The package \Package{inlinebib}, which requires that you use its \File{inlinebib.bst}. \Package{Inlinebib} was actually designed for @@ -8298,7 +8711,7 @@ combined entry for paper~1 and paper~2, and `11' will refer to paper~3. You need to make a small change to the bibliography style -(\texttt{.bst}) file you use; the \Package{mcite} package +(\extension{bst}) file you use; the \Package{mcite} package documentation tells you how to do that. Unfortunately, the \Class{revtex} system doesn't play with @@ -8310,7 +8723,7 @@ system) you need to play silly games like: \nocite{paper2} \end{verbatim} \end{quote} -and then edit the \texttt{.bbl} file to merge the two citations, to +and then edit the \extension{bbl} file to merge the two citations, to achieve the effects of \Package{mcite}. \begin{ctanrefs} \item[mcite.sty]\CTANref{mcite} @@ -8355,7 +8768,7 @@ the typeset output to be sorted in some magical way. \BibTeX{} doesn't work that way!~--- if you write \environment{thebibliography}, you get to sort its contents. \BibTeX{} will only sort the contents of a \environment{thebibliography} environment when it creates it, to -be inserted from a |.bbl| file by a \csx{bibliography} command. +be inserted from a \extension{bbl} file by a \csx{bibliography} command. \Question[Q-compactbib]{Reducing spacing in the bibliography} @@ -8415,8 +8828,8 @@ citations in captions, and have a list of figures (or tables). There's a pretty simple ``manual'' method for dealing with the problem~--- when you have the document stable: \begin{enumerate} -\item Delete the \texttt{.aux} file, and any of \texttt{.toc}, - \texttt{.lof}, \texttt{.lot} files. +\item Delete the \extension{aux} file, and any of \extension{toc}, + \extension{lof}, \extension{lot} files. \item Run \LaTeX{}. \item Run \BibTeX{} for the last time. \item Run \LaTeX{} often enough that things are stable again. @@ -8525,7 +8938,7 @@ but if you're not using such a package, the following internal \LaTeX{} and \BibTeX{} co-operate to offer special treatment of this requirement. The command \cmdinvoke{nocite}{*} is specially treated, and causes \BibTeX{} to generate bibliography entries for every entry -in each \texttt{.bib} file listed in your \csx{bibliography} statement, so +in each \extension{bib} file listed in your \csx{bibliography} statement, so that after a \LaTeX{}--\BibTeX{}--\LaTeX{} sequence, you have a document with the whole thing listed. @@ -8538,10 +8951,22 @@ Note that \LaTeX{} \emph{doesn't} produce to run things), but the lack might confuse automatic processors that scan the log file to determine whether another run is necessary. +A couple of packages are available, that aim to reduce the impact of +\cmdinvoke{nocite}{*} of a large citation database. \Package{Biblist} +was written for use under \LaTeXo{}, but seems to work well enough; +\Package{listbib} is more modern. Both provide their own +\extension{bst} files. (The impact of large databases was significant +in the old days of \LaTeX{} systems with very little free memory; this +problem is less significant now than it once was.) +\begin{ctanrefs} +\item[biblist.sty]\CTANref{biblist} +\item[listbib.sty]\CTANref{listbib} +\end{ctanrefs} + \Question[Q-htmlbib]{Making \acro{HTML} of your Bibliography} A neat solution is offered by the \Package{noTeX} bibliography style. -This style produces a \texttt{.bbl} file which is in fact a series of +This style produces a \extension{bbl} file which is in fact a series of \acro{HTML} `\texttt{P}' elements of class \texttt{noTeX}, and which may therefore be included in an \acro{HTML} file. Provision is made for customising your bibliography so that its content when processed by @@ -8554,7 +8979,7 @@ styles, and post-process the output so produced using a \ProgName{perl} script. A more conventional translator is the \ProgName{awk} script -\ProgName{bbl2html}, which translates the \texttt{.bbl} file you've generated: +\ProgName{bbl2html}, which translates the \extension{bbl} file you've generated: a sample of the script's output may be viewed on the web, at \URL{http://rikblok.cjb.net/lib/refs.html} \begin{ctanrefs} @@ -8677,6 +9102,11 @@ classes; \Package{pdfscreen} will even allow you to plug A more detailed examination of the alternatives (including examples of code using many of them) may be found at Michael Wiedmann's fine \URL{http://www.miwie.org/presentations/presentations.html} + +\CONTeXT{} users will find that much (if not all) of what they need is +already in \CONTeXT{} itself; there's a useful summary of what's +available, with examples, in +\URL{http://wiki.contextgarden.net/Presentation_Styles} % \begin{ctanrefs} \item[beamer.cls]Download all of \CTANref{beamer} @@ -9681,13 +10111,33 @@ Documentation of \Package{chappg} is to be found in the package file. \Question[Q-papersize]{Printer paper sizes} -Paper sizes can be a pain: they're a forgotten backwater, because +If you're looking at this answer, it's likely you have a problem with +fitting output to the page. It may be a common problem with Adobe +\ProgName{[Acrobat] Reader}: printing from that program % ! line break +\emph{by default} shrinks the page ''to fit''. Unfortunately, its +calculation doesn't take the existing margins of the document into +account, so that it shrinks what it believes is your whole page onto +what it believes is its output page. The effect typically looks as if +your margins have expanded. + +Solve this problem by adjusting the \ProgName{Reader}'s default in the +print dialogue; unfortunately, this dialogue varies from one version +to the next. On \ProgName{Reader} version 7, there are two entries to +check: +\begin{quote} + Page Scaling (default: ''Fit to printer margins'')~--- change to + ''None'', and\\ + Scale (default 95\% of Normal size)~--- change to ''100\%''. +\end{quote} + +More generally, we should recognise that paper sizes can be a pain: +they're a forgotten backwater, because there's no \acro{DVI} command to specify the paper size of the document. One usually finds American ``letter'' paper size being -used, by default, in macro packages (such as \Class{plain} and -\LaTeX{}); but distributions provide configuration files for -\acro{DVI} drivers (and since most distributions originate in Europe, -the drivers usually default to \acro{ISO} ``A4'' paper size). +assumed, by default, in macro packages (such as \Class{plain}~\TeX{} and +\LaTeX{}); but distributions provide separate configuration files for +\acro{DVI} drivers. Since most distributions nowadays originate in +Europe, the drivers usually default to \acro{ISO} ``A4'' paper size. This is (of course) pretty unsatisfactory. Users may change the paper size their document is designed for, pretty easily (and once off), but @@ -9695,7 +10145,7 @@ they have to ensure that every run of \ProgName{xdvi}, \ProgName{dvips}, or whatever, is given the correct override for using anything non-`standard'. -Of course, the default paper size for \acro{DVI} drivers may be +Furthermore, the default paper size for \acro{DVI} drivers may be changed by a distribution management command, but this still doesn't provide for people using the ``wrong'' sort of paper for some reason. @@ -9716,8 +10166,8 @@ The \Package{geometry} package (whose main business is defining typeset page areas), also takes notice of the paper size the document is going to print to, and can issue the commands necessary to ensure the correct size is used. If \Package{geometry} is used when a -document is being processed by either \PDFLaTeX{} or V\TeX{}, it will -set the necessary dimensions as a matter of course. If the document +document is being processed by either \PDFLaTeX{} or V\TeX{}, it can +set the necessary dimensions ''in the output''. If the document is being processed by \LaTeX{} on a \TeX{} or \eTeX{} engine, there are two package options (\pkgoption{dvipdfm} and \pkgoption{dvips}) which instruct \Package{geometry} which \csx{special} commands to use. @@ -10534,8 +10984,7 @@ emphasis of text set in Fraktur (or similar) fonts. Straightforward macros (usable, in principle, with any \TeX{} macro package) may be found in \Package{letterspacing} (which is the name of -the |.tex| file; it also appears as the \Package{letterspace} package -in some distributions). +the \extension{tex} file). %%% the package has a serious bug in it, so suppress mention pro tem %The \Package{tracking} package has similar facilities. @@ -10546,8 +10995,18 @@ Plain \TeX{}). Soul also permits hyphenation of letterspaced text; Gill's view of such an activity is not (even apocryphally) recorded. (Spacing-out forms part of the name of \Package{soul}; the other half is described in \Qref[question]{another question}{Q-underline}.) + +Possibly the `ultimate' in this field is the \Package{letterspace}, +which uses the micro-typography capabilities of current \PDFTeX{}. +\Package{Letterspace} expands the natural spacing font itself, rather +than inserting space between characters. Ordinarily, letter-spacing +will destroy ligatures; however, this is \emph{wrong} if the font is +of a fraktur style. \Package{Letterspace} provides a means of +protecting the ligatures in a letter-spaced text. \begin{ctanrefs} \item[letterspacing.tex]\CTANref{letterspacing} +\item[letterspace.sty]Distributed as part of the \CTANref{microtype} + bundle \item[soul.sty]\CTANref{soul} %\item[tracking.sty]\CTANref{tracking} \end{ctanrefs} @@ -10605,13 +11064,11 @@ standard \LaTeX{} class with \pkgoption{twocolumn} option will have |1.0em| by default, and there's no knowing what you (or some other class) will have done. -If you are using Martin Schr\"oder's \Package{ragged2e} package, it is -worth updating to the latest release (January 2003), which has a -\csx{justifying} command to match its % ! line break +Any but a really old copy of Martin Schr\"oder's \Package{ragged2e} +package has a \csx{justifying} command to match its % ! line break \Qref*{versions of the \LaTeX{} `ragged' commands}{Q-ragright}. The -package also provides a -\environment{justify} environment, which permits areas of justified -text in a larger area which is ragged. +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} \end{ctanrefs} @@ -11057,8 +11514,19 @@ package (directly or indirectly); both \Package{path} and (\Package{hyperref} isn't available in a version for use with Plain \TeX{}.) -Documentation of both \Package{path} and \Package{url} is in the -package files. +Note that neither \csx{path} (from package \Package{path}) nor \csx{url} (from +package \Package{url}) is robust (in the \LaTeX{} sense). If you need +a \acro{URL} to go in a moving argument, you need the command +\csx{urldef} from the \Package{url} package. So one might write: +\begin{quote} +\begin{verbatim} +\urldef\faqhome\url{http://www.tex.ac.uk/faq} +\end{verbatim} +\end{quote} +after which, \csx{faqhome} is robust. + +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} @@ -11183,7 +11651,7 @@ pretty straightforward. The \Package{dropping} package does the job simply, but has a curious attitude to the calculation of the size of the font to be used for the big letters. Examples appear in the package documentation, so before -you process the |.dtx|, the package itself must already be installed. +you process the \extension{dtx}, the package itself must already be installed. Unfortunately, \Package{dropping} has an intimate relation to the set of device drivers available in an early version of the \LaTeX{} graphics package, and it cannot be trusted to work with recent @@ -11201,24 +11669,43 @@ without installing the package itself). \Question[Q-dec_comma]{The comma as a decimal separator} -If you use a comma in maths mode, you get a small space after it; this -space is inappropriate if the comma is being used as a decimal -separator. An easy solution to this problem, in maths -mode, is to type \texttt{3}\marg{,}\texttt{14} instead of typing -\texttt{3,14}. However, if your language's -typographic rules require the comma as a decimal separator, such usage -can rapidly become extremely tiresome. There are two packages that +\TeX{} embodies the British/American cultural convention of using a +period as the separator between the whole number and the decimal +fraction part of a decimal number. Other cultures use a comma as +separator, but if you use a comma in maths mode you get a small space +after it; this space makes a comma that is used as a decimal separator +look untidy. + +A simple solution to this problem, in maths mode, is to type +\texttt{3}\marg{,}\texttt{14} in place of \texttt{3,14}. While such a +technique may produce the right results, it is plainly not a +comfortable way to undertake any but the most trivial amounts of +typing numbers. + +Therefore, if you need to use commas as decimal separator, you will +probably welcome macro support. There are two packages that can help relieve the tedium: \Package{icomma} and \Package{ziffer}. \Package{Icomma} ensures that there will be no extra space after a -comma, unless you type a space after it (as in \texttt{f(x, y)}, for -instance), in which case the usual small space after the comma -appears. \Package{Ziffer} is specifically targeted at the needs of -those typesetting German, but covers the present need, as well as -providing the double-minus sign used in German (and other languages) -for the empty `cents' part of an amount of currency. +comma, unless you type a space after it (as in \texttt{f(x, y)}~--- in +the absence of the package, you don't need that space), in which case +the usual small space after the comma appears. \Package{Ziffer} is +specifically targeted at the needs of those typesetting German, but +covers the present need, as well as providing the double-minus sign +used in German (and other languages) for the empty `cents' part of an +amount of currency. + +The \Package{numprint} package provides a command +\cmdinvoke*{numprint}{number} that prints its argument according to +settings you give it, or according to settings chosen to match the +language you have selected in \Package{babel}. The formatting works +equally well in text or maths. The command is very flexible (it can also +group the digits of very `long' numbers), but is inevitably less +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[numprint.sty]\CTANref{numprint} \item[ziffer.sty]\CTANref{ziffer} \end{ctanrefs} @@ -11404,8 +11891,8 @@ The way the relevant parts of sectioning commands work is exemplified by the way the \csx{chapter} command uses the counter \texttt{secnumdepth} (described in Appendix~C of the \LaTeX{} manual): \begin{enumerate} -\item put something in the \texttt{.aux} file, which will appear in - the \texttt{.toc}; +\item put something in the \extension{aux} file, which will appear in + the \extension{toc}; \htmlignore \item if \ensuremath{\texttt{secnumdepth} \geq 0}, \endhtmlignore @@ -11497,6 +11984,20 @@ document is single-sided~--- in that case, it's a synonym for \csx{clearpage}). Ensuring that the entry refers to the right place is trickier still in a \csx{section}-based class. +If you are using \Package{hyperref} (which will link entries in the +table of contents to the relevant place in the file), a slight +adjustment is necessary: +\begin{quote} +\begin{verbatim} +\phantomsection +\cleardoublepage +\addcontentsline{toc}{chapter}{Bibliography} +\bibliography{frooble} +\end{verbatim} +\end{quote} +The extra command (\csx{phantomsection}) gives \Package{hyperref} +something to ``hold on to'' when making the link. + The common solution, therefore, is to use the \Package{tocbibind} package, which provides many facilities to control the way these entries appear in the table of contents. @@ -11505,6 +12006,7 @@ Classes of the \Class{KOMA-script} bundle provide this functionality as a set of class options; the \Class{memoir} class includes \Package{tocbibind} itself. \begin{ctanrefs} +\item[hyperref.sty]\CTANref{hyperref} \item[\nothtml{\rmfamily}KOMA script bundle]\CTANref{koma-script} \item[memoir.cls]\CTANref{memoir} \item[tocbibind.sty]\CTANref{tocbibind} @@ -11519,7 +12021,7 @@ but, as the documentation observes, mini-bibliographies are a different problem~--- see \Qref[question]{bibliographies per chapter}{Q-chapbib}. -The package's basic scheme is to generate a little \texttt{.aux} file for +The package's basic scheme is to generate a little \extension{aux} file for each chapter, and to process that within the chapter. Simple usage would be: \begin{quote} @@ -11561,8 +12063,8 @@ separate topics. The \Package{multind} package provides simple and straightforward multiple indexing. You tag each \csx{makeindex}, \csx{index} and \csx{printindex} command with a file name, and indexing commands are -written to (or read from) the name with the appropriate (\texttt{.idx} or -\texttt{.ind}) extension appended. The \csx{printindex} command is modified +written to (or read from) the name with the appropriate (\extension{idx} or +\extension{ind}) extension appended. The \csx{printindex} command is modified from the \LaTeX{} standard so that it doesn't create its own chapter or section heading; you therefore decide what names (or sectioning level, even) to use for the indexes, and @@ -11600,8 +12102,8 @@ get\dots{}) The \Package{index} package provides a comprehensive set of indexing facilities, including a \csx{newindex} command that allows the definition of new styles of index. \csx{newindex} takes a `tag' (for -use in indexing commands), replacements for the \texttt{.idx} and -\texttt{.ind} file extensions, and a title for the index when it's +use in indexing commands), replacements for the \extension{idx} and +\extension{ind} file extensions, and a title for the index when it's finally printed; it can also change the item that's being indexed against (for example, one might have an index of artists referenced by the figure number where their work is shown). @@ -11668,8 +12170,8 @@ as does \Package{index}. An example of use appears in the documentation. The \Class{memoir} class has its own multiple-index functionality (as -well as index layout options, which other packages delegate to the -index style used by \ProgName{makeindex}. +well as its own index layout options, which other packages delegate to +the index style used by \ProgName{makeindex}). \begin{ctanrefs} \item[index.sty]\CTANref{index} \item[makeidx.sty]Part of the \LaTeX{} distribution @@ -11709,7 +12211,7 @@ which will work standing alone (i.e., without \Package{hyperref}: of course, in this mode its references are not hyperlinked). If you load \Package{hyperref} itself, \Package{nameref} is automatically loaded. \Class{Memoir} requires the \Package{memhfixc} when running with -\Package{hyperref}; however, following the sequence +\Package{hyperref}; following the sequence: \begin{quote} \begin{verbatim} \documentclass[...]{memoir} @@ -11720,11 +12222,28 @@ course, in this mode its references are not hyperlinked). If you load \end{quote} \Package{nameref} commands may be used in a \Class{memoir} document. -Each of the name-reference packages defines a reference command -with the same name as the package: \csx{titleref}, \csx{byname} and -\csx{nameref}. The \Package{nameref} package also defines a command -\csx{byshortnameref}, which uses the optional `short' title argument -to the chapter and section commands. +\Package{Zref} defines a proposed replacement for all of the \LaTeX{} +reference mechanisms, and among other things provides +name-referencing mechanisms: +\begin{quote} +\begin{verbatim} +\usepackage[user,titleref]{zref} +... +\section{hello}\zlabel{sec:one} +The section name is: \ztitleref{sec:one}. +\end{verbatim} +\end{quote} +(One might hope that something of this sort would be the ``way of the +future'', but things move slowly in the \LaTeX{} world: don't hold +your breath.) + +Each of \Package{titleref}, \Package{byname} and \Package{nameref} +defines a reference command with the same name as the package: +\csx{titleref}, \csx{byname} and \csx{nameref}. The \Package{nameref} +package also defines a command \csx{byshortnameref}, which uses the +optional `short' title argument to the chapter and section commands. +(Although it comes from the same author, \Package{zref} \emph{doesn't} +define a short-name variant.) \begin{ctanrefs} \item[byname.sty]Distributed with \CTANref{smartref} \item[hyperref.sty]\CTANref{hyperref} @@ -11732,6 +12251,7 @@ to the chapter and section commands. \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} \end{ctanrefs} \Question[Q-extref]{Referring to labels in other documents} @@ -11935,8 +12455,19 @@ sub- and superscripts in the % ! line break ``\Qref*{\csx{limits} position}{Q-limits}''. The \Package{amsopn} command \csx{operatorname} allows you to -introduce \emph{ad hoc} operators into your mathematics; as with -\csx{DeclareMathOperator} there's a starred version +introduce \emph{ad hoc} operators into your mathematics, so +\begin{quote} + \csx{[} \cmdinvoke{operatorname}{foo}\texttt{(bar)} \csx{]} +\end{quote} +typesets the same as +\begin{quote} +\begin{verbatim} +\DeclareMathOperator{\foo}{foo} +... +\[ \foo(bar) \] +\end{verbatim} +\end{quote} +As with \csx{DeclareMathOperator} there's a starred version \csx{operatorname*} for sub- and superscripts in the limits position. (It should be noted that ``log-like'' was reportedly a \emph{joke} on @@ -12154,6 +12685,11 @@ will serve. Either of these forms may have effects other than on the operator you're considering, but there are still those who prefer this formulation. +Remember, if you're % ! line break +\Qref*{declaring a special operator of your own}{Q-newfunction}, the +\AMSLaTeX{} functions (that you ought to be using) allow you to choose +how limits are displayed, at definition time. + (Note that the macro \csx{int} normally has \csx{nolimits} built in to its definition. There is an example in the \TeX{}book to show how odd \csx{int}\csx{limits} looks when typeset.) @@ -12388,6 +12924,30 @@ ${a+b+c+d} = z+y+x+w$ The braces say ``treat this subformula as one atom'' and (in \TeX{} at least) atoms don't get split: not a \csx{binoppenalty} change in sight. +\Question[Q-mathonlyref]{Numbers for referenced equations only} + +There are those who consider that papers look untidy with numbers on +every equation; there is also a school of thought that claims that +there should be numbers everywhere, in case some reader wants to make +reference an equation to which the author made no cross-reference. + +If you hold to the ``only cross-referenced'' school of thought, you +can (using the \csx{nonumber} command on the relevant equations, or by +using the \AMSLaTeX{} unnumbered environments such as +\environment{equation*}) mark those of your equations to which you +make no reference. In a long or complex paper, this procedure could +well become deeply tedious. + +Fortunately, help is at hand: the \Package{mh} bundle's +\Package{mathtools} package offers a `\pkgoption{showonlyrefs}' +switch through its \csx{mathtoolsset} command; when that's in +operation, only those equations to which you make reference will be +numbered in the final output. See the package's documentation for +details of how to make references when the switch is in effect. +\begin{ctanrefs} +\item[mathtools.sty]Distributed as part of \CTANref{mh} +\end{ctanrefs} + \subsection{Lists} \Question[Q-enumerate]{Fancy enumeration lists} @@ -12490,7 +13050,7 @@ The \Class{memoir} class includes functions that match those in the \item[paralist.sty]\CTANref{paralist} \end{ctanrefs} -\Question[Q-complist]{How to reduce list spacing} +\Question[Q-complist]{How to adjust list spacing} \Qref*{Lamport's book}{Q-books} lists various parameters for the layout of list (things like \csx{topsep}, @@ -12566,20 +13126,33 @@ purpose. For ultimate flexibility (including manipulation of \csx{topsep}), the \Package{enumitem} package permits adjustment of list parameters using -a ``\emph{key}\latexhtml{\ensuremath{=}}{=}\meta{value}'' format; so -for example, one might write +a ``\emph{key}\latexhtml{\ensuremath{=}}{=}\meta{value}'' format. +For example, one might write \begin{quote} \begin{verbatim} \usepackage{enumitem} ... \begin{enumerate}[topsep=0pt, partopsep=0pt] -\item ... ... +\item ... +\item ... \end{enumerate} \end{verbatim} \end{quote} -to suppress all spacing above and below your list. \Package{Enumitem} -also permits manipulation of the label format in a more ``basic'' -manner than the \Qref*{\Package{enumerate} package}{Q-enumerate} does. +to suppress all spacing above and below your list, or +\begin{quote} +\begin{verbatim} +\usepackage{enumitem} +... +\begin{enumerate}[itemsep=2pt,parsep=2pt] +\item ... +\item ... +\end{enumerate} +\end{verbatim} +\end{quote} +to set spacing between items and between paragraphs within items. +\Package{Enumitem} also permits manipulation of the label format in a +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[enumitem.sty]\CTANref{enumitem} @@ -12668,7 +13241,7 @@ which requires use of extra braces: \end{verbatim} \end{quote} \nothtml{\noindent}The \Package{enumitem} package, in its most recent -release, will allow you to resume lists, at one level only: +release, will also allow you to resume lists: \begin{quote} \begin{verbatim} \begin{enumerate} @@ -12683,6 +13256,34 @@ release, will allow you to resume lists, at one level only: which feels just as ``natural'' as the \Package{mdwtools} facility, and has the advantage of playing well with the other excellent facilities of \Package{enumitem}. + +\Package{Enumitem} also allows multi-level suspension and resumption +of lists: +\begin{quote} +\begin{verbatim} +\begin{enumerate} +\item outer item 1 +\end{enumerate} +<comment> +\begin{enumerate}[resume] +\item outer item 2 +% nested enumerate +\begin{enumerate} +\item inner item 1 +\end{enumerate} +<nested comment> +% resume nested enumerate +\begin{enumerate}[resume] +\item inner item 2 +\end{enumerate} +\item outer item 3 +% end outer enumerate +\end{enumerate} +\end{verbatim} +However, the comment interpolated in the nested enumeration appears as +if it were a second paragraph to ``outer item 2'', which is hardly +satisfactory. +\end{quote} \begin{ctanrefs} \item[enumerate.sty]Distributed as part of \CTANref{2etools} \item[enumitem.sty]\CTANref{enumitem} @@ -12827,9 +13428,13 @@ has to typeset each row several times, so things that leave ``side-effects'' (for example, a counter used to produce a row-number somewhere) are inevitably unreliable, and should not even be tried. -The \Package{ltxtable} combines the features of the -\Package{longtable} and \Package{tabularx} packages: it's important to -read the documentation, since usage is distinctly odd. +The \Package{ltxtable} package combines the features of the +\Package{longtable} and \Package{tabularx} packages. It's important +to read the documentation, since usage is distinctly odd; the +distribution contains no more than a file \File{ltxtable.tex}, which you +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} @@ -12944,9 +13549,9 @@ each row. Its disadvantages are that it's really rather slow in operation (since it gets in the way of everything within tables) and its (lack of) compatibility with other packages. -The \Package{cellspace} does a (possibly inferior) job by defining a -new table/array column type ``S'', which you apply to each column -specification. So, for example, +The \Package{cellspace} package does a (possibly inferior) job by +defining a new table/array column type ``S'', which you apply to each +column specification. So, for example, \begin{quote} \begin{verbatim} \cmdinvoke{begin}{tabular}{l l l p{3cm}} @@ -12993,7 +13598,7 @@ which is slightly tedious to set up, but which doesn't force the whole aligment onto a single page. The \Package{longtable} package builds the whole table (in chunks), in -a first pass, and then uses information it has written to the |.aux| +a first pass, and then uses information it has written to the \extension{aux} file during later passes to get the setting ``right'' (the package ordinarily manages to set tables in just two passes). Since the package has overview of the whole table at the time it's doing @@ -13074,22 +13679,6 @@ 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 simple (old) solution is to preserve the meaning of \texttt{\bsbs }: -\begin{quote} -\begin{verbatim} -\newcommand\PBS[1]{\let\temp=\\% - #1% - \let\\=\temp -} -\end{verbatim} -\end{quote} -which one uses as: -\begin{quote} -\begin{verbatim} -... & \PBS\centering blah ... \\ -\end{verbatim} -\end{quote} -(for example). The technique using \csx{PBS} was developed in the days of \LaTeXo{} because the actual value of \texttt{\bsbs } that the \environment{tabular} @@ -13101,87 +13690,54 @@ explicitly: ... & \centering blah ... \tabularnewline \end{verbatim} \end{quote} -which may be incorporated into a simple macro as: -\begin{quote} -\begin{verbatim} -\newcommand{\RBS}{\let\\=\tabularnewline} -\end{verbatim} -\end{quote} -and used as -\begin{quote} -\begin{verbatim} -... & \centering\RBS blah ... \\ -\end{verbatim} -\end{quote} -(note, you Preserve backslash with \csx{PBS} \emph{before} the command -that changes it, and Restore it with \csx{RBS} \emph{after} the -command; in fact, \csx{RBS} is marginally preferable, but the old -trick lingers on). -The \csx{PBS} and \csx{RBS} tricks also serve well in \Package{array} -package ``field format'' preamble specifications: +The \Package{array} package provides a command \csx{arraybackslash} +which restores \texttt{\bsbs } to its correct (within table) meaning; +the command may be used in \Package{array}'s ``field format'' preamble +specifications: \begin{quote} \begin{narrowversion} \begin{verbatim} -\begin{tabular}{...>{\centering\RBS}% - p{50mm}} +\begin{tabular}{...% + >{\centering\arraybackslash}% + p{50mm}} ... \end{verbatim} \end{narrowversion} \begin{wideversion} \begin{verbatim} -\begin{tabular}{... >{\centering\RBS}p{50mm}} +\begin{tabular}{... >{\centering\arraybackslash}p{50mm}} ... \end{verbatim} \end{wideversion} \end{quote} -or + +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 }: \begin{quote} -\begin{narrowversion} \begin{verbatim} -\begin{tabular}{...>{\PBS\centering}% - p{50mm}} -... +\newcommand\PBS[1]{\let\temp=\\% + #1% + \let\\=\temp +} \end{verbatim} -\end{narrowversion} \end{quote} +which one uses within a table as: \begin{quote} -\begin{wideversion} \begin{verbatim} -\begin{tabular}{... >{\PBS\centering}p{50mm}} -... +... & \PBS\centering blah ... \\ \end{verbatim} -\end{wideversion} \end{quote} -In the \Package{tabularx} and \Package{tabulary} packages, there's a -command \csx{arraybackslash} that has same effect as \csx{RBS} (above); -so in those packages, one might say: +or in the preamble as: \begin{quote} -\begin{narrowversion} \begin{verbatim} -\begin{tabular}{...% - >{\centering\arraybackslash}% - p{50mm}} -... +\begin{tabular}{...>{\PBS\centering}p{5cm}} \end{verbatim} -\end{narrowversion} -\begin{wideversion} -\begin{verbatim} -\begin{tabular}{... >{\centering\arraybackslash}p{50mm}} -... -\end{verbatim} -\end{wideversion} \end{quote} -in place of the example above; in fact, the very latest (2003/12/01) -release of array.sty also provides a \csx{tabularnewline} command, -that has the ``basic tabular/array'' meaning of `\bsbs '. -% note space at end of sentence is necessary for sanitize.pl -The command does rather lack brevity, but at least you don't have to -define it for yourself. \begin{ctanrefs} \item[array.sty]Distributed as part of \CTANref{2etools} -\item[tabularx.sty]Distributed as part of \CTANref{2etools} -\item[tabulary.sty]\CTANref{tabulary} \end{ctanrefs} \nothtml{\vskip 0pt plus 4ex} @@ -13810,6 +14366,64 @@ Note that this is a ``global'' setting (best established in a class file, or at worst in the document preamble); making the change for a single float page is likely (at the least) to be rather tricky. +\Question[Q-figurehere]{Figure (or table) \emph{exactly} where I want it} + +This is of course a contradiction: \environment{figure} and +\environment{table} are \emph{designed} to float, and will always have +the potential to appear away from where you asked for them. Therefore +you have to find a means of getting the caption and other effects +without allowing the figure or table to float. + +The most straightforward way is to use the \Package{float} package; it +gives you a \texttt{[H]} float placement option that prevents +floating: +\begin{quote} +\begin{verbatim} +\begin{figure}[H] + \centering + \includegraphics{foo} + \caption{caption text} + \label{fig:nonfloat} +\end{figure} +\end{verbatim} +\end{quote} +As the example shows, these \texttt{[H]} figures (and correspondingly, +tables) offer all you need to cross-reference as well as typeset. + +However, you don't actually \emph{have} to use \Package{float} since +it is, in fact, doing rather little for you. You can place your +figure as you please, with a sequence like +\begin{quote} +\begin{verbatim} +\begin{center} + \includegraphics{foo} + \captionof{figure}{caption text} + \label{fig:nonfloat} +\end{center} +\end{verbatim} +\end{quote} +which relies on the \csx{captionof} command to place a caption in +ordinary running text. That command may be had from the extremely +simple-minded package \Package{capt-of} or from the highly +sophisticated \Package{caption} package. + +Using either method, you have to deal with the possibility of the +figure or table being too large for the page. (Floating objects will +float away in this circumstance; ``doing it by hand'', like this, you +take upon yourself the responsibility for avoiding % ! line break +`\textit{Overfull \csx{vbox}}' errors. + +A further problem is the possibility that such ``fixed floats'' will +overtake ``real floats'', so that the numbers of figures will be out +of order: figure 6 could be on page 12, while figure 5 had floated to +page 13. It's best, therefore, either to stay with floating figures +throughout a document, or to use fixed figures throughout. +\begin{ctanrefs} +\item[capt-of.sty]\CTANref{capt-of} +\item[caption.sty]\CTANref{caption} +\item[float.sty]\CTANref{float} +\end{ctanrefs} + \subsection{Footnotes} \Question[Q-footintab]{Footnotes in tables} @@ -13878,19 +14492,30 @@ The \csx{footnote} command is fragile, so that simply placing the command in \csx{section}'s arguments isn't satisfactory. Using \csx{protect}\csx{footnote} isn't a good idea either: the arguments of a section command are used in the table of contents and (more -dangerously) potentially also in page headings. Unfortunately, -there's no mechanism to suppress the footnote in the heading while -allowing it in the table of contents, though having footnotes in the -table of contents is probably unsatisfactory anyway. +dangerously) potentially also in page headers. While footnotes will +work in the table of contents, it's generally not thought a ``good +thing'' to have them there; in the page header, footnotes will simply +fail. Whatever the desirability of the matter, there's no mechanism +to suppress the footnote in the page header while allowing it in the table +of contents, so the footnote may only appear in the section heading itself. To suppress the footnote in headings and table of contents: \begin{itemize} \item Take advantage of the fact that the mandatory argument doesn't `move' if the optional argument is present: - |\section[title]{title|\csx{footnote}|{title ftnt}}| + + |\section[title]{title|\cmdinvoke{footnote}{title ftnt}|}| \item Use the \Package{footmisc} package, with package option |stable|~--- this modifies footnotes so that they softly and - silently vanish away if used in a moving argument. + silently vanish away if used in a moving argument. With this, you + simply need: +\begin{verbatim} +% in the document preamble +\usepackage[stable]{footmisc} +... +% in the body of the document +\section{title\footnote{title ftnt}} +\end{verbatim} \end{itemize} \begin{ctanrefs} \item[footmisc.sty]\CTANref{footmisc} @@ -14040,16 +14665,21 @@ The need for more than one series of footnotes is common in critical editions (and other literary criticism), but occasionally arises in other areas. -Of course, the canonical critical edition macros, \Package{edmac}, -offer the facility, as does its \LaTeX{} port, the \Package{ledmac} +Of course, the canonical critical edition package, \Package{edmac}, +offers the facility, as does its \LaTeX{} port, the \Package{ledmac} package. Multiple ranges of footnotes are offered to \LaTeX{} users by the \Package{manyfoot} package. The package provides a fair array of -presentation options, as well. The (rather new) critical editions +presentation options, as well. Another critical edition \Package{ednotes} package is built upon a basis that includes \Package{manyfoot}, as its mechanism for multiple sets of footnotes. + +The \Package{bigfoot} package also uses \Package{manyfoot} as part of +its highly sophisticated structure of footnote facilities, which was +also designed to support typesetting critical editions. \begin{ctanrefs} +\item[bigfoot]\CTANref{bigfoot} \item[edmac]\CTANref{edmac} \item[ednotes]\CTANref{ednotes} \item[ledmac]\CTANref{ledmac} @@ -14089,13 +14719,36 @@ controlling footnote appearance, among them a package option Documentation of \Package{footnpag} comes as a \acro{DVI} file \File{footnpag-user} in the distribution. Documentation of \Package{perpage} appears in the package file, only: however, it -amounts to no more than appears above\dots +amounts to no more than appears above\dots{} \begin{ctanrefs} \item[footmisc.sty]\CTANref{footmisc} \item[footnpag.sty]\CTANref{footnpag} \item[perpage.sty]Distributed as part \CTANref{bigfoot} \end{ctanrefs} +\Question[Q-run-fn-nos]{Not resetting footnote numbers per chapter} + +Some classes (for example, \Class{book} and \Class{report}) set up a +different set of footnotes per chapter, by resetting the footnote +number at the start of the chapter. This is essentially the same +action as that of % ! line break +\Qref*{equation, figure and table numbers}{Q-running-nos}, +except that footnote numbers don't get ``decorated'' with the chapter +number, as happens with those other numbers. + +The solution is the same: use the \Package{chngcntr} package; since the +numbers aren't ``decorated'' you can use the \csx{counterwithout*} +variant; the code: +\begin{quote} +\begin{verbatim} +\counterwithout*{footnote}{chapter} +\end{verbatim} +\end{quote} +is all you need +\begin{ctanrefs} +\item[chngcntr.sty]\CTANref{chngcntr} +\end{ctanrefs} + \subsection{Document management} \Question[Q-filename]{What's the name of this file} @@ -14106,9 +14759,9 @@ footer recording what file is being processed. It's not easy\dots{} \TeX{} retains what it considers the name of the \emph{job}, only, in the primitive \csx{jobname}; this is the name of the file first handed to \TeX{}, stripped of its directory name and of any extension -(such as \texttt{.tex}). If no file was passed (i.e., you're using +(such as \extension{tex}). If no file was passed (i.e., you're using \TeX{} interactively), \csx{jobname} has the value \texttt{texput} -(the name that's given to \texttt{.log} files in this case). +(the name that's given to \extension{log} files in this case). This is fine, for the case of a small document, held in a single file; most significant documents will be held in a bunch of files, and @@ -14181,7 +14834,7 @@ Both examples of patching \csx{input} assume you always use The \Package{FiNK} (``File Name Keeper'') package provides a regular means of keeping track of the current file name (with its extension), in a macro \csx{finkfile}. If you need the unadorned file -name (without its `\texttt{.tex}'), use the commands: +name (without its `\extension{tex}'), use the commands: \begin{quote} \begin{verbatim} \def\striptexext#1.tex{#1} @@ -14229,7 +14882,7 @@ the package is the creation of archival copies of documents, but it has application in document exchange situations too. The \ProgName{bundledoc} system uses the \Package{snapshot} to produce an -archive (e.g., \texttt{.tar.gz} or \texttt{.zip}) of the files needed by your +archive (e.g., \extension{tar.gz} or \extension{zip}) of the files needed by your document; it comes with configuration files for use with \ProgName{teTeX} and \ProgName{\miktex{}}. It's plainly useful when you're sending the first copy of a document. @@ -14258,7 +14911,8 @@ information that \Package{backgrnd} patches their output routine, and will watch its behaviour very carefully (patching the \LaTeX{} output routine is not something to undertake lightly\dots{}). -The longest-established solution is the \Package{changebar} package, +The longest-established \LaTeX{}-specific solution is the +\Package{changebar} package, which uses \csx{special} commands supplied by the driver you're using. You need therefore to tell the package which driver to generate \csx{special}s for (in the same way that you need to tell the @@ -14290,12 +14944,23 @@ convention is to mark a whole changed paragraph. Finally, the \Class{memoir} class allows marginal editorial comments, which you can obviously use to delimit areas of changed text. -Another way to keep track of changes is employed by some -word-processors~--- to produce a document that embodies both ``old'' -and ``new'' versions. The \ProgName{Perl} script \ProgName{latexdiff} -does this for \LaTeX{} documents; you feed it the two documents, and -it produces a new \LaTeX{} document in which the changes are very -visible. An example of the output is embedded in the documentation, +An even more comprehensive way to keep track of changes is employed by +some word-processors~--- to produce a document that embodies both +``old'' and ``new'' versions. + +To this end, he package \Package{changes} allows the user to manually +markup changes of text, such as additions, deletions, or replacements. +Changed text is shown in a different colour; deleted text is crossed +out. The package allows you to define additional authors and their +associated colour; it also allows you to define a markup for authors +or annotations. The documentation (very clearly) demonstrates how the +various functions work. + +The \ProgName{Perl} script \ProgName{latexdiff} may also be used to +generate such markup for \LaTeX{} documents; you feed it the two +documents, and it produces a new \LaTeX{} document in which the +changes are very visible. An example of the output is embedded in the +documentation, \begin{narrowversion} % actually non-hyperversion \File{latexdiff-man.pdf}, in the distribution. \end{narrowversion} @@ -14306,10 +14971,11 @@ visible. An example of the output is embedded in the documentation, A rudimentary revision facility is provided by another \ProgName{Perl} script, \ProgName{latexrevise}, which accepts or rejects all changes. Manual editing of the difference file can be used to -accept or reject selected changes only. +accept or reject selected changes only. \begin{ctanrefs} \item[backgrnd.tex]\CTANref{backgrnd} \item[changebar.sty]\CTANref{changebar} +\item[changes.sty]\CTANref{changes} \item[framed.sty]\CTANref{framed} \item[latexdiff, latexrevise]\CTANref{latexdiff} \item[lineno.sty]\CTANref{lineno} @@ -14352,7 +15018,7 @@ the like) are missing, consider the \LaTeX{} files (rather than \csx{input} them~--- see % line wrap! \Qref[question]{What's going on in my \csx{include} commands?}{Q-include}), \LaTeX{} writes macro traces of what's going on at the end of each -chapter to the \texttt{.aux} file; by using \csx{includeonly}, you can give +chapter to the \extension{aux} file; by using \csx{includeonly}, you can give \LaTeX{} an exhaustive list of the files that are needed. Files that don't get \csx{include}d are skipped entirely, but the document processing continues as if they \emph{were} there, and page, footnote, @@ -14479,13 +15145,14 @@ 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]\CTANref{askinclude} +\item[askinclude.sty]Distributed with Heiko Oberdiek's packages~--- + \CTANref{oberdiek} \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 +\item[pagesel.sty]Distributed with Heiko Oberdiek's packages~--- \CTANref{oberdiek} \item[pdfpages.sty]\CTANref{pdfpages} \item[selectp.sty]\CTANref{selectp} @@ -14585,8 +15252,8 @@ following minimal solution: \begin{wideversion} \begin{verbatim} \def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}} -\RCS$Revision: 1.426 $ % or any RCS keyword -\RCS$Date: 2006/12/18 09:59:16 $ +\RCS$Revision: 1.498 $ % or any RCS keyword +\RCS$Date: 2007/11/05 22:31:23 $ ... \date{Revision \RCSRevision, \RCSDate} \end{verbatim} @@ -14596,8 +15263,8 @@ following minimal solution: \def\RCS$#1: #2 ${\expandafter \def\csname RCS#1\endcsname{#2}% } -\RCS$Revision: 1.426 $ % or any RCS keyword -\RCS$Date: 2006/12/18 09:59:16 $ +\RCS$Revision: 1.498 $ % or any RCS keyword +\RCS$Date: 2007/11/05 22:31:23 $ ... \date{Revision \RCSRevision, \RCSDate} \end{verbatim} @@ -14651,14 +15318,27 @@ For this reason, the only \ProgName{make}-like package on \acro{CTAN} (for a long time) was \ProgName{latexmk}, which is a \ProgName{Perl} script that analyses your \LaTeX{} source for its dependencies, runs \BibTeX{} or \ProgName{makeindex} as and when it notices that those -programs' input (parts of the |.aux| file, or the |.idx| file, -respectively) has changed, and so on. \ProgName{Latexmk} is a fine +programs' input (parts of the \extension{aux} file, or the +\extension{idx} file, respectively) has changed, and so on. +\ProgName{Latexmk} is a fine solution (and was used in generating printable versions of these \acro{FAQ}s for a long time); it has recently been upgraded and has many bells and whistles that allow it to operate as if it were a poor man's \WYSIWYG{} system. -The \Qref*{\Package{texinfo} system}{Q-texinfo} comes with a +Apparently along the same lines, and currently (2007) under active +development, is Auto\LaTeX{}. The \File{README} of the distribution is +actual a Unix-type man-page output, and shows great attention to the +details of the document production process. + +Windows users of the \miktex{} system may use that systems +\ProgName{texify} application. \ProgName{Texify} deals with basic +\LaTeX{} features, including generating a bibliography and an index; +it makes no claim to deal with other things (such as multiple +bibliographies or indexes, or lists of terminology, etc.), which +Auto\LaTeX{} can be configured to process. + +The \Qref*{\Package{texinfo} system}{Q-texinfo} comes with a similar utility called \ProgName{texi2dvi}, which is capable of ``converting'' either \LaTeX{} or \Package{texinfo} files into \acro{DVI} (or into \acro{PDF}, using \PDFTeX{}). @@ -14671,6 +15351,7 @@ The curious may examine the rules employed to run the present \acro{FAQ} through \LaTeX{}: we don't present them as a complete solution, but some of the tricks employed are surely re-usable. \begin{ctanrefs} +\item[\nothtml{\rmfamily}AutoLaTeX]\CTANref{autolatex} \item[\nothtml{\rmfamily}\acro{FAQ} distribution]\CTANref{faq} \item[\nothtml{\rmfamily}latexmake]\CTANref{latexmake} \item[latexmk]\CTANref{latexmk} @@ -14883,11 +15564,11 @@ encodings will `work' with the relevant sets of hyphenation patterns. One might hope that, with the many aspirant successors to \TeX{} such as \begin{wideversion} - \Qref{Omega}{Q-omegaleph}, \Qref{\acro{LUA}\TeX{}}{Q-luatex} and + \Qref{Omega}{Q-omegaleph}, \Qref{\LuaTeX{}}{Q-luatex} and \Qref{Ex\TeX{}}{Q-extex}, \end{wideversion} \begin{narrowversion} - Omega, \acro{LUA}\TeX{} and Ex\TeX{} + Omega, \LuaTeX{} and Ex\TeX{} (\Qref[see questions]{}{Q-omegaleph}\Qref[,]{}{Q-luatex} \Qref[and]{}{Q-extex}), \end{narrowversion} @@ -14944,7 +15625,7 @@ the error should prove little more than an inconvenience (most of the files are in better distributions anyway, but an elusive one may be found on \acro{CTAN}; if you have to retrieve a new file, ensure that it's correctly installed, for which see -\Qref[question]{installing a new package}{Q-instpackages}). +\Qref[question]{installing a new package}{Q-inst-wlcf}). Finally, you need to regenerate the formats used (in fact, most users of Babel are using it in their \LaTeX{} documents, so regenerating the @@ -15074,17 +15755,19 @@ the penalties instead. If you simply switch off hyphenation for a good bit of text, the output will have a jagged edge (with many lines seriously overfull), and your \AllTeX{} run will bombard you with warnings about overfull -and underfull lines. To avoid this you have two options. You may use -\csx{sloppy} (or its environment version \environment{sloppypar}), and -have \TeX{} stretch what would otherwise be underfull lines to fill the space -offered, and wrap other lines, while prematurely wrapping overfull -lines and stretching the remainder. Alternatively, you may set the -text \Qref*{ragged right}{Q-ragright}, and at least get rid of -the overfull lines; this technique is `traditional' (in the sense that -typists do it) and may be expected to appeal to the specifiers of -eccentric document layouts (such as those for dissertations), but for -once their sense conforms with typographic style. (Or at least, style -constrained in this curious way.) +and underfull lines. To avoid this you have two options. + +The simplest route is to use \csx{sloppy} (or its environment version +\environment{sloppypar}), and have \TeX{} stretch what would otherwise +be underfull lines to fill the space offered, while prematurely +wrapping overfull lines and stretching the remainder. + +Alternatively, you may set the text \Qref*{ragged right}{Q-ragright}, +and at least get rid of the overfull lines; this technique is +`traditional' (in the sense that typists do it) and may be expected to +appeal to the specifiers of eccentric document layouts (such as those +for dissertations), but for once their sense conforms with typographic +style. (Or at least, style constrained in this curious way.) \begin{ctanrefs} \item[hyphenat.sty]\CTANref{hyphenat} \end{ctanrefs} @@ -15129,6 +15812,21 @@ each language the word may appear in. So: (note that \Package{babel} will select the default language for the document~--- English, in this case~--- at \cmdinvoke{begin}{document}.) +A particular instance of this requirement is avoiding the hyphenation +of acronyms; a general rule for those that concoct acronyms seems to +be to make the capital-letter sequence read as near as is possible +like a ``real'' word, but hyphenating an acronym often looks silly. +The \TeX{} flag \csx{uchyph} is designed for suppressing such +behaviour: +\begin{quote} +\begin{verbatim} +\uchyph=0 +\end{verbatim} +\end{quote} +will stop hyphenation of upper-case words. (Note that Plain \TeX{} +syntax is needed here: there's no \LaTeX{} alternative for setting +this value.) + \Question[Q-hyphexcept]{Hyphenation exceptions} While \TeX{}'s hyphenation rules are good, they're not infallible: you @@ -15279,10 +15977,10 @@ There's a set of ``extra'' \MF{} files on \acro{CTAN} that provide bold versions of both \texttt{cmtt} and \texttt{cmcsc} (the small caps font). With modern \TeX{} distributions, one may bring these fonts into use simply by placing them in an % ! line break -\Qref*{appropriate place in the \emph{texmf} tree}{Q-wherefiles} +\Qref*{appropriate place in the \emph{texmf} tree}{Q-install-where} (these are \AllTeX{}-specific files, so the ``\emph{public}'' supplier would be an appropriate place). Once you've % ! line break, again -\Qref*{rebuilt the file indexes as necessary}{Q-instpackages}, +\Qref*{rebuilt the file indexes as necessary}{Q-inst-wlcf}, \TeX{} (and friends) will automatically build whatever font files they need when you first make reference to them. There's a jiffy package \Package{bold-extra} that builds the necessary font data structures @@ -15725,8 +16423,8 @@ Outline fonts which contain nothing but Euro symbols are available (free) from \href{ftp://ftp.adobe.com/pub/adobe/type/win/all/eurofont.exe}{Adobe}\nobreakspace--- the file is packaged as a \ProgName{Windows} self-extracting -executable, but it may be decoded as a |.zip| format achive on other -operating systems. +executable, but it may be decoded as a \extension{zip} format achive +on other operating systems. The \Package{euro} bundle contains metrics, \ProgName{dvips} map files, and macros (for Plain \TeX{} and \LaTeX{}), for using these fonts in documents. \LaTeX{} users will find two packages in the @@ -16415,8 +17113,8 @@ files using the \Package{shortvrb} package to define \texttt{\textbar\dots{}\textbar} as a shorthand for \csx{verb}\texttt{\textbar\dots{}\textbar}. But \texttt{\textbar} 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. +\extension{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 % beware linebreak @@ -16749,9 +17447,10 @@ and \cmdinvoke{cmd}{blah}. This is pretty simple: The case where you want to ignore an argument that consists of nothing but spaces, rather than something completely empty, is more tricky. It's solved in the code fragment \Package{ifmtarg}, which defines -commands \csx{@ifmtarg} and \csx{@ifnotmtarg}, which distinguish (in -opposite directions) between a second and third argument. The -package's code also appears in the \LaTeX{} \Class{memoir} class. +commands \csx{@ifmtarg} and \csx{@ifnotmtarg}, which examine their +first argument, and select (in opposite directions) their second or +third argument. The package's code also appears in the \LaTeX{} +\Class{memoir} class. \Package{Ifmtarg} makes challenging reading; there's also a discussion of the issue in number two of the ``around the bend'' articles by the late @@ -17004,7 +17703,7 @@ in new macro packages. \subsection{\LaTeX{} macro tools and techniques} -\Question[Q-plninltx]{Using Plain or primitive commands in \LaTeX{}} +\Question[Q-plninltx*]{Using Plain or primitive commands in \LaTeX{}} It's well-known that \LaTeX{} commands tend to be more complex, and to run more slowly than, any Plain (or primitive) command that they @@ -17039,63 +17738,23 @@ essentially equivalent to the \TeX{} primitive commands: the \LaTeX{} environment when you're already in one, or vice versa). % ! line break However, \csx{[}\texttt{\ ...\ }\csx{]} \emph{isn't} the same as \texttt{\$\$\ ...\ \$\$}: the \TeX{} version, used -in \LaTeX{}, contrives to miss the effect of the class option -\pkgoption{fleqn}. +in \LaTeX{}, can miss the effect of the class option \pkgoption{fleqn}. Font handling is, of course, wildly different in Plain \TeX{} and -\LaTeX{}: even the \LaTeX{} equivalent of the Plain \TeX{} -font-loading command (\csx{newfont}) should be avoided wherever -possible: the possibilities of confusion with constructs that vary -their behaviour according to the font size that \LaTeX{} has recorded -are (sadly) legion. A really rather funny example is to be had by -saying: -\begin{quote} -\begin{verbatim} -\documentclass{article} -\begin{document} -\font \myfont=cmr17 scaled 2000 -\myfont -\LaTeX -\end{document} -\end{verbatim} -\end{quote} -(the reader is encouraged to try this). The ``A'' of \LaTeX{} -has pretty much disappeared: \LaTeX{} sets the ``A'' according to -\emph{its} idea of the font size (10pt), but ``\csx{myfont}'' is more -than three times that size. - -Another ``\csx{myfont}'' example arises from an entirely different -source. The mini-document: -\begin{quote} -\begin{verbatim} -\documentclass{article} -\begin{document} -\font \myfont=ecrm1000 -{\myfont par\`a} -\end{document} -\end{verbatim} -\end{quote} -gives you ``German low double quotes'' in place of the grave accent. -This problem arises because \FontName{ecrm1000} is in a different -\Qref*{font encoding}{Q-whatenc} than \LaTeX{} is expecting~--- if you -use \LaTeX{} font commands, all the tiresome encoding issues are -solved for you, behind the scenes. - -So, whether you're dealing with a one-off font or a major new family, you -are far more likely to be satisfied with the \LaTeX{} file selection -system, so it's worth investing a small amount of effort to write -declarations of the font's family and how it should be loaded. For -details of the commands you need, see the \LaTeX{} font usage guide, -\File{fntguide}: this may be viewed on the archive, but you should -find a copy of the document in your own system. +\LaTeX{}. Plain \TeX{}'s font loading command +(\csx{font}\csx{foo=}\meta{fontname}) and its \LaTeX{} equivalent +(\csx{newfont}) should be avoided wherever possible. They are only +safe in the most trivial contexts, and aer potential sources of great +confusion in many circumstances. Further discussion of this issue +may be found in ``\Qref*{What's wrong with \csx{newfont}?}{Q-newfont*}''. %% %% Consider \csx{vskip} (or Plain \TeX{} users of it like \csx{medskip}) %% \emph{vs}.\nothtml{\@} \csx{vspace} or \csx{vspace*}, but most %% especially \csx{addvspace}. -\begin{ctanrefs} -\item[fntguide.pdf]\CTANref{fntguide.pdf} -\item[fntguide.tex]Distributed with \CTANref{latex} -\end{ctanrefs} +%% \begin{ctanrefs} +%% \item[fntguide.pdf]\CTANref{fntguide.pdf} +%% \item[fntguide.tex]Distributed with \CTANref{latex} +%% \end{ctanrefs} \Question[Q-atsigns]{\csx{@} and \texttt{@} in macro names} @@ -17105,8 +17764,8 @@ example of the problems caused is discussed in % ! beware line break \Qref*{\csx{@} in vertical mode}{Q-atvert}''. The problems users see are caused by copying bits of a class -(\texttt{.cls} file) or -package (\texttt{.sty} file) into a document, or by including a class or +(\extension{cls} file) or +package (\extension{sty} file) into a document, or by including a class or package file into a \LaTeX{} document by some means other than \csx{documentclass} or \csx{usepackage}. \LaTeX{} defines internal commands whose names contain the character \texttt{@} to @@ -17115,15 +17774,17 @@ normally use in our documents. In order that these commands may work at all, \csx{documentclass} and \csx{usepackage} play around with the meaning of \texttt{@}. -If you've included a file wrongly, you solve the problem by using the -correct command. +If you've included a file some other way (for example, using +\csx{input}), you can probablysolve the problem by using the correct +command. If you're using a fragment of a package or class, you may well feel confused: books such as the first edition of the % ! line break \Qref*{The \LaTeX{} Companion}{Q-books} are full of fragments of packages as examples for you to employ. -This problem has been solved in the second edition, and in addition, -all the examples from the \emph{Companion} are now available on-line. +The second edition of the \emph{Companion} makes clearer how you +should use these fragments, and in addition, the code of +all the examples is now available on \acro{CTAN}. To see the technique in practice, look at the example below, from file \File{2-2-7.ltx} in the \emph{Companion} examples directory: \begin{quote} @@ -17141,7 +17802,7 @@ To see the technique in practice, look at the example below, from file second edition.) The alternative is to treat all these fragments as a package proper, -bundling them up into a \texttt{.sty} file and including them with +bundling them up into a \extension{sty} file and including them with \csx{usepackage}; this way you hide your \LaTeX{} internal code somewhere that \LaTeX{} internal code is expected, which often looks `tidier'. \begin{ctanrefs} @@ -17163,28 +17824,43 @@ prominent examples; there's a complete list in Lamport's book %You don't want to care about this stuff? Simply |\protect| all %\LaTeX{} commands within these moving arguments. -What's going on really, behind the scenes? The commands in the moving -arguments are already expanded to their internal structure during the +What's going on really, behind the scenes? The commands in moving +arguments are normally expanded to their internal structure during the process of saving. Sometimes this expansion results in invalid \TeX{} -code when processed again. ``\csx{protect}\csx{cmd}'' tells \LaTeX{} to save -\csx{cmd} as \csx{cmd}, without expansion. +code, which shows either during expansion or when the code is +processed again. Protecting a command, using +``\csx{protect}\csx{cmd}'' tells \LaTeX{} to save \csx{cmd} as +\csx{cmd}, without expanding it at all. -What is a `fragile command'? It's a command that expands into illegal -\TeX{} code during the save process. +So, what is a `fragile command'?~--- it's a command that expands into +illegal \TeX{} code during the save process. -What is a `robust command'? It's a command that expands into legal +What is a `robust command'?~--- it's a command that expands into legal \TeX{} code during the save process. -Again, commands are marked as `robust' or `fragile', as they're -defined in Lamport's book. Sadly, some commands are robust in -\LaTeX{} itself, but are redefined by some packages to be fragile; the -\csx{cite} command commonly suffers this treatment. - -No-one (of course) likes this situation; the \LaTeX{}3 team have -removed the need for protection of some things in the production of -\LaTeXe{}, but the techniques available to them within current -\LaTeX{} mean that this is an expensive exercise. It remains a -long-term aim of the team to remove all need for these things. +Lamport's book says in its description of every LaTeX command whether +it is `robust' or `fragile'; it also says that every command with an +optional argument is fragile. These lists aren't as reliable as the +list of moving arguments; the statements may have been true in +early versions of \LaTeXe{} but are not any longer necessarily so: +\begin{itemize} +\item Some fragile commands, such as \csx{cite}, have been made robust + in later revisions of \LaTeX{}. +\item Some robust commands are redefined by certain packages to be + fragile (the \csx{cite} command commonly suffers this treatment). +\item Some commands, such as \csx{end} and \csx{nocite}, are fragile + even though they have no optional arguments. +\item The ``user's way'' of creating a command with an optional + argument (using \csx{newcommand}) now always creates a robust + command. There is no reason that a package author should not also + make robust commands with optional arguments as part of the + package. +\end{itemize} +In short, the situation is confusing. No-one believes this is +satisfactory, and the \LaTeX{} team have removed the need for +protection of some things, but the techniques available in +current \LaTeX{} mean that this is an expensive exercise. It remains +a long-term aim of the team to remove all need for \csx{protect}ion. \Question[Q-edef]{\csx{edef} does not work with \csx{protect}} @@ -17270,7 +17946,7 @@ is usually to be found, in a \acro{TDS} system, in directory \path{tex/latex/base}). In fact, \File{latex.ltx} is the product of a \ProgName{docstrip} -process on a large number of \Qref*{\texttt{.dtx} files}{Q-dtx}, and +process on a large number of \Qref*{\extension{dtx} files}{Q-dtx}, and you can refer to those instead. The \LaTeX{} distribution includes a file \File{source2e.tex}, and most systems retain it, again in \path{tex/latex/base}. \File{Source2e.tex} may be processed to @@ -17288,14 +17964,14 @@ through modules documented only through an automatic process that converted the documentation of the source of \LaTeXo{}, to modules that hardly had any useful documentation even in the \LaTeXo{} original. -In fact, each kernel module \texttt{.dtx} file will process separately +In fact, each kernel module \extension{dtx} file will process separately through \LaTeX{}, so you don't have to work with the whole of \File{source2e}. You can easily determine which module defines the macro you're interested in: use your ``malleable text editor'' to find the definition in \File{latex.ltx}; then search backwards from that point for a line that starts % ! line break \texttt{\textpercent\textpercent\textpercent\ From File:}~--- that line -tells you which \texttt{.dtx} file contains the definition you are interested +tells you which \extension{dtx} file contains the definition you are interested in. Doing this for \csx{protected@edef}, we find: \begin{quote} \begin{verbatim} @@ -17374,7 +18050,8 @@ invoked, a bug in user code has bitten\dots{} If you've already read % ! line break ``\Qref*[question]{breaking the 9-argument limit}{Q-moren9}''. -you can probably guess the solution to this problem: command relaying. +you can probably guess the ``simple'' solution to this problem: +command relaying. \LaTeX{} allows commands with a single optional argument thus: \begin{verbatim} @@ -17383,8 +18060,8 @@ you can probably guess the solution to this problem: command relaying. You may legally call such a command either with its optional argument present, as -\cmdinvoke{blah}[nonDefault] or as \csx{blah}; in the latter case, the -code of \csx{blah} will have an argument of |Default|. +\cmdinvoke{blah}[nonDefault] or without, as \csx{blah}; in the latter +case, the code of \csx{blah} will have an argument of |Default|. To define a command with two optional arguments, we use the relaying technique, as follows: @@ -17417,22 +18094,39 @@ see the comments on the use of the \Package{keyval} package, in ``\Qref*[question]{breaking the 9-argument limit}{Q-moren9}'', which offers an alternative way forward. -If you must, however, consider the \Package{optparams} package; +If you must, however, consider the \Package{optparams} or +\Package{xargs} packages. \Package{Optparams} provides a \csx{optparams} command that you use as an intermediate in defining commands with up to nine optional arguments. The documentation shows examples of commands with four optional arguments (and this from an author who has his own key-value package!). +The \Package{xargs} package uses a key-value package +(\Package{xkeyval}) to \emph{define} the layout of the optional +arguments. Thus +\begin{quote} +\begin{verbatim} +\usepackage{xargs} +... +\newcommandx{\foo}[3][1=1, 3=n]{...} +\end{verbatim} +\end{quote} +defines a command \csx{foo} that has an optional first argument +(default 1), a mandatory second argument, and an optional third +argument (default n). + An alternative approach is offered by Scott Pakin's \ProgName{newcommand} program, which takes a command name and a definition of a set of command arguments (in a fairly readily-understood language), and emits \AllTeX{} macros which enable the command to be defined. The command requires that a -\ProgName{Python} system be installed on your computer. +\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[xargs.sty]\CTANref{xargs} +\item[xkeyval.sty]\CTANref{xkeyval} \end{ctanrefs} \Question[Q-cmdstar]{Commands defined with * options} @@ -17540,7 +18234,7 @@ definition like: \item[suffix.sty]Distributed as part of \CTANref{bigfoot} \end{ctanrefs} -%\nothtml{\hrule height 0pt \nobreak\vskip0pt plus2.5in\vskip 0pt\relax} +\nothtml{\hrule height 0pt \nobreak\vskip0pt plus2.5in\vskip 0pt\relax} \Question[Q-ltxabbrv]{\LaTeX{} internal ``abbreviations'', etc.} In the deeps of time, when \TeX{} first happened, computers had @@ -17553,7 +18247,7 @@ From the very earliest days, Knuth used shortcut macros to speed things up. \LaTeX{}, over the years, has extended Knuth's list by a substantial amount. An interesting feature of the ``abbreviations'' is that on paper, they may look longer than the thing they stand for; -however, to \AllTeX{} they \emph{feel} smaller\dots +however, to \AllTeX{} they \emph{feel} smaller\dots{} The table at the end of this answer lists the commonest of these ``abbreviations''. It is not complete; as always, if the table @@ -17766,8 +18460,35 @@ number things per chapter; so figures in chapter 1 are numbered 1.1, 1.2, and so on. Sometimes this is not appropriate for the user's needs. -Short of rewriting the whole class, one may use one of the -\Package{removefr} and \Package{remreset} packages; both define a +Short of rewriting the whole class, one may use the \Package{chngctr} +package, which provides commands \csx{counterwithin} (which +establishes this nested numbering relationship) and +\csx{counterwithout} (which undoes it). + +So if you have figures numbered by chapter as 1.1, 1.2, 2.1, \dots{}, +the command +\begin{quote} +\begin{verbatim} +\counterwithout{figure}{chapter} +\end{verbatim} +\end{quote} +will convert them to figures 1, 2, 3, \dots{}. (Note that the command +has also removed the chapter number from the counter's definition.) + +More elaborate use could change things numbered per section to things +numbered per chapter: +\begin{quote} +\begin{verbatim} +\counterwithout{equation}{section} +\counterwithin{equation}{chapter} +\end{verbatim} +\end{quote} +(assuming there was a class that did such a thing in the first place...) + +The \Package{chngcntr} approach doesn't involve much programming, and +the enthusiastic \LaTeX{} programmer might choose to try the technique +that we had to use before the advent of \Package{chngcntr}. Each of +the packages \Package{removefr} and \Package{remreset} defines a \csx{@removefromreset} command, and having included the package one writes something like: \begin{quote} @@ -17789,7 +18510,7 @@ way in which the figure number (in this case) is printed: (remember to do the whole job, for every counter you want to manipulate, within \csx{makeatletter} \dots{}\@ \csx{makeatother}). -The technique may also be used to change where in a multilevel +This technique, too, may be used to change where in a multilevel structure a counter is reset. Suppose your class numbers figures as \meta{chapter}.\meta{section}.\meta{figure}, and you want figures numbered per chapter, try: @@ -17815,11 +18536,6 @@ numbered per chapter, try: \end{narrowversion} \end{quote} (the command \csx{@addtoreset} is a part of \LaTeX{} itself). - -The \Package{chngcntr} package provides a simple means to access the -two sorts of changes discussed, defining \csx{counterwithin} and -\csx{counterwithout} commands; the \Class{memoir} class also provides -these functions. \begin{ctanrefs} \item[chngcntr.sty]\CTANref{chngcntr} \item[memoir.cls]\CTANref{memoir} @@ -18207,6 +18923,109 @@ warnings about labels changing. \item[perpage.sty]Distributed as part \CTANref{bigfoot} \end{ctanrefs} +\Question[Q-fontsize]{Fonts at arbitrary sizes} + +Almost all fonts, nowadays, are provided with \LaTeX{} control +(\extension{fd}) files, so the temptation to risk the +\Qref*{problems of \csx{newfont}}{Q-newfont*} is usually easy to +resist. + +However, one temptation remains, arising from the way that \LaTeX{} +restricts the sizes of fonts. In fact, the restriction only +significantly applies to the default (Computer Modern) and the +Cork-encoded (\acro{T}1) EC fonts, but it is widely considered to be +anomalous, nowadays. In recognition of this problem, there is a +package \Package{fix-cm} which will allow you to use the fonts, within +\LaTeX{}, at any size you choose. If you're not using scaleable +versions of the fonts, most modern distributions will just generate an +appropriate bitmap for you. + +So, suppose you want to use Computer Modern Roman at 30 points, you +might be tempted to write: +\begin{quote} +\begin{verbatim} +\newfont{\bigfont}{cmr10 at 30pt} +\begin{center} + \bigfont Huge text +\end{center} +\end{verbatim} +\end{quote} +which will indeed work, but will actually produce a worse result than +\begin{quote} +\begin{verbatim} +\usepackage{fix-cm} +... +\begin{center} + \fontsize{30}{36}\selectfont + Huge text +\end{center} +\end{verbatim} +\end{quote} +Note that the \Package{fix-cm} package was not distributed until the +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 + version is available at \CTANref{fix-cm}) +\item[type1cm.sty]\CTANref{type1cm} +\item[type1ec.sty]\CTANref{type1ec} (the package is actually part of + the \CTANref{cm-super} distribution, but it works happily in + the absence of the scaled fonts) +\end{ctanrefs} + +\Question[Q-latexqual]{The quality of your \LaTeX{}} + +The \Package{l2tabu} tutorial (mentioned in % ! line break +\Qref[question]{online introductions}{Q-man-latex}) is undoubtedly a +good read. + +However, it's always difficult to remember the things you should +\emph{not} do, when there are so many things to remember that you +really must do: some automation is needed\dots{}. + +The nicely-named \Package{nag} allows you to apply a configurable set +of checks to your document, as you run it through \LaTeX{}; you get +messages like: +\begin{quote} +\begin{wideversion} +\begin{verbatim} +Package nag Warning: Command \bf is an old LaTeX 2.09 command. +(nag) Use \bfseries or \textbf instead on input line 30. +\end{verbatim} +\end{wideversion} +\begin{narrowversion} +\begin{verbatim} +Package nag Warning: Command \bf is an old + LaTeX 2.09 command. +(nag) Use \bfseries or \textbf + instead on input line 30. +\end{verbatim} +\end{narrowversion} +\end{quote} +\begin{wideversion} + (the package provides a demo file which contains most of the sorts + of errors you might make~--- this is one of them). +\end{wideversion} +\begin{narrowversion} + (the two error lines both wrapped above; the package provides a demo + file which contains most of the sorts of errors you might make~--- + this is one of them). +\end{narrowversion} + +There's also a web site +\href{http://www.kohm.name/markus/texidate.html}{TeXidate} +which will do a static analysis of your document (unfortuantely, you +have to paste your document source into a text window). The site +doesn't seem as comprehensive as \Package{nag}, but it allows you to +download its script, which you can then juggle with to make it more +draconian. +\begin{ctanrefs} +\item[l2tabu]Browse \CTANref{l2tabu} for a copy in a language that's + convenient for you +\item[nag.sty]\CTANref{nag} +\end{ctanrefs} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \section{Things are Going Wrong\dots{}} @@ -18335,14 +19154,8 @@ problems (the checklist talks throughout about figures, but applies equally well to tables, or to ``non-standard'' floats defined by the \Package{float} or other packages). \begin{itemize} -\item Do your figures need to float at all? If not, consider the - \texttt{[H]} placement option offered by the \Package{float} package: - figures with this placement are made up to look as if they're - floating, but they don't in fact float. Beware outstanding floats, - though: the \csx{caption} commands are numbered in the order they - appear in the document, and a \texttt{[H]} float can `overtake' a float - that hasn't yet been placed, so that figures numbers get out of - order. +\item Do your figures need to float at all? If not, look at the + recommendations for ``\Qref*{non-floating floats}{Q-figurehere}'' \item Are the placement parameters on your figures right? The default (\texttt{tbp}) is reasonable, but you can reasonably change it (for example, to add an \texttt{h}). Whatever you do, \emph{don't} @@ -18546,7 +19359,7 @@ plague us. There are, of course, still sites that haven't got around to upgrading; but, even if everyone upgraded, there would still be the problem of old documents that specify them. -If you have a \texttt{.tex} source that requests \FontName{msx} and +If you have a \extension{tex} source that requests \FontName{msx} and \FontName{msy}, the best technique is to edit it so that it requests \FontName{msa} and \FontName{msb} (you only need to change the single letter in the font names). @@ -18752,8 +19565,9 @@ necessary?''. \csx{verb} in the first place. \item If you're using \csx{verb} to typeset a \acro{URL} or email address or the like, then the \csx{url} command from the - \Qref{\Package{url} package}{Q-setURL} will help: it doesn't suffer - from the problems of \csx{verb}. + \Package{url} will help: it doesn't suffer from all the problems of + \csx{verb}, though it's still not robust; % ! line break + ''\Qref*{typesetting \acro{URL}s}{Q-setURL}'' offers advice here. \item If you're putting \csx{verb} into the argument of a boxing command (such as \csx{fbox}), consider using the \environment{lrbox} environment: @@ -19246,7 +20060,7 @@ Nevertheless, the facility is retained in current \LaTeX{}, and causes some confusion to those who misunderstand it. In order for \csx{includeonly} to work, \csx{include} makes a separate -\texttt{.aux} file for each included file, and makes a `checkpoint' of +\extension{aux} file for each included file, and makes a `checkpoint' of important parameters (such as page, figure, table and footnote numbers); as a direct result, it \emph{must} clear the current page both before and after the \csx{include} command. What's more, this @@ -19471,7 +20285,7 @@ problem: see The solution to the problem is for \LaTeX{} to `remember' which side of the page each \csx{marginpar} \emph{should} be on. The \Package{mparhack} package does this, using label-like marks stored in -the \texttt{.aux} file; the \Class{memoir} class does likewise. +the \extension{aux} file; the \Class{memoir} class does likewise. \begin{ctanrefs} \item[memoir.cls]\CTANref{memoir} \item[mparhack.sty]\CTANref{mparhack} @@ -20266,60 +21080,54 @@ needs \LaTeX{}'s simplest font selection commands: \item[smallcap.sty]\CTANref{smallcap} \end{ctanrefs} -\Question[Q-newfont]{What's wrong with \csx{newfont}?} +\Question[Q-newfont*]{What's wrong with \csx{newfont}?} If all else fails, you \emph{can} specify a font using the \LaTeX{} \csx{newfont} command. The font so specified doesn't fit into the \LaTeX{} font selection mechanism, but the technique can be tempting under several circumstances. The command is merely the thinnest of -wrappers around the \csx{font} primitive, and suffers from exactly the -problems with font encodings and sizes that are outlined in -\Qref[question]{using Plain \TeX{} commands in \LaTeX}{Q-plninltx}. - -Almost all fonts, nowadays, are provided with \LaTeX{} control files -(if they're adapted to \TeX{} at all). There is therefore little gain -in using \csx{newfont}. - -One temptation arises from the way that \LaTeX{} restricts the sizes -of fonts. In fact, this restriction only significantly applies to the -default (Computer Modern) and the Cork-encoded (\acro{T}1) EC fonts, but it -is widely considered to be anomalous, nowadays. In recognition of -this problem, there is a package \Package{fix-cm} which will allow you -to use the fonts, within \LaTeX{}, at any size you choose. If you're -not using scaleable versions of the fonts, most modern distributions -will just generate an appropriate bitmap for you. - -So, suppose you want to use Computer Modern Roman at 30 points, you -might be tempted to write: +wrappers around the \csx{font} primitive, and doesn't really fit with +\LaTeX{} at all. A simple, but really rather funny, example of the +problems it poses, may be seen in: \begin{quote} \begin{verbatim} -\newfont{\bigfont}{cmr10 at 30pt} -{\bigfont Huge text} +\documentclass[10pt]{article} +\begin{document} +\newfont{\myfont}{cmr17 scaled 2000} +\myfont +\LaTeX +\end{document} \end{verbatim} \end{quote} -which will indeed work, but will actually produce a worse result than +(the reader is encouraged to try this). The ``A'' of \csx{LaTeX} pretty +much disappears: \LaTeX{} chooses the size on the ``A'' according to +\emph{its} idea of the font size (10pt), but positions it according to +the dimensions of ``\csx{myfont}'', which is more than three times +that size. + +Another ``\csx{myfont}'' example arises from an entirely different +source. The mini-document: \begin{quote} \begin{verbatim} -\usepackage{fix-cm} -... -{% - \fontsize{30}{36}\selectfont - Huge text% -} +\documentclass{article} +\begin{document} +\newfont{\myfont}{ecrm1000} +{\myfont voil\`a} +\end{document} \end{verbatim} \end{quote} -Note that the \Package{fix-cm} package was not distributed until the -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 - version is available at \CTANref{fix-cm}) -\item[type1cm.sty]\CTANref{type1cm} -\item[type1ec.sty]\CTANref{type1ec} (the package is actually part of - the \CTANref{cm-super} distribution, but it works happily in - the absence of the scaled fonts) -\end{ctanrefs} +gives you ``German low double quotes'' (under the ``a'') in place of +the grave accent. This happens because \FontName{ecrm1000} is in a +different \Qref*{font encoding}{Q-whatenc} than \LaTeX{} is +expecting~--- if you use the \LaTeX{} \Package{fontenc} package to +select the \acro{EC} fonts, all these tiresome encoding issues are +solved for you, behind the scenes. + +There does however remain a circumstance when you will be tempted to +use \csx{newfont}~--- viz., to get a font size that doesn't fall into +the Knuth standard set of sizes: \LaTeX{} (by default) won't allow you +to use such a size. Don't despair: see the answer % ! line break +``\Qref*{arbitrary font sizes}{Q-fontsize}''. %*****************************************quote environments up to here @@ -20345,7 +21153,7 @@ perplexing) errors that you may encounter. There's a long list of but they often contain a straightforward clue to the problem. See \Qref[question]{the structure of errors}{Q-errstruct} for further details. -\item Read the \texttt{.log} file; it contains hints to things you may +\item Read the \extension{log} file; it contains hints to things you may not understand, often things that have not even presented as error messages. \item Be aware of the amount of context that \TeX{} gives you. The @@ -21036,9 +21844,9 @@ However, as often as not this isn't the problem, and (short of debugging the source of the document before ending) brute force is probably necessary. Excessive force (killing the job that's running \TeX{}) is to be avoided: there may well be evidence in the -|.log| file that will be useful in determining what the problem is~--- -so the aim is to persuade \TeX{} to shut itself down and hence flush -all log output to file. +\extension{log} file that will be useful in determining what the +problem is~--- so the aim is to persuade \TeX{} to shut itself down +and hence flush all log output to file. If you can persuade \TeX{} to read it, an end-of-file indication (control-|D| under Unix, control-|Z| under Windows) will provoke @@ -21055,14 +21863,14 @@ The \LaTeX{} graphics package deals with several different types of \acro{DVI} (or other) output drivers; each one of them has a potential to deal with a different selection of graphics formats. The package therefore has to be told what graphics file types its output driver -knows about; this is usually done in the \meta{driver}|.def| file +knows about; this is usually done in the \meta{driver}\extension{def} file corresponding to the output driver you're using. The error message arises, then, if you have a graphics file whose extension doesn't correspond with one your driver knows about. Most often, this is because you're being optimistic: asking -\ProgName{dvips} to deal with a |.png| file, or \PDFTeX{} to deal with -a |.eps| file: the solution in this case is to transform the graphics +\ProgName{dvips} to deal with a \extension{png} file, or \PDFTeX{} to deal with +a \extension{eps} file: the solution in this case is to transform the graphics file to a format your driver knows about. If you happen to \emph{know} that your device driver deals with the @@ -21070,8 +21878,31 @@ format of your file, you are probably falling foul of a limitation of the file name parsing code that the graphics package uses. Suppose you want to include a graphics file \File{home.bedroom.eps} using the \ProgName{dvips} driver; the package will conclude that your file's -extension is \File{.bedroom.eps}, and will complain. To get around -this limitation, you have three alternatives: +extension is \extension{bedroom.eps}, and will complain. + +The \Package{grffile} package deals with the last problem (and +others~--- see the package documentation); using the package, you may +write: +\begin{quote} +\begin{verbatim} +\usepackage{graphicx} +\usepackage{grffile} +... +\includegraphics{home.bedroom.eps} +\end{verbatim} +\end{quote} +or you may even write +\begin{quote} +\begin{verbatim} +\includegraphics{home.bedroom} +\end{verbatim} +\end{quote} +and \Package{graphicx} will find a \extension{eps} or \extension{pdf} +(or whatever) version, according to what version of \AllTeX{} you're +running. + +If for some reason you can't use \Package{grffile}, you have three +unsatisfactory alternatives: \begin{itemize} \item Rename the file~--- for example \File{home.bedroom.eps}\arrowhyph{}% \File{home-bedroom.eps} @@ -21082,26 +21913,21 @@ this limitation, you have three alternatives: \end{verbatim} \item Tell the graphics package what the file is, by means of options to the \csx{includegraphics} command: -\htmlignore -\begin{pdfversion} -\begin{verbatim} -\includegraphics[type=eps,ext=.eps,read=.eps]{home.bedroom} -\end{verbatim} -\end{pdfversion} -\begin{dviversion} +\begin{narrowversion} \begin{verbatim} -\includegraphics - [type=eps,ext=.eps,read=.eps]% - {home.bedroom} +\includegraphics[type=eps,ext=.eps, + read=.eps]{home.bedroom} \end{verbatim} -\end{dviversion} -\endhtmlignore -\begin{htmlversion} +\end{narrowversion} +\begin{wideversion} \begin{verbatim} \includegraphics[type=eps,ext=.eps,read=.eps]{home.bedroom} \end{verbatim} -\end{htmlversion} +\end{wideversion} \end{itemize} +\begin{ctanrefs} +\item[grffile.sty]Distributed as part of the \CTANref{oberdiek} collection +\end{ctanrefs} \Question[Q-nodollar]{``Missing \texttt{\$} inserted''} @@ -21320,7 +22146,7 @@ than a given length; so the solution is just to edit the file. If the problem is a ridiculous preview section, try using \ProgName{ghostscript} to reprocess the file, outputting a ``plain -\texttt{.eps}'' file. (\ProgName{Ghostscript} is distributed with a script +\extension{eps}'' file. (\ProgName{Ghostscript} is distributed with a script \ProgName{ps2epsi} which will regenerate the preview if necessary.) Users of the shareware program \ProgName{GSview} will find buttons to perform the required transformation of the file being displayed. @@ -21409,13 +22235,13 @@ system recognise which driver is needed. \Question[Q-8000]{Mismatched mode ljfour and resolution 8000} -You're running \ProgName|dvips|, and you encounter a stream of error +You're running \ProgName{dvips}, and you encounter a stream of error messages, starting with ``\texttt{Mismatched mode}''. The mode is the default used in your installation~--- it's set in the \ProgName{dvips} configuration file, and \texttt{ljfour} is commonest (since it's the default in most distributions), but not invariable. -The problem is that \ProgName|dvips| has encountered a font for which +The problem is that \ProgName{dvips} has encountered a font for which 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 \MF{}. @@ -21549,15 +22375,46 @@ package interaction. Some packages are simply incompatible with \Package{hyperref}, but most work simply by ignoring it. In most cases, therefore, you should load your package before you load \Package{hyperref}, and \Package{hyperref} will patch things up so -that they work: +that they work, so you can utilise your (patched) package \emph{after} +loading both: \begin{quote} \cmdinvoke{usepackage}{\emph{your package}}\\ - \dots{}\\ - \cmdinvoke{usepackage}[\emph{opts}]{hyperref} + \texttt{...}\\ + \cmdinvoke{usepackage}[\emph{opts}]{hyperref}\\ + \texttt{...}\\ + \meta{code that uses your package} +\end{quote} +\begin{wideversion} +For example: +\begin{quote} +\begin{verbatim} +\usepackage{float} % defines \newfloat +... +\usepackage[...]{hyperref} % patches \newfloat +... +\newfloat{...}{...}{...} +\end{verbatim} \end{quote} -You should do this as a matter of course, unless the documentation of -a package says you \emph{must} load it after \Package{hyperref}. -(There aren't many such packages: one such is \Class{memoir}'s +\end{wideversion} +\begin{narrowversion} +So, if we need \csx{newfloat}: +\begin{quote} +\cmdinvoke{usepackage}{float} +\end{quote} +will define the command, +\begin{quote} +\cmdinvoke{usepackage}[\emph{opts}]{hyperref} +\end{quote} +will patch it, and now: +\begin{quote} +\cmdinvoke{newfloat}{...}{...}{...} +\end{quote} +will use the command, patched to create `proper' hyperreferences. +\end{narrowversion} +You should load packages in this order as a matter of course, unless +the documentation of a package says you \emph{must} load it after +\Package{hyperref}. (There aren't many packages that require to be +loaded after hyperref: one such is \Class{memoir}'s ``\Package{hyperref} fixup'' package \Package{memhfixc}.) If loading your packages in the (seemingly) ``correct'' order doesn't @@ -21591,10 +22448,32 @@ could arise from a simple typo, such as: \end{tabular} \end{verbatim} \end{quote} -where the second |&| in the first line of the table is more than the -two-column \texttt{ll} column specification can cope with~--- an extra -``\texttt{l}'' in that solves the problem. (As a result of the error, -``\texttt{jim}'' will be moved to a row of his own.) +where the second \texttt{\&} in the first line of the table is more than the +two-column \texttt{ll} column specification can cope with. In this +case, an extra ``\texttt{l}'' in that solves the problem. (If you +continue from the error in this case, ``\texttt{jim}'' will be moved +to a row of his own.) Another simple typo that can provoke the error +is: +\begin{quote} +\begin{verbatim} +\begin{tabular}{ll} + hello & there + goodbye & now +\end{tabular} +\end{verbatim} +\end{quote} +where the `\bsbs' has been missed from the first line of the table. +In this case, if you continue from the error, you will find that +\LaTeX{} has made a table equivalent to: +\begin{quote} +\begin{verbatim} +\begin{tabular}{ll} + hello & there goodbye\\ + now +\end{tabular} +\end{verbatim} +\end{quote} +(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 ``\texttt{p}'' column: @@ -21702,7 +22581,7 @@ this error, quite correctly. \LaTeX{} \emph{needs} that finish off the document preamble. Other than that, the error can occur as a result of an error of yours, -of a corrupt \texttt{.aux} file, or of a buggy class or package. +of a corrupt \extension{aux} file, or of a buggy class or package. The errors you might commit are absent-mindedly typing a document command (such as \csx{section}) in the preamble of your document, @@ -21710,7 +22589,7 @@ missing the comment marker from the beginning of a line, or giving too many arguments to one of the setup commands related to the class or a package that you have loaded. -A corrupt \texttt{.aux} file might be due to any number of things; +A corrupt \extension{aux} file might be due to any number of things; delete the file and to run \LaTeX{} again, twice. If the error recurs, it's probably due to a buggy class or package. @@ -21876,6 +22755,55 @@ actually means what it says: \end{quote} produces the error, and is plainly in need of an \csx{item} command. +You can also have the error appear when at first sight things are +correct: +\begin{quote} +\begin{verbatim} +\begin{tabular}{l} + \begin{enumerate} + \item foo\\ + \item bar + \end{enumerate} +\end{tabular} +\end{verbatim} +\end{quote} +produces the error at the \bsbs{}. This usage is just wrong; if you +want to number the cells in a table, you have to do it ``by hand'': +\begin{quote} +\begin{verbatim} +\newcounter{tablecell} +\begin{tabular}{l} + \stepcounter{tablecell} + \thetablecell. foo\\ + \stepcounter{tablecell} + \thetablecell. bar + \end{enumerate} +\end{tabular} +\end{verbatim} +\end{quote} +This is obviously untidy; a command \csx{numbercell} defined as: +\begin{quote} +\begin{verbatim} +\newcounter{tablecell} +\newcommand*{\numbercell}{% + \stepcounter{tablecell}% + \thetablecell. % ** +} +\end{verbatim} +\end{quote} +could make life easier: +\begin{quote} +\begin{verbatim} +\begin{tabular}{l} + \numbercell foo\\ + \numbercell bar + \end{enumerate} +\end{tabular} +\end{verbatim} +\end{quote} +(Note the deliberate introduction of a space as part of the command, +marked with asterisks.) + However, the error regularly appears when you would never have thought that a \csx{item} command might be appropriate. For example, the seemingly innocent: @@ -22069,9 +22997,9 @@ will contain something like: \end{verbatim} \end{quote} (the parentheses for \Package{graphics} are completely enclosed in -those for \Package{foo}; the same is of course true if \Class{bar} is -the culprit, except that the line will start with the path to -\texttt{bar.cls}). +those for \Package{foo}; the same is of course true if your class +\Class{bar} is the culprit, except that the line will start with the +path to \texttt{bar.cls}). If we're dealing with a package that loads the package you are interested in, you need to ask \LaTeX{} to slip in options when @@ -22124,20 +23052,117 @@ In such a case, you have to modify the package or class itself (subject to the terms of its licence). It may prove useful to contact the author: she may have a useful alternative to suggest. +\Question[Q-checksum]{Checksum mismatch in font} + +When \MF{} generates a font it includes a checksum in the font bitmap +file, and in the font metrics file (\acro{TFM}). \AllTeX{} includes +the checksum from the \acro{TFM} file in the \acro{DVI} file. + +When \ProgName{dvips} (or other \acro{DVI} drivers) process a +\acro{DVI} file, they compare checksums in the \acro{DVI} file to +those in the bitmap fonts being used for character images. If the +checksums don't match, it means the font metric file used by \AllTeX{} +was not generated from the same \MF{} program that generated the +font. + +This commonly occurs when you're processing someone else's \acro{DVI} +file. + +The fonts on your system may also be at fault: possibilities are that +the new \acro{TFM} was not installed, or installed in a path after an +old \acro{TFM} file, or that you have a personal cache of bitmaps from +an old version of the font. + +In any case, look at the output -- the chances are that it's perfectly +\acro{OK}, since metrics tend not to change, even when the bitmaps are +improved. (Indeed, many font designers~--- Knuth included~--- +maintain the metrics come what may.) + +If the output \emph{does} look bad, your only chance is to regenerate +things from scratch. Options include: flushing your bitmap cache, +rebuild the \acro{TFM} file locally, and so on. + +\Question[Q-entercompmode]{Entering compatibility mode} + +You run your \LaTeX{} job, and it starts by saying +\begin{quote} +\begin{verbatim} +Entering LaTeX 2.09 COMPATIBILITY MODE +\end{verbatim} +\end{quote} +followed by lines of asterisks and \texttt{!!WARNING!!}. + +This means that the document is not written in ``current'' \LaTeX{} +syntax, and that there is no guarantee that all parts of the document +will be formatted correctly. + +If the document is someone else's, and you want no more than a copy to +read, ignore the error. The document may fail elsewhere, but as often +as not it will provide a \extension{dvi} or \extension{pdf} that's +adequate for most purposes. + +If it's a new document you have just started working on, you have been +misled by someone. You have written something like: +\begin{quote} + \cmdinvoke{documentstyle}{article} +\end{quote} +or, more generally: +\begin{quote} + \cmdinvoke*{documentstyle}[options]{class} +\end{quote} +These forms are (as the warning says) \LaTeXo{} syntax, and to get rid +of the warning, you must change the command. + +The simple form is easy to deal with: +\begin{quote} + \cmdinvoke{documentstyle}{article} +\end{quote} +should become: +\begin{quote} + \cmdinvoke{documentclass}{article} +\end{quote} +The complex form is more difficult, since \LaTeXo{} ``options'' +conflate two sorts of things~--- options for the class (such as +\pkgoption{11pt}, \pkgoption{fleqn}), and packages to be loaded. +So: +\begin{quote} + \cmdinvoke{documentstyle}[11pt,verbatim]{article} +\end{quote} +should become: +\begin{quote} + \cmdinvoke{documentclass}[11pt]{article}\\ + \cmdinvoke{usepackage}{verbatim} +\end{quote} +because \pkgoption{11pt} happens to be a class option, while +\Package{verbatim} is a package. + +There's no simple way to work out what are class options under +\LaTeXo{}; for \Class{article}, the list includes \pkgoption{10pt}, +\pkgoption{11pt}, \pkgoption{12pt}, \pkgoption{draft}, +\pkgoption{fleqn}, \pkgoption{leqno}, \pkgoption{twocolumn} and +\pkgoption{twoside}~--- anything else must be a package. + +Your document may well ``just work'' after changes like those above; +if not, you should think through what you're trying to do, and consult +documentation on how to do it~--- there are lots of % ! line break +\Qref*{free tutorials}{Q-tutorials*} to help you on your way, if you +don't have access to a \LaTeX{} manual of any sort. + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \section{Current \TeX{}-related projects} -\Question[Q-LaTeX3]{The \LaTeX{}3 project} +\Question[Q-LaTeX3]{The \LaTeX{} project} -The \LaTeX{}3 project team (see \URL{http://www.latex-project.org/latex3.html}) +The \LaTeX{} project team (see \URL{http://www.latex-project.org/latex3.html}) is a small group of volunteers whose aim is to produce a major new document processing system based on the -principles pioneered by Leslie Lamport in the current \LaTeX{}. It +principles pioneered by Leslie Lamport in the current \LaTeX{}. The +new system is (provisionally) called \LaTeX{}3; it will remain freely available and it will be fully documented at all levels. -The \LaTeX{}3 team's first product (\LaTeXe{}) was delivered in 1994 +The \LaTeX{} team's first product (\LaTeXe{}) was delivered in 1994 (it's now properly called ``\LaTeX{}'', since no other version is current). \LaTeXe{} was intended as a consolidation exercise, unifying several @@ -22491,9 +23516,9 @@ as use of advanced OpenType fonts) can be added in a relatively straightforward fashion. The work done in the Aleph project is also being carried forward in -the \Qref*{\acro{LUA}\TeX{}}{Q-luatex} project. +the \Qref*{\LuaTeX{}}{Q-luatex} project. -\Question[Q-luatex]{\PDFTeX{} becomes \acro{LUA}\TeX{}} +\Question[Q-luatex]{\PDFTeX{} becomes \LuaTeX{}} As is said elsewhere in these \acro{FAQ}s, development of \Qref*{\PDFTeX{}}{Q-whatpdftex} is ``in essence'' complete~--- @@ -22501,34 +23526,83 @@ development of new facilities continues, but the limitations of the present structure impose a strong limit on what facilities are possible. -Thus arose the idea of \acro{LUA}\TeX{}. \acro{LUA} is a script -language, chosen because its interpreter has a very small +In this context, the idea of \LuaTeX{} arose. +\href{http://www.lua.org/}{\ProgName{Lua}} is a script +language, designed to offer an interpreter with a very small ``footprint'', so it is rather easy to build it into other -applications. So \acro{LUA}\TeX{} was launched as a \PDFTeX{} -executable with a \acro{LUA} interpreter built into it. +applications. So \LuaTeX{} was launched as a \PDFTeX{} +executable with a \ProgName{Lua} interpreter built into it. -The \acro{LUA}\TeX{} project is now proceeding (with monetary support -from various sources) and is pursuing avenues that many of the other +A \href{http://www.luatex.org/}{\LuaTeX{} project} is now proceeding +(with monetary support from various sources) and is pursuing avenues +that many of the other current projects have in their sights, notably Unicode character representations and support for OpenType fonts. Work is also in hand to integrate the extensions pioneered by \Qref*{Aleph}{Q-omegaleph}. -\Question[Q-xetex]{The XeTeX project} +\Question[Q-xetex]{The \xetex{} project} -XeTeX (by Jonathan Kew) is a successor to the shareware \TeX{}/\acro{GX} -program. It is a Unicode-based (\acro{UTF}-8) TeX implementation which -is able to make use of Mac~\acro{OS}~X \acro{AAT} (Apple Advanced Typography) -\texttt{.dfonts} and OpenType fonts. It uses Apple's Quartz system -(which facilitates the afore-mentioned font access) to generate -\acro{PDF} output. +\xetex{} (by Jonathan Kew) is a successor to the shareware \TeX{}/\acro{GX} +program for Macintoshes. It is a Unicode-based (\acro{UTF}-8) TeX +implementation which is able to make use of Mac~\acro{OS}~X \acro{AAT} +(Apple Advanced Typography) \extension{dfonts} and OpenType fonts. It +uses Apple's Quartz system (which facilitates the afore-mentioned font +access) to generate \acro{PDF} output. \xetex{} supports Unicode +character sets and bidirectional typesetting, and is widely used by +people studying linguistics, as well as an increasing range of people +working in other fields. -A Linux version has been announced (2006); that version of course -can't use \acro{AAT} fonts, and relies on OpenType fonts alone. +A Linux and Unix-system version is available in \texlive{}~2007; that +version (of course) relies on OpenType fonts alone. A version is +planned for \miktex{} version 2.7 (currently planned for December 2007). The project has a \href{http://scripts.sil.org/xetex}{web site} for the user who wants more than this simple answer, and you can also sign up to a \href{http://www.tug.org/mailman/listinfo/xetex}{mailing list}. +\Question[Q-biblatex]{Replacing the \BibTeX{}--\LaTeX{} mechanism} + +Producing a successor to \BibTeX{} has long been a favoured activity +among a certain class of \TeX{}-users; the author has seen many +reports of progress (on many projects), over the years, yet few +announcements of packages we can use. (There are probably usable +packages out there, but none that I know of.) + +Two interesting approaches, that the author has investigated, are +\Package{amsrefs} and \Package{biblatex}. \Package{Amsrefs} does away +with \BibTeX{} altogether, while \Package{biblatex} makes rather +limited use of \BibTeX{}. Both are heavily dependent on \LaTeX{}'s +support. + +\Package{Amsrefs} uses a transformed \extension{bib} file, which is +expressed as \LaTeX{} macros. (The package provides a \BibTeX{} style +that performs the transformation, so that a \LaTeX{} source containing +a \cmdinvoke{nocite}{*} command enables \BibTeX{} to produce a usable +\Package{amsrefs} bibliography database.) + +\Package{Amsrefs} is maintained by the AMS as part of its author +support programme, + +\Package{Biblatex} uses \BibTeX{} more-or-less as normal, but with +\Package{biblatex}'s own style; the style of citations and of the +bibliography itself is determined by the way your \Package{biblatex} +style has been set up. This structure eliminates the collections of +\BibTeX{} styles, at a stroke; the package comes with a basic set of +styles, and details are determined by options, set at package loading +time. The author, Philipp Lehman, evaluated the whole field of +bibliography software before starting, and as a result the package +comes with answers to many of the questions asked in the bibliography +sections of these \acro{FAQ}s. + +\Package{Biblatex} is released as experimental software, but it's +clear that many users are already using it happily; Lehman is +responsive to problem reports, at the moment, but a set of expert +users is already establishing itself. +\begin{ctanrefs} +\item[amsrefs.sty]\CTANref{amsrefs} +\item[biblatex.sty]\CTANref{biblatex} +\end{ctanrefs} + %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % @@ -22630,7 +23704,7 @@ should run it in a clean directory, on a system with no contributed packages, it should replicate your problem. \nothtml{\noindent}\textbf{4.} Run your file through \LaTeX{}: the bug -system needs the |.log| file that this process creates. +system needs the \extension{log} file that this process creates. You now have two possible ways to proceed: either create a mail report to send to the bug processing mechanism (5, below), or submit your bug @@ -22706,7 +23780,7 @@ If you've found a bug in \LaTeXo{}, or some other such unsupported software, you may find help or \emph{de facto} support on a newsgroup such as \Newsgroup{comp.tex.tex} or on a mailing list such as -\mailto{texhax@tug.org}; be carefule to include a % ! line wrap +\mailto{texhax@tug.org}; be careful to include a % ! line wrap \Qref*{code example}{Q-minxampl} of the failure, if relevant. diff --git a/Master/texmf-doc/doc/english/FAQ-en/filectan.tex b/Master/texmf-doc/doc/english/FAQ-en/filectan.tex index 951bdeb602f..93dbaa7f3d3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/filectan.tex +++ b/Master/texmf-doc/doc/english/FAQ-en/filectan.tex @@ -15,11 +15,11 @@ \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} -\CTANfile{askinclude}{macros/latex/contrib/misc/askinclude.sty} \CTANfile{backgrnd}{macros/generic/misc/backgrnd.tex} \CTANfile{bbl2html}{biblio/bibtex/utils/misc/bbl2html.awk} \CTANfile{beginlatex-pdf}{info/beginlatex/beginlatex-3.6.pdf} \CTANfile{belleek}{fonts/belleek/belleek.zip} +\CTANfile{bibtex-faq}{biblio/bibtex/contrib/doc/btxFAQ.pdf} \CTANfile{bidstobibtex}{biblio/bibtex/utils/bids/bids.to.bibtex} \CTANfile{bold-extra}{macros/latex/contrib/misc/bold-extra.sty} \CTANfile{braket}{macros/latex/contrib/misc/braket.sty} @@ -27,6 +27,7 @@ \CTANfile{cancel}{macros/latex/contrib/misc/cancel.sty} \CTANfile{capt-of}{macros/latex/contrib/misc/capt-of.sty} \CTANfile{catalogue}{help/Catalogue/catalogue.html} +\CTANfile{cat-licences}{help/Catalogue/licenses.html} \CTANfile{chngcntr}{macros/latex/contrib/misc/chngcntr.sty} \CTANfile{chngpage}{macros/latex/contrib/misc/chngpage.sty} \CTANfile{clsguide}{macros/latex/doc/clsguide.pdf} @@ -39,7 +40,6 @@ \CTANfile{epslatex_pdf}{info/epslatex/english/epslatex.pdf} \CTANfile{epslatex_ps}{info/epslatex/english/epslatex.ps} \CTANfile{eucal}{fonts/amsfonts/latex/eucal.sty} -\CTANfile{excel2latex}{support/excel2latex/xl2latex.zip} \CTANfile{excludeonly}{macros/latex/contrib/misc/excludeonly.sty} \CTANfile{figsinlatex}{info/figsinltx.ps} \CTANfile{finplain}{biblio/bibtex/contrib/misc/finplain.bst} @@ -74,6 +74,7 @@ \CTANfile{mf-list}{info/metafont-list} \CTANfile{miktex-setup}{systems/win32/miktex/setup/setup.exe} \CTANfile{mil}{info/mil/mil.pdf} +\CTANfile{mil-short}{info/Math_into_LaTeX-4/Short_Course.pdf} \CTANfile{modes-file}{fonts/modes/modes.mf} \CTANfile{morefloats}{macros/latex/contrib/misc/morefloats.sty} \CTANfile{mpsproof}{graphics/metapost/contrib/misc/mpsproof.tex} @@ -96,7 +97,7 @@ \CTANfile{picins-summary}{macros/latex209/contrib/picins/picins.txt} \CTANfile{pk300}{fonts/cm/pk/pk300.zip} \CTANfile{pk300w}{fonts/cm/pk/pk300w.zip} -\CTANfile{protext}{systems/texlive/Images/protext.exe} +\CTANfile{printlen}{macros/latex/contrib/misc/printlen.sty} \CTANfile{removefr}{macros/latex/contrib/fragments/removefr.tex} \CTANfile{resume}{obsolete/macros/latex209/contrib/resume/resume.sty} \CTANfile{savesym}{macros/latex/contrib/savesym/savesym.sty} @@ -125,7 +126,6 @@ \CTANfile{ulem}{macros/latex/contrib/misc/ulem.sty} \CTANfile{url}{macros/latex/contrib/misc/url.sty} \CTANfile{underscore}{macros/latex/contrib/misc/underscore.sty} -\CTANfile{unixtexftp}{systems/unix/unixtex.ftp} \CTANfile{varwidth}{macros/latex/contrib/misc/varwidth.sty} \CTANfile{verbdef}{macros/latex/contrib/misc/verbdef.sty} \CTANfile{version}{macros/latex/contrib/misc/version.sty} diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2colfloat.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2colfloat.html index 561d265a260..79fddff663a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2colfloat.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2colfloat.html @@ -2,26 +2,26 @@ <title>UK TeX FAQ -- question label 2colfloat</title> </head><body> <h3>Placing two-column floats at bottom of page</h3> -<p>You specified placement ‘<code>[htbp]</code>’ for your full-width figure or +<p/>You specified placement ‘<code>[htbp]</code>’ for your full-width figure or table, but they always get placed at the top of the page... Well, it <em>is</em> what the documentation says: LaTeX, unadorned, only allows full-width floats at the top of a page, or occupying (part of) a float page. -<p>The <i>stfloats</i> package ameliorates the situation somewhat, and +<p/>The <i>stfloats</i> package ameliorates the situation somewhat, and makes LaTeX honour ‘[b]’ placement as well; the <i>dblfloatfix</i> package combines a tidied version of the changes made in <i>stfloats</i> with the <a href="FAQ-2colfltorder.html">float ordering corrections</a> defined in <i>fixltx2e</i>. -<p>A particular problem with <i>stfloats</i> and <i>dblfloatfix</i> +<p/>A particular problem with <i>stfloats</i> and <i>dblfloatfix</i> 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 <i>dblfloatfix</i> that ensures that the early-specified bottom float is set <em>before</em> any single column floats). -<p>(The FAQ team doesn’t know of any package that will make +<p/>(The FAQ team doesn’t know of any package that will make LaTeX honour ‘[h]’ placement of double-column floats, but the <i>midfloat</i> package can be pressed into service to provide something approximating the effect it would have.) @@ -30,5 +30,5 @@ something approximating the effect it would have.) <dt><tt><i>stfloats.sty, midfloat.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sttools.zip">macros/latex/contrib/sttools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sttools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfloat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfloat</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfloat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfloat</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2colfltorder.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2colfltorder.html index 5b9e631bc38..a16ff8fe4dc 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2colfltorder.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2colfltorder.html @@ -2,25 +2,25 @@ <title>UK TeX FAQ -- question label 2colfltorder</title> </head><body> <h3>Two-column float numbers out of order</h3> -<p>When LaTeX can’t place a float immediately, it places it on one of +<p/>When LaTeX can’t place a float immediately, it places it on one of several “defer” lists. If another float of the same type comes along, and the “defer” list for that type still has something in it, the later float has to wait for everything earlier in the list. -<p>Now, standard LaTeX has different lists for single-column floats, +<p/>Now, standard LaTeX has different lists for single-column floats, and double-column floats; this means that single-column figures can overtake double-column figures (or vice-versa), and you observe later figures appear in the document before early ones. The same is true, of course, for tables, or for any user-defined float. -<p>The LaTeX team recognise the problem, and provides a package +<p/>The LaTeX team recognise the problem, and provides a package (<i>fixltx2e</i>) to deal with it. <i>Fixltx2e</i> amalgamates the two defer lists, so that floats don’t get out of order. -<p>For those who are still running an older LaTeX distribution, the +<p/>For those who are still running an older LaTeX distribution, the package <i>fix2col</i> should serve. This package (also by a member of the LaTeX team) was the basis of the relevant part of <i>fixltx2e</i>. The functionality has also been included in <i>dblfloatfix</i>, which also has code to place full-width floats at <a href="FAQ-2colfloat.html"><code>[b]</code> placement</a>. -<p>Once you have loaded the package, no more remains to be done: the +<p/>Once you have loaded the package, no more remains to be done: the whole requirement is to patch the output routine; no extra commands are needed. <dl> @@ -28,5 +28,5 @@ are needed. <dt><tt><i>fix2col.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>) <dt><tt><i>fixltx2e.sty</i></tt><dd>Part of the LaTeX distribution </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfltorder">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfltorder</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfltorder">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2colfltorder</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2letterfontcmd.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2letterfontcmd.html index 3a5c3f40841..c87a5c088e6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2letterfontcmd.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-2letterfontcmd.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label 2letterfontcmd</title> </head><body> <h3>What’s wrong with <code>\</code><code>bf</code>, <code>\</code><code>it</code>, etc.?</h3> -<p>The font-selection commands of LaTeX 2.09 were <code>\</code><code>rm</code>, <code>\</code><code>sf</code>, +<p/>The font-selection commands of LaTeX 2.09 were <code>\</code><code>rm</code>, <code>\</code><code>sf</code>, <code>\</code><code>tt</code>, <code>\</code><code>it</code>, <code>\</code><code>sl</code>, <code>\</code><code>em</code> and <code>\</code><code>bf</code>; they were modal commands, so you used them as: <blockquote> @@ -13,7 +13,7 @@ commands, so you used them as: with the font change enclosed in a group, so as to limit its effect; note the italic correction command <code>\</code><code>/</code> that was necessary at the end of a section in italics. -<p>At the release of LaTeX2e in summer 1994, these simple commands were +<p/>At the release of LaTeX2e in summer 1994, these simple commands were deprecated, but recognising that their use is deeply embedded in the brains of LaTeX users, the commands themselves remain in LaTeX, <em>with their LaTeX 2.09 semantics</em>. Those semantics were part of @@ -41,10 +41,10 @@ LaTeX2e font selections with the old style commands: </blockquote><p> ignores the <code>\</code><code>textbf</code> that encloses the text, and produces typewriter text at medium weight. -<p>So why are these commands deprecated? — it is because of confusions +<p/>So why are these commands deprecated? — it is because of confusions such as that in the last example. The alternative (LaTeX2e) commands are discussed in the rest of this answer. -<p>LaTeX2e’s font commands come in two forms: modal commands and +<p/>LaTeX2e’s font commands come in two forms: modal commands and text-block commands. The default set of modal commands offers weights <code>\</code><code>mdseries</code> and <code>\</code><code>bfseries</code>, shapes <code>\</code><code>upshape</code>, <code>\</code><code>itshape</code>, <code>\</code><code>scshape</code> and <code>\</code><code>slshape</code>, and families @@ -68,7 +68,7 @@ in the default Computer Modern fonts), or </pre> </blockquote><p> (note the italic correction needed on slanted fonts, too). -<p>LaTeX2e’s text block commands take the first two letters of the +<p/>LaTeX2e’s text block commands take the first two letters of the modal commands, and form a <code>\</code><code>text</code><em><code>xx</em></code> command from them. Thus <code>\</code><code>bfseries</code> becomes <code>\</code><code>textbf{</code><em>text</em><code>}</code>, <code>\</code><code>itshape</code> becomes <code>\</code><code>textit{</code><em>text</em><code>}</code>, and <code>\</code><code>ttfamily</code> @@ -96,7 +96,7 @@ for bold typewriter, or </blockquote><p> for a bold slanted instance of the current family (note the italic correction applied at the end of the modal command group, again). -<p>The new commands (as noted above) override commands of the same type. +<p/>The new commands (as noted above) override commands of the same type. In almost all cases, this merely excludes ludicrous ideas such as “upright slanted” fonts, or “teletype roman” fonts. There are a couple of immediate oddities, though. The first is the conflict @@ -120,5 +120,5 @@ needs LaTeX’s simplest font selection commands: <dl> <dt><tt><i>smallcap.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smallcap.zip">macros/latex/contrib/smallcap</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smallcap.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/smallcap/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2letterfontcmd">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2letterfontcmd</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2letterfontcmd">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=2letterfontcmd</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-8000.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-8000.html index 11d089484b1..77549595a86 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-8000.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-8000.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label 8000</title> </head><body> <h3>Mismatched mode ljfour and resolution 8000</h3> -<p>You’re running <i>dvips</i>, and you encounter a stream of error +<p/>You’re running <i>dvips</i>, and you encounter a stream of error messages, starting with “<code>Mismatched mode</code>”. The mode is the default used in your installation — it’s set in the <i>dvips</i> configuration file, and <code>ljfour</code> is commonest (since it’s the default in most distributions), but not invariable. -<p>The problem is that <i>dvips</i> has encountered a font for which +<p/>The problem is that <i>dvips</i> has encountered a font for which it must generate a bitmap (since it can’t find it in Type 1 format), and there is no proforma available to provide instructions to give to Metafont. -<p>So what to do? The number 8000 comes from the ‘<code>-Ppdf</code>’ option +<p/>So what to do? The number 8000 comes from the ‘<code>-Ppdf</code>’ option to <i>dvips</i>, which you might have found from the answer <a href="FAQ-fuzzy-type3.html">“wrong type of fonts”</a>. The obvious @@ -20,5 +20,5 @@ 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 way of expressing what you want to do, using type 1 fonts. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=8000">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=8000</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=8000">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=8000</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-AMSpkg.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-AMSpkg.html index db71fffdda8..18d62bc7e03 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-AMSpkg.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-AMSpkg.html @@ -3,7 +3,7 @@ </head><body> <h3>What are the AMS packages (AMSTeX, <em>etc</em>.)?</h3> -<p>AMSTeX is a TeX macro package, originally written by Michael Spivak for +<p/>AMSTeX is a TeX macro package, originally written by Michael Spivak for the American Mathematical Society (AMS) during 1983–1985 and is described in the book “<a href="FAQ-books.html">The Joy of TeX</a>”. It is based on Plain TeX, and provides many @@ -14,7 +14,7 @@ aspects covered include multi-line displayed equations, equation numbering, ellipsis dots, matrices, double accents, multi-line subscripts, syntax checking (faster processing on initial error-checking TeX runs), and other things. -<p>As LaTeX increased in popularity, authors asked to submit papers to +<p/>As LaTeX increased in popularity, authors asked to submit papers to the AMS in LaTeX, and so the AMS developed AMSLaTeX, which is a collection of LaTeX packages and classes that offer authors most of @@ -26,5 +26,5 @@ its users to use AMSLaTeX instead. <dt><tt><i>AMSTeX distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/amstex.zip">macros/amstex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/amstex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/amstex/">browse</a>) <dt><tt><i>AMSLaTeX distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=AMSpkg">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=AMSpkg</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=AMSpkg">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=AMSpkg</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-BibTeXing.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-BibTeXing.html index 88d6276dc55..7591756e032 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-BibTeXing.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-BibTeXing.html @@ -2,29 +2,32 @@ <title>UK TeX FAQ -- question label BibTeXing</title> </head><body> <h3>BibTeX Documentation</h3> -<p>BibTeX, a program originally designed to produce bibliographies in +<p/>BibTeX, a program originally designed to produce bibliographies in conjunction with LaTeX, is explained in Section 4.3 and Appendix B -of Leslie Lamport’s LaTeX manual -(see <a href="FAQ-books.html">TeX-related books</a>). +of Leslie Lamport’s LaTeX manual. The document “BibTeXing”, contained in the file <i>btxdoc.tex</i>, expands on the chapter in Lamport’s book. <em>The LaTeX Companion</em> -(see <a href="FAQ-books.html">TeX-related books</a>) also -has information on BibTeX and writing BibTeX style files. -<p>The document “Designing BibTeX Styles”, contained in the file -<code>btxhak.tex</code>, explains the postfix stack-based language used to write -BibTeX styles (<code>.bst</code> files). The file <code>btxbst.doc</code> is the template -for the four standard styles (<code>plain</code>, <code>abbrv</code>, <code>alpha</code>, <code>unsrt</code>). It -also contains their documentation. -The complete BibTeX documentation set (including the files above) -is available on CTAN. -<p>A useful tutorial of the whole process of using BibTeX is Nicolas +also has information on BibTeX and writing BibTeX style files. +(See <a href="FAQ-books.html">TeX-related books</a> for details of both +books.) +<p/>The document “Designing BibTeX Styles”, contained in the file +<i>btxhak.tex</i>, explains the postfix stack-based language used to +write BibTeX styles (<i>.bst</i> files). The file <i>btxbst.doc</i> +is the template for the four standard styles (<i>plain</i>, +<i>abbrv</i>, <i>alpha</i>, and <i>unsrt</i>). It also +contains their documentation. The complete BibTeX documentation +set (including all the files above) is available on CTAN. +<p/>A useful tutorial of the whole process of using BibTeX is Nicolas Markey’s “<em>Tame the BeaST (The B to X of BibTeX)</em>”, which -may also be found on CTAN. +may also be found on CTAN. A summary and FAQ +(<i>btxFAQ</i>), by Michael Shell and David Hoadley, is also to be +recommended. <dl> <dt><tt><i>BibTeX documentation</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/distribs/doc.zip">biblio/bibtex/distribs/doc</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/distribs/doc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/distribs/doc/">browse</a>) <dt><tt><i>BibTeX documentation, in PDF</i></tt><dd> <a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/doc.zip">biblio/bibtex/contrib/doc</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/doc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/doc/">browse</a>) +<dt><tt><i>btxFAQ.pdf</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/doc/btxFAQ.pdf">biblio/bibtex/contrib/doc/btxFAQ.pdf</a> <dt><tt><i>Tame the BeaST</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/bibtex/tamethebeast/ttb_en.pdf">info/bibtex/tamethebeast/ttb_en.pdf</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=BibTeXing">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=BibTeXing</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=BibTeXing">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=BibTeXing</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-CD.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-CD.html index 94df44f1992..e902260d572 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-CD.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-CD.html @@ -1,25 +1,45 @@ <head> <title>UK TeX FAQ -- question label CD</title> </head><body> -<h3>The TeX Live distribution</h3> -<p>If you don’t have access to the Internet, there are obvious +<h3>The TeX collection</h3> +<p/>If you don’t have access to the Internet, there are obvious attractions to TeX collections on a disc. Even those with net access will find large quantities of TeX-related files to hand a great convenience. -<p>The TeX Live distribution provides this, together with -a ready-to-run TeX system. The TeX Live installation disc offers -teTeX for use on Unix-like systems, and ProTeXt for use on Windows -systems. There is also a ‘demonstration’ disc and an archive snapshot -(all on CD- or DVD-ROMs). TeX-Live -was originally developed under the auspices of a consortium of User -Groups (notably TUG, UK TUG and -GUTenberg). All members of several User Groups receive copies -free of charge. Some user groups will also sell additional copies: +<p/>The TeX collection provides this, together with +ready-to-run TeX systems for various architectures. Contents of +the collection are: +<ul> +<li> The TeX-live installation disc (a CD) provides TeX + systems for use on GNU-Linux, MacOS/X and Win-32 + architectures; +<li> The TeX-live ‘Live’ disc (a DVD) providing TeX for + a wider range of architectures; +<li> MacTeX: an easy to install TeX system for MacOS/X, based + on TeX-live, and including the + <a href="http://www.uoregon.edu/~koch/texshop/">texshop front-end</a> + and other tools; +<li> ProTeXt: an easy to install TeX system for Windows, based + on MiKTeX, and including an ‘active’ document to guide + installation; and +<li> A snapshot of CTAN. +</ul> +A fair number of national TeX User Groups, as well as TUG, +distribute copies to their members at no extra charge. Some user +groups are also able to sell additional copies: contact your local user group or <a href="FAQ-TUGstar.html">TUG</a>. -<p>Details of TeX Live are available from its own - <a href="http://www.tug.org/texlive.html">web page</a> +<p/>You may also download disc images from CTAN; the installation +disc, ProTeXt and MacTeX are all separately available. Beware: +they are all pretty large downloads. +<p/>Moew details of the collection are available from its own + <a href="http://www.tug.org/texcollection/">web page</a> on the TUG site. -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=CD">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=CD</a> +<dl> +<dt><tt><i>MacTeX</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/mac/mactex/">systems/mac/mactex/</a> +<dt><tt><i>ProTeXt</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/win32/protext/">systems/win32/protext/</a> +<dt><tt><i>TeXlive install image</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/texlive/">systems/texlive/</a> +</dl> +<p/> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=CD">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=CD</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ECfonts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ECfonts.html index 8e4173d82d8..17985361f8d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ECfonts.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ECfonts.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label ECfonts</title> </head><body> <h3>What are the EC fonts?</h3> -<p>A font consists of a number of <em>glyphs</em>. In order that the +<p/>A font consists of a number of <em>glyphs</em>. In order that the glyphs may be printed, they are <a href="FAQ-whatenc.html"><em>encoded</em></a>, and the encoding is used as an index into tables within the font. For various reasons, Knuth chose deeply eccentric encodings for his @@ -10,7 +10,7 @@ Computer Modern family of fonts; in particular, he chose different encodings for different fonts, so that the application using the fonts has to remember which font of the family it’s using before selecting a particular glyph. -<p>When TeX version 3 arrived, most of the excuses for the +<p/>When TeX version 3 arrived, most of the excuses for the 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’ @@ -23,11 +23,9 @@ 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 -the interaction of accents and hyphenation - +the interaction of accents and hyphenation (see <a href="FAQ-hyphenaccents.html">hyphenation of accented words</a>). - -<p>The only Metafont-fonts that conform to the Cork encoding are the +<p/>The only Metafont-fonts that conform to the Cork encoding are the EC fonts. They look CM-like, though their metrics differ from CM-font metrics in several areas. The fonts are now regarded as ‘stable’ (in the same sense that the CM fonts @@ -44,7 +42,7 @@ EC-equivalent fonts in type 1 or TrueType form — see <a href="FAQ-textrace.html">auto-traced versions</a> (the CM-super and the LGC fonts), and the Latin Modern series (rather directly generated from Metafont sources), are available. -<p> +<p/> Note that the Cork encoding doesn’t cover mathematics (and neither do @@ -55,15 +53,14 @@ TeX mathematics; more advanced mathematics are likely to need separate fonts anyway. Suitable mathematics fonts for use with other font families are discussed in “<a href="FAQ-psfchoice.html">choice of scalable fonts</a>”. -<p>The EC fonts are distributed with a +<p/>The EC fonts are distributed with a 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. -<p>The Cork encoding is also implemented by virtual fonts provided in the - - <a href="FAQ-usepsfont.html">PSNFSS system</a>, -for PostScript fonts, and also by the <i>txfonts</i> and +<p/>The Cork encoding is also implemented by virtual fonts provided in the +<a href="FAQ-usepsfont.html">PSNFSS system</a>, +for Adobe Type 1 fonts, and also by the <i>txfonts</i> and <i>pxfonts</i> font packages (see <a href="FAQ-psfchoice.html">“choice of scalable fonts”</a>). @@ -73,5 +70,5 @@ for PostScript fonts, and also by the <i>txfonts</i> and <dt><tt><i>EC and TC fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ec.zip">fonts/ec</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ec.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ec/">browse</a>) <dt><tt><i>Latin Modern fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/lm.zip">fonts/lm</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/lm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/lm/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ECfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ECfonts</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ECfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ECfonts</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-HPdrivers.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-HPdrivers.html index 51051bee670..7b59a98ca4d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-HPdrivers.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-HPdrivers.html @@ -2,17 +2,16 @@ <title>UK TeX FAQ -- question label HPdrivers</title> </head><body> <h3>DVI drivers for HP LaserJet</h3> -<p>The emTeX distribution (see <a href="FAQ-TeXsystems.html">TeX systems</a>) +<p/>The emTeX distribution (see <a href="FAQ-TeXsystems.html">TeX systems</a>) contains a driver for the LaserJet, <i>dvihplj</i>. -<p>Version 2.10 of the Beebe drivers supports the LaserJet. These drivers +<p/>Version 2.10 of the Beebe drivers supports the LaserJet. These drivers will compile under Unix, VMS, and on the Atari ST and DEC-20s. -<p>For Unix systems, Karl Berry’s <i>dviljk</i> uses the same -path-searching library as <i>web2c</i>. <i>dviljk</i> is no -longer distributed as a separate source, but the teTeX distribution -holds a copy under the name <i>dvilj</i>. +<p/>For Unix systems, Karl Berry’s <i>dviljk</i> uses the same +path-searching library as <i>web2c</i>. <dl> <dt><tt><i>Beebe drivers</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/beebe.zip">dviware/beebe</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/beebe.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/beebe/">browse</a>) +<dt><tt><i>dviljk</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dviljk.zip">dviware/dviljk</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dviljk.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dviljk/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=HPdrivers">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=HPdrivers</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=HPdrivers">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=HPdrivers</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX2HTML.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX2HTML.html index 08c0410d8f2..e0f2d5d30c9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX2HTML.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX2HTML.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label LaTeX2HTML</title> </head><body> <h3>Conversion from (La)TeX to HTML</h3> -<p>TeX and LaTeX are well suited to producing electronically publishable +<p/>TeX and LaTeX are well suited to producing electronically publishable 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 @@ -13,7 +13,7 @@ readers to see an exact replication of what your document looks like to you, then you cannot use HTML and you must use some other publishing format such as PDF. That is true for any HTML authoring tool. -<p>TeX’s excellent mathematical capabilities remain a challenge in the +<p/>TeX’s excellent mathematical capabilities remain a challenge in the business of conversion to HTML. There are only two generally reliable techniques for generating mathematics on the web: creating bitmaps of bits of typesetting that can’t be translated, and using @@ -25,7 +25,7 @@ requires configuration of the browser. The future of mathematical browsing may be brighter — see <a href="FAQ-mathml.html">future Web technologies</a>. -<p>For today, possible packages are: +<p/>For today, possible packages are: <dl> <dt><i>LaTeX2HTML</i><dd>a <i>Perl</i> script package that supports LaTeX only, and generates mathematics (and other @@ -35,7 +35,7 @@ browsing may be brighter — see systems. Michel Goossens and Janne Saarela published a detailed discussion of <i>LaTeX2HTML</i>, and how to tailor it, in <i>TUGboat</i> 16(2). -<p> A mailing list for users may be found via +<p/> A mailing list for users may be found via <a href="http://tug.org/mailman/listinfo/latex2html">http://tug.org/mailman/listinfo/latex2html</a> <dt><i>TtH</i><dd>a compiled program that supports either LaTeX or Plain TeX, and uses the font/table technique for representing @@ -66,7 +66,7 @@ An interesting set of samples, including conversion of the same text by the four free programs listed above, is available at <a href="http://www.mayer.dial.pipex.com/samples/example.htm">http://www.mayer.dial.pipex.com/samples/example.htm</a>; a linked page gives lists of pros and cons, by way of comparison. -<p>The World Wide Web Consortium maintains a list of “filters” to +<p/>The World Wide Web Consortium maintains a list of “filters” to HTML, with sections on (La)TeX and BibTeX — see <a href="http://www.w3.org/Tools/Word_proc_filters.html">http://www.w3.org/Tools/Word_proc_filters.html</a> <dl> @@ -74,5 +74,5 @@ HTML, with sections on (La)TeX and BibTeX — see <dt><tt><i>tex4ht</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/TeX4ht/tex4ht-all.zip">support/TeX4ht/tex4ht-all.zip</a> <dt><tt><i>tth</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/support/tth/dist/tth_C.tgz">nonfree/support/tth/dist/tth_C.tgz</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeX2HTML">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeX2HTML</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeX2HTML">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeX2HTML</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX3.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX3.html index 7b0ae4b846d..2a29b0b7692 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX3.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX3.html @@ -1,20 +1,21 @@ <head> <title>UK TeX FAQ -- question label LaTeX3</title> </head><body> -<h3>The LaTeX3 project</h3> -<p>The LaTeX3 project team (see <a href="http://www.latex-project.org/latex3.html">http://www.latex-project.org/latex3.html</a>) +<h3>The LaTeX project</h3> +<p/>The LaTeX project team (see <a href="http://www.latex-project.org/latex3.html">http://www.latex-project.org/latex3.html</a>) is a small group of volunteers whose aim is to produce a major new document processing system based on the -principles pioneered by Leslie Lamport in the current LaTeX. It +principles pioneered by Leslie Lamport in the current LaTeX. The +new system is (provisionally) called LaTeX3; it will remain freely available and it will be fully documented at all levels. -<p>The LaTeX3 team’s first product (LaTeX2e) was delivered in 1994 +<p/>The LaTeX team’s first product (LaTeX2e) was delivered in 1994 (it’s now properly called “LaTeX”, since no other version is current). -<p>LaTeX2e was intended as a consolidation exercise, unifying several +<p/>LaTeX2e was intended as a consolidation exercise, unifying several sub-variants of LaTeX while changing nothing whose change wasn’t absolutely necessary. This has permitted the team to support a single version of LaTeX, in parallel with development of LaTeX3. -<p>Some of the older discussion papers about directions for LaTeX3 are +<p/>Some of the older discussion papers about directions for LaTeX3 are to be found on CTAN; other (published) articles are to be found on the project web site (<a href="http://www.latex-project.org/papers/">http://www.latex-project.org/papers/</a>), as is some of the @@ -28,5 +29,5 @@ message ‘<code>subscribe latex-l <<em>your name</em>></code>’ <dl> <dt><tt><i>LaTeX project publications</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/ltx3pub.zip">info/ltx3pub</a> (<a href="ftp://cam.ctan.org/tex-archive/info/ltx3pub.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/ltx3pub/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeX3">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeX3</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeX3">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeX3</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXandPlain.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXandPlain.html index 174238f9a88..3cda1f19b98 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXandPlain.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXandPlain.html @@ -2,22 +2,25 @@ <title>UK TeX FAQ -- question label LaTeXandPlain</title> </head><body> <h3>How does LaTeX relate to Plain TeX?</h3> -<p>LaTeX is a program written in the programming language TeX. (In +<p/>LaTeX is a program written in the programming language TeX. (In the same sense, any LaTeX document is also a program, which is designed to run ‘alongside’, or ‘inside’ LaTeX, whichever metaphor you prefer.) -<p>Plain TeX is also a program written in the programming language +<p/>Plain TeX is also a program written in the programming language TeX. -<p>Both exist because writing your documents in ‘raw’ TeX would +<p/>Both exist because writing your documents in ‘raw’ TeX would involve much reinventing of wheels for every document. They both serve as convenient aids to make document writing more pleasant: LaTeX is a far more extensive aid. -<p>LaTeX is close to being a superset of Plain TeX. Many documents +<p/>LaTeX is close to being a superset of Plain TeX. Many documents designed for Plain TeX will work with LaTeX with no more than minor modifications (though some will require substantial work). -<p>Interpretation of any (La)TeX program involves some data-driven +<p/>Interpretation of any (La)TeX program involves some data-driven elements, and LaTeX has a wider range of such elements than does Plain TeX. As a result, the mapping from LaTeX to Plain TeX -is far less clear than that in the other direction. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeXandPlain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeXandPlain</a> +is far less clear than that in the other direction — see a later +answer about + <a href="FAQ-LaTeXtoPlain.html">translating to Plain TeX</a>. + +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeXandPlain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeXandPlain</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXtoPlain.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXtoPlain.html index 64df243538f..4a0148e2129 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXtoPlain.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXtoPlain.html @@ -2,14 +2,29 @@ <title>UK TeX FAQ -- question label LaTeXtoPlain</title> </head><body> <h3>Translating LaTeX to Plain TeX</h3> -<p>Unfortunately, no “general”, simple, automatic process is likely to +<p/>Unfortunately, no “general”, simple, automatic process is likely to succeed at this task. See “<a href="FAQ-LaTeXandPlain.html">How does LaTeX relate to Plain TeX</a>” for further details. -<p>Translating a document designed to work with LaTeX into one +<p/>Translating a document designed to work with LaTeX into one designed to work with Plain TeX is likely to amount to carefully including (or otherwise re-implementing) all those parts of LaTeX, beyond the provisions of Plain TeX, which the document uses. -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeXtoPlain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeXtoPlain</a> +<p/>Some of this work is has (in a sense) been done, in the port of the +LaTeX graphics package to Plain TeX. However, while +<i>graphics</i> is available, other complicated packages (notably +<i>hyperref</i>) are not. The aspiring translator may find the +<a href="FAQ-eplain.html">Eplain</a> system a useful source of code. (In fact, +a light-weight system such as Eplain might reasonably be adopted as +an alternative target of translation, though it undoubtedly gives the +user more than the “bare minimum” that Plain TeX is designed to +offer.) +<dl> +<dt><tt><i>\latexhtml{\textrm{The}}{The} eplain system</i></tt><dd> + <a href="ftp://cam.ctan.org/tex-archive/macros/eplain.zip">macros/eplain</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/eplain.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/eplain/">browse</a>) +<dt><tt><i>\latexhtml{\textrm{‘Plain TeX’}}{Plain TeX} graphics</i></tt><dd> + <a href="ftp://cam.ctan.org/tex-archive/macros/plain/graphics.zip">macros/plain/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/graphics/">browse</a>) +</dl> +<p/> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeXtoPlain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=LaTeXtoPlain</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-MF.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-MF.html index fe88f3967e6..45a0be06dd8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-MF.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-MF.html @@ -2,22 +2,22 @@ <title>UK TeX FAQ -- question label MF</title> </head><body> <h3>What is Metafont?</h3> -<p>Metafont was written by Knuth as a companion to TeX; whereas TeX +<p/>Metafont was written by Knuth as a companion to TeX; whereas TeX defines the layout of glyphs on a page, Metafont defines the shapes of the glyphs and the relations between them. Metafont details the sizes of glyphs, for TeX’s benefit, and details the rasters used to represent the glyphs, for the benefit of programs that will produce printed output as post processes after a run of TeX. -<p>Metafont’s language for defining fonts permits the expression of several +<p/>Metafont’s language for defining fonts permits the expression of several classes of things: first (of course), the simple geometry of the glyphs; second, the properties of the print engine for which the output is intended; and third, ‘meta’-information which can distinguish different design sizes of the same font, or the difference between two fonts that belong to the same (or related) families. -<p>Knuth (and others) have designed a fair range of fonts using Metafont, +<p/>Knuth (and others) have designed a fair range of fonts using Metafont, but font design using Metafont is much more of a minority skill than is TeX macro-writing. The complete TeX-user nevertheless needs to be aware of Metafont, and to be able to run Metafont to generate personal -copies of new fonts. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=MF">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=MF</a> +copies of Meta-fonts that come her way. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=MF">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=MF</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-MP.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-MP.html index c5c44518920..e9a6ceaaa3e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-MP.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-MP.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label MP</title> </head><body> <h3>What is MetaPost?</h3> -<p>The MetaPost system (by John Hobby) implements a picture-drawing language +<p/>The MetaPost system (by John Hobby) implements a picture-drawing language very much like that of Metafont except that it outputs Encapsulated PostScript files instead of run-length-encoded bitmaps. MetaPost is a powerful language for producing figures for documents to be printed on PostScript @@ -10,17 +10,17 @@ printers, either directly or embedded in (La)TeX documents. It includes facilities for directly integrating TeX text and mathematics with the graphics. (Knuth tells us that he uses nothing but MetaPost for diagrams in text that he is writing.) -<p>Although PDFLaTeX cannot ordinarily handle PostScript graphics, the +<p/>Although PDFLaTeX cannot ordinarily handle PostScript graphics, the output of MetaPost is sufficiently simple and regular that PDFLaTeX can handle it direct, using code borrowed from ConTeXt — see <a href="FAQ-pdftexgraphics.html">graphics in PDFLaTeX</a>. -<p>Much of MetaPost’s source code was copied from Metafont’s sources, with +<p/>Much of MetaPost’s source code was copied from Metafont’s sources, with Knuth’s permission. -<p>A mailing list discussing MetaPost is available; +<p/>A mailing list discussing MetaPost is available; subscribe via the <a href="http://lists.tug.org/metapost">TUG <i>mailman</a> interface</i>. The TUG website also hosts a <a href="http://tug.org/metapost.html">MetaPost summary page</a>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=MP">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=MP</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=MP">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=MP</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-PSpreview.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-PSpreview.html index 923a654de90..6808d33ebb8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-PSpreview.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-PSpreview.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label PSpreview</title> </head><body> <h3>Previewing files using Type 1 fonts</h3> -<p>Until recently, free TeX previewers have only been capable of +<p/>Until recently, free TeX previewers have only been capable of displaying bitmap PK fonts, but current versions of <i>xdvi</i> sport a Type 1 font renderer. @@ -10,7 +10,7 @@ displaying bitmap PK fonts, but current versions of -<p>Other (free) previewers of the current generation offer automatic +<p/>Other (free) previewers of the current generation offer automatic generation of the requisite PK files (using <i>gsftopk</i>, or similar, behind the scenes). If your previewer isn’t capable of this, you have three options: @@ -26,7 +26,9 @@ this, you have three options: - (See <a href="FAQ-commercial.html">commercial suppliers</a> for details.) +\typeout{after narrowversion, before wideversion} + (See <a href="FAQ-commercial.html">commercial suppliers</a> for details.) +\typeout{after wideversion} <li> If you have the PostScript fonts in Type 1 format, use <i>ps2pk</i> or <i>gsftopk</i> (designed for use with the <i>ghostscript</i> fonts) to make @@ -36,12 +38,12 @@ this, you have three options: this if you have purchased the fonts. </ul> <dl> -<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/ghostscript/">nonfree/support/ghostscript/</a> +<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/">support/ghostscript/</a> <dt><tt><i>ghostview</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/gnu/ghostview/">support/ghostscript/gnu/ghostview/</a> <dt><tt><i>gsftopk</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/gsftopk.zip">fonts/utilities/gsftopk</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/gsftopk.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/gsftopk/">browse</a>) <dt><tt><i>GSview</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/ghostscript/ghostgum/">nonfree/support/ghostscript/ghostgum/</a> <dt><tt><i>ps2pk</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/ps2pk.zip">fonts/utilities/ps2pk</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/ps2pk.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/ps2pk/">browse</a>) <dt><tt><i>xdvi</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/xdvi.zip">dviware/xdvi</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/xdvi.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/xdvi/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=PSpreview">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=PSpreview</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=PSpreview">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=PSpreview</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-RCS.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-RCS.html index d706c796646..1f52dd9b60b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-RCS.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-RCS.html @@ -2,31 +2,31 @@ <title>UK TeX FAQ -- question label RCS</title> </head><body> <h3>Version control using RCS, CVS or <i>Subversion</i></h3> -<p>If you use RCS, CVS or <i>Subversion</i> to maintain +<p/>If you use RCS, CVS or <i>Subversion</i> to maintain your (La)TeX documents under version control, you may need some mechanism for including the version details in your document, in such a way that they can be typeset (that is, rather than just hiding them inside a comment). -<p>The most complete solution for RCS and CVS is to use the +<p/>The most complete solution for RCS and CVS is to use the (LaTeX) package <i>rcs</i>, which allows you to parse and display the contents of RCS keyword fields in an extremely flexible way. The package <i>rcsinfo</i> is simpler, but does most of what you want, and some people prefer it; it is explicitly compatible with <i>LaTeX2HTML</i>. -<p>If, however, you need a solution which works without using external +<p/>If, however, you need a solution which works without using external packages, or which will work in Plain TeX, then you can use the following minimal solution: <blockquote> <pre> \def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}} -\RCS$Revision: 1.426 $ % or any RCS keyword -\RCS$Date: 2006/12/18 09:59:16 $ +\RCS$Revision: 1.498 $ % or any RCS keyword +\RCS$Date: 2007/11/05 22:31:23 $ ... \date{Revision \RCSRevision, \RCSDate} </pre> </blockquote><p> -<p>If you’ve entered the brave new world of <i>subversion</i>, the +<p/>If you’ve entered the brave new world of <i>subversion</i>, the package <i>svn</i> may be for you. It has explicit cleverness about dealing with dates: <blockquote> @@ -45,7 +45,7 @@ about dealing with dates: will (once <i>subversion</i> has committed a copy of the document) cause <code>\</code><code>maketitle</code> use the date that has been written into the <code>$Date$</code> keyword. -<p>The alternative is the <i>svninfo</i> package, which has much the +<p/>The alternative is the <i>svninfo</i> package, which has much the same mechanisms as does <i>svn</i> but with a rather different focus. <i>Svninfo</i> does the date trick that <i>svn</i> performs (controlled by a package option), and can set up page @@ -58,5 +58,5 @@ the packages’ documentation to see which you find best. <dt><tt><i>svn.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/svn.zip">macros/latex/contrib/svn</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/svn.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/svn/">browse</a>) <dt><tt><i>svninfo.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/svninfo.zip">macros/latex/contrib/svninfo</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/svninfo.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/svninfo/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=RCS">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=RCS</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=RCS">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=RCS</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-SGML2TeX.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-SGML2TeX.html index 4f1fe189248..8a5d7f1fd4e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-SGML2TeX.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-SGML2TeX.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label SGML2TeX</title> </head><body> <h3>Conversion from SGML or HTML to TeX</h3> -<p>SGML is a very important system for document storage and interchange, +<p/>SGML is a very important system for document storage and interchange, but it has no formatting features; its companion ISO standard DSSSL (see <a href="http://www.jclark.com/dsssl/">http://www.jclark.com/dsssl/</a>) is designed for writing @@ -44,10 +44,10 @@ translator: Both of these allow the user to write ‘handlers’ for every SGML element, with plenty of access to attributes, entities, and information about the context within the document tree. -<p> If these packages don’t meet your needs for an average SGML +<p/> If these packages don’t meet your needs for an average SGML typesetting job, you need the big commercial stuff. </ol> -<p>Since HTML is simply an example of SGML, we do not need a specific +<p/>Since HTML is simply an example of SGML, we do not need a specific system for HTML. However, Nathan Torkington developed <i>html2latex</i> from the HTML parser in NCSA’s @@ -55,11 +55,11 @@ 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 source is available on CTAN. -<p>Michel Goossens and Janne Saarela published a very useful summary of +<p/>Michel Goossens and Janne Saarela published a very useful summary of SGML, and of public domain tools for writing and manipulating it, in <i>TUGboat</i> 16(2). <dl> <dt><tt><i>html2latex source</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/html2latex.zip">support/html2latex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/html2latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/html2latex/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=SGML2TeX">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=SGML2TeX</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=SGML2TeX">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=SGML2TeX</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TUGstar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TUGstar.html index babb1228147..f33711fd008 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TUGstar.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TUGstar.html @@ -2,29 +2,30 @@ <title>UK TeX FAQ -- question label TUG*</title> </head><body> <h3>TeX User Groups</h3> -<p>There has been a TeX User Group since very near the time TeX +<p/>There has been a TeX User Group since very near the time TeX first appeared. That first group, TUG, is still active and its journal <i>TUGboat</i> continues in regular publication with articles about TeX, Metafont and related technologies, and about document design, processing and production. TUG holds a yearly conference, whose proceedings are published in <i>TUGboat</i>. -<p>TUG’s web site is a valuable resource for all sorts of +<p/>TUG’s <a href="http://www.tug.org">web site</a> is a valuable +resource for all sorts of TeX-related matters, such as details of TeX software, and lists of TeX vendors and TeX consultants. Back articles from <i>TUGboat</i> are slowly (subject to copyright issues, etc.) making their way to the site, too. -<p>Some time ago, TUG established a “technical council”, whose +<p/>Some time ago, TUG established a “technical council”, whose task was to oversee the development of TeXnical projects. Most such projects nowadays go on their way without any support from TUG, but TUG’s web site lists its <a href="http://www.tug.org/twg.html">Technical Working Groups (TWGs)</a>. -<p>TUG has a reasonable claim to be considered a world-wide +<p/>TUG has a reasonable claim to be considered a world-wide organisation, but there are many national and regional user groups, too; TUG’s web site maintains a list of <a href="http://www.tug.org/lugs.html">“local user groups” (LUGs)</a>. -<p>Contact TUG itself via: +<p/>Contact TUG itself via: <blockquote> TeX Users Group<br> 1466 NW Front Avenue, Suite 3141<br> @@ -35,6 +36,6 @@ too; TUG’s web site maintains a list of Email: <a href="mailto:tug@mail.tug.org"><i>tug@mail.tug.org</i></a><br> Web: <a href="http://www.tug.org/">http://www.tug.org/</a> </blockquote><p> -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TUG*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TUG*</a> +<p/> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TUG*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TUG*</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXfuture.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXfuture.html index a50645e52e4..6db8acf7837 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXfuture.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXfuture.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label TeXfuture</title> </head><body> <h3>What is the future of TeX?</h3> -<p>Knuth has declared that he will do no further development of TeX; +<p/>Knuth has declared that he will do no further development of TeX; 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 @@ -12,11 +12,11 @@ limit pi (at the time of writing, Knuth’s latest release is version dies; thereafter, no further changes may be made to Knuth’s source. (A similar rule is applied to Metafont; its version number tends to the limit e, and currently stands at 2.71828.) -<p>Knuth explains his decision, and exhorts us all to respect it, in a +<p/>Knuth explains his decision, and exhorts us all to respect it, in a paper originally published in <i>TUGboat</i> 11(4) (and reprinted in the <a href="http://www.ntg.nl/maps/pdf/5_34.pdf">NTG journal MAPS</a>). -<p>There are projects (some of them long-term +<p/>There are projects (some of them long-term projects: see, for example, <a href="FAQ-LaTeX3.html">the LaTeX3 project</a>) @@ -25,7 +25,9 @@ new macro packages based on TeX. For the even longer term, there are various projects to build a <em>successor</em> to TeX; see, for example, the -<a href="FAQ-omegaleph.html">Omega/Aleph</a> -<a href="FAQ-extex.html">ExTeX</a>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXfuture">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXfuture</a> +<a href="FAQ-luatex.html">\LuaTeX</a>, +<a href="FAQ-omegaleph.html">Omega/Aleph</a> and +<a href="FAQ-extex.html">ExTeX</a> + projects. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXfuture">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXfuture</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXpronounce.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXpronounce.html index ab4ab182aeb..2da01c865cf 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXpronounce.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXpronounce.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label TeXpronounce</title> </head><body> <h3>How should I pronounce “TeX”?</h3> -<p>The ‘X’ is “really” the Greek letter +<p/>The ‘X’ is “really” the Greek letter Chi, and is pronounced by English-speakers either a bit like the ‘ch’ in the Scots word ‘loch’ ([x] in the IPA) or (at a pinch, if you can’t do the Greek sound) like ‘k’. It definitely is not pronounced ‘ks’ (the Greek letter with that sound doesn’t look remotely like the Latin alphabet ‘X’). -<p>This curious usage derives from Knuth’s explanation in the TeXbook +<p/>This curious usage derives from Knuth’s explanation in the TeXbook that the name comes from the Greek word for ‘art’ or ‘craft’ (‘<em>techni</em>’), which is the root of the English word ‘technology’. Knuth’s logo for TeX is @@ -16,5 +16,5 @@ 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) in this FAQ (see <a href="FAQ-logos.html">Typesetting TeX-related logos</a>). -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXpronounce">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXpronounce</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXpronounce">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXpronounce</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html index 06cb5c301a0..b0ab7d2e143 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html @@ -2,83 +2,66 @@ <title>UK TeX FAQ -- question label TeXsystems</title> </head><body> <h3>(La)TeX for different machines</h3> -<!-- windows,macintosh,ms-dos,os/2,unix,linux --> -<p>We list here the free or shareware packages; +<!-- windows,macintosh,macos,ms-dos,os/2,unix,linux --> +<p/>We list here the free or shareware packages; another question addresses <a href="FAQ-commercial.html">commercial TeX vendors’</a> products. <dl> -<dt>Unix<dd> Instructions for retrieving the <i>web2c</i> Unix - TeX distribution via anonymous <code>ftp</code> are to be found in - <i>unixtex.ftp</i>, though nowadays the sensible installer will - take (and possibly customise) one of the packaged distributions such - as teTeX, or the <a href="FAQ-CD.html">TeX Live distribution</a>. -<p> To compile and produce a complete teTeX distribution, you need a - <code>.tar.gz</code> file for each of <code>teTeX-src</code>, - <code>teTeX-texmf</code> and <code>teTeX-texmfsrc</code>. -<p> No sets of teTeX binaries are provided on CTAN; however, - compilation of teTeX is pretty stable, on a wide variety of - platforms. If you don’t have the means to compile teTeX - yourself, you will find that most “support” sites carry compiled - versions in their “free area”, and the TeX-live discs also - carry a wide range of binary distributions. -<p> There’s a mailing list for teTeX installation problems (and the - like): subscribe by sending mail to - <a href="mailto:majordomo@dbs.uni-hannover.de"><i>majordomo@dbs.uni-hannover.de</i></a> containing nothing more than - “<code>subscribe tetex</code>”. The list is archived at - <a href="http://www.mail-archive.com/tetex@dbs.uni-hannover.de/">http://www.mail-archive.com/tetex@dbs.uni-hannover.de/</a>, and an - RSS feed is available at the same site: - <a href="http://www.mail-archive.com/tetex@dbs.uni-hannover.de/maillist.xml">http://www.mail-archive.com/tetex@dbs.uni-hannover.de/maillist.xml</a> -<p> During periods when teTeX is itself under development, a - “teTeX-beta” is available. Before proceeding with the - beta-release, check the <i>ANNOUNCE</i> files - in the two directories on CTAN: it may well be that the - beta-release doesn’t offer you anything new, - that you need. -<p> MacOS X users should refer to the information below, - under item “Mac”. +<dt>Unix<dd> The only current distribution of TeX for Unix systems + (including GNU/Linux and other free Unix-like systems) is + TeX-live, which is distributed as part of the + <a href="FAQ-CD.html">TeX collection</a>. +<p/> Members of many TeX user groups receive copies of the collection + (on CD and DVD), as part of their membership of the + groups. +<p/> MacOS/X is also a Unix-based system; however users should refer to + the information below, under item “Mac”. <dl> - <dt><tt><i>tetex</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/systems/unix/teTeX/current/distrib/">systems/unix/teTeX/current/distrib/</a> - <dt><tt><i>tetex-beta</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/unix/teTeX-beta.zip">systems/unix/teTeX-beta</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/unix/teTeX-beta.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/unix/teTeX-beta/">browse</a>) - <dt><tt><i>unixtex.ftp</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/unix/unixtex.ftp">systems/unix/unixtex.ftp</a> - <dt><tt><i>web2c</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/web2c.zip">systems/web2c</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/web2c.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/web2c/">browse</a>) + <dt><tt><i>texlive</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/systems/texlive/">systems/texlive/</a> </dl> -<dt>Linux<dd> Linux users may use teTeX (see above). -<p> A free version of the commercial - <a href="FAQ-commercial.html">VTeX</a> is available, which among other - things, specialises in direct production of PDF from - (La)TeX input. Unfortunately, it’s no longer supported. +<dt>Linux<dd> GNU/Linux users are supported by TeX-live (as noted + above). +<p/> A free version of the commercial + <a href="FAQ-commercial.html">VTeX extended TeX system</a> is available + for use under Linux, which among other things specialises in direct + 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. <dl> - <dt><tt><i>tetex</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/systems/unix/teTeX/current/distrib/">systems/unix/teTeX/current/distrib/</a> + <dt><tt><i>texlive</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/systems/texlive/">systems/texlive/</a> <dt><tt><i>vtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/linux.zip">systems/vtex/linux</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/linux.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/linux/">browse</a>) <dt><tt><i>vtex required common files</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.zip">systems/vtex/common</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/common/">browse</a>) </dl> -<dt>PC: Win32<dd> - MiKTeX, by Christian Schenk, is also a comprehensive - distribution, developed separately from the teTeX work. It has +<dt>PC: Windows post-95<dd> + MiKTeX, by Christian Schenk, is a comprehensive distribution. It has its own previewer, YAP, which is itself capable of printing, though the distribution also includes a port of <i>dvips</i>. 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). The MiKTeX developers provide a - ready-to-run copy of the distribution, on CDROM (for purchase) via the + ready-to-run copy of the distribution, on CD (for purchase) via the <a href="http://www.miktex.org/cd/">MiKTeX web site</a>; otherwise the <i>setup</i> executable is available on CTAN, together with all the optional packages. -<p> <a href="http://tug.org/protext/">ProTeXt</a>, by Thomas Feuerstack, is +<p/> <a href="http://tug.org/protext/">ProTeXt</a>, part of the TeX + collection by Thomas Feuerstack, is a further option for installing MiKTeX. It bundles a MiKTeX setup with some further useful utilities, together with a PDF file which contains clickable links for the various installation - steps, along with explanations. It again it is freeware, and copies - are distributed with the <a href="FAQ-CD.html">TeX-live CD set</a>. -<p> <a href="https://xemtex.groups.foundry.supelec.fr/">XEmTeX</a>, by + steps, along with explanations. +<p/> Windows users are also supported directly by the TeX-live + distribution; a system is provided on the installation disc of the + TeX collection (and it can, with some difficulty, be run “from + the disc” without installing <em>anything</em>). +<p/> <a href="http://foundry.supelec.fr/projects/xemtex/">XEmTeX</a>, by Fabrice Popineau (he who created the excellent, but now defunct, fpTeX distribution), is an integrated distribution of TeX, LaTeX, ConTeXt, <i>XEmacs</i> and friends for Windows. All programs have been compiled natively to take the best advantage of the Windows environment. Configuration is provided so that the resulting set of programs runs out-of-the-box. -<p> The (Japanese) W32TEX distribution was motivated by +<p/> The (Japanese) W32TEX distribution was motivated by the needs of Japanese users (Japanese won’t fit in a “simple” character set like ASCII, but TeX is based on a version of ASCII). Despite its origins, W32TEX is said to @@ -86,30 +69,30 @@ of space: the minimum documented download is as small as 95 MBytes. Investigate the distribution at <a href="http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/web2c75-e.html">http://www.fsci.fuk.kindai.ac.jp/kakuto/win32-ptex/web2c75-e.html</a> -<p> A further (free) option arises from the - <a href="http://www.cygwin.com">“CygWin” bundle</a>, which presents a +<p/> A further (free) option arises from the + <a href="http://www.cygwin.com">CygWin bundle</a>, which presents a Unix-like environment over the Win32 interface; an X-windows server is available. If you run CygWin on your Windows machine, you have - the option of using teTeX, too (you will need the X-server, to - run <i>xdvi</i>). Of course, teTeX components will look like - Unix applications (but that’s presumably what you wanted), but it’s - also reputedly somewhat slower than native Win32 implementations - such as MiKTeX or XEmTeX. TeTeX is available as part of the - CygWin distribution (in the same way that a version is available - with most Linux distributions, nowadays), and you may also build - your own copy from the current sources. -<p> BaKoMa TeX, by Basil Malyshev, is a comprehensive (shareware) + the option of using TeX-live, too (you will need the X-server, to + run <i>xdvi</i>). Of course, TeX-live components will look like + Unix applications (of course, that’s presumably what you wanted), + but TeX under CygWin also reputedly somewhat slower than native + Win32 implementations such as MiKTeX or XEmTeX. The (now + obsolete) teTeX distribution is provided as part of the CygWin + distribution, and but you can build your own copy of TeX-live from + the current sources. +<p/> BaKoMa TeX, by Basil Malyshev, is a comprehensive (shareware) distribution, which focuses on support of Acrobat. The distribution comes with a bunch of Type 1 fonts packaged to work with BaKoMa TeX, which further the focus. <dl> - <dt><tt><i>bakoma</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/win32/bakoma.zip">nonfree/systems/win32/bakoma</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/win32/bakoma.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/systems/win32/bakoma/">browse</a>) + <dt><tt><i>bakoma</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/win32/bakoma.zip">systems/win32/bakoma</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/win32/bakoma.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/win32/bakoma/">browse</a>) <dt><tt><i>miktex</i></tt><dd>Acquire <a href="ftp://cam.ctan.org/tex-archive/systems/win32/miktex/setup/setup.exe">systems/win32/miktex/setup/setup.exe</a> (also available from the MiKTeX web site), and read installation instructions from <a href="http://www.miktex.org/2.5/Setup.aspx">the MiKTeX installation page</a> - <dt><tt><i>protext.exe</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/texlive/Images/protext.exe">systems/texlive/Images/protext.exe</a> - <dt><tt><i>tetex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/unix/teTeX/current/distrib/">systems/unix/teTeX/current/distrib/</a> + <dt><tt><i>protext.exe</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/win32/protext/">systems/win32/protext/</a> + <dt><tt><i>tetex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/obsolete/systems/unix/teTeX/current/distrib/">obsolete/systems/unix/teTeX/current/distrib/</a> </dl> <dt>PC: MSDOS or OS/2<dd> EmTeX, by Eberhard Mattes, includes LaTeX, BibTeX, previewers, and drivers, and is @@ -119,7 +102,7 @@ Windows, are included in the distribution. EmTeX will operate under Windows, but Windows users are better advised to use a distribution tailored for the Windows environment. -<p> A version of emTeX, packaged to use a +<p/> A version of emTeX, packaged to use a <a href="FAQ-tds.html">TDS directory structure</a>, is separately available as an emTeX ‘contribution’. Note that neither emTeX itself, nor @@ -137,77 +120,71 @@ <dl> <dt><tt><i>djgpp</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/djgpp.zip">systems/msdos/djgpp</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/djgpp.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/djgpp/">browse</a>) </dl> -<dt>PC: OS/2<dd> OS/2 may also use a free version of the +<dt>PC: OS/2<dd> EmTeX, by Eberhard Mattes (see + above), was actually developed under OS/2, and lives happily + in that environment. +<p/> OS/2 users may also use a free version of the commercial <a href="FAQ-commercial.html">VTeX</a>, which specialises in direct production of PDF from (La)TeX input. (This version is, like the Linux version, unfortunately no longer supported.) <dl> + <dt><tt><i>emtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex.zip">systems/msdos/emtex</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/emtex/">browse</a>) + <dt><tt><i>emtexTDS</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/os2/emtex-contrib/emtexTDS.zip">obsolete/systems/os2/emtex-contrib/emtexTDS</a> (<a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/os2/emtex-contrib/emtexTDS.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/obsolete/systems/os2/emtex-contrib/emtexTDS/">browse</a>) <dt><tt><i>vtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/os2.zip">systems/vtex/os2</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/os2.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/os2/">browse</a>) <dt><tt><i>vtex required common files</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.zip">systems/vtex/common</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/common/">browse</a>) </dl> -<dt>Windows NT, other platforms<dd> Ports of MiKTeX for - NT on Power PC and AXP are available. Neither - version has been updated for version 1.2 (or later) of - MiKTeX — they may not be satisfactory. - <dl> - <dt><tt><i>miktex for AXP</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/win32/miktex-AXP.zip">obsolete/systems/win32/miktex-AXP</a> (<a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/win32/miktex-AXP.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/obsolete/systems/win32/miktex-AXP/">browse</a>) - <dt><tt><i>miktex for Power PC</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/win32/miktexppc.zip">obsolete/systems/win32/miktexppc</a> (<a href="ftp://cam.ctan.org/tex-archive/obsolete/systems/win32/miktexppc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/obsolete/systems/win32/miktexppc/">browse</a>) - </dl> -<dt>Mac<dd> OzTeX, by Andrew Trevorrow, is a shareware version of - TeX for the Macintosh. A DVI previewer and PostScript - driver are also included. -<p> UK TUG prepays the shareware fee for its members, so - that they may - acquire the software without further payment. Questions about - OzTeX may be directed to <a href="mailto:oztex@midway.uchicago.edu"><i>oztex@midway.uchicago.edu</i></a> -<p> Another partly shareware program is CMacTeX, put together - by Tom Kiffe. This is much closer - to the Unix TeX setup (it uses <i>dvips</i>, for instance). - CMacTeX includes a port of a version of + + + + + + +<dt>Mac<dd> <a href="http://www.trevorrow.com/oztex/">OzTeX</a>, by Andrew + Trevorrow, is a shareware version of + TeX for the Macintosh. A DVI previewer and PostScript + driver are also included. (Members of UK TUG may + acquire the software without further payment, as part of a + membership deal.) OzTeX does not run, natively, under MacOS/X, + but will run with a sufficiently recent CarbonLib (see + <a href="http://www.trevorrow.com/oztex/ozosx.html">http://www.trevorrow.com/oztex/ozosx.html</a>). + Other questions about OzTeX itself may be directed to + <a href="mailto:oztex@midway.uchicago.edu"><i>oztex@midway.uchicago.edu</i></a> +<p/> Another partly shareware program is + <a href="http://www.kiffe.com/cmactex.html">CMacTeX</a> , put together + by Tom Kiffe. CMacTeX is much closer than OzTeX to the Unix + TeX model of things (it uses <i>dvips</i>, for instance). + CMacTeX runs natively under includes a port of a version of <a href="FAQ-omegaleph.html">Omega</a>. -<p> Both OzTeX and CMacTeX run on either MacOS - X or on a sufficiently recent MacOS with CarbonLib +<p/> Both OzTeX and CMacTeX run on either MacOS/X or on a + sufficiently recent MacOS with CarbonLib (v1.3 for OzTeX, v1.4 for CMacTeX). - MacOS X users also have the option of - <a href="http://www.rna.nl/tex.html">gwTeX</a>, by Gerben Wierda (which - is based on teTeX). This is naturally usable from the - command line, just like any other Unix-based system, but it can also - be used Mac-style as the engine behind Richard Koch’s (free) - <a href="http://www.uoregon.edu/~koch/texshop/texshop.html">TeXShop</a>, - which is an integrated TeX editor and previewer. -<p> From its 2005 release, the <a href="FAQ-CD.html">TeX-Live disc set</a> - includes “MacTeX”, a CDROM image that contains - MacOS X teTeX (the Gerben Wierda set mentioned - above), TeXshop, and <a href="FAQ-xetex.html">XeTeX</a>. Details (and a - downloadable distribution set) may be found on the +<p/> From its 2005 release, the <a href="FAQ-CD.html">TeX-live disc set</a> + includes MacTeX. Details (and a downloadable distribution set) + may be found on the <a href="http://tug.org/mactex">TUG web site</a>; the distribution is also on CTAN. -<p> +<p/> A useful <a href="http://www.esm.psu.edu/mac-tex/">resource for Mac users</a> has a news and ‘help’ section, as well as details of systems and tools. + The MacTeX-on-OSX mailing list is a useful resource for users; + mail <a href="mailto:MacOSX-TeX-on@email.esm.psu.edu"><i>MacOSX-TeX-on@email.esm.psu.edu</i></a> to subscribe. <dl> <dt><tt><i>cmactex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/cmactex.zip">nonfree/systems/mac/cmactex</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/cmactex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/systems/mac/cmactex/">browse</a>) - <dt><tt><i>mactex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/mac/mactex.zip">systems/mac/mactex</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/mac/mactex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/mac/mactex/">browse</a>) + <dt><tt><i>mactex</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/mac/mactex/">systems/mac/mactex/</a> <dt><tt><i>oztex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/oztex.zip">nonfree/systems/mac/oztex</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/oztex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/systems/mac/oztex/">browse</a>) - <dt><tt><i>MacOS X teTeX</i></tt><dd><a href="ftp://ftp.nluug.nl/pub/comp/macosx/tex-gs/">ftp://ftp.nluug.nl/pub/comp/macosx/tex-gs/</a> - <dt><tt><i>TeXShop</i></tt><dd><a href="http://darkwing.uoregon.edu/~koch/texshop/texshop.html">http://darkwing.uoregon.edu/~koch/texshop/texshop.html</a> - </dl> -<dt>OpenVMS<dd> TeX for OpenVMS is available. -<p> - - +</dl> +<dt>OpenVMS<dd> TeX for OpenVMS is available, though + it seems unlikely that the version on CTAN is the latest + available. <dl> <dt><tt><i>OpenVMS</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/OpenVMS/TEX97_CTAN.ZIP">systems/OpenVMS/TEX97_CTAN.ZIP</a> </dl> -<dt>Atari<dd> TeX is available for the Atari ST. -<p> If anonymous <code>ftp</code> is not available to you, send a message - containing the line ‘<code>help</code>’ to - <a href="mailto:atari@atari.archive.umich.edu"><i>atari@atari.archive.umich.edu</i></a> +<dt>Atari<dd> TeX for the Atari ST is available from CTAN. <dl> <dt><tt><i>Atari TeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/atari.zip">systems/atari</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/atari.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/atari/">browse</a>) </dl> @@ -219,9 +196,9 @@ <dt>TOPS-20<dd> TeX was originally written on a DEC-10 under WAITS, and so was easily ported to TOPS-20. A distribution that runs on - TOPS-20 is available via anonymous <code>ftp</code> from <a href="ftp://ftp.math.utah.edu/">ftp.math.utah.edu</a> - in <i>pub/tex/pub/web</i> + TOPS-20 is available via anonymous <code>ftp</code> from + <a href="ftp://ftp.math.utah.edu} in <i>pub/tex/pub/web/">ftp.math.utah.edu</i> in \path{pub/tex/pub/web</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXsystems">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXsystems</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXsystems">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXsystems</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-WYGexpts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-WYGexpts.html index b56cfd4f020..2daf0143688 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-WYGexpts.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-WYGexpts.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label WYGexpts</title> </head><body> <h3>The TeX document preparation environment</h3> -<p><p>“<a href="FAQ-notWYSIWYG.html">Why TeX is not WYSIWYG</a>” +<p/><p/>“<a href="FAQ-notWYSIWYG.html">Why TeX is not WYSIWYG</a>” outlines the reasons (or excuses) for the huge disparity of user interface between “typical” TeX environments and commercial word processors. -<p>Nowadays, at last, there is a range of tools available that try either +<p/>Nowadays, at last, there is a range of tools available that try either to bridge or to close the gap. One range modestly focuses on providing the user with a legible source document. At the other extreme we have <a href="http://www.texmacs.org"><i>TeXmacs</a></i>, @@ -22,7 +22,7 @@ printed output, but you have the possibility of entering arbitrary LaTeX code. If you use constructs that LyX does not understand, it will just display them as source text marked red, but will properly export them. -<p>Since a lot of work is needed to create an editor from scratch that +<p/>Since a lot of work is needed to create an editor from scratch that actually is good at editing (as well as catering for TeX), it is perhaps no accident that several approaches have been implemented using the extensible <i>emacs</i> editor. The low end of the @@ -38,7 +38,7 @@ tools prettifying your input, we have the <i>emacs</i> package the WYSIWYG part of its work by replacing single TeX tokens and accented letter sequences with appropriate-looking characters on the screen. -<p>A different type of tool focuses on making update and access to +<p/>A different type of tool focuses on making update and access to previews of the typeset document more immediate. A recent addition in several viewers, editors and TeX executables are so-called ‘source specials’ for cross-navigation. When TeX compiles a @@ -47,7 +47,7 @@ line into the typeset output. The markers are interpreted by the DVI previewer which can be made to let its display track the page corresponding to the editor input position, or to let the editor jump to a source line corresponding to a click in the preview window. -<p>An <i>emacs</i> package that combines this sort of editor movement +<p/>An <i>emacs</i> package that combines this sort of editor movement tracking with automatic fast recompilations (through the use of dumped formats) is <a href="http://pauillac.inria.fr/whizzytex/"><i>WhizzyTeX</a></i> @@ -57,7 +57,7 @@ same author. A simpler package in a similar spirit is called use of a continuously running copy of TeX (under the moniker of <code>TeX daemon</code>) instead of dumping formats to achieve its speed. -<p>Another <i>emacs</i> package called +<p/>Another <i>emacs</i> package called <a href="http://preview-latex.sourceforge.net"><i>preview-latex</a></i> tries to solve the problem of visual correlation between source and previews in a @@ -70,7 +70,7 @@ position the source text is displayed while editing rather than the preview. This approach is more or less a hybrid of the source prettifying and fast preview approaches since it works in the source buffer but uses actual previews rendered by LaTeX. -<p>A more ambitious contender is called TeXlite. This +<p/>A more ambitious contender is called TeXlite. This 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 @@ -78,12 +78,12 @@ 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. -<p>That many of these systems occupy slightly different niches can be +<p/>That many of these systems occupy slightly different niches can be seen by comparing the range of the <i>emacs</i>-based solutions ranging from syntax highlighting to instant previewing: all of them can be activated at the same time without actually interfering in their respective tasks. -<p>The different approaches offer various choices differing in the +<p/>The different approaches offer various choices differing in the immediacy of their response, the screen area they work on (source or separate window), degree of correspondance of the display to the final output, and the balance they strike between visual aid and visual @@ -92,5 +92,5 @@ distraction. <dt><tt><i>preview-latex</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/preview-latex/">support/preview-latex/</a> <dt><tt><i>texmacs</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/systems/unix/TeXmacs/">systems/unix/TeXmacs/</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=WYGexpts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=WYGexpts</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=WYGexpts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=WYGexpts</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-abspos.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-abspos.html index 1fd200c5de7..34d7cedaf42 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-abspos.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-abspos.html @@ -2,18 +2,18 @@ <title>UK TeX FAQ -- question label abspos</title> </head><body> <h3>Putting things at fixed positions on the page</h3> -<p>TeX’s model of the world is (broadly speaking) that the author +<p/>TeX’s model of the world is (broadly speaking) that the author writes text, and TeX and its macros decide how it all fits on the page. This is not good news for the author who has, from whatever source, a requirement that certain things go in exactly the right place on the page. -<p>There <em>are</em> places on the page, from which things may be hung, +<p/>There <em>are</em> places on the page, from which things may be hung, and two LaTeX packages allow you position things relative to such points, thus providing a means of absolute positioning. -<p>The <i>textpos</i> package aids the construction of pages from +<p/>The <i>textpos</i> package aids the construction of pages from “blobs”, dotted around over the page (as in a poster); you give it the location, and it places your typeset box accordingly. -<p>The <i>eso-pic</i> defines a “shipout picture” that covers the +<p/>The <i>eso-pic</i> defines a “shipout picture” that covers the page. The user may add <code>picture</code>-mode commands to this picture, which of course can include box placements as well as the other rather stilted commands of <code>picture</code>-mode. @@ -30,5 +30,5 @@ must therefore also be available.) <dt><tt><i>everyshi.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse</a>) <dt><tt><i>textpos.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textpos.zip">macros/latex/contrib/textpos</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textpos.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textpos/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=abspos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=abspos</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=abspos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=abspos</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-acrobat.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-acrobat.html index 0f2afca46bc..da4bb7af6b0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-acrobat.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-acrobat.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label acrobat</title> </head><body> <h3>Making Acrobat PDF documents from (La)TeX</h3> -<p>There are three general routes to PDF output: Adobe’s original +<p/>There are three general routes to PDF output: Adobe’s original ‘distillation’ route (via PostScript output), conversion of a DVI file, and the use of a direct PDF generator such as <a href="FAQ-whatpdftex.html">PDFTeX</a>) or MicroPress’s VTeX (which comes both as a <a href="FAQ-commercial.html">commercial version</a> for Windows PCs, and as a <a href="FAQ-TeXsystems.html">‘free’ version)</a> for OS/2 and Linux systems). -<p>For simple documents (with no hyper-references), you can either +<p/>For simple documents (with no hyper-references), you can either <ul> <li> process the document in the normal way, produce PostScript output and distill it; @@ -27,7 +27,7 @@ MicroPress’s VTeX (which comes both as a unsupported, for Linux or OS/2) has wider graphics capability, dealing with encapsulated PostScript and some in-line PostScript. </ul> -<p>To translate all the LaTeX cross-referencing into Acrobat +<p/>To translate all the LaTeX cross-referencing into Acrobat 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 @@ -44,23 +44,23 @@ Both <i>dvips</i> and Y&Y’s <i>DVIPSONE</i> can translate the DVI with these <code>\</code><code>special</code> commands into PostScript acceptable to Distiller, and <i>dvipdfm</i> has <code>\</code><code>special</code> commands of its own. -<p>If you use Plain TeX, the <a href="FAQ-eplain.html">Eplain macros</a> can +<p/>If you use Plain TeX, the <a href="FAQ-eplain.html">Eplain macros</a> can help you create PDF documents with hyper-references. It can operate using PDFTeX primitives, or <code>\</code><code>special</code> commands for the <i>dvipdfm</i> DVI driver. -<p>While there is no free implementation of all of <i>Adobe</i> +<p/>While there is no free implementation of all of <i>Adobe</i> <i>Distiller</i>’s functionality, any but the very oldest versions of <i>Ghostscript</i> provide pretty reliable distillation (but beware of the problems with <a href="FAQ-dvips-pdf.html"><i>dvips</i> output for distillation</a>). -<p>For viewing (and printing) the resulting files, Adobe’s +<p/>For viewing (and printing) the resulting files, Adobe’s <i>Acrobat</i> <i>Reader</i> is available for a fair range of platforms; for those for which Adobe’s reader is unavailable, remotely current versions of <i>ghostscript</i> combined with <i>gv</i>, <i>GSview</i> (or even the unsupported <i>ghostview</i>) can display and print PDF files, as can <i>xpdf</i>. -<p>In many circumstances, <i>Ghostscript</i> combined with a viewer +<p/>In many circumstances, <i>Ghostscript</i> combined with a viewer application is actually preferable to Acrobat Reader. For example, on Windows Acrobat Reader locks the <code>.pdf</code> file it’s displaying: this makes the traditional (and highly effective) (La)TeX development @@ -72,12 +72,12 @@ mistake. <a href="ftp://ftp.adobe.com/pub/adobe/acrobatreader">ftp://ftp.adobe.com/pub/adobe/acrobatreader</a> <dt><tt><i>dvipdfm</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.zip">dviware/dvipdfm</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfm/">browse</a>) <dt><tt><i>dvipdfmx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfmx.zip">dviware/dvipdfmx</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfmx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfmx/">browse</a>) -<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/ghostscript/">nonfree/support/ghostscript/</a> +<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/">support/ghostscript/</a> <dt><tt><i>ghostview</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/gnu/ghostview/">support/ghostscript/gnu/ghostview/</a> <dt><tt><i>GSview</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/ghostscript/ghostgum/">nonfree/support/ghostscript/ghostgum/</a> -<dt><tt><i>gv</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/gv.zip">support/gv</a> (<a href="ftp://cam.ctan.org/tex-archive/support/gv.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/gv/">browse</a>) +<dt><tt><i>gv</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/gv/">support/gv/</a> <dt><tt><i>hyper.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyper.zip">macros/latex/contrib/hyper</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyper.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyper/">browse</a>) <dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=acrobat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=acrobat</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=acrobat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=acrobat</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-actinarg.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-actinarg.html index 1096d750a62..c4896bbf060 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-actinarg.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-actinarg.html @@ -2,19 +2,19 @@ <title>UK TeX FAQ -- question label actinarg</title> </head><body> <h3>Active characters in command arguments</h3> -<p>Occasionally, it’s nice to make one or two characters active in the +<p/>Occasionally, it’s nice to make one or two characters active in the argument of a command, to make it easier for authors to code the arguments. -<p>Active characters <em>can</em> be used safely in such situations; but +<p/>Active characters <em>can</em> be used safely in such situations; but care is needed. -<p>An example arose while this answer was being considered: an aspirant +<p/>An example arose while this answer was being considered: an aspirant macro writer posted to <i>comp.text.tex</i> asking for help to make <code>#</code> and <code>b</code> produce musical sharp and flat signs, respectively, in a macro for specifying chords. -<p>The first problem is that both <code>#</code> and <code>b</code> have rather important uses +<p/>The first problem is that both <code>#</code> and <code>b</code> have rather important uses elsewhere in TeX (to say the least!), so that the characters can only be made active while the command is executing. -<p>Using the techniques discussed in +<p/>Using the techniques discussed in “<a href="FAQ-activechars.html">characters as commands</a>”, we can define: <blockquote> @@ -55,7 +55,7 @@ split in two. So we write: </blockquote><p> and we can use the command as <code>\</code><code>chord{F#}</code> or <code>\</code><code>chord{Bb minor}</code>. -<p>Two features of the coding are important: +<p/>Two features of the coding are important: <ul> <li> <code>\</code><code>begingroup</code> in <code>\</code><code>chord</code> opens a group that is closed by <code>\</code><code>endgroup</code> in <code>\</code><code>Xchord</code>; this group limits the change of @@ -65,12 +65,12 @@ and we can use the command as <code>\</code><code>chord{F#}</code> or <em>not</em> active when it’s being defined, so that the use of <code>#1</code> doesn’t require any special attention. </ul> -<p>Note that the technique used in such macros as <code>\</code><code>chord</code>, here, is +<p/>Note that the technique used in such macros as <code>\</code><code>chord</code>, here, is analagous to that used in such commands as <code>\</code><code>verb</code>; and, in just the same way as <code>\</code><code>verb</code> (see “<a href="FAQ-verbwithin.html"><code>\</code><code>verb</code> doesn’t work in arguments</a>”), <code>\</code><code>chord</code> won’t work inside the argument of another command (the error messages, if they appear at all, will probably be rather odd). -<p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=actinarg">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=actinarg</a> +<p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=actinarg">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=actinarg</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-activechars.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-activechars.html index 5cc1b11adac..3603f16be4e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-activechars.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-activechars.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label activechars</title> </head><body> <h3>Defining characters as macros</h3> -<p>Single characters can act as macros (defined commands), and both +<p/>Single characters can act as macros (defined commands), and both Plain TeX and LaTeX define the character “<code>~</code>” as a “non-breakable space”. A character is made definable, or “active”, by setting its <em>category code</em> (catcode) to be <code>\</code><code>active</code> (13): <code>\catcode‘_=\active</code>. -<p>Any character could, in principle, be activated this way and defined +<p/>Any character could, in principle, be activated this way and defined as a macro (<code>\</code><code>def</code><code>_{</code><code>\</code><code>_</code><code>}</code> — the simple answer to <a href="FAQ-underscore.html">using underscores</a>), but you must be @@ -17,7 +17,7 @@ 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. -<p>To define the character “<code>z</code>” as a command, one would say something +<p/>To define the character “<code>z</code>” as a command, one would say something like: <blockquote> <pre> @@ -32,7 +32,7 @@ a letter; the space is therefore not necessary — “<code>\defz</code> choose to retain the space, for what little clarity we can manage.) Some LaTeX packages facilitate such definitions. For example, the <i>shortvrb</i> package with its <code>\</code><code>MakeShortVerb</code> command. -<p>TeX uses category codes to interpret characters as they are read +<p/>TeX uses category codes to interpret characters as they are read from the input. <em>Changing a catcode value will not affect characters that have already been read</em>. @@ -48,9 +48,9 @@ files using the <i>shortvrb</i> package to define <code>|...|</code> as a shorthand for <code>\</code><code>verb</code><code>|...|</code>. But <code>|</code> is also used in the preambles of tabular environments, so that tables in -<code>.dtx</code> files can only have vertical line separation between columns by -employing special measures of some sort. -<p>Another consequence is that catcode assignments made +<code>.dtx</code> files can only have vertical line separation between +columns by employing special measures of some sort. +<p/>Another consequence is that catcode assignments made in macros often don’t work as expected (see “<a href="FAQ-actinarg.html">Active characters in command arguments</a>”). For example, the definition @@ -95,7 +95,7 @@ explicitly changing a catcode: The two definitions have the same overall effect (the character is defined as a command, but the character does not remain active), except that the first defines a <code>\</code><code>global</code> command. -<p>For active characters to be used only in maths mode, it is much better +<p/>For active characters to be used only in maths mode, it is much better to leave the character having its ordinary catcode, but assign it a special active <em>maths code</em>, as with <blockquote> @@ -116,5 +116,5 @@ becomes accessible again if the character once again becomes active. <dt><tt><i>doc.sty</i></tt><dd>Distributed as part of the source of LaTeX, <a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.zip">macros/latex/base</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base/">browse</a>) <dt><tt><i>shortvrb.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) </dl> -<p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=activechars">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=activechars</a> +<p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=activechars">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=activechars</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-addtoreset.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-addtoreset.html index c0770eee25d..3fe06ce167f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-addtoreset.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-addtoreset.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label addtoreset</title> </head><body> <h3>Master and slave counters</h3> -<p>It’s common to have things numbered “per chapter” (for example, in +<p/>It’s common to have things numbered “per chapter” (for example, in the standard <i>book</i> and <i>report</i> classes, figures, tables and footnotes are all numbered thus). The process of resetting is done automatically, when the “master” counter is stepped (when the <code>\</code><code>chapter</code> command that starts chapter <<i>n</i>> happens, the <code>chapter</code> counter is stepped, and all the dependent counters are set to zero). -<p>How would you do that for yourself? You might want to number +<p/>How would you do that for yourself? You might want to number algorithms per section, or corrollaries per theorem, for example. If you’re defining these things by hand, you declare the relationship when you define the counter in the first place: @@ -18,17 +18,17 @@ when you define the counter in the first place: </blockquote><p> says that every time counter <<i>master</i>> is stepped, counter <<i>new-name</i>> will be reset. -<p>But what if you have an uncooperative package, that defines the +<p/>But what if you have an uncooperative package, that defines the objects for you, but doesn’t provide a programmer interface to make the counters behave as you want? -<p>The <code>\</code><code>newcounter</code> command uses a LaTeX internal command, and you +<p/>The <code>\</code><code>newcounter</code> command uses a LaTeX internal command, and you can also use it: <blockquote> <code>\</code><code>@addtoreset{</code><em>new-name</em><code>}{</code><em>master</em><code>}</code> </blockquote><p> (but remember that it needs to be between <code>\</code><code>makeatletter</code> and <code>\</code><code>makeatother</code>, or in a package of your own). -<p>The <i>chngcntr</i> package encapsulates the <code>\</code><code>@addtoreset</code> +<p/>The <i>chngcntr</i> package encapsulates the <code>\</code><code>@addtoreset</code> command into a command <code>\</code><code>counterwithin</code>. So: <blockquote> <pre> @@ -51,7 +51,7 @@ much any such counter-within-another; if you’re not using the <i>chngcntr</i>, refer to the answer to <a href="FAQ-the-commands.html">redefining counters’ <code>\</code><code>the-</code>commands</a> for the necessary techniques. -<p>Note that the technique doesn’t work if the master counter is <code>page</code>, +<p/>Note that the technique doesn’t work if the master counter is <code>page</code>, the number of the current page. The <code>page</code> counter is stepped deep inside the output routine, which usually gets called some time after the text for the new page has started to appear: so special @@ -70,6 +70,5 @@ warnings about labels changing. <dt><tt><i>chngcntr.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/chngcntr.sty">macros/latex/contrib/misc/chngcntr.sty</a> <dt><tt><i>perpage.sty</i></tt><dd>Distributed as part <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse</a>) </dl> -<p> -<p><p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=addtoreset">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=addtoreset</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=addtoreset">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=addtoreset</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-adobetypen.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-adobetypen.html index be29d0f560d..5ef701d5a78 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-adobetypen.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-adobetypen.html @@ -3,28 +3,30 @@ </head><body> <h3>Adobe font formats</h3> <!-- type1 type3 --> -<p>Adobe has specified a number of formats for files to represent fonts -in PostScript files; this question doesn’t attempt to be encyclopaedic, but -we’ll discuss the two formats most commonly encountered in the -(La)TeX context, types 1 and 3. -<p>Adobe Type 1 format specifies a means to represent outlines of the glyphs +<p/>Adobe has specified a number of formats for files to represent fonts +in PostScript files; this question doesn’t attempt to be encyclopaedic, so +we only discuss the two formats most commonly encountered in the +(La)TeX context, types 1 and 3. In particular, we don’t discuss the +OpenType format, whose has many advantages are somewhat ahead of the +TeX world’s mainstream (at time of writing). +<p/>Adobe Type 1 format specifies a means to represent outlines of the glyphs in a font. The ‘language’ used is closely restricted, to ensure that the font is rendered as quickly as possible. (Or rather, as quickly as possible with Adobe’s technology at the time the specification was written: the structure could well be different if it were specified now.) The format has long been the basis of the digital type-foundry -business, though things are showing signs of change. -<p> +business, though nowadays most new fonts are released in OpenType format. +<p/> -<p>In the (La)TeX context, Type 1 fonts are extremely important. Apart +<p/>In the (La)TeX context, Type 1 fonts are extremely important. Apart from their simple availability (there are thousands of commercial Type 1 text fonts around), the commonest reader for PDF files has long (in effect) <em>insisted</em> on -their use (see <a href="FAQ-dvips-pdf.html">PDF quality</a>). -<p>Type 3 fonts have a more forgiving specification. A wide range of -PostScript operators is permissible, including bitmaps operators. Type 3 +their use (see below). +<p/>Type 3 fonts have a more forgiving specification. A wide range of +PostScript operators is permissible, including bitmap specifiers. Type 3 is therefore the natural format to be used for programs such as <i>dvips</i> when they auto-generate something to represent Metafont-generated fonts in a PostScript file. It’s Adobe Acrobat Viewer’s @@ -33,10 +35,12 @@ inreasingly unattractive, in recent years. If you have a PDF document in which the text looks fuzzy and uneven in Acrobat Reader, ask Reader for the <code>File</code>-> <code>Document Properties</code>-> -<code>Fonts ...</code>, and it will show some font or other as “Type 3” -(usually with encoding “Custom”). (This problem has disappeared -with version 6 of Acrobat Reader.) -<p>Type 3 fonts should not entirely be dismissed, however. Acrobat +<code>Fonts ...</code>, and it will likely show some font or other as +“Type 3” (usually with encoding “Custom”). The problem has +disappeared with version 6 of Acrobat Reader. See +<a href="FAQ-dvips-pdf.html">PDF quality</a> for a discussion of +the issue, and for ways of addressing it. +<p/>Type 3 fonts should not entirely be dismissed, however. Acrobat Reader’s failure with them is entirely derived from its failure to use the anti-aliasing techniques common in TeX-ware. Choose a different set of PostScript graphical operators, and you can make pleasing @@ -44,5 +48,5 @@ Type 3 fonts that don’t “annoy” Reader. For example, you may change colour within a Type 1 font glyph, but there’s no such restriction on a Type 3 font, which opens opportunities for some startling effects. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=adobetypen">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=adobetypen</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=adobetypen">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=adobetypen</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-algorithms.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-algorithms.html index c493b9d9395..90868d69ce4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-algorithms.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-algorithms.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label algorithms</title> </head><body> <h3>Typesetting pseudocode in LaTeX</h3> -<p>There is no consensus on the ‘right’ way to typeset pseudocode. +<p/>There is no consensus on the ‘right’ way to typeset pseudocode. Consequently, there are a variety of LaTeX packages to choose from for producing æsthetically pleasing pseudocode listings. -<p>Pseudocode differs from actual program listings in that it lacks +<p/>Pseudocode differs from actual program listings in that it lacks strict syntax and semantics. Also, because pseudocode is supposed to be a clear expression of an algorithm it may need to incorporate mathematical notation, figures, tables, and other LaTeX features @@ -13,12 +13,12 @@ that do not appear in conventional programming languages. <a href="FAQ-codelist.html">Typesetting program listings</a> is described elsewhere. -<p>You can certainly create your own environment for typesetting +<p/>You can certainly create your own environment for typesetting pseudocode using, for example, the <code>tabbing</code> or <code>list</code> environments — it’s not difficult, but it may prove boring. So it’s worth trying the following packages, all designed specifically for typesetting pseudocode. -<p>The <i>algorithms</i> bundle (which contains packages +<p/>The <i>algorithms</i> bundle (which contains packages <i>algorithm</i> and <i>algorithmic</i>, both of which are needed for ordinary use) has a simple interface and produces fairly nice output. It provides primitives for statements, which can contain @@ -31,7 +31,7 @@ uses the facilities of the <i>float</i> package to number algorithms sequentially, enable algorithms to float like figures or tables, and support including a List of Algorithms in a document’s front matter. -<p>Packages in the <i>algorithmicx</i> bundle are similiar both in +<p/>Packages in the <i>algorithmicx</i> bundle are similiar both in concept and output form to <i>algorithmic</i> but additionally provide support for adding new keywords and altering the formatting. It provides the <i>algpseudocode</i> package which is (almost) a @@ -41,31 +41,31 @@ differently from <i>algpseudocode</i>, and puts command arguments in maths mode instead of text mode. There is no floating environment but <i>algorithmicx</i>, like <i>algorithmic</i>, is compatible with the <i>algorithm</i> package. -<p>The <i>alg</i> package, like <i>algorithms</i>, offers a +<p/>The <i>alg</i> package, like <i>algorithms</i>, offers a floating algorithm environment with all of the ensuing niceties. <i>alg</i>, however, can caption its floats in a variety of (natural) languages. In addition, <i>alg</i> unlike <i>algorithms</i>, makes it easy to add new constructs. -<p>The <i>newalg</i> package has a somewhat similar interface to +<p/>The <i>newalg</i> package has a somewhat similar interface to <i>algorithms</i>, but its output is designed to mimic the rather pleasant typesetting used in the book “<em>Introduction to Algorithms</em>” by Corman, Leiserson, Rivest and Stein. Unfortunately, <i>newalg</i> does not support a floating environment or any customisation of the output. -<p>“<em>Bona fide</em>” use of the style of “Introduction to +<p/>“<em>Bona fide</em>” use of the style of “Introduction to Algorithms” may be achieved with Cormen’s own <i>clrscode</i>: this is the package as used in the second edition of the book. -<p>Similarly, the style of +<p/>Similarly, the style of “<em>Combinatorial Algorithms: Generation, Enumeration and Search</em>” is supported by the <i>pseudocode</i> package, written by the authors of the book. It has the common ‘Pascal-like’ style, and has some interesting constructs for what one thinks of as Pascal blocks. -<p>The <i>algorithm2e</i> is of very long standing, and is widely used +<p/>The <i>algorithm2e</i> is of very long standing, and is widely used and recommended. It loads the <i>float</i> package to provide the option of floating algorithm descriptions, but you can always use the “<code>H</code>” option of <i>float</i> to have the algorithm appear “where you write it”. -<p>The usage of the <i>program</i> package is a little different from +<p/>The usage of the <i>program</i> package is a little different from that of the other packages. It typesets programs in maths mode instead of text mode; and linebreaks are significant. <i>program</i> lacks a floating environment but does number @@ -73,7 +73,7 @@ algorithms like <i>alg</i> and <i>algorithms</i>. Customisation and extension are not supported. Documentation of the <i>program</i> package (such as it is) appears in a file <i>program.msg</i> in the distribution. -<p>None of the above are perfect. The factors that should influence your +<p/>None of the above are perfect. The factors that should influence your choice of package include the output style you prefer, how much you need to extend or modify the set of keywords, and whether you require algorithms to float like figures and tables. @@ -103,5 +103,5 @@ algorithms to float like figures and tables. <dt><tt><i>program.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/program.zip">macros/latex/contrib/program</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/program.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/program/">browse</a>) <dt><tt><i>pseudocode.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pseudocode.zip">macros/latex/contrib/pseudocode</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pseudocode.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pseudocode/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=algorithms">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=algorithms</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=algorithms">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=algorithms</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-alreadydef.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-alreadydef.html index 4bd4869922e..748ce8e51cc 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-alreadydef.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-alreadydef.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label alreadydef</title> </head><body> <h3>Package reports “command already defined”</h3> -<p>You load a pair of packages, and the second reports that one of the +<p/>You load a pair of packages, and the second reports that one of the commands it defines is already present. For example, both the <i>txfonts</i> and <i>amsmath</i> define a command <code>\</code><code>iint</code> (and <code>\</code><code>iiint</code> and so on); so @@ -29,13 +29,13 @@ double integral symbol that doesn’t need to be “faked” in the symbol packages, every one of which defines the same symbol, you are likely to experience the problem in a big way (<code>\</code><code>euro</code> is a common victim). -<p>There are similar cases where one package redefines another’s command, +<p/>There are similar cases where one package redefines another’s command, but no error occurs because the redefining package doesn’t use <code>\</code><code>newcommand</code>. Often, in such a case, you only notice the change because you assume the definition given by the first package. The <i>amsmath</i>–<i>txfonts</i> packages are just such a pair; <i>txfonts</i> doesn’t provoke errors. -<p>You may deal with the problem by saving and restoring the command. +<p/>You may deal with the problem by saving and restoring the command. Macro programmers may care to do this for themselves; for the rest of us, there’s the package <i>savesym</i>. The sequence: <blockquote> @@ -50,12 +50,12 @@ us, there’s the package <i>savesym</i>. The sequence: does the job; restoring the <i>amsmath</i> version of the command, and making the <i>txfonts</i> version of the command available as <code>\</code><code>TXFiint</code>. -<p>Documentation of <i>savesym</i> doesn’t amount to much: the only +<p/>Documentation of <i>savesym</i> doesn’t amount to much: the only commands are <code>\</code><code>savesymbol</code> and <code>\</code><code>restoresymbol</code>, as noted above. <dl> <dt><tt><i>amsmath.sty</i></tt><dd>Part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>) <dt><tt><i>savesym.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/savesym/savesym.sty">macros/latex/contrib/savesym/savesym.sty</a> <dt><tt><i>txfonts.sty</i></tt><dd>Part of <a href="ftp://cam.ctan.org/tex-archive/fonts/txfonts.zip">fonts/txfonts</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/txfonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/txfonts/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=alreadydef">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=alreadydef</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=alreadydef">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=alreadydef</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-altabcr.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-altabcr.html index 5f4f9f0db80..943c835ebf6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-altabcr.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-altabcr.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label altabcr</title> </head><body> <h3>Alignment tab changed to <code>\</code><code>cr</code></h3> -<p>This is an error you may encounter in LaTeX when a tabular +<p/>This is an error you may encounter in LaTeX when a tabular environment is being processed. “Alignment tabs” are the <code>&</code> signs that separate the columns of a tabular; so the error message @@ -21,11 +21,33 @@ could arise from a simple typo, such as: \end{tabular} </pre> </blockquote><p> -where the second <code>&</code> in the first line of the table is more than the -two-column <code>ll</code> column specification can cope with — an extra -“<code>l</code>” in that solves the problem. (As a result of the error, -“<code>jim</code>” will be moved to a row of his own.) -<p>Rather more difficult to spot is the occurrence of the error when +where the second <code>&</code> in the first line of the table is more than the +two-column <code>ll</code> column specification can cope with. In this +case, an extra “<code>l</code>” in that solves the problem. (If you +continue from the error in this case, “<code>jim</code>” will be moved +to a row of his own.) Another simple typo that can provoke the error +is: +<blockquote> +<pre> +\begin{tabular}{ll} + hello & there + goodbye & now +\end{tabular} +</pre> +</blockquote><p> +where the ‘\bsbs’ has been missed from the first line of the table. +In this case, if you continue from the error, you will find that +LaTeX has made a table equivalent to: +<blockquote> +<pre> +\begin{tabular}{ll} + hello & there goodbye\\ + now +\end{tabular} +</pre> +</blockquote><p> +(with the second line of the table having only one cell). +<p/>Rather more difficult to spot is the occurrence of the error when you’re using alignment instructions in a “<code>p</code>” column: <blockquote> <pre> @@ -44,12 +66,12 @@ the problem here (as explained in “<code>happy</code>” appears in a new line of the second column, and the following <code>&</code> appears to LaTeX just like the second <code>&</code> in the first example above. -<p>Get rid of the error in the way described in +<p/>Get rid of the error in the way described in <a href="FAQ-tabcellalign.html">tabular cell alignment</a> — either use <code>\</code><code>tabularnewline</code> explicitly, or use the <code>\</code><code>RBS</code> trick described there. <dl> <dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=altabcr">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=altabcr</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=altabcr">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=altabcr</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-amfonts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-amfonts.html index 8d02c4e874d..fc542341fc2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-amfonts.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-amfonts.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label amfonts</title> </head><body> <h3>Where are the <code>am</code> fonts?</h3> -<p>One <em>still</em> occasionally comes across a request for the <i>am</i> +<p/>One <em>still</em> occasionally comes across a request for the <i>am</i> series of fonts. The initials stood for ‘Almost [Computer] Modern’, and they were the predecessors of the Computer Modern fonts that we all know and love (or hate) @@ -17,6 +17,6 @@ them by means of virtual fonts; however, most drivers let you have a configuration file in which you can specify font substitutions. If you specify that every <i>am</i> font should be replaced by its corresponding <i>cm</i> font, the output should be almost correct. -<p> -<p><p><p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=amfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=amfonts</a> +<p/> +<p/><p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=amfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=amfonts</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ant.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ant.html index 45b6f0e7b7c..9fda82f2995 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ant.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ant.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label ant</title> </head><body> <h3>The ANT typesetting system</h3> -<p>Achim Blumensath’s <a href="http://ant.berlios.de">ANT</a> project, +<p/>Achim Blumensath’s <a href="http://ant.berlios.de">ANT</a> project, in contrast to <i>NTS</i>, aims not to replicate TeX with a different implementation technique, but rather to provide a replacement for TeX which uses TeX-like typesetting algorithms in a very different programming environment. ANT remains under development, but it is now approaching the status of a usable typesetting system. -<p>ANT’s markup language is immediately recognisable to the +<p/>ANT’s markup language is immediately recognisable to the (La)TeX user, but the scheme of implementing design in ANT’s own implementation language (presently <i>OCaml</i>) comes as a pleasant surprise to the jaded FAQ @@ -19,5 +19,5 @@ derive from the design language being the same as the markup language. <dl> <dt><tt><i>ANT</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/ant.zip">systems/ant</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/ant.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/ant/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ant">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ant</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ant">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ant</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-appendix.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-appendix.html index 8cbbdb68736..89083a05049 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-appendix.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-appendix.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label appendix</title> </head><body> <h3>Appendixes</h3> -<p>LaTeX provides an exceedingly simple mechanism for appendixes: the +<p/>LaTeX provides an exceedingly simple mechanism for appendixes: the command <code>\</code><code>appendix</code> switches the document from generating sections (in <i>article</i> class) or chapters (in <i>report</i> or <i>book</i> classes) to producing appendixes. Section or chapter @@ -24,17 +24,17 @@ to alphabetic. So: would be typeset (in an <i>article</i> document) something like: <blockquote> <b>1 My inspiration</b> -<p>... -<p><b>2 Developing the inspiration</b> -<p>... -<p><b>A How I became inspired</b> -<p>... +<p/>... +<p/><b>2 Developing the inspiration</b> +<p/>... +<p/><b>A How I became inspired</b> +<p/>... </blockquote><p> which is quite enough for many ordinary purposes. Note that, once you’ve switched to typesetting appendixes, LaTeX provides you with no way back — once you’ve had an appendix, you can no longer have an “ordinary” <code>\</code><code>section</code> or <code>\</code><code>chapter</code>. -<p>The <i>appendix</i> provides several ways of elaborating on this +<p/>The <i>appendix</i> provides several ways of elaborating on this simple setup. Straightforward use of the package allows you to have a separate heading, both in the body of the document and the table of contents; this would be achieved by @@ -51,7 +51,7 @@ The <code>\</code><code>appendixpage</code> command adds a separate title &ldquo above the first appendix, and <code>\</code><code>addappheadtotoc</code> adds a similar title to the table of contents. These simple modifications cover many people’s needs about appendixes. -<p>The package also provides an <code>appendices</code> environment, +<p/>The package also provides an <code>appendices</code> environment, which provides for fancier use. The environment is best controlled by package options; the above example would be achieved by <blockquote> @@ -67,7 +67,7 @@ The great thing that the <code>appendices</code> environment gives you, is that once the environment ends, you can carry on with sections or chapters as before — numbering isn’t affected by the intervening appendixes. -<p>The package provides another alternative way of setting appendixes, as +<p/>The package provides another alternative way of setting appendixes, as inferior divisions in the document. The <code>subappendices</code> environment allows you to put separate appendixes for a particular section, coded as <code>\</code><code>subsection</code>s, or for a particular chapter, coded @@ -90,15 +90,15 @@ as <code>\</code><code>section</code>s. So one might write: Which will produce output something like: <blockquote> <b>1 My inspiration</b> -<p>... -<p><b>1.A How I became inspired</b> -<p>... -<p><b>2 Developing the inspiration</b> -<p>... +<p/>... +<p/><b>1.A How I became inspired</b> +<p/>... +<p/><b>2 Developing the inspiration</b> +<p/>... </blockquote><p> -<p>There are many other merry things one may do with the package; the +<p/>There are many other merry things one may do with the package; the user is referred to the package documentation for further details. -<p>The <i>memoir</i> class includes the facilities of the +<p/>The <i>memoir</i> class includes the facilities of the <i>appendix</i> package. The <i>KOMA-script</i> classes offer a <code>\</code><code>appendixprefix</code> command for manipulating the appearance of appendixes. <dl> @@ -106,5 +106,5 @@ user is referred to the package documentation for further details. <dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=appendix">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=appendix</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=appendix">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=appendix</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-archives.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-archives.html index c24be742466..92e541b2fb0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-archives.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-archives.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label archives</title> </head><body> <h3>Repositories of TeX material</h3> -<p>To aid the archiving and retrieval of of TeX-related files, a +<p/>To aid the archiving and retrieval of of TeX-related files, a TUG working group developed the Comprehensive TeX Archive Network (CTAN). Each CTAN site has identical material, and maintains authoritative versions of its material. These @@ -10,24 +10,38 @@ collections are extensive; in particular, almost everything mentioned in this FAQ is archived at the CTAN sites (see the lists of software at the end of each answer). -<p>The CTAN sites are currently \FTP{dante.ctan.org} (Germany), -\FTP{cam.ctan.org} (UK) and \FTP{tug.ctan.org} (USA). -The organisation of TeX files on all -CTAN sites is identical and starts at -<i>tex-archive/</i>. Each CTAN node may also be accessed via +<p/> + The CTAN sites are + <a href="ftp://dante.ctan.org/tex-archive">Dante (Germany)</a>, + <a href="ftp://cam.ctan.org/tex-archive">Cambridge (UK)</a> and + <a href="ftp://tug.ctan.org/tex-archive">TUG (USA)</a>; the links are to + the root of the CTAN tree, above which the layout is + identical at each site. +<p/>The TeX files at each CTAN node may also be accessed via the Web at URLs <a href="http://www.dante.de/tex-archive">http://www.dante.de/tex-archive</a>, <a href="http://www.tex.ac.uk/tex-archive">http://www.tex.ac.uk/tex-archive</a> and <a href="http://www.ctan.org/tex-archive">http://www.ctan.org/tex-archive</a> respectively, but not all CTAN mirrors are Web-accessible. -As a matter of course, to reduce network load, +<p/>As a matter of course, to reduce network load, please use the CTAN site or mirror closest to you. A complete and current list of CTAN sites and known mirrors is available as file <a href="ftp://cam.ctan.org/tex-archive/CTAN.sites">CTAN.sites</a> on the archives themselves. -<p>For details of how to find files at CTAN sites, see +<p/>Better still, the script behind <a href="http://mirror.ctan.org/">http://mirror.ctan.org/</a> will +cunningly choose a “nearby” mirror for you, using information from +the database ‘behind’ <a href="ftp://cam.ctan.org/tex-archive/CTAN.sites">CTAN.sites</a>; at present it uses +<code>ftp</code> protocol for transfers, but the intention is to convert +it to using <code>http</code> (web) protocol in the near future. +<p/>To access a particular thing through the <code>mirror.ctan.org</code> +mechanism, simply place the CTAN path after the base +URL; so +<a href="http://mirror.ctan.org/macros/latex/contrib/footmisc/">http://mirror.ctan.org/macros/latex/contrib/footmisc/</a> will +connect you to the <i>footmisc</i> directory — note that the +<i>tex-archive</i> part of the CTAN path isn’t needed. +<p/>For details of how to find files at CTAN sites, see “<a href="FAQ-findfiles.html">finding (La)TeX files</a>”. -<p>The TeX user who has no access to any sort of +<p/>The TeX user who has no access to any sort of network may buy a copy of the archive as part of the -<a href="FAQ-CD.html">TeX Live distribution</a>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=archives">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=archives</a> +<a href="FAQ-CD.html">TeX-live distribution</a>. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=archives">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=archives</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-askquestion.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-askquestion.html index 45a5b3e0f5a..f2f9211afd8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-askquestion.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-askquestion.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label askquestion</title> </head><body> <h3>How to ask a question</h3> -<p>You want help from the community at large; you’ve decided where you’re +<p/>You want help from the community at large; you’ve decided where you’re going to <a href="FAQ-gethelp.html">ask your question</a>, but how do you phrase it? -<p>Excellent “general” advice (how to ask questions of anyone) is +<p/>Excellent “general” advice (how to ask questions of anyone) is contained in <a href="http://catb.org/~esr/faqs/smart-questions.html">Eric Raymond’s article on the topic</a>. @@ -15,7 +15,7 @@ un-self-confident majority. It’s important to remember that you don&rsquo have a right to advice from the world, but that if you express yourself well, you will usually find someone who will be pleased to help. -<p>So how do you express yourself in the (La)TeX world? There aren’t +<p/>So how do you express yourself in the (La)TeX world? There aren’t any comprehensive rules, but a few guidelines may help in the application of your own common sense. <ul> @@ -24,7 +24,7 @@ application of your own common sense. operating system. Yes, TeX users need printers, but no, TeX users will typically <em>not</em> be <i>Foobar</i> systems managers. -<p> Similarly, avoid posing a question in a language that the majority +<p/> Similarly, avoid posing a question in a language that the majority of the group don’t use: post in Ruritanian to <i>de.comp.text.tex</i> and you may have a long wait before a German- and Ruritanian-speaking TeX expert notices your @@ -57,5 +57,5 @@ application of your own common sense. know <em>why</em> you’re doing something, just <em>what</em> you’re doing and where the problem is. </ul> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=askquestion</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsign.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsign.html index f456e10baab..de7322ecb64 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsign.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsign.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label atsign</title> </head><body> <h3>How to type an ‘@’ sign?</h3> -<p>Long ago, some packages used to make the ‘@’ sign active, so that +<p/>Long ago, some packages used to make the ‘@’ sign active, so that special measures were needed to type it. While those packages are still in principle available, few people use them, and those that do use them have ready access to rather good documentation. -<p>Ordinary people (such as the author of this FAQ) need only type +<p/>Ordinary people (such as the author of this FAQ) need only type ‘@’. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsign">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsign</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsign">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsign</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsigns.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsigns.html index 03ca954246c..f3aa3f6a649 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsigns.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atsigns.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label atsigns</title> </head><body> <h3><code>\</code><code>@</code> and <code>@</code> in macro names</h3> -<p>Macro names containing <code>@</code> are <em>internal</em> to LaTeX, and +<p/>Macro names containing <code>@</code> are <em>internal</em> to LaTeX, and without special treatment just don’t work in ordinary use. A nice example of the problems caused is discussed in <a href="FAQ-atvert.html"><code>\</code><code>@</code> in vertical mode</a>”. -<p>The problems users see are caused by copying bits of a class +<p/>The problems users see are caused by copying bits of a class (<code>.cls</code> file) or package (<code>.sty</code> file) into a document, or by including a class or package file into a LaTeX document by some means other than @@ -16,14 +16,16 @@ avoid clashes between its internal names and names that we would normally use in our documents. In order that these commands may work at all, <code>\</code><code>documentclass</code> and <code>\</code><code>usepackage</code> play around with the meaning of <code>@</code>. -<p>If you’ve included a file wrongly, you solve the problem by using the -correct command. -<p>If you’re using a fragment of a package or class, you may well feel +<p/>If you’ve included a file some other way (for example, using +<code>\</code><code>input</code>), you can probablysolve the problem by using the correct +command. +<p/>If you’re using a fragment of a package or class, you may well feel confused: books such as the first edition of the <a href="FAQ-books.html">The LaTeX Companion</a> are full of fragments of packages as examples for you to employ. -This problem has been solved in the second edition, and in addition, -all the examples from the <em>Companion</em> are now available on-line. +The second edition of the <em>Companion</em> makes clearer how you +should use these fragments, and in addition, the code of +all the examples is now available on CTAN. To see the technique in practice, look at the example below, from file <i>2-2-7.ltx</i> in the <em>Companion</em> examples directory: <blockquote> @@ -39,12 +41,12 @@ To see the technique in practice, look at the example below, from file </blockquote><p> (That example appears on page 29 of <em>The LaTeX Companion</em>, second edition.) -<p>The alternative is to treat all these fragments as a package proper, +<p/>The alternative is to treat all these fragments as a package proper, bundling them up into a <code>.sty</code> file and including them with <code>\</code><code>usepackage</code>; this way you hide your LaTeX internal code somewhere that LaTeX internal code is expected, which often looks ‘tidier’. <dl> <dt><tt><i>Examples from the Companion</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/examples/tlc2.zip">info/examples/tlc2</a> (<a href="ftp://cam.ctan.org/tex-archive/info/examples/tlc2.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/examples/tlc2/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsigns">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsigns</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsigns">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atsigns</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atvert.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atvert.html index 379e4e22925..f1761290a2d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atvert.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-atvert.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label atvert</title> </head><body> <h3><code>\</code><code>spacefactor</code> complaints</h3> -<p>The errors +<p/>The errors <pre> ! You can't use `\spacefactor' in vertical mode. \@->\spacefactor @@ -24,5 +24,5 @@ bites the LaTeX programmer who uses an internal command without taking “<a href="FAQ-atsigns.html"><code>@</code> in macro names</a>”, together with solutions. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atvert">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atvert</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atvert">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=atvert</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-backref.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-backref.html index d8def1f0f13..882a922f255 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-backref.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-backref.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label backref</title> </head><body> <h3>References from the bibliography to the citation</h3> -<p>A link (or at least a page reference), from the bibliography to the +<p/>A link (or at least a page reference), from the bibliography to the citing command, is often useful in large documents. -<p>Two packages support this requirement, <i>backref</i> and +<p/>Two packages support this requirement, <i>backref</i> and <i>citeref</i>. <i>Backref</i> is part of the <i>hyperref</i> bundle, and supports hyperlinks back to the citing command. <i>Citeref</i> is the older, and seems to rely on rather @@ -19,5 +19,5 @@ same anchor is less than appealing.) <dt><tt><i>backref.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>) <dt><tt><i>citeref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/citeref.zip">macros/latex/contrib/citeref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/citeref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/citeref/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=backref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=backref</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=backref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=backref</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-badhyph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-badhyph.html index 02c169f6c36..4ca66686b50 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-badhyph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-badhyph.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label badhyph</title> </head><body> <h3>Improper <code>\</code><code>hyphenation</code> will be flushed</h3> -<p>For example +<p/>For example <pre> ! Improper \hyphenation will be flushed. \'#1->{ @@ -19,10 +19,10 @@ -nez} </pre> in LaTeX. -<p>As mentioned in <a href="FAQ-nohyph.html">“hyphenation failures”</a>, +<p/>As mentioned in <a href="FAQ-nohyph.html">“hyphenation failures”</a>, words with accents in them may not be hyphenated. As a result, any such word is deemed improper in a <code>\</code><code>hyphenation</code> command. -<p>The solution is to use a font that contains the character in question, +<p/>The solution is to use a font that contains the character in question, and to express the <code>\</code><code>hyphenation</code> command in terms of that character; this “hides” the accent from the hyphenation mechanisms. LaTeX users can be achieved this by use of the <i>fontenc</i> @@ -31,5 +31,5 @@ font with the package, as in <code>\</code><code>usepackage[T1]{fontenc}</code>, accented-letter commands such as the <code>\’</code><code>e</code> in <code>\hyphenation{Ji-m\’</code><code>e-nez}</code> automatically become the single accented character by the time the hyphenation gets to look at it. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=badhyph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=badhyph</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=badhyph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=badhyph</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-balance.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-balance.html index 5224ff99625..f04c9d28794 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-balance.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-balance.html @@ -2,26 +2,26 @@ <title>UK TeX FAQ -- question label balance</title> </head><body> <h3>Balancing columns at the end of a document</h3> -<p>The <i>twocolumn</i> option of the standard classes causes +<p/>The <i>twocolumn</i> option of the standard classes causes LaTeX to set the text of a document in two columns. However, the last page of the document typically ends up with columns of different lengths — such columns are said to be “unbalanced”. Many (most?) people don’t like unbalanced columns. -<p>The simplest solution to the problem is to use the <i>multicol</i> +<p/>The simplest solution to the problem is to use the <i>multicol</i> package in place of the <i>twocolumn</i> option, as <i>multicol</i> balances the columns on the final page by default. However, the use of <i>multicol</i> does come at a cost: its special output routine disallows the use of in-column floats, though it does still permit full-width (e.g., <code>figure*</code> environment) floats. -<p>As a result, there is a constant push for a means of balancing columns +<p/>As a result, there is a constant push for a means of balancing columns at the end of a <i>twocolumn</i> document. Of course, the job can be done manually: <code>\</code><code>pagebreak</code> inserted at the appropriate place on the last page can often produce the right effect, but this seldom appeals, and if the last page is made up of automatically-generated text (for example, bibliography or index) inserting the command will be difficult. -<p>The <i>flushend</i> package offers a solution to this problem. It’s a +<p/>The <i>flushend</i> package offers a solution to this problem. It’s a somewhat dangerous piece of macro code, which patches one of the most intricate parts of the LaTeX kernel without deploying any of the safeguards discussed in <a href="FAQ-patch.html">patching commands</a>. @@ -30,9 +30,9 @@ The package only changes the behaviour at end document (its permits adjustment of the final balance; other packages in the bundle provide means for insertion of full width material in two-column documents. -<p>The <i>balance</i> package also patches the output routine +<p/>The <i>balance</i> package also patches the output routine (somewhat more carefully than <i>flushend</i>). -<p>The user should be aware that any of these packages are liable to +<p/>The user should be aware that any of these packages are liable to become confused in the presence of floats: if problems arise, manual adjustment of the floats in the document is likely to be necessary. It is this difficulty (what’s required in any instance can’t really be @@ -42,6 +42,6 @@ expressed in current LaTeX) that led the author of <dt><tt><i>balance.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/preprint.zip">macros/latex/contrib/preprint</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/preprint.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/preprint/">browse</a>) <dt><tt><i>flushend.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sttools.zip">macros/latex/contrib/sttools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sttools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sttools/">browse</a>) <dt><tt><i>multicol.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) -<p></dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=balance">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=balance</a> +<p/></dl> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=balance">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=balance</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-baselinepar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-baselinepar.html index ac4d3a411ea..0d1a560fea1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-baselinepar.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-baselinepar.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label baselinepar</title> </head><body> <h3>Only one <code>\</code><code>baselineskip</code> per paragraph</h3> -<p>The <code>\</code><code>baselineskip</code> is not (as one might hope) a property of a +<p/>The <code>\</code><code>baselineskip</code> is not (as one might hope) a property of a line, but of a paragraph. As a result, in a <code>10pt</code> (nominal) document (with a default <code>\</code><code>baselineskip</code> of <code>12pt</code>), a single character with a larger size, as: @@ -38,7 +38,7 @@ Next paragraph starts... </blockquote><p> will set the body of the first paragraph on the constricted <code>\</code><code>baselineskip</code> of the <code>\</code><code>footnotesize</code> comment. -<p>So, how to deal with these problems? The oversized (short) section is +<p/>So, how to deal with these problems? The oversized (short) section is typically corrected by a <em>strut</em>: this word comes from movable metal typography, and refers to a spacer that held the boxes (that contained the metal character shapes) apart. Every time you change @@ -57,7 +57,7 @@ are always going to cause problems; while you can strut larger text, ensuring that you strut every line will be tiresome, and there’s no such thing as a “negative strut” that pulls the lines together for smaller text. -<p>The only satisfactory way to deal with an extended insertion at a +<p/>The only satisfactory way to deal with an extended insertion at a different size is to set it off as a separate paragraph. A satisfactory route to achieving this is the <code>quote</code> environment, which sets its text modestly inset from the enclosing @@ -75,5 +75,5 @@ Paragraph text ... </blockquote><p> Such quote-bracketing also deals with the problem of a trailing comment on the paragraph. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=baselinepar">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=baselinepar</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=baselinepar">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=baselinepar</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibaccent.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibaccent.html index 743ad3855b3..6319f7c5ae2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibaccent.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibaccent.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label bibaccent</title> </head><body> <h3>Accents in bibliographies</h3> -<p>BibTeX not only has a tendency (by default) to mess about with the +<p/>BibTeX not only has a tendency (by default) to mess about with the <a href="FAQ-capbibtex.html">case of letters in your bibliography</a>, also makes a hash of accent commands: @@ -10,5 +10,5 @@ also makes a hash of accent commands: similar: enclose the troublesome sequence in braces, as “<code>{</code><code>\~n</code><code>}</code>”, in this example. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibaccent">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibaccent</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibaccent">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibaccent</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibinline.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibinline.html index 5e637b2650b..6bf4d75f2d8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibinline.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibinline.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label bibinline</title> </head><body> <h3>Putting bibliography entries in text</h3> -<p>This is a common requirement for journals and other publications in +<p/>This is a common requirement for journals and other publications in the humanities. Sometimes the requirement is for the entry to appear in the running text of the document, while other styles require that the entry appear in a footnote. -<p>Options for entries in running text are +<p/>Options for entries in running text are <ul> <li> The package <i>bibentry</i>, which puts slight restrictions on the format of entry that your <code>.bst</code> file generates, but is @@ -21,7 +21,7 @@ the entry appear in a footnote. styles that you may use: <i>jurabib.bst</i>, <i>jhuman.bst</i> and two Chicago-like ones. </ul> -<p>Options for entries in footnotes are +<p/>Options for entries in footnotes are <ul> <li> The package <i>footbib</i>, and <li> Packages <i>jurabib</i> and <i>inlinebib</i>, again. @@ -37,5 +37,5 @@ be advisable to use <i>jurabib</i> (or of course <dt><tt><i>inlinebib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/inlinebib.zip">biblio/bibtex/contrib/inlinebib</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/inlinebib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/inlinebib/">browse</a>) <dt><tt><i>jurabib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/jurabib.zip">macros/latex/contrib/jurabib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/jurabib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/jurabib/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibinline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibinline</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibinline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibinline</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-biblatex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-biblatex.html new file mode 100644 index 00000000000..e0606824e69 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-biblatex.html @@ -0,0 +1,44 @@ +<head> +<title>UK TeX FAQ -- question label biblatex</title> +</head><body> +<h3>Replacing the BibTeX–LaTeX mechanism</h3> +<p/>Producing a successor to BibTeX has long been a favoured activity +among a certain class of TeX-users; the author has seen many +reports of progress (on many projects), over the years, yet few +announcements of packages we can use. (There are probably usable +packages out there, but none that I know of.) +<p/>Two interesting approaches, that the author has investigated, are +<i>amsrefs</i> and <i>biblatex</i>. <i>Amsrefs</i> does away +with BibTeX altogether, while <i>biblatex</i> makes rather +limited use of BibTeX. Both are heavily dependent on LaTeX’s +support. +<p/><i>Amsrefs</i> uses a transformed <code>.bib</code> file, which is +expressed as LaTeX macros. (The package provides a BibTeX style +that performs the transformation, so that a LaTeX source containing +a <code>\</code><code>nocite{*}</code> command enables BibTeX to produce a usable +<i>amsrefs</i> bibliography database.) +<p/><i>Amsrefs</i> is maintained by the AMS as part of its author +support programme, +<p/><i>Biblatex</i> uses BibTeX more-or-less as normal, but with +<i>biblatex</i>’s own style; the style of citations and of the +bibliography itself is determined by the way your <i>biblatex</i> +style has been set up. This structure eliminates the collections of +BibTeX styles, at a stroke; the package comes with a basic set of +styles, and details are determined by options, set at package loading +time. The author, Philipp Lehman, evaluated the whole field of +bibliography software before starting, and as a result the package +comes with answers to many of the questions asked in the bibliography +sections of these FAQs. +<p/><i>Biblatex</i> is released as experimental software, but it’s +clear that many users are already using it happily; Lehman is +responsive to problem reports, at the moment, but a set of expert +users is already establishing itself. +<dl> +<dt><tt><i>amsrefs.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/amsrefs.zip">macros/latex/contrib/amsrefs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/amsrefs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/amsrefs/">browse</a>) +<dt><tt><i>biblatex.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/exptl/biblatex.zip">macros/latex/exptl/biblatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/exptl/biblatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/exptl/biblatex/">browse</a>) +</dl> +<p/> +<p/> + +<p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=biblatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=biblatex</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibplain.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibplain.html index f9b2d7d49e1..4bdbce06271 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibplain.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibplain.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label bibplain</title> </head><body> <h3>Using BibTeX with Plain TeX</h3> -<p>The file <i>btxmac.tex</i> (which is part of the Eplain system) +<p/>The file <i>btxmac.tex</i> (which is part of the Eplain system) contains macros and documentation for using BibTeX with Plain TeX, either directly or with <a href="FAQ-eplain.html">Eplain</a>. See <a href="FAQ-BibTeXing.html">the use of BibTeX</a> for more @@ -11,5 +11,5 @@ information about BibTeX itself. <dt><tt><i>btxmac.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/eplain/tex/eplain/btxmac.tex">macros/eplain/tex/eplain/btxmac.tex</a> <dt><tt><i>eplain system</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/eplain.zip">macros/eplain</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/eplain.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/eplain/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibplain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibplain</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibplain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibplain</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibprefixsort.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibprefixsort.html index 39de6ce1905..e82194c6ae8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibprefixsort.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibprefixsort.html @@ -2,19 +2,19 @@ <title>UK TeX FAQ -- question label bibprefixsort</title> </head><body> <h3>BibTeX sorting and name prefixes</h3> -<p>BibTeX recognises a bewildering array of name prefixes (mostly +<p/>BibTeX recognises a bewildering array of name prefixes (mostly those deriving from European language names); it ignores the prefixes when sorting the bibliography — you want “Ludwig van Beethoven” sorted under “Beethoven”, not under “van”. (Lamport made a witty deliberate mistake with Beethoven’s name, in the first edition of his LaTeX manual.) -<p>However, a recurring issue is the desire to quote Lord Rayleigh’s +<p/>However, a recurring issue is the desire to quote Lord Rayleigh’s publications (“Lord” isn’t an acceptable prefix), or names from languages that weren’t considered when BibTeX was designed such as “al-Wakil” (transcribed from the Arabic). What’s needed is a separate “sort key”, but BibTeX only allows such a thing in citations of items that have no author or editor. -<p>The solution is to embed the sort key in the author’s name, but to +<p/>The solution is to embed the sort key in the author’s name, but to prevent it from being typeset. Patashnik recommends a command <code>\</code><code>noopsort</code> (no-output-sortkey), which is defined and used as follows: @@ -52,5 +52,5 @@ AUTHOR = "\noopsort{Thanh Han The}{Han The Thanh}", though that author seems well-acquainted with Western confusion about the significance of the parts of his name (even to the extent of missing out the accentuation, as above...). -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibprefixsort">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibprefixsort</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibprefixsort">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibprefixsort</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibstrtl.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibstrtl.html index 806f8c86d0f..c8665ba7998 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibstrtl.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibstrtl.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label bibstrtl</title> </head><body> <h3>‘String too long’ in BibTeX</h3> -<p>The BibTeX diagnostic “Warning–you’ve exceeded 1000, the +<p/>The BibTeX diagnostic “Warning–you’ve exceeded 1000, the <code>global-string-size</code>, for entry <code>foo</code>” usually arises from a very large abstract or annotation included in the database. The diagnostic usually arises because of an infelicity in the coding of <i>abstract.bst</i>, or styles derived from it. (One doesn’t ordinarily output annotations in other styles.) -<p>The solution is to make a copy of the style file (or get a clean copy +<p/>The solution is to make a copy of the style file (or get a clean copy from CTAN — <a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/bibtools/abstract.bst">biblio/bibtex/utils/bibtools/abstract.bst</a>), and rename it (e.g., on a long file-name system, to <i>abstract-long.bst</i>). Now edit it: find function <code>output.nonnull</code> and @@ -32,9 +32,9 @@ to </ul> Finally, change your <code>\</code><code>bibliographystyle</code> command to refer to the name of the new file. -<p>This technique applies equally to any bibliography style: the same +<p/>This technique applies equally to any bibliography style: the same change can be made to any similar <code>output.nonnull</code> function. -<p>If you’re reluctant to make this sort of change, the only way forward +<p/>If you’re reluctant to make this sort of change, the only way forward is to take the entry out of the database, so that you don’t encounter BibTeX’s limit, but you may need to retain the entry because it will be included in the typeset document. In such cases, put the body @@ -51,5 +51,5 @@ of the entry in a separate file: In this way, you arrange that all BibTeX has to deal with is the file name, though it will tell TeX (when appropriate) to include all the long text. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibstrtl">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibstrtl</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibstrtl">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibstrtl</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtocorder.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtocorder.html index 0545356846a..1818cab7147 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtocorder.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtocorder.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label bibtocorder</title> </head><body> <h3>Table of contents rearranges “<i>unsrt</i>” ordering</h3> -<p>If you’re using the <i>unsrt</i> bibliography style, you’re +<p/>If you’re using the <i>unsrt</i> bibliography style, you’re expecting that your bibliography will <em>not</em> be sorted, but that the entries will appear in the order that they first appeared in your document. -<p>However, if you’re unfortunate enough to need a citation in a section +<p/>However, if you’re unfortunate enough to need a citation in a section title, and you also have a table of contents, the citations that now appear in the table of contents will upset the “natural” ordering produced by the <i>unsrt</i> style. Similarly, if you have citations in captions, and have a list of figures (or tables). -<p>There’s a pretty simple “manual” method for dealing with the +<p/>There’s a pretty simple “manual” method for dealing with the problem — when you have the document stable: <ol> <li> Delete the <code>.aux</code> file, and any of <code>.toc</code>, @@ -22,11 +22,11 @@ problem — when you have the document stable: </ol> Which is indeed simple, but it’s going to get tedious when you’ve found errors in your “stable” version, often enough. -<p>The package <i>notoccite</i> avoids the kerfuffle, and suppresses +<p/>The package <i>notoccite</i> avoids the kerfuffle, and suppresses citations while in the table of contents, or lists of figures, tables (or other floating things: the code is quite general). <dl> <dt><tt><i>notoccite.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/notoccite.sty">macros/latex/contrib/misc/notoccite.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibtocorder">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibtocorder</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibtocorder">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibtocorder</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtranscinit.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtranscinit.html index bcdf6c20345..076487e64fb 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtranscinit.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bibtranscinit.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label bibtranscinit</title> </head><body> <h3>Transcribed initials in BibTeX</h3> -<p>If your bibliographic style uses initials + surname, you may encounter +<p/>If your bibliographic style uses initials + surname, you may encounter a problem with some transcribed names (for example, Russian ones). Consider the following example from the real world: <blockquote> @@ -19,7 +19,7 @@ BibTeX’s algorithms will leave you with a citation — slightly depending on the bibliographic style — that reads: “S. Y. Epifanov and A. A. Vigasin, ...”. instead of the intended “S. Yu. Epifanov and A. A. Vigasin, ...”. -<p>One solution is to replace each affected initial by a command that +<p/>One solution is to replace each affected initial by a command that prints the correct combination. To keep your bibliography portable, you need to add that command to your bibliography with the <code>@preamble</code> directive: @@ -37,7 +37,7 @@ you need to add that command to your bibliography with the If you have many such commands, you may want to put them in a separate file and <code>\</code><code>input</code> that LaTeX file in a <code>@preamble</code> directive. -<p>An alternative is to make the transcription look like an accent, from +<p/>An alternative is to make the transcription look like an accent, from BibTeX’s point of view. For this we need a control sequence that does nothing: <blockquote> @@ -51,5 +51,5 @@ does nothing: Like the solution by generating extra commands, this involves tedious extra typing; which of the two techniques is preferable for a given bibliography will be determined by the names in it. -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibtranscinit">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibtranscinit</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibtranscinit">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bibtranscinit</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bold-extras.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bold-extras.html index 7cea6ff7058..d590e8896a4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bold-extras.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bold-extras.html @@ -2,32 +2,32 @@ <title>UK TeX FAQ -- question label bold-extras</title> </head><body> <h3>How to do bold-tt or bold-sc</h3> -<p>LaTeX, as delivered, offers no means of handling bold “teletype” +<p/>LaTeX, as delivered, offers no means of handling bold “teletype” or small-caps fonts. There’s a practical reason for this (Knuth never designed such fonts), but there are typographical considerations too (the “medium weight” <code>cmtt</code> font is already pretty bold (by comparison with other fixed-width fonts), and bold small-caps is not popular with many professional typographers). -<p>There’s a set of “extra” Metafont files on CTAN that provide bold +<p/>There’s a set of “extra” Metafont files on CTAN that provide bold versions of both <code>cmtt</code> and <code>cmcsc</code> (the small caps font). With modern TeX distributions, one may bring these fonts into use simply by placing them in an -<a href="FAQ-wherefiles.html">appropriate place in the <em>texmf</em> tree</a> +<a href="FAQ-install-where.html">appropriate place in the <em>texmf</em> tree</a> (these are (La)TeX-specific files, so the “<em>public</em>” supplier would be an appropriate place). Once you’ve -<a href="FAQ-instpackages.html">rebuilt the file indexes as necessary</a>, +<a href="FAQ-inst-wlcf.html">rebuilt the file indexes as necessary</a>, TeX (and friends) will automatically build whatever font files they need when you first make reference to them. There’s a jiffy package <i>bold-extra</i> that builds the necessary font data structures so that you can use the fonts within LaTeX. -<p>Another alternative is to use the <a href="FAQ-ECfonts.html">EC fonts</a>, +<p/>Another alternative is to use the <a href="FAQ-ECfonts.html">EC fonts</a>, which come with bold variants of the small-caps fonts. -<p>If you need to use Type 1 fonts, you can’t proceed with Knuth-style +<p/>If you need to use Type 1 fonts, you can’t proceed with Knuth-style fonts, since there are no Type 1 versions of the <i>mf-extra</i> set. There are, however, Type 1 distributions of the EC fonts, so you can switch to EC and use them; alternatives are discussed in <a href="FAQ-type1T1.html">8-bit Type 1 fonts</a>. -<p>Of course, commercial fixed-width fonts (even the default +<p/>Of course, commercial fixed-width fonts (even the default <i>Courier</i>) almost always come with a bold variant, so that’s not a problem. Furthermore <a href="FAQ-usepsfont.html">PSNFSS</a> will usually provide “faked” small caps fonts, and has no @@ -42,5 +42,5 @@ support available on the archive. <dt><tt><i>bold tt and small caps fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/mf-extra/bold.zip">fonts/cm/mf-extra/bold</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/cm/mf-extra/bold.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/mf-extra/bold/">browse</a>) <dt><tt><i>LuxiMono fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/LuxiMono.zip">fonts/LuxiMono</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/LuxiMono.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/LuxiMono/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bold-extras">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bold-extras</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bold-extras">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=bold-extras</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-boldgreek.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-boldgreek.html index aa7f2f46ea9..b2cfa27d529 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-boldgreek.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-boldgreek.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label boldgreek</title> </head><body> <h3>Setting bold Greek letters in LaTeX</h3> -<p>The issue here is complicated by the fact that <code>\</code><code>mathbf</code> (the +<p/>The issue here is complicated by the fact that <code>\</code><code>mathbf</code> (the command for setting bold <em>text</em> in TeX maths) affects a select few mathematical symbols (the uppercase Greek letters). However lower-case Greek letters behave differently from upper-case Greek @@ -11,7 +11,7 @@ letters (due to Knuth’s esoteric font encoding decisions). However, the AMSLaTeX <i>amsmath</i> package, which disables this font-switching and you must use one of the techniques outlined below. -<p>The Plain TeX solution <em>does</em> work, in a limited way: +<p/>The Plain TeX solution <em>does</em> work, in a limited way: <blockquote> <pre> {\boldmath$\theta$} @@ -25,7 +25,7 @@ $... \mbox{\boldmath$\theta$} ...$ </pre> </blockquote><p> which then causes problems in superscripts, etc. -<p>These problems may be addressed by using a bold mathematics package. +<p/>These problems may be addressed by using a bold mathematics package. <ul> <li> The <i>bm</i> package, which is part of the LaTeX tools distribution, defines a command <code>\</code><code>bm</code> which may be used anywhere @@ -34,7 +34,7 @@ which then causes problems in superscripts, etc. defines a command <code>\</code><code>boldsymbol</code>, which (though slightly less comprehensive than <code>\</code><code>bm</code>) covers almost all common cases. </ul> -<p>All these solutions cover all mathematical symbols, not merely Greek +<p/>All these solutions cover all mathematical symbols, not merely Greek letters. <dl> <dt><tt><i>bm.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) @@ -42,5 +42,5 @@ letters. <dt><tt><i>amsmath.sty</i></tt><dd>Distributed as part of AMSLaTeX <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=boldgreek">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=boldgreek</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=boldgreek">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=boldgreek</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-books.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-books.html index c18343690e5..f466f8f7bb6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-books.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-books.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label books</title> </head><body> <h3>Books on TeX and its relations</h3> -<p>While Knuth’s book is the definitive reference for TeX, there are +<p/>While Knuth’s book is the definitive reference for TeX, there are other books covering TeX: <dl> <dt>The TeXbook<dd>by Donald Knuth (Addison-Wesley, 1984, @@ -65,11 +65,12 @@ For LaTeX, see: edition, Addison-Wesley, 2004, ISBN 0-321-17385-6) <dt>The LaTeX Companion<dd>by Frank Mittelbach, Michel Goossens, Johannes Braams, David Carlisle and Chris Rowley (second edition, - Addison-Wesley, 2004, ISBN 0-201-36299-6) + Addison-Wesley, 2004, ISBN-10 0-201-36299-6, ISBN-13 978-0-201-36299-2) <dt>The LaTeX Graphics Companion:<dd> <em>Illustrating documents with TeX and PostScript</em> by Michel - Goossens, Sebastian Rahtz and Frank Mittelbach (Addison-Wesley, - 1997, ISBN 0-201-85469-4) + Goossens, Sebastian Rahtz, Frank Mittelbach, Denis Roegel and + Herbert Voss (second edition, Addison-Wesley, 2007, + ISBN-10 0-321-50892-0, ISBN-13 978-0-321-50892-8) <dt>The LaTeX Web Companion:<dd> <em>Integrating TeX, HTML and XML</em> by Michel Goossens and Sebastian Rahtz (Addison-Wesley, 1999, ISBN 0-201-43311-7) @@ -87,7 +88,7 @@ For LaTeX, see: multilingual aspects, and use of <a href="FAQ-omegaleph.html">Omega</a>, by Apostolos Syropoulos, Antonis Tsolomitis and Nick Sofroniou (Springer, 2003, ISBN 0-387-95217-9). -<p> A list of errata for the first printing is available from: +<p/> A list of errata for the first printing is available from: <a href="http://www.springer-ny.com/catalog/np/jan99np/0-387-98708-8.html">http://www.springer-ny.com/catalog/np/jan99np/0-387-98708-8.html</a> <dt>First Steps in LaTeX<dd>by George Grätzer (Birkhäuser, 1999, ISBN 0-8176-4132-7) @@ -105,16 +106,16 @@ Acrobat format, and example files for the three LaTeX Companions, and for Grätzer’s “First Steps in LaTeX”, are all available on CTAN. -<p>There’s a nicely-presented list of of “recommended books” to be had +<p/>There’s a nicely-presented list of of “recommended books” to be had on the web: <a href="http://www.macrotex.net/texbooks/">http://www.macrotex.net/texbooks/</a> -<p>The list of Metafont books is rather short: +<p/>The list of Metafont books is rather short: <dl> <dt>The Metafontbook<dd>by Donald Knuth (Addison Wesley, 1986, ISBN 0-201-13445-4, ISBN 0-201-52983-1 paperback) </dl> Alan Hoenig’s ‘<i>TeX Unbound</i>’ includes some discussion and examples of using Metafont. -<p>A book covering a wide range of topics (including installation and +<p/>A book covering a wide range of topics (including installation and maintenance) is: <dl> <dt>Making TeX Work<dd>by Norman Walsh (O’Reilly and Associates, @@ -123,7 +124,7 @@ maintenance) is: The book is decidedly dated, and is now out of print, but a copy is available via <code>sourceforge</code> and on CTAN, and we list it under “<a href="FAQ-ol-books.html">online books</a>”. -<p><p>This list only covers books in English: notices of new books, or +<p/><p/>This list only covers books in English: notices of new books, or warnings that books are now out of print are always welcome. However, this FAQ does <em>not</em> carry reviews of current published material. <dl> @@ -134,5 +135,5 @@ this FAQ does <em>not</em> carry reviews of current published material. <dt><tt><i>Sample of Math into LaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/mil/mil.pdf">info/mil/mil.pdf</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=books">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=books</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=books">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=books</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-braket.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-braket.html index 75d2f9113a5..7d05cc3c7ca 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-braket.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-braket.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label braket</title> </head><body> <h3>Set specifications and Dirac brackets</h3> -<p>One of the few glaring omissions from TeX’s mathematical +<p/>One of the few glaring omissions from TeX’s mathematical typesetting capabilities is a means of setting separators in the middle of mathematical expressions. TeX provides primitives called <code>\</code><code>left</code> and <code>\</code><code>right</code>, which can be used to modify brackets (of @@ -10,7 +10,7 @@ whatever sort) around a mathematical expression, as in: <code>\left( <expression> \right)</code> — the size of the parentheses is matched to the vertical extent of the expression. -<p>However, in all sorts of mathematical enterprises one may find oneself +<p/>However, in all sorts of mathematical enterprises one may find oneself needing a <code>\</code><code>middle</code> command, to be used in expressions like <blockquote> <pre> @@ -28,5 +28,5 @@ itself running under e-TeX. <dl> <dt><tt><i>braket.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/braket.sty">macros/latex/contrib/misc/braket.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=braket">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=braket</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=braket">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=braket</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-breakbox.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-breakbox.html index f150d1cee64..6d2d0339c93 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-breakbox.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-breakbox.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label breakbox</title> </head><body> <h3>Breaking boxes of text</h3> -<p>(La)TeX boxes may not be broken, in ordinary usage: once you’ve +<p/>(La)TeX boxes may not be broken, in ordinary usage: once you’ve typeset something into a box, it will stay there, and the box will jut out beyond the side or the bottom of the page if it doesn’t fit in the typeset area. -<p>If you want a substantial portion of your text to be framed (or +<p/>If you want a substantial portion of your text to be framed (or coloured), the restriction starts to seem a real imposition. Fortunately, there are ways around the problem. -<p>The <i>framed</i> package provides <code>framed</code> and +<p/>The <i>framed</i> package provides <code>framed</code> and <code>shaded</code> environments; both put their content into something which looks like a framed (or coloured) box, but which breaks as necessary at page end. The environments “lose” footnotes, @@ -17,13 +17,13 @@ marginpars and head-line entries, and will not work with <i>multicol</i> or other column-balancing macros. The <i>memoir</i> class includes the functionality of the <i>framed</i> package. -<p>The <i>boites</i> package provides a <code>breakbox</code> +<p/>The <i>boites</i> package provides a <code>breakbox</code> environment; examples of its use may be found in the distribution, and the package’s <i>README</i> file contains terse documentation. The environments may be nested, and may appear inside <code>multicols</code> environments; however, floats, footnotes and marginpars will be lost. -<p>For Plain TeX users, the facilities of the <i>backgrnd</i> +<p/>For Plain TeX users, the facilities of the <i>backgrnd</i> package may be useful; this package subverts the output routine to provide vertical bars to mark text, and the macros are clearly marked to show where coloured backgrounds may be introduced (this requires @@ -39,5 +39,5 @@ current LaTeX. <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>shade.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/shade.zip">macros/generic/shade</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/generic/shade.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/generic/shade/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=breakbox">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=breakbox</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=breakbox">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=breakbox</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-breaklinks.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-breaklinks.html index 224d26ffa3d..beaa7106abb 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-breaklinks.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-breaklinks.html @@ -3,22 +3,22 @@ </head><body> <h3>Link text doesn’t break at end line</h3> <!-- hyperref overfull link --> -<p>When using the <i>hyperref</i> package, you make a block of text +<p/>When using the <i>hyperref</i> package, you make a block of text “active” when you define a hyper-link (when the user clicks on that text, the reader program will divert to the <em>target</em> of the link). -<p>The <i>hyperref</i> package uses a <em>driver</em> (in the same way +<p/>The <i>hyperref</i> package uses a <em>driver</em> (in the same way as the <i>graphics</i> package does), to determine how to implement all that hyper-stuff. -<p>If you use the driver for <i>dvips</i> output (presumably you want +<p/>If you use the driver for <i>dvips</i> output (presumably you want to distill the resulting PostScript), limitations in the way <i>dvips</i> deals with the <code>\</code><code>special</code> commands mean that <i>hyperref</i> must prevent link anchors from breaking at the end of lines. Other drivers (notably those for PDFTeX and for <i>dvipdfm</i>) don’t suffer from this problem. -<p>The problem may occur in a number of different circumstances. For a +<p/>The problem may occur in a number of different circumstances. For a couple of them, there are work-arounds: -<p>First, if you have an URL which is active (so that clicking on +<p/>First, if you have an URL which is active (so that clicking on it will activate your web browser to “go to” the URL). In this case <i>hyperref</i> employs the <i>url</i> package to split up the URL (as described in @@ -28,18 +28,18 @@ the <i>breakurl</i> package, which modifies the <code>\</code><code>url</code> c to produce several smaller pieces, between each of which a line break is permitted. Each group of pieces, that ends up together in one line, is converted to a single clickable link. -<p>Second, if you have a table of contents, list of figure or tables, or +<p/>Second, if you have a table of contents, list of figure or tables, or the like, <i>hyperref</i> will ordinarily make the titles in the table of contents, or captions in the lists, active. If the title or caption is long, it will need to break within the table, but the <i>dvips</i> driver will prevent that. In this case, load <i>hyperref</i> with the option <code>linktocpage</code>, and only the page number will be made active. -<p>Otherwise, if you have a lengthy piece of text that you want active, +<p/>Otherwise, if you have a lengthy piece of text that you want active, you have at present no simple solution: you have to rewrite your text, or to use a different PDF generation mechanism. <dl> <dt><tt><i>breakurl.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/breakurl.zip">macros/latex/contrib/breakurl</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/breakurl.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/breakurl/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=breaklinks">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=breaklinks</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=breaklinks">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=breaklinks</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-brkinline.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-brkinline.html index a10665e1067..ab441192f5f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-brkinline.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-brkinline.html @@ -2,15 +2,15 @@ <title>UK TeX FAQ -- question label brkinline</title> </head><body> <h3>Line-breaking in in-line maths</h3> -<p>TeX, by default, allows you to split a mathematical expression at +<p/>TeX, by default, allows you to split a mathematical expression at the end of the line; it allows breaks at relational operators (like “=”, “<”, etc.) and at binary operators (like “+”, “-”, etc.). In the case of large expressions, this can sometimes be a life-saver. -<p>However, in the case of simple expressions like a=b+c, a +<p/>However, in the case of simple expressions like a=b+c, a break can be really disturbing to the reader, and one would like to avoid it. -<p>Fortunately, these breaks are controllable: there are “penalties” +<p/>Fortunately, these breaks are controllable: there are “penalties” associated with each type of operator: the penalty says how undesirable a break at each point is. Default values are: @@ -50,5 +50,5 @@ ${a+b+c+d} = z+y+x+w$ </blockquote><p> The braces say “treat this subformula as one atom” and (in TeX at least) atoms don’t get split: not a <code>\</code><code>binoppenalty</code> change in sight. -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=brkinline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=brkinline</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=brkinline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=brkinline</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buffovl.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buffovl.html index 5dbf6e85c97..e31223e21bf 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buffovl.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buffovl.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label buffovl</title> </head><body> <h3>Unable to read an entire line</h3> -<p>TeX belongs to the generation of applications written for +<p/>TeX belongs to the generation of applications written for environments that didn’t offer the sophisticated string and i/o manipulation we nowadays take for granted (TeX was written in Pascal, and the original Pascal standard made no mention of i/o, so that anything but the most trivial operations were likely to be unportable). -<p>When you overwhelm TeX’s input mechanism, you get told: +<p/>When you overwhelm TeX’s input mechanism, you get told: <pre> ! Unable to read an entire line---bufsize=3000. Please ask a wizard to enlarge me. @@ -16,7 +16,7 @@ unportable). (for some value of ‘3000’ — the quote was from a <i>comp.text.tex</i> posting by a someone who was presumably using an old TeX). -<p>As the message implies, there’s (what TeX thinks of as a) line in +<p/>As the message implies, there’s (what TeX thinks of as a) line in your input that’s “too long” (to TeX’s way of thinking). Since modern distributions tend to have tens of thousands of bytes of input buffer, it’s somewhat rare that these messages occur “for real”. @@ -34,21 +34,21 @@ Probable culprits are: and ignore the previews (which are only of interest, if at all, to a TeX previewer). </ul> -<p>The usual advice is to ignore what TeX says (i.e., anything about +<p/>The usual advice is to ignore what TeX says (i.e., anything about enlarging), and to put the problem right in the source. -<p>If the real problem is over-long text lines, most self-respecting text +<p/>If the real problem is over-long text lines, most self-respecting text editors will be pleased to automatically split long lines (while preserving the “word” structure) so that they are nowhere any longer than a given length; so the solution is just to edit the file. -<p>If the problem is a ridiculous preview section, try using +<p/>If the problem is a ridiculous preview section, try using <i>ghostscript</i> to reprocess the file, outputting a “plain <code>.eps</code>” file. (<i>Ghostscript</i> is distributed with a script <i>ps2epsi</i> which will regenerate the preview if necessary.) Users of the shareware program <i>GSview</i> will find buttons to perform the required transformation of the file being displayed. <dl> -<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/ghostscript/">nonfree/support/ghostscript/</a> +<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/">support/ghostscript/</a> <dt><tt><i>GSview</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/ghostscript/ghostgum/">nonfree/support/ghostscript/ghostgum/</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=buffovl">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=buffovl</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=buffovl">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=buffovl</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bug.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bug.html index 0468681e93f..3f58bef68bb 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bug.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-bug.html @@ -6,12 +6,12 @@ -<p>For a start, make entirely sure you <em>have</em> found a bug. +<p/>For a start, make entirely sure you <em>have</em> found a bug. Double-check with books about TeX, LaTeX, or whatever you’re using; compare what you’re seeing against the other answers above; ask every possible person you know who has any TeX-related expertise. The reasons for all this caution are various. -<p>If you’ve found a bug in TeX itself, you’re a rare animal indeed. +<p/>If you’ve found a bug in TeX itself, you’re a rare animal indeed. Don Knuth is so sure of the quality of his code that he offers real money prizes to finders of bugs; the cheques he writes are such rare items that they are seldom cashed. If <em>you</em> @@ -22,26 +22,26 @@ only after they are agreed as bugs by a small vetting team. In the first instance, contact Barbara Beeton at the AMS (<i>bnb@ams.org</i>), or contact <a href="FAQ-TUGstar.html">TUG</a>. -<p>If you’ve found a bug in LaTeX2e, <a href="FAQ-latexbug.html">report it</a> +<p/>If you’ve found a bug in LaTeX2e, <a href="FAQ-latexbug.html">report it</a> using mechanisms supplied by the LaTeX team. (Please be careful to ensure you’ve got a LaTeX bug, or a bug in one of the “required” packages distributed by the LaTeX team.) -<p>If you’ve found a bug in a contributed LaTeX package, you could try +<p/>If you’ve found a bug in a contributed LaTeX package, you could try contacting the author (if you can find a contact address). However, it’s generally best to treat any package as unsupported, in the first instance, and only try the author <em>after</em> mailing list/news group support has failed you. -<p>If you’ve found a bug in LaTeX 2.09, or some other such unsupported +<p/>If you’ve found a bug in LaTeX 2.09, or some other such unsupported software, you may find help or <em>de facto</em> support on a newsgroup such as <i>comp.tex.tex</i> or on a mailing list such as -<a href="mailto:texhax@tug.org"><i>texhax@tug.org</i></a>; be carefule to include a +<a href="mailto:texhax@tug.org"><i>texhax@tug.org</i></a>; be careful to include a <a href="FAQ-minxampl.html">code example</a> of the failure, if relevant. -<p>Failing all else, you may need to pay for +<p/>Failing all else, you may need to pay for help — TUG maintains a <a href="http://www.tug.org/consultants.html">register of TeX consultants</a>. -<p><p> +<p/><p/> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buildbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buildbib.html index 5a5cf86848e..03d4b998995 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buildbib.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-buildbib.html @@ -2,15 +2,15 @@ <title>UK TeX FAQ -- question label buildbib</title> </head><body> <h3>Creating a BibTeX bibliography file</h3> -<p>A BibTeX bibliography file may reasonably be compared to a small +<p/>A BibTeX bibliography file may reasonably be compared to a small database, the entries in which are references to literature that may be called up by citations in a document. -<p>Each entry in the bibliography has a <em>type</em> and a unique +<p/>Each entry in the bibliography has a <em>type</em> and a unique <em>key</em>. The bibliography is read, by BibTeX, using the details specified in a <em>bibliography style</em>. From the style, BibTeX finds what entry types are permissible, what <em>fields</em> each entry type has, and how to format the whole entry. -<p>The type specifies the type of document you’re making reference to; it +<p/>The type specifies the type of document you’re making reference to; it may run all the way from things like “<code>Book</code>” and “<code>Proceedings</code>” (which may even contain other citations of type “<code>InBook</code>” or “<code>InProceedings</code>”) @@ -23,7 +23,7 @@ the year of publication, possibly with a marker to distinguish publications in the same year. So, for example, the Dyson, Eddington, Davidson paper about deflection of starlight appears in my experimental <code>.bib</code> file as <code>Dyson20.1</code>. -<p>So, noting the rules of the style, you have ‘simply’ to write a +<p/>So, noting the rules of the style, you have ‘simply’ to write a bibliography database. Fortunately, there are several tools to help in this endeavour: <ul> @@ -36,12 +36,12 @@ in this endeavour: available, some of which permit a graphical user interface to the task. Sadly, none seems to be available with the ordinary TeX distributions. -<p> Tools such as <i>Xbibfile</i> (a graphical user interface), +<p/> Tools such as <i>Xbibfile</i> (a graphical user interface), <i>ebib</i> (a database application written to run ‘inside’ <i>emacs</i>) and <i>btOOL</i> (a set of <i>perl</i> tools for building BibTeX database handlers) are available from CTAN. -<p> Other systems, such as +<p/> Other systems, such as <a href="http://refdb.sourceforge.net/"><i>RefDB</a></i>, <a href="http://www.nongnu.org/biborb">BibORB</a>, <a href="http://bibdesk.sourceforge.net/"><i>BibDesk</a></i>, @@ -72,5 +72,5 @@ in this endeavour: <dt><tt><i>tex2bib.readme</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/tex2bib/README">biblio/bibtex/utils/tex2bib/README</a> <dt><tt><i>xbibfile</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/xbibfile.zip">biblio/bibtex/utils/xbibfile</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/xbibfile.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/xbibfile/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=buildbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=buildbib</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=buildbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=buildbib</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cancellation.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cancellation.html index 835fac1369a..cbc8bcdb45a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cancellation.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cancellation.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label cancellation</title> </head><body> <h3>Cancelling terms in maths expressions</h3> -<p>A technique used when explaining the behaviour of expressions or +<p/>A technique used when explaining the behaviour of expressions or equations (often for pedagogical purposes). The <i>cancel</i> package provides several variants of cancellation marks (“<code>\</code>”, “<code>/</code>” and “<code>X</code>”), and a means of cancelling ‘to’ a particular value. -<p>Documentation of <i>cancel</i> is in the package file. +<p/>Documentation of <i>cancel</i> is in the package file. <dl> <dt><tt><i>cancel.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/cancel.sty">macros/latex/contrib/misc/cancel.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cancellation">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cancellation</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cancellation">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cancellation</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-capbibtex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-capbibtex.html index e02940bd381..054ae10fb92 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-capbibtex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-capbibtex.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label capbibtex</title> </head><body> <h3>Capitalisation in BibTeX</h3> -<p>The standard BibTeX bibliography styles impose fixed ideas about +<p/>The standard BibTeX bibliography styles impose fixed ideas about the capitalisation of titles of things in the bibliography. While this is not unreasonable by BibTeX’s lights (the rules come from the <em>Chicago Manual of Style</em>) it can be troublesome, since BibTeX fails to recognise special uses (such as acronyms, chemical formulae, etc.). -<p>The solution is to enclose the letter or letters, whose capitalisation +<p/>The solution is to enclose the letter or letters, whose capitalisation BibTeX should not touch, in braces, as: <blockquote> <pre> @@ -36,8 +36,8 @@ though that does ensure that the capitalisation is not changed. Your BibTeX database should be a general-purpose thing, not something tuned to the requirements of a particular document, or to the way you are thinking today. -<p>There’s more on the subject in the +<p/>There’s more on the subject in the <a href="FAQ-BibTeXing.html">BibTeX documentation</a>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=capbibtex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=capbibtex</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=capbibtex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=capbibtex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-captsty.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-captsty.html index 77936b06c80..d9dfeb65092 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-captsty.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-captsty.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label captsty</title> </head><body> <h3>The style of captions</h3> -<p>Changes to the style of captions may be made by redefining the commands +<p/>Changes to the style of captions may be made by redefining the commands that produce the caption. So, for example, <code>\</code><code>fnum@figure</code> (which produces the float number for figure floats) may be redefined, in a package of your own, or between @@ -19,24 +19,24 @@ the original definition used made by patching the <code>\</code><code>caption</code> command, but since there are packages to do the job, such changes (which can get rather tricky) aren’t recommended for ordinary users. -<p>The <i>float</i> package provides some control of the appearance of +<p/>The <i>float</i> package provides some control of the appearance of captions, though it’s principally designed for the creation of non-standard floats. The <i>caption</i> and <i>ccaption</i> (note the double “<em>c</em>”) packages provide a range of different formatting options. -<p><i>ccaption</i> also provides ‘continuation’ captions and captions +<p/><i>ccaption</i> also provides ‘continuation’ captions and captions that can be placed outside of float environments. The (very simple) <i>capt-of</i> package also allows captions outside a float environment. Note that care is needed when doing things that assume the sequence of floats (as in continuation captions), or potentially mix non-floating captions with floating ones. -<p>The <i>memoir</i> class includes the facilities of the +<p/>The <i>memoir</i> class includes the facilities of the <i>ccaption</i> package; the <i>KOMA-script</i> classes also provide a wide range of caption-formatting commands. -<p>The documentation of <i>caption</i> is available by processing a +<p/>The documentation of <i>caption</i> is available by processing a file <i>manual.tex</i>, which is created when you unpack <i>caption.dtx</i> -<p>Note that the previously-recommended package <i>caption2</i> has +<p/>Note that the previously-recommended package <i>caption2</i> has now been overtaken again by <i>caption</i>; however, <i>caption2</i> remains available for use in older documents. <dl> @@ -47,5 +47,5 @@ now been overtaken again by <i>caption</i>; however, <dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=captsty">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=captsty</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=captsty">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=captsty</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-casechange.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-casechange.html index 6a8daaa7085..147a29f6e65 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-casechange.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-casechange.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label casechange</title> </head><body> <h3>Case-changing oddities</h3> -<p>TeX provides two primitive commands <code>\</code><code>uppercase</code> and +<p/>TeX provides two primitive commands <code>\</code><code>uppercase</code> and <code>\</code><code>lowercase</code> to change the case of text; they’re not much used, but are capable creating confusion. -<p>The two commands do not expand the text that is their parameter — +<p/>The two commands do not expand the text that is their parameter — the result of <code>\</code><code>uppercase{abc}</code> is ‘<code>ABC</code>’, but <code>\</code><code>uppercase{<code>\</code><code>abc</code>}</code> is always ‘<code>\</code><code>abc</code>’, whatever the meaning of <code>\</code><code>abc</code>. The commands are simply interpreting a table of @@ -23,14 +23,14 @@ ABOUT $Y=F(X)$ </pre> </blockquote><p> which is probably not what is wanted. -<p>In addition, <code>\</code><code>uppercase</code> and <code>\</code><code>lowercase</code> do not deal very well +<p/>In addition, <code>\</code><code>uppercase</code> and <code>\</code><code>lowercase</code> do not deal very well with non-American characters, for example <code>\</code><code>uppercase{<code>\</code><code>ae</code>}</code> is the same as <code>\</code><code>ae</code>. -<p>LaTeX provides commands <code>\</code><code>MakeUppercase</code> and <code>\</code><code>MakeLowercase</code> +<p/>LaTeX provides commands <code>\</code><code>MakeUppercase</code> and <code>\</code><code>MakeLowercase</code> which fixes the latter problem. These commands are used in the standard classes to produce upper case running heads for chapters and sections. -<p>Unfortunately <code>\</code><code>MakeUppercase</code> and <code>\</code><code>MakeLowercase</code> do not solve +<p/>Unfortunately <code>\</code><code>MakeUppercase</code> and <code>\</code><code>MakeLowercase</code> do not solve the other problems with <code>\</code><code>uppercase</code>, so for example a section title containing <code>\</code><code>begin{tabular}</code> ... <code>\</code><code>end{tabular}</code> will produce a running head containing @@ -48,7 +48,7 @@ Note that <code>\</code><code>mytable</code> has to be protected, otherwise it w expanded and made upper case; you can achieve the same result by declaring it with <code>\</code><code>DeclareRobustCommand</code>, in which case the <code>\</code><code>protect</code> won’t be necessary. -<p>David Carlisle’s <i>textcase</i> package +<p/>David Carlisle’s <i>textcase</i> package addresses many of these problems in a transparent way. It defines commands <code>\</code><code>MakeTextUppercase</code> and <code>\</code><code>MakeTextLowercase</code> which do upper- or lowercase, with the fancier features of the LaTeX @@ -61,5 +61,5 @@ broken page headings. <dl> <dt><tt><i>textcase.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textcase.zip">macros/latex/contrib/textcase</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textcase.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textcase/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=casechange">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=casechange</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=casechange">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=casechange</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changebars.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changebars.html index f9785178d79..1c0915f7768 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changebars.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changebars.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label changebars</title> </head><body> <h3>Marking changed parts of your document</h3> -<p>One often needs clear indications of how a document has changed, but +<p/>One often needs clear indications of how a document has changed, but the commonest technique, “change bars” (also known as “revision bars”), requires surprisingly much trickery of the programmer (the problem being that TeX ‘proper’ @@ -11,14 +11,15 @@ doesn’t provide the programmer with any information about the bar might be calculated; PDFTeX <em>does</em> provide the information, but we’re not aware yet of any programmer taking advantage of the fact to write a PDFTeX-based changebar package). -<p>The simplest package that offers change bars is Peter Schmitt’s +<p/>The simplest package that offers change bars is Peter Schmitt’s <i>backgrnd.tex</i>; this was written as a Plain TeX application that patches the output routine, but it appears to work at least on simple LaTeX documents. Wise LaTeX users will be alerted by the information that <i>backgrnd</i> patches their output routine, and will watch its behaviour very carefully (patching the LaTeX output routine is not something to undertake lightly...). -<p>The longest-established solution is the <i>changebar</i> package, +<p/>The longest-established LaTeX-specific solution is the +<i>changebar</i> package, which uses <code>\</code><code>special</code> commands supplied by the driver you’re using. You need therefore to tell the package which driver to generate <code>\</code><code>special</code>s for (in the same way that you need to tell the @@ -32,41 +33,51 @@ shareware <i>WinEDT</i> editor has a macro that will generate earlier version of your file, stored in an <i>RCS</i>-controlled repository — see <a href="http://www.winedt.org/Macros/LaTeX/RCSdiff.php">http://www.winedt.org/Macros/LaTeX/RCSdiff.php</a> -<p>The <i>vertbars</i> package uses the techniques of the +<p/>The <i>vertbars</i> package uses the techniques of the <i>lineno</i> package (which it loads, so the <i>lineno</i> itself must be installed); it’s thus the smallest of the packages for change bar marking, since it leaves all the trickery to another package. <i>Vertbars</i> defines a <code>vertbar</code> environment to create changebars. -<p>The <i>framed</i> package is +<p/>The <i>framed</i> package is another that provides bars as a side-effect of other desirable functionality: its <code>leftbar</code> environment is simply a stripped-down frame (note, though, that the environment makes a separate paragraph of its contents, so it is best used when the convention is to mark a whole changed paragraph. -<p>Finally, the <i>memoir</i> class allows marginal editorial comments, +<p/>Finally, the <i>memoir</i> class allows marginal editorial comments, which you can obviously use to delimit areas of changed text. -<p>Another way to keep track of changes is employed by some -word-processors — to produce a document that embodies both “old” -and “new” versions. The <i>Perl</i> script <i>latexdiff</i> -does this for LaTeX documents; you feed it the two documents, and -it produces a new LaTeX document in which the changes are very -visible. An example of the output is embedded in the documentation, +<p/>An even more comprehensive way to keep track of changes is employed by +some word-processors — to produce a document that embodies both +“old” and “new” versions. +<p/>To this end, he package <i>changes</i> allows the user to manually +markup changes of text, such as additions, deletions, or replacements. +Changed text is shown in a different colour; deleted text is crossed +out. The package allows you to define additional authors and their +associated colour; it also allows you to define a markup for authors +or annotations. The documentation (very clearly) demonstrates how the +various functions work. +<p/>The <i>Perl</i> script <i>latexdiff</i> may also be used to +generate such markup for LaTeX documents; you feed it the two +documents, and it produces a new LaTeX document in which the +changes are very visible. An example of the output is embedded in the +documentation, <a href="http://www.tex.ac.uk/tex-archive/support/latexdiff/latexdiff-man.pdf">latexdiff-man.pdf</a> (part of the distribution). A rudimentary revision facility is provided by another <i>Perl</i> script, <i>latexrevise</i>, which accepts or rejects all changes. Manual editing of the difference file can be used to -accept or reject selected changes only. +accept or reject selected changes only. <dl> <dt><tt><i>backgrnd.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/misc/backgrnd.tex">macros/generic/misc/backgrnd.tex</a> <dt><tt><i>changebar.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/changebar.zip">macros/latex/contrib/changebar</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/changebar.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/changebar/">browse</a>) +<dt><tt><i>changes.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/changes.zip">macros/latex/contrib/changes</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/changes.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/changes/">browse</a>) <dt><tt><i>framed.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/framed.sty">macros/latex/contrib/misc/framed.sty</a> <dt><tt><i>latexdiff, latexrevise</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/latexdiff.zip">support/latexdiff</a> (<a href="ftp://cam.ctan.org/tex-archive/support/latexdiff.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/latexdiff/">browse</a>) <dt><tt><i>lineno.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lineno.zip">macros/latex/contrib/lineno</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lineno.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/lineno/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>vertbars.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/vertbars.sty">macros/latex/contrib/misc/vertbars.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=changebars">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=changebars</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=changebars">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=changebars</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changemargin.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changemargin.html index 153d7c2567f..8de6cff6081 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changemargin.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-changemargin.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label changemargin</title> </head><body> <h3>Changing the margins in LaTeX</h3> -<p>Changing the layout of a document’s text on the page involves several +<p/>Changing the layout of a document’s text on the page involves several subtleties not often realised by the beginner. There are interactions between fundamental TeX constraints, constraints related to the design of LaTeX, and good typesetting and design practice, that mean that any change must be very carefully considered, both to ensure that it “works” and to ensure that the result is pleasing to the eye. -<p>LaTeX’s defaults sometimes seem excessively conservative, +<p/>LaTeX’s defaults sometimes seem excessively conservative, but there are sound reasons behind how Lamport designed the layouts themselves, whatever one may feel about his overall design. For example, the common request for “one-inch margins all round on A4 @@ -17,13 +17,13 @@ paper” is fine for 10- or 12-pitch typewriters, but not for 10pt (or even 11pt or 12pt) type because readers find such wide, dense, lines difficult to read. There should ideally be no more than 75 characters per line (though the constraints change for two-column text). -<p>So Lamport’s warning to beginners in his section on ‘Customizing the +<p/>So Lamport’s warning to beginners in his section on ‘Customizing the Style’ — “don’t do it” — should not lightly be ignored. -<p>This set of FAQs recommends that you use a package to establish +<p/>This set of FAQs recommends that you use a package to establish consistent settings of the parameters: the interrelationships are taken care of in the established packages, without you needing to think about them, but -<p>The following answers deal with the ways one may choose to proceed: +<p/>The following answers deal with the ways one may choose to proceed: <ul> <li> <a href="FAQ-marginpkgs.html">Choose which package to use</a>. <li> <a href="FAQ-marginmanual.html">Find advice on setting up page layout by hand</a>. @@ -33,5 +33,5 @@ temporarily — and there’s an answer that covers that, too: <ul> <li> <a href="FAQ-chngmargonfly.html">Change the margins on the fly</a>. </ul> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=changemargin">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=changemargin</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=changemargin">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=changemargin</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chapbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chapbib.html index 9d480244e66..550ae8aeb80 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chapbib.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chapbib.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label chapbib</title> </head><body> <h3>Separate bibliographies per chapter?</h3> -<p>A separate bibliography for each ‘chapter’ of a document can be provided +<p/>A separate bibliography for each ‘chapter’ of a document can be provided with the package <i>chapterbib</i> (which comes with a bunch of other good bibliographic things). The package allows you a different bibliography for each <code>\</code><code>include</code>d file (i.e., despite the package’s name, the availability of bibliographies is related to the component source files of the document rather than to the chapters that logically structure the document). -<p>The package <i>bibunits</i> ties bibliographies to logical units +<p/>The package <i>bibunits</i> ties bibliographies to logical units within the document: the package will deal with chapters and sections (as defined by LaTeX itself) and also defines a <code>bibunit</code> environment so that users can select their own structuring. @@ -17,5 +17,5 @@ environment so that users can select their own structuring. <dt><tt><i>chapterbib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cite.zip">macros/latex/contrib/cite</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cite.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cite/">browse</a>) <dt><tt><i>bibunits.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bibunits.zip">macros/latex/contrib/bibunits</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bibunits.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bibunits/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chapbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chapbib</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chapbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chapbib</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-charshift.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-charshift.html index cc8cce1c5e3..46eb2c9bac7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-charshift.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-charshift.html @@ -3,7 +3,7 @@ </head><body> <h3>Weird characters in <i>dvips</i> output</h3> <!-- fi ligature pound pounds sterling elephants --> -<p>You’ve innocently generated output, using <i>dvips</i>, and there +<p/>You’ve innocently generated output, using <i>dvips</i>, and there are weird transpositions in it: for example, the <code>fi</code> ligature has appeared as a textsterling symbol. This is an unwanted side-effect of the precautions @@ -11,10 +11,10 @@ outlined in <a href="FAQ-dvips-pdf.html">generating PostScript for PDF</a>. The <code>-G1</code> switch discussed in that question is appropriate for Knuth’s text fonts, but doesn’t work with text fonts that don’t follow Knuth’s patterns (such as fonts supplied by Adobe). -<p>If the problem arises, suppress the <code>-G1</code> switch: if you were using it +<p/>If the problem arises, suppress the <code>-G1</code> switch: if you were using it explicitly, <em>don’t</em>; if you were using <code>-Ppdf</code>, add <code>-G0</code> to suppress the implicit switch in the pseudo-printer file. -<p>The problem has been corrected in <i>dvips</i> v 5.90 (and later +<p/>The problem has been corrected in <i>dvips</i> v 5.90 (and later versions), which should be available in any recent TeX distribution. -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=charshift">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=charshift</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=charshift">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=charshift</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-checksum.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-checksum.html new file mode 100644 index 00000000000..a41bdb014bb --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-checksum.html @@ -0,0 +1,28 @@ +<head> +<title>UK TeX FAQ -- question label checksum</title> +</head><body> +<h3>Checksum mismatch in font</h3> +<p/>When Metafont generates a font it includes a checksum in the font bitmap +file, and in the font metrics file (TFM). (La)TeX includes +the checksum from the TFM file in the DVI file. +<p/>When <i>dvips</i> (or other DVI drivers) process a +DVI file, they compare checksums in the DVI file to +those in the bitmap fonts being used for character images. If the +checksums don’t match, it means the font metric file used by (La)TeX +was not generated from the same Metafont program that generated the +font. +<p/>This commonly occurs when you’re processing someone else’s DVI +file. +<p/>The fonts on your system may also be at fault: possibilities are that +the new TFM was not installed, or installed in a path after an +old TFM file, or that you have a personal cache of bitmaps from +an old version of the font. +<p/>In any case, look at the output – the chances are that it’s perfectly +OK, since metrics tend not to change, even when the bitmaps are +improved. (Indeed, many font designers — Knuth included — +maintain the metrics come what may.) +<p/>If the output <em>does</em> look bad, your only chance is to regenerate +things from scratch. Options include: flushing your bitmap cache, +rebuild the TFM file locally, and so on. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=checksum">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=checksum</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chngmargonfly.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chngmargonfly.html index 5a0616a5a66..73bf3701572 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chngmargonfly.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-chngmargonfly.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label chngmargonfly</title> </head><body> <h3>Changing margins “on the fly”</h3> -<p>One of the surprises characteristic of TeX use is that you cannot +<p/>One of the surprises characteristic of TeX use is that you cannot change the width or height of the text within the document, simply by modifying the text size parameters; TeX can’t change the text width on the fly, and LaTeX only ever looks at text height when starting a new page. -<p>So the simple rule is that the parameters should only be +<p/>So the simple rule is that the parameters should only be changed in the preamble of the document, i.e., before the <code>\</code><code>begin{document}</code> statement (so before any typesetting has happened. -<p>To adjust text width within a document we define an environment: +<p/>To adjust text width within a document we define an environment: <blockquote> <pre> \newenvironment{changemargin}[2]{% @@ -31,19 +31,19 @@ right margins, respectively, by the parameters’ values. Negative values will cause the margins to be narrowed, so <code>\</code><code>begin{changemargin}{-1cm}{-1cm}</code> narrows the left and right margins by 1 centimetre. -<p>Given that TeX can’t do this, how does it work? — well, the +<p/>Given that TeX can’t do this, how does it work? — well, the environment (which is a close relation of the LaTeX <code>quote</code> environment) <em>doesn’t</em> change the text width as far as TeX is concerned: it merely moves text around inside the width that TeX believes in. -<p>The <i>chngpage</i> package provides ready-built commands to do the +<p/>The <i>chngpage</i> package provides ready-built commands to do the above; it includes provision for changing the shifts applied to your text according to whether you’re on an odd or an even page of a two-sided document. The package’s documentation (in the file itself) suggests a strategy for changing text dimensions between pages — as mentioned above, changing the text dimensions within the body of a page may lead to unpredictable results. -<p>Changing the vertical dimensions of a page is clunkier still: the +<p/>Changing the vertical dimensions of a page is clunkier still: the LaTeX command <code>\</code><code>enlargethispage</code> adjusts the size of the current page by the size of its argument. Common uses are <blockquote> @@ -61,5 +61,5 @@ to make the page one line shorter. <dl> <dt><tt><i>chngpage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/chngpage.sty">macros/latex/contrib/misc/chngpage.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chngmargonfly">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chngmargonfly</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chngmargonfly">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=chngmargonfly</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citeURL.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citeURL.html index 3e41089bc68..911b74604f7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citeURL.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citeURL.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label citeURL</title> </head><body> <h3>URLs in BibTeX bibliographies</h3> -<p>There is no citation type for URLs, <em>per se</em>, in the +<p/>There is no citation type for URLs, <em>per se</em>, in the standard BibTeX styles, though Oren Patashnik (the author of BibTeX) is believed to beconsidering developing one such for use with the long-awaited BibTeX version 1.0. -<p>The actual information that need be available in a citation of an +<p/>The actual information that need be available in a citation of an URL is discussed at some length in the publicly available on-line @@ -14,7 +14,7 @@ on-line the techniques below do <em>not</em> satisfy all the requirements of ISO 690–2, but they offer a solution that is at least available to users of today’s tools. -<p>Until the new version of BibTeX arrives, the simplest technique is +<p/>Until the new version of BibTeX arrives, the simplest technique is to use the <code>howpublished</code> field of the standard styles’ <code>@misc</code> function. Of course, the strictures about <a href="FAQ-setURL.html">typesetting URLs</a> still apply, so the @@ -52,11 +52,10 @@ You can also acquire new BibTeX styles by use of Norman Gray’s <i>urlbst</i> system, which is based on a <i>Perl</i> script that edits an existing BibTeX style file to produce a new style. The new style thus generated has a <code>webpage</code> entry type, and -also offers support for <code>url</code> and <code>lastchecked</code> fields in the other entry -types. The <i>Perl</i> script comes with a set of converted -versions of the standard bibliography styles. Documentation is -distributed as LaTeX source. -<p>Another possibility is that some conventionally-published paper, +also offers support for <code>url</code> and <code>lastchecked</code> fields +in the other entry types. The <i>Perl</i> script comes with a set +of converted versions of the standard bibliography styles. +<p/>Another possibility is that some conventionally-published paper, technical report (or even book) is also available on the Web. In such cases, a useful technique is something like: <blockquote> @@ -86,5 +85,5 @@ removes it. <dt><tt><i>url.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/url.sty">macros/latex/contrib/misc/url.sty</a> <dt><tt><i>urlbst</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/urlbst.zip">biblio/bibtex/contrib/urlbst</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/urlbst.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/urlbst/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=citeURL">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=citeURL</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=citeURL">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=citeURL</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citesort.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citesort.html index e8297ccbc5e..2fbf74de819 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citesort.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-citesort.html @@ -2,18 +2,18 @@ <title>UK TeX FAQ -- question label citesort</title> </head><body> <h3>Sorting and compressing citations</h3> -<p>If you give LaTeX +<p/>If you give LaTeX <code>\</code><code>cite{fred,joe,harry,min}</code>, its default commands could give something like “[2,6,4,3]”; this looks awful. One can of course get the things in order by rearranging the keys in the <code>\</code><code>cite</code> command, but who wants to do that sort of thing for no more improvement than “[2,3,4,6]”? -<p>The <i>cite</i> package sorts the numbers and detects consecutive +<p/>The <i>cite</i> package sorts the numbers and detects consecutive sequences, so creating “[2–4,6]”. The <i>natbib</i> package, with the <code>numbers</code> and <code>sort&compress</code> options, will do the same when working with its own numeric bibliography styles (<i>plainnat.bst</i> and <i>unsrtnat.bst</i>). -<p>If you might need to make hyperreferences to your citations, +<p/>If you might need to make hyperreferences to your citations, <i>cite</i> isn’t adequate. If you add the <i>hypernat</i> package: <pre> @@ -31,5 +31,5 @@ the <i>natbib</i> and <i>hyperref</i> packages will interwork. <dt><tt><i>plainnat.bst</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.zip">macros/latex/contrib/natbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib/">browse</a>) <dt><tt><i>unsrtnat.bst</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.zip">macros/latex/contrib/natbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=citesort">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=citesort</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=citesort">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=citesort</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-clsvpkg.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-clsvpkg.html index 98120322eeb..b5b23e0c7b9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-clsvpkg.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-clsvpkg.html @@ -2,24 +2,24 @@ <title>UK TeX FAQ -- question label clsvpkg</title> </head><body> <h3>What are LaTeX classes and packages?</h3> -<p>Current LaTeX makes a distinction between the macros that define the +<p/>Current LaTeX makes a distinction between the macros that define the overall layout of a document, and the macros that tweak that layout (to one extent or another) to provide what the author <em>really</em> wants. -<p>The distinction was not very clear in LaTeX 2.09, and after some +<p/>The distinction was not very clear in LaTeX 2.09, and after some discussion (in the later stages of development of current LaTeX) the names “class” and “package” were applied to the two concepts. -<p>The idea is that a document’s <em>class</em> tells LaTeX what sort of +<p/>The idea is that a document’s <em>class</em> tells LaTeX what sort of document it’s dealing with, while the <em>packages</em> the document loads “refine” that overall specification. -<p>On the disc, the files only appear different by virtue of their name +<p/>On the disc, the files only appear different by virtue of their name “extension” — class files are called <code>*.cls</code> while package files are called <code>*.sty</code>. Thus we find that the LaTeX standard <i>article</i> class is represented on disc by a file called <i>article.cls</i>, while the <i>footmisc</i> package (which refines <i>article</i>’s definition of footnotes) is represented on disc by a file called <i>footmisc.sty</i>. -<p>The user defines the class of his document with the +<p/>The user defines the class of his document with the <code>\</code><code>documentclass</code> command (typically the first command in a document), and loads packages with the <code>\</code><code>usepackage</code> command. A document may have several <code>\</code><code>usepackage</code> commands, but it may have @@ -27,5 +27,5 @@ only one <code>\</code><code>documentclass</code> command. (Note that there are programming-interface versions of both commands, since a class may choose to load another class to refine its capabilities, and both classes and packages may choose to load other packages.) -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=clsvpkg">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=clsvpkg</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=clsvpkg">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=clsvpkg</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cmdstar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cmdstar.html index cb44adfe439..cd2b68610d8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cmdstar.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cmdstar.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label cmdstar</title> </head><body> <h3>Commands defined with * options</h3> -<p>LaTeX commands commonly have “versions” defined with an asterisk +<p/>LaTeX commands commonly have “versions” defined with an asterisk tagged onto their name: for example <code>\</code><code>newcommand</code> and <code>\</code><code>newcommand*</code> (the former defines a <code>\</code><code>long</code> version of the command). -<p>The simple-minded way for a user to write such a command involves use +<p/>The simple-minded way for a user to write such a command involves use of the <i>ifthen</i> package: <blockquote> <pre> @@ -22,7 +22,7 @@ of the <i>ifthen</i> package: This does the trick, for sufficiently simple commands, but it has various tiresome failure modes, and it requires <code>\</code><code>mycommandnostar</code> to take an argument. -<p>Of course, the LaTeX kernel has something slicker than this: +<p/>Of course, the LaTeX kernel has something slicker than this: <blockquote> <pre> \newcommand{\mycommand}{\@ifstar @@ -40,7 +40,7 @@ by the technique we’re using, unlike the trick described above.) The <code>\</code><code>@ifstar</code> trick is all very well, is fast and efficient, but it requires the definition to be <a href="FAQ-atsigns.html"><code>\</code><code>makeatletter</code> protected</a>. -<p>A pleasing alternative is the <i>suffix</i> package. This elegant +<p/>A pleasing alternative is the <i>suffix</i> package. This elegant piece of code allows you to define variants of your commands: <blockquote> @@ -64,6 +64,6 @@ definition like: <dt><tt><i>ifthen.sty</i></tt><dd>Part of the LaTeX distribution <dt><tt><i>suffix.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse</a>) </dl> -<p> +<p/> <p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cmdstar">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cmdstar</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-codelist.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-codelist.html index fc718386a86..a734782fae6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-codelist.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-codelist.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label codelist</title> </head><body> <h3>Code listings in LaTeX</h3> -<p>‘Pretty’ code listings are sometimes considered worthwhile by the +<p/>‘Pretty’ code listings are sometimes considered worthwhile by the “ordinary” programmer, but they have a serious place in the typesetting of dissertations by computer science and other students who are expected to write programs. Simple verbatim listings of programs are commonly useful, as well. -<p> <a href="FAQ-verbfile.html">Verbatim listings</a> are dealt with elsewhere, +<p/> <a href="FAQ-verbfile.html">Verbatim listings</a> are dealt with elsewhere, as is the problem of <a href="FAQ-algorithms.html">typesetting algorithm specifications</a>. -<p>The <i>listings</i> package is widely regarded as the best bet for +<p/>The <i>listings</i> package is widely regarded as the best bet for formatted output (it is capable of parsing program source, within the package itself), but there are several well-established packages that rely on a pre-compiler of some sort. You may use <i>listings</i> @@ -48,26 +48,26 @@ or you can have it typeset whole files: These very simple examples may be decorated in a huge variety of ways, and of course there are other languages in the package’s vocabulary than just <i>C</i>... -<p>Most people, advising others on (La)TeX lists, seem to regard +<p/>Most people, advising others on (La)TeX lists, seem to regard <i>listings</i> as the be-all and end-all on this topic. But there <em>are</em> alternatives, which may be worth considering, in some situations. -<p><i>Highlight</i> is attractive if you need more than one output +<p/><i>Highlight</i> is attractive if you need more than one output format for your program: as well as (La)TeX output, <i>highlight</i> will produce (X)HTML, RTF and XSL-FO representations of your program listing. Documentation is available on the <a href="http://www.andre-simon.de/"><i>highlight</a> project site</i>. -<p>The <i>lgrind</i> system is another well-established pre-compiler, +<p/>The <i>lgrind</i> system is another well-established pre-compiler, with all the facilities one might need and a wide repertoire of languages; it is derived from the very long-established <i>tgrind</i>, whose output is based on Plain TeX -<p>The <i>tiny_c2l</i> system is more recent: users are encouraged to +<p/>The <i>tiny_c2l</i> system is more recent: users are encouraged to generate their own driver files for languages it doesn’t already deal with. -<p>The <i>C++2LaTeX</i> system comes with strong recommendations for +<p/>The <i>C++2LaTeX</i> system comes with strong recommendations for use with C and C++. -<p>An extremely simple system is <i>c2latex</i>, for which you write +<p/>An extremely simple system is <i>c2latex</i>, for which you write LaTeX source in your C program comments. The program then converts your program into a LaTeX document for processing. The program (implicitly) claims to be “self-documenting”. @@ -80,5 +80,5 @@ program (implicitly) claims to be “self-documenting”. <dt><tt><i>tgrind</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/tgrind.zip">support/tgrind</a> (<a href="ftp://cam.ctan.org/tex-archive/support/tgrind.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/tgrind/">browse</a>) <dt><tt><i>tiny_c2l</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/tiny_c2l.zip">support/tiny_c2l</a> (<a href="ftp://cam.ctan.org/tex-archive/support/tiny_c2l.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/tiny_c2l/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=codelist">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=codelist</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=codelist">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=codelist</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-commercial.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-commercial.html index 141dc89d7ee..195e7d938ee 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-commercial.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-commercial.html @@ -3,13 +3,13 @@ </head><body> <h3>Commercial TeX implementations</h3> <!-- windows,macintosh,commercial --> -<p>There are many commercial implementations of TeX. The first +<p/>There are many commercial implementations of TeX. The first appeared not long after TeX itself appeared. -<p>What follows is probably an incomplete list. Naturally, no warranty or +<p/>What follows is probably an incomplete list. Naturally, no warranty or fitness for purpose is implied by the inclusion of any vendor in this list. The source of the information is given to provide some clues to its currency. -<p>In general, a commercial implementation will come ‘complete’, that is, +<p/>In general, a commercial implementation will come ‘complete’, that is, with suitable previewers and printer drivers. They normally also have extensive documentation (<em>i.e</em>., not just the TeXbook!) and some sort of support service. In some cases this is a toll free number @@ -76,9 +76,10 @@ also have email, and normal telephone and fax support. <blockquote> Dr Christopher Mabb<br> Scientific Word Ltd.<br> - 20 Bankpark Crescent<br> - Tranent<br> - East Lothian, EH33 1AS<br> + 990 Anlaby Road,<br> + Hull,<br> + East Yorkshire,<br> + HU4 6AT<br> UK<br> Tel: 0845 766 0340 (within the UK) <br> Fax: 0845 603 9443 (within the UK) <br> @@ -96,22 +97,24 @@ also have email, and normal telephone and fax support. Email: <a href="mailto:info@mackichan.com"><i>info@mackichan.com</i></a><br> Web: <a href="http://www.mackichan.com">http://www.mackichan.com</a> </blockquote><p> - Source: Mail from Christopher Mabb, November 2004 + Source: Mail from Christopher Mabb, August 2007 <dt>Macintosh; Textures<dd> “A TeX system ‘for the rest of - us’ ”; also gives away a Metafont implementation and some - font manipulation tools. + us’ ”. A beta release of Textures for MacOS/X is + available <a href="http://www.bluesky.com/news/220b.html">http://www.bluesky.com/news/220b.html</a> +<p/> (Blue Sky also gives away a Metafont implementation and some + font manipulation tools for Macs.) <blockquote> Blue Sky Research<br> - 534 SW Third Avenue<br> - Portland, OR 97204<br> + PO Box 80424<br> + Portland, OR 97280<br> USA<br> Tel: 800-622-8398 (within the USA)<br> - Tel: +1 503-222-9571<br> - Fax: +1 503-222-1643<br> + Tel/Fax: +1 503-222-9571<br> + Fax: +1 503-246-4574<br> Email: <a href="mailto:sales@bluesky.com"><i>sales@bluesky.com</i></a><br> Web: <a href="http://www.bluesky.com/">http://www.bluesky.com/</a> </blockquote><p> - Source: <i>TUGboat</i> 15(1) (1994) + Source: Mail from Gordon Lee, April 2007 <dt>AmigaTeX<dd> A full implementation for the Commodore Amiga, including full, on-screen and printing support for all PostScript graphics and fonts, IFF raster graphics, automatic font generation, @@ -126,12 +129,12 @@ also have email, and normal telephone and fax support. </dl> -<p>Note that the company Y&Y has gone out of business, and Y&Y +<p/>Note that the company Y&Y has gone out of business, and Y&Y TeX (and support for it) is therefore no longer available. Users of Y&Y systems may care to use the self-help <a href="http://tug.org/pipermail/yandytex/">mailing list</a> that was established in 2003; the remaining usable content of Y&Y’s web site is available at <a href="http://www.tug.org/yandy/">http://www.tug.org/yandy/</a> -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=commercial">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=commercial</a> +<p/> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=commercial">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=commercial</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-compactbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-compactbib.html index 3465a3bb995..8675cc55670 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-compactbib.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-compactbib.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label compactbib</title> </head><body> <h3>Reducing spacing in the bibliography</h3> -<p>Bibliographies are, in fact, implemented as lists, so all the +<p/>Bibliographies are, in fact, implemented as lists, so all the confusion about <a href="FAQ-complist.html">reducing list item spacing</a> also applies to bibliographies. -<p>If the <i>natbib</i> package ‘works’ for you (it may not if you are using +<p/>If the <i>natbib</i> package ‘works’ for you (it may not if you are using some special-purpose bibliography style), the solution is relatively simple — add <blockquote> @@ -15,7 +15,7 @@ simple — add </pre> </blockquote><p> to the preamble of your document. -<p>Otherwise, one is into unseemly hacking of something or other. The +<p/>Otherwise, one is into unseemly hacking of something or other. The <i>mdwlist</i> package actually does the job, but it doesn’t work here, because it makes a different-named list, while the name “<code>thebibliography</code>” is built into LaTeX and @@ -39,5 +39,5 @@ its other actions, and have it provide you a compressed bibliography <dt><tt><i>natbib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.zip">macros/latex/contrib/natbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib/">browse</a>) <dt><tt><i>savetrees.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/savetrees.zip">macros/latex/contrib/savetrees</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/savetrees.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/savetrees/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=compactbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=compactbib</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=compactbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=compactbib</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-compjobnam.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-compjobnam.html index 4f8b465b35e..616e7d9ecc0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-compjobnam.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-compjobnam.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label compjobnam</title> </head><body> <h3>Comparing the “job name”</h3> -<p>The token <code>\</code><code>jobname</code> amusingly produces a sequence of characters +<p/>The token <code>\</code><code>jobname</code> amusingly produces a sequence of characters whose category code is 12 (‘other’), regardless of what the characters actually are. Since one inevitably has to compare a macro with the contents of another macro (using <code>\</code><code>ifx</code>, somewhere) one needs to create a macro whose expansion looks the same as the expansion of <code>\</code><code>jobname</code>. We find we can do this with <code>\</code><code>meaning</code>, if we strip the “<code>\</code><code>show</code> command” prefix. -<p>The full command looks like: +<p/>The full command looks like: <blockquote> <pre> \def\StripPrefix#1>{} @@ -36,5 +36,5 @@ Note that the command <code>\</code><code>StripPrefix</code> need not be defined using LaTeX — there’s already an <a href="FAQ-atsigns.html">internal command</a> <code>\</code><code>strip@prefix</code> that you can use. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=compjobnam">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=compjobnam</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=compjobnam">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=compjobnam</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-complist.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-complist.html index 94d44e84ca4..81365892835 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-complist.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-complist.html @@ -1,8 +1,8 @@ <head> <title>UK TeX FAQ -- question label complist</title> </head><body> -<h3>How to reduce list spacing</h3> -<p><a href="FAQ-books.html">Lamport’s book</a> lists various +<h3>How to adjust list spacing</h3> +<p/><a href="FAQ-books.html">Lamport’s book</a> lists various parameters for the layout of list (things like <code>\</code><code>topsep</code>, <code>\</code><code>itemsep</code> and <code>\</code><code>parsep</code>), but fails to mention that they’re set automatically within the list itself. This happens because each list @@ -15,7 +15,7 @@ a document class designed with more modest list spacing, but we all know such things are hard to come by. The <i>memoir</i> class wasn’t designed for more compact lists <em>per se</em>, but offers the user control over the list spacing. -<p>There are packages that provide some control of list spacing, but they +<p/>There are packages that provide some control of list spacing, but they seldom address the separation from surrounding text (defined by <code>\</code><code>topsep</code>). The <i>expdlist</i> package, among its many controls of the appearance of <code>description</code> lists, offers a @@ -50,40 +50,53 @@ compaction: The package will manipulate its <code>enumerate</code> environment labels just like the <a href="FAQ-enumerate.html"><i>enumerate</i> package</a> does. -<p><i>Paralist</i> also provides <code>itemize</code> equivalents +<p/><i>Paralist</i> also provides <code>itemize</code> equivalents (<code>asparaitem</code>, etc.), and <code>description</code> equivalents (<code>asparadesc</code>, etc.). -<p>The <i>multenum</i> package offers a more regular form of +<p/>The <i>multenum</i> package offers a more regular form of <i>paralist</i>’s <code>inparaenum</code>; you define a notional grid on which list entries are to appear, and list items will always appear at positions on that grid. The effect is somewhat like that of the ‘tab’ keys on traditional typewriters; the package was designed for example sheets, or lists of answers in the appendices of a book. -<p>The ultimate in compaction (of every sort) is offered by the +<p/>The ultimate in compaction (of every sort) is offered by the <i>savetrees</i> package; compaction of lists is included. The package’s prime purpose is to save space at every touch and turn: don’t use it if you’re under any design constraint whatever! -<p>The <i>expdlist</i>, <i>mdwlist</i> and <i>paralist</i> +<p/>The <i>expdlist</i>, <i>mdwlist</i> and <i>paralist</i> packages all offer other facilities for list configuration: you should probably not try the “do-it-yourself” approaches outlined below if you need one of the packages for some other list configuration purpose. -<p>For ultimate flexibility (including manipulation of <code>\</code><code>topsep</code>), the +<p/>For ultimate flexibility (including manipulation of <code>\</code><code>topsep</code>), the <i>enumitem</i> package permits adjustment of list parameters using -a “<em>key</em>=<<i>value</i>>” format; so -for example, one might write +a “<em>key</em>=<<i>value</i>>” format. +For example, one might write <blockquote> <pre> \usepackage{enumitem} ... \begin{enumerate}[topsep=0pt, partopsep=0pt] -\item ... ... +\item ... +\item ... \end{enumerate} </pre> </blockquote><p> -to suppress all spacing above and below your list. <i>Enumitem</i> -also permits manipulation of the label format in a more “basic” -manner than the <a href="FAQ-enumerate.html"><i>enumerate</i> package</a> does. +to suppress all spacing above and below your list, or +<blockquote> +<pre> +\usepackage{enumitem} +... +\begin{enumerate}[itemsep=2pt,parsep=2pt] +\item ... +\item ... +\end{enumerate} +</pre> +</blockquote><p> +to set spacing between items and between paragraphs within items. +<i>Enumitem</i> also permits manipulation of the label format in a +more “basic” (and therefore more flexible) manner than the +<a href="FAQ-enumerate.html"><i>enumerate</i> package</a> does. <dl> <dt><tt><i>enumerate.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) <dt><tt><i>enumitem.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.zip">macros/latex/contrib/enumitem</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem/">browse</a>) @@ -94,5 +107,5 @@ manner than the <a href="FAQ-enumerate.html"><i>enumerate</i> package</a> does. <dt><tt><i>paralist.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/paralist.zip">macros/latex/contrib/paralist</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/paralist.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/paralist/">browse</a>) <dt><tt><i>savetrees.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/savetrees.zip">macros/latex/contrib/savetrees</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/savetrees.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/savetrees/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=complist">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=complist</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=complist">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=complist</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-concrete.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-concrete.html index 1b9f6ebe86b..388fc0299e8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-concrete.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-concrete.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label concrete</title> </head><body> <h3>Using the “Concrete” fonts</h3> -<p>The Concrete Roman fonts were designed by Don Knuth for a book called +<p/>The Concrete Roman fonts were designed by Don Knuth for a book called “Concrete Mathematics”, which he wrote with Graham and Patashnik (<em>the</em> Patashnik, of BibTeX fame). Knuth only designed text fonts, since the book used the Euler fonts for mathematics. The book was typeset using Plain TeX, of course, with additional macros that may be viewed in a file <i>gkpmac.tex</i>, which is available on CTAN. -<p>The packages <i>beton</i>, <i>concmath</i>, and +<p/>The packages <i>beton</i>, <i>concmath</i>, and <i>ccfonts</i> are LaTeX packages that change the default text fonts from Computer Modern to Concrete. Packages <i>beton</i> and <i>ccfonts</i> also slightly increase the default value of @@ -25,13 +25,13 @@ series of virtual fonts. While most modern distributions seem to have the requisite files installed by default, you may find you have to install them. If so, see the file <i>readme</i> in the <i>eulervm</i> distribution.) -<p>A few years after Knuth’s original design, Ulrik Vieth +<p/>A few years after Knuth’s original design, Ulrik Vieth designed the Concrete Math fonts. Packages <i>concmath</i>, and <i>ccfonts</i> also change the default math fonts from Computer Modern to Concrete and use the Concrete versions of the AMS fonts (this last behaviour is optional in the case of the <i>concmath</i> package). -<p>There are no bold Concrete fonts, but it is generally accepted that +<p/>There are no bold Concrete fonts, but it is generally accepted that the Computer Modern Sans Serif demibold condensed fonts are an adequate substitute. If you are using <i>concmath</i> or <i>ccfonts</i> and you want to follow this suggestion, then use the @@ -43,7 +43,7 @@ add <code>\</code><code>renewcommand{<code>\</code><code>bfdefault</code>}{sbc}</code> </blockquote><p> to the preamble of your document. -<p>Type 1 versions of the fonts are available. For OT1 encoding, +<p/>Type 1 versions of the fonts are available. For OT1 encoding, they are available from <a href="FAQ-psfchoice.html">MicroPress</a>. The <a href="FAQ-textrace.html">CM-Super fonts</a> contain Type 1 versions of the Concrete fonts in T1 encoding. @@ -58,5 +58,5 @@ of the Concrete fonts in T1 encoding. <dt><tt><i>eulervm bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/eulervm.zip">fonts/eulervm</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/eulervm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/eulervm/">browse</a>) <dt><tt><i>gkpmac.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/knuth/local/lib/gkpmac.tex">systems/knuth/local/lib/gkpmac.tex</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=concrete">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=concrete</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=concrete">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=concrete</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-conditional.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-conditional.html index 48dd3c2ca81..b76b84ca806 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-conditional.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-conditional.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label conditional</title> </head><body> <h3>Conditional compilation and “comments”</h3> -<p>While LaTeX (or any other TeX-derived package) isn’t really like a +<p/>While LaTeX (or any other TeX-derived package) isn’t really like a compiler, people regularly want to do compiler-like things using it. Common requirements are conditional ‘compilation’ and ‘block comments’, and several LaTeX-specific means to this end are available. -<p>The simple <code>\</code><code>newcommand{<code>\</code><code>gobble</code>}[1]</code><code>{</code><code>}</code> and +<p/>The simple <code>\</code><code>newcommand{<code>\</code><code>gobble</code>}[1]</code><code>{</code><code>}</code> and <code>\</code><code>iffalse</code><code> ... </code><code>\</code><code>fi</code> aren’t really satisfactory (as a general solution) for comments, since the matter being skipped is nevertheless scanned by TeX, not always as you would expect. The scanning @@ -27,7 +27,7 @@ The <code>\</code><code>iftrue</code> is spotted by TeX as it scans, ignoring th following <code>\</code><code>fi</code>. Also, <code>\</code><code>gobble</code> is pretty inefficient at consuming anything non-trivial, since all the matter to be skipped is copied to the argument stack before being ignored. -<p>If your requirement is for a document from which whole chapters (or +<p/>If your requirement is for a document from which whole chapters (or the like) are missing, consider the LaTeX <code>\</code><code>include</code>/<code>\</code><code>includeonly</code> system. If you ‘<code>\</code><code>include</code>’ your files (rather than <code>\</code><code>input</code> them — see @@ -40,10 +40,10 @@ processing continues as if they <em>were</em> there, and page, footnote, and other numbers are not disturbed. Note that you can choose which sections you want included interactively, using the <i>askinclude</i> package. -<p>The inverse can be done using the <i>excludeonly</i> package: this +<p/>The inverse can be done using the <i>excludeonly</i> package: this allows you to exclude a (list of) <code>\</code><code>include</code>d files from your document, by means of an <code>\</code><code>excludeonly</code> command. -<p>If you want to select particular pages of your document, use Heiko +<p/>If you want to select particular pages of your document, use Heiko Oberdiek’s <i>pagesel</i> or the <i>selectp</i> packages. You can do something similar with an existing PDF document (which you may have compiled using <i>pdflatex</i> in the first place), @@ -65,10 +65,10 @@ document looking like: </pre> </blockquote><p> omitting the start and end pages in the optional argument.) -<p>If you want flexible facilities for including or excluding small +<p/>If you want flexible facilities for including or excluding small portions of a file, consider the <i>comment</i>, <i>version</i> or <i>optional</i> packages. -<p>The <i>comment</i> package allows you to declare areas of a document to be +<p/>The <i>comment</i> package allows you to declare areas of a document to be included or excluded; you make these declarations in the preamble of your file. The command <code>\</code><code>includecomment{</code><em>version-name</em><code>}</code> declares an environment <code>version-name</code> whose content will @@ -77,20 +77,20 @@ be included in your document, while content will be excluded from the document. The package uses a method for exclusion that is pretty robust, and can cope with ill-formed bunches of text (e.g., with unbalanced braces or <code>\</code><code>if</code> commands). -<p>These FAQs employ the <i>comment</i> package to alter layout +<p/>These FAQs employ the <i>comment</i> package to alter layout between the printed (two-column) version and the PDF version for browsing; there are <code>narrowversion</code> and <code>wideversion</code> for the two versions of the file. -<p><i>version</i> offers similar facilities to <i>comment.sty</i> +<p/><i>version</i> offers similar facilities to <i>comment.sty</i> (i.e., <code>\</code><code>includeversion</code> and <code>\</code><code>excludeversion</code> commands); it’s far “lighter weight”, but is less robust (and in particular, cannot deal with very large areas of text being included/excluded). -<p>A significant development of <i>version</i>, confusingly called +<p/>A significant development of <i>version</i>, confusingly called <i>versions</i> (i.e., merely a plural of the old package name). <i>Versions</i> adds a command <code>\</code><code>markversion{</code><em>version-name</em><code>}</code> which defines an environment that prints the included text, with a clear printed mark around it. -<p><i>optional</i> defines a command <code>\</code><code>opt</code>; its first argument is +<p/><i>optional</i> defines a command <code>\</code><code>opt</code>; its first argument is an ‘inclusion flag’, and its second is text to be included or excluded. Text to be included or excluded must be well-formed (nothing mismatched), and should not be too big — if a large body of @@ -100,13 +100,13 @@ how to declare which sections are to be included: this can be done in the document preamble, but the documentation also suggests ways in which it can be done on the command line that invokes LaTeX, or interactively. -<p>And, not least of this style of conditional compilation, +<p/>And, not least of this style of conditional compilation, <i>verbatim</i> (which should be available in any distribution) defines a <code>comment</code> environment, which enables the dedicated user of the source text editor to suppress bits of a LaTeX source file. The <i>memoir</i> class offers the same environment. -<p>An interesting variation is the <i>xcomment</i> package. This +<p/>An interesting variation is the <i>xcomment</i> package. This defines an environment whose body is all excluded, apart from environments named in its argument. So, for example: <blockquote> @@ -124,7 +124,7 @@ environments named in its argument. So, for example: \end{xcomment} </pre> </blockquote><p> -<p>A further valuable twist is offered by the <i>extract</i> package. +<p/>A further valuable twist is offered by the <i>extract</i> package. This allows you to produce a “partial copy” of an existing document: the package was developed to permit production of a “book of examples” from a set of lecture notes. The package documentation @@ -149,13 +149,14 @@ including (numeric or labelled) ranges of environments to extract, and an <code>extract</code> environment which you can use to create complete ready-to-run LaTeX documents with stuff you’ve extracted. <dl> -<dt><tt><i>askinclude.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/askinclude.sty">macros/latex/contrib/misc/askinclude.sty</a> +<dt><tt><i>askinclude.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages — + <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>) <dt><tt><i>comment.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/comment.zip">macros/latex/contrib/comment</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/comment.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/comment/">browse</a>) <dt><tt><i>excludeonly.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/excludeonly.sty">macros/latex/contrib/misc/excludeonly.sty</a> <dt><tt><i>extract.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/extract.zip">macros/latex/contrib/extract</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/extract.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/extract/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>optional.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/optional.sty">macros/latex/contrib/misc/optional.sty</a> -<dt><tt><i>pagesel.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages +<dt><tt><i>pagesel.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages — <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>) <dt><tt><i>pdfpages.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdfpages.zip">macros/latex/contrib/pdfpages</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdfpages.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdfpages/">browse</a>) <dt><tt><i>selectp.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/selectp.sty">macros/latex/contrib/misc/selectp.sty</a> @@ -164,5 +165,5 @@ ready-to-run LaTeX documents with stuff you’ve extracted. <dt><tt><i>versions.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/versions/versions.sty">macros/latex/contrib/versions/versions.sty</a> <dt><tt><i>xcomment.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/seminar.zip">macros/latex/contrib/seminar</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/seminar.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/seminar/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=conditional">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=conditional</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=conditional">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=conditional</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-context.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-context.html index 8a87be7f21e..c3f57b68c60 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-context.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-context.html @@ -2,26 +2,49 @@ <title>UK TeX FAQ -- question label context</title> </head><body> <h3>What is ConTeXt?</h3> -<p><a href="http://www.pragma-ade.com/">ConTeXt</a> is a macro package -developed by Hans Hagen, originally to -serve the needs of his (Dutch) firm Pragma. It was designed with the -same general-purpose aims as LaTeX, but (being younger) reflects -much more recent thinking about the structure of markup, etc. In -particular, ConTeXt can customise its markup to an -author’s language (customising modules for Dutch, English and German -are provided, at present). -<p>ConTeXt is well integrated, in all of its structure, -with the needs of hypertext markup, and in particular with the -facilities offered by <a href="FAQ-whatpdftex.html">PDFTeX</a>. -The default installation employs a version of PDFTeX built with the -<a href="FAQ-etex.html">e-TeX extensions</a>, which allows further flexibility. -<p>ConTeXt doesn’t yet have quite such a large developer community as +<p/><a href="http://www.pragma-ade.com/">ConTeXt</a> is a macro package +developed by Hans Hagen of Pragma-Ade. ConTeXt is a +document-production system based, like LaTeX, on the TeX +typesetting system. Whereas LaTeX insulates the writer from +typographical details, ConTeXt takes a complementary approach by +providing structured interfaces for handling typography, including +extensive support for colors, backgrounds, hyperlinks, presentations, +figure-text integration, and conditional compilation. It gives the +user extensive control over formatting while making it easy to create +new layouts and styles without learning the TeX macro +language. ConTeXt’s unified design avoids the package clashes that +can happen with LaTeX. +<p/>ConTeXt also integrates MetaFun, a superset of MetaPost and a powerful +system for vector graphics. MetaFun can be used as a stand-alone +system to produce figures, but its strength lies in enhancing +ConTeXt documents with accurate graphic elements. +<p/>ConTeXt allows the users to specify formatting commands in English, +Dutch, German, French, or Italian, and to use different typesetting +engines (PDFTeX, XeTeX, Aleph, and soon LuaTeX) without +changing the user interface. ConTeXt is developed rapidly, often in +response to requests from the user community. +<p/> + + + + + + + + + + + + + +<p/>ConTeXt doesn’t yet have quite such a large developer community as does LaTeX, but those developers who are active seem to have -prodigious energy. Some support is available via a -<a href="http://contextgarden.net/">WIKI site</a>. +prodigious energy. Support is available via a +<a href="http://contextgarden.net">WIKI site</a> and via the +<a href="http://www.ntg.nl/mailman/listinfo/ntg-context">mailing list</a>. <dl> <dt><tt><i>ConTeXt distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/context.zip">macros/context</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/context.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/context/">browse</a>) </dl> -<p> +<p/> <p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=context">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=context</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-crop.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-crop.html index 7f02601736f..2c86ecce729 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-crop.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-crop.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label crop</title> </head><body> <h3>How to create crop marks</h3> -<p>If you’re printing something that’s eventually to be reproduced in +<p/>If you’re printing something that’s eventually to be reproduced in significant quantities, and bound, it’s conventional to print on paper larger than your target product, and to place “crop marks” outside the printed area. These crop marks are available to the production house, for lining up reproduction and trimming machines. -<p>You can save yourself the (considerable) trouble of programming these +<p/>You can save yourself the (considerable) trouble of programming these marks for yourself by using the package <i>crop</i>, which has facilities to satisfy any conceivable production house. Users of the <i>memoir</i> class don’t need the package, since <i>memoir</i> has @@ -16,5 +16,5 @@ its own facilities for programming crop marks. <dt><tt><i>crop.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/crop.zip">macros/latex/contrib/crop</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/crop.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/crop/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=crop">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=crop</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=crop">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=crop</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-crossref.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-crossref.html index 914cc1e9db3..c4b0763ff22 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-crossref.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-crossref.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label crossref</title> </head><body> <h3>LaTeX gets cross-references wrong</h3> -<p>Sometimes, however many times you run LaTeX, the cross-references +<p/>Sometimes, however many times you run LaTeX, the cross-references are just wrong. Remember that the <code>\</code><code>label</code> command must come <em>after</em> the <code>\</code><code>caption</code> command, or be part of it. For example, @@ -13,7 +13,7 @@ be part of it. For example, \label{fig} \label{fig}} \end{figure} \end{figure} </pre> -<p>You can, just as effectively, shield the <code>\</code><code>caption</code> command from its +<p/>You can, just as effectively, shield the <code>\</code><code>caption</code> command from its associated <code>\</code><code>label</code> command, by enclosing the caption in an environment of its own. For example, people commonly seek help after: <blockquote> @@ -34,5 +34,5 @@ those in the know commonly reject it), code it as: \end{center} </pre> </blockquote><p> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=crossref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=crossref</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=crossref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=crossref</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-csname.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-csname.html index abf7849cbbb..d2abced359a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-csname.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-csname.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label csname</title> </head><body> <h3>Defining a macro from an argument</h3> -<p>It’s common to want a command to create another command: often one +<p/>It’s common to want a command to create another command: often one wants the new command’s name to derive from an argument. LaTeX does this all the time: for example, <code>\</code><code>newenvironment</code> creates start- and end-environment commands whose names are derived from the name of the environment command. -<p>The (seemingly) obvious approach: +<p/>The (seemingly) obvious approach: <blockquote> <pre> \def\relay#1#2{\def\#1{#2}} @@ -27,11 +27,11 @@ above should read: </blockquote><p> With this definition, <code>\</code><code>relay{blah}{bleah}</code> is equivalent to <code>\</code><code>def</code><code>\</code><code>blah{bleah}</code>. -<p>Note that the definition of <code>\</code><code>relay</code> omits the braces round the +<p/>Note that the definition of <code>\</code><code>relay</code> omits the braces round the ‘command name’ in the <code>\</code><code>newcommand</code> it executes. This is because they’re not necessary (in fact they seldom are), and in this circumstance they make the macro code slightly more tedious. -<p>The name created need not (of course) be <em>just</em> the argument: +<p/>The name created need not (of course) be <em>just</em> the argument: <blockquote> <pre> @@ -53,5 +53,5 @@ With commands </pre> </blockquote><p> these ‘races’ could behave a bit like LaTeX environments. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=csname">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=csname</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=csname">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=csname</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-custbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-custbib.html index 893603414ef..69209eed9eb 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-custbib.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-custbib.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label custbib</title> </head><body> <h3>Creating a bibliography style</h3> -<p>It <em>is</em> possible to write your own: the standard bibliography +<p/>It <em>is</em> possible to write your own: the standard bibliography styles are distributed in a commented form, and there is a description of the language (see @@ -11,7 +11,7 @@ However, it must be admitted that the language in which BibTeX styles are written is pretty obscure, and one would not recommend anyone who’s not a confident programmer to write their own, though minor changes to an existing style may be within the grasp of many. -<p>If your style isn’t too ‘far out’, you can probably generate it by +<p/>If your style isn’t too ‘far out’, you can probably generate it by using the facilities of the <i>custom-bib</i> bundle. This contains a file <i>makebst.tex</i>, which runs you through a text menu to produce a file of instructions, with which you can generate your @@ -22,5 +22,5 @@ offer significantly more than the BibTeX standard set. <dt><tt><i>BibTeX documentation</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/distribs/doc.zip">biblio/bibtex/distribs/doc</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/distribs/doc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/distribs/doc/">browse</a>) <dt><tt><i>makebst.tex</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/custom-bib.zip">macros/latex/contrib/custom-bib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/custom-bib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/custom-bib/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=custbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=custbib</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=custbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=custbib</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cv.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cv.html index 043e5ae246e..caa9ad674ba 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cv.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cv.html @@ -2,33 +2,33 @@ <title>UK TeX FAQ -- question label cv</title> </head><body> <h3><em>Curriculum Vitae</em> (Résumé)</h3> -<p>Andrej Brodnik’s class, <i>vita</i>, offers a framework for producing +<p/>Andrej Brodnik’s class, <i>vita</i>, offers a framework for producing a <em>curriculum vitae</em>. The class may be customised both for subject (example class option files support both computer scientists and singers), and for language (both the options provided are available for both English and Slovene). Extensions may be written by creating new class option files, or by using macros defined in the class to define new entry types, etc. -<p>Didier Verna’s class, <i>curve</i>, is based on a model in which +<p/>Didier Verna’s class, <i>curve</i>, is based on a model in which the CV is made of a set of <em>rubrics</em> (each one dealing with a major item that you want to discuss, such as ‘education’, ‘work experience’, etc). The class’s documentation is supported by a couple of example files, and an emacs mode is provided. -<p>Xavier Danaux offers a class <i>moderncv</i> which supports +<p/>Xavier Danaux offers a class <i>moderncv</i> which supports typesetting modern <em>curricula vitarum</em>, both in a classic and in a casual style. It is fairly customizable, allowing you to define your own style by changing the colours, the fonts, etc. -<p>The European Commission has recommended a format for +<p/>The European Commission has recommended a format for <em>curricula vitarum</em> within Europe, and Nicola Vitacolonna has developed a class <i>europecv</i> to produce it. While (by his own admission) the class doesn’t solve all problems, it seems well-thought out and supports all current official EU languages (together with a few non-official languages, such as Catalan, Galician and Serbian). -<p>The alternative to using a separate class is to impose a package on +<p/>The alternative to using a separate class is to impose a package on one of the standard classes. An example, Axel Reichert’s <i>currvita</i> package, has been recommended to the FAQ team. Its output certainly looks good. -<p>There is also a LaTeX 2.09 package <i>resume</i>, which comes with +<p/>There is also a LaTeX 2.09 package <i>resume</i>, which comes with little but advice <em>against</em> trying to use it. <dl> <dt><tt><i>currvita.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/currvita.zip">macros/latex/contrib/currvita</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/currvita.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/currvita/">browse</a>) @@ -38,5 +38,5 @@ little but advice <em>against</em> trying to use it. <dt><tt><i>resume.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/obsolete/macros/latex209/contrib/resume/resume.sty">obsolete/macros/latex209/contrib/resume/resume.sty</a> <dt><tt><i>vita.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/vita.zip">macros/latex/contrib/vita</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/vita.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/vita/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cv">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cv</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cv">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cv</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cvtlatex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cvtlatex.html index 30e02ea73ab..cdaf84cfbbf 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cvtlatex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-cvtlatex.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label cvtlatex</title> </head><body> <h3>Transcribing LaTeX command definitions</h3> -<p>At several places in this FAQ, questions are answered in terms +<p/>At several places in this FAQ, questions are answered in terms of how to program a LaTeX macro. Sometimes, these macros might also help users of Plain TeX or other packages; this answer attempts to provide a rough-and-ready guide to transcribing such macro definitions for use in other packages. -<p>The reason LaTeX has commands that replace <code>\</code><code>def</code>, is that +<p/>The reason LaTeX has commands that replace <code>\</code><code>def</code>, is that there’s a general philosophy within LaTeX that the user should be protected from himself: the user has different commands according to whether the command to be defined exists (<code>\</code><code>renewcommand</code>) or not @@ -21,13 +21,13 @@ the present state of the command. The final command of this sort is expansion”); from the Plain TeX user’s point of view, <code>\</code><code>DeclareRobustCommand</code> should be treated as a non-checking version of <code>\</code><code>newcommand</code>. -<p>LaTeX commands are, by default, defined <code>\</code><code>long</code>; an optional <code>*</code> +<p/>LaTeX commands are, by default, defined <code>\</code><code>long</code>; an optional <code>*</code> between the <code>\</code><code>newcommand</code> and its (other) arguments specifies that the command is <em>not</em> to be defined <code>\</code><code>long</code>. The <code>*</code> is detected by a command <code>\</code><code>@ifstar</code> which uses <code>\</code><code>futurelet</code> to switch between two branches, and gobbles the <code>*</code>: LaTeX users are encouraged to think of the <code>*</code> as part of the command name. -<p>LaTeX’s checks for unknown command are done by <code>\</code><code>ifx</code> comparison +<p/>LaTeX’s checks for unknown command are done by <code>\</code><code>ifx</code> comparison of a <code>\</code><code>csname</code> construction with <code>\</code><code>relax</code>; since the command name argument is the desired control sequence name, this proves a little long-winded. Since <code>#1</code> is the requisite argument, we have: @@ -41,7 +41,7 @@ long-winded. Since <code>#1</code> is the requisite argument, we have: </pre> </blockquote><p> (<code>\</code><code>@gobble</code> simply throws away its argument). -<p>The arguments of a LaTeX command are specified by two optional +<p/>The arguments of a LaTeX command are specified by two optional arguments to the defining command: a count of arguments (0–9: if the count is 0, the optional count argument may be omitted), and a default value for the first argument, if the defined command’s first argument @@ -58,7 +58,7 @@ In the last case, <code>\</code><code>foo</code> may be called as <code>\</code> which is equivalent to <code>\</code><code>foo[boo]{goodbye}</code> (employing the default value given for the first argument), or as <code>\</code><code>foo[hello]{goodbye}</code> (with an explicit first argument). -<p>Coding of commands with optional arguments is exemplified by the +<p/>Coding of commands with optional arguments is exemplified by the coding of the last <code>\</code><code>foo</code> above: <blockquote> <pre> @@ -73,5 +73,5 @@ coding of the last <code>\</code><code>foo</code> above: \def\@x@foo[#1]#2{...#1...#2...} </pre> </blockquote><p> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cvtlatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cvtlatex</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cvtlatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=cvtlatex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dec_comma.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dec_comma.html index da92267ebfe..0483d24f15c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dec_comma.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dec_comma.html @@ -2,24 +2,40 @@ <title>UK TeX FAQ -- question label dec_comma</title> </head><body> <h3>The comma as a decimal separator</h3> -<p>If you use a comma in maths mode, you get a small space after it; this -space is inappropriate if the comma is being used as a decimal -separator. An easy solution to this problem, in maths -mode, is to type <code>3</code><code>{,}</code><code>14</code> instead of typing -<code>3,14</code>. However, if your language’s -typographic rules require the comma as a decimal separator, such usage -can rapidly become extremely tiresome. There are two packages that +<p/>TeX embodies the British/American cultural convention of using a +period as the separator between the whole number and the decimal +fraction part of a decimal number. Other cultures use a comma as +separator, but if you use a comma in maths mode you get a small space +after it; this space makes a comma that is used as a decimal separator +look untidy. +<p/>A simple solution to this problem, in maths mode, is to type +<code>3</code><code>{,}</code><code>14</code> in place of <code>3,14</code>. While such a +technique may produce the right results, it is plainly not a +comfortable way to undertake any but the most trivial amounts of +typing numbers. +<p/>Therefore, if you need to use commas as decimal separator, you will +probably welcome macro support. There are two packages that can help relieve the tedium: <i>icomma</i> and <i>ziffer</i>. -<p><i>Icomma</i> ensures that there will be no extra space after a -comma, unless you type a space after it (as in <code>f(x, y)</code>, for -instance), in which case the usual small space after the comma -appears. <i>Ziffer</i> is specifically targeted at the needs of -those typesetting German, but covers the present need, as well as -providing the double-minus sign used in German (and other languages) -for the empty ‘cents’ part of an amount of currency. +<p/><i>Icomma</i> ensures that there will be no extra space after a +comma, unless you type a space after it (as in <code>f(x, y)</code> — in +the absence of the package, you don’t need that space), in which case +the usual small space after the comma appears. <i>Ziffer</i> is +specifically targeted at the needs of those typesetting German, but +covers the present need, as well as providing the double-minus sign +used in German (and other languages) for the empty ‘cents’ part of an +amount of currency. +<p/>The <i>numprint</i> package provides a command +<code>\</code><code>numprint{</code><em>number</em><code>}</code> that prints its argument according to +settings you give it, or according to settings chosen to match the +language you have selected in <i>babel</i>. The formatting works +equally well in text or maths. The command is very flexible (it can also +group the digits of very ‘long’ numbers), but is inevitably less +convenient than <i>icomma</i> or <i>ziffer</i> if you are typing a +lot of numbers. <dl> <dt><tt><i>icomma.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/was.zip">macros/latex/contrib/was</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/was.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/was/">browse</a>) +<dt><tt><i>numprint.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/numprint.zip">macros/latex/contrib/numprint</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/numprint.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/numprint/">browse</a>) <dt><tt><i>ziffer.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/ziffer.sty">macros/latex/contrib/misc/ziffer.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dec_comma">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dec_comma</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dec_comma">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dec_comma</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-destable.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-destable.html index 99b0c00764b..df8a05647fc 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-destable.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-destable.html @@ -2,22 +2,22 @@ <title>UK TeX FAQ -- question label destable</title> </head><body> <h3>The design of tables</h3> -<p>In recent years, several authors have argued that the examples, set +<p/>In recent years, several authors have argued that the examples, set out by Lamport in his <a href="FAQ-books.html">LaTeX manual</a>, have cramped authors’ style and have led to extremely poor table design. It is in fact difficult even to work out what many of the examples in Lamport’s book “mean”. -<p>The criticism focuses on the excessive use of rules (both horizontal +<p/>The criticism focuses on the excessive use of rules (both horizontal and vertical) and on the poor vertical spacing that Lamport’s macros offer. -<p>The problem of vertical spacing is plain for all to see, and is +<p/>The problem of vertical spacing is plain for all to see, and is addressed in several packages — see “<a href="FAQ-struttab.html">spacing of lines in tables</a>”. -<p>The argument about rules is presented in the excellent essay that +<p/>The argument about rules is presented in the excellent essay that prefaces the documentation of Simon Fear’s <i>booktabs</i> package, which (of course) implements Fear’s scheme for ‘comfortable’ rules. (The same rule commands are implemented in the <i>memoir</i> class.) -<p>Lamport’s LaTeX was also inflexibly wrong in “insisting” that +<p/>Lamport’s LaTeX was also inflexibly wrong in “insisting” that captions should come at the bottom of a table. Since a table may extend over several pages, traditional typography places the caption at the top of a table float. The <code>\</code><code>caption</code> command will get its @@ -56,7 +56,7 @@ with an option that has the same effect: \usepackage[tableposition=top]{caption} </pre> </blockquote><p> -<p>Doing the job yourself is pretty easy: <i>topcapt</i> switches the +<p/>Doing the job yourself is pretty easy: <i>topcapt</i> switches the values of the LaTeX2e parameters <code>\</code><code>abovecaptionskip</code> (default value <code>10pt</code>) and <code>\</code><code>belowcaptionskip</code> (default value <code>0pt</code>), so: <blockquote> @@ -78,5 +78,5 @@ does the job. (The package itself is very slightly more elaborate...) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>topcapt.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/topcapt.sty">macros/latex/contrib/misc/topcapt.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=destable">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=destable</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=destable">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=destable</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-distill-prob.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-distill-prob.html index 1fc2a3375fe..c5f3d90571e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-distill-prob.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-distill-prob.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label distill-prob</title> </head><body> <h3>Characters missing from PDF output</h3> -<p>If you’re using <i>Acrobat</i> <i>Distiller</i> to create your +<p/>If you’re using <i>Acrobat</i> <i>Distiller</i> to create your PDF output, you may find characters missing. This may manifest itself as messed-up maths equations (missing @@ -10,26 +10,26 @@ itself as messed-up maths equations (missing from large symbols. Early versions of <i>Distiller</i> used to ignore character positions 0–31 and 128–159 of every font: Adobe’s fonts never use such positions, so why should <i>Distiller</i>? -<p>Well, the answer to this question is “because Adobe don’t produce all +<p/>Well, the answer to this question is “because Adobe don’t produce all the world’s fonts” — fonts like <i>Computer</i> <i>Modern</i> were around before Adobe came on the scene, and <em>they</em> use positions 0–31. Adobe don’t react to complaints like that in the previous sentence, but they do release new versions of their programs; and <i>Distiller</i>, since at least version 4.0, <em>has</em> recognised the font positions it used to shun. -<p>Meanwhile, TeX users with old versions of <i>Distiller</i> need +<p/>Meanwhile, TeX users with old versions of <i>Distiller</i> need to deal with their fonts. <i>Dvips</i> comes to our aid: the switch <code>-G1</code> (“remap characters”), which moves the offending characters out of the way. The PDF configuration file (<code>-Ppdf</code>), recommended in “<a href="FAQ-fuzzy-type3.html">the wrong type of fonts</a>”, includes the switch. -<p>The switch is not without its problems; pre-2003 versions of +<p/>The switch is not without its problems; pre-2003 versions of <i>dvips</i> will apply it to Adobe fonts as well, causing <a href="FAQ-charshift.html">havoc</a>, but fortunately that problem is usually soluble. However, a document using both CM and Adobe-specified fonts is stuck. The only real solution is either to upgrade <i>dvips</i>, or to spend money to upgrade <i>Distiller</i>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=distill-prob">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=distill-prob</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=distill-prob">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=distill-prob</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-divzero.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-divzero.html index 24b188bd6e0..675a02de27b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-divzero.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-divzero.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label divzero</title> </head><body> <h3>Graphics division by zero</h3> -<p>While the error +<p/>While the error <blockquote> <pre> ! Package graphics Error: Division by 0. @@ -10,12 +10,12 @@ </blockquote><p> can actually be caused by offering the package a figure which claims to have a zero dimension, it’s more commonly caused by rotation. -<p>Objects in TeX may have both height (the height above the baseline) +<p/>Objects in TeX may have both height (the height above the baseline) and depth (the distance the object goes below the baseline). If you rotate an object by 180 degrees, you convert its height into depth, and vice versa; if the object started with zero depth, you’ve converted it to a zero-height object. -<p>Suppose you’re including your graphic with a command like: +<p/>Suppose you’re including your graphic with a command like: <blockquote> <pre> \includegraphics[angle=180,height=5cm]{myfig.eps} @@ -24,7 +24,7 @@ converted it to a zero-height object. </blockquote><p> In the case that <i>myfig.eps</i> has no depth to start with, the scaling calculations will produce the division-by-zero error. -<p>Fortunately, the <i>graphicx</i> package has a keyword +<p/>Fortunately, the <i>graphicx</i> package has a keyword <code>totalheight</code>, which allows you to specify the size of the image relative to the sum of the object’s <code>height</code> and <code>depth</code>, so @@ -35,7 +35,7 @@ image relative to the sum of the object’s <code>height</code> and </blockquote><p> will resolve the error, and will behave as you might hope. -<p>If you’re using the simpler <i>graphics</i> package, use the +<p/>If you’re using the simpler <i>graphics</i> package, use the <code>*</code> form of the <code>\</code><code>resizebox</code> command to specify the use of <code>totalheight</code>: <blockquote> @@ -50,5 +50,5 @@ will resolve the error, and will behave as you might hope. <dl> <dt><tt><i>graphics.sty,graphicx.sty</i></tt><dd>Both parts of the <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) bundle </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=divzero">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=divzero</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=divzero">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=divzero</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-doc-dirs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-doc-dirs.html index e79b23ff057..577b074dc47 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-doc-dirs.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-doc-dirs.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label doc-dirs</title> </head><body> <h3>Directories of (La)TeX information</h3> -<p>TUG India is developing a series of online LaTeX tutorials +<p/>TUG India is developing a series of online LaTeX tutorials which can be strongly recommended: select single chapters at a time from <a href="http://www.tug.org.in/tutorials.html">http://www.tug.org.in/tutorials.html</a> — the set comprises two parts, “Text” and “Graphics”, so far. -<p>Herbert Voss’s excellent +<p/>Herbert Voss’s excellent <a href="http://texnik.de/">LaTeX tips and tricks</a> is an excellent source of small articles on the use of LaTeX. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-dirs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-dirs</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-dirs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-dirs</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-doc-wiki.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-doc-wiki.html index 16432550efd..14f72dc46ec 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-doc-wiki.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-doc-wiki.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label doc-wiki</title> </head><body> <h3>WIKI pages for TeX and friends</h3> -<p>The <em>WIKI</em> concept can be a boon to everyone, if used sensibly. +<p/>The <em>WIKI</em> concept can be a boon to everyone, if used sensibly. The “general” WIKI allows <em>anyone</em> to add stuff, or to edit stuff that someone else has added: while there is obvious potential for chaos, there is evidence that a strong user community can keep a WIKI under control. -<p>Following the encouraging performance of the +<p/>Following the encouraging performance of the <a href="http://contextgarden.net/">ConTeXt WIKI</a>, both a <a href="http://en.wikibooks.org/wiki/TeX">(Plain) TeX WIKI</a> and a <a href="http://en.wikibooks.org/wiki/LaTeX">LaTeX WIKI</a> have been @@ -17,5 +17,5 @@ the LaTeX WIKI has details on the <a href="FAQ-eqnarray.html">use of the <code>eqnarray</code> environment</a>); however one may hope that both will become useful resources in the longer term. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-wiki">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-wiki</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-wiki">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=doc-wiki</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-docotherdir.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-docotherdir.html index ef9c4ba7155..aa6074b7fed 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-docotherdir.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-docotherdir.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label docotherdir</title> </head><body> <h3>Bits of document from other directories</h3> -<p>A common way of constructing a large document is to break it into a +<p/>A common way of constructing a large document is to break it into a set of files (for example, one per chapter) and to keep everything related to each of these subsidiary files in a subdirectory. -<p>Unfortunately, TeX doesn’t have a changeable “current directory”, +<p/>Unfortunately, TeX doesn’t have a changeable “current directory”, so that all files you refer to have to be specified relative to the same directory as the main file. Most people find this counter-intuitive. -<p>It may be appropriate to use the “path extension” technique +<p/>It may be appropriate to use the “path extension” technique <a href="FAQ-tempinst.html">used in temporary installations</a> to deal with this problem. However, if there several files with the same name in @@ -20,7 +20,7 @@ which you’re referring to when in the main chapter file you say human-prepared files (just don’t name them all the same), automatically produced files have a way of having repetitious names, and changing <em>them</em> is a procedure prone to error. -<p>The <i>import</i> package comes to your help here: it defines an +<p/>The <i>import</i> package comes to your help here: it defines an <code>\</code><code>import</code> command that accepts a full path name and the name of a file in that directory, and arranges things to “work properly”. So, for example, if <i>/home/friend/results.tex</i> contains @@ -35,7 +35,7 @@ graph and explanation as one might hope. A <code>\</code><code>subimport</code> does the same sort of thing for a subdirectory (a relative path rather than an absolute one), and there are corresponding <code>\</code><code>includefrom</code> and <code>\</code><code>subincludefrom</code> commands. -<p>The <i>chapterfolder</i> package provides commands to deal with its +<p/>The <i>chapterfolder</i> package provides commands to deal with its (fixed) model of file inclusion in a document. It provides commands <code>\</code><code>cfpart</code>, <code>\</code><code>cfchapter</code>, <code>\</code><code>cfsection</code> and <code>\</code><code>cfsubsection</code>, each of which takes directory and file arguments, e.g.: @@ -49,17 +49,17 @@ which command will issue a ‘normal’ command <i>part1/part.tex</i>, remembering that <i>part1/</i> is now the “current folder”. There are also commands of the form <code>\</code><code>cfpartstar</code> (which corresponds to a <code>\</code><code>part*</code> command). -<p>Once you’re “in” a <i>chapterfolder</i>-included document, you +<p/>Once you’re “in” a <i>chapterfolder</i>-included document, you may use <code>\</code><code>cfinput</code> to input something relative to the “current folder”, or you may use <code>\</code><code>input</code>, using <code>\</code><code>cfcurrentfolder</code> to provide a path to the file. (There are also <code>\</code><code>cfcurrentfolderfigure</code> for a <i>figure/</i> subdirectory and <code>\</code><code>cfcurrentfolderlistings</code> for a <i>listings/</i> subdirectory.) -<p>Documentation of <i>chapterfolder</i> is in French, but the +<p/>Documentation of <i>chapterfolder</i> is in French, but the <i>README</i> in the directory is in English. <dl> <dt><tt><i>chapterfolder.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/chapterfolder.zip">macros/latex/contrib/chapterfolder</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/chapterfolder.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/chapterfolder/">browse</a>) <dt><tt><i>import.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/import.sty">macros/latex/contrib/misc/import.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docotherdir">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docotherdir</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docotherdir">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docotherdir</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-docpictex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-docpictex.html index c496f699597..2040e88b3ac 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-docpictex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-docpictex.html @@ -1,18 +1,22 @@ <head> <title>UK TeX FAQ -- question label docpictex</title> </head><body> -<h3>The PiCTeX manual</h3> -<p>PiCTeX is a set of macros by Michael Wichura for drawing diagrams +<h3>The PicTeX manual</h3> +<p/>PicTeX is a set of macros by Michael Wichura for drawing diagrams and pictures. The macros are freely available; however, the -PiCTeX manual itself is not free. +PicTeX manual itself is not free. Unfortunately, TUG is no longer able to supply copies of the manual (as it once did), and it is now available only through Personal TeX Inc, the vendors of PCTeX (<a href="http://www.pctex.com/">http://www.pctex.com/</a>). The manual is <em>not</em> available electronically. +<p/>However, there <em>is</em> a summary of PicTeX commands available on +CTAN, which is a great aide-memoire for those who basically +know the package to start with. <dl> <dt><tt><i>pictex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/pictex.zip">graphics/pictex</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pictex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pictex/">browse</a>) +<dt><tt><i>PiCTeX summary</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/pictex/summary.zip">info/pictex/summary</a> (<a href="ftp://cam.ctan.org/tex-archive/info/pictex/summary.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/pictex/summary/">browse</a>) </dl> -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docpictex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docpictex</a> +<p/> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docpictex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=docpictex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dolldoll.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dolldoll.html index a8a2eef7595..5c1c9bfffad 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dolldoll.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dolldoll.html @@ -2,20 +2,20 @@ <title>UK TeX FAQ -- question label dolldoll</title> </head><body> <h3>Why use <code>\</code><code>[</code> ...<code>\</code><code>]</code> in place of <code>$$</code> ...<code>$$</code>?</h3> -<p>LaTeX defines inline- and display-maths commands, apparently +<p/>LaTeX defines inline- and display-maths commands, apparently analagous to those that derive from the TeX primitive maths sequences bracketing maths commands with single dollar signs (or pairs of dollar signs). -<p>As it turns out, LaTeX’s inline maths grouping, +<p/>As it turns out, LaTeX’s inline maths grouping, <code>\</code><code>(</code><code> ... </code><code>\</code><code>)</code>, has precisely the same effect as the TeX primitive version <code>$ ... $</code>. (Except that the LaTeX version checks to ensure you don’t put <code>\</code><code>(</code> and <code>\</code><code>)</code> the wrong way round.) -<p>In this circumstance, one often finds LaTeX users, who have some +<p/>In this circumstance, one often finds LaTeX users, who have some experience of using Plain TeX, merely assuming that LaTeX’s display maths grouping <code>\</code><code>[</code><code> ... </code><code>\</code><code>]</code> may be replaced by the TeX primitive display maths <code>$$ ... $$</code>. -<p>Unfortunately, they are wrong: if LaTeX code is going to patch display +<p/>Unfortunately, they are wrong: if LaTeX code is going to patch display maths, it can only do so by patching <code>\</code><code>[</code> and <code>\</code><code>]</code>. The most obvious way this turns up, is that the class option <code>fleqn</code> simply does not work for equations coded using @@ -25,9 +25,9 @@ alone, or using package <i>amsmath</i>. Also, the <code>\</code><code>[</code> cases; that code is not available in <code>$$ ... $$</code>, so if you use the non-standard version, you may occasionally observe inconsistent vertical spacing . -<p>There are more subtle effects (especially with package +<p/>There are more subtle effects (especially with package <i>amsmath</i>), and the simple rule is <code>\</code><code>[</code><code> ... </code><code>\</code><code>]</code> whenever unadorned displayed maths is needed in LaTeX. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dolldoll">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dolldoll</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dolldoll">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dolldoll</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dpfloat.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dpfloat.html index 8693abdb01c..56c65cbb3c2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dpfloat.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dpfloat.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label dpfloat</title> </head><body> <h3>Facing floats on 2-page spread</h3> -<p>If a pair of floats are to be forced to form a 2-page spread (in a +<p/>If a pair of floats are to be forced to form a 2-page spread (in a book, or whatever), the first must lie on the left side of the spread, on an even-numbered page. The <i>dpfloat</i> package provides for this: the construction to use is: @@ -22,10 +22,10 @@ this: the construction to use is: </blockquote><p> The construction has no effect unless the standard class option <code>twoside</code> is in effect. -<p>Full documentation of the package (such as it is) is to be found in +<p/>Full documentation of the package (such as it is) is to be found in <i>README.dpfloat</i> <dl> <dt><tt><i>dpfloat.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/dpfloat.zip">macros/latex/contrib/dpfloat</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/dpfloat.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/dpfloat/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dpfloat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dpfloat</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dpfloat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dpfloat</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawFeyn.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawFeyn.html index 23745790a6d..08a3f88af38 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawFeyn.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawFeyn.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label drawFeyn</title> </head><body> <h3>Drawing Feynman diagrams in LaTeX</h3> -<p>Michael Levine’s <i>feynman</i> bundle for drawing the diagrams in +<p/>Michael Levine’s <i>feynman</i> bundle for drawing the diagrams in LaTeX 2.09 is still available. -<p>Thorsten Ohl’s <i>feynmf</i> is designed for use with current +<p/>Thorsten Ohl’s <i>feynmf</i> is designed for use with current LaTeX, and works in combination with Metafont (or, in its <i>feynmp</i> incarnation, with MetaPost). The <i>feynmf</i> or @@ -14,11 +14,11 @@ font (or PostScript file) for use in a subsequent LaTeX run. For new users, who have access to MetaPost, the PostScript version is probably the better route, for document portability and other reasons. -<p>Jos Vermaseren’s <i>axodraw</i> is mentioned as an alternative in +<p/>Jos Vermaseren’s <i>axodraw</i> is mentioned as an alternative in the documentation of <i>feynmf</i>, but it is written entirely in terms of <i>dvips</i> <code>\</code><code>special</code> commands, and is thus rather imperfectly portable. -<p>An alternative approach is implemented by Norman Gray’s <i>feyn</i> +<p/>An alternative approach is implemented by Norman Gray’s <i>feyn</i> package. Rather than creating complete diagrams as postscript images, <i>feyn</i> provides a font (in a variety of sizes) containing fragments, which you can compose to produce complete diagrams. It @@ -30,5 +30,5 @@ than complicated ones more suitable for display in figures. <dt><tt><i>feynman bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/feynman.zip">macros/latex209/contrib/feynman</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/feynman.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex209/contrib/feynman/">browse</a>) <dt><tt><i>feynmf/feynmp bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/feynmf.zip">macros/latex/contrib/feynmf</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/feynmf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/feynmf/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=drawFeyn">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=drawFeyn</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=drawFeyn">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=drawFeyn</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawing.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawing.html index 216a28841e3..1f4478df3b8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawing.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-drawing.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label drawing</title> </head><body> <h3>Drawing with TeX</h3> -<p>There are many packages to do pictures in (La)TeX itself (rather than +<p/>There are many packages to do pictures in (La)TeX itself (rather than importing graphics created externally), ranging from simple use of LaTeX <code>picture</code> environment, through enhancements like <i>epic</i>, to -sophisticated (but slow) drawing with PiCTeX. Depending on your type +sophisticated (but slow) drawing with PicTeX. Depending on your type of drawing, and setup, here are a few systems you may consider: <ul> <li> <i>pict2e</i>; this was advertised in @@ -56,7 +56,7 @@ of drawing, and setup, here are a few systems you may consider: full power of MetaPost, but a friendlier interface; of course, with MetaPost output, the results can be used equally well in either LaTeX or PDFLaTeX. -<li> You liked PiCTeX but don’t have enough memory or time? Look +<li> You liked PicTeX but don’t have enough memory or time? Look at Eitan Gurari’s <i>dratex</i>, which is as powerful as most other TeX drawing packages, but is an entirely new implementation, which is not as hard on memory, is much more @@ -72,5 +72,5 @@ of drawing, and setup, here are a few systems you may consider: <dt><tt><i>pstricks</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.zip">graphics/pstricks</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pstricks/">browse</a>) <dt><tt><i>tikz.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/graphics/pgf.zip">graphics/pgf</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pgf.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pgf/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=drawing">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=drawing</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=drawing">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=drawing</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-driver.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-driver.html index ebc89d48b51..bb395b8b06a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-driver.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-driver.html @@ -1,16 +1,17 @@ <head> <title>UK TeX FAQ -- question label driver</title> </head><body> -<h3>What is a driver?</h3> -<p>A driver is a program that takes as input a DVI file +<h3>What is a DVI driver?</h3> +<p/>A DVI driver is a program that takes as input a DVI file (<a href="FAQ-dvi.html">DVI files</a>) and (usually) produces a file that can be sent to a typographic -output device, called a printer for short. -<p>A driver will usually be specific to a particular printer, +output device (which we will call a printer, for short), or to another +format. +<p/>A driver will usually be specific to a particular printer, although any PostScript printer ought to be able to print the output from a PostScript driver. -<p>As well as the DVI file, the driver needs font information. +<p/>As well as the DVI file, the driver also needs font information. Font information may be held as bitmaps or as outlines, or simply as a set of pointers into the fonts that the printer itself ‘has’. Each driver will expect the font information in @@ -20,5 +21,5 @@ see <a href="FAQ-pk.html">PK files</a>, <a href="FAQ-tfm.html">TFM files</a>, <a href="FAQ-virtualfonts.html">virtual fonts</a> and <a href="FAQ-usepsfont.html">Using PostScript fonts with TeX</a>. -<p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=driver">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=driver</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=driver">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=driver</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dropping.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dropping.html index fcf35f59c97..32a0256fd41 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dropping.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dropping.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label dropping</title> </head><body> <h3>Big letters at the start of a paragraph</h3> -<p>A common style of typesetting, now seldom seen except in newspapers, +<p/>A common style of typesetting, now seldom seen except in newspapers, is to start a paragraph (in books, usually the first of a chapter) with its first letter set large enough to span several lines. -<p>This style is known as “dropped capitals”, or (in French) +<p/>This style is known as “dropped capitals”, or (in French) «lettrines», and TeX’s primitive facilities for hanging indentation make its (simple) implementation pretty straightforward. -<p>The <i>dropping</i> package does the job simply, but has a curious +<p/>The <i>dropping</i> package does the job simply, but has a curious attitude to the calculation of the size of the font to be used for the big letters. Examples appear in the package documentation, so before you process the <code>.dtx</code>, the package itself must already be installed. @@ -17,7 +17,7 @@ Unfortunately, <i>dropping</i> has an intimate relation to the set of device drivers available in an early version of the LaTeX graphics package, and it cannot be trusted to work with recent offerings like PDFTeX, VTeX or DVIpdfm. -<p>On such occasions, the more recent <i>lettrine</i> package is more +<p/>On such occasions, the more recent <i>lettrine</i> package is more likely to succeed. It has a well-constructed array of options, and the examples (a pretty impressive set) come as a separate file in the distribution (also available in PostScript, so that they can be viewed @@ -26,5 +26,5 @@ without installing the package itself). <dt><tt><i>dropping</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/dropping.zip">macros/latex/contrib/dropping</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/dropping.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/dropping/">browse</a>) <dt><tt><i>lettrine</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lettrine.zip">macros/latex/contrib/lettrine</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lettrine.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/lettrine/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dropping">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dropping</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dropping">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dropping</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html index 35bea68fcd6..e22c17504e6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html @@ -2,43 +2,42 @@ <title>UK TeX FAQ -- question label dtx</title> </head><body> <h3>Documented LaTeX sources (<code>.dtx</code> files)</h3> -<p>LaTeX2e, and most contributed macro packages, are now written in a +<p/>LaTeX2e, and most contributed macro packages, are now written in a <a href="FAQ-lit.html">literate programming style</a>, with source and documentation in the same file. This format, known as ‘doc’, in fact originated before the days of the LaTeX project as one of the “Mainz” series of -packages. The documented sources conventionally have the suffix -<code>.dtx</code>, and should normally be stripped of documentation -before use with LaTeX. Alternatively you can run LaTeX on a +packages. A documented source file conventionally has the suffix +<code>.dtx</code>, and will normally be ‘stripped’ before use with +LaTeX; an installation file (<code>.ins</code>) is normally provided, +to automate this process of removing comments for speed of loading. +To read the comments, you can run LaTeX on the <code>.dtx</code> file to produce a nicely formatted version of the -documented code. An installation script (with suffix -<code>.ins</code>) is usually provided, which needs the standard LaTeX2e -<i>docstrip</i> package (among other things, the installation -process strips all the comments that make up the documentation for -speed when loading the file into a running LaTeX system). Several -packages can be included in one <code>.dtx</code> file, with conditional -sections, and there facilities for indices of macros etc. Anyone can -write <code>.dtx</code> files; the format is explained in -<a href="FAQ-books.html">The LaTeX Companion</a>, and a tutorial is -available from CTAN (which comes with skeleton <code>.dtx</code> and +documented code. Several +packages can be included in one <code>.dtx</code> file (they’re sorted +out by the <code>.ins</code> file), with conditional +sections, and there are facilities for indexes of macros, etc. +<p/>Anyone can write <code>.dtx</code> files; the format is explained in +<a href="FAQ-books.html">The LaTeX Companion</a>, and a tutorial is available +from CTAN (which comes with skeleton <code>.dtx</code> and <code>.ins</code> files). -<p>Composition of <code>.dtx</code> files is supported in <i>emacs</i> by +<p/>Composition of <code>.dtx</code> files is supported in <i>emacs</i> by Matt Swift’s <i>swiftex</i> system: it provides a <code>doc-tex</code> mode which treats <code>.dtx</code> files rather better than <a href="FAQ-editors.html">AUC-TeX</a> manages. -<p>Another useful way of generating <code>.dtx</code> files is to write the +<p/>Another useful way of generating <code>.dtx</code> files is to write the documentation and the code separately, and then to combine them using the <i>makedtx</i> system. This technique has particular value in that the documentation file can be used separately to generate HTML output; it is often quite difficult to make <a href="FAQ-LaTeX2HTML.html">LaTeX to HTML conversion</a> tools deal with <code>.dtx</code> files, since they use an unusual class file. -<p><code>.dtx</code> files are not used by LaTeX after they have been +<p/>The <code>.dtx</code> files are not used by LaTeX after they have been processed to produce <code>.sty</code> or <code>.cls</code> (or whatever) files. They need not be kept with the working system; however, for many packages the <code>.dtx</code> file is the primary source of documentation, so you may want to keep <code>.dtx</code> files elsewhere. -<p>An interesting sideline to the story of <code>.dtx</code> files is the +<p/>An interesting sideline to the story of <code>.dtx</code> files is the <i>docmfp</i> package, which extends the model of the <i>doc</i> package to <a href="FAQ-MF.html">Metafont</a> and <a href="FAQ-MP.html">MetaPost</a>, @@ -52,5 +51,5 @@ Metafont and MetaPost together with related LaTeX code. <dt><tt><i>makedtx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/makedtx.zip">support/makedtx</a> (<a href="ftp://cam.ctan.org/tex-archive/support/makedtx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/makedtx/">browse</a>) <dt><tt><i>swiftex.el</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/emacs-modes/swiftex.zip">support/emacs-modes/swiftex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/emacs-modes/swiftex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/emacs-modes/swiftex/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dtx">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dtx</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dtx">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dtx</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi-bmp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi-bmp.html index b552f590db1..11ea878604c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi-bmp.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi-bmp.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label dvi-bmp</title> </head><body> <h3>Generating bitmaps from DVI</h3> -<p>In the last analysis, any DVI driver or previewer is generating +<p/>In the last analysis, any DVI driver or previewer is generating bitmaps: bitmaps for placing tiny dots on paper via a laser- or inkjet-printer, or bitmaps for filling some portion of your screen. However, it’s usually difficult to extract any of those bitmaps any way other than by screen capture, and the resolution of <em>that</em> is commonly lamentable. -<p>Why would one want separate bitmaps? Most often, the requirement is for +<p/>Why would one want separate bitmaps? Most often, the requirement is for something that can be included in HTML generated from (La)TeX source — not everything that you can write in (La)TeX can be translated to HTML (at least, portable HTML that may be @@ -21,20 +21,19 @@ sample bitmaps, and generation for insertion into some other application’s display — to insert equations into Microsoft PowerPoint, or to support the enhanced-<i>emacs</i> setup called <a href="FAQ-WYGexpts.html"><i>preview</i>-<i>latex</i></a>. -<p>In the past, the commonest way of generating bitmaps was to generate a +<p/>In the past, the commonest way of generating bitmaps was to generate a PostScript file of the DVI and then use <i>ghostscript</i> to produce the required bitmap format (possibly by way of PNM format or something similar). This is an undesirable procedure (it is very slow, and requires two or three steps) but it has served for a long time. -<p>(La)TeX users may now take advantage of two bitmap ‘drivers’. The -longest-established, <i>dvi2bitmap</i>, will generate XBM and +<p/>(La)TeX users may now take advantage of two bitmap ‘drivers’. The +longer-established, <i>dvi2bitmap</i>, will generate XBM and XPM formats, the long-deprecated GIF format (which is -now obsolescent, but is -finally, in Summer 2003, to be relieved of the patent protection of -the LZW compression it uses), and also +now obsolescent, but has finally been relieved of the patent +protection of the LZW compression it uses), and also the modern (ISO-standardised) PNG format. -<p>Dvipng started out as a PNG renderer; from version 1.2 it can also +<p/>Dvipng started out as a PNG renderer; from version 1.2 it can also render to the GIF format. It is designed for speed, in environments that generate large numbers of PNG files: the <i>README</i> mentions <i>preview</i>-<i>latex</i>, <i>LyX</i>, and a few @@ -45,6 +44,6 @@ for speed. <dt><tt><i>dvi2bitmap</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvi2bitmap.zip">dviware/dvi2bitmap</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvi2bitmap.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvi2bitmap/">browse</a>) <dt><tt><i>dvipng</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvipng.zip">dviware/dvipng</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvipng.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipng/">browse</a>) </dl> -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvi-bmp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvi-bmp</a> +<p/> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvi-bmp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvi-bmp</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html index 90edef45b5b..f07f1ccd244 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi.html @@ -2,26 +2,27 @@ <title>UK TeX FAQ -- question label dvi</title> </head><body> <h3>What is a DVI file?</h3> -<p>A DVI file (that is, a file with the type or extension <code>.dvi</code>) is -TeX’s main output file, using TeX in its broadest sense to -include LaTeX, etc. ‘DVI’ is supposed to be an acronym for -DeVice-Independent, meaning that the file can be -printed on almost any -kind of typographic output device. The DVI file is designed to be +<p/>A DVI file (that is, a file with the type or extension +<code>.dvi</code>) is TeX’s main output file, using TeX in its +broadest sense to include LaTeX, etc. ‘DVI’ is supposed to +be an acronym for DeVice-Independent, meaning +that the file can be printed on most +kinds of typographic output device. The DVI file is designed to be read by a driver (<a href="FAQ-driver.html">DVI drivers</a>) to produce further output designed specifically for a particular printer (e.g., a LaserJet) or to be used as input to a previewer for display on a computer screen. DVI files use TeX’s internal coding; a TeX input file should produce the same DVI file regardless of which implementation of TeX is used to produce it. -<p>A DVI file contains all the information that is needed for printing +<p/>A DVI file contains all the information that is needed for printing or previewing except for the actual bitmaps or outlines of fonts, and possibly material to be introduced by means of <a href="FAQ-specials.html"><code>\</code><code>special</code> commands</a>. -<p>The canonical reference for the structure of a DVI file is the -source of <i>dvitype</i>. +<p/>The canonical reference for the structure of a DVI file is the +source of Knuth’s program <i>dvitype</i> (whose original purpose, +as its name implies, was to view the content of a DVI file). <dl> <dt><tt><i>dvitype</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/knuth/texware/dvitype.web">systems/knuth/texware/dvitype.web</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvi">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvi</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvi">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvi</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipdfmgraphics.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipdfmgraphics.html index 0b2888602f3..e0e0c376c90 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipdfmgraphics.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipdfmgraphics.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label dvipdfmgraphics</title> </head><body> <h3>Imported graphics in <i>dvipdfm</i></h3> -<p><i>Dvipdfm</i> translates direct from DVI to PDF +<p/><i>Dvipdfm</i> translates direct from DVI to PDF (all other available routes produce PostScript output using <i>dvips</i> and then convert that to PDF with <i>ghostscript</i> or <i>Acrobat</i> <i>Distiller</i>). -<p><i>Dvipdfm</i> is a particularly flexible application. It will +<p/><i>Dvipdfm</i> is a particularly flexible application. It will permit the inclusion of bitmap and PDF graphics, as does <a href="FAQ-pdftexgraphics.html">PDFTeX</a>, but is also capable of employing <i>ghostscript</i> “on the fly” so as to be able to permit the @@ -14,7 +14,7 @@ inclusion of encapsulated PostScript (<code>.eps</code>) files by translating them to PDF. In this way, <i>dvipdfm</i> combines the good qualities of <i>dvips</i> and of PDFTeX as a means of processing illustrated documents. -<p>Unfortunately, “ordinary” LaTeX can’t deduce the bounding box of +<p/>Unfortunately, “ordinary” LaTeX can’t deduce the bounding box of a binary bitmap file (such as JPEG or PNG), so you have to specify the bounding box. This may be done explicitly, in the document: @@ -51,7 +51,7 @@ which makes the operation feel as simple as does including <i>dvips</i>; the <i>graphicx</i> package knows to look for a <code>.bb</code> file if no bounding box is provided in the <code>\</code><code>includegraphics</code> command. -<p>The one place where usage isn’t quite so simple is the need to quote +<p/>The one place where usage isn’t quite so simple is the need to quote <i>dvipdfm</i> explicitly, as an option when loading the <i>graphicx</i> package: if you are using <i>dvips</i>, you don’t ordinarily need to specify the fact, since the default graphics @@ -61,5 +61,5 @@ configuration file (of most distributions) “guesses” the <dt><tt><i>dvipdfm</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.zip">dviware/dvipdfm</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfm/">browse</a>) <dt><tt><i>ebb</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.zip">dviware/dvipdfm</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfm/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvipdfmgraphics">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvipdfmgraphics</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvipdfmgraphics">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvipdfmgraphics</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips-pdf.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips-pdf.html index 8639e3fab52..9da7380561b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips-pdf.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips-pdf.html @@ -3,12 +3,12 @@ </head><body> <h3>Quality of PDF from PostScript</h3> <!-- blurry fuzzy crippled --> -<p>Any reasonable PostScript, including any output of <i>dvips</i>, may be +<p/>Any reasonable PostScript, including any output of <i>dvips</i>, may be converted to PDF, using (for example) a sufficiently recent version of <i>ghostscript</i>, Frank Siegert’s (shareware) <a href="http://www.pstill.com/"><i>PStill</a></i>, or Adobe’s (commercial) <i>Distiller</i>. -<p>But, although the job may (almost always) be done, the results are +<p/>But, although the job may (almost always) be done, the results are often not acceptable: the most frequent problem is bad presentation of the character glyphs that make up the document. The following answers offer solutions to this (and other) problems of bad presentation. @@ -36,11 +36,11 @@ address. This is of course good news: however, it will inevitably be a long time before every user in the world has this (or later) versions, so the remedies below are going to remain for some time to come. -<p>The problems are also discussed, with practical examples, in Mike +<p/>The problems are also discussed, with practical examples, in Mike Shell’s <i>testflow</i> package, which these FAQs recommend as a “<a href="FAQ-tutbitslatex.html">specialised tutorial</a>. <dl> <dt><tt><i>testflow</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/IEEEtran/testflow/">macros/latex/contrib/IEEEtran/testflow/</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips-pdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips-pdf</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips-pdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips-pdf</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips.html index d0a45303513..d433daecc2a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips.html @@ -2,20 +2,20 @@ <title>UK TeX FAQ -- question label dvips</title> </head><body> <h3>DVI to PostScript conversion programs</h3> -<p>The best public domain DVI to PostScript conversion program, which +<p/>The best public domain DVI to PostScript conversion program, which runs under many operating systems, is Tom Rokicki’s <i>dvips</i>. <i>dvips</i> is written in C and ports easily. All current development is in the context of Karl Berry’s <i>kpathsea</i> -library, and sources are available from the TeX live repository, +library, and sources are available from the TeX-live repository, and versions are available in all TeX distributions that recognise the use of PostScript. -<p>An VMS versions is available as part of the CTAN +<p/>An VMS versions is available as part of the CTAN distribution of TeX for VMS. -<p>A precompiled version to work with emTeX is available on CTAN. +<p/>A precompiled version to work with emTeX is available on CTAN. <dl> <dt><tt><i>MSDOS and OS/2</i></tt><dd> <a href="ftp://cam.ctan.org/tex-archive/systems/msdos/dviware/dvips.zip">systems/msdos/dviware/dvips</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/dviware/dvips.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/dviware/dvips/">browse</a>) <dt><tt><i>VMS distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/OpenVMS/TEX97_CTAN.ZIP">systems/OpenVMS/TEX97_CTAN.ZIP</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvips</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipsgraphics.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipsgraphics.html index d0295f7464f..3c0bc61364e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipsgraphics.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvipsgraphics.html @@ -2,29 +2,29 @@ <title>UK TeX FAQ -- question label dvipsgraphics</title> </head><body> <h3>Imported graphics in <i>dvips</i></h3> -<p><i>Dvips</i>, as originally conceived, can only import a single +<p/><i>Dvips</i>, as originally conceived, can only import a single graphics format: <a href="FAQ-eps.html">encapsulated PostScript</a> (<code>.eps</code> files). <i>Dvips</i> also deals with the slightly eccentric EPS that is created by <a href="FAQ-MP.html">MetaPost</a>. -<p>Apart from the fact that a depressing proportion of drawing +<p/>Apart from the fact that a depressing proportion of drawing applications produce corrupt EPS when asked for such output, this is pretty satisfactory for vector graphics work. -<p>To include bitmap graphics, you need some means of converting them to +<p/>To include bitmap graphics, you need some means of converting them to PostScript; in fact many standard image manipulators (such as <i>ImageMagick</i>’s <i>convert</i>) make a good job of creating EPS files (but be sure to ask for output at PostScript level 2 or higher). (<i>Unix</i> users should beware of <i>xv</i>’s claims: it has a tendency to downsample your bitmap to your screen resolution.) -<p>Special purpose applications <i>jpeg2ps</i> (which converts +<p/>Special purpose applications <i>jpeg2ps</i> (which converts JPEG files using PostScript level 2 functionality) and <i>bmeps</i> (which converts both JPEG and PNG files), and <i>a2ping</i>/<i>sam2p</i> (which convert a bewildering array of bitmap formats to EPS or PDF files; <i>sam2p</i> is one of the engines that <i>a2ping</i> uses) are also considered “good bets”. -<p><i>Bmeps</i> comes with patches to produce your own version of +<p/><i>Bmeps</i> comes with patches to produce your own version of <i>dvips</i> that can cope with JPEG and PNG direct, using <i>bmeps</i>’s conversion library. <i>Dvips</i>, as distributed by MiKTeX, comes with those patches built-in. @@ -34,5 +34,5 @@ distributed by MiKTeX, comes with those patches built-in. <dt><tt><i>jpeg2ps</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/support/jpeg2ps.zip">nonfree/support/jpeg2ps</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/support/jpeg2ps.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/jpeg2ps/">browse</a>) <dt><tt><i>sam2p</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/sam2p.zip">graphics/sam2p</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/sam2p.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/sam2p/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvipsgraphics">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvipsgraphics</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvipsgraphics">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=dvipsgraphics</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-edef.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-edef.html index 89679591c1c..79f1400d62d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-edef.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-edef.html @@ -2,19 +2,19 @@ <title>UK TeX FAQ -- question label edef</title> </head><body> <h3><code>\</code><code>edef</code> does not work with <code>\</code><code>protect</code></h3> -<p>Robust LaTeX commands are either “naturally robust” — meaning that +<p/>Robust LaTeX commands are either “naturally robust” — meaning that they never need <code>\</code><code>protect</code>, or “self-protected” — meaning that they have <code>\</code><code>protect</code> built in to their definition in some way. Self-protected commands are robust only in a context where the <code>\</code><code>protect</code> mechanism is properly handled. The body of an <code>\</code><code>edef</code> definition doesn’t handle <code>\</code><code>protect</code> properly, since <code>\</code><code>edef</code> is a TeX primitive rather than a LaTeX command. -<p>This problem is resolved by a LaTeX internal command +<p/>This problem is resolved by a LaTeX internal command <code>\</code><code>protected@edef</code>, which does the job of <code>\</code><code>edef</code> while keeping the <code>\</code><code>protect</code> mechanism working. There’s a corresponding <code>\</code><code>protected@xdef</code> which does the job of <code>\</code><code>xdef</code>. -<p>Of course, these commands need to be tended carefully, since they’re +<p/>Of course, these commands need to be tended carefully, since they’re internal: see <a href="FAQ-atsigns.html">’@’ in control sequence names</a>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=edef">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=edef</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=edef">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=edef</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-editors.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-editors.html index 167a7302290..18f4c49733f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-editors.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-editors.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label editors</title> </head><body> <h3>TeX-friendly editors and shells</h3> -<p>There are good TeX-writing environments and editors for most +<p/>There are good TeX-writing environments and editors for most operating systems; some are described below, but this is only a personal selection: <dl> @@ -15,7 +15,7 @@ personal selection: lays out markup nicely, lets you call TeX and drivers from within the editor, and everything else like this that you can think of. Complex, but very powerful. -<p> Many who fail to find the versions of <i>emacs</i> attractive, prefer +<p/> Many who consider the versions of <i>emacs</i> spawn of the devil, prefer <a href="http://vim.sourceforge.net"><i>vim</a></i>, a highly configurable editor (also available for Windows and Macintosh systems). Many plugins are available to support the needs of the (La)TeX user, @@ -23,18 +23,18 @@ personal selection: auto-insertion and -completion of common (La)TeX structures, and browsing LaTeX help. The scripts <i>auctex.vim</i> and <i>bibtex.vim</i> seem to be the most common recommendations. -<p> The editor <a href="http://nedit.org/"><i>NEdit</a></i> is also free +<p/> The editor <a href="http://nedit.org/"><i>NEdit</a></i> is also free and programmable, and is available for Unix systems. An AUC-TeX-alike set of extensions for <i>NEdit</i> is available from CTAN. -<p> <i>LaTeX4Jed</i> provides much enhanced LaTeX support for the +<p/> <i>LaTeX4Jed</i> provides much enhanced LaTeX support for the <a href="http://www.jedsoft.org/jed/"><i>jed</a></i> editor. <i>LaTeX4Jed</i> is similar to AUC-TeX: menus, shortcuts, templates, syntax highlighting, document outline, integrated debugging, symbol completion, full integration with external programs, and more. It was designed with both the beginner and the advanced LaTeX user in mind. -<p> The <i>Kile</i> editor that is provided with the KDE +<p/> The <i>Kile</i> editor that is provided with the KDE window manager provides GUI “shell-like” facilities, in a similar way to the widely-praised <i>Winedt</i> (see below); details (and downloads) are available from the project’s @@ -45,15 +45,15 @@ personal selection: <dt>MSDOS<dd> TeXshell is a simple, easily-customisable environment, which can be used with the editor of your choice. -<p> You can also use GNU <i>emacs</i> and AUC-TeX +<p/> You can also use GNU <i>emacs</i> and AUC-TeX under MSDOS. <dt>Windows ’9x, NT, etc.<dd><i>TeXnicCenter</i> is a (free) TeX-oriented development system, uniting a powerful platform for executing (La)TeX and friends with a configurable editor. -<p> <i>Winedt</i>, a shareware package, is also highly spoken of. +<p/> <i>Winedt</i>, a shareware package, is also highly spoken of. It too provides a shell for the use of TeX and related programs, as well as a powerful and well-configured editor. -<p> Both <i>emacs</i> and <i>vim</i> are available in versions +<p/> Both <i>emacs</i> and <i>vim</i> are available in versions for Windows systems. <dt>OS/2<dd> <i>epmtex</i> offers an OS/2-specific shell. <dt>Macintosh<dd> The commercial Textures provides an excellent integrated @@ -61,24 +61,27 @@ personal selection: editor) is the shareware <i>Alpha</i> which is extensible enough to let you perform almost any TeX-related job. It works well with OzTeX. -<p> For MacOS X users, the tool of choice appears to be +<p/> For MacOS X users, the tool of choice appears to be <a href="http://www.uoregon.edu/~koch/texshop/texshop.html">TeXShop</a>, which combines an editor and a shell with a coherent philosophy of dealing - with (La)TeX in the OS X environment. -<p> <i>Vim</i> is available for use on Macintosh systems. + with (La)TeX in the OS X environment. TeXShop is distributed as + part of the MacTeX system, and will therefore be available out of + the box on machines on which MacTeX has been installed. +<p/> <i>Vim</i> is also available for use on Macintosh systems. </dl> Atari, Amiga and NeXT users also have nice environments. LaTeX users looking for <i>make</i>-like -facilities should try <i>latexmk</i>. -<p>While many (La)TeX-oriented editors can support work on BibTeX +facilities should review the answer on +<a href="FAQ-make.html">Makefiles for LaTeX documents</a>. +<p/>While many (La)TeX-oriented editors can support work on BibTeX files, there are many systems that provide specific “database-like” -access to your BibTeX files — -see <a href="FAQ-buildbib.html">“creating a bibliography file”</a>. +access to your BibTeX files — + see “<a href="FAQ-buildbib.html">creating a bibliography file</a>”. + <dl> <dt><tt><i>alpha</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/support/alpha.zip">nonfree/systems/mac/support/alpha</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/systems/mac/support/alpha.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/systems/mac/support/alpha/">browse</a>) <dt><tt><i>auctex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/auctex.zip">support/auctex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/auctex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/auctex/">browse</a>) <dt><tt><i>epmtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/os2/epmtex.zip">systems/os2/epmtex</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/os2/epmtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/os2/epmtex/">browse</a>) -<dt><tt><i>latexmk</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/latexmk.zip">support/latexmk</a> (<a href="ftp://cam.ctan.org/tex-archive/support/latexmk.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/latexmk/">browse</a>) <dt><tt><i>LaTeX4Jed</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/jed.zip">support/jed</a> (<a href="ftp://cam.ctan.org/tex-archive/support/jed.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/jed/">browse</a>) <dt><tt><i>Nedit LaTeX support</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/NEdit-LaTeX-Extensions.zip">support/NEdit-LaTeX-Extensions</a> (<a href="ftp://cam.ctan.org/tex-archive/support/NEdit-LaTeX-Extensions.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/NEdit-LaTeX-Extensions/">browse</a>) <dt><tt><i>TeXnicCenter</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/systems/win32/TeXnicCenter/">systems/win32/TeXnicCenter/</a> @@ -86,5 +89,5 @@ see <a href="FAQ-buildbib.html">“creating a bibliography file”</a>. <dt><tt><i>TeXtelmExtel</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex-contrib/TeXtelmExtel.zip">systems/msdos/emtex-contrib/TeXtelmExtel</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex-contrib/TeXtelmExtel.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/emtex-contrib/TeXtelmExtel/">browse</a>) <dt><tt><i>winedt</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/win32/winedt/winedt32.exe">systems/win32/winedt/winedt32.exe</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=editors">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=editors</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=editors">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=editors</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-empty.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-empty.html index fb132a0f368..0d37b2b6658 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-empty.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-empty.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label empty</title> </head><body> <h3>Detecting that something is empty</h3> -<p>Suppose you need to know that the argument of your command is empty: +<p/>Suppose you need to know that the argument of your command is empty: that is, to distinguish between <code>\</code><code>cmd{}</code> and <code>\</code><code>cmd{blah}</code>. This is pretty simple: <blockquote> @@ -21,10 +21,11 @@ and <code>\</code><code>cmd{blah}</code>. This is pretty simple: The case where you want to ignore an argument that consists of nothing but spaces, rather than something completely empty, is more tricky. It’s solved in the code fragment <i>ifmtarg</i>, which defines -commands <code>\</code><code>@ifmtarg</code> and <code>\</code><code>@ifnotmtarg</code>, which distinguish (in -opposite directions) between a second and third argument. The -package’s code also appears in the LaTeX <i>memoir</i> class. -<p><i>Ifmtarg</i> makes challenging reading; there’s also a discussion of the +commands <code>\</code><code>@ifmtarg</code> and <code>\</code><code>@ifnotmtarg</code>, which examine their +first argument, and select (in opposite directions) their second or +third argument. The package’s code also appears in the LaTeX +<i>memoir</i> class. +<p/><i>Ifmtarg</i> makes challenging reading; there’s also a discussion of the issue in number two of the “around the bend” articles by the late lamented Mike Downes. <dl> @@ -32,5 +33,5 @@ lamented Mike Downes. <dt><tt><i>ifmtarg.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/ifmtarg.sty">macros/latex/contrib/misc/ifmtarg.sty</a> <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=empty">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=empty</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=empty">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=empty</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html index 97e41672260..1a2720a3b15 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label endingroup</title> </head><body> <h3><code>\</code><code>end</code> occurred inside a group</h3> -<p>The actual error we observe is: -<p> +<p/>The actual error we observe is: +<p/> <code>(\end occurred inside a group at level <</code><code><em>n</em></code><code>>)</code> -<p> +<p/> and it tells us that something we started in the document never got finished before we ended the document itself. The things involved (‘groups’) are what TeX uses for restricting the scope of things: @@ -13,14 +13,14 @@ you see them, for example, in the “traditional” font selection commands: <code>{\it stuff\/}</code> — if the closing brace is left off such a construct, the effect of <code>\</code><code>it</code> will last to the end of the document, and you’ll get the diagnostic. -<p>TeX itself doesn’t tell you where your problem is, but you can +<p/>TeX itself doesn’t tell you where your problem is, but you can often spot it by looking at the typeset output in a previewer. Otherwise, you can usually find mismatched braces using an intelligent editor (at least <code>emacs</code> and <i>winedt</i> offer this facility). However, groups are not <em>only</em> created by matching <code>{</code> with <code>}</code>: other grouping commands are discussed elsewhere in these FAQs, and are also a potential source of unclosed group. -<p><code>\</code><code>begin{<<i>environment</i>>}</code> encloses the environment’s body +<p/><code>\</code><code>begin{<<i>environment</i>>}</code> encloses the environment’s body in a group, and establishes its own diagnostic mechanism. If you end the document before closing some other environment, you get the ‘usual’ LaTeX diagnostic @@ -37,7 +37,7 @@ recognises other unclosed <code>\</code><code>begin{blob}</code> commands, and generates an “ended by” error message for each one, rather than producing the “occurred inside a group” message, which is sometimes useful (if you remember to load the package). -<p>In the absence of such information from LaTeX, you need to use +<p/>In the absence of such information from LaTeX, you need to use “traditional” binary search to find the offending group. Separate the preamble from the body of your file, and process each half on its own with the preamble; this tells you which half of the file is at @@ -45,7 +45,7 @@ fault. Divide again and repeat. The process needs to be conducted with care (it’s obviously possible to split a correctly-written group by chopping in the wrong place), but it will usually find the problem fairly quickly. -<p>e-TeX (and e-LaTeX — LaTeX run on e-TeX) gives you +<p/>e-TeX (and e-LaTeX — LaTeX run on e-TeX) gives you further diagnostics after the traditional infuriating TeX one — it actually keeps the information in a similar way to LaTeX: @@ -64,5 +64,5 @@ level). <dl> <dt><tt><i>checkend.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bezos.zip">macros/latex/contrib/bezos</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bezos.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bezos/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=endingroup">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=endingroup</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=endingroup">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=endingroup</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-enlarge.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-enlarge.html index 5773403a956..6b4f7dae543 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-enlarge.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-enlarge.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label enlarge</title> </head><body> <h3>Enlarging TeX</h3> -<p>The TeX error message ‘capacity exceeded’ covers a multitude of +<p/>The TeX error message ‘capacity exceeded’ covers a multitude of problems. What has been exhausted is listed in brackets after the error message itself, as in: <blockquote> @@ -18,12 +18,12 @@ often introduced when files are transferred incorrectly between operating systems, and line-endings are not preserved properly (the tell-tale sign of an extra-long line error is the complaint that the ‘<code>buf_size</code>’ has overflowed). -<p>If you really need to extend your TeX’s capacity, the proper method +<p/>If you really need to extend your TeX’s capacity, the proper method depends on your installation. There is no need (with modern TeX implementations) to change the defaults in Knuth’s WEB source; but if you do need to do so, use a change file to modify the values set in module 11, recompile your TeX and regenerate all format files. -<p>Modern implementations allow the sizes of the various bits of TeX’s +<p/>Modern implementations allow the sizes of the various bits of TeX’s memory to be changed semi-dynamically. Some (such as emTeX) allow the memory parameters to be changed in command-line switches when TeX is started; most frequently, a configuration file is read which @@ -32,5 +32,5 @@ this file is called <i>texmf.cnf</i>: see the documentation that comes with the distribution for other implementations. Almost invariably, after such a change, the format files need to be regenerated after changing the memory parameters. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enlarge">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enlarge</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enlarge">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enlarge</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-entercompmode.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-entercompmode.html new file mode 100644 index 00000000000..edf4b689a28 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-entercompmode.html @@ -0,0 +1,64 @@ +<head> +<title>UK TeX FAQ -- question label entercompmode</title> +</head><body> +<h3>Entering compatibility mode</h3> +<p/>You run your LaTeX job, and it starts by saying +<blockquote> +<pre> +Entering LaTeX 2.09 COMPATIBILITY MODE +</pre> +</blockquote><p> +followed by lines of asterisks and <code>!!WARNING!!</code>. +<p/>This means that the document is not written in “current” LaTeX +syntax, and that there is no guarantee that all parts of the document +will be formatted correctly. +<p/>If the document is someone else’s, and you want no more than a copy to +read, ignore the error. The document may fail elsewhere, but as often +as not it will provide a <code>.dvi</code> or <code>.pdf</code> that’s +adequate for most purposes. +<p/>If it’s a new document you have just started working on, you have been +misled by someone. You have written something like: +<blockquote> + <code>\</code><code>documentstyle{article}</code> +</blockquote><p> +or, more generally: +<blockquote> + <code>\</code><code>documentstyle[</code><em>options</em><code>]{</code><em>class</em><code>}</code> +</blockquote><p> +These forms are (as the warning says) LaTeX 2.09 syntax, and to get rid +of the warning, you must change the command. +<p/>The simple form is easy to deal with: +<blockquote> + <code>\</code><code>documentstyle{article}</code> +</blockquote><p> +should become: +<blockquote> + <code>\</code><code>documentclass{article}</code> +</blockquote><p> +The complex form is more difficult, since LaTeX 2.09 “options” +conflate two sorts of things — options for the class (such as +<code>11pt</code>, <code>fleqn</code>), and packages to be loaded. +So: +<blockquote> + <code>\</code><code>documentstyle[11pt,verbatim]{article}</code> +</blockquote><p> +should become: +<blockquote> + <code>\</code><code>documentclass[11pt]{article}</code><br> + <code>\</code><code>usepackage{verbatim}</code> +</blockquote><p> +because <code>11pt</code> happens to be a class option, while +<i>verbatim</i> is a package. +<p/>There’s no simple way to work out what are class options under +LaTeX 2.09; for <i>article</i>, the list includes <code>10pt</code>, +<code>11pt</code>, <code>12pt</code>, <code>draft</code>, +<code>fleqn</code>, <code>leqno</code>, <code>twocolumn</code> and +<code>twoside</code> — anything else must be a package. +<p/>Your document may well “just work” after changes like those above; +if not, you should think through what you’re trying to do, and consult +documentation on how to do it — there are lots of +<a href="FAQ-tutorialstar.html">free tutorials</a> to help you on your way, if you +don’t have access to a LaTeX manual of any sort. +<p/> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=entercompmode">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=entercompmode</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-enumerate.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-enumerate.html index 943ad360e99..0804dc1c7ea 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-enumerate.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-enumerate.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label enumerate</title> </head><body> <h3>Fancy enumeration lists</h3> -<p>The <i>enumerate</i> package allows you to control the display of +<p/>The <i>enumerate</i> package allows you to control the display of the enumeration counter. The package adds an optional parameter to the <code>enumerate</code> environment, which is used to specify the layout of the labels. The layout parameter contains an enumeration @@ -30,10 +30,10 @@ starts a list whose labels run (a), (b), (c), ...; while </pre> </blockquote><p> starts a list whose labels run I/, II/, III/, ... -<p>The <i>paralist</i> package, whose primary purpose is +<p/>The <i>paralist</i> package, whose primary purpose is <a href="FAQ-complist.html">compaction of lists</a>, provides the same facilities for its <code>enumerate</code>-like environments. -<p>If you need non-stereotyped designs, the <i>enumitem</i> package +<p/>If you need non-stereotyped designs, the <i>enumitem</i> package gives you most of the flexibility you might want to design your own. The silly roman example above could be achieved by: <blockquote> @@ -60,7 +60,7 @@ references to list item labels: </blockquote><p> to make references to the list items format appear as (i), (ii), (iii), etc. -<p>The <i>memoir</i> class includes functions that match those in the +<p/>The <i>memoir</i> class includes functions that match those in the <i>enumerate</i> package, and has similar functionality for <code>itemize</code> lists. @@ -85,5 +85,5 @@ to make references to the list items format appear as (i), (ii), <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>paralist.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/paralist.zip">macros/latex/contrib/paralist</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/paralist.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/paralist/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enumerate">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enumerate</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enumerate">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=enumerate</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-epigraph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-epigraph.html index 6c9d5a3103e..30224225c79 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-epigraph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-epigraph.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label epigraph</title> </head><body> <h3>Typesetting epigraphs</h3> -<p>Epigraphs are those neat quotations that authors put at the start of +<p/>Epigraphs are those neat quotations that authors put at the start of chapters (or even at the end of chapters: Knuth puts things at the ends of chapters of the TeXbook). -<p>Typesetting them is a bit of a fiddle, but not impossible to do for +<p/>Typesetting them is a bit of a fiddle, but not impossible to do for yourself. Fortunately, there are two packages that do the job, to some extent; there are also facilities in the two “big” classes (<i>memoir</i> and <i>koma-script</i>. -<p>The <i>epigraph</i> package defines an <code>\</code><code>epigraph</code> command, for +<p/>The <i>epigraph</i> package defines an <code>\</code><code>epigraph</code> command, for creating a single epigraph (as at the top of a chapter): <blockquote> @@ -48,17 +48,17 @@ The <<i>distance</i>> says how far above the chapter heading the epigraph is to go; it’s expressed in terms of the <code>\</code><code>unitlength</code> that’s used in the <code>picture</code> environment; the package’s author recommends <code>70pt</code>. -<p>The package also offers various tricks for adjusting the layout of +<p/>The package also offers various tricks for adjusting the layout of chapter header (necessary if you’ve found a hugely long quotation for an <code>\</code><code>epigraphhead</code>), for patching the bibliography, for patching <code>\</code><code>part</code> pages, and so on. (Some of these suggested patches lead you through writing your own package...) -<p>The <i>quotchap</i> package redefines chapter headings (in a +<p/>The <i>quotchap</i> package redefines chapter headings (in a moderately striking way), and provides an environment <code>savequotes</code> in which you can provide one (or more) quotations to use as epigraphs. The facilities seem not as flexible as those of <i>epigraph</i>, but it’s probably easier to use. -<p>The <i>memoir</i> class offers all the facilities of the +<p/>The <i>memoir</i> class offers all the facilities of the <i>epigraph</i> package. The <i>Koma-script</i> classes have commands <code>\</code><code>setchapterpreamble</code> and <code>\</code><code>dictum</code> to provide these facilities. @@ -68,5 +68,5 @@ facilities. <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>quotchap.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/quotchap.zip">macros/latex/contrib/quotchap</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/quotchap.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/quotchap/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=epigraph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=epigraph</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=epigraph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=epigraph</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eplain.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eplain.html index e94d8d8dace..de3f766ac42 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eplain.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eplain.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label eplain</title> </head><body> <h3>What is Eplain?</h3> -<p>The <a href="http://tug.org/eplain">Eplain</a> +<p/>The <a href="http://tug.org/eplain">Eplain</a> macro package expands on and extends the definitions in Plain TeX. Eplain is not intended to provide “generic typesetting capabilities”, as do LaTeX or <a href="FAQ-texinfo.html">Texinfo</a>. Instead, it defines macro tools that should be useful whatever commands you choose to use when you prepare your manuscript. -<p>For example, Eplain does not have a command <code>\</code><code>section</code>, +<p/>For example, Eplain does not have a command <code>\</code><code>section</code>, which would format section headings in an “appropriate” way, as LaTeX’s <code>\</code><code>section</code> does. The philosophy of Eplain is that some people will always need or want to go beyond the macro designer’s @@ -16,18 +16,18 @@ idea of “appropriate”. Such canned macros are fine — as long are willing to accept the resulting output. If you don’t like the results, or if you are trying to match a different format, you are out of luck. -<p>On the other hand, almost everyone would like capabilities such as +<p/>On the other hand, almost everyone would like capabilities such as cross-referencing by labels, so that you don’t have to put actual page numbers in the manuscript. The authors of Eplain are not aware of any generally available macro packages that do not force their typographic style on an author, and yet provide such capabilities. -<p>Another useful feature of Eplain is the ability to create PDF files +<p/>Another useful feature of Eplain is the ability to create PDF files with hyperlinks. The cross-referencing macros can implicitly generate hyperlinks for the cross-references, but you can also create explicit hyperlinks, both internal (pointing to a destination within the current document) and external (pointing to another local document or a URL). -<p>Several LaTeX packages provide capabilities which Plain TeX +<p/>Several LaTeX packages provide capabilities which Plain TeX users are lacking, most notably text colouring and rotation provided by the <i>graphics</i> bundle (packages <i>color</i> and <i>graphics</i>). Although the <i>graphics</i> bundle provides @@ -39,12 +39,12 @@ to the packages just as they are in LaTeX. The following packages are known to work with Eplain: <i>graphics</i>, <i>graphicx</i>, <i>color</i>, <i>autopict</i> (LaTeX picture environment), <i>psfrag</i>, and <i>url</i>. -<p><a href="http://tug.org/docs/html/eplain">Eplain documentation</a> is +<p/><a href="http://tug.org/docs/html/eplain">Eplain documentation</a> is available online, and there’s also a mailing list — sign up, or browse the list archives, via <a href="http://tug.org/mailman/listinfo/tex-eplain">http://tug.org/mailman/listinfo/tex-eplain</a> <dl> <dt><tt><i>Eplain distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/eplain.zip">macros/eplain</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/eplain.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/eplain/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eplain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eplain</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eplain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eplain</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eps.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eps.html index 7e44cafe153..ae5d45c197a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eps.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eps.html @@ -2,15 +2,16 @@ <title>UK TeX FAQ -- question label eps</title> </head><body> <h3>What is “Encapsulated PostScript” (“EPS”)</h3> -<p>PostScript has over the years become a <em>lingua franca</em> of -powerful printers; since PostScript is also a powerful graphical -programming language, it is commonly used as an output medium for -drawing (and other) packages. -<p>However, since PostScript <em>is</em> such a powerful language, some +<p/>PostScript has been for many years a <em>lingua franca</em> of powerful +printers (modern high-quality printers now tend to require some +constrained form of Adobe Acrobat, instead); since PostScript is also a +powerful graphical programming language, it is commonly used as an +output medium for drawing (and other) packages. +<p/>However, since PostScript <em>is</em> such a powerful language, some rules need to be imposed, so that the output drawing may be included in a document as a figure without “leaking” (and thereby destroying the surrounding document, or failing to draw at all). -<p>Appendix H of the PostScript Language Reference Manual (second +<p/>Appendix H of the PostScript Language Reference Manual (second and subsequent editions), specifies a set of rules for PostScript to be used as figures in this way. The important features are: <ul> @@ -33,5 +34,5 @@ including PostScript are structured to use Encapsulated PostScript; which of course leads to much hilarity as exasperated (La)TeX users struggle to cope with the output of drawing software whose authors don’t know the rules. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eps">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eps</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eps">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eps</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-epsf.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-epsf.html index aa69bc030ee..10eab64cd9b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-epsf.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-epsf.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label epsf</title> </head><body> <h3><code>epsf</code> gives up after a bit</h3> -<p>Some copies of the documentation of <i>epsf.tex</i> seem to suggest +<p/>Some copies of the documentation of <i>epsf.tex</i> seem to suggest that the command <pre> \input epsf @@ -16,7 +16,7 @@ after a while; this is because each time <i>epsf.tex</i> is loaded, it allocates itself a <em>new</em> file-reading handle to check the figure for its bounding box, and there just aren’t enough of these things (see <a href="FAQ-noroom.html">no room for a new thing</a>). -<p>The solution is simple — this is in fact an example of misuse of +<p/>The solution is simple — this is in fact an example of misuse of macros; one only need read <i>epsf.tex</i> once, so change <pre> ... @@ -33,5 +33,5 @@ macros; one only need read <i>epsf.tex</i> once, so change somewhere near the start of your document, and then decorate your <code>\</code><code>epsffile</code> statements with no more than adjustments of <code>\</code><code>epsfxsize</code> and so on. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=epsf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=epsf</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=epsf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=epsf</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eqnarray.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eqnarray.html index ad6d7287488..8e023a4e0e0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eqnarray.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-eqnarray.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label eqnarray</title> </head><body> <h3>Why not use <code>eqnarray</code>?</h3> -<p>The environment <code>eqnarray</code> is attractive for the +<p/>The environment <code>eqnarray</code> is attractive for the occasional user of mathematics in LaTeX documents: it seems to allow aligned systems of equations. Indeed it <em>does</em> supply such things, but it makes a serious mess of spacing. In the system: @@ -18,7 +18,7 @@ the spacing around the “=” signs is <em>not</em> that defined in the metrics for the font from which the glyph comes — it’s <code>\</code><code>arraycolsep</code>, which may be set to some very odd value for reasons associated with real arrays elsewhere in the document. -<p>The user is far better served by the AMSLaTeX bundle, which +<p/>The user is far better served by the AMSLaTeX bundle, which provides an <code>align</code> environment, which is designed with the needs of mathematicians in mind (as opposed to the convenience of LaTeX programmers). For this simple case (align is capable of far @@ -34,5 +34,5 @@ greater things), code as: <dl> <dt><tt><i>AMSLaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eqnarray">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eqnarray</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eqnarray">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=eqnarray</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errmissitem.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errmissitem.html index 27f50e1bf25..cf7d29a3f68 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errmissitem.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errmissitem.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label errmissitem</title> </head><body> <h3>Perhaps a missing <code>\</code><code>item</code>?</h3> -<p>Sometimes, the error +<p/>Sometimes, the error <blockquote> <pre> Something's wrong--perhaps a missing \item @@ -17,7 +17,55 @@ actually means what it says: </pre> </blockquote><p> produces the error, and is plainly in need of an <code>\</code><code>item</code> command. -<p>However, the error regularly appears when you would never have thought +<p/>You can also have the error appear when at first sight things are +correct: +<blockquote> +<pre> +\begin{tabular}{l} + \begin{enumerate} + \item foo\\ + \item bar + \end{enumerate} +\end{tabular} +</pre> +</blockquote><p> +produces the error at the bsbs. This usage is just wrong; if you +want to number the cells in a table, you have to do it “by hand”: +<blockquote> +<pre> +\newcounter{tablecell} +\begin{tabular}{l} + \stepcounter{tablecell} + \thetablecell. foo\\ + \stepcounter{tablecell} + \thetablecell. bar + \end{enumerate} +\end{tabular} +</pre> +</blockquote><p> +This is obviously untidy; a command <code>\</code><code>numbercell</code> defined as: +<blockquote> +<pre> +\newcounter{tablecell} +\newcommand*{\numbercell}{% + \stepcounter{tablecell}% + \thetablecell. % ** +} +</pre> +</blockquote><p> +could make life easier: +<blockquote> +<pre> +\begin{tabular}{l} + \numbercell foo\\ + \numbercell bar + \end{enumerate} +\end{tabular} +</pre> +</blockquote><p> +(Note the deliberate introduction of a space as part of the command, +marked with asterisks.) +<p/>However, the error regularly appears when you would never have thought that a <code>\</code><code>item</code> command might be appropriate. For example, the seemingly innocent: <blockquote> @@ -39,7 +87,7 @@ itself, in fact, so <code>\</code><code>begin{itemize}</code> won’t work i paragraphs, so it makes a new paragraph of its own. Inside the <code>\</code><code>fbox</code> command, that doesn’t work, and subsequent macros convince themselves that there’s a missing <code>\</code><code>item</code> command. -<p>To solve this rather cryptic error, one must put the +<p/>To solve this rather cryptic error, one must put the <code>alltt</code> inside a paragraph-style box. The following modification of the above <em>does</em> work: <blockquote> @@ -57,13 +105,13 @@ The code above produces a box that’s far too wide for the text. One may want to use something that allows <a href="FAQ-varwidth.html">variable size boxes</a> in place of the <code>minipage</code> environment. -<p>Oddly, although the <code>verbatim</code> environment wouldn’t work +<p/>Oddly, although the <code>verbatim</code> environment wouldn’t work inside a <code>\</code><code>fbox</code> command argument (see <a href="FAQ-verbwithin.html">verbatim in command arguments</a>), you get an error that complains about <code>\</code><code>item</code>: the environment’s internal list bites you before <code>verbatim</code> has even had a chance to create its own sort of chaos. -<p>Another (seemingly) obvious use of <code>\</code><code>fbox</code> also falls foul of this +<p/>Another (seemingly) obvious use of <code>\</code><code>fbox</code> also falls foul of this error: <blockquote> <pre> @@ -75,5 +123,5 @@ either write your own macros to replace the insides of LaTeX’s sectioning macros, or look for some alternative in the packages discussed in “<a href="FAQ-secthead.html">The style of section headings</a>”. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errmissitem">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errmissitem</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errmissitem">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errmissitem</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-erroradvice.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-erroradvice.html index 6f14c2e7f24..52223c34168 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-erroradvice.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-erroradvice.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label erroradvice</title> </head><body> <h3>How to approach errors</h3> -<p>Since TeX is a macroprocessor, its error messages are often +<p/>Since TeX is a macroprocessor, its error messages are often difficult to understand; this is a (seemingly invariant) property of macroprocessors. Knuth makes light of the problem in the TeXbook, suggesting that you acquire the sleuthing skills of a latter-day @@ -43,11 +43,11 @@ perplexing) errors that you may encounter. There’s a long list of <a href="FAQ-books.html">books about TeX</a>) in some detail, fully to understand the trace. -<p> The command <code>\</code><code>tracingall</code> sets up maximum tracing; it also sets +<p/> The command <code>\</code><code>tracingall</code> sets up maximum tracing; it also sets the output to come to the interactive terminal, which is somewhat of a mixed blessing (since the output tends to be so vast — all but the simplest traces are best examined in a text editor after the event). -<p> The LaTeX <i>trace</i> package (first distributed with the +<p/> The LaTeX <i>trace</i> package (first distributed with the 2001 release of LaTeX) provides more manageable tracing. Its <code>\</code><code>traceon</code> command gives you what <code>\</code><code>tracingall</code> offers, but suppresses tracing around some of the truly verbose parts of @@ -67,5 +67,5 @@ report full backtraces (see <code>errorcontextlines</code> above) and so on. <dl> <dt><tt><i>trace.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=erroradvice">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=erroradvice</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=erroradvice">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=erroradvice</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errparnum.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errparnum.html index acf76cb6dcb..2fc2e255709 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errparnum.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errparnum.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label errparnum</title> </head><body> <h3>Illegal parameter number in definition</h3> -<p>The error message means what it says. In the simple case, you’ve +<p/>The error message means what it says. In the simple case, you’ve attempted a definition like: <blockquote> <pre> @@ -19,7 +19,7 @@ In either of the above, the definition uses an argument, but the programmer did not tell (La)TeX, in advance, that she was going to. The fix is simple — <code>\</code><code>newcommand{<code>\</code><code>abc</code>}[1]</code>, in the LaTeX case, <code>\def\abc#1</code> in the basic TeX case. -<p>The more complicated case is exemplified by the attempted definition: +<p/>The more complicated case is exemplified by the attempted definition: <blockquote> <pre> \newcommand{\abc}{joy, oh joy!% @@ -39,5 +39,5 @@ This is because special care is needed when defining one macro within the code of another macro. This is explained elsewhere, separately for <a href="FAQ-ltxhash.html">LaTeX definitions</a> and for <a href="FAQ-hash.html">TeX primitive definitions</a> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errparnum">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errparnum</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errparnum">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errparnum</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errstruct.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errstruct.html index 96584e85424..5f29857452f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errstruct.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-errstruct.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label errstruct</title> </head><body> <h3>The structure of TeX error messages</h3> -<p>TeX’s error messages are reminiscent of the time when TeX itself +<p/>TeX’s error messages are reminiscent of the time when TeX itself was conceived (the 1970s): they’re not terribly user-friendly, though they do contain all the information that TeX can offer, usually in a pretty concise way. -<p>TeX’s error reports all have the same structure: +<p/>TeX’s error reports all have the same structure: <ul> <li> An error message <li> Some ‘context’ @@ -19,7 +19,7 @@ difficult to relate to the actual problem in the “higher-level” macros. Many LaTeX-detected problems manifest themselves as ‘generic’ errors, with error text provided by LaTeX itself (or by a LaTeX class or package). -<p>The context of the error is a stylised representation of what TeX +<p/>The context of the error is a stylised representation of what TeX was doing at the point that it detected the error. As noted in <a href="FAQ-erroradvice.html">approaching errors</a>, a macro package can tell TeX how much context to display, and the user may need to @@ -63,7 +63,7 @@ producing l.5 \blah{\bleah} , folks </pre> -<p>The prompt accepts single-character commands: the list of what’s +<p/>The prompt accepts single-character commands: the list of what’s available may be had by typing <code>?</code>. One immediately valuable command is <code>h</code>, which gives you an expansion of TeXs original précis message, sometimes accompanied by a hint on what to do to @@ -71,5 +71,5 @@ work round the problem in the short term. If you simply type ‘return&rsqu (or whatever else your system uses to signal the end of a line) at the prompt, TeX will attempt to carry on (often with rather little success). -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errstruct">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errstruct</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errstruct">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=errstruct</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-etex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-etex.html index ce6542cd99b..49ec4c33a05 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-etex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-etex.html @@ -2,34 +2,34 @@ <title>UK TeX FAQ -- question label etex</title> </head><body> <h3>What is e-TeX?</h3> -<p>While Knuth has declared that TeX will never +<p/>While Knuth has declared that TeX will never <a href="FAQ-TeXfuture.html">change in any substantial way</a>, there remain things that one might wish had been done differently, or indeed implemented at all. -<p>The NTS project set out to produce an advanced replacement for +<p/>The NTS project set out to produce an advanced replacement for TeX, to provide a basis for developing such modifications: this “New Typesetting System” would share Knuth’s aims, but would implement the work in a modern way taking account of the lessons learned with TeX. While a first demonstrator NTS did appear, it wasn’t practically useful, and the project seems no longer active. -<p>In parallel with its work on NTS itself, the project developed +<p/>In parallel with its work on NTS itself, the project developed a set of extensions that can be used with a (“true”) TeX system. Such a modified system is known as an e-TeX system, and the concept has proved widely successful. Indeed, current TeX distributions are delivered with most formats built with an e-TeX system (for those who don’t want them, e-TeX’s extensions can be disabled, leaving a functionally standard TeX system). -<p>The extensions range from the simple (increasing the number of -available registers from 256 to 65536) through to extremely subtle +<p/>The extensions range from the seemingly simple (increasing the number +of available registers from 256 to 32768) through to extremely subtle programming support. -<p><a href="FAQ-context.html">ConTeXt</a> has required e-TeX for its operation +<p/><a href="FAQ-context.html">ConTeXt</a> has required e-TeX for its operation for some time. -<p>Some LaTeX packages already specify the use of e-TeX. Some such +<p/>Some LaTeX packages already specify the use of e-TeX. Some such packages may not work at all on a non-e-TeX system; others will work, but not as well as on an e-TeX system. The <a href="FAQ-LaTeX3.html">LaTeX team</a> has announced that future LaTeX packages (specifically those from the team, as opposed to those individually contributed) may require e-TeX for optimum performance. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=etex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=etex</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=etex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=etex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-euro.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-euro.html index ed62f2c201c..78c2fd342d3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-euro.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-euro.html @@ -2,15 +2,15 @@ <title>UK TeX FAQ -- question label euro</title> </head><body> <h3>Typesetting the Euro sign</h3> -<p>The European currency “Euro” is represented by a symbol of somewhat +<p/>The European currency “Euro” is represented by a symbol of somewhat dubious design, but it’s an important currency and (La)TeX users need to typeset it. -<p>Note that the Commission of the European Community at first deemed +<p/>Note that the Commission of the European Community at first deemed that the Euro symbol should always be set in a sans-serif font; fortunately, this eccentric ruling has now been rescinded, and one may apply best typesetting efforts to making it appear at least slightly “respectable” (typographically). -<p>The TS1-encoded fonts provided as part of the EC font +<p/>The TS1-encoded fonts provided as part of the EC font distribution provide Euro glyphs. The fonts are called Text Companion (TC) fonts, and offer the same range of faces as do the EC fonts themselves. The @@ -20,7 +20,7 @@ text. The design of the symbol in the TC fonts is not universally loved... Nevertheless, use the TC font version of the symbol if you are producing documents using Knuth’s Computer Modern Fonts. -<p>The <i>latin9</i> input encoding defined by the <i>inputenc</i> +<p/>The <i>latin9</i> input encoding defined by the <i>inputenc</i> package has a euro character defined (character position 164, occupied in other ISO Latin character sets by the “currency symbol”). The encoding uses the command <code>\</code><code>texteuro</code> for the character; at @@ -29,12 +29,12 @@ present that command is <em>only</em> available from the too, but standardisation of such things proceeds via rather different routes and the LaTeX project hasn’t yet been given details of the change. -<p>Outline fonts which contain nothing but Euro symbols are available +<p/>Outline fonts which contain nothing but Euro symbols are available (free) from <a href="ftp://ftp.adobe.com/pub/adobe/type/win/all/eurofont.exe">Adobe</a> — the file is packaged as a <i>Windows</i> self-extracting -executable, but it may be decoded as a <code>.zip</code> format achive on other -operating systems. +executable, but it may be decoded as a <code>.zip</code> format achive +on other operating systems. The <i>euro</i> bundle contains metrics, <i>dvips</i> map files, and macros (for Plain TeX and LaTeX), for using these fonts in documents. LaTeX users will find two packages in the @@ -46,28 +46,28 @@ with the surrounding text (providing the command <code>\</code><code>EUR</code>) either package with the <i>latin9</i> encoding, you need to define <code>\</code><code>texteuro</code> as an alias for the euro command the package defines. -<p>The Adobe fonts are probably the best bet for use in non-Computer +<p/>The Adobe fonts are probably the best bet for use in non-Computer Modern environments. They are apparently designed to fit with Adobe Times, Helvetica and Courier, but can probably fit with a wider range of modern fonts. -<p>The <i>eurofont</i> package provides a compendious analysis of the +<p/>The <i>eurofont</i> package provides a compendious analysis of the “problem of the euro symbol” in its documentation, and offers macros for configuring the source of the glyphs to be used; however, it seems rather large for everyday use. -<p>The <i>euro-ce</i> bundle is a rather pleasing Metafont-only design +<p/>The <i>euro-ce</i> bundle is a rather pleasing Metafont-only design providing Euro symbols in a number of shapes. The file <i>euro-ce.tex</i>, in the distribution, offers hints as to how a Plain TeX user might make use of the fonts. -<p>Euro symbols are found in several other places, which we list here for +<p/>Euro symbols are found in several other places, which we list here for completeness. -<p>The <i>marvosym</i> fonts contain a Euro symbol among many other +<p/>The <i>marvosym</i> fonts contain a Euro symbol among many other good things. -<p>Other Metafont-based bundles containing Euro symbols are to be found in +<p/>Other Metafont-based bundles containing Euro symbols are to be found in <i>china2e</i> (whose primary aim is Chinese dates and suchlike matters) and the <i>eurosym</i> fonts. <dl> @@ -80,5 +80,5 @@ matters) and the <i>eurosym</i> fonts. <dt><tt><i>marvosym fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/psfonts/marvosym.zip">fonts/psfonts/marvosym</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/psfonts/marvosym.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/psfonts/marvosym/">browse</a>) <dt><tt><i>textcomp.sty</i></tt><dd>Part of the LaTeX distribution. </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=euro">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=euro</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=euro">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=euro</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-exscale.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-exscale.html index a2458e57cce..fb1431f03c4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-exscale.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-exscale.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label exscale</title> </head><body> <h3>Maths symbols don’t scale up</h3> -<p>By default, the “large” maths symbols stay at the same size +<p/>By default, the “large” maths symbols stay at the same size regardless of the font size of the text of the document. There’s good reason for this: the <i>cmex</i> fonts aren’t really designed to scale, so that TeX’s maths placement algorithms don’t perform as well as they might when the fonts are scaled. -<p>However, this behaviour confounds user expectations, and can lead to +<p/>However, this behaviour confounds user expectations, and can lead to slightly odd-looking documents. If you want the fonts to scale, despite the warning above, use the <i>exscale</i> package — just loading it is enough. @@ -18,5 +18,5 @@ loading it is enough. <dl> <dt><tt><i>exscale.sty</i></tt><dd>Part of the LaTeX distribution. </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=exscale">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=exscale</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=exscale">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=exscale</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extex.html index 0ee13e76201..79c17ffe680 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extex.html @@ -2,21 +2,21 @@ <title>UK TeX FAQ -- question label extex</title> </head><body> <h3>The ExTeX project</h3> -<p><a href="http://www.extex.org/">The ExTeX project</a> is +<p/><a href="http://www.extex.org/">The ExTeX project</a> is building on the experience of the many existing TeX development and extension projects, to develop a new TeX-like system. The system is to be developed in Java (like the ill-fated <i>NTS</i> project). -<p>While ExTeX will implement all of TeX’s primitives, some may be +<p/>While ExTeX will implement all of TeX’s primitives, some may be marked as obsolete, and “modern” alternatives provided (an obvious example is the primitive <code>\</code><code>input</code> command, whose syntax inevitably makes life difficult for users of modern operating system file paths). Desirable extensions from <a href="FAQ-etex.html">e-TeX</a>, <a href="FAQ-whatpdftex.html">PDFTeX</a> and <a href="FAQ-omegaleph.html">Omega</a> have been identified. -<p>Usability will be another focus of the work: debugging support and log +<p/>Usability will be another focus of the work: debugging support and log filtering mechanisms will please those who have long struggled with TeX macros. -<p>ExTeX will accept Unicode input, from the start. In the longer +<p/>ExTeX will accept Unicode input, from the start. In the longer term, drawing primitives are to be considered. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extex</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extrabrace.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extrabrace.html index a0e03cd4640..1f68cf4bd74 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extrabrace.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extrabrace.html @@ -3,12 +3,12 @@ </head><body> <h3>An extra ‘<code>}</code>’??</h3> <!-- caption heading --> -<p>You’ve looked at your LaTeX source and there’s no sign of a misplaced +<p/>You’ve looked at your LaTeX source and there’s no sign of a misplaced <code>}</code> on the line in question. -<p>Well, no: this is TeX’s cryptic way of hinting that you’ve put a +<p/>Well, no: this is TeX’s cryptic way of hinting that you’ve put a <a href="FAQ-protect.html">fragile command</a> in a moving argument. -<p>For example, <code>\</code><code>footnote</code> is fragile, and if we put that in the +<p/>For example, <code>\</code><code>footnote</code> is fragile, and if we put that in the moving argument of a <code>\</code><code>section</code> command, as <blockquote> @@ -58,8 +58,8 @@ example as: </blockquote><p> for, after all, even if you want display maths in a caption, you surely don’t want it in the list of figures. -<p>The case of footnotes is somewhat more complex; +<p/>The case of footnotes is somewhat more complex; “<a href="FAQ-ftnsect.html">footnotes in LaTeX section headings</a>” deals specifically with that issue. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extrabrace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extrabrace</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extrabrace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extrabrace</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extref.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extref.html index b9e13263f44..c38d4bf0af9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extref.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extref.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label extref</title> </head><body> <h3>Referring to labels in other documents</h3> -<p>When producing a set of inter-related documents, you’ll often want to +<p/>When producing a set of inter-related documents, you’ll often want to refer to labels in another document of the set; but LaTeX, of its own accord, doesn’t permit this. -<p>So the package <i>xr</i> was written: if you say +<p/>So the package <i>xr</i> was written: if you say <blockquote> <pre> \usepackage{xr} @@ -14,7 +14,7 @@ own accord, doesn’t permit this. </blockquote><p> will load all the references from <i>volume1</i> into your present document. -<p>But what if the documents both have a section labelled +<p/>But what if the documents both have a section labelled “<code>introduction</code>” (likely enough, after all)? The package provides a means to transform all the imported labels, so you don’t have to change label names in either document. For example: @@ -51,7 +51,7 @@ compiled), write: </blockquote><p> and the name reference will appear as an active link to the “introduction” chapter of <i>volume1.pdf</i>. -<p>To link to a PDF document on the Web, for which you happen to +<p/>To link to a PDF document on the Web, for which you happen to have the .aux file, write: <blockquote> <pre> @@ -67,6 +67,6 @@ have the .aux file, write: <dt><tt><i>xr.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) <dt><tt><i>xr-hyper.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>) </dl> -<p> -<p><p><p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extref</a> +<p/> +<p/><p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extref</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extsizes.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extsizes.html index fa71555960b..20f9d86dafe 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extsizes.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-extsizes.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label extsizes</title> </head><body> <h3>Other “document font” sizes?</h3> -<p>The LaTeX standard classes have a concept of a (base) “document +<p/>The LaTeX standard classes have a concept of a (base) “document font” size; this size is the basis on which other font sizes (those from <code>\</code><code>tiny</code> to <code>\</code><code>Huge</code>) are determined. The classes are designed on the assumption that they won’t be used with sizes other than the @@ -10,13 +10,13 @@ set that LaTeX offers by default (10–12pt), but people regularly find they need other sizes. The proper response to such a requirement is to produce a new design for the document, but many people don’t fancy doing that. -<p>A simple solution is to use the <i>extsizes</i> bundle. This +<p/>A simple solution is to use the <i>extsizes</i> bundle. This bundle offers “extended” versions of the article, report, book and letter classes, at sizes of 8, 9, 14, 17 and 20pt as well as the standard 10–12pt. Since little has been done to these classes other than to adjust font sizes and things directly related to them, they may not be optimal — but they’re certainly practical. -<p>More satisfactory are the <em>KOMA-script</em> classes, which are +<p/>More satisfactory are the <em>KOMA-script</em> classes, which are designed to work properly with the class option files that come with <i>extsizes</i>, and the <i>memoir</i> class that has its own options for document font sizes 9pt, 14pt and 17pt. @@ -25,5 +25,5 @@ options for document font sizes 9pt, 14pt and 17pt. <dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) </dl> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extsizes">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extsizes</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extsizes">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=extsizes</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fancyhdr.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fancyhdr.html index 9160b1850dd..a07ae879e1d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fancyhdr.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fancyhdr.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label fancyhdr</title> </head><body> <h3>Alternative head- and footlines in LaTeX</h3> -<p>The standard LaTeX document classes define a small set of ‘page +<p/>The standard LaTeX document classes define a small set of ‘page styles’ which specify head- and footlines for your document (though they can be used for other purposes, too). The standard set is very limited, but LaTeX is capable of much more. The internal @@ -10,22 +10,22 @@ LaTeX coding needed to change page styles is not particularly challenging, but there’s no need — there are packages that provide useful abstractions that match the way we typically think about these things. -<p>The <i>fancyhdr</i> package provides +<p/>The <i>fancyhdr</i> package provides simple mechanisms for defining pretty much every head- or footline variation you could want; the directory also contains some documentation and one or two smaller packages. <i>Fancyhdr</i> also deals with the tedious behaviour of the standard styles with <a href="FAQ-psatempty.html">initial pages</a>, by enabling you to define different page styles for initial and for body pages. -<p>While <i>fancyhdr</i> will work with <i>KOMA-script</i> classes, +<p/>While <i>fancyhdr</i> will work with <i>KOMA-script</i> classes, an alternative package, <i>scrpage2</i>, eases integration with the classes. <i>Scrpage2</i> may also be used as a <i>fancyhdr</i> replacement, providing similar facilities. The <i>KOMA-script</i> classes themselves permit some modest redefinition of head- and footlines, without the use of the extra package. -<p><i>Memoir</i> also contains the functionality of <i>fancyhdr</i>, +<p/><i>Memoir</i> also contains the functionality of <i>fancyhdr</i>, and has several predefined styles. -<p>Documentation of <i>fancyhdr</i> is distributed with the package, +<p/>Documentation of <i>fancyhdr</i> is distributed with the package, in a separate file; documentation of <i>scrpage2</i> is integrated with the <i>scrgui*</i> documentation files that are distributed with the <i>KOMA-script</i> classes. @@ -34,5 +34,5 @@ the <i>KOMA-script</i> classes. <dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fancyhdr">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fancyhdr</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fancyhdr">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fancyhdr</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fig.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fig.html index b0a86b437ba..5d151d09186 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fig.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fig.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label fig</title> </head><body> <h3>Fig, a (La)TeX-friendly drawing package</h3> -<p><i>(X)Fig</i> is a menu driven tool that allows you to +<p/><i>(X)Fig</i> is a menu driven tool that allows you to draw objects on the screen of an X workstation; <i>transfig</i> is a set of tools which translate the code <i>fig</i>. The list of export formats is very long, and includes Metafont and MetaPost, Encapsulated PostScript and PDF, as well as combinations that wrap a graphics format in a LaTeX import file. -<p>There’s no explicit port of <i>xfig</i> to windows (although it is +<p/>There’s no explicit port of <i>xfig</i> to windows (although it is believed to work under <i>cygwin</i> with their X-windows system). However, the program <a href="http://tech-www.informatik.uni-hamburg.de/applets/javafig/"><i>jfig</a></i> @@ -17,5 +17,5 @@ is thought by many to be an acceptable substitute, written in Java. <dt><tt><i>xfig</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/xfig.zip">graphics/xfig</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/xfig.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/xfig/">browse</a>) <dt><tt><i>transfig</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/transfig.zip">graphics/transfig</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/transfig.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/transfig/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fig">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fig</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fig">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fig</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-figurehere.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-figurehere.html new file mode 100644 index 00000000000..e5b38703e2e --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-figurehere.html @@ -0,0 +1,57 @@ +<head> +<title>UK TeX FAQ -- question label figurehere</title> +</head><body> +<h3>Figure (or table) <em>exactly</em> where I want it</h3> +<p/>This is of course a contradiction: <code>figure</code> and +<code>table</code> are <em>designed</em> to float, and will always have +the potential to appear away from where you asked for them. Therefore +you have to find a means of getting the caption and other effects +without allowing the figure or table to float. +<p/>The most straightforward way is to use the <i>float</i> package; it +gives you a <code>[H]</code> float placement option that prevents +floating: +<blockquote> +<pre> +\begin{figure}[H] + \centering + \includegraphics{foo} + \caption{caption text} + \label{fig:nonfloat} +\end{figure} +</pre> +</blockquote><p> +As the example shows, these <code>[H]</code> figures (and correspondingly, +tables) offer all you need to cross-reference as well as typeset. +<p/>However, you don’t actually <em>have</em> to use <i>float</i> since +it is, in fact, doing rather little for you. You can place your +figure as you please, with a sequence like +<blockquote> +<pre> +\begin{center} + \includegraphics{foo} + \captionof{figure}{caption text} + \label{fig:nonfloat} +\end{center} +</pre> +</blockquote><p> +which relies on the <code>\</code><code>captionof</code> command to place a caption in +ordinary running text. That command may be had from the extremely +simple-minded package <i>capt-of</i> or from the highly +sophisticated <i>caption</i> package. +<p/>Using either method, you have to deal with the possibility of the +figure or table being too large for the page. (Floating objects will +float away in this circumstance; “doing it by hand”, like this, you +take upon yourself the responsibility for avoiding +‘<i>Overfull <code>\</code><code>vbox</code></i>’ errors. +<p/>A further problem is the possibility that such “fixed floats” will +overtake “real floats”, so that the numbers of figures will be out +of order: figure 6 could be on page 12, while figure 5 had floated to +page 13. It’s best, therefore, either to stay with floating figures +throughout a document, or to use fixed figures throughout. +<dl> +<dt><tt><i>capt-of.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/capt-of.sty">macros/latex/contrib/misc/capt-of.sty</a> +<dt><tt><i>caption.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/caption.zip">macros/latex/contrib/caption</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/caption.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/caption/">browse</a>) +<dt><tt><i>float.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse</a>) +</dl> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=figurehere">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=figurehere</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html index d66aec9f640..440367ae596 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html @@ -2,25 +2,25 @@ <title>UK TeX FAQ -- question label filename</title> </head><body> <h3>What’s the name of this file</h3> -<p>One might want this so as to automatically generate a page header or +<p/>One might want this so as to automatically generate a page header or footer recording what file is being processed. It’s not easy... -<p>TeX retains what it considers the name of the <em>job</em>, only, in +<p/>TeX retains what it considers the name of the <em>job</em>, only, in the primitive <code>\</code><code>jobname</code>; this is the name of the file first handed to TeX, stripped of its directory name and of any extension (such as <code>.tex</code>). If no file was passed (i.e., you’re using TeX interactively), <code>\</code><code>jobname</code> has the value <code>texput</code> (the name that’s given to <code>.log</code> files in this case). -<p>This is fine, for the case of a small document, held in a single file; +<p/>This is fine, for the case of a small document, held in a single file; most significant documents will be held in a bunch of files, and TeX makes no attempt to keep track of files input to the <em>job</em>. So the user has to keep track, himself — the only way is to patch the input commands and cause them to retain details of the file name. This is particularly difficult in the case of Plain TeX, since the syntax of the <code>\</code><code>input</code> command is so peculiar. -<p>In the case of LaTeX, the input commands have pretty regular +<p/>In the case of LaTeX, the input commands have pretty regular syntax, and the simplest <a href="FAQ-patch.html">patching techniques</a> can be used on them. -<p>If you’re not inputting things from a file that’s already been input, +<p/>If you’re not inputting things from a file that’s already been input, the job is almost trivial: <blockquote> <pre> @@ -36,7 +36,7 @@ With that, the macro <code>\</code><code>ThisFile</code> always contains the las input: it starts pointing at the base file of your document (<code>\</code><code>jobname</code>), and thereafter changes every time you use <code>\</code><code>input{</code><em>file</em><code>}</code>. -<p>Most ordinary users will quickly become irritated with the simplicity +<p/>Most ordinary users will quickly become irritated with the simplicity of of the <code>\</code><code>ThisFile</code> mechanism above. The following code is more cunning: it maintains details of the files you’ve ‘come through’ to get to where you are, and it restores <code>\</code><code>ThisFile</code> to what the @@ -74,7 +74,7 @@ To do the same for <code>\</code><code>include</code>, we need the simple additi </blockquote><p> Both examples of patching <code>\</code><code>input</code> assume you always use LaTeX syntax, i.e., always use braces around the argument. -<p>The <i>FiNK</i> (“File Name Keeper”) package provides a +<p/>The <i>FiNK</i> (“File Name Keeper”) package provides a regular means of keeping track of the current file name (with its extension), in a macro <code>\</code><code>finkfile</code>. If you need the unadorned file name (without its ‘<code>.tex</code>’), use the commands: @@ -90,5 +90,5 @@ support under <i>emacs</i> with AUC-TeX. <dl> <dt><tt><i>fink.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fink.zip">macros/latex/contrib/fink</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fink.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fink/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=filename">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=filename</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=filename">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=filename</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filesused.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filesused.html index 101822a2bf4..9a10f936df3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filesused.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filesused.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label filesused</title> </head><body> <h3>All the files used by this document</h3> -<p>When you’re sharing a document with someone else (perhaps as part of a +<p/>When you’re sharing a document with someone else (perhaps as part of a co-development cycle) it’s as well to arrange that both correspondents have the same set of auxiliary files, as well as the document in question. Your correspondent obviously needs the same set of files @@ -11,11 +11,11 @@ too, for example). But suppose you have a bug-free version of the <i>shinynew</i> package but her copy is still the unstable original; until you both realise what is happening, such a situation can be very confusing. -<p>The simplest solution is the LaTeX <code>\</code><code>listfiles</code> command. This +<p/>The simplest solution is the LaTeX <code>\</code><code>listfiles</code> command. This places a list of the files used and their version numbers in the log file. If you extract that list and transmit it with your file, it can be used as a check-list in case that problems arise. -<p>Note that <code>\</code><code>listfiles</code> only registers things that are input by the +<p/>Note that <code>\</code><code>listfiles</code> only registers things that are input by the “standard” LaTeX mechanisms (<code>\</code><code>documentclass</code>, <code>\</code><code>usepackage</code>, <code>\</code><code>input</code>, <code>\</code><code>include</code>, <code>\</code><code>includegraphics</code> and so on). But if you use TeX primitive syntax, as in @@ -24,12 +24,12 @@ use TeX primitive syntax, as in </pre> <i>mymacros.tex</i> <em>won’t</em> be listed by <code>\</code><code>listfiles</code>, since you’ve bypassed the mechanism that records its use. -<p>The <i>snapshot</i> package helps the owner of a LaTeX document +<p/>The <i>snapshot</i> package helps the owner of a LaTeX document obtain a list of the external dependencies of the document, in a form that can be embedded at the top of the document. The intended use of the package is the creation of archival copies of documents, but it has application in document exchange situations too. -<p>The <i>bundledoc</i> system uses the <i>snapshot</i> to produce an +<p/>The <i>bundledoc</i> system uses the <i>snapshot</i> to produce an archive (e.g., <code>.tar.gz</code> or <code>.zip</code>) of the files needed by your document; it comes with configuration files for use with <i>teTeX</i> and <i>MiKTeX</i>. It’s plainly useful when @@ -38,5 +38,5 @@ you’re sending the first copy of a document. <dt><tt><i>bundledoc</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/bundledoc.zip">support/bundledoc</a> (<a href="ftp://cam.ctan.org/tex-archive/support/bundledoc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/bundledoc/">browse</a>) <dt><tt><i>snapshot.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/snapshot.zip">macros/latex/contrib/snapshot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/snapshot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/snapshot/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=filesused">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=filesused</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=filesused">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=filesused</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfiles.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfiles.html index f8298cfb5c1..dac5bec453a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfiles.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfiles.html @@ -2,22 +2,22 @@ <title>UK TeX FAQ -- question label findfiles</title> </head><body> <h3>Finding (La)TeX files</h3> -<p>Modern TeX distributions contain a huge array of support files of +<p/>Modern TeX distributions contain a huge array of support files of various sorts, but sooner or later most people need to find something that’s not in their present system (if nothing else, because they’ve heard that something has been updated). -<p>But how to find the files? -<p>Some sources, such as these FAQ answers, provide links to +<p/>But how to find the files? +<p/>Some sources, such as these FAQ answers, provide links to files: so if you’ve learnt about a package here, you should be able to retrieve it without too much fuss. -<p>Otherwise, the CTAN sites provide searching facilities, via the web. +<p/>Otherwise, the CTAN sites provide searching facilities, via the web. The simplest search, locating files by name, is to be found on the Dante CTAN at <a href="http://www.dante.de/cgi-bin/ctan-index">http://www.dante.de/cgi-bin/ctan-index</a>; the script scans a list of files (<i>FILES.byname</i> — see below) and returns a list of matches, arranged very neatly as a series of links to directories and to individual files. -<p>The <a href="http://www.tex.ac.uk/search">UK</a> and +<p/>The <a href="http://www.tex.ac.uk/search">UK</a> and <a href="http://www.ctan.org/search">USA</a> CTANs offer a search page that provides <ul> @@ -29,12 +29,12 @@ search page that provides <li> a search form that allows you to use <i>Google</i> to search CTAN. </ul> -<p>An alternative way to scan the catalogue is to use the catalogue’s +<p/>An alternative way to scan the catalogue is to use the catalogue’s <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/bytopic.html">“by topic” index</a>; this lists a series of topics, and (La)TeX projects that are worth considering if you’re working on matters related to the topic. -<p>In fact, <i>Google</i>, and other search engines, can be useful +<p/>In fact, <i>Google</i>, and other search engines, can be useful tools. Enter your search keywords, and you may pick up a package that the author hasn’t bothered to submit to CTAN. If you’re using <i>Google</i>, you can restrict your search to CTAN by @@ -45,7 +45,7 @@ entering in <i>Google</i>’s “search box”. You can also enforce the restriction using <i>Google</i>’s “advanced search” mechanism; other search engines (presumably) have similar facilities. -<p>Many people avoid the need to go over the network at all, for their +<p/>Many people avoid the need to go over the network at all, for their searches, by downloading the file list that the archives’ web file searches use. This file, <i>FILES.byname</i>, presents a unified listing of the archive (omitting directory names and @@ -57,5 +57,5 @@ updated only once a day, a nightly automatic download (perhaps using <dt><tt><i>FILES.byname</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/FILES.byname">FILES.byname</a> <dt><tt><i>FILES.last07days</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/FILES.last07days">FILES.last07days</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findfiles">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findfiles</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findfiles">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findfiles</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfont.html index 8dcbcacdbe8..240ad8b393d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfont.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findfont.html @@ -2,21 +2,26 @@ <title>UK TeX FAQ -- question label findfont</title> </head><body> <h3>Finding new fonts</h3> -<p>A comprehensive list of Metafont fonts used to be posted to +<p/>A comprehensive list of Metafont fonts used to be posted to <i>comp.fonts</i> and to <i>comp.text.tex</i>, roughly -every six weeks, by Lee Quin. -<p> - - - -<p>Nowadays, authors of new material in Metafont are few and far between +every six weeks, by Lee Quin. +Nowadays, authors of new material in Metafont are few and far between (and mostly designing highly specialised things with limited appeal to -ordinary users). Most new fonts that appear are prepared in some -scalable outline form or other (see -<a href="FAQ-psfchoice.html">“choice of scalable fonts”</a>), and they -are almost all distributed under commercial terms. +ordinary users); as a result, no-one has taken over maintenance of the +list of fonts. If you need a font for some esoteric purpose, it may +be worth <a href="FAQ-findfiles.html">searching CTAN</a> using your purpose +as a search keyword. +<p/>Most new fonts that appear are prepared in some scalable outline form +or other, and a large proportion is distributed under commercial +terms. However, once you have acquired such a font, converting it to +a form usable by your (La)TeX distribution is not (in principle) a +serious problem. +<p/>The answer “<a href="FAQ-psfchoice.html">choice of scalable fonts</a>” discusses +fonts that are configured for general (both textual and mathematical) +use with (La)TeX. The list of such fonts is sufficiently short that +they <em>can</em> all be discussed in one answer here. <dl> <dt><tt><i>Metafont font list</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/metafont-list">info/metafont-list</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findfont</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findfont</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findwidth.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findwidth.html index c6cfdeef124..c381aed0824 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findwidth.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-findwidth.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label findwidth</title> </head><body> <h3>Finding the width of a letter, word, or phrase</h3> -<p>Put the word in a box, and measure the width of the box. For example, +<p/>Put the word in a box, and measure the width of the box. For example, <blockquote> <pre> \newdimen\stringwidth @@ -14,7 +14,7 @@ Note that if the quantity in the <code>\</code><code>hbox</code> is a phrase, th measurement only approximates the width that the phrase will occupy in running text, since the inter-word glue can be adjusted in paragraph mode. -<p>The same sort of thing is expressed in LaTeX by: +<p/>The same sort of thing is expressed in LaTeX by: <blockquote> <pre> \newlength{\gnat} @@ -23,5 +23,5 @@ mode. </blockquote><p> This sets the value of the length command <code>\gnat</code> to the width of “small” in bold-face text. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findwidth">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findwidth</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findwidth">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=findwidth</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixnam.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixnam.html index d8a6bf5120c..c71a2416792 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixnam.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixnam.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label fixnam</title> </head><body> <h3>How to change LaTeX’s “fixed names”</h3> -<p>LaTeX document classes define several typographic operations that +<p/>LaTeX document classes define several typographic operations that need ‘canned text’ (text not supplied by the user). In the earliest days of LaTeX 2.09 these bits of text were built in to the body of LaTeX’s macros and were rather difficult to change, but “fixed @@ -13,7 +13,7 @@ command is always called <code>\</code><code>contentsname</code> (or rather, wha <code>\</code><code>contentsname</code> is defined to mean). Changing the canned text is now one of the easiest customisations a user can do to LaTeX. -<p>The canned text macros are all of the form +<p/>The canned text macros are all of the form <code>\</code><code><<i>thing</code>name</i>>, and changing them is simplicity itself. Put: <blockquote> @@ -25,12 +25,12 @@ use a different mechanism: be sure to check <a href="FAQ-latexwords.html">changing <i>babel</i> names</a> if you’re using it.) -<p>The names that are defined in the standard LaTeX classes (and the +<p/>The names that are defined in the standard LaTeX classes (and the <i>makeidex</i> package) are listed below. Some of the names are only defined in a subset of the classes (and the <i>letter</i> class has a set of names all of its own); the list shows the specialisation of each name, where appropriate. -<p><table rules="groups" border="0" cellpadding="3"><tbody><tr><td> +<p/><table rules="groups" border="0" cellpadding="3"><tbody><tr><td> <code>\</code><code>abstractname</code> <td> Abstract<tr><td> <code>\</code><code>alsoname</code> <td> see also (<i>makeidx</i> package)<tr><td> <code>\</code><code>appendixname</code> <td> Appendix<tr><td> @@ -50,5 +50,5 @@ the list shows the specialisation of each name, where appropriate. <code>\</code><code>seename</code> <td> see (<i>makeidx</i> package)<tr><td> <code>\</code><code>tablename</code> <td> Table (for caption) </tbody></table> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixnam">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixnam</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixnam">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixnam</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixwidtab.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixwidtab.html index c5cc58bb42f..44d4bc41ac1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixwidtab.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fixwidtab.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label fixwidtab</title> </head><body> <h3>Fixed-width tables</h3> -<p>There are two basic techniques for making fixed-width tables in +<p/>There are two basic techniques for making fixed-width tables in LaTeX: you can make the gaps between the columns stretch, or you can stretch particular cells in the table. -<p>Basic LaTeX can make the gaps stretch: the <code>tabular*</code> +<p/>Basic LaTeX can make the gaps stretch: the <code>tabular*</code> environment takes an extra argument (before the <code>clpr</code> layout one) which takes a length specification: you can say things like “<code>15cm</code>” or “<code>\</code><code>columnwidth</code>” here. You must also have an <code>\</code><code>extracolsep</code> @@ -18,11 +18,11 @@ for example, one might have The <code>\</code><code>extracolsep</code> applies to all inter-column gaps to its right as well; if you don’t want all gaps stretched, add <code>\</code><code>extracolsep{0pt}</code> to cancel the original. -<p>The <i>tabularx</i> package defines an extra <code>clpr</code> column +<p/>The <i>tabularx</i> package defines an extra <code>clpr</code> column specification, <code>X</code>; <code>X</code> columns behave as <code>p</code> columns which expand to fill the space available. If there’s more than one <code>X</code> column in a table, the spare space is distributed between them. -<p>The <i>tabulary</i> package (by the same author) provides a way of +<p/>The <i>tabulary</i> package (by the same author) provides a way of “balancing” the space taken by the columns of a table. The package defines column specifications <code>C</code>, <code>L</code>, <code>R</code> and <code>J</code>, giving, respectively, centred, left, right and fully-justified versions of @@ -36,13 +36,17 @@ specified minimum. Of course, all this work means that the package has to typeset each row several times, so things that leave “side-effects” (for example, a counter used to produce a row-number somewhere) are inevitably unreliable, and should not even be tried. -<p>The <i>ltxtable</i> combines the features of the -<i>longtable</i> and <i>tabularx</i> packages: it’s important to -read the documentation, since usage is distinctly odd. +<p/>The <i>ltxtable</i> package combines the features of the +<i>longtable</i> and <i>tabularx</i> packages. It’s important +to read the documentation, since usage is distinctly odd; the +distribution contains no more than a file <i>ltxtable.tex</i>, which you +should process using LaTeX. Processing will give you a <i>.sty</i> +file as well as the <i>.dvi</i> or <i>.pdf</i> output containing the +documentation. <dl> <dt><tt><i>ltxtable.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>) <dt><tt><i>tabularx.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) <dt><tt><i>tabulary.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tabulary.zip">macros/latex/contrib/tabulary</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tabulary.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tabulary/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixwidtab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixwidtab</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixwidtab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fixwidtab</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fllost.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fllost.html index 596df8c8868..9d2d936517b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fllost.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fllost.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label fllost</title> </head><body> <h3>Float(s) lost</h3> -<p>The error +<p/>The error <blockquote> <pre> ! LaTeX Error: Float(s) lost. @@ -10,19 +10,19 @@ </blockquote><p> seldom occurs, but always seems deeply cryptic when it <em>does</em> appear. -<p>The message means what it says: one or more figures, tables, etc., or +<p/>The message means what it says: one or more figures, tables, etc., or marginpars has not been typeset. (Marginpars are treated internally as floats, which is how they come to be lumped into this error message.) -<p>The most likely reason is that you placed a float or a <code>\</code><code>marginpar</code> +<p/>The most likely reason is that you placed a float or a <code>\</code><code>marginpar</code> command inside another float or marginpar, or inside a <code>minipage</code> environment, a <code>\</code><code>parbox</code> or <code>\</code><code>footnote</code>. Note that the error may be detected a long way from the problematic command(s), so the techniques of <a href="FAQ-erroradvice.html">tracking down elusive errors</a> all need to be called into play. -<p>This author has also encountered the error when developing macros that +<p/>This author has also encountered the error when developing macros that used the LaTeX internal float mechanisms. Most people doing that sort of thing are expected to be able to work out their own problems... -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fllost">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fllost</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fllost">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fllost</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floatpages.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floatpages.html index c933ce46d99..2a12c789b0b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floatpages.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floatpages.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label floatpages</title> </head><body> <h3>Floats on their own on float pages</h3> -<p>It’s sometimes necessary to force a float to live on a page by itself. +<p/>It’s sometimes necessary to force a float to live on a page by itself. (It’s sometimes even necessary for <em>every</em> float to live on a page by itself.) When the float fails to ‘set’, and waits for the end of a chapter or of the document, the natural thing to do is to declare @@ -14,7 +14,7 @@ but the overriding <code>!</code> modifier has no effect on float page floats; s you have to make the float satisfy the parameters. <a href="FAQ-floats.html">Moving tables and figures</a> offers some suggestions, but doesn’t solve the one-float-per-page question. -<p>The ‘obvious’ solution, using the counter <code>totalnumber</code> (“total +<p/>The ‘obvious’ solution, using the counter <code>totalnumber</code> (“total number of floats per page”) doesn’t work: <code>totalnumber</code> only applies to floats on ‘text’ pages (pages containing text as well as one or more float). So, to allow any diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floats.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floats.html index 3ff95d552b5..a11a06cb088 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floats.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-floats.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label floats</title> </head><body> <h3>Moving tables and figures in LaTeX</h3> -<p>Tables and figures have a tendency to surprise, by <em>floating</em> +<p/>Tables and figures have a tendency to surprise, by <em>floating</em> away from where they were specified to appear. This is in fact perfectly ordinary document design; any professional typesetting package will float figures and tables to where they’ll fit without @@ -19,14 +19,8 @@ problems (the checklist talks throughout about figures, but applies equally well to tables, or to “non-standard” floats defined by the <i>float</i> or other packages). <ul> -<li> Do your figures need to float at all? If not, consider the - <code>[H]</code> placement option offered by the <i>float</i> package: - figures with this placement are made up to look as if they’re - floating, but they don’t in fact float. Beware outstanding floats, - though: the <code>\</code><code>caption</code> commands are numbered in the order they - appear in the document, and a <code>[H]</code> float can ‘overtake’ a float - that hasn’t yet been placed, so that figures numbers get out of - order. +<li> Do your figures need to float at all? If not, look at the + recommendations for “<a href="FAQ-figurehere.html">non-floating floats</a>” <li> Are the placement parameters on your figures right? The default (<code>tbp</code>) is reasonable, but you can reasonably change it (for example, to add an <code>h</code>). Whatever you do, <em>don’t</em> @@ -94,5 +88,5 @@ equally well to tables, or to “non-standard” floats defined by the <dt><tt><i>morefloats.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/morefloats.sty">macros/latex/contrib/misc/morefloats.sty</a> <dt><tt><i>placeins.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/placeins.zip">macros/latex/contrib/placeins</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/placeins.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/placeins/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=floats">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=floats</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=floats">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=floats</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-flushboth.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-flushboth.html index b0895f82e77..bef0c5e7501 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-flushboth.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-flushboth.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label flushboth</title> </head><body> <h3>Cancelling <code>\</code><code>ragged</code> commands</h3> -<p>LaTeX provides commands <code>\</code><code>raggedright</code> and <code>\</code><code>raggedleft</code>, but +<p/>LaTeX provides commands <code>\</code><code>raggedright</code> and <code>\</code><code>raggedleft</code>, but none to cancel their effect. The <code>\</code><code>centering</code> command is implemented in the same way as the <code>\</code><code>ragged*</code> commands, and suffers in the same way. -<p>The following code (to be inserted in a package of your own, or as +<p/>The following code (to be inserted in a package of your own, or as <a href="FAQ-atsigns.html">internal LaTeX code</a>) defines a command that restores flush justification at both margins: @@ -23,13 +23,11 @@ zero, but the setting isn’t a constant of nature: documents using a standard LaTeX class with <code>twocolumn</code> option will have <code>1.0em</code> by default, and there’s no knowing what you (or some other class) will have done. -<p>If you are using Martin Schröder’s <i>ragged2e</i> package, it is -worth updating to the latest release (January 2003), which has a -<code>\</code><code>justifying</code> command to match its +<p/>Any but a really old copy of Martin Schröder’s <i>ragged2e</i> +package has a <code>\</code><code>justifying</code> command to match its <a href="FAQ-ragright.html">versions of the LaTeX ‘ragged’ commands</a>. The -package also provides a -<code>justify</code> environment, which permits areas of justified -text in a larger area which is ragged. +package also provides a <code>justify</code> environment, which +permits areas of justified text in a larger area which is ragged. <dl> <dt><tt><i>ragged2e.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse</a>) </dl> @@ -42,5 +40,5 @@ text in a larger area which is ragged. -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=flushboth">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=flushboth</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=flushboth">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=flushboth</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fmtconv.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fmtconv.html index 4889668394e..6d25578742e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fmtconv.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fmtconv.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label fmtconv</title> </head><body> <h3>Other conversions to and from (La)TeX</h3> -<p><dl> +<p/><dl> <dt>troff<dd><i>Tr2latex</i>, assists in the translation of a <i>troff</i> document into LaTeX 2.09 format. It recognises most <code>-ms</code> and <code>-man</code> macros, plus most <i>eqn</i> and some @@ -11,15 +11,15 @@ (which converts very well to LaTeX...). <i>Tr2latex</i> is an enhanced version of the earlier <i>troff-to-latex</i> (which is no longer available). -<p> +<p/> -<p> +<p/> -<p><dt>WordPerfect<dd> <i>wp2latex</i> +<p/><dt>WordPerfect<dd> <i>wp2latex</i> has recently been much improved, and is now available either for MSDOS or for Unix systems, thanks to its current maintainer Jaroslav Fojtik. @@ -41,7 +41,7 @@ The latest converter, by Ujwal Sathyam and Scott Prahl, is <i>rtf2latex2e</i>; this system seems rather good already, and is still being improved. -<p> Translation <em>to</em> RTF may be done (for a somewhat +<p/> Translation <em>to</em> RTF may be done (for a somewhat constrained set of LaTeX documents) by TeX2RTF, which can produce ordinary RTF, Windows Help RTF (as well as HTML, <a href="FAQ-LaTeX2HTML.html">conversion to HTML</a>). @@ -53,11 +53,11 @@ shareware translators from <a href="http://www.chikrii.com/">Chikrii Softlab</a>; users’ reports are very positive. -<p> If cost is a constraint, the best bet is probably to use an +<p/> If cost is a constraint, the best bet is probably to use an intermediate format such as RTF or HTML. <i>Word</i> outputs and reads both, so in principle this route may be useful. -<p> Another, unlikely, intermediate form is PDF: Acrobat Reader +<p/> Another, unlikely, intermediate form is PDF: Acrobat Reader for Windows (version 5.0 and later) will output rather feeble RTF that <i>Word</i> can read. <dt>Excel<dd> <i>Excel2Latex</i> converts an <i>Excel</i> file @@ -65,19 +65,19 @@ <code>.xls</code> file which defines some <i>Excel</i> macros to produce output in a new format. </dl> -<p> +<p/> <a href="http://www.tug.org/utilities/texconv/index.html">Wilfried Hennings’ FAQ</a>, which deals specifically with conversions between TeX-based formats and word processor formats, offers much detail as well as tables that allow quick comparison of features. -<p>A group at Ohio State University (USA) is working on +<p/>A group at Ohio State University (USA) is working on a common document format based on SGML, with the ambition that any format could be translated to or from this one. <i>FrameMaker</i> provides “import filters” to aid translation from alien formats (presumably including TeX) to <i>FrameMaker</i>’s own. <dl> -<dt><tt><i>excel2latex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/excel2latex/xl2latex.zip">support/excel2latex/xl2latex.zip</a> +<dt><tt><i>excel2latex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/excel2latex.zip">support/excel2latex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/excel2latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/excel2latex/">browse</a>) <dt><tt><i>pcwritex.arc</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/pcwritex.zip">support/pcwritex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/pcwritex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/pcwritex/">browse</a>) <dt><tt><i>refer and tib tools</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/refer-tools.zip">biblio/bibtex/utils/refer-tools</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/refer-tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/refer-tools/">browse</a>) <dt><tt><i>rnototex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/rnototex.zip">support/rnototex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/rnototex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/rnototex/">browse</a>) @@ -91,5 +91,5 @@ translated to or from this one. <i>FrameMaker</i> provides <dt><tt><i>Word processor FAQ (source)</i></tt><dd> <a href="ftp://cam.ctan.org/tex-archive/help/wp-conv.zip">help/wp-conv</a> (<a href="ftp://cam.ctan.org/tex-archive/help/wp-conv.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/wp-conv/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fmtconv">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fmtconv</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fmtconv">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fmtconv</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontname.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontname.html index 111a33128a4..0b6f33c0f47 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontname.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontname.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label fontname</title> </head><body> <h3>What is the “Berry naming scheme”</h3> -<p>In the olden days, (La)TeX distributions were limited by the +<p/>In the olden days, (La)TeX distributions were limited by the feebleness of file systems’ ability to represent long names. (The MSDOS file system was a particular bugbear: fortunately any current Microsoft system allows rather more freedom to specify file names. Sadly, the ISO 9660 standard for the structure of CDROMs has a similar failing, but that too has been modified by various extension mechanisms.) -<p>One area in which this was a particular problem was that of file names +<p/>One area in which this was a particular problem was that of file names for Type 1 fonts. These fonts are distributed by their vendors with pretty meaningless short names, and there’s a natural ambition to change the name to something that identifies the font somewhat @@ -17,10 +17,10 @@ precisely. Unfortunately, names such as “BaskervilleMT” are already far beyond the abilities of the typical feeble file system, and add the specifier of a font shape or variant, and the difficulties spiral out of control. -<p>Thus arose the Berry naming scheme. -<p>The basis of the scheme is to encode the meanings of the various parts +<p/>Thus arose the Berry naming scheme. +<p/>The basis of the scheme is to encode the meanings of the various parts of the file’s specification in an extremely terse way, so that enough -font names can be expressed even in impoverished file spaces. The +font names can be expressed even in impoverished file name-spaces. The encoding allocates one letter to the font “foundry”, two to the typeface name, one to the weight, and so on. The whole scheme is outlined in the <i>fontname</i> distribution, which includes @@ -29,6 +29,6 @@ been systematised. <dl> <dt><tt><i>fontname distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/fontname.zip">info/fontname</a> (<a href="ftp://cam.ctan.org/tex-archive/info/fontname.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/fontname/">browse</a>) </dl> -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontname">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontname</a> +<p/> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontname">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontname</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fonts-pln.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fonts-pln.html index 6ebd65d03eb..072bd278a78 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fonts-pln.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fonts-pln.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label fonts-pln</title> </head><body> <h3>Using non-standard fonts in Plain TeX</h3> -<p>Plain TeX (in accordance with its description) doesn’t do anything +<p/>Plain TeX (in accordance with its description) doesn’t do anything fancy with fonts: it sets up the fonts that Knuth found he needed when writing the package, and leaves you to do the rest. -<p>To use something other than Knuth’s default, the default mechanism is +<p/>To use something other than Knuth’s default, the default mechanism is to use the <code>\</code><code>font</code> primitive: <blockquote> <pre> @@ -17,7 +17,7 @@ Text set using nonstdfont ... </blockquote><p> The name you use (<code>nonstdfont</code>, above) is the name of the <code>.tfm</code> file for the font you want. -<p>If you want to use an italic version of <code>\</code><code>foo</code>, you need to use +<p/>If you want to use an italic version of <code>\</code><code>foo</code>, you need to use <code>\</code><code>font</code> again: <blockquote> <pre> @@ -27,7 +27,7 @@ The name you use (<code>nonstdfont</code>, above) is the name of the Text set using nonstdfont italic... </pre> </blockquote><p> -<p>This is all very elementary stuff, and serves for simple use of fonts. +<p/>This is all very elementary stuff, and serves for simple use of fonts. However, there are wrinkles, the most important of which is the matter of <a href="FAQ-whatenc.html">font encodings</a>. Unfortunately, many fonts that have appeared recently simply don’t come in versions using Knuth’s @@ -38,29 +38,29 @@ selection scheme” — this ‘NFSS’ (‘N’ for &ls opposed to what LaTeX 2.09 had) carries around with it separate information about the fonts you use, so the changes to encoding-specific commands happen automagically. -<p>If you only want to use the <a href="FAQ-ECfonts.html">EC fonts</a>, you +<p/>If you only want to use the <a href="FAQ-ECfonts.html">EC fonts</a>, you can in principle use the <i>ec-plain</i> bundle, which gives you a version of Plain TeX which you can run in the same way that you run Plain TeX using the original CM fonts, by invoking <i>tex</i>. (<i>Ec-plain</i> also extends the EC fonts, for reasons which aren’t immediately clear, but which might cause problems if you’re hoping to use Type 1 versions of the fonts.) -<p>The <i>font_selection</i> package provides a sort of halfway house: +<p/>The <i>font_selection</i> package provides a sort of halfway house: it provides font face and size, but not family selection. This gives you considerable freedom, but leaves you stuck with the original CM fonts. It’s a compact solution, within its restrictions. -<p>Other Plain TeX approaches to the problem (packages +<p/>Other Plain TeX approaches to the problem (packages <i>plnfss</i>, <i>fontch</i> and <i>ofs</i>) break out of the Plain TeX model, towards the sort of font selection provided by ConTeXt and LaTeX — font selection that allows you to change family, as well as size and face. The remaining packages all make provision for using encodings other than Knuth’s OT1. -<p><i>Plnfss</i> has a rather basic set of font family details; +<p/><i>Plnfss</i> has a rather basic set of font family details; however, it is capable of using font description (<code>.fd</code>) files created for LaTeX. (This is useful, since most modern mechanisms for integrating outline fonts with TeX generate <code>.fd</code> files in their process.) -<p><i>Fontch</i> has special provision for T1 and TS1 +<p/><i>Fontch</i> has special provision for T1 and TS1 encodings, which you select by arcane commands, such as: <blockquote> <pre> @@ -69,18 +69,28 @@ encodings, which you select by arcane commands, such as: </pre> </blockquote><p> for T1. -<p><i>Ofs</i> seems to be the most thoroughly thought-through of the +<p/><i>Ofs</i> seems to be the most thoroughly thought-through of the alternatives, and can select more than one encoding: as well as T1 it covers the encoding IL2, which is favoured in the Czech Republic and Slovakia. <i>Ofs</i> also covers mathematical fonts, allowing you the dubious pleasure of using fonts such as the <a href="FAQ-psfchoice.html"><i>pxfonts</i> and <i>txfonts</i></a>. +<p/>The <i>pdcmac</i> Plain TeX macro package aims to be a complete +document preparation environment, like <a href="FAQ-eplain.html">Eplain</a>. One +of its components is a font selection scheme, <i>pdcfsel</i>, which +is rather simple but adequately powerful for many uses. The package +doesn’t preload fonts: the user is required to declare the fonts the +document is going to use, and the package provides commands to select +fonts as they’re needed. The distribution includes a configuration to +use Adobe ‘standard’ fonts for typesetting text. (Eplain itself +seems not to offer a font selection scheme.) <dl> <dt><tt><i>ec-plain</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/ec-plain.zip">macros/ec-plain</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/ec-plain.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/ec-plain/">browse</a>) <dt><tt><i>fontch</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/fontch.zip">macros/plain/contrib/fontch</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/fontch.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/fontch/">browse</a>) <dt><tt><i>font_selection</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/font_selection.zip">macros/plain/contrib/font_selection</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/font_selection.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/font_selection/">browse</a>) <dt><tt><i>ofs</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/ofs.zip">macros/generic/ofs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/generic/ofs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/generic/ofs/">browse</a>) +<dt><tt><i>pdcmac</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/pdcmac.zip">macros/plain/contrib/pdcmac</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/pdcmac.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/pdcmac/">browse</a>) <dt><tt><i>plnfss</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/plnfss/">macros/plain/contrib/plnfss/</a> </dl> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fonts-pln">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fonts-pln</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fonts-pln">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fonts-pln</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontsize.html index 0feb24ebd15..73a6e47094e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfont.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontsize.html @@ -1,31 +1,28 @@ <head> -<title>UK TeX FAQ -- question label newfont</title> +<title>UK TeX FAQ -- question label fontsize</title> </head><body> -<h3>What’s wrong with <code>\</code><code>newfont</code>?</h3> -<p>If all else fails, you <em>can</em> specify a font using the LaTeX -<code>\</code><code>newfont</code> command. The font so specified doesn’t fit into the -LaTeX font selection mechanism, but the technique can be tempting -under several circumstances. The command is merely the thinnest of -wrappers around the <code>\</code><code>font</code> primitive, and suffers from exactly the -problems with font encodings and sizes that are outlined in -<a href="FAQ-plninltx.html">using Plain TeX commands in \LaTeX</a>. -<p>Almost all fonts, nowadays, are provided with LaTeX control files -(if they’re adapted to TeX at all). There is therefore little gain -in using <code>\</code><code>newfont</code>. -<p>One temptation arises from the way that LaTeX restricts the sizes -of fonts. In fact, this restriction only significantly applies to the -default (Computer Modern) and the Cork-encoded (T1) EC fonts, but it -is widely considered to be anomalous, nowadays. In recognition of -this problem, there is a package <i>fix-cm</i> which will allow you -to use the fonts, within LaTeX, at any size you choose. If you’re -not using scaleable versions of the fonts, most modern distributions -will just generate an appropriate bitmap for you. -<p>So, suppose you want to use Computer Modern Roman at 30 points, you +<h3>Fonts at arbitrary sizes</h3> +<p/>Almost all fonts, nowadays, are provided with LaTeX control +(<code>.fd</code>) files, so the temptation to risk the +<a href="FAQ-newfontstar.html">problems of <code>\</code><code>newfont</code></a> is usually easy to +resist. +<p/>However, one temptation remains, arising from the way that LaTeX +restricts the sizes of fonts. In fact, the restriction only +significantly applies to the default (Computer Modern) and the +Cork-encoded (T1) EC fonts, but it is widely considered to be +anomalous, nowadays. In recognition of this problem, there is a +package <i>fix-cm</i> which will allow you to use the fonts, within +LaTeX, at any size you choose. If you’re not using scaleable +versions of the fonts, most modern distributions will just generate an +appropriate bitmap for you. +<p/>So, suppose you want to use Computer Modern Roman at 30 points, you might be tempted to write: <blockquote> <pre> \newfont{\bigfont}{cmr10 at 30pt} -{\bigfont Huge text} +\begin{center} + \bigfont Huge text +\end{center} </pre> </blockquote><p> which will indeed work, but will actually produce a worse result than @@ -33,10 +30,10 @@ which will indeed work, but will actually produce a worse result than <pre> \usepackage{fix-cm} ... -{% +\begin{center} \fontsize{30}{36}\selectfont - Huge text% -} + Huge text +\end{center} </pre> </blockquote><p> Note that the <i>fix-cm</i> package was not distributed until the @@ -51,7 +48,5 @@ the packages <i>type1cm</i> (for CM fonts) and the <a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.zip">fonts/ps-type1/cm-super</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super/">browse</a>) distribution, but it works happily in the absence of the scaled fonts) </dl> -<p> -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfont</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontsize">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontsize</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontunavail.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontunavail.html index 3f27b955bc4..b14b1e7e089 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontunavail.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fontunavail.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label fontunavail</title> </head><body> <h3>Warning: “Font shape ... not available”</h3> -<p>LaTeX’s font selection scheme maintains tables of the font families +<p/>LaTeX’s font selection scheme maintains tables of the font families it has been told about. These tables list the font families that LaTeX knows about, and the shapes and series in which those font families are available. In addition, in some cases, the tables list the sizes at which LaTeX is willing to load fonts from the family. -<p>When you specify a font, using one of the LaTeX font selection +<p/>When you specify a font, using one of the LaTeX font selection commands, LaTeX looks for the font (that is, a font that matches the encoding, family, shape, series and size that you want) in its tables. If the font isn’t there at the size you want, you will see a @@ -24,7 +24,7 @@ LaTeX Font Warning: Size substitutions with differences (Font) up to 0.5pt have occurred. </pre> after LaTeX has encountered <code>\</code><code>end{document}</code>. -<p>The message tells you that you’ve chosen a font size that is not in +<p/>The message tells you that you’ve chosen a font size that is not in LaTeX’s list of “allowed” sizes for this font; LaTeX has chosen the nearest font size it knows is allowed. In fact, you can tell LaTeX to allow <em>any</em> size: the restrictions come from the @@ -35,7 +35,7 @@ available in scaleable (Adobe Type 1) form. If your installation uses scaleable versions of the Computer Modern or European Computer Modern (EC) fonts, you can tell LaTeX to remove the restrictions; use the <i>type1cm</i> or <i>type1ec</i> package as appropriate. -<p>If the combination of font shape and series isn’t available, LaTeX +<p/>If the combination of font shape and series isn’t available, LaTeX will usually have been told of a fall-back combination that may be used, and will select that: @@ -43,7 +43,7 @@ used, and will select that: LaTeX Font Warning: Font shape `OT1/cmr/bx/sc' undefined (Font) using `OT1/cmr/bx/n' instead on input line 0. </pre> -<p>Substitutions may also be “silent”; in this case, there is no more +<p/>Substitutions may also be “silent”; in this case, there is no more than an “information” message in the log file. For example, if you specify an encoding for which there is no version in the current font family, the ‘default family for the encoding’ is selected. This @@ -55,7 +55,7 @@ encoding. My test log contained: LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10> not available (Font) Font shape `OMS/cmsy/m/n' tried instead on input line ... </pre> -<p>In summary, these messages are not so much error messages, as +<p/>In summary, these messages are not so much error messages, as information messages, that tell you what LaTeX has made of your text. You should check what the messages say, but you will ordinarily not be surprised at their content. @@ -63,5 +63,5 @@ not be surprised at their content. <dt><tt><i>type1cm.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/type1cm.zip">macros/latex/contrib/type1cm</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/type1cm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/type1cm/">browse</a>) <dt><tt><i>type1ec.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super/type1ec.sty">fonts/ps-type1/cm-super/type1ec.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontunavail">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontunavail</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontunavail">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fontunavail</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footintab.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footintab.html index 8d579563b7d..12c4bd7e3be 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footintab.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footintab.html @@ -2,20 +2,20 @@ <title>UK TeX FAQ -- question label footintab</title> </head><body> <h3>Footnotes in tables</h3> -<p>The standard LaTeX <code>\</code><code>footnote</code> command doesn’t work in tables; the table +<p/>The standard LaTeX <code>\</code><code>footnote</code> command doesn’t work in tables; the table traps the footnotes and they can’t escape to the bottom of the page. -<p>If your table is floating, your best bet is (unfortunately) to put the +<p/>If your table is floating, your best bet is (unfortunately) to put the table in a <code>minipage</code> environment and to put the notes underneath the table, or to use Donald Arseneau’s package <i>threeparttable</i> (which implements “table notes” proper). -<p>The <i>ctable</i> package extends the model of +<p/>The <i>ctable</i> package extends the model of <i>threeparttable</i>, and also uses the ideas of the <i>booktabs</i> package. The <code>\</code><code>ctable</code> command does the complete job of setting the table, placing the caption, and defining the notes. The “table” may consist of diagrams, and a parameter in <code>\</code><code>ctable</code>’s optional argument makes the float that is created a “figure” rather than a “table”. -<p>Otherwise, if your table is not floating (it’s just a +<p/>Otherwise, if your table is not floating (it’s just a ‘<code>tabular</code>’ in the middle of some text), there are several things you can do to fix the problem. <ul> @@ -44,7 +44,7 @@ things you can do to fix the problem. the standard ‘tools’ ones, though) to become very unhappy and stop working. </ul> -<p>The documentation of <i>threeparttable</i> appears in the package +<p/>The documentation of <i>threeparttable</i> appears in the package file itself; that of <i>ctable</i> is distributed as a PDF file (for convenience’s sake). <dl> @@ -55,5 +55,5 @@ file (for convenience’s sake). <dt><tt><i>threeparttable.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/threeparttable.sty">macros/latex/contrib/misc/threeparttable.sty</a> <dt><tt><i>tabularx.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footintab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footintab</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footintab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footintab</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footnpp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footnpp.html index 3a52cc32570..9e16888977f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footnpp.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-footnpp.html @@ -2,36 +2,36 @@ <title>UK TeX FAQ -- question label footnpp</title> </head><body> <h3>Footnotes numbered “per page”</h3> -<p>The obvious solution is to make the footnote number reset whenever the +<p/>The obvious solution is to make the footnote number reset whenever the page number is stepped, using the <a href="FAQ-addtoreset.html">LaTeX internal mechanism</a>. Sadly, the place in the document where the page number is stepped is unpredictable, not (“tidily”) at the end of the printed page; so the link only ever works by luck. -<p>As a result, resetting footnotes is inevitably a two-pass process, +<p/>As a result, resetting footnotes is inevitably a two-pass process, using labels of some sort. It’s nevertheless important, given the common requirement for footnotes marked by symbols (with painfully small symbol sets). There are three packages that manage it, one way or another. -<p>The <i>footnpag</i> package does per-page footnotes and nothing +<p/>The <i>footnpag</i> package does per-page footnotes and nothing else. -<p>The <i>perpage</i> package provides a general mechanism for +<p/>The <i>perpage</i> package provides a general mechanism for resetting counters per page, so can obviously be used for this task. The interface is pretty simple: <code>\</code><code>MakePerPage{footnote}</code> will do the job. If you want to restart the counter at something other than 1 (for example to avoid something in the LaTeX footnote symbol list), you can use: <code>\</code><code>MakePerPage[2]{footnote}</code>. -<p>The <i>footmisc</i> package provides a variety of means of +<p/>The <i>footmisc</i> package provides a variety of means of controlling footnote appearance, among them a package option <code>perpage</code> that adjusts the numbering per page. -<p>Documentation of <i>footnpag</i> comes as a DVI file +<p/>Documentation of <i>footnpag</i> comes as a DVI file <i>footnpag-user</i> in the distribution. Documentation of <i>perpage</i> appears in the package file, only: however, it -amounts to no more than appears above\dots +amounts to no more than appears above... <dl> <dt><tt><i>footmisc.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.zip">macros/latex/contrib/footmisc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footmisc/">browse</a>) <dt><tt><i>footnpag.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footnpag.zip">macros/latex/contrib/footnpag</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footnpag.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footnpag/">browse</a>) <dt><tt><i>perpage.sty</i></tt><dd>Distributed as part <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse</a>) </dl> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footnpp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footnpp</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footnpp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=footnpp</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-formatstymy.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-formatstymy.html index ba72434a0aa..46463ed2b18 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-formatstymy.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-formatstymy.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label formatstymy</title> </head><body> <h3>“Fatal format file error; I’m stymied”</h3> -<p>(La)TeX applications often fail with this error when you’ve been +<p/>(La)TeX applications often fail with this error when you’ve been playing with the configuration, or have just installed a new version. -<p>The format file contains the macros that define the system you want to +<p/>The format file contains the macros that define the system you want to use: anything from the simplest (Plain TeX) all the way to the most complicated, such as LaTeX or ConTeXt. From the command you issue, TeX knows which format you want. -<p>The error message +<p/>The error message <pre> Fatal format file error; I'm stymied </pre> @@ -20,7 +20,7 @@ same machine can understand each other’s formats. So the new version of TeX you have just installed, won’t understand the format generated by the one you installed last year. -<p>Resolve the problem by regenerating the format; of course, this +<p/>Resolve the problem by regenerating the format; of course, this depends on which system you are using. <ul> <li> On a teTeX-based system, run @@ -38,5 +38,5 @@ depends on which system you are using. <code>MiKTeX Options</code>, and in the options window, click <code>Update now</code>. </ul> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=formatstymy">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=formatstymy</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=formatstymy">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=formatstymy</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-formbiblabel.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-formbiblabel.html index a79ff3a2684..aa9b41b0c40 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-formbiblabel.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-formbiblabel.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label formbiblabel</title> </head><body> <h3>Format of numbers in the bibliography</h3> -<p>By default, LaTeX makes entries in the bibliography look like: +<p/>By default, LaTeX makes entries in the bibliography look like: <blockquote> [1] Doe, Joe et al. Some journal. 2004.<br> [2] Doe, Jane et al. Some journal. 2003. @@ -12,7 +12,7 @@ while many documents need something like: 1. Doe, Joe et al. Some journal. 2004.<br> 2. Doe, Jane et al. Some journal. 2003. </blockquote><p> -<p>This sort of change may be achieved by many of the “general” +<p/>This sort of change may be achieved by many of the “general” citation packages; for example, in <i>natbib</i>, it’s as simple as: <blockquote> <pre> @@ -31,5 +31,5 @@ LaTeX commands, in the preamble of your document, will do the job: <dl> <dt><tt><i>natbib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.zip">macros/latex/contrib/natbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/natbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/natbib/">browse</a>) </dl> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=formbiblabel">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=formbiblabel</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=formbiblabel">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=formbiblabel</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftncapt.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftncapt.html index 53117549237..f02c5ebd728 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftncapt.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftncapt.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label ftncapt</title> </head><body> <h3>Footnotes in captions</h3> -<p>Footnotes in captions are especially tricky: they present problems of +<p/>Footnotes in captions are especially tricky: they present problems of their own, on top of the problems one experiences with <a href="FAQ-ftnsect.html">footnotes in section titles</a> and with <a href="FAQ-footintab.html">footnotes in tables</a>. Fortunately, the @@ -13,7 +13,7 @@ scheme (see, again, <a href="FAQ-footintab.html">footnotes in tables</a>) also applies to notes in captions, and may very well be preferable to whatever you were thinking of. -<p>If you <em>are</em> going to proceed: +<p/>If you <em>are</em> going to proceed: <ul> <li> use an optional argument in your <code>\</code><code>caption</code> command, that doesn’t have the footnote in it; this prevents the footnote @@ -37,17 +37,17 @@ However, <em>as well as</em> all of the above, one <em>also</em> has to deal with the tendency of the <code>\</code><code>caption</code> command to produce the footnote’s text twice. For this last problem, there is no tidy solution this author is aware of. -<p>If you’re suffering the problem, a well-constructed <code>\</code><code>caption</code> +<p/>If you’re suffering the problem, a well-constructed <code>\</code><code>caption</code> command in a <code>minipage</code> environment within a float (as in the example above) can produce <em>two</em> copies of the footnote body “blah”. (In fact, the effect only occurs with captions that are long enough to require two lines to be typeset, and so wouldn’t appear with such a short caption.) -<p>The documentation of the <i>ccaption</i> package describes a really +<p/>The documentation of the <i>ccaption</i> package describes a really rather awful work-around. <dl> <dt><tt><i>ccaption.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ccaption.zip">macros/latex/contrib/ccaption</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ccaption.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ccaption/">browse</a>) <dt><tt><i>threeparttable.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/threeparttable.sty">macros/latex/contrib/misc/threeparttable.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ftncapt">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ftncapt</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ftncapt">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ftncapt</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftnsect.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftnsect.html index e66e1695c4a..b014c32a9ba 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftnsect.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ftnsect.html @@ -2,25 +2,35 @@ <title>UK TeX FAQ -- question label ftnsect</title> </head><body> <h3>Footnotes in LaTeX section headings</h3> -<p>The <code>\</code><code>footnote</code> command is fragile, so that simply placing the +<p/>The <code>\</code><code>footnote</code> command is fragile, so that simply placing the command in <code>\</code><code>section</code>’s arguments isn’t satisfactory. Using <code>\</code><code>protect</code><code>\</code><code>footnote</code> isn’t a good idea either: the arguments of a section command are used in the table of contents and (more -dangerously) potentially also in page headings. Unfortunately, -there’s no mechanism to suppress the footnote in the heading while -allowing it in the table of contents, though having footnotes in the -table of contents is probably unsatisfactory anyway. -<p>To suppress the footnote in headings and table of contents: +dangerously) potentially also in page headers. While footnotes will +work in the table of contents, it’s generally not thought a “good +thing” to have them there; in the page header, footnotes will simply +fail. Whatever the desirability of the matter, there’s no mechanism +to suppress the footnote in the page header while allowing it in the table +of contents, so the footnote may only appear in the section heading itself. +<p/>To suppress the footnote in headings and table of contents: <ul> <li> Take advantage of the fact that the mandatory argument doesn’t ‘move’ if the optional argument is present: - <code>\section[title]{title</code><code>\</code><code>footnote</code><code>{title ftnt}}</code> +<p/> <code>\section[title]{title</code><code>\</code><code>footnote{title ftnt}</code><code>}</code> <li> Use the <i>footmisc</i> package, with package option <code>stable</code> — this modifies footnotes so that they softly and - silently vanish away if used in a moving argument. + silently vanish away if used in a moving argument. With this, you + simply need: +<pre> +% in the document preamble +\usepackage[stable]{footmisc} +... +% in the body of the document +\section{title\footnote{title ftnt}} +</pre> </ul> <dl> <dt><tt><i>footmisc.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.zip">macros/latex/contrib/footmisc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footmisc/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ftnsect">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ftnsect</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ftnsect">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ftnsect</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-T1.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-T1.html index 1e665e46980..3c65b2248d0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-T1.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-T1.html @@ -3,13 +3,13 @@ </head><body> <h3>Fonts go fuzzy when you switch to T1</h3> <!-- crippled blurry --> -<p>You’ve been having problems with hyphenation, and someone has +<p/>You’ve been having problems with hyphenation, and someone has suggested that you should use “<code>\</code><code>usepackage[T1]{fontenc}</code>” to help sort them out. Suddenly you find that your final PDF has become fuzzy. The problem may arise whether you are using PostScript output and then distilling it, or you are using PDFTeX for the whole job. -<p>In fact, this is the same problem as most others about the +<p/>In fact, this is the same problem as most others about the <a href="FAQ-dvips-pdf.html">quality of PDF</a>: you’ve abandoned your previous setup using Type 1 versions of the CM fonts, and <i>dvips</i> has inserted Type 3 versions of the EC fonts @@ -18,17 +18,17 @@ into your document output. (See for details of these font types; also, note that the font <em>encoding</em> T1 has nothing directly to do with the font <em>format</em> Type 1). -<p>However, as noted in +<p/>However, as noted in “<a href="FAQ-type1T1.html">8-bit Type 1 fonts</a>”, Type 1 versions of CM-like fonts in T1 (or equivalent) encoding are now available, both as “real” fonts, and as virtual font sets. One solution, therefore, is to use one of these alternatives. -<p>The alternative is to switch font family altogether, to something like +<p/>The alternative is to switch font family altogether, to something like <i>Times</i> (as a no-thought default) or one of the many more pleasing Adobe-encoded fonts. The default action of <i>fontinst</i>, when creating metrics for such a font, is to create settings for both OT1 and T1 encodings, so there’s little change in what goes on (at the user level) even if you have switched to T1 encoding when using the fonts. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-T1">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-T1</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-T1">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-T1</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-gs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-gs.html index f3231fa2a9b..848da58ff4f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-gs.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-gs.html @@ -3,11 +3,11 @@ </head><body> <h3>Fuzzy fonts because <i>Ghostscript</i> too old</h3> <!-- crippled blurry --> -<p>So you’ve done everything the FAQ has told you that you need, +<p/>So you’ve done everything the FAQ has told you that you need, correct fonts properly installed and appearing in the <i>dvips</i> output, but <em>still</em> you get fuzzy character output after distilling with <i>ghostscript</i>. -<p>The problem could arise from too old a version of +<p/>The problem could arise from too old a version of <i>ghostscript</i>, which you may be using directly, or via a script such as <i>ps2pdf</i> (distributed with <i>ghostscript</i> itself), <i>dvipdf</i>, or similar. @@ -17,10 +17,10 @@ any font other than the fundamental 35 fonts (<i>Times</i>, <i>Helvetica</i>, etc.). Later versions added ‘complete’ distillation, but it wasn’t until version 6.50 that one could rely on it for everyday work. -<p>So, if your PDF output still looks fuzzy in <i>Acrobat</i> +<p/>So, if your PDF output still looks fuzzy in <i>Acrobat</i> <i>Reader</i>, upgrade <i>ghostscript</i>. The new version should be at least version 6.50, of course, but it’s usually good policy to go to the most recent version (version 8.12 at the time of writing — 2003). -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-gs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-gs</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-gs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-gs</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-type3.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-type3.html index d4c8472b683..043e7fb8fb9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-type3.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-type3.html @@ -3,14 +3,14 @@ </head><body> <h3>The wrong type of fonts in PDF</h3> <!-- crippled blurry --> -<p>This is far the commonest problem: the symptom is that text in the +<p/>This is far the commonest problem: the symptom is that text in the document looks “fuzzy”. -<p>Most people use <i>Adobe</i> <i>Acrobat</i> <i>Reader</i> +<p/>Most people use <i>Adobe</i> <i>Acrobat</i> <i>Reader</i> to view their PDF: <i>Reader</i> is distributed free of charge, and is widely available, for all its faults. One of those faults is its failure to deal with bitmap fonts (at least, in all versions earlier than the recently released version 6). -<p>So we don’t want bitmap fonts in our PostScript: with them, characters show +<p/>So we don’t want bitmap fonts in our PostScript: with them, characters show up in <i>Reader</i>’s display as blurred blobs which are often not recognisable as the original letter, and are often not properly placed on the line. Nevertheless, even now, most TeX systems have @@ -18,23 +18,23 @@ on the line. Nevertheless, even now, most TeX systems have <a href="FAQ-pk.html"><code>.pk</code> files</a> in its output. Even PDFTeX will use <code>.pk</code> files if it can see no alternative for a font in the document it is processing. -<p>Our remedy is to use +<p/>Our remedy is to use “<a href="FAQ-adobetypen.html">Adobe Type 1</a>” versions of the fonts we need. Since Adobe are in the business of selling Type 1 fonts, <i>Reader</i> was of course made to deal with them really rather well, from the very beginning. -<p>Of course, if your document uses nothing but fonts that came from +<p/>Of course, if your document uses nothing but fonts that came from Adobe in the first place — fonts such as <i>Times</i> that appear in pretty much every PostScript printer, or such as Adobe <i>Sabon</i> that you pay extra for — then there’s no problem. -<p>But most people use <i>Computer</i> <i>Modern</i> to start +<p/>But most people use <i>Computer</i> <i>Modern</i> to start with, and even those relative sophisticates who use something as exotic as <i>Sabon</i> often find themselves using odd characters from CM without really intending to do so. Fortunately, rather good versions of the CM fonts are available from the AMS (who have them courtesy of <a href="FAQ-commercial.html">Blue Sky Research</a> and Y&Y). -<p>Most modern systems have the fonts installed ready to use; and any +<p/>Most modern systems have the fonts installed ready to use; and any system installed less than 3 years ago has a <i>dvips</i> configuration file ‘<code>pdf</code>’ that signals the use of the CM fonts, and also sets a few other parameters to improve @@ -53,15 +53,15 @@ or something similar, or about failing to find a font file: </pre> Either of these failures signals that your system doesn’t have the fonts in the first place. -<p>A way of using the fonts that doesn’t involve the sophistication of +<p/>A way of using the fonts that doesn’t involve the sophistication of the <code>-Ppdf</code> mechanism is simply to load maps: <pre> dvips -Pcmz -Pamz myfile -o myfile.ps </pre> You may encounter the same warning messages as listed above. -<p>If your system does not have the fonts, it won’t have the +<p/>If your system does not have the fonts, it won’t have the configuration file either; however, it might have the configuration file without the fonts. In either case, you need to <a href="FAQ-inst1cm.html">install the fonts</a>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-type3">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-type3</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-type3">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-type3</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-getbitmap.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-getbitmap.html index 3eaa08ea12c..1de7abe52c5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-getbitmap.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-getbitmap.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label getbitmap</title> </head><body> <h3>Acquiring bitmap fonts</h3> -<p>When CTAN was young, most people would start using TeX +<p/>When CTAN was young, most people would start using TeX with a 300 dots-per-inch (dpi) laser printer, and sets of Computer Modern bitmap fonts for this resolution are available on CTAN. (There are separate sets for write-black and write-white printers, as well as sets at 120 dpi and 240 dpi.) -<p>Over the years, there have been regular requests that CTAN should hold +<p/>Over the years, there have been regular requests that CTAN should hold a wider range of resolutions, but they were resisted for two reasons: <ul> <li> The need to decide which printers to generate fonts for. The @@ -22,27 +22,35 @@ arguments: most (if not all) current distributions generate bitmap fonts as needed, and cache them for later re-use. The impatient user, who is determined that all bitmap fonts should be created once and for all, may be supported by scripts such as <i>allcm</i> -(distributed with teTeX, at least; otherwise such a person should -consult <a href="FAQ-useMF.html">"the use of Metafont"</a>). -<p>If your output is to a PostScript-capable device, you advised to switch to +(distributed with TeX-live, at least; otherwise such a +person should consult “<a href="FAQ-useMF.html">the use of Metafont</a>)”. +<p/>If your output is to a PostScript-capable device, or if your output is +destined to be converted to PDF, you should switch to using Type 1 versions of the CM fonts. Two free -sets are currently available; the older (<i>bakoma</i>) is +sets are available; the older (<i>bakoma</i>) is somewhat less well produced than the <i>bluesky</i> fonts, which were originally professionally produced and sold, but were then donated to the public domain by their originators Y&Y and Bluesky Research, -in association with the AMS. Unfortunately, the coverage of -the sets is slightly different, but you are advised to use the +in association with the AMS. The two sets contain slightly +different ranges of fonts, but you are advised to use the <i>bluesky</i> set except when <i>bakoma</i> is for some reason absolutely unavoidable. In recent years, several other ‘Metafont’ fonts have been converted to Type 1 format; it’s common never to need to generate bitmap fonts for any purpose other than previewing (see -<a href="FAQ-PSpreview.html">“previewing documents with Type 1 fonts”</a>). +<a href="FAQ-PSpreview.html">“previewing documents with Type 1 fonts”</a>), +if even then. +<p/>More modern fonts may be used in place of the Computer Modern set. The +<a href="FAQ-ECfonts.html">EC fonts</a> and the +<a href="FAQ-uselmfonts.html">Latin Modern fonts</a> are both close relatives of +Computer Modern with wider ranges of glyphs to offer. <dl> -<dt><tt><i>bakoma</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/ps-type1/bakoma.zip">fonts/cm/ps-type1/bakoma</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/cm/ps-type1/bakoma.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/ps-type1/bakoma/">browse</a>) -<dt><tt><i>bluesky</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/ps-type1/bluesky/">fonts/cm/ps-type1/bluesky/</a> -<dt><tt><i>cm fonts (write-black printers)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/pk/pk300.zip">fonts/cm/pk/pk300.zip</a> -<dt><tt><i>cm fonts (write-white printers)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/pk/pk300w.zip">fonts/cm/pk/pk300w.zip</a> +<dt><tt><i>BaKoMa fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/ps-type1/bakoma.zip">fonts/cm/ps-type1/bakoma</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/cm/ps-type1/bakoma.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/ps-type1/bakoma/">browse</a>) +<dt><tt><i>Bluesky fonts</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/ps-type1/bluesky/">fonts/cm/ps-type1/bluesky/</a> +<dt><tt><i>CM fonts (write-black printers)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/pk/pk300.zip">fonts/cm/pk/pk300.zip</a> +<dt><tt><i>CM fonts (write-white printers)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/pk/pk300w.zip">fonts/cm/pk/pk300w.zip</a> +<dt><tt><i>EC fonts (Type 1 format)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.zip">fonts/ps-type1/cm-super</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super/">browse</a>) +<dt><tt><i>Latin Modern fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/lm.zip">fonts/lm</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/lm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/lm/">browse</a>) </dl> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=getbitmap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=getbitmap</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=getbitmap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=getbitmap</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gethelp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gethelp.html index 8f0b2c4d907..305e3615654 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gethelp.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gethelp.html @@ -2,26 +2,29 @@ <title>UK TeX FAQ -- question label gethelp</title> </head><body> <h3>How to get help</h3> -<p>So you’ve looked at all relevant <a href="FAQ-whereFAQ.html">FAQs</a> you +<p/>So you’ve looked at all relevant <a href="FAQ-whereFAQ.html">FAQs</a> you can find, you’ve looked in any <a href="FAQ-books.html">books</a> you have, and scanned relevant <a href="FAQ-tutorialstar.html">tutorials</a>... and still you don’t know what to do. -<p> If you are seeking a particular package or program, look on your own +<p/>If you are seeking a particular package or program, look on your own system first: you might already have it — the better TeX distributions contain a wide range of supporting material. The CTAN Catalogue can also help: you can <a href="http://www.tex.ac.uk/search">search it</a>, or you can browse it -“<a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/bytopic.html">by topic</a>”. -A catalogue entry has a description of the package, and links to any -documentation known on the net. ... when the entry is up-to-date. -<p>Failing all that, look to see if anyone else has had the problem +“<a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/bytopic.html">by topic</a>”. +A catalogue entry has a brief description of the package, and links to +any known documentation on the net. In fact, a large proportion of +CTAN package directoris now include documentation, so it’s +often worth looking at the catalogue entry for a package you’re considering +using. +<p/>Failing all that, look to see if anyone else has had the problem before; there are two places where people ask: browse or search the newsgroup <i>comp.text.tex</i> via <a href="http://groups.google.com/group/comp.text.tex">Google groups</a>, and the mailing list <code>texhax</code> via its <a href="http://tug.org/pipermail/texhax/">archive</a> -<p>If those “back question” searches fail, you’ll have to ask the world +<p/>If those “back question” searches fail, you’ll have to ask the world at large. To ask a question on <i>comp.text.tex</i>, you can use your own news client (if you have one), or use the “start a new topic” button on <a href="http://groups.google.com/group/comp.text.tex">http://groups.google.com/group/comp.text.tex</a>. @@ -29,5 +32,10 @@ To ask a question on <code>texhax</code>, you may simply send mail to <a href="mailto:texhax@tug.org"><i>texhax@tug.org</i></a>, but it’s probably better to subscribe to the list (via <a href="http://tug.org/mailman/listinfo/texhax">http://tug.org/mailman/listinfo/texhax</a>) first — not everyone will answer to you as well as to the list. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gethelp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gethelp</a> +<p/>Do <b>not</b> try mailing the +<a href="FAQ-LaTeX3.html">LaTeX project team</a> or the maintainers of these +FAQs for help; while both addresses reach experienced (La)TeX +users, no small group can possibly have expertise in every area of +usage so that the “big” lists are a far better bet. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gethelp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gethelp</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graph-pspdf.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graph-pspdf.html index 1ac43924e3c..9ff4a89bdf6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graph-pspdf.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graph-pspdf.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label graph-pspdf</title> </head><body> <h3>Portable imported graphics</h3> -<p>A regular need is a document to be distributed in more than +<p/>A regular need is a document to be distributed in more than one format: commonly both PostScript and PDF. The following advice is based on a post by one with much experience of dealing with the problem of dealing with EPS graphics in this @@ -31,5 +31,5 @@ case. <i>Dvipdfm</i>’s charms are less than attractive here: the document itself needs to be altered from its default (<i>dvips</i>) state, before <i>dvipdfm</i> will process it. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graph-pspdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graph-pspdf</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graph-pspdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graph-pspdf</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graphicspath.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graphicspath.html index 6dbcff59b82..b0f03e19b76 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graphicspath.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-graphicspath.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label graphicspath</title> </head><body> <h3>Importing graphics from “somewhere else”</h3> -<p>By default, graphics commands like <code>\</code><code>includegraphics</code> look +<p/>By default, graphics commands like <code>\</code><code>includegraphics</code> look “wherever TeX files are found” for the graphic file they’re being asked to use. This can reduce your flexibility if you choose to hold your graphics files in a common directory, away from your (La)TeX sources. -<p>The simplest solution is to patch TeX’s path, by changing the +<p/>The simplest solution is to patch TeX’s path, by changing the default path. On most systems, the default path is taken from the environment variable <code>TEXINPUTS</code>, if it’s present; you can adapt that to take in the path it already has, by setting the variable to @@ -21,10 +21,10 @@ rather than “<code>:</code>”. The “<code>.</code>” is t that the current directory is searched first; the trailing “<code>:</code>” says “patch in the value of <code>TEXINPUTS</code> from your configuration file, here”. -<p>This method has the merit of efficiency ((La)TeX does <em>all</em> of +<p/>This method has the merit of efficiency ((La)TeX does <em>all</em> of the searches, which is quick), but it’s always clumsy and may prove inconvenient to use in Windows setups (at least). -<p>The alternative is to use the <i>graphics</i> package command +<p/>The alternative is to use the <i>graphics</i> package command <code>\</code><code>graphicspath</code>; this command is of course also available to users of the <i>graphicx</i> and the <i>epsfig</i> packages. The syntax of <code>\</code><code>graphicspath</code>’s one argument is slightly odd: it’s a @@ -39,17 +39,17 @@ enclosed in braces. A slightly odd sample, given in the however, if the security checks on your (La)TeX system allow, the path may be anything you choose (rather than strictly relative, like those above); note that the trailing “<code>/</code>” <em>is</em> required. -<p>Be aware that <code>\</code><code>graphicspath</code> does not affect the operations of +<p/>Be aware that <code>\</code><code>graphicspath</code> does not affect the operations of graphics macros other than those from the graphics bundle — in particular, those of the outdated <i>epsf</i> and <i>psfig</i> packages are immune. -<p>The disadvantage of the <code>\</code><code>graphicspath</code> method is inefficiency. The +<p/>The disadvantage of the <code>\</code><code>graphicspath</code> method is inefficiency. The package will call (La)TeX once for each entry in the list, which is itself slows things. More seriously, TeX remembers the file name, thus effectively losing memory, every time it’s asked to look up a file, so a document that uses a huge number of graphical inputs could be embarrassed by lack of memory. -<p>If your document is split into a variety of directories, and each +<p/>If your document is split into a variety of directories, and each directory has its associated graphics, the <i>import</i> package may well be the thing for you; see the discussion in the question “ @@ -59,5 +59,5 @@ in the question “ <dt><tt><i>graphics bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) <dt><tt><i>import.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/import.sty">macros/latex/contrib/misc/import.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graphicspath">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graphicspath</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graphicspath">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=graphicspath</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-grmaxwidth.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-grmaxwidth.html index 271700e262f..06edd868751 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-grmaxwidth.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-grmaxwidth.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label grmaxwidth</title> </head><body> <h3>Limit the width of imported graphics</h3> -<p>Suppose you have graphics which may or may not be able to fit within +<p/>Suppose you have graphics which may or may not be able to fit within the width of the page; if they will fit, you want to set them at their natural size, but otherwise you want to scale the whole picture so that it fits within the page width. -<p>You do this by delving into the innards of the graphics package (which +<p/>You do this by delving into the innards of the graphics package (which of course needs a little LaTeX internals programming): <blockquote> <pre> @@ -24,11 +24,11 @@ of course needs a little LaTeX internals programming): This defines a “variable” width which has the properties you want. Replace <code>\</code><code>linewidth</code> if you have a different constraint on the width of the graphic. -<p>Use the command as follows: +<p/>Use the command as follows: <blockquote> <pre> \includegraphics[width=\maxwidth]{figure} </pre> </blockquote><p> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=grmaxwidth">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=grmaxwidth</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=grmaxwidth">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=grmaxwidth</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gutter.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gutter.html index 34a3c78ad16..05ddfdb9a15 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gutter.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-gutter.html @@ -2,29 +2,29 @@ <title>UK TeX FAQ -- question label gutter</title> </head><body> <h3>Why is the inside margin so narrow?</h3> -<p>If you give the standard classes the <code>twoside</code> option, the +<p/>If you give the standard classes the <code>twoside</code> option, the class sets the margins narrow on the left of odd-numbered pages, and on the right of even-numbered pages. This is often thought to look odd, but it is quite right. -<p>The idea is that the typographic urge for symmetry should also apply +<p/>The idea is that the typographic urge for symmetry should also apply to margins: if you lay an even numbered page to the left of an odd-numbered one, you will see that you’ve three equal chunks of un-printed paper: the left margin of the even page, the right margin of the odd page, and the two abutting margins together. -<p>This is all very fine in the abstract, but in practical book(let) +<p/>This is all very fine in the abstract, but in practical book(let) production it only works “sometimes”. -<p>If your booklet is produced on double-width paper and stapled, the +<p/>If your booklet is produced on double-width paper and stapled, the effect will be good; if your book(let) is produced using a so-called “perfect” binding, the effect will again be good. -<p>However, almost any “quality” book-binder will need some of your +<p/>However, almost any “quality” book-binder will need some of your paper to grab hold of, and a book bound in such a way won’t exhibit the treasured symmetry unless you’ve done something about the margin settings. -<p>The packages recommended in +<p/>The packages recommended in “<a href="FAQ-marginpkgs.html">setting up margins</a>” mostly have provision for a “binding offset” or a “binding correction” — search for “binding” in the manuals (<i>vmargin</i> doesn’t help, here). -<p>If you’re doing the job by hand (see +<p/>If you’re doing the job by hand (see <a href="FAQ-marginmanual.html">manual margin setup</a>), the trick is to calculate your page and margin dimensions as normal, and then: <ul> @@ -40,8 +40,8 @@ which can be achieved by: </blockquote><p> (substituting something sensible like “<code>5mm</code>” for “<code>offset</code>”, above). -<p>The above may not be the best you can do: you may well choose to +<p/>The above may not be the best you can do: you may well choose to change the <code>\</code><code>textwidth</code> in the presence of the binding offset; but the changes do work for constant <code>\</code><code>textwidth</code>. -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gutter">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gutter</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gutter">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=gutter</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hash.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hash.html index 2fda5454772..0d74b368834 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hash.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hash.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label hash</title> </head><body> <h3>Defining macros within macros</h3> -<p>The way to think of this is that <code>##</code> gets replaced by <code>#</code> in just the +<p/>The way to think of this is that <code>##</code> gets replaced by <code>#</code> in just the same way that <code>#1</code> gets replaced by ‘whatever is the first argument’. -<p>So if you define a macro and use it as: +<p/>So if you define a macro and use it as: <blockquote> <pre> \def\a#1{+++#1+++#1+++#1+++} \a{b} @@ -30,8 +30,8 @@ define <code>\</code><code>x</code> to be a macro with one argument, you need to and <code>\</code><code>a{b</code>} will expand to ‘+++b+++<code>\def\x #1{xxx#1}</code>’, because <code>#1</code> gets replaced by ‘b’ and <code>##</code> gets replaced by <code>#</code>. -<p>To nest a definition inside a definition inside a definition then +<p/>To nest a definition inside a definition inside a definition then you need <code>####1</code>, as at each stage <code>##</code> is replaced by <code>#</code>. At the next level you need 8 <code>#</code>s each time, and so on. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hash">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hash</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hash">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hash</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-howmanypp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-howmanypp.html index f418e2e6e68..1ebcaea92f0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-howmanypp.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-howmanypp.html @@ -2,27 +2,27 @@ <title>UK TeX FAQ -- question label howmanypp</title> </head><body> <h3>How many pages are there in my document?</h3> -<p>Simple documents (those that start at page 1, and don’t have any +<p/>Simple documents (those that start at page 1, and don’t have any breaks in their page numbering until their last page) present no problem to the seeker after this truth. The number of pages is reported by the <i>lastpage</i> package in its <code>LastPage</code> label. -<p>For more complicated documents (most obviously, books with frontmatter +<p/>For more complicated documents (most obviously, books with frontmatter in a different series of page numbers) this simple approach will not do. -<p>The <i>count1to</i> package defines a label <code>TotalPages</code>; this is +<p/>The <i>count1to</i> package defines a label <code>TotalPages</code>; this is the value of its copy of <code>\</code><code>count1</code> (a reserved TeX count register) at the end of the document. -<p>Package <i>totpages</i> defines a label <code>TotPages</code>, but it also +<p/>Package <i>totpages</i> defines a label <code>TotPages</code>, but it also makes the register it uses available as a LaTeX counter, <code>TotPages</code>, which you can also reference via <code>\</code><code>theTotPages</code>. Of course, the counter <code>TotPages</code> is asynchronous in the same way that page numbers are, but snapshots may safely be taken in the output routine. -<p>The <i>memoir</i> class defines two counters <code>lastpage</code> and +<p/>The <i>memoir</i> class defines two counters <code>lastpage</code> and <code>lastsheet</code>, which are set (after the first run of a document) to the equivalent of the <code>LastPage</code> label and the <code>TotalPages</code> labels. -<p>Both <i>count1to</i> and <i>totpages</i> need the support of +<p/>Both <i>count1to</i> and <i>totpages</i> need the support of the <i>everyshi</i> package. <dl> <dt><tt><i>count1to.sty and everyshi.sty</i></tt><dd> @@ -31,5 +31,5 @@ the <i>everyshi</i> package. <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>totpages.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/totpages.zip">macros/latex/contrib/totpages</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/totpages.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/totpages/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=howmanypp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=howmanypp</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=howmanypp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=howmanypp</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-htmlbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-htmlbib.html index 178747e4695..1ea5aaf2e27 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-htmlbib.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-htmlbib.html @@ -2,18 +2,18 @@ <title>UK TeX FAQ -- question label htmlbib</title> </head><body> <h3>Making HTML of your Bibliography</h3> -<p>A neat solution is offered by the <i>noTeX</i> bibliography style. +<p/>A neat solution is offered by the <i>noTeX</i> bibliography style. This style produces a <code>.bbl</code> file which is in fact a series of HTML ‘<code>P</code>’ elements of class <code>noTeX</code>, and which may therefore be included in an HTML file. Provision is made for customising your bibliography so that its content when processed by <i>noTeX</i> is different from that presented when it is processed in the ordinary way by (La)TeX. -<p>A thorough solution is offered by <i>bib2xhtml</i>; using it, you +<p/>A thorough solution is offered by <i>bib2xhtml</i>; using it, you make use of one of its modified versions of many common BibTeX styles, and post-process the output so produced using a <i>perl</i> script. -<p>A more conventional translator is the <i>awk</i> script +<p/>A more conventional translator is the <i>awk</i> script <i>bbl2html</i>, which translates the <code>.bbl</code> file you’ve generated: a sample of the script’s output may be viewed on the web, at <a href="http://rikblok.cjb.net/lib/refs.html">http://rikblok.cjb.net/lib/refs.html</a> @@ -22,6 +22,6 @@ a sample of the script’s output may be viewed on the web, at <dt><tt><i>bib2xhtml</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/bib2xhtml.zip">biblio/bibtex/utils/bib2xhtml</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/bib2xhtml.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/utils/bib2xhtml/">browse</a>) <dt><tt><i>noTeX.bst</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/misc/noTeX.bst">biblio/bibtex/utils/misc/noTeX.bst</a> </dl> -<p> -<p><p><p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=htmlbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=htmlbib</a> +<p/> +<p/><p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=htmlbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=htmlbib</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyper.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyper.html index 060a4c1b4a6..caaa70653c6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyper.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyper.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label hyper</title> </head><body> <h3>Making hypertext documents from TeX</h3> -<p>If you want on-line hypertext with a (La)TeX source, probably on the +<p/>If you want on-line hypertext with a (La)TeX source, probably on the World Wide Web, there are four technologies to consider: <ul> <li> Direct <a href="FAQ-LaTeX2HTML.html">(La)TeX conversion to HTML</a>; @@ -17,13 +17,13 @@ World Wide Web, there are four technologies to consider: commands); there are supporting macro packages for Plain TeX and LaTeX). </ul> -<p>The HyperTeX project extended the functionality of all the +<p/>The HyperTeX project extended the functionality of all the LaTeX cross-referencing commands (including the table of contents) to produce <code>\</code><code>special</code> commands which are parsed by DVI processors conforming to the HyperTeX guidelines; it provides general hypertext links, including those to external documents. -<p>The HyperTeX specification says that conformant viewers/translators +<p/>The HyperTeX specification says that conformant viewers/translators must recognize the following set of <code>\</code><code>special</code> commands: <dl> <dt>href:<dd> <code>html:<a href = "href_string"></code> @@ -32,13 +32,13 @@ must recognize the following set of <code>\</code><code>special</code> commands: <dt>image:<dd> <code>html:<img src = "href_string"></code> <dt>base_name:<dd> <code>html:<base href = "href_string"></code> </dl> -<p>The <em>href</em>, <em>name</em> and <em>end</em> commands are used to do +<p/>The <em>href</em>, <em>name</em> and <em>end</em> commands are used to do the basic hypertext operations of establishing links between sections of documents. -<p>Further details are available on <a href="http://arXiv.org/hypertex/">http://arXiv.org/hypertex/</a>; there +<p/>Further details are available on <a href="http://arXiv.org/hypertex/">http://arXiv.org/hypertex/</a>; there are two commonly-used implementations of the specification, a modified <i>xdvi</i> and (recent releases of) <i>dvips</i>. Output from the latter may be used in recent releases of <i>ghostscript</i> or Acrobat Distiller. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyper">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyper</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyper">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyper</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyperdupdest.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyperdupdest.html index ebd3320f341..49ca9f2012c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyperdupdest.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyperdupdest.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label hyperdupdest</title> </head><body> <h3>PDFTeX destination ... ignored</h3> -<p>The warning: +<p/>The warning: <blockquote> <pre> ! pdfTeX warning (ext4): destination with the same identifier @@ -14,23 +14,38 @@ arises because of duplicate page numbers in your document. The problem is usually soluble: see <a href="FAQ-pdfpagelabels.html">PDF page destinations</a> — which answer also describes the problem in more detail. -<p>If the identifier in the message is different, for example +<p/>If the identifier in the message is different, for example <code>name{figure.1.1}</code>, the problem is (usually) due to a problem of package interaction. Some packages are simply incompatible with <i>hyperref</i>, but most work simply by ignoring it. In most cases, therefore, you should load your package before you load <i>hyperref</i>, and <i>hyperref</i> will patch things up so -that they work: +that they work, so you can utilise your (patched) package <em>after</em> +loading both: <blockquote> <code>\</code><code>usepackage{<em>your package</em>}</code><br> - ...<br> - <code>\</code><code>usepackage[<em>opts</em>]{hyperref}</code> + <code>...</code><br> + <code>\</code><code>usepackage[<em>opts</em>]{hyperref}</code><br> + <code>...</code><br> + <<i>code that uses your package</i>> </blockquote><p> -You should do this as a matter of course, unless the documentation of -a package says you <em>must</em> load it after <i>hyperref</i>. -(There aren’t many such packages: one such is <i>memoir</i>’s +For example: +<blockquote> +<pre> +\usepackage{float} % defines \newfloat +... +\usepackage[...]{hyperref} % patches \newfloat +... +\newfloat{...}{...}{...} +</pre> +</blockquote><p> + +You should load packages in this order as a matter of course, unless +the documentation of a package says you <em>must</em> load it after +<i>hyperref</i>. (There aren’t many packages that require to be +loaded after hyperref: one such is <i>memoir</i>’s “<i>hyperref</i> fixup” package <i>memhfixc</i>.) -<p>If loading your packages in the (seemingly) “correct” order doesn’t +<p/>If loading your packages in the (seemingly) “correct” order doesn’t solve the problem, you need to <a href="FAQ-gethelp.html">seek further help</a>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyperdupdest">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyperdupdest</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyperdupdest">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyperdupdest</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphen.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphen.html index 6d19b22b297..a7bf8f25ab3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphen.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphen.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label hyphen</title> </head><body> <h3>How does hyphenation work in TeX?</h3> -<p>Everyone knows what hyphenation is: we see it in most books we read, -and (if we’re alert) often spot ridiculous mis-hyphenation from time -to time (at one time, British newspapers were a fertile source). -<p>Hyphenation styles are culturally-determined, and the same language +<p/>Everyone knows what hyphenation is: we see it in most books we read, +and (if we’re alert) will spot occasional ridiculous mis-hyphenation +(at one time, British newspapers were a fertile source). +<p/>Hyphenation styles are culturally-determined, and the same language may be hyphenated differently in different countries — for example, British and American styles of hyphenation of English are very different. As a result, a typesetting system that is not restricted to a single language at a single locale needs to be able to change its hyphenation rules from time to time. -<p>TeX uses a pretty good system for hyphenation (originally designed +<p/>TeX uses a pretty good system for hyphenation (originally designed by Frank Liang), and while it’s capable of missing “sensible” hyphenation points, it seldom selects grossly wrong ones. The algorithm matches candidates for hyphenation against a set of @@ -19,20 +19,21 @@ algorithm matches candidates for hyphenation against a set of sequences of letters (or other single characters that TeX may be persuaded to think of as letters) — things such as TeX’s <code>\</code><code>accent</code> primitive interrupt hyphenation. -<p>Sets of hyphenation patterns are usually derived from analysis of +<p/>Sets of hyphenation patterns are usually derived from analysis of a list of valid hyphenations (the process of derivation, using a tool called <i>patgen</i>, is not ordinarily a participatory sport). -<p>The patterns for the languages a TeX system is going to deal with +<p/>The patterns for the languages a TeX system is going to deal with may only be loaded when the system is installed. To change the set of languages, a <a href="FAQ-newlang.html">partial reinstallation</a> is necessary. -<p>TeX provides two “user-level” commands for control of +<p/>TeX provides two “user-level” commands for control of hyphenation: <code>\</code><code>language</code> (which selects a hyphenation style), and <code>\</code><code>hyphenation</code> (which gives explicit instructions to the hyphenation engine, overriding the effect of the patterns). -<p>The ordinary LaTeX user need not worry about <code>\</code><code>language</code>, since +<p/>The ordinary LaTeX user need not worry about <code>\</code><code>language</code>, since it is very thoroughly managed by the <i>babel</i> package; use of <code>\</code><code>hyphenation</code> is discussed in + the context of <a href="FAQ-nohyph.html">hyphenation failure</a>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphen">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphen</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphen">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphen</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphenaccents.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphenaccents.html index 11218ae82a0..4b1eb28c382 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphenaccents.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphenaccents.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label hyphenaccents</title> </head><body> <h3>Accented words aren’t hyphenated</h3> -<p>TeX’s algorithm for hyphenation gives up when it encounters an +<p/>TeX’s algorithm for hyphenation gives up when it encounters an <code>\</code><code>accent</code> command; there are good reasons for this, but it means that quality typesetting in non-English languages can be difficult. -<p>For TeX macro packages, you can avoiding the effect by using an +<p/>For TeX macro packages, you can avoiding the effect by using an appropriately encoded font (for example, a Cork-encoded font — see <a href="FAQ-ECfonts.html">the EC fonts</a>) which contains accented letters as single glyphs. LaTeX users can achieve this end simply @@ -17,12 +17,12 @@ to the preamble of their document. Other encodings (notably LY1, once promoted by Y&Y inc) may be used in place of T1. Indeed, most current 8-bit TeX font encodings will ‘work’ with the relevant sets of hyphenation patterns. -<p>One might hope that, with the many aspirant successors to TeX such +<p/>One might hope that, with the many aspirant successors to TeX such as - <a href="FAQ-omegaleph.html">Omega</a>, <a href="FAQ-luatex.html">LUATeX</a> and + <a href="FAQ-omegaleph.html">Omega</a>, <a href="FAQ-luatex.html">LuaTeX</a> and <a href="FAQ-extex.html">ExTeX</a>, all of which base their operations on Unicode, that the whole basis of encodings will change. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphenaccents">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphenaccents</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphenaccents">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphenaccents</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphexcept.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphexcept.html index 2291ff25330..50bcaf4f25e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphexcept.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphexcept.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label hyphexcept</title> </head><body> <h3>Hyphenation exceptions</h3> -<p>While TeX’s hyphenation rules are good, they’re not infallible: you +<p/>While TeX’s hyphenation rules are good, they’re not infallible: you will occasionally find words TeX just gets <em>wrong</em>. So for example, TeX’s default hyphenation rules (for American English) don’t know the word “<em>manuscript</em>”, and since it’s a long word you @@ -15,7 +15,7 @@ hyphenation out” each time you use the word: </blockquote><p> Here, each of the <code>\</code><code>-</code> commands is converted to a hyphenated break, if (<em>and only if</em>) necessary. -<p>That technique can rapidly become tedious: you’ll probably only accept +<p/>That technique can rapidly become tedious: you’ll probably only accept it if there are no more than one or two wrongly-hyphenated words in your document. The alternative is to set up hyphenations in the document preamble. To do that, for the hyphenation above, you would @@ -29,7 +29,7 @@ and the hyphenation would be set for the whole document. Barbara Beeton publishes articles containing lists of these “hyphenation exceptions”, in <i>TUGboat</i>; the hyphenation ‘man-u-script’ comes from one of those articles. -<p>What if you have more than one language in your document? Simple: +<p/>What if you have more than one language in your document? Simple: select the appropriate language, and do the same as above: <blockquote> <pre> @@ -63,10 +63,10 @@ patterns provided in the usual distributions, the encoding is \hyphenation{r\'e-f\'e-rence} </pre> </blockquote><p> -<p>The same sort of performance goes for any language for which 8-bit +<p/>The same sort of performance goes for any language for which 8-bit fonts and corresponding hyphenation patterns are available. Since you have to select both the language and the font encoding to have your document typeset correctly, it should not be a great imposition to do the selections before setting up hyphenation exceptions. -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphexcept">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphexcept</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphexcept">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphexcept</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphoff.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphoff.html index b5224ca3221..918039bbbe6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphoff.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyphoff.html @@ -2,32 +2,32 @@ <title>UK TeX FAQ -- question label hyphoff</title> </head><body> <h3>Stopping all hyphenation</h3> -<p>It may seem an odd thing to want to do (after all, one of TeX’s +<p/>It may seem an odd thing to want to do (after all, one of TeX’s great advertised virtues is the quality of its hyphenation) but it’s sometimes necessary. The real problem is, that the quality of TeX’s output is by default largely dependent on the presence of hyphenation; if you want to abandon hyphenation, something has to give. -<p>TeX (slightly confusingly) offers four possible mechanisms for +<p/>TeX (slightly confusingly) offers four possible mechanisms for suppressing hyphenation (there were only two prior to the extensions that arrived with TeX version 3). -<p>First, one can set the hyphenation penalties <code>\</code><code>hyphenpenalty</code> and +<p/>First, one can set the hyphenation penalties <code>\</code><code>hyphenpenalty</code> and <code>\</code><code>exhyphenpenalty</code> to an ‘infinite’ value (that is to say, 10000). This means that all hyphenations will sufficiently penalise the line that would contain them, that the hyphenation won’t happen. The disadvantage of this method is that TeX will re-evaluate any paragraph for which hyphenations might help, which will slow TeX down. -<p>Second, one can select a language for which no hyphenation patterns +<p/>Second, one can select a language for which no hyphenation patterns exist. Some distributions create a language <code>nohyphenation</code>, and the <i>hyphenat</i> package uses this technique for its <code>\</code><code>nohyphens</code> command which sets its argument without any hyphenation. -<p>Third, one can set <code>\</code><code>left-</code> and/or <code>\</code><code>righthyphenmin</code> to a +<p/>Third, one can set <code>\</code><code>left-</code> and/or <code>\</code><code>righthyphenmin</code> to a sufficiently large value that no hyphenation could possibly succeed, since the minimum is larger than the length of the longest word TeX is willing to hyphenate (the appropriate value is 62). -<p>Fourth, one can suppress hyphenation for all text using the current +<p/>Fourth, one can suppress hyphenation for all text using the current font by the command <blockquote> <pre> @@ -38,34 +38,34 @@ This isn’t a particularly practical way for users to suppress hyphenation — the command has to be issued for every font the document uses — but it’s how LaTeX itself suppresses hyphenation in <code>tt</code> and other fixed-width fonts. -<p>Which of the techniques you should use depends on what you actually +<p/>Which of the techniques you should use depends on what you actually want to do. If the text whose hyphenation is to be suppressed runs for less than a paragraph, your only choice is the no-hyphens language: the language value is preserved along with the text (in the same way that the current font is); the values for penalties and hyphen minima active at the end of a paragraph are used when hyphenation is calculated. -<p>Contrariwise, if you are writing a multilanguage document using the +<p/>Contrariwise, if you are writing a multilanguage document using the <i>babel</i> package, you <em>cannot</em> suppress hyphenation throughout using either the no-hyphens language or the hyphen minima: all those values get changed at a <i>babel</i> language switch: use the penalties instead. -<p>If you simply switch off hyphenation for a good bit of text, the +<p/>If you simply switch off hyphenation for a good bit of text, the output will have a jagged edge (with many lines seriously overfull), and your (La)TeX run will bombard you with warnings about overfull -and underfull lines. To avoid this you have two options. You may use -<code>\</code><code>sloppy</code> (or its environment version <code>sloppypar</code>), and -have TeX stretch what would otherwise be underfull lines to fill the space -offered, and wrap other lines, while prematurely wrapping overfull -lines and stretching the remainder. Alternatively, you may set the -text <a href="FAQ-ragright.html">ragged right</a>, and at least get rid of -the overfull lines; this technique is ‘traditional’ (in the sense that -typists do it) and may be expected to appeal to the specifiers of -eccentric document layouts (such as those for dissertations), but for -once their sense conforms with typographic style. (Or at least, style -constrained in this curious way.) +and underfull lines. To avoid this you have two options. +<p/>The simplest route is to use <code>\</code><code>sloppy</code> (or its environment version +<code>sloppypar</code>), and have TeX stretch what would otherwise +be underfull lines to fill the space offered, while prematurely +wrapping overfull lines and stretching the remainder. +<p/>Alternatively, you may set the text <a href="FAQ-ragright.html">ragged right</a>, +and at least get rid of the overfull lines; this technique is +‘traditional’ (in the sense that typists do it) and may be expected to +appeal to the specifiers of eccentric document layouts (such as those +for dissertations), but for once their sense conforms with typographic +style. (Or at least, style constrained in this curious way.) <dl> <dt><tt><i>hyphenat.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyphenat.zip">macros/latex/contrib/hyphenat</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyphenat.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyphenat/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphoff">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphoff</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphoff">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=hyphoff</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-i18nbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-i18nbib.html index 5d0063df514..7376c7dfe99 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-i18nbib.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-i18nbib.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label i18nbib</title> </head><body> <h3>Non-english bibliographies</h3> -<p>Like so much of early (La)TeX software, BibTeX’s assumptions were +<p/>Like so much of early (La)TeX software, BibTeX’s assumptions were firmly rooted in what its author knew well, viz., academic papers in English (particularly those with a mathematical bent). BibTeX’s standard styles all address exactly that problem, leaving the user who writes in another language (or who deal with citations in the style of other disciplines than maths) to strike out into contributed software. -<p>For the user whose language is not English, there are several +<p/>For the user whose language is not English, there are several alternatives. The simplest is to provide translations of BibTeX styles into the required language: the solitary <i>finplain.bst</i> does that for Finnish; others one can find are for Danish @@ -17,13 +17,13 @@ does that for Finnish; others one can find are for Danish (<i>swebib</i>) bundles (of which the <i>bib-fr</i> set is the most extensive). The <i>spain</i> style implements a traditional Spanish citation style. -<p>These static approaches solve the problem, for the languages that have +<p/>These static approaches solve the problem, for the languages that have been covered by them. Unfortunately, with such an approach, a lot of work is needed for every language involved. Two routes to a solution of the “general” problem are available — that offered by <i>babelbib</i>, and the <a href="FAQ-custbib.html"><i>custom-bib</i> mechanism for generating styles</a>. -<p><i>Babelbib</i> (which is a development of the ideas of the +<p/><i>Babelbib</i> (which is a development of the ideas of the <i>bibgerm</i> package) co-operates with <i>babel</i> to control the language of presentation of citations (potentially at the level of individual items). The package has a built-in set of languages it @@ -31,7 +31,7 @@ individual items). The package has a built-in set of languages it commands for other languages. <i>Babelbib</i> comes with its own set of bibliography styles, which could be a restriction if there wasn’t also a link from <i>custom-bib</i>. -<p>The <i>makebst</i> menu of <i>custom-bib</i> allows you to +<p/>The <i>makebst</i> menu of <i>custom-bib</i> allows you to choose a language for the BibTeX style you’re generating (there are 14 languages to choose; it looks as if <i>spain.bst</i>, mentioned above, was generated this way). If, however, you opt not to specify a @@ -49,5 +49,5 @@ freedom via the extensibility of <i>babelbib</i> <dt><tt><i>spain</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/spain.zip">biblio/bibtex/contrib/spain</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/spain.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/spain/">browse</a>) <dt><tt><i>swebib bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/swebib.zip">biblio/bibtex/contrib/swebib</a> (<a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/contrib/swebib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/biblio/bibtex/contrib/swebib/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=i18nbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=i18nbib</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=i18nbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=i18nbib</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ifpdf.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ifpdf.html index fabab280854..7f26397e5c5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ifpdf.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ifpdf.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label ifpdf</title> </head><body> <h3>Am I using PDFTeX?</h3> -<p>It’s often useful to know whether your macros are operating within +<p/>It’s often useful to know whether your macros are operating within PDFTeX or within (“normal”) TeX; getting the right answer is surprisingly tricky. -<p>Suppose you need to test whether your output will be PDF or +<p/>Suppose you need to test whether your output will be PDF or DVI. The natural thing is to check whether you have access to some PDFTeX-only primitive; a good one to try (not least because it was present in the very first releases of PDFTeX) is @@ -29,7 +29,7 @@ written: </blockquote><p> so that your test will falsely choose the first alternative. While this is a theoretical problem, it is unlikely to be a major one. -<p>More important is the user who loads a package that uses +<p/>More important is the user who loads a package that uses LaTeX-style testing for the command name’s existence (for example, the LaTeX <i>graphics</i> package, which is useful even to the Plain TeX user). Such a package may have gone ahead of you, so the @@ -50,7 +50,7 @@ test may need to be elaborated: If you only want to know whether some PDFTeX extension (such as marginal kerning) is present, you can stop at this point: you know as much as you need. -<p>However, if you need to know whether you’re creating PDF +<p/>However, if you need to know whether you’re creating PDF output, you also need to know about the value of <code>\</code><code>pdfoutput</code>: <blockquote> <pre> @@ -76,5 +76,5 @@ Heiko’s explanation. <dl> <dt><tt><i>ifpdf.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ifpdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ifpdf</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ifpdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ifpdf</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-impgraph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-impgraph.html index 7b2c9979e45..310ef48b1ff 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-impgraph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-impgraph.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label impgraph</title> </head><body> <h3>How to import graphics into (La)TeX documents</h3> -<p>Knuth, when designing the current version of TeX back in the early +<p/>Knuth, when designing the current version of TeX back in the early 1980s, could discern no “standard” way of expressing graphics in documents. He reasoned that this state could not persist for ever, but that it would be foolish for him to define TeX primitives that @@ -11,29 +11,29 @@ deferred the specification of the use of graphics to the writers of DVI drivers; TeX documents would control the drivers by means of <a href="FAQ-specials.html"><code>\</code><code>special</code> commands</a>. -<p>There is therefore a straightforward way for anyone to import graphics +<p/>There is therefore a straightforward way for anyone to import graphics into their document: read the specification of the <code>\</code><code>special</code> commands your driver uses, and ‘just’ code them. This is the hair-shirt approach: it definitely works, but it’s not for everyone. -<p>Over the years, therefore, “graphics inclusion” packages have sprung +<p/>Over the years, therefore, “graphics inclusion” packages have sprung up; most were designed for inclusion of <a href="FAQ-eps.html">Encapsulated PostScript graphics</a> — which has become the <em>lingua franca</em> of graphics inclusion over the last decade or so. -<p>Notable examples are the <i>epsf</i> package (distributed with +<p/>Notable examples are the <i>epsf</i> package (distributed with <i>dvips</i>) and the <i>psfig</i> package. (Both of these packages were designed to work well with both Plain TeX and LaTeX 2.09; they are both still available.) All such packages were tied to a particular DVI driver (<i>dvips</i>, in the above two cases), but their code could be configured for others. -<p>The obvious next step was to make the code configurable dynamically. +<p/>The obvious next step was to make the code configurable dynamically. The LaTeX standard <i>graphics</i> package and its derivatives made this step: it is strongly preferred for all current work. It can also be used (with the help of the <i>miniltx</i> “LaTeX emulator” and the <i>graphicx.tex</i> front-end) in documents written in Plain TeX. -<p>The <i>graphics</i> package takes a variety of “driver +<p/>The <i>graphics</i> package takes a variety of “driver options” — package options that select code to generate the commands appropriate to the DVI driver in use. In most cases, your (La)TeX distribution will provide a <i>graphics.cfg</i> file @@ -41,12 +41,12 @@ that will select the correct driver for what you’re doing (for example, a distribution that provides both LaTeX and PDFLaTeX will usually provide a configuration file that determins whether PDFLaTeX is running, and selects the definitions for it if so). -<p>The <i>graphics</i> package provides a toolkit of commands (insert +<p/>The <i>graphics</i> package provides a toolkit of commands (insert graphics, scale a box, rotate a box), which may be composed to provide most facilities you need; the basic command, <code>\</code><code>includegraphics</code>, takes one optional argument, which specifies the bounding box of the graphics to be included. -<p>The <i>graphicx</i> package uses the facilities of of +<p/>The <i>graphicx</i> package uses the facilities of of <i>graphics</i> behind a rather more sophisticated command syntax to provide a very powerful version of the <code>\</code><code>includegraphics</code> command. <i>graphicx</i>’s version can combine scaling and @@ -55,7 +55,7 @@ is all a convenience (at some cost of syntax), it is also capable of producing noticeably more efficient PostScript, and some of its combinations are simply not possible with the <i>graphics</i> package version. -<p>The <i>epsfig</i> package provides the same facilities as +<p/>The <i>epsfig</i> package provides the same facilities as <i>graphicx</i>, but via a <code>\</code><code>psfig</code> command (also known as <code>\</code><code>epsfig</code>), capable of emulating the behaviour (if not the bugs) the old <i>psfig</i> package. @@ -65,12 +65,12 @@ declare you’re using <i>epsfig</i>, any potential mailing list or usenet helper has to clear out of the equation the possibility that you’re using “old” <i>epsfig</i>, so that support is slower coming than it would otherwise be. -<p>There is no rational reason to stick with the old packages, which have +<p/>There is no rational reason to stick with the old packages, which have never been entirely satisfactory in the LaTeX context. (One irrational reason to leave them behind is that their replacement’s name tends not to imply that it’s exclusively related to PostScript graphics. The reasoning also excludes <i>epsfig</i>, of course.) -<p>A wide variety of detailed techniques and tricks have been developed +<p/>A wide variety of detailed techniques and tricks have been developed over the years, and Keith Reckdahl’s <i>epslatex</i> outlines them in compendious detail: this highly recommendable document is available from CTAN. An invaluable review of the practicalities of @@ -92,5 +92,5 @@ but may also be <dt><tt><i>miniltx.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/graphics.zip">macros/plain/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/graphics/">browse</a>) <dt><tt><i>psfig.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/graphics/psfig.zip">nonfree/graphics/psfig</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/graphics/psfig.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/graphics/psfig/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=impgraph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=impgraph</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=impgraph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=impgraph</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inclplain.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inclplain.html index 5351d1f8d0a..a6f329ef344 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inclplain.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inclplain.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label inclplain</title> </head><body> <h3>Including Plain TeX files in LaTeX</h3> -<p>LaTeX, though originally +<p/>LaTeX, though originally <a href="FAQ-LaTeXandPlain.html">based on Plain TeX</a>, does not contain all of Plain TeX’s commands. Worse, some Plain TeX command names appear in LaTeX, with different semantics. As a result, special measures need to be taken to allow general Plain TeX documents (or parts of documents) to be typeset within LaTeX. -<p>The truly reliable way is to translate the Plain TeX commands, to +<p/>The truly reliable way is to translate the Plain TeX commands, to produce an equivalent of the original’s semantics. However, this is not practical in many circumstances, and for those occasions, the <i>plain</i> package will often come to your aid. The package @@ -29,5 +29,5 @@ the environment saves a lot of work on many occasions. <dl> <dt><tt><i>plain.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>) </dl> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inclplain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inclplain</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inclplain">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inclplain</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-include.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-include.html index e1158bfc6d2..7a758f34ee1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-include.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-include.html @@ -2,34 +2,34 @@ <title>UK TeX FAQ -- question label include</title> </head><body> <h3>What’s going on in my <code>\</code><code>include</code> commands?</h3> -<p>The original LaTeX provided the <code>\</code><code>include</code> command to address the +<p/>The original LaTeX provided the <code>\</code><code>include</code> command to address the problem of long documents: with the relatively slow computers of the time, the companion <code>\</code><code>includeonly</code> facility was a boon. With the vast increase in computer speed, <code>\</code><code>includeonly</code> is less valuable (though it still has its place in some very large projects). Nevertheless, the facility is retained in current LaTeX, and causes some confusion to those who misunderstand it. -<p>In order for <code>\</code><code>includeonly</code> to work, <code>\</code><code>include</code> makes a separate +<p/>In order for <code>\</code><code>includeonly</code> to work, <code>\</code><code>include</code> makes a separate <code>.aux</code> file for each included file, and makes a ‘checkpoint’ of important parameters (such as page, figure, table and footnote numbers); as a direct result, it <em>must</em> clear the current page both before and after the <code>\</code><code>include</code> command. What’s more, this mechanism doesn’t work if a <code>\</code><code>include</code> command appears in a file that was <code>\</code><code>include</code>d itself: LaTeX diagnoses this as an error. -<p>So, we can now answer the two commonest questions about <code>\</code><code>include</code>: +<p/>So, we can now answer the two commonest questions about <code>\</code><code>include</code>: <ul> <li> Why does LaTeX throw a page before and after <code>\</code><code>include</code> commands? -<p> Answer: because it has to. If you don’t like it, replace the +<p/> Answer: because it has to. If you don’t like it, replace the <code>\</code><code>include</code> command with <code>\</code><code>input</code> — you won’t be able to use <code>\</code><code>includeonly</code> any more, but you probably don’t need it anyway, so don’t worry. -<p><li> Why can’t I nest <code>\</code><code>include</code>d files? — I always used to be +<p/><li> Why can’t I nest <code>\</code><code>include</code>d files? — I always used to be able to under LaTeX 2.09. -<p> Answer: in fact, you couldn’t, even under LaTeX 2.09, but the failure +<p/> Answer: in fact, you couldn’t, even under LaTeX 2.09, but the failure wasn’t diagnosed. However, since you were happy with the behaviour under LaTeX 2.09, replace the <code>\</code><code>include</code> commands with <code>\</code><code>input</code> commands (with <code>\</code><code>clearpage</code> as appropriate). </ul> -<p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=include">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=include</a> +<p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=include">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=include</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inputlev.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inputlev.html index e4047de4ee8..366d97da0c9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inputlev.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inputlev.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label inputlev</title> </head><body> <h3>Capacity exceeded — input levels</h3> -<p>The error +<p/>The error <pre> ! TeX capacity exceeded, sorry [text input levels=15]. </pre> @@ -18,8 +18,8 @@ modern TeX distribution. TeTeX (used to produce the error message above) allows 15 files open for TeX input at any one time, which is improbably huge for a document generated by real human beings. -<p>However, for those improbable (or machine-generated) situations, +<p/>However, for those improbable (or machine-generated) situations, some distributions offer the opportunity to adjust the parameter <code>max_in_open</code> in a configuration file. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inputlev">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inputlev</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inputlev">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inputlev</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-miktexinst.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-miktex.html index 3856b06b125..17e7df91632 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-miktexinst.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-miktex.html @@ -1,25 +1,25 @@ <head> -<title>UK TeX FAQ -- question label miktexinst</title> +<title>UK TeX FAQ -- question label inst-miktex</title> </head><body> <h3>Installing MiKTeX “known packages”</h3> -<p>MiKTeX 2.1 (and later) maintains a database of packages it “knows about”, +<p/>MiKTeX 2.1 (and later) maintains a database of packages it “knows about”, together with (coded) installation instructions that enable it to install the packages with minimal user intervention. -<p>If MiKTeX does know about a package you need installed, it’s worth +<p/>If MiKTeX does know about a package you need installed, it’s worth using the system. -<p>First, open the MiKTeX packages window: click on +<p/>First, open the MiKTeX packages window: click on <code>Start</code>-> <code>Programs</code>-> <code>MiKTeX</code>-> <code>MiKTeX Options</code>, and select the <code>Packages</code> tab. -<p>On the tab, there is an Explorer-style display of packages. +<p/>On the tab, there is an Explorer-style display of packages. Right-click on the root of the tree, “<code>MiKTeX Packages</code>”, and select “<code>Search</code>”: enter the name of the package you’re interested in, and press the “<code>Search</code>” button. If MiKTeX knows about your package, it will open up the tree to show you a tick box for your package: check that box. -<p>If you prefer a command-line utility, there’s <i>mpm</i>. Open a +<p/>If you prefer a command-line utility, there’s <i>mpm</i>. Open a command shell, and type: <blockquote> <pre> @@ -28,14 +28,14 @@ mpm --install=<package> </blockquote><p> (which of course assumes you know the name by which MiKTeX refers to your package). -<p>If MiKTeX <em>doesn’t</em> know about the package you’re interested -in, you have to use the <a href="FAQ-instpackages.html">long-winded procedure</a> -outlined elsewhere in this FAQ. -<p>If necessary, repeat to select other packages, and then press +<p/>If MiKTeX <em>doesn’t</em> know about the package you’re interested +in, you have to use the <a href="FAQ-installthings.html">long-winded procedure</a> +outlined above. +<p/>If necessary, repeat to select other packages, and then press “<code>OK</code>”; MiKTeX tells you how many packages you have selected — if you’re happy, press “<code>OK</code>” again. MiKTeX will go off, download the package (as a <code>.cab</code> file), if necessary, install the files of the package, and then refresh the filename database so that the files will be found. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=miktexinst">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=miktexinst</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-miktex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-miktex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-tidy.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-tidy.html new file mode 100644 index 00000000000..6678ef7888a --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-tidy.html @@ -0,0 +1,22 @@ +<head> +<title>UK TeX FAQ -- question label inst-tidy</title> +</head><body> +<h3>Tidying up after installation</h3> +<p/>There’s not usually a lot to do after you’ve completed the steps +above — indeed, if you’re merely installed files direct from the +archive, or whatever, there will be precisely nothing left, by way of +debris. +<p/>Things you might care to clean up are: +<ul> +<li> the archive file, if you retrieved your data from the archive + as a <code>.zip</code> file, or the like; +<li> the <code>.dtx</code> and <code>.ins</code> files, if you chose not + to install them with the documentation; and +<li> the <code>.aux</code>, <code>.log</code>, <code>.idx</code>, etc., + from building the documentation. +</ul> +A simple way of achieving all this is to download to a working +directory that was created for the purpose, and then to delete that +directory and all its contents after you’ve finished installing. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-tidy">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-tidy</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-wlcf.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-wlcf.html new file mode 100644 index 00000000000..ec1eb84f888 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst-wlcf.html @@ -0,0 +1,43 @@ +<head> +<title>UK TeX FAQ -- question label inst-wlcf</title> +</head><body> +<h3>Installing files “where (La)TeX can find them”</h3> +<p/>In the past, package documentation used always to tell you to put your +files “where LaTeX can find them”; this was always unhelpful — +if you knew where that <em>was</em>, you didn’t need telling, but if you +<em>didn’t</em> know, you were completely stuck. +<p/>It was from this issue that the whole idea of the TDS sprang; +“where to put” questions now come down to “where’s the TDS +tree?”. +<p/>We therefore answer the question by considering: +<ul> +<li> <a href="FAQ-what-TDS.html">what tree to use</a>, and +<li> <a href="FAQ-install-where.html">where in the tree to put the files</a>. +</ul> +<p/>Once we know the answer to both questions, and we’ve created any +directories that are needed, we simply copy files to their rightful +location. +<p/>This has done what the old requirement specified: LaTeX (or +whatever) <em>can</em> (in principle) find the files. However, in order +that the software <em>will</em> find the files, we need to update an +index file. +<p/>On a MiKTeX system, open the window + <code>Start</code>-> + <code>All Programs</code>-> + <code>MiKTeX <<i>version</i>></code>-> + <code>Settings</code>, +and click on <code>Refresh FNDB</code>. +The job may also be done in a command window, using the command: +<blockquote> +<pre> +initexmf -u +</pre> +</blockquote><p> +See the MiKTeX documentation for further details about +<code>initexmf</code>. +<p/>On a teTeX or TeX-live-based system, use the command +<code>texhash</code> (or if that’s not available, <code>mktexlsr</code> — +they ought to be different names for the same program). +<p/>Having done all this, the new package will be available for use. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-wlcf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst-wlcf</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html index 08835e07d90..3a18c4217fd 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label inst1cm</title> </head><body> <h3>Installing the Bluesky versions of the CM fonts</h3> -<p>This is a specialised case of <a href="FAQ-instfont.html">installing a font</a>, +<p/>This is a specialised case of <a href="FAQ-instfont.html">installing a font</a>, but it comes easier than most, since the font metrics are installed in every (La)TeX system before you even start. Indeed, most recent systems will have @@ -16,13 +16,13 @@ so the first thing to do is to just try it. On a system that uses </pre> at a “command prompt” (<i>shell</i>, in a Unix-style system, “DOS box” in a Windows system). -<p>If the command works at all, the console output of the command will +<p/>If the command works at all, the console output of the command will include a sequence of Type 1 font file names, listed as <code><cmr10.pfb></code> and so on; this is <i>dvips</i> telling you it’s including the Type 1 font, and you need do no more. -<p>If the test has failed, you need to install your own set of the fonts. -<p>The CTAN directories listed below contain compressed archives of +<p/>If the test has failed, you need to install your own set of the fonts. +<p/>The CTAN directories listed below contain compressed archives of the Type 1 files for various architectures, both for the Computer Modern fonts and for the AMS fonts of mathematical and other useful things. @@ -32,18 +32,18 @@ extract the files — you only actually need the contents of the installed in the “ordinary” way, so that the TFM files are already present. (You don’t need the PostScript font metric — AFM and PFM — files in any case.) -<p>The files should go into your local <code>texmf</code> tree (<i>texmf.local</i>, +<p/>The files should go into your local <code>texmf</code> tree (<i>texmf.local</i>, <i>texmf-local</i>, <i>localtexmf</i>, or whatever). Create directories at offsets <i>fonts/type1/bluesky/cm</i> and <i>fonts/type1/bluesky/ams</i>, and copy the <code>pfb</code> files into them. -<p>Now you need to tell <i>dvips</i>, PDFTeX, etc., that the fonts +<p/>Now you need to tell <i>dvips</i>, PDFTeX, etc., that the fonts are available. This is done by use of a <em>map file</em>, which lists <em>font name</em> (as TeX understands it), <em>font name</em> (as it appears in the type 1 file itself), and where the program will find the file. Map files are provided in the download bundles for the AMS fonts; for the CM fonts, map files are available separately. -<p>The set of map files includes files <code>config.*</code>; each of these contains +<p/>The set of map files includes files <code>config.*</code>; each of these contains an instruction to load a single map file. For ordinary use, you instruct <i>dvips</i> to load the “detailed” map of the CM fonts by use of the command: @@ -61,12 +61,12 @@ loaded by the command <pre> dvips -Pbluesky myfile </pre> -<p>Remember, after all such changes, the -<a href="FAQ-instpackages.html">file-name database must be refreshed</a>. +<p/>Remember, after all such changes, the +<a href="FAQ-inst-wlcf.html">file-name database must be refreshed</a>. <dl> <dt><tt><i>AMS fonts</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/ps-type1/">fonts/amsfonts/ps-type1/</a> <dt><tt><i>CM fonts</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/ps-type1/bluesky/">fonts/cm/ps-type1/bluesky/</a> <dt><tt><i>CM font maps</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/cm/ps-type1/bluesky-contrib/dvips.zip">fonts/cm/ps-type1/bluesky-contrib/dvips</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/cm/ps-type1/bluesky-contrib/dvips.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/cm/ps-type1/bluesky-contrib/dvips/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst1cm">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst1cm</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst1cm">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=inst1cm</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-doc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-doc.html new file mode 100644 index 00000000000..b13fa3a39e8 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-doc.html @@ -0,0 +1,40 @@ +<head> +<title>UK TeX FAQ -- question label install-doc</title> +</head><body> +<h3>Generating package documentation</h3> +<p/>We are faced with a range of “normal” provision, as well as several +oddities. One should note that documentation of many packages is +available on CTAN, without the need of any further effort by +the user — such documentation can usually be browsed <em>in situ</em>. +<p/>However, if you find a package that does not offer documentation on +the archive, or if you need the documentation in some other format +than the archive offers, you can usually generate the documentation +yourself from what you download from the archive. +<p/>The standard mechanism, for LaTeX packages, is simply to run +LaTeX on the <i>package.dtx</i> file, as you would any ordinary +LaTeX file (i.e., repeatedly until the warnings go away). +<p/>A variant is that the unpacking process provides a file +<i>package.drv</i>; if such a thing appears, process it in preference +to the <i>package.dtx</i> (it seems that when the documented LaTeX +source mechanism was first discussed, the <i>.drv</i> mechanism was +suggested, but it’s not widely used nowadays). +<p/>Sometimes, the LaTeX run will complain that it can’t find +<i>package.ind</i> (the code line index) and/or <i>package.gls</i> +(the list of change records). Both types of file are processed with +special <i>makeindex</i> style files; appropriate commands are: +<blockquote> +<pre> +makeindex -s gind package +makeindex -s gglo -o package.gls package.glo +</pre> +</blockquote><p> +This author finds that the second (the change record) is generally of +limited utility when reading package documentation; it is, however, +valuable if you’re part of the package development team. +<p/>Another common (and reasonable) trick is to provide a separate file +<i>package-doc.tex</i> or even simply <i>manual.tex</i>; if the file +<i>package.dtx</i> doesn’t help, simply look around for alternatives. +Such files are treated in the same way as any “ordinary” LaTeX +file. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-doc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-doc</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-find.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-find.html new file mode 100644 index 00000000000..76463c0aa74 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-find.html @@ -0,0 +1,31 @@ +<head> +<title>UK TeX FAQ -- question label install-find</title> +</head><body> +<h3>Finding packages to install</h3> +<p/>How did you find about the package? +<p/>If you learned about your package in these FAQs, you should +already have a link to the file: + + click on that link, +and you can get the file, one way or another. +<p/>If you heard about the file somewhere else, it’s possible that the +source told you where to look; if not, try the CTAN searching +facilities, such as <a href="http://www.tex.ac.uk/search/">http://www.tex.ac.uk/search/</a>. That (rather +simple) search engine can return data from a search of the CTAN +catalogue (which covers most useful packages), or data from a search +of the names of files on the archive. +<p/>Remember that you may want <i>foo.sty</i> but that file is distributed +in a LaTeX documented source file <i>foo.dtx</i>; it’s usually best +to search just for <em>foo</em> — <i>foo.sty</i> won’t be visible +anywhere on the archive or in the catalogue. +<p/>Packages come in a variety of different styles of distribution; the +very simplest will offer just <i>package.sty</i> — in this case, +just download the file and +<a href="FAQ-inst-wlcf.html">get on with installation</a>. +<p/>However, most packages occupy their own directory on the archive; in +this case, you should download the whole directory +<p/>Having acquired the package distribution, see +“<a href="FAQ-install-unpack.html">unpacking LaTeX packages</a>” for your +next step. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-find">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-find</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-unpack.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-unpack.html new file mode 100644 index 00000000000..69ae2b4d7c6 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-unpack.html @@ -0,0 +1,25 @@ +<head> +<title>UK TeX FAQ -- question label install-unpack</title> +</head><body> +<h3>Unpacking LaTeX packages</h3> +<p/>As discussed <a href="FAQ-dtx.html">elsewhere</a>, the ‘ordinary’ way to +distribute a LaTeX package is as a pair of files <i>package.dtx</i> +and <i>package.ins</i>. If you’ve acquired such a pair, you simply +process <i>package.ins</i> with LaTeX, and the files will appear, +ready for installation. +<p/>Other sorts of provision should ordinarily be accompanied by a +<i>README</i> file, telling you what to do; we list a few example +configurations. +<p/>Sometimes, a directory comes with a bunch of <i>.dtx</i> files, but +fewer (often only one) <i>.ins</i> files (LaTeX itself comes +looking like this). The way to go, in this case is simply to process +the <i>.ins</i> file(s) one by one. +<p/>If you’re missing the <i>package.ins</i> altogether, you need to play +around until something works. Some <i>.dtx</i> files are +“self-extracting” — they do without a <i>.ins</i> file, and once +you’ve processed the <i>package.dtx</i>, <i>package.sty</i> has +automagically appeared. Various other oddities may appear, but the +archivists aim to have <i>README</i> file in every package, which +should document anything out of the ordinary with the distribution. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-unpack">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-unpack</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-where.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-where.html new file mode 100644 index 00000000000..0764f0a5450 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-install-where.html @@ -0,0 +1,67 @@ +<head> +<title>UK TeX FAQ -- question label install-where</title> +</head><body> +<h3>Where to install packages</h3> +<p/>Where precisely you put files that you have downloaded depends on +what TeX distribution you have. We will assume that you have one +of the modern TDS-compliant distributions, and discuss the +general rules that you should follow. +<p/>First, you must decide which tree to put your files into; this isn’t +entirely trivial, and is discussed in +“<a href="FAQ-what-TDS.html">choosing a TDS tree</a>”. +<p/>We’ll assume from here on, that you’ve decided on a directory tree, +and we will write <code>$TEXMF</code> for it, whatever it is for your +system. +<p/>The basic idea is to imitate the directory structure in your +existing tree(s). Here are some examples of where various sorts of +files should go: +<blockquote> +<pre> +.sty, .cls or .fd: $TEXMF/tex/latex/<package>/ +.dvi, .ps or .pdf: $TEXMF/doc/latex/<package>/ +.mf: $TEXMF/fonts/source/<supplier>/<font>/ +.tfm: $TEXMF/fonts/tfm/<supplier>/<font>/ +.vf: $TEXMF/fonts/vf/<supplier>/<font>/ +.afm: $TEXMF/fonts/afm/<supplier>/<font>/ +.pfb: $TEXMF/fonts/type1/<supplier>/<font>/ +.ttf: $TEXMF/fonts/truetype/<supplier>/<font>/ +.otf: $TEXMF/fonts/opentype/<supplier>/<font>/ +.pool, .fmt, .base or .mem: $TEXMF/web2c +</pre> +</blockquote><p> +and for modern systems (those distributed in 2005 or later, using TDS +v1.1 layouts): +<blockquote> +<pre> +.map: $TEXMF/fonts/map/<syntax>/<bundle>/ +.enc: $TEXMF/fonts/enc/<syntax>/<bundle>/ +</pre> +</blockquote><p> +(Map and encoding files went to directories under +<i>$TEXMF/dvips/</i>, in earlier distributions.) +<p/>In the lists above, <<i>package</i>>, <<i>font</i>> and <<i>supplier</i>> depend +upon what’s appropriate for the individual file — the supplier +“public” is commonly used for free fonts. The <<i>syntax</i>> +(for <code>.map</code> and <code>.enc</code> files) is a categorisation based +on the way the files are written; typically, it’s the name of a +program such as <i>dvips</i> or <i>pdftex</i>. +<p/>“Straight” (La)TeX input can take other forms than the <code>.sty</code>, +<code>.cls</code> or <code>.fd</code> listed above, too. Examples are +<code>.sto</code> and <code>.clo</code> for package and class options, +<code>.cfg</code> for configuration information, and so on. +<p/>Note that <<i>font</i>> may stand for a single font or an entire family: +for example, files for all of Knuth’s Computer Modern fonts are to be +found in <code>.../public/cm</code>, with various prefixes as appropriate. +<p/>The font “supplier” <em>public</em> is a sort of hold-all for +“free fonts produced for use with (La)TeX”: as well as Knuth’s +fonts, <em>public</em>’s directory holds fonts designed by others +(originally, but no longer exclusively, in Metafont). +<p/>Some packages have configuration files (commonly with file suffix +<code>.cfg</code>), and occasionally other run-time files. The package +documentation <em>should</em> mention these things, but sometimes +doesn’t. An exception is the <code>.drv</code> file, used by some +packages as part of the documentation building process; this is +usually part of the package documentation process, and should not be +installed. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-where">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=install-where</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-installthings.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-installthings.html new file mode 100644 index 00000000000..6c15565106b --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-installthings.html @@ -0,0 +1,22 @@ +<head> +<title>UK TeX FAQ -- question label installthings</title> +</head><body> +<h3>Installing things on a (La)TeX system</h3> +<p/>Installing (or replacing) things on your (La)TeX system has the +potential to be rather complicated; the following questions attempt to +provide a step-by-step approach, starting from the point where you’ve +decided what it is that you want to install: +<ul> +<li> You must <a href="FAQ-install-find.html">find the file you need</a>; +<li> If you are going to install a LaTeX package, you may need to + <a href="FAQ-install-unpack.html">unpack the distributed files</a>; +<li> It’s probably a good idea to + <a href="FAQ-install-doc.html">generate some documentation to read</a>; +<li> You need to + <a href="FAQ-install-where.html">decide where to install the files</a>; +<li> You must now <a href="FAQ-inst-wlcf.html">install the files</a>; and + finally +<li> You may need to <a href="FAQ-inst-tidy.html">tidy up</a> after the installation. +</ul> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=installthings">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=installthings</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instfont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instfont.html index fe8d33b74fa..e60489af791 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instfont.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instfont.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label instfont</title> </head><body> <h3>Installing a new font</h3> -<p>Fonts are really “just another package”, and so should be installed +<p/>Fonts are really “just another package”, and so should be installed in the same sort of way as packages. However, fonts tend to be more complicated than the average package, and as a result it’s sometimes difficult to see the overall structure. -<p>Font files may appear in any of a large number of different formats; +<p/>Font files may appear in any of a large number of different formats; each format has a different function in a TeX system, and each is stored in a directory its own sub-tree in the installation’s TDS tree; all these sub-trees have the directory @@ -17,5 +17,5 @@ this answer to view them all. Other answers discuss specific font families — for example, “<a href="FAQ-concrete.html">using the concrete fonts</a>”. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instfont</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instfont</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html index d1fd7f10b4a..83604ccd16b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instmffont.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label instmffont</title> </head><body> <h3>Installing a font provided as Metafont source</h3> -<p>Metafont fonts are (by comparison with other sorts of font) rather +<p/>Metafont fonts are (by comparison with other sorts of font) rather pleasingly simple. Nowadays, they are mostly distributed just as the Metafont source, since modern TeX distributions are able to produce everything the user needs “on the fly”; however, if the distribution @@ -12,11 +12,11 @@ distributions of PK font bitmap files: there’s no way of learning from them what printer they were generated for, and naming schemes under different operating systems are another source of confusion. -<p>“<a href="FAQ-wherefiles.html">Where to install files</a>” +<p/>“<a href="FAQ-install-where.html">Where to install files</a>” specifies where the files should go. -<p>Further confusion is introduced by font families whose authors devise rules +<p/>Further confusion is introduced by font families whose authors devise rules for automatic generation of Metafont sources for generating fonts at particular sizes; the installation has to know about the rules, as otherwise it cannot generate font files. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instmffont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instmffont</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instmffont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instmffont</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instpackages.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instpackages.html deleted file mode 100644 index 2e389887e49..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instpackages.html +++ /dev/null @@ -1,89 +0,0 @@ -<head> -<title>UK TeX FAQ -- question label instpackages</title> -</head><body> -<h3>Installing a new package</h3> -<p>The first step in installing a new package for your LaTeX system -is usually to <a href="FAQ-findfiles.html">find where it is</a> -and then to get it, usually from CTAN. However MiKTeX, -since version 2.1, offers a <a href="FAQ-miktexinst.html">simpler procedure</a> -than that described here, for packages it knows about. -<p>Ordinarily, you should download the whole distribution directory; the -only occasion when this is not necessary is when you are getting -something from one of the (La)TeX contributed “<i>misc</i>” -directories on CTAN; these directories contain collections of -single files, which are supposedly complete in themselves. -<p>A small package <<i>smallpack</i>> might be just a single <code>.sty</code> file -(typically <i>smallpack.sty</i>) with the usage instructions either -included as comments in the file or in a separate user manual or -<i>README</i> file. More often a package <<i>pack</i>> will come as -a pair of files, <i>pack.ins</i> and <i>pack.dtx</i>, written to be -used with the LaTeX <i>doc</i> system. The package code must be -extracted from these files. If there is a <i>README</i> file as part -of the package distribution, read it! -<p>In the <i>doc</i> system, the user manual and documented package -code is in the <code>.dtx</code> file, and the <code>.ins</code> file contains LaTeX -instructions on what code should be extracted from the <code>.dtx</code> file. To -unpack a <i>doc</i> package <<i>pack</i>>, do the following: -<ul> -<li> Run latex on <i>pack.ins</i>. This will generate one or more - files (normally a <i>pack.sty</i> file but there may be others - depending on the particular package). -<li> Run latex on <i>pack.dtx</i> as a start to getting the user - manual and possibly a commented version of the package code. -<li> Run latex again on <i>pack.dtx</i>, which should resolve any - references and generate a Table of Contents if it was called for. -<li> LaTeX may have said “<code>No file pack.ind</code>”; this is the - source for the command index; if you want the index, process the raw - material with: - <blockquote> - <code>makeindex -s gind.ist pack</code> - </blockquote><p> - and run LaTeX again. -<li> Print and read <i>pack.dvi</i> -</ul> -Sometimes a user manual is supplied separately from the <i>.dtx</i> -file. Process this <em>after</em> doing the above, just in case the user -manual uses the package it is describing. -<p>Almost the final stage of the installation is to put the package -file(s) <em>‘where LaTeX can find them’</em>. Where the magic place -is, and how you put the files there depends on your particular -LaTeX system and how it is set up (see - -<a href="FAQ-tds.html">the TeX directory structure standard</a> for -general principles, -<a href="FAQ-wherefiles.html">where to put files</a> for specific advice). -<p>The final stage is to tell LaTeX that there is a new file, or -files, that it should be able to go and find. Most free LaTeX systems -maintain a database of the names and locations of latex-related files -to enable faster searching. In these systems the database must be -updated, using the script or program provided with the distribution -for this purpose. -<dl> -<dt>teTeX<dd> Run: <br> - <code>texhash</code> -<dt>web2c<dd> On a current <i>web2c</i> distribution, <code>texhash</code> - ought to work; if it doesn’t, run <code>mktexlsr</code> -<dt>MiKTeX<dd> On a <i>MiKTeX</i> distribution earlier than v2.0, - click - <code>Start</code>-> - <code>Programs</code>-> - <code>MiKTeX</code>-> - <code>Maintenance</code>-> - <code>Refresh filename database</code> - - -<p> or get a DOS window and run:<br> - <code>initexmf --update-fndb</code> -<p> On a <i>MiKTeX</i> distribution v2.0 or later, do:<br> - <code>Start</code>-> - <code>Programs</code>-> - <code>MiKTeX 2</code>-> - <code>MiKTeX Options</code>, and press the - - <code>Refresh now</code> button (<code>Update filename database</code> in - earlier versions of MiKTeX). -</dl> -<p>Remember that a <code>\usepackage{pack}</code> command must be put in the preamble -of each document in which you want to use the <i>pack</i> package. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instpackages">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instpackages</a> -</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instprinterfont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instprinterfont.html index 788de00a57a..2ac895a9bef 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instprinterfont.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instprinterfont.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label instprinterfont</title> </head><body> <h3>Installing a PostScript printer built-in font</h3> -<p>There is a “standard” set of fonts that has appeared in every PostScript +<p/>There is a “standard” set of fonts that has appeared in every PostScript printer since the second generation of the type. These fonts (8 families of four text fonts each, and three special-purpose fonts) are of course widely used, because of their simple availability. The @@ -27,13 +27,13 @@ system will have some version of <i>psnfss</i> installed, but users should note that the most recent version has much improved coverage of maths-with-<i>Times</i> and -<i>Palatino</i>, as well as a more reliable set of font metrics. -<p>The archive <i>lw35nfss.zip</i> is laid out according to the +<p/>The archive <i>lw35nfss.zip</i> is laid out according to the TDS, so in principle, installation consists simply of “unzipping” the file at the root of a <i>texmf</i> tree. -<p>Documentation of the <i>psnfss</i> bundle is provided in +<p/>Documentation of the <i>psnfss</i> bundle is provided in <i>psnfss2e.pdf</i> in the distribution. <dl> <dt><tt><i>psnfss bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss.zip">macros/latex/required/psnfss</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/psnfss/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instprinterfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instprinterfont</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instprinterfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instprinterfont</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html index 5d5cf7533ed..042ba93b39b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instt1font.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label instt1font</title> </head><body> <h3>Installing a Type 1 font</h3> -<p>The process of installing a Type 1 font set is rather convoluted, but +<p/>The process of installing a Type 1 font set is rather convoluted, but it may be separated into a modest set of stages. <ul> <li> Acquire the font. A very small set of Type 1 fonts is installed in most PostScript printers you will encounter. For those few (whose use is covered by the basic PSNFSS package), you don’t need the Type 1 font itself, to be able to print using the font. -<p> For all the myriad other Type 1 fonts, to be able to print using +<p/> For all the myriad other Type 1 fonts, to be able to print using the font you need the Type 1 file itself. Some of these are available for free (they’ve either been donated to the public domain, or were developed as part of a free software project), but @@ -38,7 +38,7 @@ it may be separated into a modest set of stages. font family in both T1 and OT1 font encodings. Nevertheless, with fancier fonts, more elaborate things are possible with <i>fontinst</i>: see the documentation for details. -<p> <i>Fontinst</i> also generates map files, and LaTeX font +<p/> <i>Fontinst</i> also generates map files, and LaTeX font definition (<code>.fd</code>) files. <li> Install the files, in your <code>texmf</code> tree. All the strictures about installing non-standard things apply here: be sure @@ -63,7 +63,7 @@ and in other (earlier) systems as .map .../dvips/fontinst/<foundry> </pre> <li> Regenerate the file indexes (as described in - <a href="FAQ-instpackages.html">package installation</a>). + <a href="FAQ-inst-wlcf.html">package installation</a>). <li> Update the <i>dvips</i> and other maps: <ul> <li> On a teTeX system earlier than version 2.0, edit the file @@ -90,6 +90,6 @@ Lehman’s guide to font installation, which may be found on CTAN. <dt><tt><i>fontinst.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.zip">fonts/utilities/fontinst</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/fontinst/">browse</a>) <dt><tt><i>Type 1 installation guide</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/Type1fonts/fontinstallationguide/fontinstallationguide.pdf">info/Type1fonts/fontinstallationguide/fontinstallationguide.pdf</a> </dl> -<p> -<p><p><p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instt1font">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instt1font</a> +<p/> +<p/><p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instt1font">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instt1font</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-interruptlist.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-interruptlist.html index 0de9ad2eeb2..72367f6d61f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-interruptlist.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-interruptlist.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label interruptlist</title> </head><body> <h3>Interrupting enumerated lists</h3> -<p>It’s often convenient to have commentary text, ‘outside’ the list, +<p/>It’s often convenient to have commentary text, ‘outside’ the list, between successive entries of a list. In the case of <code>itemize</code> lists this is no problem, since there’s never anything to distinguish successive items, while in the case of <code>description</code> lists, the item labels are under the user’s control so there’s no automatic issue of continuity. -<p>For <code>enumerate</code> lists, the labels are generated +<p/>For <code>enumerate</code> lists, the labels are generated automatically, and are context-sensitive, so the context (in this case, the state of the enumeration counter) needs to be preserved. -<p>The belt-and-braces approach is to remember the state of the +<p/>The belt-and-braces approach is to remember the state of the enumeration in your own counter variable, and then restore it when restarting enumerate: <blockquote> @@ -29,12 +29,12 @@ restarting enumerate: \end{enumerate} </pre> </blockquote><p> -<p>This is reasonable, in small doses... Problems (apart from sheer +<p/>This is reasonable, in small doses... Problems (apart from sheer verbosity) are getting the level right (“should I use counter <code>enumi</code>, <code>enumii</code>, ...”) and remembering not to nest the interruptions (i.e., not to have a separate list, that is itself interrupted) in the “commentary text”). -<p>The <i>mdwlist</i> package defines commands <code>\</code><code>suspend</code> and +<p/>The <i>mdwlist</i> package defines commands <code>\</code><code>suspend</code> and <code>\</code><code>resume</code> that simplify the process: <blockquote> <pre> @@ -51,7 +51,7 @@ The package allows an optional name (as in <code>\</code><code>suspend[id]{enumerate}</code>) to allow you to identify a particular suspension, and hence provide a handle for manipulating nested suspensions. -<p>If you’re suspending a <a href="FAQ-enumerate.html">fancy-enumeration list</a>, +<p/>If you’re suspending a <a href="FAQ-enumerate.html">fancy-enumeration list</a>, you need to re-supply the optional “item label layout” parameters required by the <i>enumerate</i> package when resuming the list, whether by the @@ -72,7 +72,7 @@ which requires use of extra braces: </pre> </blockquote><p> The <i>enumitem</i> package, in its most recent -release, will allow you to resume lists, at one level only: +release, will also allow you to resume lists: <blockquote> <pre> \begin{enumerate} @@ -87,10 +87,37 @@ release, will allow you to resume lists, at one level only: which feels just as “natural” as the <i>mdwtools</i> facility, and has the advantage of playing well with the other excellent facilities of <i>enumitem</i>. +<p/><i>Enumitem</i> also allows multi-level suspension and resumption +of lists: +<blockquote> +<pre> +\begin{enumerate} +\item outer item 1 +\end{enumerate} +<comment> +\begin{enumerate}[resume] +\item outer item 2 +% nested enumerate +\begin{enumerate} +\item inner item 1 +\end{enumerate} +<nested comment> +% resume nested enumerate +\begin{enumerate}[resume] +\item inner item 2 +\end{enumerate} +\item outer item 3 +% end outer enumerate +\end{enumerate} +</pre> +However, the comment interpolated in the nested enumeration appears as +if it were a second paragraph to “outer item 2”, which is hardly +satisfactory. +</blockquote><p> <dl> <dt><tt><i>enumerate.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) <dt><tt><i>enumitem.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.zip">macros/latex/contrib/enumitem</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem/">browse</a>) <dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse</a>) </dl> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=interruptlist">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=interruptlist</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=interruptlist">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=interruptlist</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-isdef.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-isdef.html index bfca87b02fc..beb30d35535 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-isdef.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-isdef.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label isdef</title> </head><body> <h3>Is this command defined?</h3> -<p>Macro sets from the earliest days of TeX programming may be +<p/>Macro sets from the earliest days of TeX programming may be observed to test whether commands exist by using <blockquote> <code>\</code><code>ifx</code> csx<code><em>command</em></code> <code>\</code><code>undefined</code> <<i>stuff</i>> ... @@ -15,7 +15,7 @@ exist). LaTeX programmers can make use of the internal command which executes <code>action1</code> if the command is undefined, and <code>action2</code> if it is defined (<em>cmd name</em> is the command name only, omitting the ‘<code>\</code>’ character). -<p>The <code>\</code><code>@ifundefined</code> command is based on the sequence +<p/>The <code>\</code><code>@ifundefined</code> command is based on the sequence <blockquote> <pre> @@ -24,21 +24,21 @@ which executes <code>action1</code> if the command is undefined, and </blockquote><p> which relies on the way <code>\</code><code>csname</code> works: if the command doesn’t exist, it simply creates it as an alias for <code>\</code><code>relax</code>. -<p>So: what is wrong with these techniques? -<p>Using <code>\</code><code>undefined</code> blithely assumes that the command is indeed not +<p/>So: what is wrong with these techniques? +<p/>Using <code>\</code><code>undefined</code> blithely assumes that the command is indeed not defined. This isn’t entirely safe; one could make the name more improbable, but that may simply make it more difficult to spot a problem when things go wrong. LaTeX programmers who use the technique will typically employ <code>\</code><code>@undefined</code>, adding a single level of obscurity. -<p>The <code>\</code><code>@ifundefined</code> mechanism has the unfortunate property of +<p/>The <code>\</code><code>@ifundefined</code> mechanism has the unfortunate property of polluting the name space: each test that turns out undefined adds a name to the set TeX is holding, and often all those “<code>\</code><code>relax</code>” names serve no purpose whatever. Even so (sadly) there are places in the code of LaTeX where the existence of the <code>\</code><code>relax</code> is relied upon, after the test, so we can’t get away from <code>\</code><code>@ifundefined</code> altogether. -<p>David Kastrup offers the (rather tricky) +<p/>David Kastrup offers the (rather tricky) <blockquote> <pre> {\expandafter}\expandafter\ifx \csname cmd name\endcsname\relax ... @@ -48,7 +48,7 @@ altogether. which “creates” the <code>\</code><code>relax</code>-command inside the group of the first <code>\</code><code>expandafter</code>, therefore forgets it again once the test is done. The test is about as good as you can do with macros. -<p>The <a href="FAQ-etex.html">e-TeX system</a> system comes to our help here: it +<p/>The <a href="FAQ-etex.html">e-TeX system</a> system comes to our help here: it defines two new primitives: <ul> <li> <code>\</code><code>ifdefined</code>, which tests whether a thing is defined (the @@ -79,8 +79,8 @@ However, after using the LaTeX command as “existing” (since it has been <code>\</code><code>let</code> to <code>\</code><code>relax</code>); so it is important not to mix mechanisms for detecting the state of a command. -<p>Since most distributions nowadays use e-TeX as their base executable +<p/>Since most distributions nowadays use e-TeX as their base executable for most packages, these two primitives may be expected appear widely in new macro packages. -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=isdef">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=isdef</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=isdef">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=isdef</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-isitanum.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-isitanum.html index 0e2111d2a84..b45422f401c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-isitanum.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-isitanum.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label isitanum</title> </head><body> <h3>Is the argument a number?</h3> -<p>TeX’s own lexical analysis doesn’t offer the macro programmer +<p/>TeX’s own lexical analysis doesn’t offer the macro programmer terribly much support: while category codes will distinguish letters (or what TeX currently thinks of as letters) from everything else, there’s no support for analysing numbers. -<p>The simple-minded solution is to compare numeric characters with the +<p/>The simple-minded solution is to compare numeric characters with the characters of the argument, one by one, by a sequence of direct tests, and to declare the argument “not a number” if any character fails all comparisons: @@ -36,7 +36,7 @@ satisfactory: getting the recursion “right” is troublesome (it has a tendency to gobble spaces in the argument), and in any case TeX itself has mechanisms for reading numbers, and it would be nice to use them. -<p>Donald Arseneau’s <i>cite</i> package offers the following test +<p/>Donald Arseneau’s <i>cite</i> package offers the following test for an argument being a strictly positive integer: <blockquote> <pre> @@ -65,7 +65,7 @@ or a test for any integer: </pre> </blockquote><p> but this surely stretches the technique further than is reasonable. -<p>If we don’t care about the sign, we can use TeX to remove the +<p/>If we don’t care about the sign, we can use TeX to remove the entire number (sign and all) from the input stream, and then look at what’s left: <blockquote> @@ -96,7 +96,7 @@ which relies on <code>\</code><code>romannumeral</code> producing an empty resul argument is zero. Sadly, this technique has the unfortunate property that it accepts simple expressions such as ‘<code>1+2-3</code>’; this could be solved by an initial <code>\</code><code>gobbleminus</code>-like construction. -<p>All the complete functions above are designed to be used in TeX +<p/>All the complete functions above are designed to be used in TeX conditionals written “naturally” — for example: <blockquote> <pre> @@ -110,7 +110,7 @@ conditionals written “naturally” — for example: The LaTeX <i>memoir</i> class has an internal command of its own, <code>\</code><code>checkifinteger{</code><em>num</em><code>}</code>, that sets the conditional command <code>\</code><code>ifinteger</code> according to whether the argument was an integer. -<p>Of course, all this kerfuffle would be (essentially) void if there was +<p/>Of course, all this kerfuffle would be (essentially) void if there was a simple means of “catching” TeX errors. Imagining an error-catching primitive <code>\</code><code>ifnoerror</code>, one might write: <blockquote> @@ -134,5 +134,5 @@ impossible to program within TeX!). <dl> <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=isitanum">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=isitanum</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=isitanum">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=isitanum</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-journalpaper.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-journalpaper.html index 4e74cbf1606..b3da3be3629 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-journalpaper.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-journalpaper.html @@ -2,24 +2,24 @@ <title>UK TeX FAQ -- question label journalpaper</title> </head><body> <h3>Setting papers for journals</h3> -<p>Publishers of journals have a wide range of requirements for the +<p/>Publishers of journals have a wide range of requirements for the presentation of papers, and while many publishers do accept electronic submissions in (La)TeX, they don’t often submit recommended macros to public archives. -<p>Nevertheless, there are considerable numbers of macros of one sort or +<p/>Nevertheless, there are considerable numbers of macros of one sort or another available on CTAN; searching for your journal name in the CTAN catalogue (see <a href="FAQ-findfiles.html">searching CTAN</a>) may well turn up what you’re seeking. -<p>Failing that, you may be well advised to contact the prospective +<p/>Failing that, you may be well advised to contact the prospective publisher of your paper; many publishers have macros on their own web sites, or otherwise available only upon application. -<p>Check that the publisher is offering you macros suitable to an +<p/>Check that the publisher is offering you macros suitable to an environment you can use: a few still have no macros for current LaTeX, for example, claiming that LaTeX 2.09 is good enough... -<p>Some publishers rekey anything sent them anyway, so that it doesn’t +<p/>Some publishers rekey anything sent them anyway, so that it doesn’t really matter what macros you use. Others merely encourage you to use as few extensions of a standard package as possible, so that they will find it easy to transform your paper to their own internal form. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=journalpaper">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=journalpaper</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=journalpaper">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=journalpaper</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-keepfonts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-keepfonts.html index aa30defd5c3..84234b0e9dd 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-keepfonts.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-keepfonts.html @@ -2,26 +2,26 @@ <title>UK TeX FAQ -- question label keepfonts</title> </head><body> <h3>Which font files should be kept</h3> -<p>Metafont produces from its run three files, a metrics (TFM) file, a +<p/>Metafont produces from its run three files, a metrics (TFM) file, a generic font (GF) file, and a log file; all of these files have the same base name as does the input (<em>e.g.</em>, if the input file was <i>cmr10.mf</i>, the outputs will be <i>cmr10.tfm</i>, <i>cmr10.nnngf</i> and <i>cmr10.log</i>). -<p>For TeX to use the font, you need a TFM file, so you need +<p/>For TeX to use the font, you need a TFM file, so you need to keep that. However, you are likely to generate the same font at more than one magnification, and each time you do so you’ll (incidentally) generate another TFM file; these files are all the same, so you only need to keep one of them. -<p>To preview or to produce printed output, the DVI processor will need a +<p/>To preview or to produce printed output, the DVI processor will need a font raster file; this is what the GF file provides. However, while there used (once upon a time) to be DVI processors that could use GF files, modern processors use packed raster (PK) files. Therefore, you need to generate a PK file from the GF file; the program <i>gftopk</i> does this for you, and once you’ve done that you may throw the GF file away. -<p>The log file should never need to be used, unless there was some sort +<p/>The log file should never need to be used, unless there was some sort of problem in the Metafont run, and need not be ordinarily kept. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=keepfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=keepfonts</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=keepfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=keepfonts</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelctr.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelctr.html index 0226073d97d..c629c881aa0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelctr.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelctr.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label labelctr</title> </head><body> <h3>Making labels from a counter</h3> -<p>Suppose we have a LaTeX counter, which we’ve defined with +<p/>Suppose we have a LaTeX counter, which we’ve defined with <code>\</code><code>newcounter{foo}</code>. We can increment the value of the counter by <code>\</code><code>addtocounter{foo}{1}</code>, but that’s pretty clunky for an operation that happens so often ... so there’s a command <code>\</code><code>stepcounter{foo}</code> that does this special case of increasing-by-one. -<p>There’s an internal LaTeX variable, the “current label”, that +<p/>There’s an internal LaTeX variable, the “current label”, that remembers the last ‘labellable’ thing that LaTeX has processed. You could (if you were to insist) set that value by the relevant TeX command (having taken the necessary precautions to ensure that @@ -17,5 +17,5 @@ of either of the stepping methods above, you say <code>\</code><code>refstepcounter{foo}</code>, the internal variable is set to the new value, and (until something else comes along), <code>\</code><code>label</code> will refer to the counter. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelctr">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelctr</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelctr">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelctr</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelfig.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelfig.html index 41af36c2aff..820715ebb60 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelfig.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelfig.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label labelfig</title> </head><body> <h3>Labelling graphics</h3> -<p>“Technical” graphics (such as graphs and diagrams) are often +<p/>“Technical” graphics (such as graphs and diagrams) are often labelled with quite complex mathematical expressions: there are few drawing or graphing tools that can do such things (the honourable exception being MetaPost, which allows you to program the labels, in (La)TeX, in the middle of specifying your graphic). -<p>Labels on graphics produced by all those <em>other</em> tools is where +<p/>Labels on graphics produced by all those <em>other</em> tools is where the <i>psfrag</i> package can help. Place an unique text in your graphic, using the normal text features of your tool, and you can ask <i>psfrag</i> to replace the text with arbitrary @@ -25,7 +25,7 @@ hand, <a href="FAQ-commercial.html">VTeX</a>’s GeX processor explicitly deals with <i>psfrag</i>, both in its free and commercial instances.) -<p>The <i>psfragx</i> package goes one step further than +<p/>The <i>psfragx</i> package goes one step further than <i>psfrag</i>: it provides a means whereby you can put the <i>psfrag</i> commands into the preamble of your EPS file itself. <i>Psfrag</i> has such a command itself, but deprecates @@ -33,25 +33,25 @@ it; <i>psfragx</i> has cleaned up the facility, and provides a script <i>laprint</i> for use with <i>Matlab</i> to produce appropriately tagged output. (In principle, other graphics applications could provide a similar facility, but apparently none does.) -<p><i>Emacs</i> users may find the embedded editor <i>iTe</i> a +<p/><i>Emacs</i> users may find the embedded editor <i>iTe</i> a useful tool for placing labels: it’s a (La)TeX-oriented graphical editor written in <i>Emacs Lisp</i>. You create <code>iteblock</code> environments containing graphics and text, and may then invoke <i>iTe</i> to arrange the elements relative to one another. -<p>Another useful approach is <i>overpic</i>, which overlays a +<p/>Another useful approach is <i>overpic</i>, which overlays a <code>picture</code> environment on a graphic included by use of <code>\</code><code>includegraphics</code>. This treatment lends itself to ready placement of texts and the like on top of a graphic. The package can draw a grid for planning your “attack”; the distribution comes with simple examples. -<p><i>Pstricks</i> can of course do everything that <i>overpic</i> +<p/><i>Pstricks</i> can of course do everything that <i>overpic</i> can, with all the flexibility of PostScript programming that it offers The <i>pstricks</i> web site has a page with several <a href="http://pstricks.tug.org/main.cgi?file=Examples/overlay">examples of labelling</a> which will get you started; if <i>pstricks</i> is <a href="FAQ-drawing.html">an option for you</a>, this route is worth a try. -<p>The confident user may, of course, do the whole job in a picture +<p/>The confident user may, of course, do the whole job in a picture environment which itself includes the graphic. I would recommend <i>overpic</i> or the <i>pstricks</i> approach, but such things are plainly little more than a convenience over what is achievable @@ -64,6 +64,6 @@ with the do-it-yourself approach. <dt><tt><i>psfragx.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psfragx.zip">macros/latex/contrib/psfragx</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psfragx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/psfragx/">browse</a>) <dt><tt><i>pstricks.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.zip">graphics/pstricks</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pstricks/">browse</a>) </dl> -<p> -<p><p><p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelfig">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelfig</a> +<p/> +<p/><p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelfig">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelfig</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelformat.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelformat.html index b3a63660267..1a34c99d57e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelformat.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labelformat.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label labelformat</title> </head><body> <h3>How to change the format of labels</h3> -<p>By default, when a label is created, it takes on the appearance of the +<p/>By default, when a label is created, it takes on the appearance of the counter labelled, so the label appears as <code>\</code><code>the</code><code><<i>counter</i>></code> — what would be used if you asked to typeset the counter in your text. This isn’t always what you @@ -23,7 +23,7 @@ which would be both tedious and error-prone. What’s more, it would be undesirable, since you would be constructing a visual representation which is inflexible (you couldn’t change all the references to elements of a list at one fell swoop). -<p>LaTeX in fact has a label-formatting command built into every label +<p/>LaTeX in fact has a label-formatting command built into every label definition; by default it’s null, but it’s available for the user to program. For any label <<i>counter</i>> there’s a LaTeX internal command <code>\</code><code>p@</code><<i><code>counter</i>></code>; for example, a label definition @@ -54,7 +54,7 @@ all inner lists by adding the following code in your preamble: This would make the labels for second-level enumerated lists appear as “1(a)” (and so on). The analogous change works for any counter that gets used in a <code>\</code><code>label</code> command. -<p>In fact, the <i>fncylab</i> package does all the above (including +<p/>In fact, the <i>fncylab</i> package does all the above (including the patch to LaTeX itself). With the package, the code above is (actually quite efficiently) rendered by the command: <blockquote> @@ -70,5 +70,5 @@ package, which is discussed in the answer about <dt><tt><i>enumitem.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.zip">macros/latex/contrib/enumitem</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/enumitem.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/enumitem/">browse</a>) <dt><tt><i>fncylab.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/fncylab.sty">macros/latex/contrib/misc/fncylab.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelformat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelformat</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelformat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labelformat</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labundef.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labundef.html index 2cba86986ff..ba3c6c803b8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labundef.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-labundef.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label labundef</title> </head><body> <h3>Finding if a label is undefined</h3> -<p>People seem to want to know (at run time) if a label is undefined (I +<p/>People seem to want to know (at run time) if a label is undefined (I don’t actually understand <em>why</em>, particularly: it’s a transient state, and LaTeX deals with it quite well). -<p>A resolved label is simply a command: +<p/>A resolved label is simply a command: <code>\</code><code>r@</code><code><<i>label-name</i>></code>; determining if the label is set is then simply a matter of detecting if the command exists. The usual LaTeX internal way of doing this is to use the command @@ -18,16 +18,16 @@ a <code>\</code><code>label</code> command, and the remaining two arguments are sequences to be used if the label is undefined (<<i>undef-cmds</i>>) or if it is defined (<<i>def-cmds</i>>). -<p>Note that any command that incorporates <code>\</code><code>@ifundefined</code> is naturally +<p/>Note that any command that incorporates <code>\</code><code>@ifundefined</code> is naturally fragile, so remember to create it with <code>\</code><code>DeclareRobustCommand</code> or to use it with <code>\</code><code>protect</code> in a moving argument. -<p>If you’re into this game, you may well not care about LaTeX’s +<p/>If you’re into this game, you may well not care about LaTeX’s warning about undefined labels at the end of the document; however, if you are, include the command <code>\</code><code>G@refundefinedtrue</code> in <<i><code>undef-cmds</i>></code>. -<p>And of course, remember you’re dealing in internal commands, and pay +<p/>And of course, remember you’re dealing in internal commands, and pay attention to the <a href="FAQ-atsigns.html">at-signs</a>. -<p>All the above can be avoided by using the <i>labelcas</i> package: +<p/>All the above can be avoided by using the <i>labelcas</i> package: it provides commands that enable you to switch according to the state of a single label, or the states of a list of labels. The package’s definition is a bit complicated, but the package itself is pretty @@ -35,5 +35,5 @@ powerful. <dl> <dt><tt><i>labelcas.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/labelcas.zip">macros/latex/contrib/labelcas</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/labelcas.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/labelcas/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labundef">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labundef</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labundef">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=labundef</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-landscape.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-landscape.html index a14842e51ae..f2b910ffd23 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-landscape.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-landscape.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label landscape</title> </head><body> <h3>Typesetting things in landscape orientation</h3> -<p>It’s often necessary to typeset part of a document in landscape +<p/>It’s often necessary to typeset part of a document in landscape orientation; to achieve this, one needs not only to change the page dimensions, but also to instruct the output device to print the strange page differently. -<p>There are two “ordinary” mechanisms for doing two slight variations +<p/>There are two “ordinary” mechanisms for doing two slight variations of landscape typesetting: <ul> <li> If you have a single floating object that is wider than it is @@ -14,7 +14,7 @@ of landscape typesetting: the <i>rotating</i> package; this defines <code>sidewaysfigure</code> and <code>sidewaystable</code> environments which create floats that occupy a whole page. -<p> Note that <i>rotating</i> has problems in a document that also +<p/> Note that <i>rotating</i> has problems in a document that also loads the <i>float</i> package, which recommended in other answers in these FAQs, for example that on <a href="FAQ-floats.html">float placement</a>. The <i>rotfloat</i> package @@ -43,14 +43,14 @@ rotate the landscape portion using the rotation facilities of the orientation would be somewhat easier: the portrait part of the page would be a bottom float at the end of the landscape section, with its content rotated.) -<p>To set an entire document in landscape orientation, one might use +<p/>To set an entire document in landscape orientation, one might use <i>lscape</i> around the whole document. A better option is the <code>landscape</code> option of the <i>geometry</i> package; if you also give it <code>dvips</code> or <code>pdftex</code> option, <i>geometry</i> also emits the rotation instructions to cause the output to be properly oriented. The <i>memoir</i> class has the same facilities, in this respect, as does <i>geometry</i>. -<p>A word of warning: most current TeX previewers do not honour +<p/>A word of warning: most current TeX previewers do not honour rotation requests in DVI files. @@ -79,5 +79,5 @@ to view these ‘final’ forms with an appropriate viewer. <dt><tt><i>rotfloat.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rotfloat.zip">macros/latex/contrib/rotfloat</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/rotfloat.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/rotfloat/">browse</a>) <dt><tt><i>supertabular.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/supertabular.zip">macros/latex/contrib/supertabular</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/supertabular.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/supertabular/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=landscape">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=landscape</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=landscape">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=landscape</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latex.html index 022e518df26..45ebbff0b07 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latex.html @@ -2,17 +2,17 @@ <title>UK TeX FAQ -- question label latex</title> </head><body> <h3>What is LaTeX?</h3> -<p>LaTeX is a TeX macro package, originally written by Leslie Lamport, that +<p/>LaTeX is a TeX macro package, originally written by Leslie Lamport, that provides a document processing system. LaTeX allows markup to describe the structure of a document, so that the user need not think about presentation. By using document classes and add-on packages, the same document can be produced in a variety of different layouts. -<p>Lamport says that LaTeX +<p/>Lamport says that LaTeX “<em>represents a balance between functionality and ease of use</em>”. This shows itself as a continual conflict that leads to the need for such things as FAQs: LaTeX <em>can</em> meet most user requirements, but finding out <em>how</em> is often tricky. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latex</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latex2e.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latex2e.html index 189dececf96..52101cdbfe6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latex2e.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latex2e.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label latex2e</title> </head><body> <h3>What is LaTeX2e?</h3> -<p>Lamport’s last version of LaTeX (LaTeX 2.09, last updated in 1992) +<p/>Lamport’s last version of LaTeX (LaTeX 2.09, last updated in 1992) was superseded in 1994 by a new version (LaTeX2e) provided by <a href="FAQ-LaTeX3.html">the LaTeX team</a>. LaTeX2e is now the only readily-available version of LaTeX, and draws together several threads of LaTeX development from the later days of LaTeX 2.09. -<p>LaTeX2e has several enhancements over LaTeX 2.09, but they were all +<p/>LaTeX2e has several enhancements over LaTeX 2.09, but they were all rather minor, with a view to continuity and stability rather than the “big push” that some had expected from the team. LaTeX2e continues to this day to offer a compatibility mode in which most @@ -21,6 +21,6 @@ each new release of LaTeX2e). <dl> <dt><tt><i>LaTeX guides and news</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/doc.zip">macros/latex/doc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/doc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/doc/">browse</a>) </dl> -<p><p> +<p/><p/> <p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latex2e">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latex2e</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexbug.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexbug.html index 7673f440e8e..fdc854a2f5d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexbug.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexbug.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label latexbug</title> </head><body> <h3>Reporting a LaTeX bug</h3> -<p>The LaTeX team supports LaTeX, and will deal with +<p/>The LaTeX team supports LaTeX, and will deal with <em>bona fide</em> bug reports. Note that the LaTeX team does <em>not</em> deal with contributed packages — just the software that @@ -11,16 +11,16 @@ is part of the LaTeX distribution itself: LaTeX and the Furthermore, you need to be slightly careful to produce a bug report that is usable by the team. The steps are: -<p><b>1.</b> Are you still using current LaTeX? Maintenance is only +<p/><b>1.</b> Are you still using current LaTeX? Maintenance is only available for sufficiently up-to-date versions of LaTeX — if your LaTeX is more than two versions out of date, the bug reporting mechanisms may reject your report. -<p><b>2.</b> Has your bug already been reported? Browse the +<p/><b>2.</b> Has your bug already been reported? Browse the <a href="http://www.latex-project.org/cgi-bin/ltxbugs2html?introduction=yes">LaTeX bugs database</a>, to find any earlier instance of your bug. In many cases, the database will list a work-around. -<p><b>3.</b> Prepare a +<p/><b>3.</b> Prepare a <a href="FAQ-minxampl.html">“minimum” file</a> that exhibits the problem. Ideally, such a file should contain no contributed packages — the LaTeX team as a whole takes no responsibility for such packages (if @@ -28,12 +28,12 @@ they’re supported at all, they’re supported by their authors). The “minimum” file should be self-sufficient: if a member of the team should run it in a clean directory, on a system with no contributed packages, it should replicate your problem. -<p><b>4.</b> Run your file through LaTeX: the bug +<p/><b>4.</b> Run your file through LaTeX: the bug system needs the <code>.log</code> file that this process creates. -<p>You now have two possible ways to proceed: either create a mail report +<p/>You now have two possible ways to proceed: either create a mail report to send to the bug processing mechanism (5, below), or submit your bug report via the web (7, below). -<p><b>5.</b> Process the bug-report creation file, using LaTeX itself: +<p/><b>5.</b> Process the bug-report creation file, using LaTeX itself: <pre> latex latexbug </pre> @@ -43,12 +43,12 @@ which includes the details you’ve supplied, your “minimum” exa file, and the log file you got after running the example. (I always need to edit the result before submitting it: typing text into <i>latexbug</i> isn’t much fun.) -<p><b>6.</b> Mail the resulting file to +<p/><b>6.</b> Mail the resulting file to <i>latex-bugs@latex-project.org</i>; the subject line of your email should be the same as the bug title you gave to <i>latexbug</i>. The file <i>latexbug.msg</i> should be included into your message in-line: attachments are likely to be rejected by the bug processor. -<p><b>7.</b> Connect to the +<p/><b>7.</b> Connect to the <a href="http://www.latex-project.org/bugs-upload.html">latex bugs processing web page</a> and enter details of your bug — category, summary and full @@ -56,6 +56,6 @@ description, and the two important files (source and log file); note that members of the LaTeX team <em>need</em> your name and email address, as they may need to discuss the bug with you, or to advise you of a work-around. -<p> +<p/> <p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexbug">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexbug</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexpronounce.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexpronounce.html index ede339371fe..d06cf474cee 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexpronounce.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexpronounce.html @@ -3,13 +3,13 @@ </head><body> <h3>How should I pronounce “LaTeX(2e)”?</h3> -<p>Lamport never recommended how one should pronounce LaTeX, but a lot +<p/>Lamport never recommended how one should pronounce LaTeX, but a lot of people pronounce it ‘Lay TeX’ or perhaps ‘Lah TeX’ (with TeX pronounced as the program itself; see <a href="FAQ-TeXpronounce.html">the rules for TeX</a>). It is definitely <em>not</em> to be pronounced in the same way as the rubber-tree gum. -<p>The ‘epsilon’ in ‘LaTeX2e’ is supposed to be suggestive of a small +<p/>The ‘epsilon’ in ‘LaTeX2e’ is supposed to be suggestive of a small improvement over the old LaTeX 2.09. Nevertheless, most people pronounce the name as ‘LaTeX-two-ee’. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexpronounce">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexpronounce</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexpronounce">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexpronounce</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexqual.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexqual.html new file mode 100644 index 00000000000..78840e4638e --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexqual.html @@ -0,0 +1,38 @@ +<head> +<title>UK TeX FAQ -- question label latexqual</title> +</head><body> +<h3>The quality of your LaTeX</h3> +<p/>The <i>l2tabu</i> tutorial (mentioned in +<a href="FAQ-man-latex.html">online introductions</a>) is undoubtedly a +good read. +<p/>However, it’s always difficult to remember the things you should +<em>not</em> do, when there are so many things to remember that you +really must do: some automation is needed.... +<p/>The nicely-named <i>nag</i> allows you to apply a configurable set +of checks to your document, as you run it through LaTeX; you get +messages like: +<blockquote> +<pre> +Package nag Warning: Command \bf is an old LaTeX 2.09 command. +(nag) Use \bfseries or \textbf instead on input line 30. +</pre> + +</blockquote><p> + (the package provides a demo file which contains most of the sorts + of errors you might make — this is one of them). + +<p/>There’s also a web site +<a href="http://www.kohm.name/markus/texidate.html">TeXidate</a> +which will do a static analysis of your document (unfortuantely, you +have to paste your document source into a text window). The site +doesn’t seem as comprehensive as <i>nag</i>, but it allows you to +download its script, which you can then juggle with to make it more +draconian. +<dl> +<dt><tt><i>l2tabu</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/info/l2tabu/">info/l2tabu/</a> for a copy in a language that’s + convenient for you +<dt><tt><i>nag.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/nag.zip">macros/latex/contrib/nag</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/nag.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/nag/">browse</a>) +</dl> +<p/> +<p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexqual">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexqual</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexwords.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexwords.html index e949a3ce475..eae9c92a51f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexwords.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-latexwords.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label latexwords</title> </head><body> <h3>Changing the words <i>babel</i> uses</h3> -<p>LaTeX uses symbolic names for many of the automatically-generated +<p/>LaTeX uses symbolic names for many of the automatically-generated text it produces (special-purpose section headings, captions, etc.). As noted in <a href="FAQ-fixnam.html">“\LaTeX fixed names”</a> (which includes a list of the names themselves), @@ -17,7 +17,7 @@ would expect to place a command {Indholdsfortegnelse} </pre> in the preamble of her document. -<p>However, it’s natural for a user of a non-English language to use +<p/>However, it’s natural for a user of a non-English language to use <i>babel</i>, because it offers many conveniences and typesetting niceties for those preparing documents in those languages. In particular, when <i>babel</i> is selecting a new language, it @@ -25,13 +25,13 @@ ensures that LaTeX’s symbolic names are translated appropriately for the language in question. Unfortunately, <i>babel</i>’s choice of names isn’t always to everyone’s choice, and there is still a need for a mechanism to replace the ‘standard’ names. -<p>Whenever a new language is selected, <i>babel</i> resets all the +<p/>Whenever a new language is selected, <i>babel</i> resets all the names to the settings for that language. In particular, <i>babel</i> selects the document’s main language when <code>\</code><code>begin{document}</code> is executed, which immediately destroys any changes to these symbolic names made in the prologue of a document that uses <i>babel</i>. -<p>Therefore, babel defines a command to enable users to change the +<p/>Therefore, babel defines a command to enable users to change the definitions of the symbolic names, on a per-language basis: <code>\</code><code>addto</code><code>\</code><code>captions</code><code><<i>language</i>></code> is the thing (<code><<i>language</i>></code> being the language option you gave to @@ -42,5 +42,5 @@ definitions of the symbolic names, on a per-language basis: {Indholdsfortegnelse}% } </pre> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexwords">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexwords</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexwords">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=latexwords</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterclass.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterclass.html index 102ccd33d81..8df126797e0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterclass.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterclass.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label letterclass</title> </head><body> <h3>Letters and the like</h3> -<p>LaTeX itself provides a <i>letter</i> document class, which is +<p/>LaTeX itself provides a <i>letter</i> document class, which is widely disliked; the present author long since gave up trying with it. If you nevertheless want to try it, but are irritated by its way of vertically-shifting a single-page letter, try the following hack: @@ -12,22 +12,22 @@ of vertically-shifting a single-page letter, try the following hack: \makeatother </pre> in the preamble of your file. -<p>Doing-it-yourself is a common strategy; Knuth (for use with plain +<p/>Doing-it-yourself is a common strategy; Knuth (for use with plain TeX, in the TeXbook), and Kopka and Daly (in their Guide to LaTeX) offer worked examples. -<p>Nevertheless, there <em>are</em> contributed alternatives — in fact +<p/>Nevertheless, there <em>are</em> contributed alternatives — in fact there are an awfully large number of them: the following list, of necessity, makes but a small selection. -<p>The largest, most comprehensive, class is <i>newlfm</i>; the <code>lfm</code> +<p/>The largest, most comprehensive, class is <i>newlfm</i>; the <code>lfm</code> part of the name implies that the class can create letters, faxes and memoranda. The documentation is voluminous, and the package seems very flexible. -<p>Axel Kielhorn’s <i>akletter</i> class is the only other one, +<p/>Axel Kielhorn’s <i>akletter</i> class is the only other one, recommended for inclusion in this FAQ, whose documentation is available in English. -<p>The <i>dinbrief</i> class, while recommended, is only documented in +<p/>The <i>dinbrief</i> class, while recommended, is only documented in German. -<p>There are letter classes in each of the excellent +<p/>There are letter classes in each of the excellent <i>KOMA-script</i> (<i>scrlttr2</i>: documentation is available in English) and <i>ntgclass</i> (<i>brief</i>: documentation in Dutch only) bundles. While these are probably good (since the bundles @@ -40,5 +40,5 @@ any users. <dt><tt><i>newlfm.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/newlfm.zip">macros/latex/contrib/newlfm</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/newlfm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/newlfm/">browse</a>) <dt><tt><i>scrlttr2.cls</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=letterclass">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=letterclass</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=letterclass">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=letterclass</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterspace.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterspace.html index e8a7dbd27e2..c429fb7ee9e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterspace.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-letterspace.html @@ -2,35 +2,43 @@ <title>UK TeX FAQ -- question label letterspace</title> </head><body> <h3>Changing the space between letters</h3> -<p>A common technique in advertising copy (and other text whose actual +<p/>A common technique in advertising copy (and other text whose actual content need not actually be <em>read</em>) is to alter the space between the letters (otherwise known as the tracking). As a general rule, this is a very bad idea: it detracts from legibility, which is contrary to the principles of typesetting (any respectable font you might be using should already have optimum tracking built into it). -<p>The great type designer, Eric Gill, is credited with saying “he who +<p/>The great type designer, Eric Gill, is credited with saying “he who would letterspace lower-case text, would steal sheep”. (The attribution is probably apocryphal: others are also credited with the remark. Stealing sheep was, in the 19th century, a capital offence in Britain.) As the remark suggests, though, letterspacing of upper-case text is less awful a crime; the technique used also to be used for emphasis of text set in Fraktur (or similar) fonts. -<p>Straightforward macros (usable, in principle, with any TeX macro +<p/>Straightforward macros (usable, in principle, with any TeX macro package) may be found in <i>letterspacing</i> (which is the name of -the <code>.tex</code> file; it also appears as the <i>letterspace</i> package -in some distributions). -<p> +the <code>.tex</code> file). +<p/> -<p>A more comprehensive solution is to be found in the <i>soul</i> +<p/>A more comprehensive solution is to be found in the <i>soul</i> package (which is optimised for use with LaTeX, but also works with Plain TeX). Soul also permits hyphenation of letterspaced text; Gill’s view of such an activity is not (even apocryphally) recorded. (Spacing-out forms part of the name of <i>soul</i>; the other half is described in <a href="FAQ-underline.html">another question</a>.) +<p/>Possibly the ‘ultimate’ in this field is the <i>letterspace</i>, +which uses the micro-typography capabilities of current PDFTeX. +<i>Letterspace</i> expands the natural spacing font itself, rather +than inserting space between characters. Ordinarily, letter-spacing +will destroy ligatures; however, this is <em>wrong</em> if the font is +of a fraktur style. <i>Letterspace</i> provides a means of +protecting the ligatures in a letter-spaced text. <dl> <dt><tt><i>letterspacing.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/misc/letterspacing.tex">macros/generic/misc/letterspacing.tex</a> +<dt><tt><i>letterspace.sty</i></tt><dd>Distributed as part of the <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/microtype.zip">macros/latex/contrib/microtype</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/microtype.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/microtype/">browse</a>) + bundle <dt><tt><i>soul.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/soul.zip">macros/latex/contrib/soul</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/soul.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/soul/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=letterspace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=letterspace</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=letterspace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=letterspace</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-limits.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-limits.html index 895e067b068..c09918b890b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-limits.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-limits.html @@ -2,18 +2,18 @@ <title>UK TeX FAQ -- question label limits</title> </head><body> <h3>Sub- and superscript positioning for operators</h3> -<p>The commonest hand-written style for expressions is to place the limit +<p/>The commonest hand-written style for expressions is to place the limit expressions on operators such as <code>\</code><code>sum</code> and <code>\</code><code>int</code> physically above and below the operator. In (La)TeX, we write these limit expressions using sub- and superscripts applied to the operator, but they don’t always appear in the “handwritten” way in TeX’s output. -<p>The reason is, that when an expression appears in non-display maths, +<p/>The reason is, that when an expression appears in non-display maths, in running text (and is therefore in TeX <code>\</code><code>textstyle</code>), placing the limits thus could lead to ragged line spacing (and hence difficult-to-read text). It is therefore common (in <code>\</code><code>textstyle</code>) to place the limits as one would sub- and superscripts of variables. -<p>This is not universally satisfactory, so the primitive <code>\</code><code>limits</code> is +<p/>This is not universally satisfactory, so the primitive <code>\</code><code>limits</code> is provided: <blockquote> <pre> @@ -22,7 +22,7 @@ $\sum\limits_{n=1}^{m} ...$ </blockquote><p> which will place the limits right above and below the symbol (and be blowed to the typography...). -<p>Contrariwise, you may wish to change the arrangement of the limits +<p/>Contrariwise, you may wish to change the arrangement of the limits when in <code>\</code><code>displaystyle</code>. For this purpose, there’s a corresponding <code>\</code><code>nolimits</code>: <blockquote> @@ -31,7 +31,7 @@ when in <code>\</code><code>displaystyle</code>. For this purpose, there’ </pre> </blockquote><p> which will place the limits as they would be in <code>\</code><code>textstyle</code>. -<p>Alternatively, one can manipulate the +<p/>Alternatively, one can manipulate the <code>\</code><code>textstyle</code>/<code>\</code><code>displaystyle</code> state of the mathematics. To get “<code>\</code><code>limits</code> placement” in inline maths, <blockquote> @@ -49,8 +49,12 @@ and for “<code>\</code><code>nolimits</code> placement” in display m will serve. Either of these forms may have effects other than on the operator you’re considering, but there are still those who prefer this formulation. -<p>(Note that the macro <code>\</code><code>int</code> normally has <code>\</code><code>nolimits</code> built in to +<p/>Remember, if you’re +<a href="FAQ-newfunction.html">declaring a special operator of your own</a>, the +AMSLaTeX functions (that you ought to be using) allow you to choose +how limits are displayed, at definition time. +<p/>(Note that the macro <code>\</code><code>int</code> normally has <code>\</code><code>nolimits</code> built in to its definition. There is an example in the TeXbook to show how odd <code>\</code><code>int</code><code>\</code><code>limits</code> looks when typeset.) -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=limits">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=limits</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=limits">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=limits</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linenos.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linenos.html index 1471cdd3c43..ac06276ba38 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linenos.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linenos.html @@ -2,18 +2,18 @@ <title>UK TeX FAQ -- question label linenos</title> </head><body> <h3>Including line numbers in typeset output</h3> -<p>For general numbering of lines, there are two packages for use with +<p/>For general numbering of lines, there are two packages for use with LaTeX, <i>lineno</i> (which permits labels attached to individual lines of typeset output) and <i>numline</i>. -<p>Both of these packages play fast and loose with the LaTeX output +<p/>Both of these packages play fast and loose with the LaTeX output routine, which can cause problems: the user should beware... -<p>If the requirement is for numbering verbatim text, <i>moreverb</i>, +<p/>If the requirement is for numbering verbatim text, <i>moreverb</i>, <i>memoir</i> or <i>fancyvrb</i> (see <a href="FAQ-verbfile.html">including files verbatim</a>) may be used. -<p>One common use of line numbers is in critical editions of texts, and +<p/>One common use of line numbers is in critical editions of texts, and for this the <i>edmac</i> package offers comprehensive support; <i>ledmac</i> is a LaTeX port of <i>edmac</i>. -<p>The <i>vruler</i> package sidesteps many of the problems associated +<p/>The <i>vruler</i> package sidesteps many of the problems associated with line-numbering, by offering (as its name suggests) a rule that numbers positions on the page. The effect is good, applied to even-looking text, but is poor in texts that involve breaks such as @@ -30,5 +30,5 @@ the package itself, is pretty tough going, though there is an example <dt><tt><i>numline.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/numline/numline.sty">macros/latex/contrib/numline/numline.sty</a> <dt><tt><i>vruler.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/vruler.sty">macros/latex/contrib/misc/vruler.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linenos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linenos</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linenos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linenos</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linespace.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linespace.html index 922fe04f6c6..459a395ed47 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linespace.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linespace.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label linespace</title> </head><body> <h3>Double-spaced documents in LaTeX</h3> -<p>A quick and easy way of getting inter-line space for copy-editing is +<p/>A quick and easy way of getting inter-line space for copy-editing is to change <code>\</code><code>baselinestretch</code> — <code>\</code><code>linespread{1.2}</code> (or, equivalently <code>\</code><code>renewcommand{<code>\</code><code>baselinestretch</code>}{1.2}</code>) may be adequate. Note that <code>\</code><code>baselinestretch</code> changes don’t take @@ -10,7 +10,7 @@ effect until you select a new font, so make the change in the preamble before any font is selected. Don’t try changing <code>\</code><code>baselineskip</code>: its value is reset at any size-changing command so that results will be inconsistent. -<p>For preference (and certainly for a production document, such as a +<p/>For preference (and certainly for a production document, such as a dissertation or an article submission), use a line-spacing package. The only one currently supported is <i>setspace</i> (do <em>not</em> be tempted by <i>doublespace</i> — its performance under current @@ -19,7 +19,7 @@ double-spacing at places where even the most die-hard official would doubt its utility (footnotes, figure captions, and so on); it’s very difficult to do this consistently if you’re manipulating <code>\</code><code>baselinestretch</code> yourself. -<p>Of course, the real solution (other than for private copy editing) is +<p/>Of course, the real solution (other than for private copy editing) is <em>not</em> to use double-spacing at all. Universities, in particular, have no excuse for specifying double-spacing in submitted dissertations: LaTeX is a typesetting system, not a @@ -28,14 +28,14 @@ even more easily readable than double-spaced typewritten text. If you have any influence on your university’s system (for example, through your dissertation supervisor), it may be worth attempting to get the rules changed (at least to permit a “well-designed book” format). -<p>Double-spaced submissions are also commonly required when submitting +<p/>Double-spaced submissions are also commonly required when submitting papers to conferences or journals. Fortunately (judging by the questions from users in this author’s department), this demand is becoming less common. -<p>Documentation of <i>setspace</i> appears as TeX comments in the +<p/>Documentation of <i>setspace</i> appears as TeX comments in the package file itself. <dl> <dt><tt><i>setspace.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/setspace/setspace.sty">macros/latex/contrib/setspace/setspace.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linespace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linespace</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linespace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linespace</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linespread.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linespread.html index a54af3c6b87..79c57fffa0e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linespread.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-linespread.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label linespread</title> </head><body> <h3>Why doesn’t <code>\</code><code>linespread</code> work?</h3> -<p>The command <code>\</code><code>linespread{</code><em>factor</em><code>}</code> is supposed to multiply +<p/>The command <code>\</code><code>linespread{</code><em>factor</em><code>}</code> is supposed to multiply the current <code>\</code><code>baselineskip</code> by <<i>factor</i>>; but, to all appearances, it doesn’t. -<p>In fact, the command is equivalent to +<p/>In fact, the command is equivalent to <code>\</code><code>renewcommand{<code>\</code><code>baselinestretch</code>}{factor}</code>: written that way, it somehow feels less surprising that the effect isn’t immediate. The <code>\</code><code>baselinestretch</code> factor is only used when a font is selected; @@ -35,5 +35,5 @@ linespread changes within a paragraph: read <dl> <dt><tt><i>setspace.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/setspace/setspace.sty">macros/latex/contrib/setspace/setspace.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linespread">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linespread</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linespread">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=linespread</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-lit.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-lit.html index 0fd057a21bd..539033c4fd6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-lit.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-lit.html @@ -2,18 +2,18 @@ <title>UK TeX FAQ -- question label lit</title> </head><body> <h3>What is Literate Programming?</h3> -<p>Literate programming is the combination of documentation and source +<p/>Literate programming is the combination of documentation and source together in a fashion suited for reading by human beings. In general, literate programs combine source and documentation in a single file. Literate programming tools then parse the file to produce either readable documentation or compilable source. The WEB style of literate programming was created by D. E. Knuth during the development of TeX. -<p> - The <a href="FAQ-dtx.html">“documented LaTeX”</a> style of programming +<p/> + The “<a href="FAQ-dtx.html">documented LaTeX</a>” style of programming is regarded by some as a form of literate programming, though it only contains a subset of the constructs Knuth used. -<p>Discussion of literate programming is conducted in the newsgroup +<p/>Discussion of literate programming is conducted in the newsgroup <i>comp.programming.literate</i>, whose FAQ is stored on CTAN. Another good source of information is <a href="http://www.literateprogramming.com/">http://www.literateprogramming.com/</a> @@ -21,5 +21,5 @@ CTAN. Another good source of information is <dt><tt><i>Literate Programming FAQ</i></tt><dd> <a href="ftp://cam.ctan.org/tex-archive/help/comp.programming.literate_FAQ">help/comp.programming.literate_FAQ</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=lit">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=lit</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=lit">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=lit</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-logos.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-logos.html index 0717bba5454..f0e08fac9cc 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-logos.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-logos.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label logos</title> </head><body> <h3>Typesetting all those TeX-related logos</h3> -<p>Knuth was making a particular point about the capabilities of TeX +<p/>Knuth was making a particular point about the capabilities of TeX when he defined the logo. Unfortunately, many believe, he thereby opened floodgates to give the world a whole range of rather silly -‘bumpy road’ logos such as AMSTeX, PiCTeX, BibTeX, and so on, +‘bumpy road’ logos such as AMSTeX, PicTeX, BibTeX, and so on, produced in a flurry of different fonts, sizes, and baselines — indeed, everything one might hope to cause them to obstruct the reading process. In particular, Lamport invented LaTeX @@ -16,7 +16,7 @@ stranger current logo LaTeX2e, which appends a lowered single-stroke Greek letter epsilon. -<p>Sensible users don’t have to follow this stuff wherever it goes, +<p/>Sensible users don’t have to follow this stuff wherever it goes, but, for those who insist, a large collection of logos is defined in the <i>texnames</i> package (but note that this set of macros isn’t entirely reliable in LaTeX2e). @@ -30,17 +30,17 @@ use of the Knuthian font for MetaPost (you might get something like ‘META O T’). You needn’t despair, however — the author himself uses just ‘MetaPost’. -<p>For those who don’t wish to acquire the ‘proper’ logos, the canonical +<p/>For those who don’t wish to acquire the ‘proper’ logos, the canonical thing to do is to say <code>AMS-</code><code>\</code><code>TeX</code> for AMSTeX, <code>Pic</code><code>\</code><code>TeX</code> -for PiCTeX, <code>Bib</code><code>\</code><code>TeX</code> +for PicTeX, <code>Bib</code><code>\</code><code>TeX</code> for BibTeX, and so on. <dl> <dt><tt><i>mflogo.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mflogo.zip">macros/latex/contrib/mflogo</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mflogo.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mflogo/">browse</a>) <dt><tt><i>texnames.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/biblio/texnames.sty">info/biblio/texnames.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=logos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=logos</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=logos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=logos</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-lollipop.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-lollipop.html index b1a4659f01c..ec9d1b7a1a8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-lollipop.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-lollipop.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label lollipop</title> </head><body> <h3>What is Lollipop?</h3> -<p>Lollipop is a macro package written by Victor Eijkhout; it was used in +<p/>Lollipop is a macro package written by Victor Eijkhout; it was used in the production of his book “<em>TeX by Topic</em>” (see <a href="FAQ-ol-books.html">(La)TeX Tutorials</a>). The manual says of it: @@ -14,18 +14,18 @@ it: an average document, and that it would be a task that could be accomplished by someone with only a very basic training in TeX programming. -<p> Lollipop is an attempt to make structured text formatting available +<p/> Lollipop is an attempt to make structured text formatting available for environments where previously only WYSIWYG packages could be used because adapting the layout is so much more easy with them than with traditional TeX macro packages. </blockquote><p> -<p>The manual goes on to talk of ambitions to “capture some of the +<p/>The manual goes on to talk of ambitions to “capture some of the LaTeX market share”; it’s a very witty package, but little sign of it taking over from LaTeX is detectable... An article about Lollipop appeared in <i>TUGboat</i> 13(3). <dl> -<dt><tt><i>Lollipop distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/macros/lollipop.zip">nonfree/macros/lollipop</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/macros/lollipop.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/macros/lollipop/">browse</a>) +<dt><tt><i>Lollipop distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/lollipop.zip">macros/lollipop</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/lollipop.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/lollipop/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=lollipop">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=lollipop</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=lollipop">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=lollipop</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-longtab.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-longtab.html index d55fbe8226f..fabb6d164aa 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-longtab.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-longtab.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label longtab</title> </head><body> <h3>Tables longer than a single page</h3> -<p>Tables are, by default, set entirely in boxes of their own: as a +<p/>Tables are, by default, set entirely in boxes of their own: as a result, they won’t split over a page boundary. Sadly, the world keeps turning up tables longer than a single page that we need to typeset. -<p>For simple tables (whose shape is highly regular), the simplest +<p/>For simple tables (whose shape is highly regular), the simplest solution may well be to use the <code>tabbing</code> environment, which is slightly tedious to set up, but which doesn’t force the whole aligment onto a single page. -<p>The <i>longtable</i> package builds the whole table (in chunks), in +<p/>The <i>longtable</i> package builds the whole table (in chunks), in a first pass, and then uses information it has written to the <code>.aux</code> file during later passes to get the setting “right” (the package ordinarily manages to set tables in just two passes). Since the @@ -28,7 +28,7 @@ should be in a file of its own, and included by multiple-page tables can’t possibly live inside floats, the package provides for captions within the <code>longtable</code> environment itself. -<p>A seeming alternative to <i>ltxtable</i> is <i>ltablex</i>; but +<p/>A seeming alternative to <i>ltxtable</i> is <i>ltablex</i>; but it is outdated and not fully functional. Its worst problem is its strictly limited memory capacity (<i>longtable</i> is not so limited, at the cost of much complication in its code); @@ -36,25 +36,25 @@ limited, at the cost of much complication in its code); likely that support is available; but its user interface is much simpler than <i>ltxtable</i>, so if its restrictions aren’t a problem for you, it may be worth a try. -<p>The <i>supertabular</i> package starts and stops a +<p/>The <i>supertabular</i> package starts and stops a <code>tabular</code> environment for each page of the table. As a result, each ‘page worth’ of the table is compiled independently, and the widths of corresponding columns may differ on successive pages. However, if the correspondence doesn’t matter, or if your columns are fixed-width, <i>supertabular</i> has the great advantage of doing its job in a single run. -<p>Both <i>longtable</i> and <i>supertabular</i> allow definition +<p/>Both <i>longtable</i> and <i>supertabular</i> allow definition of head- and footlines for the table; <i>longtable</i> allows distinction of the first and last head and foot. -<p>The <i>xtab</i> package fixes some infelicities of +<p/>The <i>xtab</i> package fixes some infelicities of <i>supertabular</i>, and also provides a “last head” facility (though this, of course, destroys <i>supertabular</i>’s advantage of operating in a single run). -<p>The <i>stabular</i> package provides a simple-to-use “extension to +<p/>The <i>stabular</i> package provides a simple-to-use “extension to <code>tabular</code>” that allows it to typeset tables that run over the end of a page; it also has usability extensions, but doesn’t have the head- and footline capabilities of the major packages. -<p>Documentation of <i>ltablex</i> is to be found in the package file. +<p/>Documentation of <i>ltablex</i> is to be found in the package file. <dl> <dt><tt><i>longtable.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) <dt><tt><i>ltablex.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ltablex/ltablex.sty">macros/latex/contrib/ltablex/ltablex.sty</a> @@ -63,5 +63,5 @@ the head- and footline capabilities of the major packages. <dt><tt><i>supertabular.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/supertabular.zip">macros/latex/contrib/supertabular</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/supertabular.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/supertabular/">browse</a>) <dt><tt><i>xtab.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xtab.zip">macros/latex/contrib/xtab</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xtab.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xtab/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=longtab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=longtab</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=longtab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=longtab</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxabbrv.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxabbrv.html index 0fba285df84..0602a30cfc6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxabbrv.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxabbrv.html @@ -2,17 +2,17 @@ <title>UK TeX FAQ -- question label ltxabbrv</title> </head><body> <h3>LaTeX internal “abbreviations”, etc.</h3> -<p>In the deeps of time, when TeX first happened, computers had +<p/>In the deeps of time, when TeX first happened, computers had extremely limited memory, and were (by today’s standards) painfully slow. When LaTeX came along, things weren’t much better, and even when LaTeX2e appeared, there was a strong imperative to save memory space (and to a lesser extent) CPU time. -<p>From the very earliest days, Knuth used shortcut macros to speed +<p/>From the very earliest days, Knuth used shortcut macros to speed things up. LaTeX, over the years, has extended Knuth’s list by a substantial amount. An interesting feature of the “abbreviations” is that on paper, they may look longer than the thing they stand for; -however, to (La)TeX they <em>feel</em> smaller\dots -<p>The table at the end of this answer lists the commonest of these +however, to (La)TeX they <em>feel</em> smaller... +<p/>The table at the end of this answer lists the commonest of these “abbreviations”. It is not complete; as always, if the table doesn’t help, try the LaTeX source. The table lists each abbreviation’s <em>name</em> and its <em>value</em>, which provide most of @@ -20,7 +20,7 @@ what a user needs to know. The table also lists the abbreviation’s <em>type</em>, which is a trickier concept: if you need to know, the only real confusion is that the abbreviations labelled ‘defn’ are defined using an <code>\</code><code><em>xxx</code>def</em> command. -<p><table rules="groups" border="0" cellpadding="3"><tbody><tr><td> +<p/><table rules="groups" border="0" cellpadding="3"><tbody><tr><td> Name <td> Type <td> Value <tr><td> </tbody><tbody><tr><td> <code>\</code><code>m@ne</code> <td> count <td> -1 <tr><td> @@ -55,5 +55,5 @@ Name <td> Type <td> Value <tr><td> <code>\</code><code>@minus</code> <td> macro <td> “<code>minus</code>” <tr><td> </tbody></table> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxabbrv">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxabbrv</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxabbrv">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxabbrv</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxcmds.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxcmds.html index 40d9ce5bb68..af41f3f0733 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxcmds.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxcmds.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label ltxcmds</title> </head><body> <h3>The definitions of LaTeX commands</h3> -<p>There are several reasons to want to know the definitions of LaTeX +<p/>There are several reasons to want to know the definitions of LaTeX commands: from the simplest “idle curiosity”, to the pressing need to patch something to make it “work the way you want it”. None of these are <em>pure</em> motives, but knowledge and expertise seldom arrive through the purest of motives. -<p>The simple answer is to try <code>\</code><code>show</code>, in a run of LaTeX that is +<p/>The simple answer is to try <code>\</code><code>show</code>, in a run of LaTeX that is taking commands from the terminal: <blockquote> <pre> @@ -32,7 +32,7 @@ TeX itself produces.) We may perhaps, now, wonder about and we’re starting to see how one part of the <code>\</code><code>protect</code>ion mechanism works (one can probably fairly safely guess what <code>\</code><code>restore@protect</code> does). -<p>Many kernel commands are declared robust: +<p/>Many kernel commands are declared robust: <blockquote> <pre> *\show\texttt @@ -56,11 +56,11 @@ shown below, and use that instead: Note that the command name that is protected is the ‘base’ command, with a space appended. This is cryptically visible, in a couple of places above. (Again, the output has been sanitised.) -<p>If one has a malleable text editor, the same investigation may more +<p/>If one has a malleable text editor, the same investigation may more comfortably be conducted by examining the file <i>latex.ltx</i> (which is usually to be found, in a TDS system, in directory <i>tex/latex/base</i>). -<p>In fact, <i>latex.ltx</i> is the product of a <i>docstrip</i> +<p/>In fact, <i>latex.ltx</i> is the product of a <i>docstrip</i> process on a large number of <a href="FAQ-dtx.html"><code>.dtx</code> files</a>, and you can refer to those instead. The LaTeX distribution includes a file <i>source2e.tex</i>, and most systems retain it, again in @@ -71,13 +71,13 @@ advising you what to do). The result is a huge document, with a line-number index of control sequences the entire kernel and a separate index of changes recorded in each of the files since the LaTeX team took over. -<p>The printed kernel is a nice thing to have, but it’s unwieldy and sits +<p/>The printed kernel is a nice thing to have, but it’s unwieldy and sits on my shelves, seldom used. One problem is that the comments are patchy: the different modules range from well and lucidly documented, through modules documented only through an automatic process that converted the documentation of the source of LaTeX 2.09, to modules that hardly had any useful documentation even in the LaTeX 2.09 original. -<p>In fact, each kernel module <code>.dtx</code> file will process separately +<p/>In fact, each kernel module <code>.dtx</code> file will process separately through LaTeX, so you don’t have to work with the whole of <i>source2e</i>. You can easily determine which module defines the macro you’re interested in: use your “malleable text editor” to find @@ -94,7 +94,7 @@ in. Doing this for <code>\</code><code>protected@edef</code>, we find: When we come to look at it, <i>ltdefns.dtx</i> proves to contain quite a dissertation on the methods of handling <code>\</code><code>protect</code>ion; it also contains some automatically-converted LaTeX 2.09 documentation. -<p>And of course, the kernel isn’t all of LaTeX: your command may be +<p/>And of course, the kernel isn’t all of LaTeX: your command may be defined in one of LaTeX’s class or package files. For example, we find a definition of <code>\</code><code>thebibliography</code> in <i>article</i>, but there’s no <i>article.dtx</i>. Some such files are generated from @@ -113,10 +113,10 @@ we find: </blockquote><p> so we need to format <i>classes.dtx</i> to see the definition in context. -<p>All these .dtx files are on CTAN as part of the main LaTeX +<p/>All these .dtx files are on CTAN as part of the main LaTeX distribution. <dl> <dt><tt><i>LaTeX distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.zip">macros/latex/base</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxcmds">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxcmds</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxcmds">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxcmds</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxhash.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxhash.html index a733f758907..0e3d777727f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxhash.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ltxhash.html @@ -2,18 +2,18 @@ <title>UK TeX FAQ -- question label ltxhash</title> </head><body> <h3>Defining LaTeX commands within other commands</h3> -<p>LaTeX command definition is significantly different from the TeX +<p/>LaTeX command definition is significantly different from the TeX primitive form discussed in an <a href="FAQ-hash.html">earlier question</a> about definitions within macros. -<p>In most ways, the LaTeX situation is simpler (at least in part +<p/>In most ways, the LaTeX situation is simpler (at least in part because it imposes more restrictions on the user); however, defining a command within a command still requires some care. -<p>The earlier question said you have to double the <code>#</code> signs in command +<p/>The earlier question said you have to double the <code>#</code> signs in command definitions: in fact, the same rule holds, except that LaTeX already takes care of some of the issues, by generating argument lists for you. -<p>The basic problem is that: +<p/>The basic problem is that: <blockquote> <pre> \newcommand{\abc}[1]{joy, oh #1!% @@ -30,7 +30,7 @@ followed by a call: typesets “joy, oh joy!”, but defines a command <code>\</code><code>ghi</code> that takes one parameter, which it ignores; <code>\</code><code>ghi{gloom}</code> will expand to “gloom, oh joy!”, which is presumably not what was expected. -<p>And (as you will probably guess, if you’ve read the earlier question) +<p/>And (as you will probably guess, if you’ve read the earlier question) the definition: <blockquote> <pre> @@ -41,7 +41,7 @@ the definition: </blockquote><p> does what is required, and <code>\</code><code>ghi{gloom}</code> will expand to “gloom, oh gloom!”, whatever the argument to <code>\</code><code>abc</code>. -<p>The doubling is needed whether or not the enclosing command has an +<p/>The doubling is needed whether or not the enclosing command has an argument, so: <blockquote> <pre> @@ -51,5 +51,5 @@ argument, so: </pre> </blockquote><p> is needed to produce a replica of the <code>\</code><code>ghi</code> we defined earlier. -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxhash">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxhash</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxhash">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ltxhash</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-luatex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-luatex.html index 762ace63127..ad6ba02ce6a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-luatex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-luatex.html @@ -1,21 +1,23 @@ <head> <title>UK TeX FAQ -- question label luatex</title> </head><body> -<h3>PDFTeX becomes LUATeX</h3> -<p>As is said elsewhere in these FAQs, development of +<h3>PDFTeX becomes LuaTeX</h3> +<p/>As is said elsewhere in these FAQs, development of <a href="FAQ-whatpdftex.html">PDFTeX</a> is “in essence” complete — development of new facilities continues, but the limitations of the present structure impose a strong limit on what facilities are possible. -<p>Thus arose the idea of LUATeX. LUA is a script -language, chosen because its interpreter has a very small +<p/>In this context, the idea of LuaTeX arose. +<a href="http://www.lua.org/"><i>Lua</a></i> is a script +language, designed to offer an interpreter with a very small “footprint”, so it is rather easy to build it into other -applications. So LUATeX was launched as a PDFTeX -executable with a LUA interpreter built into it. -<p>The LUATeX project is now proceeding (with monetary support -from various sources) and is pursuing avenues that many of the other +applications. So LuaTeX was launched as a PDFTeX +executable with a <i>Lua</i> interpreter built into it. +<p/>A <a href="http://www.luatex.org/">LuaTeX project</a> is now proceeding +(with monetary support from various sources) and is pursuing avenues +that many of the other current projects have in their sights, notably Unicode character representations and support for OpenType fonts. Work is also in hand to integrate the extensions pioneered by <a href="FAQ-omegaleph.html">Aleph</a>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=luatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=luatex</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=luatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=luatex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mailliststar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mailliststar.html index 47afee4ea91..c44c1de89f7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mailliststar.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mailliststar.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label maillists*</title> </head><body> <h3>Specialist mailing lists</h3> -<p>The previous question, “<a href="FAQ-gethelp.html">getting help</a>”, talked of +<p/>The previous question, “<a href="FAQ-gethelp.html">getting help</a>”, talked of the two major forums in which (La)TeX, Metafont and MetaPost are discussed; however, these aren’t the only ones available. -<p>The TUG web site offers many mailing lists other than just +<p/>The TUG web site offers many mailing lists other than just <code>texhax</code> via its <a href="http://tug.org/mailman/listinfo">mail list management page</a>. -<p>The French national TeX user group, Gutenberg, offers a Metafont (and, +<p/>The French national TeX user group, Gutenberg, offers a Metafont (and, de facto, MetaPost) mailing list, <a href="mailto:metafont@ens.fr"><i>metafont@ens.fr</i></a>: subscribe to it by sending a message <blockquote> @@ -17,10 +17,10 @@ subscribe metafont </pre> </blockquote><p> to <a href="mailto:sympa@ens.fr"><i>sympa@ens.fr</i></a> -<p>Note that there’s also a MetaPost-specific mailing list available via the +<p/>(Note that there’s also a MetaPost-specific mailing list available via the TUG lists; in fact there’s little danger of becoming confused -by subscribing to both. -<p>Announcements of TeX-related installations on the CTAN +by subscribing to both.) +<p/>Announcements of TeX-related installations on the CTAN archives are sent to the mailing list <code>ctan-ann</code>. Subscribe to the list via its <i>MailMan</i> web-site <a href="https://lists.dante.de/mailman/listinfo/ctan-ann">https://lists.dante.de/mailman/listinfo/ctan-ann</a>; list archives @@ -28,5 +28,5 @@ are available at the same address. The list archives may also be browsed via <a href="http://www.mail-archive.com/ctan-ann@dante.de/">http://www.mail-archive.com/ctan-ann@dante.de/</a>, and an RSS feed is also available: <a href="http://www.mail-archive.com/ctan-ann@dante.de/maillist.xml">http://www.mail-archive.com/ctan-ann@dante.de/maillist.xml</a> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=maillists*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=maillists*</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=maillists*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=maillists*</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-make.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-make.html index 9b4efe95361..18971011cad 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-make.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-make.html @@ -2,37 +2,49 @@ <title>UK TeX FAQ -- question label make</title> </head><body> <h3>Makefiles for LaTeX documents</h3> -<p>LaTeX is a tricky beast for running <i>make</i> on: the need to +<p/>LaTeX is a tricky beast for running <i>make</i> on: the need to instruct LaTeX to run several times for essentially different reasons (for example, “get the table of contents stable”, “get the labels stable”, “add the bibliography”, “add the index”) is actually rather difficult to express in the ‘ordinary’ sort of dependency graph that one constructs for <i>make</i>. -<p>For this reason, the only <i>make</i>-like package on CTAN +<p/>For this reason, the only <i>make</i>-like package on CTAN (for a long time) was <i>latexmk</i>, which is a <i>Perl</i> script that analyses your LaTeX source for its dependencies, runs BibTeX or <i>makeindex</i> as and when it notices that those -programs’ input (parts of the <code>.aux</code> file, or the <code>.idx</code> file, -respectively) has changed, and so on. <i>Latexmk</i> is a fine +programs’ input (parts of the <code>.aux</code> file, or the +<code>.idx</code> file, respectively) has changed, and so on. +<i>Latexmk</i> is a fine solution (and was used in generating printable versions of these FAQs for a long time); it has recently been upgraded and has many bells and whistles that allow it to operate as if it were a poor man’s WYSIWYG system. -<p>The <a href="FAQ-texinfo.html"><i>texinfo</i> system</a> comes with a +<p/>Apparently along the same lines, and currently (2007) under active +development, is AutoLaTeX. The <i>README</i> of the distribution is +actual a Unix-type man-page output, and shows great attention to the +details of the document production process. +<p/>Windows users of the MiKTeX system may use that systems +<i>texify</i> application. <i>Texify</i> deals with basic +LaTeX features, including generating a bibliography and an index; +it makes no claim to deal with other things (such as multiple +bibliographies or indexes, or lists of terminology, etc.), which +AutoLaTeX can be configured to process. +<p/>The <a href="FAQ-texinfo.html"><i>texinfo</i> system</a> comes with a similar utility called <i>texi2dvi</i>, which is capable of “converting” either LaTeX or <i>texinfo</i> files into DVI (or into PDF, using PDFTeX). -<p>A later contribution is the bundle <i>latexmake</i>, which +<p/>A later contribution is the bundle <i>latexmake</i>, which offers a set of <i>make</i> rules that invoke <i>texi2dvi</i> as necessary. -<p>The curious may examine the rules employed to run the present +<p/>The curious may examine the rules employed to run the present FAQ through LaTeX: we don’t present them as a complete solution, but some of the tricks employed are surely re-usable. <dl> +<dt><tt><i>AutoLaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/autolatex.zip">support/autolatex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/autolatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/autolatex/">browse</a>) <dt><tt><i>FAQ distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.zip">help/uk-tex-faq</a> (<a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/">browse</a>) <dt><tt><i>latexmake</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/latexmake.zip">support/latexmake</a> (<a href="ftp://cam.ctan.org/tex-archive/support/latexmake.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/latexmake/">browse</a>) <dt><tt><i>latexmk</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/latexmk.zip">support/latexmk</a> (<a href="ftp://cam.ctan.org/tex-archive/support/latexmk.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/latexmk/">browse</a>) <dt><tt><i>texi2dvi</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/texinfo/texinfo.zip">macros/texinfo/texinfo</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/texinfo/texinfo.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/texinfo/texinfo/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=make">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=make</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=make">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=make</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-makebib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-makebib.html index b22b0945c50..80fafa4181e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-makebib.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-makebib.html @@ -2,21 +2,21 @@ <title>UK TeX FAQ -- question label makebib</title> </head><body> <h3>Reconstructing <code>.bib</code> files</h3> -<p>Perhaps you’ve lost the <code>.bib</code> file you generated your document from, +<p/>Perhaps you’ve lost the <code>.bib</code> file you generated your document from, or have been sent a document without one. Or even, you’ve realised the error of building a substantial document without the benefit of BibTeX... -<p>The <i>Perl</i> script, <i>tex2bib</i> makes a reasonable job +<p/>The <i>Perl</i> script, <i>tex2bib</i> makes a reasonable job of regenerating <code>.bib</code> files from <code>thebibliography</code> environments, provided that the original (whether automatically or manually generated) doesn’t deviate too far from the “standard” styles. -<p>You are well-advised to check the output of the script. While it will +<p/>You are well-advised to check the output of the script. While it will not usually destroy information, it can quite reasonably mislabel it. -<p>Documentation of the script is to be found in the file <i>tex2bib.readme</i> +<p/>Documentation of the script is to be found in the file <i>tex2bib.readme</i> <dl> <dt><tt><i>tex2bib</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/tex2bib/tex2bib">biblio/bibtex/utils/tex2bib/tex2bib</a> <dt><tt><i>tex2bib.readme</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/utils/tex2bib/README">biblio/bibtex/utils/tex2bib/README</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=makebib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=makebib</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=makebib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=makebib</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-makeindex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-makeindex.html index 4cb88a99c35..f0a1f6ca76d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-makeindex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-makeindex.html @@ -2,19 +2,19 @@ <title>UK TeX FAQ -- question label makeindex</title> </head><body> <h3>Generating an index in (La)TeX</h3> -<p>Making an index is not trivial; what to index, and how to index it, is +<p/>Making an index is not trivial; what to index, and how to index it, is difficult to decide, and uniform implementation is difficult to achieve. You will need to mark all items to be indexed in your text (typically with <code>\</code><code>index</code> commands). -<p>It is not practical to sort a large index within TeX, so a +<p/>It is not practical to sort a large index within TeX, so a post-processing program is used to sort the output of one TeX run, to be included into the document at the next run. -<p>The following programs are available: +<p/>The following programs are available: <dl> <dt>makeindex<dd> Comes with most distributions — a good workhorse, but is not well-arranged to deal with other sort orders than the canonical ASCII ordering. -<p> The <i>makeindex</i> documentation is a good source of +<p/> The <i>makeindex</i> documentation is a good source of information on how to create your own index. <i>Makeindex</i> can be used with some TeX macro packages other than LaTeX, such as @@ -24,7 +24,7 @@ to be included into the document at the next run. glossary-maker called <i>glotex</i>. <dt>texindex<dd> A witty little shell/<i>sed</i>-script-based utility for LaTeX under Unix. -<p> The <a href="FAQ-texinfo.html">Texinfo</a> system also uses a program +<p/> The <a href="FAQ-texinfo.html">Texinfo</a> system also uses a program <i>texindex</i>, whose source is to be found in the <i>texinfo</i> distribution. The <i>ltxindex</i> package provides macros to allow LaTeX users to use <em>this</em> @@ -49,5 +49,5 @@ to be included into the document at the next run. <dt><tt><i>texsis (makeindex support)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/texsis/index/index.tex">macros/texsis/index/index.tex</a> <dt><tt><i>xindy</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/support/xindy/">support/xindy/</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=makeindex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=makeindex</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=makeindex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=makeindex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-latex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-latex.html index 82eb49440c1..afd067857f7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-latex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-latex.html @@ -2,42 +2,45 @@ <title>UK TeX FAQ -- question label man-latex</title> </head><body> <h3>Online introductions: LaTeX</h3> -<p>Tobias Oetiker’s ‘(Not so) Short Introduction to LaTeX2e’, is +<p/>Tobias Oetiker’s ‘(Not so) Short Introduction to LaTeX2e’, is regularly updated, as people suggest better ways of explaining things, etc. The introduction is available on CTAN, together with translations into a rather large set of languages. -<p>Peter Flynn’s “Beginner’s LaTeX” (which also started as course +<p/>Peter Flynn’s “Beginner’s LaTeX” (which also started as course material) is a pleasing read. A complete copy may be found on CTAN, but it may also be browsed over the web (<a href="http://www.tex.ac.uk/tex-archive/info/beginlatex/html/">http://www.tex.ac.uk/tex-archive/info/beginlatex/html/</a>). -<p>Harvey Greenberg’s ‘Simplified Introduction to LaTeX’ was written +<p/>Harvey Greenberg’s ‘Simplified Introduction to LaTeX’ was written for a lecture course, and is also available on CTAN (in PostScript only, unfortunately). -<p>Edith Hodgen’s +<p/>The fourth edition of George Grätzer’s book “Math into LaTeX” +contains a “short course” in LaTeX itself, and that course has +been made publicly available on CTAN. +<p/>Edith Hodgen’s <a href="http://www.mcs.vuw.ac.nz/~david/latex/notes.pdf">LaTeX, a Braindump</a> starts you from the ground up — giving a basic tutorial in the use of <i>Linux</i> to get you going (rather a large file...). Its parent site, David Friggens’ <a href="http://www.mcs.vuw.ac.nz/~david/latex/">documentation page</a> is a useful collection of links in itself. -<p> +<p/> <a href="http://www.andy-roberts.net/misc/latex/">Andy Roberts’ introductory material</a> is a pleasing short introduction to the use of (La)TeX; some of the slides for <em>actual</em> tutorials are to be found on the page, as well. -<p>Chris Harrison’s +<p/>Chris Harrison’s <a href="http://www.chrisharrison.co.uk/xophbook/mybooks/tex/index.html">TeX book</a> presents basic LaTeX with useful hints for extensions -<p>Nicola Talbot’s +<p/>Nicola Talbot’s <a href="http://theoval.cmp.uea.ac.uk/~nlct/latex/novices/novices.html">LaTeX for complete novices</a> does what it claims: the author teaches LaTeX at the University of -East Anglia. -<p>Nicola Talbot also provides a set of +East Anglia. That is one of several of Nicola’s <a href="http://theoval.cmp.uea.ac.uk/~nlct/latex/">introductory tutorials</a>, -which include exercises (with solutions). The page was developed as -an extension to the LaTeX course Nicola teaches at the University -of East Anglia. -<p>An interesting (and practical) tutorial about what <em>not</em> to do is +which include exercises (with solutions). Other tutorials include +those for writing theses/dissertations with LaTeX, and for using +LaTeX in administrative work. (The page seems to be an adjunct to +her LaTeX courses — fortunate people, the people of UEA!). +<p/>An interesting (and practical) tutorial about what <em>not</em> to do is <i>l2tabu</i>, or “A list of sins of LaTeX2e users” by Mark Trettin, translated into English by Jürgen Fenn. The tutorial is available from CTAN as a PDF file (though @@ -48,9 +51,10 @@ the source is also available). (in English, you may browse for sources and other language versions at <a href="http://www.tex.ac.uk/tex-archive/info/lshort/">info/lshort/</a>) <dt><tt><i>Simplified LaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/simplified-latex/simplified-intro.ps">info/simplified-latex/simplified-intro.ps</a> +<dt><tt><i>Short Course in LaTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/Math_into_LaTeX-4/Short_Course.pdf">info/Math_into_LaTeX-4/Short_Course.pdf</a> <dt><tt><i>The sins of LaTeX users</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/l2tabu/english/l2tabuen.pdf">info/l2tabu/english/l2tabuen.pdf</a>; source also available: <a href="ftp://cam.ctan.org/tex-archive/info/l2tabu/english/l2tabuen.tex">info/l2tabu/english/l2tabuen.tex</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-latex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-latex</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-latex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-latex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-tex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-tex.html index 284171ca500..7b021ea561e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-tex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-man-tex.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label man-tex</title> </head><body> <h3>Online introductions: Plain TeX</h3> -<p>Michael Doob’s splendid ‘Gentle Introduction’ to Plain TeX +<p/>Michael Doob’s splendid ‘Gentle Introduction’ to Plain TeX (available on CTAN) has been stable for a very long time. -<p>Another recommendable document is D. R. Wilkins ‘Getting started with TeX’, +<p/>Another recommendable document is D. R. Wilkins ‘Getting started with TeX’, available on the web at <a href="http://www.ntg.nl/doc/wilkins/pllong.pdf">http://www.ntg.nl/doc/wilkins/pllong.pdf</a> <dl> <dt><tt><i>Gentle Introduction</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/gentle/gentle.pdf">info/gentle/gentle.pdf</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-tex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-tex</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-tex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=man-tex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-manyauthor.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-manyauthor.html index 18831b01224..8828376fbf1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-manyauthor.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-manyauthor.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label manyauthor</title> </head><body> <h3>BibTeX doesn’t understand lists of names</h3> -<p>BibTeX has a strict syntax for lists of authors’ (or editors’) +<p/>BibTeX has a strict syntax for lists of authors’ (or editors’) names in the BibTeX data file; if you write the list of names in a “natural”-seeming way, the chances are you will confuse BibTeX, and the output produced will be quite different from what you had hoped. -<p>Names should be expressed in one of the forms +<p/>Names should be expressed in one of the forms <blockquote> <pre> First Last @@ -52,5 +52,5 @@ distract attention from his co-authors, he would write: AUTHOR = {Fred Q. Bloggs and others} </pre> </blockquote><p> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manyauthor">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manyauthor</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manyauthor">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manyauthor</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-manymathalph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-manymathalph.html index a0b87651471..349ad41cd8d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-manymathalph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-manymathalph.html @@ -2,22 +2,22 @@ <title>UK TeX FAQ -- question label manymathalph</title> </head><body> <h3>Too many math alphabets</h3> -<p>TeX mathematics is one of its most impressive features, yet the +<p/>TeX mathematics is one of its most impressive features, yet the internal structure of the mechanism that produces it is painfully complicated and (in some senses) pathetically limited. One area of limitation is that one is only allowed 16 ”maths alphabets” -<p>LaTeX offers the user quite a lot of flexibility with allocating +<p/>LaTeX offers the user quite a lot of flexibility with allocating maths alphabets, but few people use the flexibility directly. Nevertheless, there are many packages that provide symbols, or that manipulate them, which allocate themselves one or more maths alphabet. -<p>If you can’t afford to drop any of these packages, there’s +<p/>If you can’t afford to drop any of these packages, there’s still hope if you’re using the <i>bm</i> package to support <a href="FAQ-boldgreek.html">bold maths</a>: <i>bm</i> is capable of gobbling alphabets as if there is no tomorrow. The package defines two limiter commands: <code>\</code><code>bmmax</code> (for <em>bold</em> symbols; default 4) and <code>\</code><code>hmmax</code> (for <em>heavy</em> symbols, if you have them; default 3), which control the number of alphabets to be used. -<p>Any reduction of the <code>\</code><code><em>xx</code>max</em> variables will slow +<p/>Any reduction of the <code>\</code><code><em>xx</code>max</em> variables will slow <i>bm</i> down — but that’s surely better than the document not running at all. So unless you’re using maths fonts (such as <i>Mathtime Plus</i>) that feature a heavy symbol weight, suppress all @@ -37,5 +37,5 @@ until (with a bit of luck) the error goes away. <dl> <dt><tt><i>bm.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manymathalph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manymathalph</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manymathalph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=manymathalph</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginmanual.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginmanual.html index ef5873fa7d8..55669eb2d3c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginmanual.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginmanual.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label marginmanual</title> </head><body> <h3>How to set up page layout “by hand”</h3> -<p>So you’re eager to do it yourself, notwithstanding the cautions +<p/>So you’re eager to do it yourself, notwithstanding the cautions outlined in “<a href="FAQ-changemargin.html">changing margins</a>”. -<p>It’s important that you first start by familiarising yourself +<p/>It’s important that you first start by familiarising yourself with LaTeX’s page layout parameters. For example, see section C.5.3 of the LaTeX manual (pp. 181-182), or corresponding sections in many of the other good LaTeX manuals (see <a href="FAQ-books.html">LaTeX books</a>). -<p>LaTeX controls the page layout with a number of parameters, which +<p/>LaTeX controls the page layout with a number of parameters, which allow you to change the distance from the edges of a page to the left and top edges of your typeset text, the width and height of the text, and the placement of other text on the page. However, they are @@ -17,13 +17,13 @@ somewhat complex, and it is easy to get their interrelationships wrong when redefining the page layout. The layout package defines a <code>\</code><code>layout</code> command which draws a diagram of your existing page layout, with the dimensions (but not their interrelationships) shown. -<p>Even changing the text height and width, <code>\</code><code>textheight</code> and +<p/>Even changing the text height and width, <code>\</code><code>textheight</code> and <code>\</code><code>textwidth</code>, requires more care than you might expect: the height should be set to fit a whole number of text lines (in terms of multiples of <code>\</code><code>baselinskip</code>), and the width should be constrained by the number of characters per line, as mentioned in “<a href="FAQ-changemargin.html">changing margins</a>”. -<p>Margins are controlled by two parameters: <code>\</code><code>oddsidemargin</code> and +<p/>Margins are controlled by two parameters: <code>\</code><code>oddsidemargin</code> and <code>\</code><code>evensidemargin</code>, whose names come from the convention that odd-numbered pages appear on the right-hand side (‘recto’) of a two-page spread and even-numbered pages on the left-hand side @@ -33,7 +33,7 @@ implication, from the value of <code>\</code><code>textwidth</code> and the widt paper. (In a one-sided document, which is the default in many classes, including the standard <i>article</i> and <i>report</i> classes, <code>\</code><code>oddsidemargin</code> stands for both.) -<p>The +<p/>The “origin” (the zero position) on the page is one inch from the top of the paper and one inch from the left side; positive horizontal measurements extend right across the page, and positive vertical @@ -42,5 +42,5 @@ measurements extend down the page. Thus, the parameters be set to be 1 inch less than the true margin; for margins closer to the left and top edges of the page than 1 inch, the margin parameters must be set to negative values. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginmanual">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginmanual</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginmanual">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginmanual</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginparside.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginparside.html index 2a29ccbb504..47a3f431d65 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginparside.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginparside.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label marginparside</title> </head><body> <h3>Getting <code>\</code><code>marginpar</code> on the right side</h3> -<p>In an ideal world, marginal notes would be in “analagous” places on +<p/>In an ideal world, marginal notes would be in “analagous” places on every page: notes on an even-side page would be in the left margin, while those on an odd-side page would be in the right margin. A moment’s thought shows that a marginal note on the left needs to be @@ -19,7 +19,7 @@ up on the wrong side of the page. This is an instance of a general problem: see “<a href="FAQ-oddpage.html">finding if you’re on an odd or an even page</a>”. -<p>The solution to the problem is for LaTeX to ‘remember’ which side +<p/>The solution to the problem is for LaTeX to ‘remember’ which side of the page each <code>\</code><code>marginpar</code> <em>should</em> be on. The <i>mparhack</i> package does this, using label-like marks stored in the <code>.aux</code> file; the <i>memoir</i> class does likewise. @@ -27,5 +27,5 @@ the <code>.aux</code> file; the <i>memoir</i> class does likewise. <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>mparhack.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mparhack.zip">macros/latex/contrib/mparhack</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mparhack.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mparhack/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginparside">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginparside</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginparside">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginparside</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginpkgs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginpkgs.html index e45539bf772..a8a81d47fe4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginpkgs.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-marginpkgs.html @@ -2,17 +2,17 @@ <title>UK TeX FAQ -- question label marginpkgs</title> </head><body> <h3>Packages to set up page designs</h3> -<p>The ‘ultimate’ tool for adjusting the dimensions and position of the +<p/>The ‘ultimate’ tool for adjusting the dimensions and position of the printed material on the page is the <i>geometry</i> package; a very wide range of adjustments of the layout may be relatively straightforwardly programmed, and package documentation is good and comprehensive. -<p>As is usual, users of the <i>memoir</i> class have built-in +<p/>As is usual, users of the <i>memoir</i> class have built-in facilities for this task, and users of the <i>KOMA-script</i> classes are recommended to use an alternative package, <i>typearea</i>. In either case it is difficult to argue that users should go for <i>geometry</i>: both alternatives are good. -<p>The documentation of <i>geometry</i> is a bit overwhelming, and +<p/>The documentation of <i>geometry</i> is a bit overwhelming, and learning all its capabilities may be more than you ever need. Somewhat simpler to use is the <i>vmargin</i> package, which has a canned set of paper sizes (a superset of that provided in LaTeX2e), @@ -26,5 +26,5 @@ two-sided printing. <dt><tt><i>typearea.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) <dt><tt><i>vmargin.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/vmargin.zip">macros/latex/contrib/vmargin</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/vmargin.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/vmargin/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginpkgs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginpkgs</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginpkgs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=marginpkgs</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-matchbrak.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-matchbrak.html index efcbf4da21c..1f7f5f25f3b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-matchbrak.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-matchbrak.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label matchbrak</title> </head><body> <h3>My brackets don’t match</h3> -<p>(La)TeX has a low-level mechanism for matching braces in document +<p/>(La)TeX has a low-level mechanism for matching braces in document text. This means you can type something like: <blockquote> <pre> @@ -13,7 +13,7 @@ and know that the first brace (for the argument of <code>\</code><code>section</ be matched with the last brace, and the internal pair of braces (for the argument of <code>\</code><code>emph</code>) will be matched with each other. It’s all very simple. -<p>However, LaTeX has a convention of enclosing optional arguments in +<p/>However, LaTeX has a convention of enclosing optional arguments in brackets, as in: <blockquote> <pre> @@ -31,7 +31,7 @@ straightforward-looking usages like: aren’t OK at all — the optional argument comes to consist of “All [OK”, and <code>\</code><code>section</code> takes the single character “n” (of the first “now”) as its argument. -<p>Fortunately, TeX’s scanning mechanisms helps us by accepting the +<p/>Fortunately, TeX’s scanning mechanisms helps us by accepting the syntax “<code>{]}</code>” to ‘hide’ the closing bracket from the scanning mechanism that LaTeX uses. In practice, the commonest way to use this facility is: @@ -41,7 +41,7 @@ to use this facility is: </pre> </blockquote><p> since bracing the bracket on its own “looks odd”. -<p>LaTeX has another argument syntax, even less regular, where the +<p/>LaTeX has another argument syntax, even less regular, where the argument is enclosed in parentheses, as in: <blockquote> <pre> @@ -49,9 +49,9 @@ argument is enclosed in parentheses, as in: </pre> </blockquote><p> (a picture environment command). -<p>This mechanism is also prone to problems with matching closing +<p/>This mechanism is also prone to problems with matching closing parentheses, but the issue seldom arises since such arguments rarely contain text. If it were to arise, the same solution (enclosing the confused characters in braces) would solve the problem. -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=matchbrak">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=matchbrak</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=matchbrak">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=matchbrak</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathlips.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathlips.html index 8c40ce88519..6308b2a33a8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathlips.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathlips.html @@ -3,7 +3,7 @@ </head><body> <h3>Ellipses</h3> <!-- <code>\</code><code>dots</code> <code>\</code><code>cdots</code> <code>\</code><code>vdots</code> <code>\</code><code>ddots</code> --> -<p>Ellipses are commonly required, and LaTeX natively supplies a fair +<p/>Ellipses are commonly required, and LaTeX natively supplies a fair range (<code>\</code><code>dots</code>, <code>\</code><code>cdots</code>, <code>\</code><code>vdots</code> and <code>\</code><code>ddots</code>). By using the <i>graphics</i> package, one can change the slope of the <code>\</code><code>ddots</code> command, as in @@ -14,11 +14,11 @@ While this works, it is not a recommended way of achieving the desired result (see below). Moreover, LaTeX’s range is not adequate to everyone’s requirements, and at least three packages provide extensions to the set. -<p>The AMSLaTeX bundle provides a range of “semantically-named” +<p/>The AMSLaTeX bundle provides a range of “semantically-named” ellipses, for use in different situations: <code>\</code><code>dotsb</code> for use between pairs of binary operators, <code>\</code><code>dotsc</code> for use between pairs of commas, and so on. -<p>The <i>yhmath</i> package defines an <code>\</code><code>adots</code> command, which is +<p/>The <i>yhmath</i> package defines an <code>\</code><code>adots</code> command, which is the analogue of <code>\</code><code>ddots</code>, sloping forwards rather than backwards. The <i>yhmath</i> package comes with a rather interesting font that extends the standard <i>cmex</i>; details are in the documentation. @@ -26,11 +26,11 @@ The disadvantage of this setup is, that although <code>\</code><code>adots</code a macro, the package tries to load its own font and produces a “missing font” substitution warning message if you haven’t installed the font. -<p>The <i>mathdots</i> package (besides fixing up the behaviour of +<p/>The <i>mathdots</i> package (besides fixing up the behaviour of (La)TeX <code>\</code><code>ddots</code> and <code>\</code><code>vdots</code> when the font size changes) provides an “inverse diagonal” ellipsis <code>\</code><code>iddots</code> (doing the same job as <i>yhmath</i>’s <code>\</code><code>adots</code>, but better). -<p>Documentation of <i>yhmath</i> appears, processed, in the +<p/>Documentation of <i>yhmath</i> appears, processed, in the distribution (thus saving you the bother of installing the package before being able to read the documentation). Documentation of <i>mathdots</i> appears at the end the package file itself. @@ -41,5 +41,5 @@ before being able to read the documentation). Documentation of <dt><tt><i>yhmath (fonts)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/yhmath.zip">fonts/yhmath</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/yhmath.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/yhmath/">browse</a>) <dt><tt><i>yhmath (macros)</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/yhmath.zip">macros/latex/contrib/yhmath</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/yhmath.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/yhmath/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathlips">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathlips</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathlips">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathlips</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathml.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathml.html index d932b1f0b89..aa9979a8592 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathml.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathml.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label mathml</title> </head><body> <h3>Future WWW technologies and (La)TeX</h3> -<p>An earlier answer +<p/>An earlier answer (<a href="FAQ-LaTeX2HTML.html">“converting to HTML”</a>) addresses the issue of converting existing (La)TeX documents for viewing on the Web as HTML. All the present techniques are somewhat flawed: the answer explains why. -<p>However, things are changing, with +<p/>However, things are changing, with better font availability, cunning HTML programming and the support for new Web standards. <dl> @@ -18,13 +18,13 @@ support for new Web standards. hitching them to alternate font face specifications for standard code points in a non-standard way. This does nothing for the universality of the HTML so generated. -<p> In the near future, we can expect rather wide availability of +<p/> In the near future, we can expect rather wide availability of Unicode fonts with good coverage of symbols, which should make life easier for those who need to represent mathematics. <dt>XML<dd> The core of the range of new standards is XML, which provides a framework for better structured markup; limited support for it has already appeared in some browsers. -<p> Conversion of (La)TeX source to XML is already available +<p/> Conversion of (La)TeX source to XML is already available (through TeX4ht at least), and work continues in that arena. The alternative, authoring in XML (thus producing documents that are immediately Web-friendly, if not ready) and using (La)TeX to @@ -51,7 +51,7 @@ support for new Web standards. -<p> An approach different from (La)TeX conversion is taken by +<p/> An approach different from (La)TeX conversion is taken by the <a href="http://www.albany.edu/~hammond/gellmu/"><em>GELLMU</em> Project</a>. Its <em>article</em> XML document type, which has a markup vocabulary close to LaTeX that can be edited using LaTeX-like markup @@ -67,7 +67,7 @@ support for new Web standards. representations of formulas are also possible, in place of the separate bitmaps that have been used in the past (and while we wait for the wider deployment of MathML). -<p> Browser plug-ins, that deal with SVG are already available +<p/> Browser plug-ins, that deal with SVG are already available (Adobe offer one, for example). More recently, the open source graphics editor <a href="http://www.inkscape.org/"><i>Inkscape</a></i> has appeared, and has been reported to be useful for @@ -81,7 +81,7 @@ support for new Web standards. plug-in, while still retaining its (La)TeX abilities, but it’s now distributed (free for Linux and Windows platforms) by <a href="http://www.integretechpub.com/">Integre Technical Publishing</a>. -<p> The disadvantage of the TechExplorer approach is that it places the +<p/> The disadvantage of the TechExplorer approach is that it places the onus on the browser user; and however technically proficient <em>you</em> are, it’s never safe to assume too much of your readers. An interesting alternative is @@ -100,5 +100,5 @@ support for new Web standards. <dt><tt><i>MimeTeX</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/mimetex.zip">support/mimetex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/mimetex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/mimetex/">browse</a>) <dt><tt><i>TeX4HT</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/TeX4ht/tex4ht-all.zip">support/TeX4ht/tex4ht-all.zip</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathml">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathml</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathml">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathml</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathonlyref.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathonlyref.html new file mode 100644 index 00000000000..317eb2cd798 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathonlyref.html @@ -0,0 +1,25 @@ +<head> +<title>UK TeX FAQ -- question label mathonlyref</title> +</head><body> +<h3>Numbers for referenced equations only</h3> +<p/>There are those who consider that papers look untidy with numbers on +every equation; there is also a school of thought that claims that +there should be numbers everywhere, in case some reader wants to make +reference an equation to which the author made no cross-reference. +<p/>If you hold to the “only cross-referenced” school of thought, you +can (using the <code>\</code><code>nonumber</code> command on the relevant equations, or by +using the AMSLaTeX unnumbered environments such as +<code>equation*</code>) mark those of your equations to which you +make no reference. In a long or complex paper, this procedure could +well become deeply tedious. +<p/>Fortunately, help is at hand: the <i>mh</i> bundle’s +<i>mathtools</i> package offers a ‘<code>showonlyrefs</code>’ +switch through its <code>\</code><code>mathtoolsset</code> command; when that’s in +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. +<dl> +<dt><tt><i>mathtools.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mh.zip">macros/latex/contrib/mh</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mh.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mh/">browse</a>) +</dl> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathonlyref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathonlyref</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathsize.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathsize.html index a8942dfa9a8..c24a7c06895 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathsize.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathsize.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label mathsize</title> </head><body> <h3>Adjusting maths font sizes</h3> -<p>In Plain TeX, when you introduce a new font size you must also +<p/>In Plain TeX, when you introduce a new font size you must also declare what size fonts are to be used in mathematics with it. This is done by declaring <code>\</code><code>textfont</code>, <code>\</code><code>scriptfont</code> and <code>\</code><code>scriptscriptfont</code> for the maths families you’re using; all such @@ -10,7 +10,7 @@ things are described in chapter 17 of the <a href="FAQ-books.html">TeXbook</a> and in other books and <a href="FAQ-man-tex.html">tutorials</a> that discuss Plain TeX in sufficient detail. -<p>In LaTeX, of course, all this stuff is automated: there is a scheme +<p/>In LaTeX, of course, all this stuff is automated: there is a scheme that, for each (text) font size, determines what maths font sizes are to be used. The scheme first checks a set of “known” text sizes, for each of which maths sizes are declared in advance. If the text @@ -18,7 +18,7 @@ size isn’t “known”, the script- and scriptscriptfont sizes are calculated as fixed ratios of the tex font size. (The values used are <code>\</code><code>defaultscriptratio</code>=0.7, and <code>\</code><code>defaultscriptscriptratio</code>=0.5.) -<p>The fixed-ratio formula is capable of producing inconvenient results +<p/>The fixed-ratio formula is capable of producing inconvenient results (particularly if you are using fonts which LaTeX believes are only available in a fixed set of sizes). You may also want to replace LaTeX’s ideas altogether, for example by setting maths noticeably @@ -31,7 +31,7 @@ the maths font sizes to be used when the surrounding text font size is <code><<i>tfs</i>></code>; (<code><<i>ts</i>></code> being the size used for <code>\</code><code>textfont</code>, <code><<i>ss</i>></code> for <code>\</code><code>scriptfont</code> and <code><<i>sss</i>></code> for <code>\</code><code>scriptscriptfont</code>). -<p>For example, you might want to use a font with a smaller body height +<p/>For example, you might want to use a font with a smaller body height than Computer Modern, but still prefer CM math to any of the alternatives. In this case, you might use: <blockquote> @@ -40,7 +40,7 @@ alternatives. In this case, you might use: </pre> </blockquote><p> to get 9pt maths when the surrounding body text is (nominal) 10pt. -<p><code>\</code><code>DeclareMathSizes</code> may only be used in the preamble of the +<p/><code>\</code><code>DeclareMathSizes</code> may only be used in the preamble of the document: only one association is available for each text font size for the whole document. The default settings are specified in <i>fontdef.dtx</i> in the latex distribution, and are compiled into @@ -54,5 +54,5 @@ they contain those internal abbreviations, they need to be treated as <dt><tt><i>fontdef.dtx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/base/fontdef.dtx">macros/latex/base/fontdef.dtx</a> <dt><tt><i>fontmath.ltx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/unpacked/fontmath.ltx">macros/latex/unpacked/fontmath.ltx</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathsize">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathsize</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathsize">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathsize</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathstext.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathstext.html index 91241a4f485..777930ef9f9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathstext.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mathstext.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label mathstext</title> </head><body> <h3>Text inside maths</h3> -<p>When we type maths in (La)TeX, the letters from which we make up +<p/>When we type maths in (La)TeX, the letters from which we make up ordinary text assume a special significance: they all become single-letter variable names. The letters appear in italics, but it’s not the same sort of italics that you see when you’re typing ordinary @@ -13,10 +13,10 @@ well together, whereas the maths is set to look as if you’re multiplying <em>h</em> by <em>e</em> by <em>r</em> by <em>e</em>. The other way things are odd in TeX maths typing is that spaces are ignored: at best we can write single words in this oddly lumpy font. -<p>So, if we’re going to have good-looking text in amongst maths we’re +<p/>So, if we’re going to have good-looking text in amongst maths we’re writing, we have to take special precautions. If you’re using LaTeX, the following should help. -<p>The simplest is to use <code>\</code><code>mbox</code> or <code>\</code><code>textrm</code>: +<p/>The simplest is to use <code>\</code><code>mbox</code> or <code>\</code><code>textrm</code>: <blockquote> <pre> $e = mc^2 \mbox{here we go again}$ @@ -30,7 +30,7 @@ $z = a_{\mbox{other end}}$ </pre> </blockquote><p> looks quite painfully wrong. -<p>The other simple technique, <code>\</code><code>textrm</code>, is more promising: +<p/>The other simple technique, <code>\</code><code>textrm</code>, is more promising: <blockquote> <pre> $z = a_{\textrm{other end}}$ @@ -39,11 +39,11 @@ $z = a_{\textrm{other end}}$ is definitely right. However, the surrounding text may not be in your roman font; if you care about matching text, you need to choose between <code>\</code><code>textrm</code>, <code>\</code><code>textsf</code>, and so on. -<p>(The maths-mode instance of your roman font (<code>\</code><code>mathrm</code>) gets the +<p/>(The maths-mode instance of your roman font (<code>\</code><code>mathrm</code>) gets the size right, but since it’s intended for use in maths, its spaces get ignored — use <code>\</code><code>mathrm</code> for upright roman alphabetic variable names, but not otherwise.) -<p>You can correct these problems with size selectors in the text, as: +<p/>You can correct these problems with size selectors in the text, as: <blockquote> <pre> $z = a_{\mbox{\scriptsize other end}}$ @@ -51,7 +51,7 @@ $z = a_{\mbox{\scriptsize other end}}$ </blockquote><p> which works if your surrounding text is at default document size, but gives you the wrong size otherwise. -<p>These short cuts are (just about) OK for the “occasional” +<p/>These short cuts are (just about) OK for the “occasional” mathematician, but serious mathematics calls for a technique that relieves the typist of the sort of thought required. As usual, the AMSLaTeX system provides what’s necessary — the <code>\</code><code>text</code> @@ -68,7 +68,7 @@ $z = a_{\text{other end}}$ </blockquote><p> and the text will be at the right size, and in the same font as surrounding text. -<p>AMSLaTeX also makes provision for interpolated comments in the +<p/>AMSLaTeX also makes provision for interpolated comments in the middle of one of its multi-line display structures, through the <code>\</code><code>intertext</code> command. For example: <blockquote> @@ -107,7 +107,7 @@ signs): \end{flalign} </pre> </blockquote><p> -<p>Comprehensive documentation of AMSLaTeX is to be found in +<p/>Comprehensive documentation of AMSLaTeX is to be found in <i>amsldoc</i>, in the distribution; it is also available on the web at <a href="ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf">ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf</a> <dl> @@ -120,5 +120,5 @@ at <a href="ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf">ftp://ftp.ams.org <dt><tt><i>mathtools.sty</i></tt><dd>Distributed as part of the <i>mh</i> bundle <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mh.zip">macros/latex/contrib/mh</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mh.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mh/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathstext">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathstext</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathstext">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mathstext</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcfloat.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcfloat.html index 7f8679ff342..8184f2d9ad3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcfloat.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcfloat.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label mcfloat</title> </head><body> <h3>Floats in multicolumn setting</h3> -<p>If you use +<p/>If you use <blockquote> <pre> \begin{figure} @@ -21,7 +21,7 @@ instead you use </blockquote><p> the figure will stretch right across the page (just the same as a <code>figure*</code> in standard LaTeX’s <code>twocolumn</code> option). -<p>It’s possible to have single-column figures and tables with captions, +<p/>It’s possible to have single-column figures and tables with captions, using the ‘<code>[H]</code>’ placement option introduced by the <i>float</i> package but you might have to fiddle with the placement because they won’t ‘float’, and exhibit other strange behaviours (such as silently @@ -31,5 +31,5 @@ running off the end of the column at the end of the <dt><tt><i>float.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse</a>) <dt><tt><i>multicol.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mcfloat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mcfloat</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mcfloat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mcfloat</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcite.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcite.html index e02dd602bc6..4a577b1dabc 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcite.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mcite.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label mcite</title> </head><body> <h3>Multiple citations</h3> -<p>A convention sometimes used in physics journals is to “collapse” a group of +<p/>A convention sometimes used in physics journals is to “collapse” a group of related citations into a single entry in the bibliography. BibTeX, by default, can’t cope with this arrangement, but the <i>mcite</i> package deals with the problem. -<p>The package overloads the <code>\</code><code>cite</code> command to recognise a +<p/>The package overloads the <code>\</code><code>cite</code> command to recognise a “<code>*</code>” at the start of a key, so that citations of the form <blockquote> <pre> @@ -26,10 +26,10 @@ Which will appear in the document as 3 citations “[4,7,11]” (say) — citation ‘4’ will refer to paper 0, ‘7’ will refer to a combined entry for paper 1 and paper 2, and ‘11’ will refer to paper 3. -<p>You need to make a small change to the bibliography style +<p/>You need to make a small change to the bibliography style (<code>.bst</code>) file you use; the <i>mcite</i> package documentation tells you how to do that. -<p>Unfortunately, the <i>revtex</i> system doesn’t play with +<p/>Unfortunately, the <i>revtex</i> system doesn’t play with <i>mcite</i>. As a result, for that (primarily physics-targeted system) you need to play silly games like: <blockquote> @@ -44,5 +44,5 @@ achieve the effects of <i>mcite</i>. <dt><tt><i>mcite.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mcite.zip">macros/latex/contrib/mcite</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mcite.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mcite/">browse</a>) <dt><tt><i>revtex bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/revtex.zip">macros/latex/contrib/revtex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/revtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/revtex/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mcite">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mcite</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mcite">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mcite</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-metrics.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-metrics.html index cddb11091c1..06dd0d2de82 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-metrics.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-metrics.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label metrics</title> </head><body> <h3>TeX font metric files for PostScript fonts</h3> -<p>Reputable font vendors such as Adobe supply metric files for each +<p/>Reputable font vendors such as Adobe supply metric files for each font, in AFM (Adobe Font Metric) form; these can be converted to TFM (TeX Font Metric) form. Most modern distributions have prebuilt metrics which will be more than enough for many people; but you may @@ -28,17 +28,17 @@ which is designed to sit well with “Adobe standard” encoded fonts. Basic support of LY1 is available on CTAN: note that the “relation with Adobe’s encoding” means that there are no virtual fonts in the LY1 world. -<p>Alan Jeffrey’s <i>fontinst</i> package is an AFM to +<p/>Alan Jeffrey’s <i>fontinst</i> package is an AFM to TFM converter written in TeX; it is used to generate the files used by LaTeX2e’s PSNFSS package to support use of PostScript fonts. It is a sophisticated package, not for the faint-hearted, but is powerful enough to cope with most needs. Much of its power relies on the use of <a href="FAQ-virtualfonts.html">virtual fonts</a>. -<p>For slightly simpler problems, Rokicki’s <i>afm2tfm</i>, +<p/>For slightly simpler problems, Rokicki’s <i>afm2tfm</i>, distributed with <i>dvips</i>, is fast and efficient; note that the metrics and styles that come with <i>dvips</i> are <em>not</em> currently LaTeX2e compatible. -<p>For the Macintosh (classic), there is a program called +<p/>For the Macintosh (classic), there is a program called <i>EdMetrics</i> which does the job (and more). <i>EdMetrics</i> comes with the (commercial) <a href="FAQ-commercial.html">Textures</a> distribution, but is itself free @@ -53,5 +53,5 @@ software, and is available on CTAN. <dt><tt><i>fontinst</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.zip">fonts/utilities/fontinst</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/fontinst.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/fontinst/">browse</a>) <dt><tt><i>LY1 support</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psnfssx/ly1.zip">macros/latex/contrib/psnfssx/ly1</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psnfssx/ly1.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/psnfssx/ly1/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=metrics">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=metrics</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=metrics">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=metrics</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mfptutorials.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mfptutorials.html index 3f4843658ea..a43366b900e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mfptutorials.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mfptutorials.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label mfptutorials</title> </head><body> <h3>Metafont and MetaPost Tutorials</h3> -<p>Apart from Knuth’s book, there seems to be only one publicly-available +<p/>Apart from Knuth’s book, there seems to be only one publicly-available <a href="http://metafont.tutorial.free.fr/">tutorial for Metafont</a>, by Christophe Grandsire (a copy in PDF form may be downloaded). Geoffrey Tobin’s <i>Metafont for Beginners</i> (see <a href="FAQ-useMF.html">using Metafont</a>) describes how the Metafont system works and how to avoid some of the potential pitfalls. -<p>There is also an article on how to run both Metafont and MetaPost (the +<p/>There is also an article on how to run both Metafont and MetaPost (the programs). Peter Wilson’s <i>Some Experiences in Running Metafont and MetaPost</i> offers the benefit of Peter’s experience (he has designed a number of @@ -17,21 +17,21 @@ towards testing and installing new Metafont fonts, while its MetaPost section describes how to use MetaPost illustrations in LaTeX and PDFLaTeX documents, with an emphasis on how to use appropriate fonts for any text or mathematics. -<p>Hans Hagen (of ConTeXt fame) offers a MetaPost tutorial called -MetaFun (which admittedly concentrates on the use of MetaPost within -ConTeXt). It may be found on his company’s -<a href="http://www.pragma-ade.com/metapost.htm">MetaPost page</a>. -<p>Other MetaPost tutorials that have appeared are two in English by +<p/> + + + +<p/>Other MetaPost tutorials that have appeared are two in English by <a href="http://remote.science.uva.nl/~heck/Courses/mptut.pdf">André Heck</a> and <a href="http://www.tlhiv.org/MetaPost/tutorial/">Urs Oswald</a>, and one in French (listed here because it’s clearly enough written -that this author understands it), by +that even this author understands it), by <a href="http://pauillac.inria.fr/~cheno/metapost/metapost.pdf">Laurent Chéno</a>; both have been recommended for inclusion in the FAQ -<p>Urs Oswald’s tutorial is accompanied by a super tool for testing -little bits of MetaPost, which is an invaluable aid to the learner: -<a href="http://www.tlhiv.org/cgi-bin/MetaPostPreviewer/index.cgi">http://www.tlhiv.org/cgi-bin/MetaPostPreviewer/index.cgi</a> -<p>Vincent Zoonekynd’s massive set of example MetaPost files is available on +<p/>Urs Oswald’s tutorial is accompanied by a super tool (by Troy +Henderson) for testing little bits of MetaPost, which is an invaluable +aid to the learner: <a href="http://www.tlhiv.org/mppreview">http://www.tlhiv.org/mppreview</a> +<p/>Vincent Zoonekynd’s massive set of example MetaPost files is available on CTAN; the set includes a <i>Perl</i> script to convert the set to html, and the set may be <a href="http://zoonek.free.fr/LaTeX/Metapost/metapost.html">viewed on the web</a>. @@ -45,5 +45,5 @@ written more as a document, and presented in PDF. (PDF format) <dt><tt><i>Vincent Zoonekynd’s examples</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/metapost/examples.zip">info/metapost/examples</a> (<a href="ftp://cam.ctan.org/tex-archive/info/metapost/examples.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/metapost/examples/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mfptutorials">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mfptutorials</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mfptutorials">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mfptutorials</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minitoc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minitoc.html index 751599a1d3a..75fec2d9e7a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minitoc.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minitoc.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label minitoc</title> </head><body> <h3>Table of contents, etc., per chapter</h3> -<p>The common style, of a “small” table of contents for each part, +<p/>The common style, of a “small” table of contents for each part, chapter, or even section, is supported by the <i>minitoc</i> package. The package also supports mini-lists of tables and figures; but, as the documentation observes, mini-bibliographies are a different problem — see <a href="FAQ-chapbib.html">bibliographies per chapter</a>. -<p>The package’s basic scheme is to generate a little <code>.aux</code> file for +<p/>The package’s basic scheme is to generate a little <code>.aux</code> file for each chapter, and to process that within the chapter. Simple usage would be: <blockquote> @@ -27,7 +27,7 @@ would be: </blockquote><p> though a lot of elaborations are possible (for example, you don’t need a <code>\</code><code>minitoc</code> for every chapter). -<p><i>Babel</i> doesn’t know about <i>minitoc</i>, but +<p/><i>Babel</i> doesn’t know about <i>minitoc</i>, but <i>minitoc</i> makes provision for other document languages than English — a wide variety is available. Fortunately, the current version of the <i>hyperref</i> package does know about @@ -38,5 +38,5 @@ same way as “real” tables of contents. <dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>) <dt><tt><i>minitoc.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/minitoc.zip">macros/latex/contrib/minitoc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/minitoc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/minitoc/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=minitoc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=minitoc</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=minitoc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=minitoc</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minxampl.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minxampl.html index ee4750a9437..195ab584490 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minxampl.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-minxampl.html @@ -2,24 +2,26 @@ <title>UK TeX FAQ -- question label minxampl</title> </head><body> <h3>How to make a “minimum example”</h3> -<p><a href="FAQ-askquestion.html">Our advice on asking questions</a> +<p/><a href="FAQ-askquestion.html">Our advice on asking questions</a> suggests that you prepare a “minimum example” (also commonly known as a “<em>minimal</em> example”) of failing behaviour, as a sample to post with your question. If you have a problem in a two hundred page document, it may be unclear how to proceed from this problem to a succinct demonstration of your problem. -<p>There are two valid approaches to this task: building up, and hacking +<p/>There are two valid approaches to this task: building up, and hacking down. -<p>The “building up” process starts with a basic document structure +<p/> +<b><em>Building up</em></b> starts +with a basic document structure (for LaTeX, this would have <code>\</code><code>documentclass</code>, <code>\</code><code>begin{document}</code>, <code>\</code><code>end{document}</code>) and adds things. First to add is a paragraph or so around the actual point where the problem occurrs. (It may prove difficult to find the actual line that’s provoking the problem. If the original problem is an error, reviewing -<a href="FAQ-errstruct.html">the structure of TeX errors</a> may -help.) -<p>Note that there are things that can go wrong in one part of the +<a href="FAQ-errstruct.html">“the structure of TeX errors”</a> +may help.) +<p/>Note that there are things that can go wrong in one part of the document as a result of something in another part: the commonest is problems in the table of contents (from something in a section title, or whatever), or the list of <<i>something</i>> (from something in a @@ -27,44 +29,47 @@ or whatever), or the list of <<i>something</i>> (from something in a (the caption probably needs the <code>figure</code> or <code>table</code> environment around it, but it <em>doesn’t</em> need the figure or table itself). -<p>If this file you’ve built up collapses already, then you’re done. +<p/>If this file you’ve built up shows the problem already, then you’re done. Otherwise, try adding packages; the optimum is a file with only one -package in it, but you may find that the guilty package only works at -all with another package loaded (or only fails in the context of -another package). -<p>The “hacking down” route starts with your entire document, and +package in it, but you may find that the guilty package won’t even load +properly unless another package has been loaded. (Another common case +is that package <i>A</i> only fails when package <i>B</i> has been +loaded.) +<p/> +<b><em>Hacking down</em></b> starts +with your entire document, and removes bits until the file no longer fails (and then of course restores the last thing removed). Don’t forget to hack out any unnecessary packages, but mostly, the difficulty is choosing what to hack out of the body of the document; this is the mirror of the problem above, in the “building up” route. -<p>If you’ve added a package (or more than one), add <code>\</code><code>listfiles</code> to +<p/>If you’ve added a package (or more than one), add <code>\</code><code>listfiles</code> to the preamble too: that way, LaTeX will produce a list of the packages you’ve used and their version numbers. This information may be useful evidence for people trying to help you. -<p>What if your document simply doesn’t fail in any of these cut-down +<p/>What if your document simply doesn’t fail in any of these cut-down scenarios? Whatever you do, don’t post the whole of the document: if you can, it may be useful to make a copy available on the web somewhere: people will probably understand if it’s impossible ... or inadvisable, in the case of something confidential. -<p>If the whole document is necessary, it could be that it’s an overflow +<p/>If the whole document is necessary, it could be that it’s an overflow of some sort; the best you can do is to post the code “around” the error, and (of course) the full text of the error. -<p>It may seem that all this work is rather excessive for preparing a +<p/>It may seem that all this work is rather excessive for preparing a simple post. There are two responses to that, both based on the relative inefficiency of asking a question on the internet. -<p>First, preparing a minimum document very often leads <em>you</em> to the +<p/>First, preparing a minimum document very often leads <em>you</em> to the answer, without all the fuss of posting and looking for responses. -<p>Second, your prime aim is to get an answer as quickly as possible; a +<p/>Second, your prime aim is to get an answer as quickly as possible; a well-prepared example stands a good chance of attracting an answer “in a single pass”: if the person replying to your post finds she needs more information, you have to find that request, post again, and wait for your benefactor to produce a second response. -<p>All things considered, a good example file can save you a day, for +<p/>All things considered, a good example file can save you a day, for perhaps half an hour’s effort invested. -<p>The above advice, differently phrased, may also be read on the web at -<a href="http://www.latex-einfuehrung.de/mini-en.html">http://www.latex-einfuehrung.de/mini-en.html</a>; source of that -article may be found at <a href="http://www.latex-einfuehrung.de/">http://www.latex-einfuehrung.de/</a>, in +<p/>The above advice, differently phrased, may also be read on the web at +<a href="http://www.minimalbeispiel.de/mini-en.html">http://www.minimalbeispiel.de/mini-en.html</a>; source of that +article may be found at <a href="http://www.minimalbeispiel.de/">http://www.minimalbeispiel.de/</a>, in both German and English. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=minxampl">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=minxampl</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=minxampl">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=minxampl</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missbegdoc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missbegdoc.html index 7a7e314c89c..75ea3442415 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missbegdoc.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missbegdoc.html @@ -2,26 +2,26 @@ <title>UK TeX FAQ -- question label missbegdoc</title> </head><body> <h3>Missing <code>\</code><code>begin</code><code>{document}</code></h3> -<p>Give it a file of plain text, or a LaTeX file that really does have no +<p/>Give it a file of plain text, or a LaTeX file that really does have no <code>\</code><code>begin{document}</code> command in it, and LaTeX will produce this error, quite correctly. LaTeX <em>needs</em> <code>\</code><code>begin{document}</code> so as to know when to execute the commands that finish off the document preamble. -<p>Other than that, the error can occur as a result of an error of yours, +<p/>Other than that, the error can occur as a result of an error of yours, of a corrupt <code>.aux</code> file, or of a buggy class or package. -<p>The errors you might commit are absent-mindedly typing a document +<p/>The errors you might commit are absent-mindedly typing a document command (such as <code>\</code><code>section</code>) in the preamble of your document, missing the comment marker from the beginning of a line, or giving too many arguments to one of the setup commands related to the class or a package that you have loaded. -<p>A corrupt <code>.aux</code> file might be due to any number of things; +<p/>A corrupt <code>.aux</code> file might be due to any number of things; delete the file and to run LaTeX again, twice. If the error recurs, it’s probably due to a buggy class or package. -<p>If the error occurs while LaTeX is reading a class or package, then +<p/>If the error occurs while LaTeX is reading a class or package, then there’s probably a bug in the file. The author of the class or package stands the best chance of finding the bug, but with luck you (or someone you ask on a mailing list or on <i>comp.text.tex</i>) will be able to spot the problem and provide a work-around. Always report such bugs, even if you have found a work-around. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=missbegdoc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=missbegdoc</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=missbegdoc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=missbegdoc</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-misschar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-misschar.html index 18f8a22bfe7..cef0b600977 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-misschar.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-misschar.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label misschar</title> </head><body> <h3>Where have my characters gone?</h3> -<p>You’ve typed some apparently reasonable text and processed it, but the +<p/>You’ve typed some apparently reasonable text and processed it, but the result contains no sign of some of the characters you typed. A likely reason is that the font you selected just doesn’t have a representation for the character in question. -<p>For example, if I type “that will be £44.00” into an ordinary +<p/>For example, if I type “that will be £44.00” into an ordinary (La)TeX document, or if I select the font <code>rsfs10</code> (which contains uppercase letters only) and type pretty much anything, the £ sign, or any lowercase letters or digits will not appear in the @@ -23,7 +23,7 @@ Missing character: There is no 3 in font rsfs10! which have the eighth bit set, while the <code>rsfs10</code> example shows that TeX will log the actual character in error, if it thinks it’s possible). -<p>Somewhat more understandable are the diagnostics you may get from +<p/>Somewhat more understandable are the diagnostics you may get from <i>dvips</i> when using the OT1 and T1 versions of fonts that were supplied in Adobe standard encoding: <blockquote> @@ -39,5 +39,5 @@ encodings and in the Cork encoding are not available in the Adobe fonts. In these cases, there <em>is</em> a typeset sign of the character: <i>dvips</i> produces a black rectangle of whatever size the concocted font file has specified. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=misschar">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=misschar</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=misschar">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=misschar</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missssymb.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missssymb.html index 48cbe402dd2..f8c2d6be169 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missssymb.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-missssymb.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label missssymb</title> </head><body> <h3>Missing symbol commands</h3> -<p>You’re processing an old document, and some symbol commands such as +<p/>You’re processing an old document, and some symbol commands such as <code>\</code><code>Box</code> and <code>\</code><code>lhd</code> appear no longer to exist. These commands were present in the core of LaTeX 2.09, but are not in current LaTeX. They are available in the <i>latexsym</i> package (which is part of @@ -13,5 +13,5 @@ symbol fonts). <dt><tt><i>amsfonts.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/latex.zip">fonts/amsfonts/latex</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/latex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/latex/">browse</a>) <dt><tt><i>AMS symbol fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/sources/symbols.zip">fonts/amsfonts/sources/symbols</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/sources/symbols.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/sources/symbols/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=missssymb">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=missssymb</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=missssymb">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=missssymb</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-moren9.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-moren9.html index 37f93400467..20669160583 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-moren9.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-moren9.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label moren9</title> </head><body> <h3>How to break the 9-argument limit</h3> -<p>If you think about it, you will realise that Knuth’s command +<p/>If you think about it, you will realise that Knuth’s command definition syntax: <blockquote> <pre> @@ -12,7 +12,7 @@ definition syntax: is intrinsically limited to just 9 arguments. There’s no direct way round this: how would you express a 10th argument? — and ensure that the syntax didn’t gobble some other valid usage? -<p>If you really must have more than 9 arguments, the way to go is: +<p/>If you really must have more than 9 arguments, the way to go is: <blockquote> <pre> \def\blah#1#2 ... #9{% @@ -33,7 +33,7 @@ the syntax didn’t gobble some other valid usage? </blockquote><p> This technique is easily extendible by concert pianists of the TeX keyboard, but is really hard to recommend. -<p>LaTeX users have the small convenience of merely giving a number of +<p/>LaTeX users have the small convenience of merely giving a number of arguments in the <code>\</code><code>newcommand</code> that defines each part of the relaying mechanism: Knuth’s restriction applies to <code>\</code><code>newcommand</code> just as it does to <code>\</code><code>def</code>. However, LaTeX users also have the @@ -60,5 +60,5 @@ accurately. <dl> <dt><tt><i>keyval.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.zip">macros/latex/required/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/graphics/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=moren9">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=moren9</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=moren9">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=moren9</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mpprologues.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mpprologues.html index aff6d6e4f29..e6e58665fd5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mpprologues.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-mpprologues.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label mpprologues</title> </head><body> <h3>Displaying MetaPost output in <i>ghostscript</i></h3> -<p>MetaPost ordinarily expects its output to be included in some context +<p/>MetaPost ordinarily expects its output to be included in some context where the ‘standard’ Metafont fonts (that you’ve specified) are already defined — for example, as a figure in TeX document. If you’re debugging your MetaPost code, you may want to view it in @@ -17,7 +17,7 @@ Error: /undefined in cmmi10 </blockquote><p> There is provision in MetaPost for avoiding this problem: issue the command <code>prologues := 2;</code> at the start of the <code>.mp</code> file. -<p>Unfortunately, the PostScript that MetaPost inserts in its output, +<p/>Unfortunately, the PostScript that MetaPost inserts in its output, following this command, is incompatible with ordinary use of the PostScript in inclusions into (La)TeX documents, so it’s best to make the <code>prologues</code> command optional. Furthermore, MetaPost takes a @@ -27,7 +27,7 @@ troublesome. If you’re suffering such problems (the symptom is that characters disappear, or are wrongly presented) the only solution is to view the ‘original’ metapost output after processing through LaTeX and <i>dvips</i>. -<p>Conditional compilation may be done either +<p/>Conditional compilation may be done either by inputting <i>MyFigure.mp</i> indirectly from a simple wrapper <i>MyFigureDisplay.mp</i>: <blockquote> @@ -44,7 +44,7 @@ mp '\prologues:=2; input MyFigure' </blockquote><p> (which will work without the quote marks if you’re not using a Unix shell). -<p>A suitable LaTeX route would involve processing +<p/>A suitable LaTeX route would involve processing <i>MyFigure.tex</i>, which contains: <blockquote> <pre> @@ -66,12 +66,12 @@ dvips -E -o MyFigure.eps MyFigure would then give a satisfactory Encapsulated PostScript file. This procedure may be automated using the <i>Perl</i> script <i>mps2eps</i>, thus saving a certain amount of tedium. -<p>The Plain TeX user may use an adaptation of a jiffy of Knuth’s, by +<p/>The Plain TeX user may use an adaptation of a jiffy of Knuth’s, by Dan Luecking. Dan’s version <i>mpsproof.tex</i> will work under TeX to produce a DVI file for use with <i>dvips</i>, or under PDFTeX to produce a PDF file, direct. The output is set up to look like a proof sheet. -<p>A script application, <i>mptopdf</i>, is available in recent +<p/>A script application, <i>mptopdf</i>, is available in recent (La)TeX distributions: it seems fairly reliably to produce PDF from MetaPost, so may reasonably be considered an answer to the question... @@ -80,5 +80,5 @@ the question... <dt><tt><i>mpsproof.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/metapost/contrib/misc/mpsproof.tex">graphics/metapost/contrib/misc/mpsproof.tex</a> <dt><tt><i>mptopdf</i></tt><dd>Part of <a href="ftp://cam.ctan.org/tex-archive/macros/pdftex/graphics.zip">macros/pdftex/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/pdftex/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/pdftex/graphics/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mpprologues">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mpprologues</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mpprologues">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=mpprologues</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-msxy.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-msxy.html index 3122c0f19e0..6c92ec94c7e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-msxy.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-msxy.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label msxy</title> </head><body> <h3>Where are the <code>msx</code> and <code>msy</code> fonts?</h3> -<p>The <i>msx</i> and <i>msy</i> fonts were designed by the +<p/>The <i>msx</i> and <i>msy</i> fonts were designed by the American Mathematical Society in the very early days of TeX, for use in typesetting papers for mathematical journals. They were designed using the ‘old’ Metafont, which wasn’t portable and is no longer @@ -11,19 +11,19 @@ which only imperfectly matched modern printers. The AMS has now redesigned the fonts, using the current version of Metafont, and the new versions are called the <i>msa</i> and <i>msb</i> families. -<p>Nevertheless, <i>msx</i> and <i>msy</i> continue to turn up to +<p/>Nevertheless, <i>msx</i> and <i>msy</i> continue to turn up to plague us. There are, of course, still sites that haven’t got around to upgrading; but, even if everyone upgraded, there would still be the problem of old documents that specify them. -<p>If you have a <code>.tex</code> source that requests <i>msx</i> and +<p/>If you have a <code>.tex</code> source that requests <i>msx</i> and <i>msy</i>, the best technique is to edit it so that it requests <i>msa</i> and <i>msb</i> (you only need to change the single letter in the font names). -<p>If you have a DVI file that requests the fonts, there is a package +<p/>If you have a DVI file that requests the fonts, there is a package of <a href="FAQ-virtualfonts.html">virtual fonts</a> to map the old to the new series. <dl> <dt><tt><i>msa and msb fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/sources/symbols.zip">fonts/amsfonts/sources/symbols</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/sources/symbols.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/sources/symbols/">browse</a>) <dt><tt><i>virtual font set</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/vf-files/msx2msa.zip">fonts/vf-files/msx2msa</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/vf-files/msx2msa.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/vf-files/msx2msa/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=msxy">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=msxy</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=msxy">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=msxy</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multbib.html index 1aa4eb9eeca..9ea0e52d624 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multbib.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multbib.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label multbib</title> </head><body> <h3>Multiple bibliographies?</h3> -<p>If you’re thinking of multiple bibliographies tied to some part of +<p/>If you’re thinking of multiple bibliographies tied to some part of your document (such as the chapters within the document), please see <a href="FAQ-chapbib.html">bibliographies per chapter</a>. -<p>For more than one bibliography, there are three options. -<p>The <i>multibbl</i> package offers a very simple interface: you use +<p/>For more than one bibliography, there are three options. +<p/>The <i>multibbl</i> package offers a very simple interface: you use a command <code>\</code><code>newbibliography</code> to define a bibliography “tag”. The package redefines the other bibliography commands so that each time you use any one of them, you give it the tag for the bibliography where you want the @@ -37,7 +37,7 @@ section or chapter (i.e., it patches new tag argument, and that the <code>\</code><code>bibliography</code> commands may list more than one <code>.bib</code> file — indeed all <code>\</code><code>bibliography</code> commands may list the same set of files.) -<p>The <code>\</code><code>bibliography</code> data goes into files whose names are +<p/>The <code>\</code><code>bibliography</code> data goes into files whose names are <<i>tag-name</i>><em>.aux</em>, so you will need to run <blockquote> <pre> @@ -47,7 +47,7 @@ bibtex art </blockquote><p> after the first run of LaTeX, to get the citations in the correct place. -<p>The <i>multibib</i> package allows you to define a series of +<p/>The <i>multibib</i> package allows you to define a series of “additional topics”, each of which comes with its own series of bibliography commands. So one might write: <blockquote> @@ -69,7 +69,7 @@ bibliography commands. So one might write: </blockquote><p> Again, as for <i>multibbl</i>, any <code>\</code><code>bibliography...</code> command may scan any list of <code>.bib</code> files. -<p>BibTeX processing with <i>multibib</i> is much like that with +<p/>BibTeX processing with <i>multibib</i> is much like that with <i>multibbl</i>; with the above example, one needs: <blockquote> <pre> @@ -79,7 +79,7 @@ bibtex art </blockquote><p> Note that, unlike <i>multibbl</i>, <i>multibib</i> allows a simple, unmodified bibliography (as well as the “topic” ones). -<p>The <i>bibtopic</i> package allows you separately to cite several +<p/>The <i>bibtopic</i> package allows you separately to cite several different bibliographies. At the appropriate place in your document, you put a sequence of <code>btSect</code> environments (each of which specifies a bibliography database to scan) to typeset the separate @@ -106,7 +106,7 @@ bibliographies. Thus, one might have a file <i>diss.tex</i> containing: Note the different way of specifying a bibliographystyle: if you want a different style for a particular bibliography, you may give it as an optional argument to the <code>btSect</code> environment. -<p>Processing with BibTeX, in this case, uses <code>.aux</code> files whose names +<p/>Processing with BibTeX, in this case, uses <code>.aux</code> files whose names are derived from the name of the base document. So in this example you need to say: <blockquote> @@ -115,14 +115,14 @@ bibtex diss1 bibtex diss2 </pre> </blockquote><p> -<p>There is also a command <code>\</code><code>btPrintNotCited</code>, which gives the rest of +<p/>There is also a command <code>\</code><code>btPrintNotCited</code>, which gives the rest of the content of the database (if nothing has been cited from the database, this is equivalent to LaTeX standard <code>\</code><code>nocite{*}</code>). -<p>However, the <em>real</em> difference from <i>miltibbl</i> and +<p/>However, the <em>real</em> difference from <i>miltibbl</i> and <i>mltibib</i> is that selection of what appears in each bibliography section is determined in <i>bibtopic</i> by what’s in the <code>.bib</code> files. -<p>An entirely different approach is taken by the <i>splitbib</i> +<p/>An entirely different approach is taken by the <i>splitbib</i> package. You provide a <code>category</code> environment, in the preamble of your document, for each category you want a separate citation list for. In each environment, you list the <code>\</code><code>cite</code> keys @@ -140,5 +140,5 @@ sorting process.) A code example appears in the package documentation <dt><tt><i>multibib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multibib.zip">macros/latex/contrib/multibib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multibib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multibib/">browse</a>) <dt><tt><i>splitbib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/splitbib.zip">macros/latex/contrib/splitbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/splitbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/splitbib/">browse</a>) </dl> -<p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multbib</a> +<p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multbib</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multfoot.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multfoot.html index bcbba3b7e3f..0d2441aa7df 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multfoot.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multfoot.html @@ -2,23 +2,27 @@ <title>UK TeX FAQ -- question label multfoot</title> </head><body> <h3>More than one sequence of footnotes</h3> -<p>The need for more than one series of footnotes is common in critical +<p/>The need for more than one series of footnotes is common in critical editions (and other literary criticism), but occasionally arises in other areas. -<p>Of course, the canonical critical edition macros, <i>edmac</i>, -offer the facility, as does its LaTeX port, the <i>ledmac</i> +<p/>Of course, the canonical critical edition package, <i>edmac</i>, +offers the facility, as does its LaTeX port, the <i>ledmac</i> package. -<p>Multiple ranges of footnotes are offered to LaTeX users by the +<p/>Multiple ranges of footnotes are offered to LaTeX users by the <i>manyfoot</i> package. The package provides a fair array of -presentation options, as well. The (rather new) critical editions +presentation options, as well. Another critical edition <i>ednotes</i> package is built upon a basis that includes <i>manyfoot</i>, as its mechanism for multiple sets of footnotes. +<p/>The <i>bigfoot</i> package also uses <i>manyfoot</i> as part of +its highly sophisticated structure of footnote facilities, which was +also designed to support typesetting critical editions. <dl> +<dt><tt><i>bigfoot</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.zip">macros/latex/contrib/bigfoot</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/bigfoot.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/bigfoot/">browse</a>) <dt><tt><i>edmac</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/edmac.zip">macros/plain/contrib/edmac</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/contrib/edmac.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/contrib/edmac/">browse</a>) <dt><tt><i>ednotes</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ednotes.zip">macros/latex/contrib/ednotes</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ednotes.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ednotes/">browse</a>) <dt><tt><i>ledmac</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ledmac.zip">macros/latex/contrib/ledmac</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ledmac.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ledmac/">browse</a>) <dt><tt><i>manyfoot.sty</i></tt><dd>Distributed as part of the <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ncctools.zip">macros/latex/contrib/ncctools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ncctools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ncctools/">browse</a>) bundle </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multfoot">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multfoot</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multfoot">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multfoot</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multidoc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multidoc.html index 60166cabfaa..f5ee627147b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multidoc.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multidoc.html @@ -2,28 +2,28 @@ <title>UK TeX FAQ -- question label multidoc</title> </head><body> <h3>A ‘report’ from lots of ‘article’s</h3> -<p>This is a requirement, for example, if one is preparing the +<p/>This is a requirement, for example, if one is preparing the proceedings of a conference whose papers were submitted in LaTeX. -<p>The nearest things to canned solutions are Peter Wilson’s +<p/>The nearest things to canned solutions are Peter Wilson’s <i>combine</i> and Federico Garcia’s <i>subfiles</i> classes. -<p><i>Combine</i> defines the means to ‘<code>\</code><code>import</code>’ entire documents, +<p/><i>Combine</i> defines the means to ‘<code>\</code><code>import</code>’ entire documents, and provides means of specifying significant features of the layout of the document, as well as a global table of contents, and so on. An auxiliary package, <i>combinet</i>, allows use of the <code>\</code><code>title</code>s and <code>\</code><code>author</code>s (etc.) of the <code>\</code><code>import</code>ed documents to appear in the global table of contents. -<p><i>Subfiles</i> is used in the component files of a multi-file +<p/><i>Subfiles</i> is used in the component files of a multi-file project, and the corresponding <i>subfiles</i> is used in the master file; arrangements may be made so that the component files will be typeset using different page format, etc., parameters than those used when they are typeset as a part of the main file. -<p>A more ‘raw’ toolkit is offered by Matt Swift’s <i>includex</i> and +<p/>A more ‘raw’ toolkit is offered by Matt Swift’s <i>includex</i> and <i>newclude</i> packages, both part of the <i>frankenstein</i> bundle. Note that Matt believes <i>includex</i> is obsolete (though it continues to work for this author); furthermore, its replacement, <i>newclude</i> remains “in development”, as it has been since 1999. -<p>Both <i>includex</i> and <i>newclude</i> enable you to +<p/>Both <i>includex</i> and <i>newclude</i> enable you to ‘<code>\</code><code>includedoc</code>’ complete articles (in the way that you ‘<code>\</code><code>include</code>’ chapter files in an ordinary report). The preamble (everything up to <code>\</code><code>begin{document}</code>), and everything after @@ -32,7 +32,7 @@ packages don’t “do the whole job” for you, though: you need to analyse the package use of the individual papers, and ensure that a consistent set is loaded in the preamble of the main report. (Both packages require <i>moredefs</i>, which is also part of the bundle.) -<p>A completely different approach is to use the <i>pdfpages</i> +<p/>A completely different approach is to use the <i>pdfpages</i> package, and to include articles submitted in PDF format into a a PDF document produced by PDFLaTeX. The package defines an <code>\</code><code>includepdf</code> command, which takes arguments similar to @@ -50,5 +50,5 @@ of the included pages. <dt><tt><i>pdfpages.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdfpages.zip">macros/latex/contrib/pdfpages</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdfpages.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdfpages/">browse</a>) <dt><tt><i>subfiles.cls, etc.</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/subfiles.zip">macros/latex/contrib/subfiles</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/subfiles.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/subfiles/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multidoc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multidoc</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multidoc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multidoc</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multind.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multind.html index 5bd54ce8209..8dad6c9943a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multind.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multind.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label multind</title> </head><body> <h3>Multiple indexes</h3> -<p>LaTeX’s standard indexing capabilities (those provided by the +<p/>LaTeX’s standard indexing capabilities (those provided by the <i>makeidx</i> package) only provide for one index in your document; even quite modest documents can be improved by indexes for separate topics. -<p>The <i>multind</i> package provides simple and straightforward +<p/>The <i>multind</i> package provides simple and straightforward multiple indexing. You tag each <code>\</code><code>makeindex</code>, <code>\</code><code>index</code> and <code>\</code><code>printindex</code> command with a file name, and indexing commands are written to (or read from) the name with the appropriate (<code>.idx</code> or @@ -15,7 +15,7 @@ from the LaTeX standard so that it doesn’t create its own chapter or section heading; you therefore decide what names (or sectioning level, even) to use for the indexes, and <a href="FAQ-fixnam.html"><code>\</code><code>indexname</code></a> is completely ignored. -<p>To create a “general” and an “authors” index, one might write: +<p/>To create a “general” and an “authors” index, one might write: <blockquote> <pre> \usepackage{multind} @@ -43,7 +43,7 @@ to process are not necessarily related to the name of the LaTeX file you’re processing, at all. (There’s no documentation that comes with the package: what you see above is as good as you will get...) -<p>The <i>index</i> package provides a comprehensive set of indexing +<p/>The <i>index</i> package provides a comprehensive set of indexing facilities, including a <code>\</code><code>newindex</code> command that allows the definition of new styles of index. <code>\</code><code>newindex</code> takes a ‘tag’ (for use in indexing commands), replacements for the <code>.idx</code> and @@ -51,7 +51,7 @@ use in indexing commands), replacements for the <code>.idx</code> and finally printed; it can also change the item that’s being indexed against (for example, one might have an index of artists referenced by the figure number where their work is shown). -<p>Using <i>index</i>, to create an author index together with a +<p/>Using <i>index</i>, to create an author index together with a “normal” index, one would start with preamble commands: <blockquote> <pre> @@ -93,7 +93,7 @@ and rerun LaTeX. The <i>makeindex</i> commands process <i>myfile.idx</i> to <i>myfile.ind</i> (the default action), and then <i>myfile.adx</i> to <i>myfile.and</i>, the two files needed as input by the two <code>\</code><code>printindex</code> commands in <i>myfile.tex</i>. -<p>The <i>splitidx</i> package can operate in the same way as the +<p/>The <i>splitidx</i> package can operate in the same way as the others: load the package with the <code>split</code> option, and declare each index with a <code>\</code><code>newindex</code> command: <blockquote> @@ -110,9 +110,9 @@ operating systems); if you use this auxiliary program (and don’t use from this trick, <i>splitidx</i> supports the same sorts of things as does <i>index</i>. An example of use appears in the documentation. -<p>The <i>memoir</i> class has its own multiple-index functionality (as -well as index layout options, which other packages delegate to the -index style used by <i>makeindex</i>. +<p/>The <i>memoir</i> class has its own multiple-index functionality (as +well as its own index layout options, which other packages delegate to +the index style used by <i>makeindex</i>). <dl> <dt><tt><i>index.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/index.zip">macros/latex/contrib/index</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/index.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/index/">browse</a>) <dt><tt><i>makeidx.sty</i></tt><dd>Part of the LaTeX distribution @@ -121,6 +121,6 @@ index style used by <i>makeindex</i>. <dt><tt><i>splitidx.sty and splitindex</i></tt><dd> <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/splitindex.zip">macros/latex/contrib/splitindex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/splitindex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/splitindex/">browse</a>) </dl> -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multind">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multind</a> +<p/> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multind">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multind</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multirow.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multirow.html index 525c9da51c0..4c651bfec35 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multirow.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-multirow.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label multirow</title> </head><body> <h3>Merging cells in a column of a table</h3> -<p>It’s easy to come up with a table design that requires a cell that +<p/>It’s easy to come up with a table design that requires a cell that spans several rows. An example is something where the left-most column labels the rest of the table; this can be done (in simple cases) by using <a href="FAQ-slashbox.html">diagonal separation in corner cells</a>, but that technique rather strictly limits what can be used as the content of the cell. -<p>The <i>multirow</i> package enables you to construct such multi-row +<p/>The <i>multirow</i> package enables you to construct such multi-row cells, in a very simple manner. For the simplest possible use, one might write: <blockquote> @@ -29,7 +29,7 @@ and <i>multirow</i> will position “Common g text” at the vertical centre of the space defined by the other rows. Note that the rows that don’t contain the “multi-row” specification must have empty cells where the multi-row is going to appear. -<p>The “<code>*</code>” may be replaced by a column width specification. In this +<p/>The “<code>*</code>” may be replaced by a column width specification. In this case, the argument may contain forced line-breaks: <blockquote> <pre> @@ -47,7 +47,7 @@ case, the argument may contain forced line-breaks: A similar effect (with the possibility of a little more sophistication) may be achieved by putting a smaller table that lines up the text into a <code>*</code>-declared <code>\</code><code>multirow</code>. -<p>The <code>\</code><code>multirow</code> command may also used to write labels vertically +<p/>The <code>\</code><code>multirow</code> command may also used to write labels vertically down one or other side of a table (with the help of the <i>graphics</i> or <i>graphicx</i> package, which provide the <code>\</code><code>rotatebox</code> command): @@ -66,7 +66,7 @@ down one or other side of a table (with the help of the </blockquote><p> (which gives text going upwards; use angle <code>-90</code> for text going downwards, of course). -<p>To make a <code>\</code><code>multicolumn</code> multi-row “cell” in a table, you have to +<p/>To make a <code>\</code><code>multicolumn</code> multi-row “cell” in a table, you have to enclose a <code>\</code><code>multirow</code> inside a <code>\</code><code>multicolumn</code> — the other way around does not work, so: <blockquote> @@ -88,11 +88,11 @@ package (which is also discussed in the answer to <a href="FAQ-struttab.html">spacing lines in tables</a>). You use an optional argument to the <code>\</code><code>multirow</code> command to say how many of the rows in the multi-row have been opened up with <code>\</code><code>bigstrut</code>. -<p>The documentation of both <i>multirow</i> and <i>bigstrut</i> is +<p/>The documentation of both <i>multirow</i> and <i>bigstrut</i> is to be found, as comments, in the package files themselves. <dl> <dt><tt><i>bigstrut.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multirow.zip">macros/latex/contrib/multirow</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multirow.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow/">browse</a>) <dt><tt><i>multirow.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multirow.zip">macros/latex/contrib/multirow</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/multirow.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/multirow/">browse</a>) </dl> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multirow">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multirow</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multirow">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=multirow</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-music.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-music.html index 0080a30db78..5b29906117c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-music.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-music.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label music</title> </head><body> <h3>Typesetting music in TeX</h3> -<p>In the early days, a simple music package called MuTeX was +<p/>In the early days, a simple music package called MuTeX was written by Angelika Schofer and Andrea Steinbach, which demonstrated that music typesetting was possible; the package was very limited, and is hardly ever used nowadays. Daniel Taupin took up the baton, and developed MusicTeX, which allows the typesetting of polyphonic and other multiple-stave music; MusicTeX remains available, but is most definitely no longer recommended. -<p>MusicTeX has been superseded by its successor MusiXTeX, which is +<p/>MusicTeX has been superseded by its successor MusiXTeX, which is a three-pass system (with a processor program that computes values for the element spacing in the music), and achieves finer control than is possible in the unmodified TeX-based mechanism that MusicTeX @@ -17,29 +17,29 @@ uses. Daniel Taupin’s is the only version of MusiXTeX currently being developed (the original author, Andreas Egler, had an alternative version, but he is now working on a different package altogether). -<p>Input to MusixTeX is extremely tricky stuff, and Don Simons’ +<p/>Input to MusixTeX is extremely tricky stuff, and Don Simons’ preprocessor <i>pmx</i> is the preferred method of creating input for Taupin’s version. <i>Pmx</i> greatly eases use of MusixTeX, but it doesn’t support the full range of MusixTeX’s facilities directly; however, it does allow in-line MusixTeX code in <i>pmx</i> sources. -<p>Dirk Laurie’s <i>M-Tx</i> allows preparation of music with lyrics; +<p/>Dirk Laurie’s <i>M-Tx</i> allows preparation of music with lyrics; it operates “on top of” <i>pmx</i> -<p>Another simple notation is supported by <i>abc2mtex</i>; this is a +<p/>Another simple notation is supported by <i>abc2mtex</i>; this is a package designed to notate tunes stored in an ASCII format (<code>abc</code> notation). It was designed primarily for folk and traditional tunes of Western European origin (such as Irish, English and Scottish) which can be written on one stave in standard classical notation, and creates input intended for MusicTeX. However, it should be extendable to many other types of music. -<p>Digital music fans can typeset notation for their efforts by using +<p/>Digital music fans can typeset notation for their efforts by using <i>midi2tex</i>, which translates MIDI data files into MusicTeX source code. -<p>There is a mailing list (<i>TeX-music@icking-music-archive.org</i>) +<p/>There is a mailing list (<i>TeX-music@icking-music-archive.org</i>) for discussion of typesetting music in TeX; it mostly covers MusixTeX and related systems. To subscribe, use <a href="http://icking-music-archive.org/mailman/listinfo/tex-music/">http://icking-music-archive.org/mailman/listinfo/tex-music/</a> -<p>An alternative (free) means of embedding music examples into (La)TeX +<p/>An alternative (free) means of embedding music examples into (La)TeX documents is <a href="http://www.lilypond.org">Lilypond</a>. Lilypond is (at heart) a batch music typesetting system with plain text input that does most of its work without TeX. Lilypond’s input syntax is far @@ -57,5 +57,5 @@ Lilypond can also produce basic MIDI output. <dt><tt><i>mutex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/mtex.zip">macros/mtex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/mtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/mtex/">browse</a>) <dt><tt><i>pmx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/pmx.zip">support/pmx</a> (<a href="ftp://cam.ctan.org/tex-archive/support/pmx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/pmx/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=music">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=music</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=music">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=music</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nameref.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nameref.html index 29a8976f320..cc1f61d9071 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nameref.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nameref.html @@ -2,27 +2,27 @@ <title>UK TeX FAQ -- question label nameref</title> </head><body> <h3>Referring to things by their name</h3> -<p>LaTeX’s labelling mechanism is designed for the impersonal world of +<p/>LaTeX’s labelling mechanism is designed for the impersonal world of the academic publication, in which everything has a number: an extension is necessary if we are to record the <em>name</em> of things we’ve labelled. The two packages available extend the LaTeX sectioning commands to provide reference by the name of the section. -<p>The <i>titleref</i> package is a simple extension which provides +<p/>The <i>titleref</i> package is a simple extension which provides the command <code>\</code><code>titleref</code>; it is a stand-alone package — don’t use it in a document in which you also need to use <i>hyperref</i>. -<p>The <i>byname</i> package is part of the <i>smartref</i> bundle +<p/>The <i>byname</i> package is part of the <i>smartref</i> bundle and works well with <i>smartref</i>, and works (to an extent) with <i>hyperref</i>, but the links it defines are not hyperlinks. -<p>The <i>memoir</i> class incorporates the functionality of +<p/>The <i>memoir</i> class incorporates the functionality of <i>titleref</i>, but doesn’t work with <i>byname</i> (though a search of <i>comp.text.tex</i> on <a href="groups.google.com">groups.google.com</a> will find a patch to <i>byname</i> to remedy the problem). -<p>The <i>hyperref</i> bundle includes a package <i>nameref</i>, +<p/>The <i>hyperref</i> bundle includes a package <i>nameref</i>, which will work standing alone (i.e., without <i>hyperref</i>: of course, in this mode its references are not hyperlinked). If you load <i>hyperref</i> itself, <i>nameref</i> is automatically loaded. <i>Memoir</i> requires the <i>memhfixc</i> when running with -<i>hyperref</i>; however, following the sequence +<i>hyperref</i>; following the sequence: <blockquote> <pre> \documentclass[...]{memoir} @@ -32,11 +32,27 @@ course, in this mode its references are not hyperlinked). If you load </pre> </blockquote><p> <i>nameref</i> commands may be used in a <i>memoir</i> document. -<p>Each of the name-reference packages defines a reference command -with the same name as the package: <code>\</code><code>titleref</code>, <code>\</code><code>byname</code> and -<code>\</code><code>nameref</code>. The <i>nameref</i> package also defines a command -<code>\</code><code>byshortnameref</code>, which uses the optional ‘short’ title argument -to the chapter and section commands. +<p/><i>Zref</i> defines a proposed replacement for all of the LaTeX +reference mechanisms, and among other things provides +name-referencing mechanisms: +<blockquote> +<pre> +\usepackage[user,titleref]{zref} +... +\section{hello}\zlabel{sec:one} +The section name is: \ztitleref{sec:one}. +</pre> +</blockquote><p> +(One might hope that something of this sort would be the “way of the +future”, but things move slowly in the LaTeX world: don’t hold +your breath.) +<p/>Each of <i>titleref</i>, <i>byname</i> and <i>nameref</i> +defines a reference command with the same name as the package: +<code>\</code><code>titleref</code>, <code>\</code><code>byname</code> and <code>\</code><code>nameref</code>. The <i>nameref</i> +package also defines a command <code>\</code><code>byshortnameref</code>, which uses the +optional ‘short’ title argument to the chapter and section commands. +(Although it comes from the same author, <i>zref</i> <em>doesn’t</em> +define a short-name variant.) <dl> <dt><tt><i>byname.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smartref.zip">macros/latex/contrib/smartref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smartref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/smartref/">browse</a>) <dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>) @@ -44,6 +60,7 @@ to the chapter and section commands. <dt><tt><i>nameref.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>) <dt><tt><i>smartref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smartref.zip">macros/latex/contrib/smartref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/smartref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/smartref/">browse</a>) <dt><tt><i>titleref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/titleref.sty">macros/latex/contrib/misc/titleref.sty</a> +<dt><tt><i>zref.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nameref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nameref</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nameref">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nameref</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newans.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newans.html index ea46571a378..00b8df11947 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newans.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newans.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label newans</title> </head><body> <h3>Submitting new material for the FAQ</h3> -<p>The FAQ will never be complete, and we always expect that +<p/>The FAQ will never be complete, and we always expect that there will be people out there who know better than we do about something or other. We always need to be put right about whatever we’ve got wrong, and suggestions for improvements, particularly @@ -10,7 +10,7 @@ covering areas we’ve missed, are always needed: mail anything you have to the <a href="mailto:faq-devel@tex.ac.uk">maintainers</a> -<p>If you have actual material to submit, your contribution is more than +<p/>If you have actual material to submit, your contribution is more than ever welcome. Submission in plain text is entirely acceptable, but if you’re really willing, you may feel free to mark up your submission in the form needed for the FAQ itself. The markup is a @@ -28,5 +28,5 @@ up to date for development purposes. <dl> <dt><tt><i>FAQ distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.zip">help/uk-tex-faq</a> (<a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newans">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newans</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newans">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newans</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfontstar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfontstar.html new file mode 100644 index 00000000000..70ce959aeee --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfontstar.html @@ -0,0 +1,52 @@ +<head> +<title>UK TeX FAQ -- question label newfont*</title> +</head><body> +<h3>What’s wrong with <code>\</code><code>newfont</code>?</h3> +<p/>If all else fails, you <em>can</em> specify a font using the LaTeX +<code>\</code><code>newfont</code> command. The font so specified doesn’t fit into the +LaTeX font selection mechanism, but the technique can be tempting +under several circumstances. The command is merely the thinnest of +wrappers around the <code>\</code><code>font</code> primitive, and doesn’t really fit with +LaTeX at all. A simple, but really rather funny, example of the +problems it poses, may be seen in: +<blockquote> +<pre> +\documentclass[10pt]{article} +\begin{document} +\newfont{\myfont}{cmr17 scaled 2000} +\myfont +\LaTeX +\end{document} +</pre> +</blockquote><p> +(the reader is encouraged to try this). The “A” of <code>\</code><code>LaTeX</code> pretty +much disappears: LaTeX chooses the size on the “A” according to +<em>its</em> idea of the font size (10pt), but positions it according to +the dimensions of “<code>\</code><code>myfont</code>”, which is more than three times +that size. +<p/>Another “<code>\</code><code>myfont</code>” example arises from an entirely different +source. The mini-document: +<blockquote> +<pre> +\documentclass{article} +\begin{document} +\newfont{\myfont}{ecrm1000} +{\myfont voil\`a} +\end{document} +</pre> +</blockquote><p> +gives you “German low double quotes” (under the “a”) in place of +the grave accent. This happens because <i>ecrm1000</i> is in a +different <a href="FAQ-whatenc.html">font encoding</a> than LaTeX is +expecting — if you use the LaTeX <i>fontenc</i> package to +select the EC fonts, all these tiresome encoding issues are +solved for you, behind the scenes. +<p/>There does however remain a circumstance when you will be tempted to +use <code>\</code><code>newfont</code> — viz., to get a font size that doesn’t fall into +the Knuth standard set of sizes: LaTeX (by default) won’t allow you +to use such a size. Don’t despair: see the answer +“<a href="FAQ-fontsize.html">arbitrary font sizes</a>”. +<p/> +<p/> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfont*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfont*</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfunction.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfunction.html index fcf30d12aba..3e6065fe3b8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfunction.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newfunction.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label newfunction</title> </head><body> <h3>Defining a new log-like function in LaTeX</h3> -<p>Use the <code>\</code><code>mathop</code> command, as in: +<p/>Use the <code>\</code><code>mathop</code> command, as in: <blockquote> <pre> \newcommand{\diag}{\mathop{\mathrm{diag}}} </pre> </blockquote><p> -<p>Subscripts and superscripts on <code>\</code><code>diag</code> will be placed below and +<p/>Subscripts and superscripts on <code>\</code><code>diag</code> will be placed below and above the function name, as they are on <code>\</code><code>lim</code>. If you want your subscripts and superscripts always placed to the right, do: @@ -18,7 +18,7 @@ to the right, do: \newcommand{\diag}{\mathop{\mathrm{diag}}\nolimits} </pre> </blockquote><p> -<p>AMSLaTeX (in its <i>amsopn</i> package, which is automatically +<p/>AMSLaTeX (in its <i>amsopn</i> package, which is automatically loaded by <i>amsmath</i>) provides a command <code>\</code><code>DeclareMathOperator</code> that takes does the same job as the first definition above. To create our original <code>\</code><code>diag</code> command, one would @@ -31,14 +31,25 @@ say: <code>\</code><code>DeclareMathOperator*</code> declares the operator always to have its sub- and superscripts in the “<a href="FAQ-limits.html"><code>\</code><code>limits</code> position</a>”. -<p>The <i>amsopn</i> command <code>\</code><code>operatorname</code> allows you to -introduce <em>ad hoc</em> operators into your mathematics; as with -<code>\</code><code>DeclareMathOperator</code> there’s a starred version +<p/>The <i>amsopn</i> command <code>\</code><code>operatorname</code> allows you to +introduce <em>ad hoc</em> operators into your mathematics, so +<blockquote> + <code>\</code><code>[</code> <code>\</code><code>operatorname{foo}</code><code>(bar)</code> <code>\</code><code>]</code> +</blockquote><p> +typesets the same as +<blockquote> +<pre> +\DeclareMathOperator{\foo}{foo} +... +\[ \foo(bar) \] +</pre> +</blockquote><p> +As with <code>\</code><code>DeclareMathOperator</code> there’s a starred version <code>\</code><code>operatorname*</code> for sub- and superscripts in the limits position. -<p>(It should be noted that “log-like” was reportedly a <em>joke</em> on +<p/>(It should be noted that “log-like” was reportedly a <em>joke</em> on Lamport’s part; it is of course clear what was meant.) <dl> <dt><tt><i>amsopn.sty</i></tt><dd>In the AMSLaTeX distribution <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfunction">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfunction</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfunction">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newfunction</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlang.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlang.html index 20fd4797ce8..297fa5858c8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlang.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlang.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label newlang</title> </head><body> <h3>Using a new language with Babel</h3> -<p><i>Babel</i> is capable of working with a large range of +<p/><i>Babel</i> is capable of working with a large range of languages, and a new user often wants to use a language that her TeX installation is not set up to employ. Simply asking Babel to use the language, with the command @@ -16,7 +16,7 @@ Package babel Warning: No hyphenation patterns were loaded for (babel) I will use the patterns loaded for \language=0 instead. </pre> -<p>The problem is that your TeX system doesn’t know how to hyphenate +<p/>The problem is that your TeX system doesn’t know how to hyphenate Catalan text: you need to tell it how before Babel can do its work properly. To do this, for LaTeX installations, one needs to change <i>language.dat</i> (which is part of the Babel installation); it will @@ -27,7 +27,7 @@ contain a line which, if you remove the comment marker, is supposed to instruct LaTeX to load Catalan hyphenation patterns when you tell it to build a new format. -<p>Unfortunately, in many Babel distributions, the line just isn’t +<p/>Unfortunately, in many Babel distributions, the line just isn’t right — you need to check the name of the file containing the patterns you’re going to use. As you can see, in the author’s system, the name is supposed to be <i>cahyphen.tex</i>; however the file @@ -36,8 +36,8 @@ the error should prove little more than an inconvenience (most of the files are in better distributions anyway, but an elusive one may be found on CTAN; if you have to retrieve a new file, ensure that it’s correctly installed, for which see -<a href="FAQ-instpackages.html">installing a new package</a>). -<p>Finally, you need to regenerate the formats used (in fact, most users +<a href="FAQ-inst-wlcf.html">installing a new package</a>). +<p/>Finally, you need to regenerate the formats used (in fact, most users of Babel are using it in their LaTeX documents, so regenerating the LaTeX-related formats will ordinarily be enough; however, the author always generates the lot, regardless). @@ -50,9 +50,9 @@ texconfig hyphen latex which first enters an editor for you to edit <i>language.dat</i>, and then regenerates the format you specify (<i>latex</i> in this case). -<p> Otherwise, to regenerate all formats, do: <br> +<p/> Otherwise, to regenerate all formats, do: <br> <code>fmtutil --all</code> -<p> If you’re willing to think through what you’re doing (this is +<p/> If you’re willing to think through what you’re doing (this is <em>not</em> for the faint-hearted), you can select a sequence of formats and for each one, run: <br> <code>fmtutil --byfmt <<i>formatname</i>></code><br> @@ -68,9 +68,9 @@ texconfig hyphen latex <code>Maintenance</code>-> <code>Create all format files</code> -<p> or get a DOS window and run:<br> +<p/> or get a DOS window and run:<br> <code>initexmf --dump</code> -<p> On a <i>MiKTeX</i> distribtution v2.0 or later, the whole +<p/> On a <i>MiKTeX</i> distribtution v2.0 or later, the whole procedure can be done via the GUI. To select the new language, do:<br> <code>Start</code>-> @@ -80,12 +80,12 @@ texconfig hyphen latex Select your language from the list, press the <code>Apply</code> button, and then the <code>OK</code> button. Then select the <code>General</code> tab and press the <code>Update Now</code> button. -<p> Otherwise, edit the <i>language.dat</i> file (as outlined above), +<p/> Otherwise, edit the <i>language.dat</i> file (as outlined above), and then run:<br> <code>initexmf --dump</code><br> just as for a pre-v2.0 system. </dl> -<p><b><em>Caveat</em>:</b> It is (just) possible that +<p/><b><em>Caveat</em>:</b> It is (just) possible that your TeX system may run out of “pattern memory” while generating the new format. Most TeX implementations have fixed-size arrays for storing the details of hyphenation patterns, but although their @@ -97,5 +97,5 @@ it may be worth scanning the list of languages in your <dt><tt><i>babel</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/babel.zip">macros/latex/required/babel</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/babel.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/babel/">browse</a>) <dt><tt><i>hyphenation patterns</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/language/hyphenation.zip">language/hyphenation</a> (<a href="ftp://cam.ctan.org/tex-archive/language/hyphenation.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/language/hyphenation/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlang">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlang</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlang">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlang</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlineargs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlineargs.html index 68a8d346ccf..ea8b6608c1d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlineargs.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-newlineargs.html @@ -3,7 +3,7 @@ </head><body> <h3>Start of line goes awry</h3> <!-- asterisk square bracket start line --> -<p>This answer concerns two sorts of problems: errors of the form +<p/>This answer concerns two sorts of problems: errors of the form <blockquote> <pre> ! Missing number, treated as zero. @@ -14,15 +14,15 @@ </blockquote><p> and those where a single asterisk at the start of a line mysteriously fails to appear in the output. -<p>Both problems arise because <code>\</code><code>\</code> takes optional arguments. The +<p/>Both problems arise because <code>\</code><code>\</code> takes optional arguments. The command <code>\</code><code>\*</code> means “break the line here, and inhibit page break following the line break”; the command <code>\</code><code>\[</code><<i>dimen</i>><code>]</code> means “break the line here and add <<i>dimen</i>> extra vertical space afterwards”. -<p>So why does <code>\</code><code>\</code> get confused by these things at the start of a +<p/>So why does <code>\</code><code>\</code> get confused by these things at the start of a line? It’s looking for the first non-blank thing, and in the test it uses ignores the end of the line in your input text. -<p>The solution is to enclose the stuff at the start of the new line in +<p/>The solution is to enclose the stuff at the start of the new line in braces: <blockquote> <pre> @@ -36,7 +36,7 @@ braces: (The above text derives from an actual post to <i>comp.text.tex</i>; this particular bit of typesetting could plainly also be done using the <code>verbatim</code> environment.) -<p>The problem also appears in maths mode, in arrays and so on. In this +<p/>The problem also appears in maths mode, in arrays and so on. In this case, large-scale bracketing of things is <em>not</em> a good idea; the TeX primitive <code>\</code><code>relax</code> (which does nothing except to block searches of this nature) may be used. From another @@ -51,8 +51,8 @@ searches of this nature) may be used. From another </blockquote><p> which is a usage this FAQ would not recommend, anyway: refer to the <a href="FAQ-eqnarray.html">reason not to use <code>eqnarray</code></a>. -<p>Note that the <i>amsmath</i> package modifies the behaviour of +<p/>Note that the <i>amsmath</i> package modifies the behaviour of <code>\\</code> in maths. With <i>amsmath</i>, the <code>eqnarray</code> example doesn’t need any special measures. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlineargs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlineargs</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlineargs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=newlineargs</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noans.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noans.html index b71d0f92289..2970987925d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noans.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noans.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label noans</title> </head><body> <h3>You don’t understand the answer</h3> -<p>While the FAQ maintainers don’t offer a ‘help’ service, they’re +<p/>While the FAQ maintainers don’t offer a ‘help’ service, they’re very keen that you understand the answers they’ve already written. They’re (almost) written “in a vacuum”, to provide something to cover a set of questions that have arisen; it’s always possible that they’re written in a way that a novice won’t understand them. -<p>Which is where you can help the community. Mail the +<p/>Which is where you can help the community. Mail the <a href="mailto:faq-devel@tex.ac.uk">maintainers</a> to report the answer that you find unclear, and (if you can) suggest @@ -15,10 +15,10 @@ what we need to clarify. Time permitting (the team is small and all its members are busy), we’ll try and clarify the answer. This way, with a bit of luck, we can together improve the value of this resource to the whole community. -<p>Note that the FAQ development email address is not for +<p/>Note that the FAQ development email address is not for answering questions: it’s for you to suggest which questions we should work on, or new questions we should answer in future editions. -<p>Those who simply ask questions at that address will be referred to +<p/>Those who simply ask questions at that address will be referred to <a href="mailto:texhax@tug.org"><i>texhax@tug.org</i></a> or to <i>comp.text.tex</i>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noans">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noans</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noans">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noans</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nocitestar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nocitestar.html index 013ce258b18..3e0337627c9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nocitestar.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nocitestar.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label nocite*</title> </head><body> <h3>Listing all your BibTeX entries</h3> -<p>LaTeX and BibTeX co-operate to offer special treatment of this +<p/>LaTeX and BibTeX co-operate to offer special treatment of this requirement. The command <code>\</code><code>nocite{*}</code> is specially treated, and causes BibTeX to generate bibliography entries for every entry in each <code>.bib</code> file listed in your <code>\</code><code>bibliography</code> statement, so that after a LaTeX–BibTeX–LaTeX sequence, you have a document with the whole thing listed. -<p>Note that LaTeX <em>doesn’t</em> produce +<p/>Note that LaTeX <em>doesn’t</em> produce “<code>Citation ... undefined</code>” or “<code>There were undefined references</code>” warnings in respect of @@ -16,5 +16,16 @@ document with the whole thing listed. LaTeX “by hand” (you <em>know</em> exactly how many times you have to run things), but the lack might confuse automatic processors that scan the log file to determine whether another run is necessary. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nocite*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nocite*</a> +<p/>A couple of packages are available, that aim to reduce the impact of +<code>\</code><code>nocite{*}</code> of a large citation database. <i>Biblist</i> +was written for use under LaTeX 2.09, but seems to work well enough; +<i>listbib</i> is more modern. Both provide their own +<code>.bst</code> files. (The impact of large databases was significant +in the old days of LaTeX systems with very little free memory; this +problem is less significant now than it once was.) +<dl> +<dt><tt><i>biblist.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/biblist.zip">macros/latex209/contrib/biblist</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/biblist.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex209/contrib/biblist/">browse</a>) +<dt><tt><i>listbib.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/listbib.zip">macros/latex/contrib/listbib</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/listbib.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/listbib/">browse</a>) +</dl> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nocite*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nocite*</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nodollar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nodollar.html index 7e8c7c7f90e..fe6805b81cd 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nodollar.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nodollar.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label nodollar</title> </head><body> <h3>“Missing <code>$</code> inserted”</h3> -<p>There are certain things that <em>only</em> work in maths mode. If your +<p/>There are certain things that <em>only</em> work in maths mode. If your document is not in maths mode and you have an <code>_</code> or a <code>^</code> character, TeX (and by inheritance, LaTeX too) will say <pre> @@ -14,16 +14,16 @@ commited a typo in failing to enter maths mode. TeX, therefore, tries to patch things up by inserting the <code>$</code> you ‘forgot’, so that the maths-only object will work; as often as not this will land you in further confusion. -<p>It’s not just the single-character maths sub- and superscript +<p/>It’s not just the single-character maths sub- and superscript operators: anything that’s built in or declared as a maths operation, from the simplest lower-case <code>\</code><code>alpha</code> through the inscrutable <code>\</code><code>mathchoice</code> primitive, and beyond, will provoke the error if misused in text mode. -<p>LaTeX offers a command <code>\</code><code>ensuremath</code>, which will put you in maths +<p/>LaTeX offers a command <code>\</code><code>ensuremath</code>, which will put you in maths mode for the execution of its argument, if necessary: so if you want an <code>\</code><code>alpha</code> in your running text, say <code>\</code><code>ensuremath{<code>\</code><code>alpha</code>}</code>; if the bit of running text somehow transmutes into a bit of mathematics, the <code>\</code><code>ensuremath</code> will become a no-op, so it’s pretty much always safe. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nodollar">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nodollar</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nodollar">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nodollar</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nofm.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nofm.html index 8726a73e346..311acf2188a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nofm.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nofm.html @@ -3,18 +3,18 @@ </head><body> <h3>Page numbering “<<i>n</i>> of <<i>m</i>>”</h3> -<p>Finding the page number of the last page of a document, from within +<p/>Finding the page number of the last page of a document, from within the document, is somewhat tricky. The <i>lastpage</i> package is therefore supplied to make life easy for us all; it defines a label <code>LastPage</code> whose number is <em>right</em> (after sufficiently many passes through LaTeX, of course). The <i>memoir</i> class also defines a “last page” label. -<p>The documentation of the <i>fancyhdr</i> package spells out exactly +<p/>The documentation of the <i>fancyhdr</i> package spells out exactly how one might actually use this information to produce page numbering as suggested in the question. <dl> <dt><tt><i>fancyhdr documentation</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.zip">macros/latex/contrib/fancyhdr</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fancyhdr.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyhdr/">browse</a>) <dt><tt><i>lastpage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lastpage.zip">macros/latex/contrib/lastpage</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/lastpage.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/lastpage/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nofm">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nofm</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nofm">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nofm</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nohyph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nohyph.html index cda9186ca1b..793582fa4f6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nohyph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nohyph.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label nohyph</title> </head><body> <h3>My words aren’t being hyphenated</h3> -<p>Let’s assume you’ve selected the right TeX ‘language’ — as +<p/>Let’s assume you’ve selected the right TeX ‘language’ — as explained in <a href="FAQ-hyphen.html">“how hyphenation works”</a>, you’re not likely to get the correct results typesetting one language using the hyphenation rules of another. (Select the proper language, @@ -11,7 +11,7 @@ you need another set of hyphenation patterns; see <a href="FAQ-newlang.html">“using a new language”</a> for advice on how to install it.) -<p>So what else can go wrong? +<p/>So what else can go wrong? <ul> <li> Since TeX version 3.0, the limits on how near to either end of a word hyphenation may take place have been programmable (see @@ -61,5 +61,5 @@ hyphenation; some feel the American hyphenation feels <dl> <dt><tt><i>hyphenat.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyphenat.zip">macros/latex/contrib/hyphenat</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyphenat.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyphenat/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nohyph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nohyph</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nohyph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nohyph</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noline.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noline.html index efa0517cb29..4363e53a8c9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noline.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noline.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label noline</title> </head><body> <h3>No line here to end</h3> -<p>The error +<p/>The error <blockquote> <pre> ! LaTeX Error: There's no line here to end. @@ -31,12 +31,12 @@ label. This would lead to an “<code>Underfull \hbox</code>” warning do any actual harm other than slowing down your LaTeX run, any message that doesn’t convey any information distracts for no useful purpose. -<p>The proper solution to the problem is to write a new sort of +<p/>The proper solution to the problem is to write a new sort of <code>description</code> environment, that does just what you’re after. (The <a href="FAQ-books.html"><em>LaTeX Companion</em></a> offers a rather wide selection of variants of these things.) -<p>The quick-and-easy solution, which avoids the warning, is to write: +<p/>The quick-and-easy solution, which avoids the warning, is to write: <blockquote> <pre> \begin{description} @@ -49,7 +49,7 @@ which fills out the under-full line before forcing its closure. The <i>expdlist</i> package provides the same functionality with its <code>\</code><code>breaklabel</code> command, and <i>mdwlist</i> provides it via its <code>\</code><code>desclabelstyle</code> command. -<p>The other common occasion for the message is when you’re using the +<p/>The other common occasion for the message is when you’re using the <code>center</code> (or <code>flushleft</code> or <code>flushright</code>) environment, and have decided you need extra separation between lines in the environment: @@ -79,6 +79,6 @@ by saying: <dt><tt><i>expdlist.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/expdlist.zip">macros/latex/contrib/expdlist</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/expdlist.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/expdlist/">browse</a>) <dt><tt><i>mdwlist.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse</a>) </dl> -<p> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noline</a> +<p/> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noline</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonfree.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonfree.html index 425df5a775d..4c62ea60570 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonfree.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonfree.html @@ -2,23 +2,65 @@ <title>UK TeX FAQ -- question label nonfree</title> </head><body> <h3>What’s the CTAN <code>nonfree</code> tree?</h3> -<p>The CTAN archives are currently restructuring their holdings -so that files that are ‘not free’ are held in a separate tree. The -definition of what is ‘free’ (for this purpose) is influenced by, but -not exactly the same as the - - -<a href="http://www.debian.org/social_contract#guidelines">Debian Free Software Guidelines (DFSG)</a>. -<p>Material is placed on the <code>nonfree</code> tree if it is not -freely-usable (e.g., if the material is shareware, commercial, or if -its usage is not permitted in certain domains at all, or without -payment). Users of the archive should check that they are entitled to -use material they have retrieved from the <code>nonfree</code> tree. -<p>The Catalogue (one of the prime sources for finding TeX-related -material via -<a href="FAQ-findfiles.html">web search</a>) lists the licence details in each -entry in its lists. -For details of the licence categories, see its -<a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/licenses.html">list of licences</a>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonfree">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonfree</a> +<p/>When CTAN was founded, in the 1990s, it was unusual to publish +the terms under which a TeX-related package was distributed (or, at +any rate, to publish those terms formally). +<p/>With the advent of the TeX <em>distributions</em>, however, people +started to realise the need for such information, to protect those who +create, distribute or sell the discs that hold the packages, etc. +With the licence information available, the distributors can decide +which packages may be distributed. +<p/>The CTAN team decided that it would be useful for users (and +distributors, not to say package authors) to separate packages that +were candidates for distribution, and those that were in some sense +“not free”. Thus was the <code>nonfree</code> tree born. +<p/>From the start, the <code>nonfree</code> tree was controversial: the terms +under which a package would be placed on the tree were hotly +contested, and the CTAN team were only able slowly to populate +the tree. It is now obvious to the team that the project would never +be completed. +<p/>The CTAN catalogue now records the nature of the licences of a +good proportion of the packages it describes (though there remain +several for which the licence is unknown, which is as good, for the +distributors, as a licence forbidding distribution). Since the +catalogue’s coverage of CTAN is good (and slowly improving), +the general rule for distributors has become +<blockquote> +“if the package is listed in the catalogue, check there to see +whether you should distribute; if the package is not listed in the +catalogue, don’t think of distributing it”. +</blockquote><p> +<p/>(The catalogue only has a modest +<a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/licenses.html">list of licences</a>, but it covers the set used +by packages on CTAN, with a wild-card “<code>other-free</code>” +which covers packages that the CTAN administrators believe to +be free even though the authors haven’t used a standard licence.) +<p/>In the light of the above, the <code>nonfree</code> tree is being +dismantled, and its contents moved to the main CTAN tree. So +the answer to the question is, now, “the nonfree tree is a part of +CTAN, and is now being merged with the main tree”. +<p/><p/> + + + + + + + + + + + +<p/> + + + + +<p/> + + + + + +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonfree">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonfree</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonpdfsp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonpdfsp.html index b901dfb8c0d..aa63ddd54c5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonpdfsp.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonpdfsp.html @@ -2,21 +2,21 @@ <title>UK TeX FAQ -- question label nonpdfsp</title> </head><body> <h3>Non-PDF special ignored!</h3> -<p>This is a PDFTeX error: PDFTeX is running in PDF output +<p/>This is a PDFTeX error: PDFTeX is running in PDF output mode, and it has encountered a <a href="FAQ-specials.html"><code>\</code><code>special</code></a> command. PDFTeX is able to generate its own output, and in this mode of operation has no need of <code>\</code><code>special</code> commands (which allow the user to pass information to the driver being used to generate output). -<p>Why does this happen? LaTeX users, nowadays, hardly ever use +<p/>Why does this happen? LaTeX users, nowadays, hardly ever use <code>\</code><code>special</code> commands on their own — they employ packages to do the job for them. Some packages will generate <code>\</code><code>special</code> commands however they are invoked: <i>pstricks</i> is an example (it’s very raison d’être is to emit PostScript code in a sequence of <code>\</code><code>special</code> commands). <i>Pstricks</i> may be dealt with by other means (the <i>pdftricks</i> package offers a usable technique). -<p>More amenable to correction, but more confusing, are packages (such as +<p/>More amenable to correction, but more confusing, are packages (such as <i>color</i>, <i>graphics</i> and <i>hyperref</i>) that specify a “driver”. These packages have plug-in modules that determine what <code>\</code><code>special</code> (or other commands) are needed to generate @@ -33,5 +33,5 @@ system recognise which driver is needed. <dt><tt><i>pdftricks.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdftricks.zip">macros/latex/contrib/pdftricks</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pdftricks.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pdftricks/">browse</a>) <dt><tt><i>pstricks.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.zip">graphics/pstricks</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pstricks.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pstricks/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonpdfsp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonpdfsp</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonpdfsp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonpdfsp</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonum.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonum.html index 37016846394..74783f3351c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonum.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonum.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label nonum</title> </head><body> <h3>“Missing number, treated as zero”</h3> -<p>In general, this means you’ve tried to assign something to a count, +<p/>In general, this means you’ve tried to assign something to a count, dimension or skip register that isn’t (in TeX’s view of things) a number. Usually the problem will become clear using the <a href="FAQ-erroradvice.html">ordinary techniques of examining errors</a>. -<p>Two LaTeX-specific errors are commonly aired on the newsgroups. -<p>The commonest arises from attempting to use an example from the +<p/>Two LaTeX-specific errors are commonly aired on the newsgroups. +<p/>The commonest arises from attempting to use an example from the <a href="FAQ-books.html"><em>The LaTeX Companion</em> (first edition)</a>, and is exemplified by the following error text: <pre> @@ -24,7 +24,7 @@ document using such examples from the <em>Companion</em>. (The problem does not really arise with the second edition; copies of all the examples are available on the accompanying CDROM, or on CTAN.) -<p>The other problem, which is increasingly rare nowadays, arises from +<p/>The other problem, which is increasingly rare nowadays, arises from misconfiguration of a system that has been upgraded from LaTeX 2.09: the document uses the <i>times</i> package, and the error appears at <code>\</code><code>begin{document}</code>. The file search paths are wrongly set @@ -44,5 +44,5 @@ text rather better. <dt><tt><i>Examples for LaTeX Companion</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/examples/tlc2.zip">info/examples/tlc2</a> (<a href="ftp://cam.ctan.org/tex-archive/info/examples/tlc2.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/examples/tlc2/">browse</a>) <dt><tt><i>The psnfss bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss.zip">macros/latex/required/psnfss</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/psnfss/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonum">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonum</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonum">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonum</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopagebrk.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopagebrk.html index 189dea74418..2916264f930 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopagebrk.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopagebrk.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label nopagebrk</title> </head><body> <h3>Preventing page breaks between lines</h3> -<p>One commonly requires that a block of typeset material be kept on the +<p/>One commonly requires that a block of typeset material be kept on the same page; it turns out to be surprisingly tricky to arrange this. -<p>LaTeX provides a <code>samepage</code> environment which claims it +<p/>LaTeX provides a <code>samepage</code> environment which claims it does this sort of thing for you. It proceeds by setting infinite penalties for all sorts of page-break situations; but in many situations where you want to prevent a page break, @@ -16,20 +16,20 @@ pagebreak hints, <code>samepage</code> has no power over them: a good exaple is list items — they suggest page breaks between them. Even if <code>samepage</code> <em>does</em> work, it’s likely to leave stuff jutting out at the bottom of the page. -<p>A convenient trick is to set all the relevant stuff in a <code>\</code><code>parbox</code> +<p/>A convenient trick is to set all the relevant stuff in a <code>\</code><code>parbox</code> (or a <code>minipage</code> if it contains things like verbatim text that may not be in the argument of a <code>\</code><code>parbox</code>). The resulting box certainly <em>won’t</em> break between pages, but that’s not to say that it will actually do what you want it to do: again, the box may be left jutting out at the bottom of the page. -<p>Why do neither of these obvious things work? Because TeX can’t +<p/>Why do neither of these obvious things work? Because TeX can’t really distinguish between infinitely awful things. <code>Samepage</code> will make any possible break point “infinitely bad” and boxes don’t even offer the option of breaks, but if the alternative is the leave an infinitely bad few centimetres of blank paper at the bottom of the page, TeX will take the line of least resistance and do nothing. -<p>This problem still arises even if you have <code>\</code><code>raggedbottom</code> in +<p/>This problem still arises even if you have <code>\</code><code>raggedbottom</code> in effect: TeX doesn’t notice the value of <em>that</em> until it starts actually shipping a page out. One approach is to set: <blockquote> @@ -51,7 +51,7 @@ as well as resetting <code>\</code><code>flushbottom</code>. (Note that the <co actually shows up, because it is overwhelmed when the page is shipped out by the stretchability introduced by <code>\</code><code>raggedbottom</code>; however, it could well have an effect if <code>\</code><code>flushbottom</code> was in effect.) -<p>An alternative (which derives from a suggestion by Knuth in the +<p/>An alternative (which derives from a suggestion by Knuth in the TeXbook) is the package <i>needspace</i> or the <i>memoir</i> class, which both define a command <code>\</code><code>needspace</code> whose argument tells it what space is needed. If the space isn’t available, the current page @@ -90,7 +90,7 @@ interrupted by a forced page break (such as <code>\</code><code>clearpage</code> be introduced by a <code>\</code><code>chapter</code> command, or the end of the document). If the sequence is not interrupted, the last block is likely to be forced onto a new page, regardless of whether it actually needs it. -<p>If one is willing to accept that not everything can be accomplished +<p/>If one is willing to accept that not everything can be accomplished totally automatically, the way to go is to typeset the document and to check for things that have the potential to give trouble. In such a scenario (which has Knuth’s authority behind it, if one is to believe @@ -107,5 +107,5 @@ command remains a useful item in the armoury. <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>needspace.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/needspace.sty">macros/latex/contrib/misc/needspace.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nopagebrk">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nopagebrk</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nopagebrk">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nopagebrk</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopageno.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopageno.html index ee7f0729a23..b755174cb2b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopageno.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nopageno.html @@ -2,19 +2,19 @@ <title>UK TeX FAQ -- question label nopageno</title> </head><body> <h3>How to get rid of page numbers</h3> -<p>The package <i>nopageno</i> will suppress page numbers in a whole +<p/>The package <i>nopageno</i> will suppress page numbers in a whole document. -<p>To suppress page numbers from a single page, use +<p/>To suppress page numbers from a single page, use <code>\</code><code>thispagestyle{empty}</code> somewhere within the text of the page. (Note that <code>\</code><code>maketitle</code> and <code>\</code><code>chapter</code> both use <code>\</code><code>thispagestyle</code> internally, so you need to call it after you’ve called them.) -<p>To suppress page numbers from a sequence of pages, you may use +<p/>To suppress page numbers from a sequence of pages, you may use <code>\</code><code>pagestyle{empty}</code> at the start of the sequence, and restore the original page style at the end. Unfortunately, you still have to use <code>\</code><code>thispagestyle</code> after any <code>\</code><code>maketitle</code> or <code>\</code><code>chapter</code> command. -<p>In the <i>memoir</i> class, the troublesome commands (<code>\</code><code>maketitle</code>, +<p/>In the <i>memoir</i> class, the troublesome commands (<code>\</code><code>maketitle</code>, <code>\</code><code>chapter</code>, etc.) invoke their own page style (<code>title</code>, <code>chapter</code>, etc.), which you may redefine using the class’s own techniques to be equivalent to @@ -25,13 +25,13 @@ commands that contain the page style to be used, so one might say: \renewcommand*{\titlepagestyle}{empty} </pre> </blockquote><p> -<p>An alternative (in all classes) is to use the rather delightful +<p/>An alternative (in all classes) is to use the rather delightful <code>\</code><code>pagenumbering{gobble}</code>; this has the simple effect that any attempt to print a page number produces nothing, so there’s no issue about preventing any part of LaTeX from printing the number. However, the <code>\</code><code>pagenumbering</code> command does have the side effect that it resets the page number (to 1), which may be undesirable. -<p>The <i>scrpage2</i> package separates out the representation from +<p/>The <i>scrpage2</i> package separates out the representation from the resetting; so one can say <blockquote> <pre> @@ -46,5 +46,5 @@ resetting the page number. <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>scrpage2.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nopageno">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nopageno</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nopageno">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nopageno</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-normalszmiss.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-normalszmiss.html index f5e40246587..d2605726723 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-normalszmiss.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-normalszmiss.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label normalszmiss</title> </head><body> <h3><code>\</code><code>normalsize</code> not defined</h3> -<p>The LaTeX error: +<p/>The LaTeX error: <blockquote> <pre> @@ -14,5 +14,5 @@ is reporting something pretty fundamental (document base font size not set up). While this <em>can</em>, as the message implies, be due to a broken class file, the more common cause is that you have simply forgotten to put a <code>\</code><code>documentclass</code> command in your document. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=normalszmiss">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=normalszmiss</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=normalszmiss">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=normalszmiss</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noroom.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noroom.html index cf320e54560..a1f154fd3c2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noroom.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-noroom.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label noroom</title> </head><body> <h3>No room for a new ‘<em>thing</em>’</h3> -<p>The technology available to Knuth at the time TeX was written is +<p/>The technology available to Knuth at the time TeX was written is said to have been particularly poor at managing dynamic storage; as a result much of the storage used within TeX is allocated as fixed arrays, in the reference implementations. Many of these fixed arrays @@ -12,7 +12,7 @@ arrays of “registers” is written into the specification as being 256 the result TeX (see <a href="FAQ-triptrap.html">testing TeX implementations</a>). -<p>If you fill up one of these register arrays, you get a TeX error +<p/>If you fill up one of these register arrays, you get a TeX error message saying <blockquote> <pre> @@ -26,20 +26,20 @@ LaTeX’s <code>\</code><code>newsavebox</code> command), or <code>\</code>< <code>\</code><code>toks</code>, <code>\</code><code>read</code>, <code>\</code><code>write</code> or <code>\</code><code>language</code> (all types of object whose use is “hidden” in LaTeX; the limit on the number of <code>\</code><code>read</code> or <code>\</code><code>write</code> objects is just 16). -<p>There is nothing that can directly be done about this error, as you can’t +<p/>There is nothing that can directly be done about this error, as you can’t extend the number of available registers without extending TeX itself. Of course, <a href="FAQ-etex.html">e-TeX</a> and <a href="FAQ-omegaleph.html">Omega</a> both do this, as does <a href="FAQ-commercial.html">MicroPress Inc’s VTeX</a>. -<p>The commonest way to encounter one of these error messages is to have +<p/>The commonest way to encounter one of these error messages is to have broken macros of some sort, or incorrect usage of macros (an example is discussed in <a href="FAQ-epsf.html">epsf problems</a>). -<p>However, sometimes one just <em>needs</em> more than TeX can offer, +<p/>However, sometimes one just <em>needs</em> more than TeX can offer, and when this happens, you’ve just got to work out a different way of doing things. An example is the -<a href="FAQ-usepictex.html">difficulty of loading PiCTeX with LaTeX</a>. -In cases like PiCTeX, it may be possible to use +<a href="FAQ-usepictex.html">difficulty of loading PicTeX with LaTeX</a>. +In cases like PicTeX, it may be possible to use <a href="FAQ-etex.html">e-TeX</a> (all modern distributions provide it). The LaTeX package <i>etex</i> modifies the register allocation mechanism to make use of e-TeX’s extended register sets (it’s a @@ -47,5 +47,5 @@ derivative of the Plain TeX macro file <i>etex.src</i>, which is used in building the e-TeX Plain format; both files are part of the e-TeX distribution). Unfortunately, e-TeX doesn’t help with <code>\</code><code>read</code> or <code>\</code><code>write</code> objects. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noroom">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noroom</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noroom">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=noroom</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-notWYSIWYG.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-notWYSIWYG.html index 069f6c96eb1..09247c59096 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-notWYSIWYG.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-notWYSIWYG.html @@ -2,24 +2,24 @@ <title>UK TeX FAQ -- question label notWYSIWYG</title> </head><body> <h3>Why is TeX not a WYSIWYG system?</h3> -<p>WYSIWYG is a marketing term (“What you see is what you get”) for +<p/>WYSIWYG is a marketing term (“What you see is what you get”) for a particular style of text processor. WYSIWYG systems are characterised by two principal claims: that you type what you want to print, and that what you see on the screen as you type is a close approximation to how your text will finally be printed. -<p>The simple answer to the question is, of course, that TeX was +<p/>The simple answer to the question is, of course, that TeX was conceived long before the marketing term, at a time when the marketing imperative wasn’t perceived as significant. However, that was a long time ago: why has nothing been done with the “wonder text processor” to make it fit with modern perceptions? -<p>There are two answers to this. First, the simple “things <em>have</em> +<p/>There are two answers to this. First, the simple “things <em>have</em> been done” (but they’ve not taken over the TeX world); and second, “there are philosophical reasons why the way TeX has developed is ill-suited to the WYSIWYG style”. Indeed, there is a fundamental problem with applying WYSIWYG techniques to TeX: the complexity of TeX makes it hard to get the equivalent of TeX’s output without actually running TeX. -<p>A celebrated early system offering “WYSIWYG using TeX” came from the +<p/>A celebrated early system offering “WYSIWYG using TeX” came from the VorTeX project: a pair of (early) Sun workstations worked in tandem, one handling the user interface while the other beavered away in the background typesetting the result. VorTeX was quite @@ -32,11 +32,11 @@ their approach are Lightning Textures (an extension of Blue Sky’s original TeX system for the Macintosh), and Scientific Word (which can also cooperate with a computer algebra system); both these systems are <a href="FAQ-commercial.html">commercially available</a>. -<p>The issue has of recent years started to attract attention from TeX +<p/>The issue has of recent years started to attract attention from TeX developers, and several interesting projects addressing the “<a href="FAQ-WYGexpts.html">TeX document preparation environment</a>” are in progress. -<p>Nevertheless, the TeX world has taken a long time to latch onto the +<p/>Nevertheless, the TeX world has taken a long time to latch onto the idea of WYSIWYG. Apart from simple arrogance (“we’re better, and have no need to consider the petty doings of the commercial word processor market”), @@ -47,7 +47,7 @@ where every object within the document is labelled according to what it is rather than how it should appear: appearance is deduced from the properties of the type of object. Properly applied, markup can provide valuable assistance when it comes to re-use of documents. -<p>Established WYSIWYG systems find the expression of this sort of +<p/>Established WYSIWYG systems find the expression of this sort of structured markup difficult; however, markup <em>is</em> starting to appear in the lists of the commercial world’s requirements, for two reasons. First, an element of markup helps impose style on a @@ -58,5 +58,5 @@ challenges must needs be addressed by TeX-based document preparation support schemes, so we are observing a degree of confluence of the needs of the two communities: interesting times may be ahead of us. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=notWYSIWYG">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=notWYSIWYG</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=notWYSIWYG">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=notWYSIWYG</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-numbersets.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-numbersets.html index cfa682358c0..57edaa32534 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-numbersets.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-numbersets.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label numbersets</title> </head><body> <h3>Symbols for the number sets</h3> -<p>It is a good idea to have commands such as <code>\</code><code>R</code> for the real numbers and +<p/>It is a good idea to have commands such as <code>\</code><code>R</code> for the real numbers and other standard number sets. Traditionally these were typeset in bold. Because, in the ordinary course of events, mathematicians do not have access to bold chalk, they invented the special symbols that are now @@ -10,7 +10,7 @@ often used for <code>\</code><code>R</code>, <code>\</code><code>C</code>, <em>e as “blackboard bold”. Before insisting on using them, consider whether going back to the old system of ordinary bold might not be acceptable (it is certainly simpler). -<p>A set of blackboard bold capitals is available in the AMS +<p/>A set of blackboard bold capitals is available in the AMS <i>msbm</i> fonts (<i>msbm</i> is available at a range of design sizes, with names such as <i>msbm10</i>). The pair of font families (the other is called <i>msam</i>) have a large number of @@ -21,20 +21,20 @@ Plain TeX and LaTeX (packages <i>amssymb</i> and <i>amsfonts</i>), are available. The font shape is a rather austere sans, which many people don’t like (though it captures the essence of quickly-chalked writing rather well). -<p>The <i>bbold</i> family is set of blackboard bold fonts written in +<p/>The <i>bbold</i> family is set of blackboard bold fonts written in Metafont. This set offers blackboard bold forms of lower-case letters; the font source directory also contains sources for a LaTeX package that enables use of the fonts. The fonts are not available in Type 1 format. -<p>The <i>bbm</i> family claims to provide +<p/>The <i>bbm</i> family claims to provide ‘blackboard’ versions of most of the <i>cm</i> fonts ... including the bold and bold-extended series. Again, the fonts are designed in Metafont and are not available in Type 1 format. LaTeX macro support comes from a package by Torsten Hilbrich. -<p>The <i>doublestroke</i> family comes in just roman +<p/>The <i>doublestroke</i> family comes in just roman and sans shapes, at a single weight, and is available both as Metafont sources and as Type 1; the font covers the uppercase latin letters, lowercase ‘h’ and ’k’, and the digit ‘1’. -<p>An alternative source of Type 1 fonts with blackboard bold characters +<p/>An alternative source of Type 1 fonts with blackboard bold characters may be found in the steadily increasing set of complete families, both commercial and free, that have been prepared for use with (La)TeX (see @@ -46,7 +46,7 @@ fonts). The <i>mathpazo</i> family includes a “mathematically significant” choice of blackboard bold characters, and the <i>fourier</i> fonts contain blackboard bold upper-case letters, the digit ‘1’, and lower-case ‘k’. -<p>The “lazy person’s” blackboard bold macros: +<p/>The “lazy person’s” blackboard bold macros: <blockquote> <pre> \newcommand{\R}{{\sf R\hspace*{-0.9ex}% @@ -80,5 +80,5 @@ looks even worse!). <dt><tt><i>pxfonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/pxfonts.zip">fonts/pxfonts</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/pxfonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/pxfonts/">browse</a>) <dt><tt><i>txfonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/txfonts.zip">fonts/txfonts</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/txfonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/txfonts/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=numbersets">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=numbersets</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=numbersets">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=numbersets</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oarglikesect.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oarglikesect.html index e5de72fef15..ee818a6709e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oarglikesect.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oarglikesect.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label oarglikesect</title> </head><body> <h3>Optional arguments like <code>\</code><code>section</code></h3> -<p>Optional arguments, in macros defined using <code>\</code><code>newcommand</code>, don’t +<p/>Optional arguments, in macros defined using <code>\</code><code>newcommand</code>, don’t quite work like the optional argument to <code>\</code><code>section</code>. The default value of <code>\</code><code>section</code>’s optional argument is the value of the mandatory argument, but <code>\</code><code>newcommand</code> requires that you ‘know’ the value of the default beforehand. -<p>The requisite trick is to use a macro in the optional argument: +<p/>The requisite trick is to use a macro in the optional argument: <blockquote> <pre> \documentclass{article} @@ -36,5 +36,5 @@ above would have been programmed: In that code, <code>\</code><code>@thing</code> is only ever called with an optional and a mandatory argument; if the default from the <code>\</code><code>newcommand</code> is invoked, a bug in user code has bitten... -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oarglikesect">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oarglikesect</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oarglikesect">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oarglikesect</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddhyphen.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddhyphen.html index 5831983ded8..c7190c78a0a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddhyphen.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddhyphen.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label oddhyphen</title> </head><body> <h3>(Merely) peculiar hyphenation</h3> -<p>You may have found that TeX’s famed automatic word-division does +<p/>You may have found that TeX’s famed automatic word-division does not produce the break-points recommended by your dictionary. This may be because TeX is set up for American English, whose rules for word division (as specified, for example, in Webster’s Dictionary) are @@ -17,5 +17,5 @@ on adding this new “language”). <dl> <dt><tt><i>UK patterns</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/language/hyphenation/ukhyphen.tex">language/hyphenation/ukhyphen.tex</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oddhyphen">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oddhyphen</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oddhyphen">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oddhyphen</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddpage.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddpage.html index 8f8332eeab4..5ad4bc7e7d4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddpage.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oddpage.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label oddpage</title> </head><body> <h3>Finding if you’re on an odd or an even page</h3> -<p><a href="FAQ-marginparside.html">Another question</a> discusses the issue +<p/><a href="FAQ-marginparside.html">Another question</a> discusses the issue of getting <code>\</code><code>marginpar</code> commands to put their output in the correct margin of two-sided documents. This is an example of the general problem of knowing where a particular bit of text lies: the output @@ -11,18 +11,18 @@ bit of the “next” page before deciding to output any page. As a result, the <code>page</code> counter (known internally in LaTeX as <code>\</code><code>c@page</code>) is normally only reliable when you’re actually <em>in</em> the output routine. -<p>The solution is to use some version of the <code>\</code><code>label</code> mechanism to +<p/>The solution is to use some version of the <code>\</code><code>label</code> mechanism to determine which side of the page you’re on; the value of the page counter that appears in a <code>\</code><code>pageref</code> command has been inserted in the course of the output routine, and is therefore safe. -<p>However, <code>\</code><code>pageref</code> itself isn’t reliable: one might hope that +<p/>However, <code>\</code><code>pageref</code> itself isn’t reliable: one might hope that <pre> \ifthenelse{\isodd{\pageref{foo}}}{odd}{even} </pre> would do the necessary, but both the <i>babel</i> and <i>hyperref</i> packages have been known to interfere with the output of <code>\</code><code>pageref</code>; be careful! -<p>The <i>chngpage</i> package needs to provide this functionality for +<p/>The <i>chngpage</i> package needs to provide this functionality for its own use, and therefore provides a command <code>\</code><code>checkoddpage</code>; this sets a private-use label, and the page reference part of that label is then examined (in a <i>hyperref</i>-safe way) to set a conditional @@ -30,7 +30,7 @@ then examined (in a <i>hyperref</i>-safe way) to set a conditional <i>memoir</i> class has the same command setting a conditional <code>\</code><code>ifoddpage</code>. Of course, the <code>\</code><code>label</code> contributes to LaTeX’s “Rerun to get cross-references right” error messages... -<p>The Koma-Script classes have an <code>addmargin*</code> environment +<p/>The Koma-Script classes have an <code>addmargin*</code> environment that also provides the sorts of facilities that the <i>chngpage</i> offers. Koma-Script’s supporting command is <code>\</code><code>ifthispageodd{<true>}{<false>}</code> executes different things @@ -40,5 +40,5 @@ depending on the page number. <dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oddpage">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oddpage</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oddpage">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oddpage</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ol-books.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ol-books.html index 9136865f352..52b45d9bb96 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ol-books.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ol-books.html @@ -2,19 +2,18 @@ <title>UK TeX FAQ -- question label ol-books</title> </head><body> <h3>Freely available (La)TeX books</h3> -<p>People have long argued for (La)TeX books to be made available on +<p/>People have long argued for (La)TeX books to be made available on the web, and until relatively recently this demand went un-answered. -<p>The first to appear was Victor Eijkhout’s excellent “TeX by +<p/>The first to appear was Victor Eijkhout’s excellent “TeX by Topic” in 2001 (it had been published by Addison-Wesley, but was long -out of print). The book is currently available at -<a href="http://www.eijkhout.net/tbt/">http://www.eijkhout.net/tbt/</a>; it’s not a beginner’s tutorial but -it’s a fine reference. -<p>Addison-Wesley have also released the copyright of “TeX for the +out of print). The book is now available on CTAN; it’s not a +beginner’s tutorial but it’s a fine reference. +<p/>Addison-Wesley have also released the copyright of “TeX for the Impatient” by Paul W. Abrahams, Karl Berry and Kathryn A. Hargreaves, another book whose unavailability many have lamented. The authors have re-released the book under the GNU general documentation licence, and it is available from CTAN. -<p>Norm Walsh’s “Making TeX Work” (originally published by O’Reilly) +<p/>Norm Walsh’s “Making TeX Work” (originally published by O’Reilly) is also available (free) on the Web, at <a href="http://makingtexwork.sourceforge.net/mtw/">http://makingtexwork.sourceforge.net/mtw/</a>; the sources of the Web page are on CTAN. The book was an excellent resource in @@ -23,7 +22,8 @@ and is a welcome addition to the list of on-line resources. A project to update it is believed to be under way. <dl> <dt><tt><i>Making TeX Work</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/makingtexwork/mtw-1.0.1-html.tar.gz">info/makingtexwork/mtw-1.0.1-html.tar.gz</a> +<dt><tt><i>TeX by Topic</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/texbytopic.zip">info/texbytopic</a> (<a href="ftp://cam.ctan.org/tex-archive/info/texbytopic.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/texbytopic/">browse</a>) <dt><tt><i>TeX for the Impatient</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/impatient.zip">info/impatient</a> (<a href="ftp://cam.ctan.org/tex-archive/info/impatient.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/info/impatient/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ol-books">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ol-books</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ol-books">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ol-books</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oldfontnames.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oldfontnames.html index ba0374a88ca..d53ed253afb 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oldfontnames.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-oldfontnames.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label oldfontnames</title> </head><body> <h3>Old LaTeX font references such as <code>\</code><code>tenrm</code></h3> -<p>LaTeX 2.09 defined a large set of commands for access to the fonts +<p/>LaTeX 2.09 defined a large set of commands for access to the fonts that it had built in to itself. For example, various flavours of <code>cmr</code> could be found as <code>\</code><code>fivrm</code>, <code>\</code><code>sixrm</code>, <code>\</code><code>sevrm</code>, <code>\</code><code>egtrm</code>, <code>\</code><code>ninrm</code>, <code>\</code><code>tenrm</code>, <code>\</code><code>elvrm</code>, <code>\</code><code>twlrm</code>, <code>\</code><code>frtnrm</code>, <code>\</code><code>svtnrm</code>, <code>\</code><code>twtyrm</code> and <code>\</code><code>twfvrm</code>. These commands were never documented, but certain packages nevertheless used them to achieve effects they needed. -<p>Since the commands weren’t public, they weren’t included in LaTeX2e; +<p/>Since the commands weren’t public, they weren’t included in LaTeX2e; to use the unconverted LaTeX 2.09 packages under LaTeX2e, you need also to include the <i>rawfonts</i> package (which is part of the LaTeX2e distribution). -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oldfontnames">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oldfontnames</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oldfontnames">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=oldfontnames</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-omegaleph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-omegaleph.html index 2a8b40146c5..f8a4d6d829f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-omegaleph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-omegaleph.html @@ -2,24 +2,24 @@ <title>UK TeX FAQ -- question label omegaleph</title> </head><body> <h3>Omega and Aleph</h3> -<p>Omega was developed as an extension of +<p/>Omega was developed as an extension of TeX, to use with multilingual texts, expressed in a variety of input encodings. Omega uses 16-bit, Unicode-encoded, characters. It provides many innovative concepts, notably including the “translation process” that takes a character stream and transforms it according to various processes that may be internally specified, or be a separate program. -<p>While Omega showed a lot of promise at its mid-1990s announcement, its +<p/>While Omega showed a lot of promise at its mid-1990s announcement, its development was slow, and development was essentially dead by the time that one of the original developers withdrew (taking with him a bunch of research students). -<p>Before that distressing event, a separate thread of development was +<p/>Before that distressing event, a separate thread of development was started, to produce a program called Aleph , which merged the facilities of <a href="FAQ-etex.html">e-TeX</a> into a stable Omega codebase and added other extensions. Aleph also proved an attractive platform for many people; but its development, too, has dried up. -<p>The latest news (from EuroTeX 2006) is that development of Omega is +<p/>The latest news (from EuroTeX 2006) is that development of Omega is picking up again, in parallel with research into what the (new) authors consider a rational scheme for supporting TeX-style typesetting. The new system is to be known as Omega-2 @@ -27,7 +27,7 @@ typesetting. The new system is to be known as Omega-2 designed in a modular fashion so that support of new facilities (such as use of advanced OpenType fonts) can be added in a relatively straightforward fashion. -<p>The work done in the Aleph project is also being carried forward in -the <a href="FAQ-luatex.html">LUATeX</a> project. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=omegaleph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=omegaleph</a> +<p/>The work done in the Aleph project is also being carried forward in +the <a href="FAQ-luatex.html">LuaTeX</a> project. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=omegaleph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=omegaleph</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-onecolabs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-onecolabs.html index eddafb746f6..acd67d35d03 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-onecolabs.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-onecolabs.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label onecolabs</title> </head><body> <h3>1-column abstract in 2-column document</h3> -<p>One often requires that the abstract of a paper should appear across +<p/>One often requires that the abstract of a paper should appear across the entire page, even in a two-column paper. The required trick is: <pre> \documentclass[twocolumn]{article} @@ -34,7 +34,7 @@ can make them like this: } </pre> and so on. -<p>As an alternative, among other facilities the <i>abstract</i> package +<p/>As an alternative, among other facilities the <i>abstract</i> package provides a <code>\</code><code>saythanks</code> command and a <code>onecolabstract</code> environment which remove the need to fiddle with the <code>\</code><code>thanks</code> and @@ -53,5 +53,5 @@ The <i>memoir</i> class offers all the facilities of <i>abstract</i>. <dt><tt><i>abstract.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/abstract.zip">macros/latex/contrib/abstract</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/abstract.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/abstract/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=onecolabs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=onecolabs</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=onecolabs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=onecolabs</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-optionclash.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-optionclash.html index 950e0536391..f42f1325341 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-optionclash.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-optionclash.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label optionclash</title> </head><body> <h3>Option clash for package</h3> -<p>So you’ve innocently added: +<p/>So you’ve innocently added: <blockquote> <code>\</code><code>usepackage[draft]{graphics}</code> </blockquote><p> @@ -13,13 +13,13 @@ to your document, and LaTeX responds with </pre> </blockquote><p> -<p>The error is a complaint about loading a package +<p/>The error is a complaint about loading a package <em>with options</em>, more than once (LaTeX doesn’t actually examine what options there are: it complains because it can’t do anything with the multiple sets of options). You can load a package any number of times, with no options, and LaTeX will be happy, but you may only supply options when you first load the package. -<p>So perhaps you weren’t entirely innocent — the error would have +<p/>So perhaps you weren’t entirely innocent — the error would have occurred on the second line of: <blockquote> <code>\</code><code>usepackage[dvips]{graphics}</code><br> @@ -29,7 +29,7 @@ which could quite reasonably (and indeed correctly) have been typed: <blockquote> <code>\</code><code>usepackage[dvips,draft]{graphics}</code> </blockquote><p> -<p>But if you’ve not made that mistake (even with several lines +<p/>But if you’ve not made that mistake (even with several lines separating the <code>\</code><code>usepackage</code> commands, it’s pretty easy to spot), the problem could arise from something else loading the package for you. How do you find the culprit? The "<code>h</code>" response to the @@ -50,10 +50,10 @@ will contain something like: </pre> </blockquote><p> (the parentheses for <i>graphics</i> are completely enclosed in -those for <i>foo</i>; the same is of course true if <i>bar</i> is -the culprit, except that the line will start with the path to -<code>bar.cls</code>). -<p>If we’re dealing with a package that loads the package you are +those for <i>foo</i>; the same is of course true if your class +<i>bar</i> is the culprit, except that the line will start with the +path to <code>bar.cls</code>). +<p/>If we’re dealing with a package that loads the package you are interested in, you need to ask LaTeX to slip in options when <i>foo</i> loads it. Instead of: <blockquote> @@ -70,7 +70,7 @@ its options were passed, when it finally loads a package. As you would expect from its name, <code>\</code><code>PassOptionsToPackage</code> can deal with a list of options, just as you would have in the the options brackets of <code>\</code><code>usepackage</code>. -<p>More trickily, instead of: +<p/>More trickily, instead of: <blockquote> <code>\</code><code>documentclass[...]{bar}</code><br> <code>\</code><code>usepackage[draft]{graphics}</code> @@ -82,7 +82,7 @@ you would write: </blockquote><p> with <code>\</code><code>PassOptionsToPackage</code> <em>before</em> the <code>\</code><code>documentclass</code> command. -<p>However, if the <i>foo</i> package or the <i>bar</i> class loads +<p/>However, if the <i>foo</i> package or the <i>bar</i> class loads <i>graphics</i> with an option of its own that clashes with what you need in some way, you’re stymied. For example: <blockquote> @@ -97,9 +97,8 @@ it, so your <code>draft</code> will get forgotten. In extreme cases, the package might generate an error here (<i>graphics</i> doesn’t go in for that kind of thing, and there’s no indication that <code>draft</code> has been forgotten). -<p>In such a case, you have to modify the package or class itself +<p/>In such a case, you have to modify the package or class itself (subject to the terms of its licence). It may prove useful to contact the author: she may have a useful alternative to suggest. -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=optionclash">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=optionclash</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=optionclash">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=optionclash</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-otherprinters.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-otherprinters.html index f0559e4bf42..86dc97512a8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-otherprinters.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-otherprinters.html @@ -2,21 +2,21 @@ <title>UK TeX FAQ -- question label otherprinters</title> </head><body> <h3>Output to “other” printers</h3> -<p>In the early years of TeX, there were masses of DVI drivers +<p/>In the early years of TeX, there were masses of DVI drivers for any (then) imaginable kind of printer, but the steam seems rather -to have gone out of the market for production of such drivers for +to have gone out of the market for production of drivers for printer-specific formats. There are several reasons for this, but the primary one is that few formats offer the flexibility available through PostScript, and <i>ghostscript</i> is <em>so</em> good, and has <em>such</em> a wide range of printer drivers (perhaps this is where the DVI output driver writers have all gone?). -<p>The general advice, then, is to <a href="FAQ-dvips.html">generate PostScript</a>, and +<p/>The general advice, then, is to <a href="FAQ-dvips.html">generate PostScript</a>, and to process that with <i>ghostscript</i> set to generate the format for the printer you actually have. If you are using a Unix system of some sort, it’s generally quite easy to insert <i>ghostscript</i> into the print spooling process. <dl> -<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/ghostscript/">nonfree/support/ghostscript/</a> +<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/">support/ghostscript/</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=otherprinters">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=otherprinters</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=otherprinters">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=otherprinters</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ouparmd.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ouparmd.html index eaaf9d73a81..40d1c2c3510 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ouparmd.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ouparmd.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label ouparmd</title> </head><body> <h3>Not in outer par mode</h3> -<p>The error: +<p/>The error: <blockquote> <pre> ! LaTeX Error: Not in outer par mode. @@ -10,7 +10,7 @@ </blockquote><p> comes when some “main” document feature is shut up somewhere it doesn’t like. -<p>The commonest occurrence is when the user wants a figure somewhere +<p/>The commonest occurrence is when the user wants a figure somewhere inside a table: <blockquote> <pre> @@ -36,7 +36,7 @@ but doesn’t work, any more than: The problem is, that the <code>tabular</code> environment, and the <code>\</code><code>framebox</code> command restrain the <code>figure</code> environment from its natural métier, which is to float around the document. -<p>The solution is simply not to use the <code>figure</code> environment +<p/>The solution is simply not to use the <code>figure</code> environment here: <blockquote> <pre> @@ -50,7 +50,7 @@ here: What was the float for? — as written in the first two examples, it serves no useful purpose; but perhaps you actually wanted a diagram and its caption framed, in a float. -<p>It’s simple to achieve this — just reverse the order of the +<p/>It’s simple to achieve this — just reverse the order of the environments (or of the <code>figure</code> environment and the command): <blockquote> @@ -69,5 +69,5 @@ The same goes for <code>table</code> environments (or any other sort of float you’ve defined for yourself) inside tabulars or box commands; you <em>must</em> get the float environment out from inside, one way or another. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ouparmd">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ouparmd</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ouparmd">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ouparmd</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-outszwrng.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-outszwrng.html index aa6ca53ec1f..9df037e476c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-outszwrng.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-outszwrng.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label outszwrng</title> </head><body> <h3>(La)TeX PDF output prints at wrong size</h3> -<p>Having got everything <em>else</em> right, you should be aware that the +<p/>Having got everything <em>else</em> right, you should be aware that the problem may have nothing to do with (La)TeX and everything to do with the program you use for printing. A regular cause for such problems lies with Acrobat Reader, which by default enables its option @@ -10,7 +10,7 @@ to scale pages to fit on the printable area of the paper. Since a printer can rarely print right to the edge, this means that pdf-files will be shrunk by some (small) factor (even if the pdf-file is formatted for A4, and your paper size is set to A4 as well). -<p>Correcting this silliness is not very hard, but the exact details +<p/>Correcting this silliness is not very hard, but the exact details depend on the version of Acrobat Reader (or "Adobe Reader" from version 6.0 onwards) you have installed: <ul> @@ -26,5 +26,5 @@ version 6.0 onwards) you have installed: checkbox is unchecked. It may also be useful to uncheck the “Expand small pages to fit paper size” checkbox as well. </ul> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=outszwrng">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=outszwrng</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=outszwrng">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=outszwrng</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-overfull.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-overfull.html index f708e6696e9..b518a27bc39 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-overfull.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-overfull.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label overfull</title> </head><body> <h3>(La)TeX makes overfull lines</h3> -<p>When TeX is building a paragraph, it can make several attempts to +<p/>When TeX is building a paragraph, it can make several attempts to get the line-breaking right; on each attempt it runs the same algorithm, but gives it different parameters. You can affect the way TeX’s line breaking works by adjusting the parameters: this answer @@ -10,7 +10,7 @@ deals with the “tolerance” and stretchability parameters. The other vital ‘parameter’ is the set of hyphenations to be applied: see “<a href="FAQ-nohyph.html">my words aren’t being hyphenated</a>” (and the questions it references) for advice. -<p>If you’re getting an undesired “overfull box”, what has happened is +<p/>If you’re getting an undesired “overfull box”, what has happened is that TeX has given up: the parameters you gave it don’t allow it to produce a result that <em>doesn’t</em> overfill. In this circumstance, Knuth decided the best thing to do was to produce a warning, and to @@ -23,7 +23,7 @@ cases it’s impossible to solve the problem without adjusting the parameters. This answer discusses the approaches one might take to resolution of the problem, on the assumption that you’ve got the hyphenation correct. -<p>The simplest case is where a ‘small’ word fails to break at the end of +<p/>The simplest case is where a ‘small’ word fails to break at the end of a line; pushing the entire word to a new line isn’t going to make much difference, but it might make things just bad enough that TeX won’t do it by default. In such a case on can <em>try</em> the LaTeX @@ -31,7 +31,7 @@ do it by default. In such a case on can <em>try</em> the LaTeX will save an awful lot of fiddling. Otherwise, one needs to adjust parameters: to do that we need to recap the details of TeX’s line breaking mechanisms. -<p>TeX’s first attempt at breaking lines is performed without even +<p/>TeX’s first attempt at breaking lines is performed without even trying hyphenation: TeX sets its “tolerance” of line breaking oddities to the internal value <code>\</code><code>pretolerance</code>, and sees what happens. If it can’t get an acceptable break, TeX adds the @@ -40,7 +40,7 @@ using the internal <code>\</code><code>tolerance</code> value. If this pass als the internal <code>\</code><code>emergencystretch</code> value is positive, TeX will try a pass that allows <code>\</code><code>emergencystretch</code> worth of extra stretchability to the spaces in each line. -<p>In principle, therefore, there are three parameters (other than +<p/>In principle, therefore, there are three parameters (other than hyphenation) that you can change: <code>\</code><code>pretolerance</code>, <code>\</code><code>tolerance</code> and <code>\</code><code>emergencystretch</code>. Both the <code>tolerance</code> values are simple numbers, and should be set by TeX primitive count @@ -53,7 +53,7 @@ assignment — for example For both, an “infinite” tolerance is represented by the value <code>10</code><code>000</code>, but infinite tolerance is rarely appropriate, since it can lead to very bad line breaks indeed. -<p><code>\</code><code>emergencystretch</code> is a TeX-internal ‘dimen’ register, and can +<p/><code>\</code><code>emergencystretch</code> is a TeX-internal ‘dimen’ register, and can be set as normal for dimens in Plain TeX; in LaTeX, use <code>\</code><code>setlength</code> — for example: <blockquote> @@ -61,17 +61,17 @@ be set as normal for dimens in Plain TeX; in LaTeX, use \setlength{\emergencystretch}{3em} </pre> </blockquote><p> -<p>The choice of method has time implications — each of the +<p/>The choice of method has time implications — each of the passes takes time, so adding a pass (by changing <code>\</code><code>emergencystretch</code>) is less desirable than suppressing one (by changing <code>\</code><code>pretolerance</code>). However, it’s unusual nowadays to find a computer that’s slow enough that the extra passes are really troublesome. -<p>In practice, <code>\</code><code>pretolerance</code> is rarely used other than to manipulate +<p/>In practice, <code>\</code><code>pretolerance</code> is rarely used other than to manipulate the use of hyphenation; Plain TeX and LaTeX both set its value to <code>100</code>. To suppress the first scan of paragraphs, set <code>\</code><code>pretolerance</code> to <code>-1</code>. -<p><code>\</code><code>tolerance</code> is often a good method for adjusting spacing; +<p/><code>\</code><code>tolerance</code> is often a good method for adjusting spacing; Plain TeX and LaTeX both set its value to <code>200</code>. LaTeX’s <code>\</code><code>sloppy</code> command sets it to <code>9999</code>, as does the <code>sloppypar</code> environment. This value is the largest @@ -95,7 +95,7 @@ LaTeX users could use an environment like: </pre> </blockquote><p> enclosing entire paragraphs (or set of paragraphs) in it. -<p>The value of <code>\</code><code>emergencystretch</code> is added to the assumed +<p/>The value of <code>\</code><code>emergencystretch</code> is added to the assumed stretchability of each line of a paragraph, in a further run of the paragraph formatter in case that the paragraph can’t be made to look right any other way. (The extra scan happens if @@ -108,7 +108,7 @@ lots of spaces, this could be reasonable, but with (say) only three spaces on the line, each could stretch to four times its natural width. It is therefore clear that <code>\</code><code>emergencystretch</code> needs to be treated with a degree of caution. -<p>More subtle (but more tricky to manage) are the microtypographic +<p/>More subtle (but more tricky to manage) are the microtypographic extensions provided by PDFTeX. Since PDFTeX is the default ‘engine’ for LaTeX and ConTeXt work in all distributions, nowadays, the extensions are available to all. There are two @@ -120,7 +120,7 @@ Font expansion works like a subtler version of the trick that may be stretched (or shrunk) to a certain extent, and will do that “on the fly” to optimise the setting of a paragraph. This is a powerful tool in the armoury of the typesetter. -<p>As mentioned above, the microtypographic extensions are tricky beasts +<p/>As mentioned above, the microtypographic extensions are tricky beasts to control; however, the <i>microtype</i> package relieves the user of the tedious work of specifying how to perform margin adjustments and how much to scale each font ... for the fonts the package @@ -129,5 +129,5 @@ specification of adjustments for yet more fonts are always welcome. <dl> <dt><tt><i>microtype.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/microtype.zip">macros/latex/contrib/microtype</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/microtype.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/microtype/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overfull">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overfull</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overfull">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overfull</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-overstrike.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-overstrike.html index 4ccc01c9700..a167ee447d5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-overstrike.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-overstrike.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label overstrike</title> </head><body> <h3>Overstriking characters</h3> -<p>This may be used, for example, to indicate text deleted in the course +<p/>This may be used, for example, to indicate text deleted in the course of editing. Both the <i>ulem</i> and the <i>soul</i> packages provide the necessary facilities. -<p>Overstriking for +<p/>Overstriking for <a href="FAQ-cancellation.html">cancellation in maths expressions</a> is achieved by a different mechanism. -<p>Documentation of <i>ulem</i> is in the package file. +<p/>Documentation of <i>ulem</i> is in the package file. <dl> <dt><tt><i>soul.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/soul.zip">macros/latex/contrib/soul</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/soul.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/soul/">browse</a>) <dt><tt><i>ulem.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/ulem.sty">macros/latex/contrib/misc/ulem.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overstrike">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overstrike</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overstrike">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=overstrike</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pagebychap.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pagebychap.html index bfa768c7424..6ab9fcfe881 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pagebychap.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pagebychap.html @@ -2,25 +2,25 @@ <title>UK TeX FAQ -- question label pagebychap</title> </head><body> <h3>Page numbering by chapter</h3> -<p>When I was a young man, a common arrangement for loose bound technical +<p/>When I was a young man, a common arrangement for loose bound technical manuals is to number pages by chapter. (It’s quite a good scheme, in those situations: even if your corrections add a whole page to the chapter, the most you have to redistribute is that chapter.) -<p>The problem, at first sight, seems pretty much the same as that in +<p/>The problem, at first sight, seems pretty much the same as that in another answer on <a href="FAQ-running-nos.html">running numbers within a chapter</a>, and the basic technique is indeed pretty similar. -<p>However, tidying-up loose ends, making sure the page number gets reset +<p/>However, tidying-up loose ends, making sure the page number gets reset to the correct value at the start of each chapter, and so on, is slightly more challenging. This is why the <i>chappg</i> package was written: it does the obvious things, and more. -<p>Users have been known to ask for running page numbers within a +<p/>Users have been known to ask for running page numbers within a section, but this really doesn’t make sense: you need to run page numbers within document objects that always start on a fresh page. -<p>Documentation of <i>chappg</i> is to be found in the package file. +<p/>Documentation of <i>chappg</i> is to be found in the package file. <dl> <dt><tt><i>chappg.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/chappg.zip">macros/latex/contrib/chappg</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/chappg.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/chappg/">browse</a>) </dl> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pagebychap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pagebychap</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pagebychap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pagebychap</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-papersize.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-papersize.html index 353e5314cfe..356866d8651 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-papersize.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-papersize.html @@ -2,44 +2,62 @@ <title>UK TeX FAQ -- question label papersize</title> </head><body> <h3>Printer paper sizes</h3> -<p>Paper sizes can be a pain: they’re a forgotten backwater, because +<p/>If you’re looking at this answer, it’s likely you have a problem with +fitting output to the page. It may be a common problem with Adobe +<i>[Acrobat] Reader</i>: printing from that program +<em>by default</em> shrinks the page ”to fit”. Unfortunately, its +calculation doesn’t take the existing margins of the document into +account, so that it shrinks what it believes is your whole page onto +what it believes is its output page. The effect typically looks as if +your margins have expanded. +<p/>Solve this problem by adjusting the <i>Reader</i>’s default in the +print dialogue; unfortunately, this dialogue varies from one version +to the next. On <i>Reader</i> version 7, there are two entries to +check: +<blockquote> + Page Scaling (default: ”Fit to printer margins”) — change to + ”None”, and<br> + Scale (default 95\ +</blockquote><p> +<p/>More generally, we should recognise that paper sizes can be a pain: +they’re a forgotten backwater, because there’s no DVI command to specify the paper size of the document. One usually finds American “letter” paper size being -used, by default, in macro packages (such as <i>plain</i> and -LaTeX); but distributions provide configuration files for -DVI drivers (and since most distributions originate in Europe, -the drivers usually default to ISO “A4” paper size). -<p>This is (of course) pretty unsatisfactory. Users may change the paper +assumed, by default, in macro packages (such as <i>plain</i> TeX and +LaTeX); but distributions provide separate configuration files for +DVI drivers. Since most distributions nowadays originate in +Europe, the drivers usually default to ISO “A4” paper size. +<p/>This is (of course) pretty unsatisfactory. Users may change the paper size their document is designed for, pretty easily (and once off), but they have to ensure that every run of <i>xdvi</i>, <i>dvips</i>, or whatever, is given the correct override for using anything non-‘standard’. -<p>Of course, the default paper size for DVI drivers may be +<p/>Furthermore, the default paper size for DVI drivers may be changed by a distribution management command, but this still doesn’t provide for people using the “wrong” sort of paper for some reason. -<p>An interestingly different issue arises for users of PDFTeX — the +<p/>An interestingly different issue arises for users of PDFTeX — the PDF format <em>does</em> have the means of expressing paper size, but much of the core software predates PDFTeX, so not even PDFLaTeX sets the correct values into <code>\</code><code>pdfpagewidth</code> and <code>\</code><code>pdfpageheight</code>. -<p>The DVI drivers <i>dvips</i> and <i>dvipdfm</i> define +<p/>The DVI drivers <i>dvips</i> and <i>dvipdfm</i> define <code>\</code><code>special</code> commands for the document to specify its own paper size; so in those cases, as in the case of PDFTeX and VTeX, the paper size can be programmed by the document. Users who wish to, may of course consult the manuals of the various programs to write the necessary code. -<p>The <i>geometry</i> package (whose main business is defining +<p/>The <i>geometry</i> package (whose main business is defining typeset page areas), also takes notice of the paper size the document is going to print to, and can issue the commands necessary to ensure the correct size is used. If <i>geometry</i> is used when a -document is being processed by either PDFLaTeX or VTeX, it will -set the necessary dimensions as a matter of course. If the document +document is being processed by either PDFLaTeX or VTeX, it can +set the necessary dimensions ”in the output”. If the document is being processed by LaTeX on a TeX or e-TeX engine, there are two package options (<code>dvipdfm</code> and <code>dvips</code>) which instruct <i>geometry</i> which <code>\</code><code>special</code> commands to use. (Note that the options are ignored if you are using either PDFLaTeX or VTeX.) -<p>So, the resolution of the problem is to add +<p/>So, the resolution of the problem is to add <blockquote> <pre> \usepackage[dvixxx,...]{geometry} @@ -48,12 +66,12 @@ or VTeX.) (where <code>dvixxx</code> is your current favourite DVI driver), and the document will run correctly with any of LaTeX (whether or not run on VTeX) or PDFLaTeX. -<p>Give the <i>typearea</i> package the <code>pagesize</code> and it +<p/>Give the <i>typearea</i> package the <code>pagesize</code> and it will do the same job, for PDFLaTeX output and PostScript output from LaTeX via <i>dvips</i>. <dl> <dt><tt><i>geometry.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/geometry.zip">macros/latex/contrib/geometry</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/geometry.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/geometry/">browse</a>) <dt><tt><i>typearea.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=papersize">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=papersize</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=papersize">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=papersize</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parallel.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parallel.html index ed533cb12a7..911075c41be 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parallel.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parallel.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label parallel</title> </head><body> <h3>Parallel setting of text</h3> -<p>It’s commonly necessary to present text in two languages ‘together’ on a +<p/>It’s commonly necessary to present text in two languages ‘together’ on a page, or on a two-page spread. For this to be satisfactory, one usually needs some sort of alignment between the two texts. -<p>The <i>parallel</i> package satisfies the need, permitting +<p/>The <i>parallel</i> package satisfies the need, permitting typesetting in two columns (not necessarily of the same width) on one page, or on the two opposing pages of a two-page spread. Use can be as simple as @@ -21,7 +21,7 @@ as simple as \end{Parallel} </pre> </blockquote><p> -<p>The <i>parcolumns</i> package can (in principle) deal with any +<p/>The <i>parcolumns</i> package can (in principle) deal with any number of columns: the documentation shows its use with three columns. Usage is rather similar to that of <i>parallel</i>, though there is of course a “number of columns to specify”: @@ -40,7 +40,7 @@ though there is of course a “number of columns to specify”: </blockquote><p> The <<i>options</i>> can specify the widths of the columns, whether to place rules between the columns, whether to set the columns sloppy, etc. -<p>The <i>ledpar</i> package is distributed with (and integrated with) +<p/>The <i>ledpar</i> package is distributed with (and integrated with) the <a href="FAQ-linenos.html"><i>ledmac</i> package</a>. It provides parallel setting carefully integrated with the needs of a scholarly text, permitting translation, or notes, or both, to be set in parallel with @@ -50,5 +50,5 @@ the ‘base’ text of the document. <dt><tt><i>parallel.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/parallel.zip">macros/latex/contrib/parallel</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/parallel.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/parallel/">browse</a>) <dt><tt><i>parcolumns.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sauerj.zip">macros/latex/contrib/sauerj</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sauerj.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sauerj/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=parallel">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=parallel</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=parallel">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=parallel</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-paraparam.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-paraparam.html index 70ac18b8573..60ded834d24 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-paraparam.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-paraparam.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label paraparam</title> </head><body> <h3>Why does it ignore paragraph parameters?</h3> -<p>When TeX is laying out text, it doesn’t work from word to word, or +<p/>When TeX is laying out text, it doesn’t work from word to word, or from line to line; the smallest complete unit it formats is the paragraph. The paragraph is laid down in a buffer, as it appears, and isn’t touched further until the end-paragraph marker is processed. @@ -10,7 +10,7 @@ It’s at this point that the paragraph parameters have effect; and it&rsquo because of this sequence that one often makes mistakes that lead to the paragraph parameters not doing what one would have hoped (or expected). -<p>Consider the following sequence of LaTeX: +<p/>Consider the following sequence of LaTeX: <blockquote> <pre> {\raggedright % declaration for ragged text @@ -29,7 +29,7 @@ line, which it knows to treat as a <code>\</code><code>par</code> token, so it t two sentences; but because the enclosing group has now been closed, the parameter settings have been lost, and the paragraph will be typeset normally. -<p>The solution is simple: close the paragraph inside the group, so that +<p/>The solution is simple: close the paragraph inside the group, so that the setting parameters remain in place. An appropriate way of doing that is to replace the last three lines above with: <blockquote> @@ -40,7 +40,7 @@ Here's more that needn't be ragged... </blockquote><p> In this way, the paragraph is completed while <code>\</code><code>raggedright</code>’s parameters are still in force within the enclosing group. -<p>Another alternative is to define an environment that does the +<p/>Another alternative is to define an environment that does the appropriate job for you. For the above example, LaTeX already defines an appropriate one: <blockquote> @@ -50,10 +50,10 @@ Here's text to be ranged left... \end{flushleft} </pre> </blockquote><p> -<p>In fact, there are a number of parameters for which TeX only +<p/>In fact, there are a number of parameters for which TeX only maintains one value per paragraph. A tiresome one is the set of upper case/lower case translations, which (oddly enough) constrains hyphenation of mutilingual texts. Another that regularly creates confusion is <a href="FAQ-baselinepar.html"><code>\</code><code>baselineskip</code></a>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=paraparam">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=paraparam</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=paraparam">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=paraparam</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parskip.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parskip.html index 3892cb64bf3..2407453735b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parskip.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-parskip.html @@ -2,29 +2,29 @@ <title>UK TeX FAQ -- question label parskip</title> </head><body> <h3>Zero paragraph indent</h3> -<p>The conventional way of typesetting running text has no separation +<p/>The conventional way of typesetting running text has no separation between paragraphs, and the first line of each paragraph in a block of text indented. -<p>In contrast, one common convention for typewritten text was to have no +<p/>In contrast, one common convention for typewritten text was to have no indentation of paragraphs; such a style is often required for “brutalist” publications such as technical manuals, and in styles that hanker after typewritten manuscripts, such as officially-specified dissertation formats. -<p>Anyone can see, after no more than a moment’s thought, that if the +<p/>Anyone can see, after no more than a moment’s thought, that if the paragraph indent is zero, the paragraphs must be separated by blank space: otherwise it is sometimes going to be impossible to see the breaks between paragraphs. -<p>The simple-minded approach to zero paragraph indentation is thus: +<p/>The simple-minded approach to zero paragraph indentation is thus: <pre> \setlength{\parindent}{0pt} \setlength{\parskip}{\baselineskip} </pre> and in the very simplest text, it’s a fine solution. -<p>However, the non-zero <code>\</code><code>parskip</code> interferes with lists and the like, +<p/>However, the non-zero <code>\</code><code>parskip</code> interferes with lists and the like, and the result looks pretty awful. The <i>parskip</i> package patches things up to look reasonable; it’s not perfect, but it deals with most problems. -<p>The Netherlands Users’ Group’s set of classes includes an +<p/>The Netherlands Users’ Group’s set of classes includes an <i>article</i> equivalent (<i>artikel3</i>) and a <i>report</i> equivalent (<i>rapport3</i>) whose design incorporates zero paragraph indent and non-zero paragraph skip. @@ -32,5 +32,5 @@ indent and non-zero paragraph skip. <dt><tt><i>NTG classes</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntgclass.zip">macros/latex/contrib/ntgclass</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntgclass.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ntgclass/">browse</a>) <dt><tt><i>parskip.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/parskip.sty">macros/latex/contrib/misc/parskip.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=parskip">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=parskip</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=parskip">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=parskip</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-patch.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-patch.html index 8340ec898e3..495b7e0b6da 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-patch.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-patch.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label patch</title> </head><body> <h3>Patching existing commands</h3> -<p>In the general case (possibly sticking something in the middle of an +<p/>In the general case (possibly sticking something in the middle of an existing command) this is difficult. However, the common requirement, to add some code at the beginning or the end of an existing command, is conceptually quite easy. Suppose we want to define a version of a @@ -16,7 +16,7 @@ would naturally write: However, this would not work: a call to <code>\</code><code>splat</code> would execute <code>\</code><code>mumble</code>, and the call the redefined <code>\</code><code>splat</code> again; this is an infinite recursive loop, that will quickly exhaust TeX’s memory. -<p>Fortunately, the TeX primitive <code>\</code><code>let</code> command comes to our +<p/>Fortunately, the TeX primitive <code>\</code><code>let</code> command comes to our rescue; it allows us to take a “snapshot” of the current state of a command, which we can then use in the redefinition of the command. So: @@ -35,7 +35,7 @@ pass them on: </pre> </blockquote><p> -<p>The general case may be achieved in two ways. First, one can use the +<p/>The general case may be achieved in two ways. First, one can use the LaTeX command <code>\</code><code>CheckCommand</code>; this compares an existing command with the definition you give it, and issues a warning if two don’t match. Use is therefore: @@ -47,9 +47,9 @@ This technique is obviously somewhat laborious, but if the original command comes from a source that’s liable to change under the control of someone else, it does at least warn you that your patch is in danger of going wrong. -<p>Otherwise, LaTeX users may use one of the <i>patch</i> or +<p/>Otherwise, LaTeX users may use one of the <i>patch</i> or <i>patchcmd</i> systems. -<p><i>Patch</i> gives you an ingenious (and difficult to understand) +<p/><i>Patch</i> gives you an ingenious (and difficult to understand) mechanism, and comes as an old-style LaTeX documented macro file. Sadly the old-style <i>doc</i> macros are no longer available, but the file (<i>patch.doc</i>) may be input directly, and the @@ -58,7 +58,7 @@ the command a set of instructions analagous to <i>sed</i> substitutions, and it regenerates the command thus amended. The author of this FAQ has (slightly reluctantly) given up using <i>patch</i>... -<p>The <i>patchcmd</i> package addresses a slightly simpler task, by +<p/>The <i>patchcmd</i> package addresses a slightly simpler task, by restricting the set of commands that you may patch; you mayn’t patch any command that has an optional argument, though it does deal with the case of commands defined with <code>\</code><code>DeclareRobustCommand</code>. The @@ -72,5 +72,5 @@ will produce a new version of <code>\</code><code>b</code> that contains “ <dt><tt><i>patch.doc</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/generic/misc/patch.doc">macros/generic/misc/patch.doc</a> <dt><tt><i>patchcommand.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/patchcmd.zip">macros/latex/contrib/patchcmd</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/patchcmd.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/patchcmd/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=patch">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=patch</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=patch">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=patch</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdfpagelabels.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdfpagelabels.html index 10acbf573f3..e217ac4db7f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdfpagelabels.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdfpagelabels.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label pdfpagelabels</title> </head><body> <h3><i>Hyperref</i> and repeated page numbers</h3> -<p>The <i>book</i> class (and its friends and relations) automatically +<p/>The <i>book</i> class (and its friends and relations) automatically changes the display of page numbers in the frontmatter of the document to lower-case roman. This is fine for human readers, but it confuses <i>hyperref</i> since there are pages which seem (to <i>hyperref</i>) to have the same page number. Fortunately, there are configuration options to make <i>hyperref</i> “do the right thing”. -<p>The two options in question are: +<p/>The two options in question are: <dl> <dt><code>plainpages=false</code><dd> Make page anchors using the formatted form of the page number. With this option, @@ -24,7 +24,7 @@ thing”. </dl> The two should be used whenever page numbering is not just ‘1<code>..</code>n’; they may be used independently, but usually are not. -<p>The recipe isn’t perfect: it relies on <code>\</code><code>thepage</code> being different +<p/>The recipe isn’t perfect: it relies on <code>\</code><code>thepage</code> being different for every page in the document. A common problem arises when there is an unnumbered title page, after which page numbers are reset: the PDFTeX warning of “<a href="FAQ-hyperdupdest.html">duplicate destinations</a>” @@ -32,5 +32,5 @@ will happen in this case, regardless of the options. <dl> <dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdfpagelabels">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdfpagelabels</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdfpagelabels">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdfpagelabels</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdftexgraphics.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdftexgraphics.html index f40b1ec8f3c..a82acae3585 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdftexgraphics.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pdftexgraphics.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label pdftexgraphics</title> </head><body> <h3>Imported graphics in PDFLaTeX</h3> -<p>PDFTeX itself has a rather wide range of formats that it can +<p/>PDFTeX itself has a rather wide range of formats that it can “natively” incorporate into its output PDF stream: JPEG (<code>.jpg</code> files) for photographs and similar images, PNG files for artificial bitmap images, and PDF for @@ -10,17 +10,17 @@ vector drawings. Old versions of PDFTeX (prior to version 1.10a) supported TIFF (<code>.tif</code> files) format as an alternative to PNG files; don’t rely on this facility, even if you <em>are</em> running an old enough version of PDFTeX... -<p>In addition to the ‘native’ formats, the standard PDFLaTeX +<p/>In addition to the ‘native’ formats, the standard PDFLaTeX <i>graphics</i> package setup causes Hans Hagen’s <i>supp-pdf</i> macros to be loaded: these macros are capable of translating the output of MetaPost to PDF “on the fly”; thus MetaPost output (<code>.mps</code> files) may also be included in PDFLaTeX documents. -<p>The commonest problem users encounter, when switching from TeX, is +<p/>The commonest problem users encounter, when switching from TeX, is that there is no straightforward way to include EPS files: since PDFTeX is its own “driver”, and since it contains no means of converting PostScript to PDF, there’s no direct way the job can be done. -<p>The simple solution is to convert the EPS to an appropriate +<p/>The simple solution is to convert the EPS to an appropriate PDF file. The <i>epstopdf</i> program will do this: it’s available either as a Windows executable or as a <i>Perl</i> script to run on Unix and other similar systems. A LaTeX package, @@ -28,20 +28,20 @@ script to run on Unix and other similar systems. A LaTeX package, files “on the fly”; this is convenient, but requires that you suppress one of TeX’s security checks: don’t allow its use in files from sources you don’t entirely trust. -<p>A similar package, <i>pst-pdf</i>, permits other things than ‘mere’ +<p/>A similar package, <i>pst-pdf</i>, permits other things than ‘mere’ graphics files in its argument. <i>Pst-pdf</i> operates (the authors suggest) “like BibTeX” — you process your file using PDFLaTeX, then use LaTeX, <i>dvips</i> and <i>ps2pdf</i> in succession, to produce a secondary file to input to your next PDFLaTeX run. (Scripts are provided to ease the production of the secondary file.) -<p>An alternative solution is to use <i>purifyeps</i>, a +<p/>An alternative solution is to use <i>purifyeps</i>, a <i>Perl</i> script which uses the good offices of <i>pstoedit</i> and of MetaPost to convert your Encapsulated PostScript to “Encapsulated PostScript that comes out of MetaPost”, and can therefore be included directly. Sadly, <i>purifyeps</i> doesn’t work for all <code>.eps</code> files. -<p>Good coverage of the problem is to be found in Herbert Voss’ +<p/>Good coverage of the problem is to be found in Herbert Voss’ <a href="http://pstricks.tug.org/main.cgi?file=pdf/pdfoutput">PDF support page</a>, which is targeted at the use of <i>pstricks</i> in PDFLaTeX, and also covers the <i>pstricks</i>-specific package @@ -55,5 +55,5 @@ PDFLaTeX, and also covers the <i>pstricks</i>-specific package <dt><tt><i>pstoedit</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/pstoedit.zip">support/pstoedit</a> (<a href="ftp://cam.ctan.org/tex-archive/support/pstoedit.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/pstoedit/">browse</a>) <dt><tt><i>purifyeps</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/purifyeps.zip">support/purifyeps</a> (<a href="ftp://cam.ctan.org/tex-archive/support/purifyeps.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/purifyeps/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdftexgraphics">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdftexgraphics</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdftexgraphics">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pdftexgraphics</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pk.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pk.html index 269187fdd88..7beb3103a30 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pk.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pk.html @@ -2,18 +2,19 @@ <title>UK TeX FAQ -- question label pk</title> </head><body> <h3>What are PK files?</h3> -<p>PK files (packed raster) contain font bitmaps. The output -from - - <a href="FAQ-useMF.html">Metafont</a> -includes a generic font (GF) file and the +<p/>PK files (packed raster) contain font bitmaps. The output +from <a href="FAQ-useMF.html">Metafont</a> includes a generic font (GF) file +and the utility <i>gftopk</i> produces the PK file from that. There are a lot of PK files, as one is needed for each font, that is each magnification (size) of each design (point) size for each weight for each family. Further, since the PK files for one printer do not necessarily work well for another, the whole set needs to be -duplicated for each printer type at a site. As a result, they are -often held in an elaborate directory structure, or in ‘font library -files’, to regularise access. -<p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pk">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pk</a> +duplicated for each printer type at a site. In a modern TeX +distribution, files are arranged according to the TeX directory +structure + +(see <a href="FAQ-tds.html">TDS</a>), +which has provision for all this variety. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pk">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pk</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkfix.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkfix.html index 9c0b4184417..ddb525c90ce 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkfix.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkfix.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label pkfix</title> </head><body> <h3>Replacing Type 3 fonts in PostScript</h3> -<p>One often comes across a PostScript file generated by +<p/>One often comes across a PostScript file generated by <i>dvips</i> which contains embedded PK fonts; if you try to generate PDF from such a file, the quality will be poor. -<p>Of course, the proper solution is to regenerate the PostScript file, +<p/>Of course, the proper solution is to regenerate the PostScript file, but if neither the sources nor the DVI file are available, one must needs resort to some sort of patching to replace the bitmap fonts in the file by outline fonts. -<p>The program <i>pkfix</i> (by Heiko Oberdiek) will do this +<p/>The program <i>pkfix</i> (by Heiko Oberdiek) will do this patching, for files created by “not too old versions” of <i>dvips</i>: it finds the fonts to be replaced by examining the PostScript comments <i>dvips</i> has put in the file. For each @@ -17,7 +17,7 @@ font, <i>pkfix</i> puts appropriate TeX commands in a file, which it then processes and runs through <i>dvips</i> (with switch <code>-Ppdf</code>) to acquire an appropriate copy of the font; these copies are then patched back into the original file. -<p> +<p/> @@ -34,5 +34,5 @@ in the file with Type 1 versions. <dl> <dt><tt><i>pkfix</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/pkfix.zip">support/pkfix</a> (<a href="ftp://cam.ctan.org/tex-archive/support/pkfix.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/pkfix/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pkfix">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pkfix</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pkfix">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pkfix</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkgdoc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkgdoc.html index 2ed7affb208..b37cd7dcb54 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkgdoc.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-pkgdoc.html @@ -2,34 +2,35 @@ <title>UK TeX FAQ -- question label pkgdoc</title> </head><body> <h3>Documentation of packages</h3> -<p>These FAQs regularly suggest packages that will “solve” +<p/>These FAQs regularly suggest packages that will “solve” particular problems. In some cases, the answer provides a recipe for the job. In other cases, or when the solution needs elaborating, how is the poor user to find out what to do? -<p>If you’re lucky, the package you need is already in your installation. +<p/>If you’re lucky, the package you need is already in your installation. If you’re particularly lucky, you’re using a distribution that gives access to package documentation and the documentation is available in -a form that can easily be shown. For example, on a teTeX-based -system, the <i>texdoc</i> command is usually useful, as in: +a form that can easily be shown. For example, on many current +distributions, the <i>texdoc</i> command often helps, as in: <blockquote> <pre> texdoc footmisc </pre> </blockquote><p> -which opens an <i>xdvi</i> window showing documentation of the +which opens a DVI viewer window showing documentation of the <i>footmisc</i> package. According to the type of file -<i>texdoc</i> finds, it will launch <i>xdvi</i>, -a <i>ghostscript</i>-based PostScript viewer or a PDF reader. -If it can’t find any documentation, it may launch a Web browser to -look at its copy of the CTAN catalogue. The catalogue has an -entry for package documentation, and since CTAN now -encourages authors to submit documentation of their packages, that -entry may provide a useful lead. -<p>If your luck (as defined above) doesn’t hold out, you’ve got to find +<i>texdoc</i> finds, it will launch a DVI or PostScript viewer +or a PDF reader. +<p/>If <i>texdoc</i> can’t find any documentation, it may launch a Web +browser to look at its copy of the CTAN catalogue. The +catalogue has an entry for package documentation, and since the +CTAN team asks authors documentation of their packages (and +even occasionally generates documentation itself, you will more often +than not find documentation that way. +<p/>If your luck (as defined above) doesn’t hold out, you’ve got to find documentation by other means. This is where you need to exercise your intelligence: you have to find the documentation for yourself. What follows offers a range of possible techniques. -<p>The commonest form of documentation of LaTeX add-ons is within the +<p/>The commonest form of documentation of LaTeX add-ons is within the <code>.dtx</code> file in which the code is distributed (see <a href="FAQ-dtx.html">documented LaTeX sources</a>). Such files are supposedly processable by LaTeX itself, but there are @@ -37,11 +38,11 @@ occasional hiccups on the way to readable documentation. Common problems are that the package itself is needed to process its own documentation (so must be unpacked before processing), and that the <code>.dtx</code> file will <em>not</em> in fact process with LaTeX. In the -latter case, the <code>.ins</code> file will usually produce a <code>.drv</code> (or -similarly-named) file, which you process with LaTeX instead. -(Sometimes the package author even thinks to mention this wrinkle in -a package <code>README</code> file.) -<p>Another common form is the separate documentation file; particularly +latter case, the <code>.ins</code> file will usually produce a +<code>.drv</code> (or similarly-named) file, which you process with +LaTeX instead. (Sometimes the package author even thinks to +mention this wrinkle in a package <code>README</code> file.) +<p/>Another common form is the separate documentation file; particularly if a package is “conceptually large” (and therefore needs a lot of documentation), the documentation would prove a cumbersome extension to the <code>.dtx</code> file. Examples of such cases are the <i>memoir</i> @@ -53,13 +54,13 @@ documentation derives from a definitive tutorial in a mathematical journal). Even if the documentation is not separately identified in a <code>README</code> file, it should not be too difficult to recognise its existence. -<p>Documentation within the package itself is the third common form. +<p/>Documentation within the package itself is the third common form. Such documentation ordinarily appears in comments at the head of the file, though at least one eminent author regularly places it after the <code>\</code><code>endinput</code> command in the package. (This is desirable, since <code>\</code><code>endinput</code> is a ‘logical’ end-of-file, and (La)TeX doesn’t read beyond it: thus such documentation does not ‘cost’ any package loading time.) -<p>The above suggestions cover most possible ways of finding +<p/>The above suggestions cover most possible ways of finding documentation. If, despite your best efforts, you can’t find it in any of the above places, there’s the awful possibility that the author didn’t bother to document his package (on the “if it was hard @@ -67,5 +68,5 @@ to write, it should be hard to use” philosophy). Most ordinary mortals will seek support from some more experienced user at this stage, though it <em>is</em> possible to proceed in the way that the original author apparently expected...by reading his code. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pkgdoc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pkgdoc</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pkgdoc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=pkgdoc</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plainvltx.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plainvltx.html index e42a28eff35..ee2ed09f399 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plainvltx.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plainvltx.html @@ -2,20 +2,20 @@ <title>UK TeX FAQ -- question label plainvltx</title> </head><body> <h3>Should I use Plain TeX or LaTeX?</h3> -<p>There’s no straightforward answer to this question. Many people swear +<p/>There’s no straightforward answer to this question. Many people swear by Plain TeX, and produce highly respectable documents using it (Knuth is an example of this, of course). But equally, many people are happy to let someone else take the design decisions for them, accepting a small loss of flexibility in exchange for a saving of brain power. -<p>The arguments around this topic can provoke huge amounts of noise and +<p/>The arguments around this topic can provoke huge amounts of noise and heat, without offering much by way of light; your best bet is to find out what those around you are using, and to go with the crowd. Later on, you can always switch your allegiance; don’t bother about it. -<p>If you are preparing a manuscript for a publisher or journal, ask them +<p/>If you are preparing a manuscript for a publisher or journal, ask them what markup they want before you develop your own; many big publishers have developed their own (La)TeX styles for journals and books, and insist that authors stick closely to their markup. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plainvltx">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plainvltx</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plainvltx">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plainvltx</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plninltx.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plninltx.html deleted file mode 100644 index 6cc4b4747dd..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plninltx.html +++ /dev/null @@ -1,90 +0,0 @@ -<head> -<title>UK TeX FAQ -- question label plninltx</title> -</head><body> -<h3>Using Plain or primitive commands in LaTeX</h3> -<p>It’s well-known that LaTeX commands tend to be more complex, and to -run more slowly than, any Plain (or primitive) command that they -replace. There is therefore great temptation not to use LaTeX -commands when macro programming. Nevertheless, the general rule is -that you should use LaTeX commands, if there are seeming -equivalents. The exception is when you are sure you know the -differences between the two commands and you know that you need the -Plain version. So, for example, use <code>\</code><code>mbox</code> in place of <code>\</code><code>hbox</code> -unless you know that the extras that LaTeX provides in <code>\</code><code>mbox</code> -would cause trouble in your application. Similarly, use -<code>\</code><code>newcommand</code> (or one of its relatives) unless you need one of the -constructs that cannot be achieved without the use of <code>\</code><code>def</code> (or friends). -<p>As a general rule, any LaTeX text command will start a new -paragraph if necessary; this isn’t the case with Plain TeX -commands, a fact which has a potential to confuse. -<p>The commands <code>\</code><code>smallskip</code>, <code>\</code><code>medskip</code> and <code>\</code><code>bigskip</code> exist both -in Plain TeX and LaTeX, but behave slightly differently: in Plain -TeX they terminate the current paragraph, but in LaTeX they -don’t. The command <code>\</code><code>line</code> is part of picture mode in LaTeX, -whereas it’s defined as “<code>\</code><code>hbox</code><code> to </code><code>\</code><code>hsize</code>” in -Plain TeX. (There’s no equivalent for users of the Plain TeX command in -LaTeX: an equivalent appears as the internal command <code>\</code><code>@@line</code>). -<p>Maths setting shows a case where the LaTeX version <em>is</em> -essentially equivalent to the TeX primitive commands: the LaTeX -<code>\</code><code>(</code><code> ... </code><code>\</code><code>)</code> does essentially no different to the -TeX <code>$ ... $</code> -(except for checking that you’re not attempting to open a maths -environment when you’re already in one, or vice versa). -However, <code>\</code><code>[</code><code> ... </code><code>\</code><code>]</code> <em>isn’t</em> the same as -<code>$$ ... $$</code>: the TeX version, used -in LaTeX, contrives to miss the effect of the class option -<code>fleqn</code>. -<p>Font handling is, of course, wildly different in Plain TeX and -LaTeX: even the LaTeX equivalent of the Plain TeX -font-loading command (<code>\</code><code>newfont</code>) should be avoided wherever -possible: the possibilities of confusion with constructs that vary -their behaviour according to the font size that LaTeX has recorded -are (sadly) legion. A really rather funny example is to be had by -saying: -<blockquote> -<pre> -\documentclass{article} -\begin{document} -\font \myfont=cmr17 scaled 2000 -\myfont -\LaTeX -\end{document} -</pre> -</blockquote><p> -(the reader is encouraged to try this). The “A” of LaTeX -has pretty much disappeared: LaTeX sets the “A” according to -<em>its</em> idea of the font size (10pt), but “<code>\</code><code>myfont</code>” is more -than three times that size. -<p>Another “<code>\</code><code>myfont</code>” example arises from an entirely different -source. The mini-document: -<blockquote> -<pre> -\documentclass{article} -\begin{document} -\font \myfont=ecrm1000 -{\myfont par\`a} -\end{document} -</pre> -</blockquote><p> -gives you “German low double quotes” in place of the grave accent. -This problem arises because <i>ecrm1000</i> is in a different -<a href="FAQ-whatenc.html">font encoding</a> than LaTeX is expecting — if you -use LaTeX font commands, all the tiresome encoding issues are -solved for you, behind the scenes. -<p>So, whether you’re dealing with a one-off font or a major new family, you -are far more likely to be satisfied with the LaTeX file selection -system, so it’s worth investing a small amount of effort to write -declarations of the font’s family and how it should be loaded. For -details of the commands you need, see the LaTeX font usage guide, -<i>fntguide</i>: this may be viewed on the archive, but you should -find a copy of the document in your own system. - - - - -<dl> -<dt><tt><i>fntguide.pdf</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/doc/fntguide.pdf">macros/latex/doc/fntguide.pdf</a> -<dt><tt><i>fntguide.tex</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.zip">macros/latex/base</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base/">browse</a>) -</dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plninltx">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plninltx</a> -</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plninltxstar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plninltxstar.html new file mode 100644 index 00000000000..e82af36e735 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-plninltxstar.html @@ -0,0 +1,52 @@ +<head> +<title>UK TeX FAQ -- question label plninltx*</title> +</head><body> +<h3>Using Plain or primitive commands in LaTeX</h3> +<p/>It’s well-known that LaTeX commands tend to be more complex, and to +run more slowly than, any Plain (or primitive) command that they +replace. There is therefore great temptation not to use LaTeX +commands when macro programming. Nevertheless, the general rule is +that you should use LaTeX commands, if there are seeming +equivalents. The exception is when you are sure you know the +differences between the two commands and you know that you need the +Plain version. So, for example, use <code>\</code><code>mbox</code> in place of <code>\</code><code>hbox</code> +unless you know that the extras that LaTeX provides in <code>\</code><code>mbox</code> +would cause trouble in your application. Similarly, use +<code>\</code><code>newcommand</code> (or one of its relatives) unless you need one of the +constructs that cannot be achieved without the use of <code>\</code><code>def</code> (or friends). +<p/>As a general rule, any LaTeX text command will start a new +paragraph if necessary; this isn’t the case with Plain TeX +commands, a fact which has a potential to confuse. +<p/>The commands <code>\</code><code>smallskip</code>, <code>\</code><code>medskip</code> and <code>\</code><code>bigskip</code> exist both +in Plain TeX and LaTeX, but behave slightly differently: in Plain +TeX they terminate the current paragraph, but in LaTeX they +don’t. The command <code>\</code><code>line</code> is part of picture mode in LaTeX, +whereas it’s defined as “<code>\</code><code>hbox</code><code> to </code><code>\</code><code>hsize</code>” in +Plain TeX. (There’s no equivalent for users of the Plain TeX command in +LaTeX: an equivalent appears as the internal command <code>\</code><code>@@line</code>). +<p/>Maths setting shows a case where the LaTeX version <em>is</em> +essentially equivalent to the TeX primitive commands: the LaTeX +<code>\</code><code>(</code><code> ... </code><code>\</code><code>)</code> does essentially no different to the +TeX <code>$ ... $</code> +(except for checking that you’re not attempting to open a maths +environment when you’re already in one, or vice versa). +However, <code>\</code><code>[</code><code> ... </code><code>\</code><code>]</code> <em>isn’t</em> the same as +<code>$$ ... $$</code>: the TeX version, used +in LaTeX, can miss the effect of the class option <code>fleqn</code>. +<p/>Font handling is, of course, wildly different in Plain TeX and +LaTeX. Plain TeX’s font loading command +(<code>\</code><code>font</code><code>\</code><code>foo=</code><<i>fontname</i>>) and its LaTeX equivalent +(<code>\</code><code>newfont</code>) should be avoided wherever possible. They are only +safe in the most trivial contexts, and aer potential sources of great +confusion in many circumstances. Further discussion of this issue +may be found in “<a href="FAQ-newfontstar.html">What’s wrong with <code>\</code><code>newfont</code>?</a>”. + + + + + + + + +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plninltx*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=plninltx*</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-poster.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-poster.html index ef7cd3de774..895a9baa746 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-poster.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-poster.html @@ -2,25 +2,25 @@ <title>UK TeX FAQ -- question label poster</title> </head><body> <h3>Creating posters with LaTeX</h3> -<p>There is no complete “canned solution” to creating a poster (as, for +<p/>There is no complete “canned solution” to creating a poster (as, for example, classes like <i>seminar</i>, <i>powerdot</i> and <i>beamer</i> serve for creating presentations in a variety of styles). -<p>The nearest approach to the complete solution is the <i>sciposter</i> +<p/>The nearest approach to the complete solution is the <i>sciposter</i> class, which provides the means to produce really rather good posters according to the author’s required style. A complete worked example is provided with the distribution -<p>Otherwise, there is a range of tools, most of which are based on the +<p/>Otherwise, there is a range of tools, most of which are based on the <i>a0poster</i> class, which sets up an appropriately-sized piece of paper, sets font sizes appropriately, and leaves you to your own devices. -<p>Having used <i>a0poster</i>, you can of course slog it out, and write +<p/>Having used <i>a0poster</i>, you can of course slog it out, and write all your poster as an unadorned LaTeX document (presumably in multiple columns, using the <i>multicol</i> package), but it’s not really necessary: the (straightforward) <i>textpos</i> package provides a simple way of positioning chunks of text, or tables or figures, on the poster page. -<p>More sophisticated is the <i>flowfram</i> package, whose basic aim +<p/>More sophisticated is the <i>flowfram</i> package, whose basic aim in life is flowing text from one box on the page to the next. One of the package’s design aims seems to have been the production of posters, and a worked example is provided. The author of @@ -28,7 +28,7 @@ posters, and a worked example is provided. The author of <a href="http://theoval.cmp.uea.ac.uk/~nlct/jpgfdraw/">JpgfDraw</a>, which allows you to construct the outline of frames for use with <i>flowfram</i>. -<p>Despite the relative shortage of tools, there are a fair few web pages +<p/>Despite the relative shortage of tools, there are a fair few web pages that explain the process (mostly in terms of the <i>a0poster</i> route): <ul> @@ -50,5 +50,5 @@ route): <dt><tt><i>sciposter.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sciposter.zip">macros/latex/contrib/sciposter</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sciposter.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sciposter/">browse</a>) <dt><tt><i>textpos.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textpos.zip">macros/latex/contrib/textpos</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/textpos.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/textpos/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=poster">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=poster</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=poster">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=poster</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-previewers.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-previewers.html index c2a314e47ee..c803b2df4d3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-previewers.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-previewers.html @@ -2,21 +2,19 @@ <title>UK TeX FAQ -- question label previewers</title> </head><body> <h3>DVI previewers</h3> -<p>EmTeX for PCs running MSDOS or OS/2, MiKTeX and +<p/>EmTeX for PCs running MSDOS or OS/2, MiKTeX and XEmTeX for PCs running Windows and OzTeX for the Macintosh, all come with previewers that can be used on those platforms. EmTeX’s previewer can also be run under Windows 3.1. -<p>Commercial PC TeX packages (see +<p/>Commercial PC TeX packages (see <a href="FAQ-commercial.html">commercial vendors</a>) have good previewers for PCs running Windows, or for Macintoshes. -<p>For Unix systems, there is one ‘canonical’ viewer, <i>xdvi</i>. +<p/>For Unix systems, there is one ‘canonical’ viewer, <i>xdvi</i>. <i>Xdvik</i> is a version of <i>xdvi</i> using the <i>web2c</i> libraries; it is now built from the same distribution -as <i>xdvi</i>. Unix TeX distributions (such as -teTeX) include a version of <i>xdvik</i> -using the same version of <i>web2c</i> as the rest of the -distribution. -<p>Alternatives to previewing include +as <i>xdvi</i>. The TeX-live distributions for Unix systems +include a version of <i>xdvik</i>. +<p/>Alternatives to previewing include <ul> <li> conversion to ‘similar’ ASCII text (see <a href="FAQ-toascii.html">converting to ASCII</a>) and using a @@ -30,5 +28,5 @@ distribution. <dl> <dt><tt><i>xdvi</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/xdvi.zip">dviware/xdvi</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/xdvi.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/xdvi/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=previewers">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=previewers</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=previewers">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=previewers</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-prinvalint.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-prinvalint.html index d04c18a79e8..b3cd65cb41c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-prinvalint.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-prinvalint.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label prinvalint</title> </head><body> <h3>The Principal Value Integral symbol</h3> -<p>This symbol (an integral sign, ‘crossed’) does not appear in any of +<p/>This symbol (an integral sign, ‘crossed’) does not appear in any of the fonts ordinarily available to (La)TeX users, but it can be created by use of the following macros: <pre> @@ -20,5 +20,5 @@ created by use of the following macros: <code>\</code><code>dashint</code> gives a single-dashed integral sign, <code>\</code><code>ddashint</code> a double-dashed one. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=prinvalint">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=prinvalint</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=prinvalint">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=prinvalint</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-privinst.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-privinst.html index c178fbaa85a..3cbdc3ec470 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-privinst.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-privinst.html @@ -2,26 +2,31 @@ <title>UK TeX FAQ -- question label privinst</title> </head><body> <h3>“Private” installations of files</h3> -<p>It sometimes happens that you need a new version of some macro package +<p/>It sometimes happens that you need a new version of some macro package or font, but that the machine you use is maintained by someone who’s unwilling to update and won’t give you privileges to do the job yourself. A <a href="FAQ-tempinst.html">“temporary” installation</a> is sometimes the correct approach, but if there’s the slightest chance that the installation will be needed on more than one project, temporary installations aren’t right. -<p>In circumstances where you have plenty of quota on backed-up media, or +<p/>In circumstances where you have plenty of quota on backed-up media, or adequate local scratch space, the correct approach is to create a private installation of (La)TeX which includes the new stuff you need; this is the ideal, but is not generally possible. -<p>So, since you can’t install into the public <code>texmf</code> tree, you -have to install into a <i>texmf</i> of your own; fortunately, the -TDS standard allows for this, and teTeX 2.0 actually makes -provision for it, defining an internal variable <code>HOMETEXMF</code> -which points to the directory <i>$HOME/texmf</i>. (TeTeX 1.0 had -the definition, but suppressed it with comment markers.) -<p>So, install your new package (or whatever) in the -<a href="FAQ-wherefiles.html">correct place</a> in a tree based on -<i>$HOME/texmf</i>, and generate an index of that tree +<p/>So, since you can’t install into the public <code>texmf</code> tree, you +have to install into a <i>texmf</i> tree of your own; fortunately, the +TDS standard allows for this, and modern distributions allow +you to do it. The most modern distributions refer to the tree as +<code>$TEXMFHOME</code>, but it used to be called <code>$HOMETEXMF</code>; +so to check that your TeX system does indeed support the mechanism +you should start with +<pre> +kpsewhich -expand-var "\$TEXMFHOME" +</pre> +<p/>If you can confirm that the technique does indeed work, install your +new package (or whatever) in the <a href="FAQ-install-where.html">correct place</a> +in a tree based on <i>$HOME/texmf</i>, and generate an index of that +tree <blockquote> <pre> texhash $HOME/texmf @@ -31,13 +36,13 @@ texhash $HOME/texmf since you don’t, by hypothesis, have access to the main tree, and <i>texhash</i> without the argument would try to write the main tree. -<p>There are two wrinkles to this simple formula: first, the installation -you’re using may <em>not</em> define <code>HOMETEXMF</code> (teTeX 1.0 -didn’t, for example), and second, there may be some obstruction to -using <i>$HOME/texmf</i> as the default name. In either case, a good -solution is to have your own <i>texmf.cnf</i> — an idea that sounds -more frightening that it actually is. The installation’s existing -file may be located with the command: +<p/>There are two wrinkles to this simple formula: first, the installation +you’re using may <em>not</em> define a home TEXMF directory, and second, +there may be some obstruction to using <i>$HOME/texmf</i> as the +default name. In either case, a good solution is to have your own +<i>texmf.cnf</i> — an idea that sounds more frightening that it +actually is. The installation’s existing file may be located with the +command: <blockquote> <pre> kpsewhich texmf.cnf @@ -61,16 +66,15 @@ setenv TEXMFCNF $HOME/texmf/web2c </pre> </blockquote><p> (for a C-shell style system). Now edit the copy of <i>texmf.cnf</i> -<p>There will be a line in the existing file that defines the tree where +<p/>There will be a line in the existing file that defines the tree where everything searches; the simplest form of the line is: <blockquote> <pre> TEXMF = !!$TEXMFMAIN </pre> </blockquote><p> -but, as teTeX 1.0 is distributed, there are several alternative -settings behind comment markers (“<code>%</code>”), and the -person who +but, there are likely to be several alternative settings behind +comment markers (“<code>%</code>”), and the person who installed your system may have left them there. Whatever, you need to modify the line that’s in effect: change the above to three lines: <blockquote> @@ -80,8 +84,9 @@ TEXMF = {$HOMETEXMF,!!$TEXMFMAIN} % TEXMF = !!$TEXMFMAIN </pre> </blockquote><p> -the important point being that <code>$HOMETEXMF</code> must come before whatever -was there before, inside the braces. For example, if the original was +the important point being that <code>$HOMETEXMF</code> must come before +whatever was there before, inside the braces. For example, if the +original was <blockquote> <pre> TEXMF = {!!$LOCALTEXMF,!!$TEXMFMAIN} @@ -109,9 +114,9 @@ TEXMF = {!!$HOMETEXMF,!!$LOCALTEXMF,!!$TEXMFMAIN} </pre> </blockquote><p> as this will make (La)TeX find its files marginally faster. -<p>Having made all these changes, (La)TeX should “just use” files in +<p/>Having made all these changes, (La)TeX should “just use” files in your new tree, in preference to anything in the main tree — you can use it for updates to packages in the main tree, as well as for installing new versions of things. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=privinst">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=privinst</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=privinst">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=privinst</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-proof.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-proof.html index e1bf94ca702..87b47238e3e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-proof.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-proof.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label proof</title> </head><body> <h3>Proof environment</h3> -<p>It has long been thought impossible to make a <code>proof</code> +<p/>It has long been thought impossible to make a <code>proof</code> environment which automatically includes an ‘end-of-proof’ symbol. Some proofs end in displayed maths; others do not. If the input file contains @@ -14,7 +14,7 @@ tricky. You <em>can</em> insert the symbol by hand, but the <i>ntheorem</i> package now solves the problem for LaTeX users: it does indeed provide an automatic way of signalling the end of a proof. -<p>The AMSLaTeX package <i>amsthm</i> also provides a +<p/>The AMSLaTeX package <i>amsthm</i> also provides a <code>proof</code> environment that does the job; though you need to insert a <code>\</code><code>qedhere</code> command if the proof ends with a displayed equation: @@ -35,5 +35,5 @@ AMSLaTeX’s numbering environments. <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>) <dt><tt><i>ntheorem</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntheorem.zip">macros/latex/contrib/ntheorem</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntheorem.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ntheorem/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=proof">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=proof</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=proof">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=proof</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html index bcc7d341a3b..710c346f896 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-protect.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label protect</title> </head><body> <h3>What’s the reason for ‘protection’?</h3> -<p>Sometimes LaTeX saves data it will reread later. These data are +<p/>Sometimes LaTeX saves data it will reread later. These data are often the argument of some command; they are the so-called moving arguments. (‘Moving’ because data are moved around.) Places to look for are all arguments that may go into table of contents, list of figures, @@ -11,25 +11,41 @@ read in later. Other places are those data that might appear in head- or footlines. Section headings and figure captions are the most prominent examples; there’s a complete list in Lamport’s book (see <a href="FAQ-books.html">TeX-related books</a>). -<p> +<p/> -<p>What’s going on really, behind the scenes? The commands in the moving -arguments are already expanded to their internal structure during the +<p/>What’s going on really, behind the scenes? The commands in moving +arguments are normally expanded to their internal structure during the process of saving. Sometimes this expansion results in invalid TeX -code when processed again. “<code>\</code><code>protect</code><code>\</code><code>cmd</code>” tells LaTeX to save -<code>\</code><code>cmd</code> as <code>\</code><code>cmd</code>, without expansion. -<p>What is a ‘fragile command’? It’s a command that expands into illegal +code, which shows either during expansion or when the code is +processed again. Protecting a command, using +“<code>\</code><code>protect</code><code>\</code><code>cmd</code>” tells LaTeX to save <code>\</code><code>cmd</code> as +<code>\</code><code>cmd</code>, without expanding it at all. +<p/>So, what is a ‘fragile command’? — it’s a command that expands into +illegal TeX code during the save process. +<p/>What is a ‘robust command’? — it’s a command that expands into legal TeX code during the save process. -<p>What is a ‘robust command’? It’s a command that expands into legal -TeX code during the save process. -<p>Again, commands are marked as ‘robust’ or ‘fragile’, as they’re -defined in Lamport’s book. Sadly, some commands are robust in -LaTeX itself, but are redefined by some packages to be fragile; the -<code>\</code><code>cite</code> command commonly suffers this treatment. -<p>No-one (of course) likes this situation; the LaTeX3 team have -removed the need for protection of some things in the production of -LaTeX2e, but the techniques available to them within current -LaTeX mean that this is an expensive exercise. It remains a -long-term aim of the team to remove all need for these things. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=protect">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=protect</a> +<p/>Lamport’s book says in its description of every LaTeX command whether +it is ‘robust’ or ‘fragile’; it also says that every command with an +optional argument is fragile. These lists aren’t as reliable as the +list of moving arguments; the statements may have been true in +early versions of LaTeX2e but are not any longer necessarily so: +<ul> +<li> Some fragile commands, such as <code>\</code><code>cite</code>, have been made robust + in later revisions of LaTeX. +<li> Some robust commands are redefined by certain packages to be + fragile (the <code>\</code><code>cite</code> command commonly suffers this treatment). +<li> Some commands, such as <code>\</code><code>end</code> and <code>\</code><code>nocite</code>, are fragile + even though they have no optional arguments. +<li> The “user’s way” of creating a command with an optional + argument (using <code>\</code><code>newcommand</code>) now always creates a robust + command. There is no reason that a package author should not also + make robust commands with optional arguments as part of the + package. +</ul> +In short, the situation is confusing. No-one believes this is +satisfactory, and the LaTeX team have removed the need for +protection of some things, but the techniques available in +current LaTeX mean that this is an expensive exercise. It remains +a long-term aim of the team to remove all need for <code>\</code><code>protect</code>ion. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=protect">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=protect</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psatempty.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psatempty.html index afaf4f255b3..36d2b34284b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psatempty.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psatempty.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label ps@empty</title> </head><body> <h3><code>\pagestyle{empty}</code> on first page in LaTeX</h3> -<p>If you use <code>\</code><code>pagestyle{empty}</code>, but the first page is numbered +<p/>If you use <code>\</code><code>pagestyle{empty}</code>, but the first page is numbered anyway, you are probably using the <code>\</code><code>maketitle</code> command too. The behaviour is not a bug but a feature. The standard LaTeX classes are written so that initial pages (pages containing a <code>\</code><code>maketitle</code>, @@ -10,14 +10,14 @@ written so that initial pages (pages containing a <code>\</code><code>maketitle< of the document; to achieve this, the commands internally issue <code>\</code><code>thispagestyle{plain}</code>. This is usually not acceptable behaviour if the surrounding page style is ‘empty’. -<p>Possible workarounds include: +<p/>Possible workarounds include: <ul> <li> Put <code>\</code><code>thispagestyle{empty</code>} immediately after the <code>\</code><code>maketitle</code> command, with no blank line between them. <li> Use the <i>fancyhdr</i> or <i>scrpage2</i> packages, which allow you to customise the style for initial pages independently of that for body pages. -<p> For example, use <i>fancyhdr</i> commands: +<p/> For example, use <i>fancyhdr</i> commands: <pre> \fancypagestyle{plain}{% \fancyhf{}% @@ -38,5 +38,5 @@ behaviour if the surrounding page style is ‘empty’. <dt><tt><i>nopageno.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle/nopageno.sty">macros/latex/contrib/carlisle/nopageno.sty</a> <dt><tt><i>scrpage2.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ps@empty">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ps@empty</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ps@empty">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ps@empty</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfchoice.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfchoice.html index f3686216433..e7b2aeebaea 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfchoice.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfchoice.html @@ -2,14 +2,19 @@ <title>UK TeX FAQ -- question label psfchoice</title> </head><body> <h3>Choice of scalable outline fonts</h3> -<p>If you are interested in text alone, you can in principle use any of +<p/>If you are interested in text alone, you can in principle use any of the huge numbers of text fonts in Adobe Type 1, TrueType or OpenType formats. The constraint is, of course, that your previewer and printer driver should support such fonts (TeX itself <em>only</em> cares about metrics, not the actual character programs). -<p>If you also need mathematics, then you are severely limited by the -demands that TeX makes of maths fonts (for details, see the paper by B.K.P. -Horn in <i>TUGboat</i> 14(3)). +<p/>If you also need mathematics, then you are severely limited by the +demands that TeX makes of maths fonts (for details, see the papers +by + + <a href="http://tug.org/TUGboat/Articles/tb14-3/tb40horn.pdf">B.K.P. Horn in <i>TUGboat</i> 14(3)</a>, + or by + <a href="http://tug.org/TUGboat/Articles/tb19-2/tb59bouc.pdf">Thierry Bouche in <i>TUGboat</i> 19(2)</a>). + For maths, then, there are relatively few choices (though the list is at last growing). There are several font families available that are based on Knuth’s original designs, and some that complement other @@ -58,11 +63,23 @@ mathematics include: fonts come with a <i>fourier</i> package for use with LaTeX; text support of OT1 encoding is not provided — you are expected to use T1. -<dt>MathDesign<dd>(3 entire families...so far) Paul Pichareau<br> - This (very new: first release was in April 2005) set so far offers - mathematics fonts to match Adobe Utopia, URW Garamond and Bitstream - Charter (all of which are separately available, on CTAN, in Type 1 - format). There has been a little comment on these fonts, but none +<dt>Fourier/New Century Schoolbook<dd>Michael Zedler<br> + <i>Fouriernc</i> is a configuration using the Fourier fonts in + the context of New Century Schoolbook text fonts. +<dt>Kp-fonts<dd>The Johannes Kepler project<br> + The <i>kp-fonts</i> family provides a comprehensive set of text + and maths fonts. The set includes replacement fixed-width and sans + fonts (though some reports have suggested that these are less + successful, and their use may be suppressed when loading the fonts’ + <i>kpfonts</i> LaTeX support package). +<dt>MathDesign<dd>(4 entire families...so far) Paul Pichareau<br> + This set so far offers mathematics fonts to match Adobe Utopia, URW + Garamond, Bitstream Charter (all of which are separately available, + on CTAN, in Type 1 format) and Fontsite Garamond + (which is a commercial font, available from the + <a href="FontSite Web shop">http://www.fontsite.com/Pages/FFDownloads.html</a>). + + There has been a little comment on these fonts, but none from actual users posted to the public forums. Users, particularly those who are willing to discuss their experiences, would obviously be welcome. Browse the CTAN directory and see which you @@ -73,13 +90,12 @@ mathematics include: as Type 1 fonts, and as TrueType fonts. The fonts act as “drop-in” replacements for the basic MathTime set (as an example of “what might be done”). -<p> The paper outlining Kinch’s thoughts, proceeding from considerations +<p/> The paper outlining Kinch’s thoughts, proceeding from considerations of the ‘intellectual’ superiority of Metafont to evaluations of why its adoption is so limited and what might be done about the problem, is to be found at <a href="http://truetex.com/belleek.pdf">http://truetex.com/belleek.pdf</a> (the paper is a - good read, but exhibits the problems discussed in - “<a href="FAQ-dvips-pdf.html">getting good PDF</a>” — - don’t try to read it on-screen in Acrobat reader). + good read, but is set with Bitmap fonts, and can be difficult + on-screen in Acrobat reader 5 or earlier). <dt>mathptmx<dd>Alan Jeffrey, Walter Schmidt and others.<br> This set contains maths italic, symbol, extension, and roman virtual fonts, built from Adobe Times, Symbol, Zapf Chancery, and the @@ -105,7 +121,7 @@ commercially, include: useful glyphs of the TS1 encoding. Macros for using the fonts with Plain TeX, LaTeX 2.09 and current LaTeX are provided. -<p> +<p/> For further details (including samples) see<br> <a href="http://www.micropress-inc.com/fonts/bamath/bamain.htm">http://www.micropress-inc.com/fonts/bamath/bamain.htm</a> @@ -129,7 +145,7 @@ commercially, include: <i>hfbright</i> bundle offers free Type 1 fonts for text using the OT1 encoding — the <i>cm-super</i> set for use with T1 texts doesn’t (yet) offer support for mathematics. -<p> +<p/> For further details of Micropress’ offering (including samples) see<br> <a href="http://www.micropress-inc.com/fonts/brmath/brmain.htm">http://www.micropress-inc.com/fonts/brmath/brmain.htm</a> @@ -144,7 +160,7 @@ commercially, include: applications such as posters or transparencies. Concrete Math fonts, as well as Concrete Roman fonts, are supplied in Type 1 format by MicroPress, Inc. -<p> +<p/> For further information (including samples) see<br> <a href="http://www.micropress-inc.com/fonts/ccmath/ccmain.htm">http://www.micropress-inc.com/fonts/ccmath/ccmain.htm</a> @@ -158,7 +174,7 @@ commercially, include: encoding. Macros for using the fonts with Plain TeX, LaTeX 2.09 and current LaTeX are provided. Bitmapped copies of the fonts are available free, on CTAN. -<p> +<p/> For further details (and samples) see<br> <a href="http://www.micropress-inc.com/fonts/hvmath/hvmain.htm">http://www.micropress-inc.com/fonts/hvmath/hvmain.htm</a> @@ -170,7 +186,7 @@ commercially, include: in normal weight, as well as OT1 encoded text fonts in upright and oblique shapes. Macros for using the fonts with Plain TeX, LaTeX 2.09 and current LaTeX are provided. -<p> +<p/> For further details (including samples) see<br> <a href="http://www.micropress-inc.com/fonts/ifmath/ifmain.htm">http://www.micropress-inc.com/fonts/ifmath/ifmain.htm</a> @@ -188,9 +204,8 @@ commercially, include: smallcaps, bold maths, upright ‘maths italic’, <em>etc</em>., to the set. Support under LaTeX is available under the auspices of the PSNFSS, and pre-built metrics are also provided. -<p> - TUG has recently (November 2005) acquired the right to distribute - these fonts; the web site +<p/> + TUG has the right to distribute these fonts; the web site “<a href="http://tug.org/lucida/">Lucida and TUG</a>” has details. @@ -228,7 +243,7 @@ commercially, include: -<dt>MathTime Pro<dd>Publish or Perish (Michael Spivak)<br> +<dt>MathTime Pro2<dd>Publish or Perish (Michael Spivak)<br> This latest instance of the MathTime family covers all the weights (medium, bold and heavy) and symbols of previous versions of MathTime. In addition it has a much extended range of symbols, and @@ -236,10 +251,19 @@ commercially, include: The fonts are supported under both Plain TeX and LaTeX2e, and are exclusively available for purchase from <a href="FAQ-commercial.html">Personal TeX Inc</a>. - \par + <p/> - For a sample, see <a href="http://www.pctex.com/mtpdemo.pdf">http://www.pctex.com/mtpdemo.pdf</a> + For further details and samples and fliers, see + <a href="http://www.pctex.com/mtpro2.html">http://www.pctex.com/mtpro2.html</a> +<dt>Minion Pro and MnSymbol<dd>Adobe, LaTeX support and packaging by + Achim Blumensath <em>et al</em>.<br> + <i>Minion Pro</i> derives from the widely-available commercial + OpenType font of the same name by Adobe; scripts are provided to + convert relevant parts of it to Adobe Type 1 format. The + <i>MinionPro</i> package will set up text and maths support using + <i>Minion Pro</i>, but a separate (free) font set + <i>MnSymbol</i> greatly extends the symbol coverage. <dt>PA Math<dd> PA Math is a family of serif fonts loosely based on the Palatino (TM) typeface. PA Math comprises the fonts necessary for mathematical typesetting (maths @@ -249,7 +273,7 @@ commercially, include: with the most useful glyphs of the TS1 encoding. Macros for using the fonts with Plain TeX, LaTeX 2.09 and current LaTeX are provided. -<p> +<p/> For further details (and samples) see<br> <a href="http://www.micropress-inc.com/fonts/pamath/pamain.htm">http://www.micropress-inc.com/fonts/pamath/pamain.htm</a> @@ -263,7 +287,7 @@ commercially, include: using the fonts with Plain TeX, LaTeX 2.09 and current LaTeX are provided. Bitmapped copies of the fonts are available free, on CTAN. -<p> +<p/> For further details (and samples) see<br> <a href="http://www.micropress-inc.com/fonts/tmmath/tmmain.htm">http://www.micropress-inc.com/fonts/tmmath/tmmain.htm</a> @@ -296,7 +320,7 @@ working on them, and several problems have been identified: <a href="http://www.tex.ac.uk/tex-archive/fonts/pxfonts/doc/pxfontsdocA4.pdf">Documentation</a> is readily available. -<p> The fonts are licensed under the GPL; use in published +<p/> The fonts are licensed under the GPL; use in published documents is permitted. <dt>txfonts set version 3.1<dd>(42 fonts) by Young Ryu<br> The <i>txfonts</i> set consists of @@ -318,7 +342,7 @@ working on them, and several problems have been identified: <a href="http://www.tex.ac.uk/tex-archive/fonts/txfonts/doc/txfontsdocA4.pdf">Documentation</a> is readily available. -<p> The fonts are licensed under the GPL; use in published +<p/> The fonts are licensed under the GPL; use in published documents is permitted. </dl> Finally, one must not forget: @@ -336,7 +360,7 @@ maths font has to be explicitly designed for use with TeX, which is an expensive business, and is of little appeal in other markets. Furthermore, the TeX market for commercial fonts is minute by comparison with the huge sales of other font sets. -<p>Text fonts in Type 1 format are available from many vendors including +<p/>Text fonts in Type 1 format are available from many vendors including Adobe, Monotype and Bitstream. However, be careful with cheap font “collections”; many of them dodge copyright restrictions by removing (or crippling) parts of the font programs such as hinting. Such @@ -344,13 +368,13 @@ behaviour is both unethical and bad for the consumer. The fonts may not render well (or at all, under ATM), may not have the ‘standard’ complement of 228 glyphs, or may not include metric files (which you need to make TFM files). -<p>TrueType remains the “native” format for Windows. Some TeX +<p/>TrueType remains the “native” format for Windows. Some TeX implementations such as <a href="FAQ-commercial.html">TrueTeX</a> use TrueType versions of Computer Modern and Times Maths fonts to render TeX documents in Windows without the need for additional system software like ATM. (When used on a system running Windows XP, TrueTeX can also use Type 1 fonts.) -<p>When choosing fonts, your own system environment may not be the only one of +<p/>When choosing fonts, your own system environment may not be the only one of interest. If you will be sending your finished documents to others for further use, you should consider whether a given font format will introduce compatibility problems. Publishers may require TrueType exclusively because @@ -370,17 +394,21 @@ print file (PostScript or PDF) for their output device. <a href="ftp://cam.ctan.org/tex-archive/fonts/eulervm.zip">fonts/eulervm</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/eulervm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/eulervm/">browse</a>) <dt><tt><i>fourier (including metrics and other support for utopia</i></tt><dd> <a href="ftp://cam.ctan.org/tex-archive/fonts/fourier-GUT.zip">fonts/fourier-GUT</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/fourier-GUT.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/fourier-GUT/">browse</a>) +<dt><tt><i>fouriernc</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/fouriernc.zip">fonts/fouriernc</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/fouriernc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/fouriernc/">browse</a>) <dt><tt><i>hfbright collection</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/hfbright.zip">fonts/ps-type1/hfbright</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/hfbright.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/hfbright/">browse</a>) <dt><tt><i>hvmath (free bitmapped version)</i></tt><dd> <a href="ftp://cam.ctan.org/tex-archive/fonts/micropress/hvmath.zip">fonts/micropress/hvmath</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/micropress/hvmath.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/micropress/hvmath/">browse</a>) +<dt><tt><i>kpfonts family</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/kpfonts.zip">fonts/kpfonts</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/kpfonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/kpfonts/">browse</a>) <dt><tt><i>Lucida Bright/Math metrics</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/psfonts/bh/lucida.zip">fonts/psfonts/bh/lucida</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/psfonts/bh/lucida.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/psfonts/bh/lucida/">browse</a>) <dt><tt><i>Lucida PSNFSS support</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psnfssx/lucidabr.zip">macros/latex/contrib/psnfssx/lucidabr</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/psnfssx/lucidabr.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/psnfssx/lucidabr/">browse</a>) <dt><tt><i>MathDesign collection</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/fonts/mathdesign/">fonts/mathdesign/</a> +<dt><tt><i>Minion Pro support</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/minionpro.zip">fonts/minionpro</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/minionpro.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/minionpro/">browse</a>) +<dt><tt><i>MnSymbol family</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/mnsymbol.zip">fonts/mnsymbol</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/mnsymbol.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/mnsymbol/">browse</a>) <dt><tt><i>pxfonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/pxfonts.zip">fonts/pxfonts</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/pxfonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/pxfonts/">browse</a>) <dt><tt><i>tmmath (free bitmapped version)</i></tt><dd> <a href="ftp://cam.ctan.org/tex-archive/fonts/micropress/tmmath.zip">fonts/micropress/tmmath</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/micropress/tmmath.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/micropress/tmmath/">browse</a>) <dt><tt><i>txfonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/txfonts.zip">fonts/txfonts</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/txfonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/txfonts/">browse</a>) <dt><tt><i>utopia fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utopia.zip">fonts/utopia</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utopia.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utopia/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=psfchoice">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=psfchoice</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=psfchoice">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=psfchoice</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html index d52bbafee1d..95ce51a336a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html @@ -2,17 +2,17 @@ <title>UK TeX FAQ -- question label psfontprob</title> </head><body> <h3>Deploying Type 1 fonts</h3> -<p>For the LaTeX user trying to use the +<p/>For the LaTeX user trying to use the <a href="FAQ-usepsfont.html">PSNFSS</a> package, three questions may arise. -<p>First, you have to declare to the DVI driver that you are using +<p/>First, you have to declare to the DVI driver that you are using PostScript fonts; in the case of <i>dvips</i>, this means adding lines to the <code>psfonts.map</code> file, so that <i>dvips</i> will know where the proper fonts are, and won’t try to find PK files. If the font isn’t built into the printer, you have to acquire it (which may mean that you need to purchase the font files). -<p>Second, your previewer must know what to do with the fonts: see +<p/>Second, your previewer must know what to do with the fonts: see <a href="FAQ-PSpreview.html">previewing type 1 fonts</a>. -<p>Third, the stretch and shrink between words is a function of the +<p/>Third, the stretch and shrink between words is a function of the font metric; it is not specified in AFM files, so different converters choose different values. The PostScript metrics that come with PSNFSS used to produce quite tight setting, but they were revised in mid 1995 @@ -21,5 +21,5 @@ Sophisticated users may not find even the new the values to their taste, and want to override them. Even the casual user may find more hyphenation or overfull boxes than Computer Modern produces; but CM is extremely generous. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=psfontprob">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=psfontprob</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=psfontprob">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=psfontprob</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ragright.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ragright.html index 52cb0c0a86a..b40bbf4d248 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ragright.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ragright.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label ragright</title> </head><body> <h3>Setting text ragged right</h3> -<p>The trick with typesetting ragged right is to be sure you’ve told the +<p/>The trick with typesetting ragged right is to be sure you’ve told the TeX engine “make this paragraph ragged, but never <em>too</em> ragged”. The LaTeX <code>\</code><code>raggedright</code> command (and the corresponding <code>flushleft</code> environment) has a tendency to @@ -15,7 +15,7 @@ of the line, but in some circumstances (such as where <a href="FAQ-hyphoff.html">hyphenation is suppressed</a>) painfully large gaps may sometimes be required. -<p>Martin Schröder’s <i>ragged2e</i> package offers the best of both +<p/>Martin Schröder’s <i>ragged2e</i> package offers the best of both worlds: it provides raggedness which is built on the Plain TeX model, but which is easily configurable. It defines easily-remembered command (e.g., <code>\</code><code>RaggedRight</code>) and environment (e.g., @@ -26,5 +26,5 @@ parameters of <i>ragged2e</i>’s operation. <dl> <dt><tt><i>ragged2e.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ragright">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ragright</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ragright">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ragright</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readML.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readML.html index c3bb9727379..eb8f31c7835 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readML.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readML.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label readML</title> </head><body> <h3>Using TeX to read SGML or XML directly</h3> -<p>This can nowadays be done, with a certain amount of clever macro +<p/>This can nowadays be done, with a certain amount of clever macro programming. David Carlisle’s <i>xmltex</i> is the prime example; it offers a practical solution to typesetting XML files. -<p>One use of a TeX that can typeset XML files is as a backend +<p/>One use of a TeX that can typeset XML files is as a backend processor for XSL formatting objects, serialized as XML. Sebastian Rahtz’s PassiveTeX uses <i>xmltex</i> to achieve this end. @@ -14,5 +14,5 @@ achieve this end. <dt><tt><i>xmltex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/xmltex/base.zip">macros/xmltex/base</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/xmltex/base.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/xmltex/base/">browse</a>) <dt><tt><i>passivetex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/xmltex/contrib/passivetex.zip">macros/xmltex/contrib/passivetex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/xmltex/contrib/passivetex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/xmltex/contrib/passivetex/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=readML">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=readML</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=readML">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=readML</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html index d1a4c3b0832..7844a57b389 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label readtex</title> </head><body> <h3>Reading (La)TeX files</h3> -<p>So you’ve been sent a TeX file: what are you going to do with it? -<p>You can, of course, “just read it”, since it’s a plain text file, +<p/>So you’ve been sent a TeX file: what are you going to do with it? +<p/>You can, of course, “just read it”, since it’s a plain text file, but the markup tags in the document may prove distracting. Most of the time, even TeX experts will typeset a TeX file before attempting to read it. -<p>So, you need to typeset the document. The good news is that TeX +<p/>So, you need to typeset the document. The good news is that TeX systems are available, free, for most sorts of computer; the bad news is that you need a pretty complete TeX system even to read a single file, and complete TeX systems are pretty large. -<p>TeX is a typesetting system that arose from a publishing project (see +<p/>TeX is a typesetting system that arose from a publishing project (see <a href="FAQ-whatTeX.html">what is TeX</a>), and its basic source is available free from its author. However, at its root, it is <em>just</em> a typesetting engine: even to view or to @@ -24,7 +24,7 @@ of the sorts of things that are available, see or “<a href="FAQ-commercial.html">commercial TeX distributions</a>”. -<p>But beware — TeX makes no attempt to look like the sort of +<p/>But beware — TeX makes no attempt to look like the sort of WYSIWYG system you’re probably used to (see <a href="FAQ-notWYSIWYG.html">why is TeX not WYSIWYG</a>): @@ -32,11 +32,9 @@ while many modern versions of TeX have a compile–view cycle that rivals the best commercial word processors in its responsiveness, what you type is usually <em>markup</em>, which typically defines a logical (rather than a visual) view of what you want typeset. -<p>However, in this context markup proves to be a blessing in disguise: a -good proportion of most TeX documents is immediately readable in an -ordinary text editor. So, while you need to install a considerable -system to attain the full benefits of the TeX document that you -were sent, the chances are you can understand quite a bit of it with -nothing more than the ordinary tools you already have on your computer. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=readtex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=readtex</a> +<p/>So there’s a balance between the simplicity of the original +(marked-up) document, which can more-or-less be read in <em>any</em> +editor, and the really rather large investment needed to install a +system to read a document “as intended”. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=readtex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=readtex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reallyblank.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reallyblank.html index eaf948013a4..30e0bc2407e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reallyblank.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reallyblank.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label reallyblank</title> </head><body> <h3>Really blank pages between chapters</h3> -<p><i>Book</i> (by default) and <i>report</i> (with <code>openright</code> class +<p/><i>Book</i> (by default) and <i>report</i> (with <code>openright</code> class option) ensure that each chapter starts on a right-hand (recto) page; they do this by inserting a <code>\</code><code>cleardoublepage</code> command between chapters (rather than a mere <code>\</code><code>clearpage</code>). The empty page thus created gets to have a normal running header, which some people don’t like. -<p>The (excellent) <i>fancyhdr</i> manual covers this issue, basically +<p/>The (excellent) <i>fancyhdr</i> manual covers this issue, basically advising the creation of a command <code>\</code><code>clearemptydoublepage</code>: <blockquote> <pre> @@ -35,14 +35,14 @@ of <code>\</code><code>cleardoublepage</code>: instructions on macro programming <a href="FAQ-patch.html">patching techniques</a> explain the problem and why this is a solution. -<p>Note that the <em>KOMA-Script</em> replacements for the +<p/>Note that the <em>KOMA-Script</em> replacements for the <i>book</i> amd <i>report</i> classes (<i>scrbook</i> and <i>scrreprt</i> offers class options <code>cleardoubleempty</code>, <code>cleardoubleplain</code> and <code>cleardoublestandard</code> (using the running page style, as normal) that control the appearance of these empty pages. The classes also offer do-it-yourself commands <code>\</code><code>cleardoubleempty</code> (etc.). -<p>The <i>memoir</i> class (and the <i>nextpage</i> package) +<p/>The <i>memoir</i> class (and the <i>nextpage</i> package) provide commands <code>\</code><code>cleartooddpage</code> and <code>\</code><code>cleartoevenpage</code>, which both take an optional argument (the first, with no argument, being an equivalent of <code>\</code><code>cleardoublepage</code>). One can achieve @@ -57,5 +57,5 @@ intentionally left blank” in the centre of an otherwise empty page. <dt><tt><i>nextpage.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/nextpage.sty">macros/latex/contrib/misc/nextpage.sty</a> <dt><tt><i>scrbook.cls, scrrept.cls</i></tt><dd>Part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=reallyblank">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=reallyblank</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=reallyblank">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=reallyblank</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-recovertex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-recovertex.html index f8111cdc156..9d9ae11ad33 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-recovertex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-recovertex.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label recovertex</title> </head><body> <h3>Retrieving (La)TeX from DVI, etc.</h3> -<p>The job just can’t be done automatically: DVI, PostScript and +<p/>The job just can’t be done automatically: DVI, PostScript and PDF are “final” formats, supposedly not susceptible to further editing — information about where things came from has been discarded. So if you’ve lost your (La)TeX source (or never @@ -11,25 +11,25 @@ on your hands. In many circumstances, the best strategy is to retype the whole document, but this strategy is to be tempered by consideration of the size of the document and the potential typists’ skills. -<p>If automatic assistance is necessary, it’s unlikely that any more than +<p/>If automatic assistance is necessary, it’s unlikely that any more than text retrieval is going to be possible; the (La)TeX markup that creates the typographic effects of the document needs to be recreated by editing. -<p>If the file you have is in DVI format, many of the techniques +<p/>If the file you have is in DVI format, many of the techniques for <a href="FAQ-toascii.html">converting (La)TeX to ASCII</a> are applicable. Consider <i>dvi2tty</i>, <i>crudetype</i> and <i>catdvi</i>. Remember that there are likely to be problems finding included material (such as included PostScript figures, that don’t appear in the DVI file itself), and mathematics is unlikely to convert easily. -<p>To retrieve text from PostScript files, the +<p/>To retrieve text from PostScript files, the <i>ps2ascii</i> tool (part of the <i>ghostscript</i> distribution) is available. One could try applying this tool to PostScript derived from an PDF file using <i>pdf2ps</i> (also from the <i>ghostscript</i> distribution), or <i>Acrobat</i> <i>Reader</i> itself; an alternative is <i>pdftotext</i>, which is distributed with <i>xpdf</i>. -<p>Another avenue available to those with a PDF file they want to +<p/>Another avenue available to those with a PDF file they want to process is offered by Adobe <i>Acrobat</i> (version 5 or later): you can tag the PDF file into an estructured document, output thence to well-formed XHTML, and import the results into @@ -37,16 +37,16 @@ Microsoft <i>Word</i> (2000 or later). From there, one may convert to (La)TeX using one of the techniques discussed in “<a href="FAQ-fmtconv.html">converting to and from (La)TeX</a>”. -<p>The result will typically (at best) be poorly marked-up. Problems may +<p/>The result will typically (at best) be poorly marked-up. Problems may also arise from the oddity of typical TeX font encodings (notably those of the maths fonts), which <i>Acrobat</i> doesn’t know how to map to its standard Unicode representation. <dl> <dt><tt><i>catdvi</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/catdvi.zip">dviware/catdvi</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/catdvi.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/catdvi/">browse</a>) <dt><tt><i>crudetype</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/crudetype.zip">dviware/crudetype</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/crudetype.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/crudetype/">browse</a>) -<dt><tt><i>dvi2tty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/dviware/dvi2tty.zip">nonfree/dviware/dvi2tty</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/dviware/dvi2tty.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/dviware/dvi2tty/">browse</a>) -<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/ghostscript/">nonfree/support/ghostscript/</a> +<dt><tt><i>dvi2tty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvi2tty.zip">dviware/dvi2tty</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvi2tty.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvi2tty/">browse</a>) +<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/">support/ghostscript/</a> <dt><tt><i>xpdf</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/xpdf/">support/xpdf/</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=recovertex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=recovertex</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=recovertex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=recovertex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ref-doc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ref-doc.html index 65aac9f7fda..6b55c4319d0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ref-doc.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-ref-doc.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label ref-doc</title> </head><body> <h3>Reference documents</h3> -<p>For TeX primitive commands a rather nice +<p/>For TeX primitive commands a rather nice <a href="http://www.nmt.edu/tcc/help/pubs/texcrib.pdf">quick reference booklet</a>, by John W. Shipman, is available; it’s arranged in the same way as the TeXbook. By contrast, you can view David Bausum’s @@ -10,14 +10,14 @@ TeXbook. By contrast, you can view David Bausum’s alphabetically or arranged by “family”. Either way, the list has a link for each control sequence, that leads you to a detailed description, which includes page references to the TeXbook. -<p>There doesn’t seem to be a reference that takes in Plain TeX as +<p/>There doesn’t seem to be a reference that takes in Plain TeX as well as the primitive commands. -<p>Similarly, there’s no completely reliable command-organised reference +<p/>Similarly, there’s no completely reliable command-organised reference to LaTeX, but the NASA <a href="http://www.giss.nasa.gov/latex/">Hypertext Help with LaTeX</a> is recently much improved. It still talks in LaTeX 2.09-isms in places, but it’s been updated for current LaTeX; there are a number of mirrors of the site, and it may be worth choosing a “local” one if you’re going to use it a lot. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ref-doc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ref-doc</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ref-doc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=ref-doc</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-repeatgrf.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-repeatgrf.html index 804ade5cd7e..8689aa5a640 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-repeatgrf.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-repeatgrf.html @@ -2,27 +2,27 @@ <title>UK TeX FAQ -- question label repeatgrf</title> </head><body> <h3>Repeated graphics in a document</h3> -<p>A logo or “watermark” image, or any other image that is repeated in +<p/>A logo or “watermark” image, or any other image that is repeated in your document, has the potential to make the processed version of the document unmanageably large. The problem is, that the default mechanisms of graphics usage add the image at every point it’s to be used, and when processed, the image appears in the output file at each such point. -<p>Huge PostScript files are embarrassing; explaining <em>why</em> such a file +<p/>Huge PostScript files are embarrassing; explaining <em>why</em> such a file is huge, is more embarrassing still. -<p>The <a href="FAQ-tutbitslatex.html"><i>epslatex</i> graphics tutorial</a> +<p/>The <a href="FAQ-tutbitslatex.html"><i>epslatex</i> graphics tutorial</a> describes a technique for avoiding the problem: basically, one converts the image that’s to be repeated into a PostScript subroutine, and load that as a <i>dvips</i> prologue file. In place of the image, you load a file (with the same bounding box as the image) containing no more than an invocation of the subroutine defined in the prologue. -<p>The <i>epslatex</i> technique is tricky, but does the job. Trickier +<p/>The <i>epslatex</i> technique is tricky, but does the job. Trickier still is the neat scheme of converting the figure to a one-character Adobe Type 3 outline font. While this technique is for the “real experts” only (the author of this answer has never even tried it), it has potential for the same sort of space saving as the <i>epslatex</i> technique, with greater flexibility in actual use. -<p>More practical is Hendri Adriaens’ <i>graphicx-psmin</i>; you load +<p/>More practical is Hendri Adriaens’ <i>graphicx-psmin</i>; you load this <em>in place</em> of <i>graphicx</i>, so rather than: <blockquote> <pre> @@ -44,14 +44,14 @@ and at the start of your document, you write: and each of the graphics in the list is converted to an “object” for use within the resulting PostScript output. (This is, in essence, an automated version of the <i>epslatex</i> technique described above.) -<p>Having loaded the package as above, whenever you use +<p/>Having loaded the package as above, whenever you use <code>\</code><code>includegraphics</code>, the command checks if the file you’ve asked for is one of the graphics in <code>\</code><code>loadgraphics</code>’ list. If so, the operation is converted into a call to the “object” rather than a new copy of the file; the resulting PostScript can of course be <em>much</em> smaller. -<p>Note that the package requires a recent <i>dvips</i>, version +<p/>Note that the package requires a recent <i>dvips</i>, version 5.95b (this version isn’t — yet — widely distributed). -<p>If your PostScript is destined for conversion to PDF, either by a +<p/>If your PostScript is destined for conversion to PDF, either by a <i>ghostscript</i>-based mechanism such as <i>ps2pdf</i> or by (for example) <i>Acrobat</i> <i>Distiller</i>, the issue isn’t so pressing, since the distillation mechanism will amalgamate graphics @@ -61,5 +61,5 @@ into references to graphics objects. <dl> <dt><tt><i>graphicx-psmin.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/graphicx-psmin.zip">macros/latex/contrib/graphicx-psmin</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/graphicx-psmin.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/graphicx-psmin/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repeatgrf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repeatgrf</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repeatgrf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repeatgrf</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-repfootnote.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-repfootnote.html index 3876ced01b2..ae3ebeb8d5f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-repfootnote.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-repfootnote.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label repfootnote</title> </head><body> <h3>Footnotes whose texts are identical</h3> -<p>If the <em>same</em> footnote turns up at several places within a +<p/>If the <em>same</em> footnote turns up at several places within a document, it’s often inappropriate to repeat the footnote in its entirety over and over again. We can avoid repetition by semi-automatic means, or by simply labelling footnotes that we know we’re going to repeat and then referencing the result. There is no completely automatic solution (that detects and suppresses repeats) available. -<p>If you know you only have one footnote, which you want to repeat, the +<p/>If you know you only have one footnote, which you want to repeat, the solution is simple: merely use the optional argument of <code>\</code><code>footnotemark</code> to signify the repeats: <blockquote> @@ -24,7 +24,7 @@ footnote number 1. A similar technique can be used once the footnotes are stable, reusing the number that LaTeX has allocated. This can be tiresome, though, as any change of typesetting could change the relationships of footnote and repeat: labelling is inevitably better. -<p>Simple hand-labelling of footnotes is possible, using a counter dedicated +<p/>Simple hand-labelling of footnotes is possible, using a counter dedicated to the job: <blockquote> <pre> @@ -61,7 +61,7 @@ example to: This is the cleanest simple way of doing the job. Note that the <code>\</code><code>label</code> command <em>must</em> be inside the argument of <code>\</code><code>footnote</code>. -<p>The <i>fixfoot</i> package takes away some of the pain of the +<p/>The <i>fixfoot</i> package takes away some of the pain of the matter: you declare footnotes you’re going to reuse, typically in the preamble of your document, using a <code>\</code><code>DeclareFixedFoot</code> command, and then use the command you’ve ‘declared’ in the body of the document: @@ -81,5 +81,5 @@ the repeats. <dt><tt><i>footmisc.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.zip">macros/latex/contrib/footmisc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footmisc/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repfootnote">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repfootnote</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repfootnote">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=repfootnote</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-replstdcls.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-replstdcls.html index b635a61665a..2588d3fcc3f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-replstdcls.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-replstdcls.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label replstdcls</title> </head><body> <h3>Replacing the standard classes</h3> -<p>People are forever concocting classes that replace the standard ones: +<p/>People are forever concocting classes that replace the standard ones: the present author produced an <i>ukart</i> class that used the <i>sober</i> package, and a few British-specific things (such as appear in the <i>babel</i> package’s British-english specialisation) in the 1980s, which is still occasionally used. -<p>Similar public efforts were available well back in the days of +<p/>Similar public efforts were available well back in the days of LaTeX 2.09: a notable example, whose pleasing designs seem not to have changed much over all that time, is the <i>ntgclass</i> bundle. Each of the standard classes is replaced by a selection of classes, @@ -15,13 +15,13 @@ named in Dutch, sometimes with a single numeric digit attached. So we have classes <i>artikel2</i>, <i>rapport1</i>, <i>boek3</i> and <i>brief</i>. These classes are moderately well documented in English. -<p>The <i>KOMA-script</i> bundle (classes named <i>scr...</i>) are a +<p/>The <i>KOMA-script</i> bundle (classes named <i>scr...</i>) are a strong current contender. They are actively supported, are comprehensive in their coverage of significant typesetting issues, produce good-looking output and are well documented in both English and German (<i>scrguien</i> in the distribution for English, <i>scrguide</i> for German). -<p>The other comparable class is <i>memoir</i>. This aims to replace +<p/>The other comparable class is <i>memoir</i>. This aims to replace <i>book</i> and <i>report</i> classes directly, and (like <i>KOMA-script</i>) is comprehensive in its coverage of small issues. <i>Memoir</i>’s documentation (<i>memman</i>) is very highly @@ -33,5 +33,5 @@ recommended as a tutorial on typesetting. <dt><tt><i>NTGclass bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntgclass.zip">macros/latex/contrib/ntgclass</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntgclass.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ntgclass/">browse</a>) <dt><tt><i>sober.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/misc/sober.sty">macros/latex209/contrib/misc/sober.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=replstdcls">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=replstdcls</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=replstdcls">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=replstdcls</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rerun.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rerun.html index dbb98259de7..47c99b6788f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rerun.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rerun.html @@ -2,31 +2,31 @@ <title>UK TeX FAQ -- question label rerun</title> </head><body> <h3>“Rerun” messages won’t go away</h3> -<p>The LaTeX message “Rerun to get crossreferences right” is +<p/>The LaTeX message “Rerun to get crossreferences right” is supposed to warn the user that the job needs to be processed again, since labels seem to have changed since the previous run. (LaTeX compares the labels it has created this time round with what it found from the previous run when it started; it does this comparison at <code>\</code><code>end{document}</code>.) -<p>Sometimes, the message won’t go away: however often you reprocess your +<p/>Sometimes, the message won’t go away: however often you reprocess your document, LaTeX still tells you that “Label(s) may have changed”. This can sometimes be caused by a broken package: both <i>footmisc</i> (with the <code>perpage</code> option) and <i>hyperref</i> have been known to give trouble, in the past: if you are using either, check you have the latest version, and upgrade if possible. -<p>However, there <em>is</em> a rare occasion when this error can happen +<p/>However, there <em>is</em> a rare occasion when this error can happen as a result of pathological structure of the document itself. Suppose you have pages numbered in roman, and you add a reference to a label on page “ix” (9). The presence of the reference pushes the thing referred to onto page “x” (10), but since that’s a shorter reference the label moves back to page “ix” at the next run. Such a sequence can obviously not terminate. -<p>The only solution to this problem is to make a small change to your +<p/>The only solution to this problem is to make a small change to your document (something as small as adding or deleting a comma will often be enough). <dl> <dt><tt><i>footmisc.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.zip">macros/latex/contrib/footmisc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/footmisc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/footmisc/">browse</a>) <dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=rerun">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=rerun</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=rerun">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=rerun</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-resolns.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-resolns.html index 53bfda94754..f4e5bcebd24 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-resolns.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-resolns.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label resolns</title> </head><body> <h3>What are “resolutions”</h3> -<p>“Resolution” is a word that is used with little concern for its +<p/>“Resolution” is a word that is used with little concern for its multiple meanings, in computer equipment marketing. The word suggests a measure of what an observer (perhaps the human eye) can resolve; yet we regularly see advertisements for printers whose resolution is @@ -11,7 +11,7 @@ advertisements are talking about the precision with which the printer can place spots on the printed image, which affects the fineness of the representation of fonts, and the accuracy of the placement of glyphs and other marks on the page. -<p>In fact, there are two sorts of “resolution” on the printed page +<p/>In fact, there are two sorts of “resolution” on the printed page that we need to consider for (La)TeX’s purposes: <ul> <li> the positioning accuracy, and @@ -21,34 +21,31 @@ In the case where (La)TeX output is being sent direct to a printer, in the printer’s “native” language, it’s plain that the DVI processor must know all such details, and must take detailed account of both types of resolution. -<p>In the case where output is being sent to an intermediate distribution +<p/>In the case where output is being sent to an intermediate distribution format, that has potential for printing (or displaying) we know not where, the final translator, that connects to directly to the printer or display, has the knowledge of the device’s properties: the DVI processor need not know, and should not presume to guess. -<p>Both PostScript and PDF output are in this category. While PostScript is +<p/>Both PostScript and PDF output are in this category. While PostScript is used less frequently for document distribution nowadays, it is regularly used as the source for distillation into PDF; and PDF is the workhorse of an enormous explosion of document distribution. -<p>Therefore, we need DVI processors that will produce +<p/>Therefore, we need DVI processors that will produce “resolution independent” PostScript or PDF output; of course, the independence needs to extend to both forms of independence outlined above. -<p>Resolution-independence of fonts is forced upon the world by the -feebleness of Adobe’s <i>Acrobat</i> <i>Reader</i> at dealing -with bitmap files: a sequence of answers starting with one aiming at -the <a href="FAQ-dvips-pdf.html">quality of PDF from PostScript</a> addresses +<p/>Resolution-independence of fonts was for a long time forced upon the +world by the feebleness of Adobe’s <i>Acrobat</i> +<i>Reader</i> at dealing with bitmap files: a sequence of answers +starting with one aiming at the +<a href="FAQ-dvips-pdf.html">quality of PDF from PostScript</a> addresses the problems that arise. -<p>Resolution-independence of positioning is more troublesome: +<p/>Resolution-independence of positioning is more troublesome: <i>dvips</i> is somewhat notorious for insisting on positioning to the accuracy of the declared resolution of the printer. - - - -One -commonly-used approach is to declare a resolution of 8000 (“better +One commonly-used approach is to declare a resolution of 8000 (“better than any device”), and this is reasonably successful though it does have its <a href="FAQ-8000.html">problems</a>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=resolns">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=resolns</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=resolns">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=resolns</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reuseq.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reuseq.html index 712d948ef0b..67f62f82ec1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reuseq.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-reuseq.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label reuseq</title> </head><body> <h3>Re-using an equation</h3> -<p>To repeat an existing equation, one wants not only to have the same +<p/>To repeat an existing equation, one wants not only to have the same mathematics in it, one also wants to re-use the original label it had. The <i>amsmath</i> package comes to our help, here: <blockquote> @@ -24,7 +24,7 @@ Remember that Here, the second instance of a=b will be typeset with a copy, made by the <code>\</code><code>tag</code> command, of the label of the first instance. -<p>Comprehensive documentation of AMSLaTeX is to be found in +<p/>Comprehensive documentation of AMSLaTeX is to be found in <i>amsldoc</i>, in the distribution; it is also available on the web at <a href="ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf">ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf</a> <dl> @@ -33,5 +33,5 @@ at <a href="ftp://ftp.ams.org/pub/tex/doc/amsmath/amsldoc.pdf">ftp://ftp.ams.org <dt><tt><i>amsmath.sty</i></tt><dd>Distributed as part of AMSLaTeX <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.zip">macros/latex/required/amslatex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/amslatex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/amslatex/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=reuseq">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=reuseq</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=reuseq">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=reuseq</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rulethk.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rulethk.html index 625afa7d991..2f56abae1b7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rulethk.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-rulethk.html @@ -2,22 +2,22 @@ <title>UK TeX FAQ -- question label rulethk</title> </head><body> <h3>The thickness of rules in LaTeX tables</h3> -<p>The rules in a LaTeX table are by default <code>0.4pt</code> thick; +<p/>The rules in a LaTeX table are by default <code>0.4pt</code> thick; this is in fact a default built in at the lowest level, and applies to all rules (including those separating blocks of running text). -<p>Sometimes, however, we look at a table and find we want the rules to +<p/>Sometimes, however, we look at a table and find we want the rules to stand out — perhaps to separate the text from the rest of the body text, or to make the sections of the table stand out from one another. However, a quick review of any LaTeX manual will reveal no technique for making any one rule stand out, and a little experimentation shows that it is indeed pretty difficult to prevent a change “bleeding” out to affect other rules in the same table. -<p>If you look at what we have to say on the +<p/>If you look at what we have to say on the <a href="FAQ-destable.html">design of tables</a>, elsewhere among these FAQs, and you may sense that the design of LaTeX simply skipped the issues surrounding table design: <em>that’s</em> presumably why there’s no facilities to help you. -<p>Specifically, the length <code>\</code><code>arrayrulewidth</code> affects the thickness of +<p/>Specifically, the length <code>\</code><code>arrayrulewidth</code> affects the thickness of the rules (both horizontal and vertical) within both <code>tabular</code> and <code>array</code> environments. If you change from the default (see above) only as far as @@ -30,14 +30,14 @@ the change is remarkably striking. However, really quite subtle user level programming proves incapable of changing just <em>one</em> rule: it’s necessary to delve into the (rather tricky) code of <code>\</code><code>hline</code> and <code>\</code><code>cline</code> themselves. -<p>Fortunately, this job has already been done for the community: the +<p/>Fortunately, this job has already been done for the community: the <i>booktabs</i> package defines three different classes of rule (<code>\</code><code>toprule</code>, <code>\</code><code>midrule</code> and <code>\</code><code>bottomrule</code>), and the package documentation offers hints on how to use them. You are <em>strongly</em> advised to read the documentation pretty carefully. -<p>The <i>memoir</i> class includes the <i>booktabs</i> package, and +<p/>The <i>memoir</i> class includes the <i>booktabs</i> package, and repeats the documentation in its compendious manual. -<p>Note that none of the above mentions the issue of the weight of +<p/>Note that none of the above mentions the issue of the weight of vertical rules (except in passing). For the reasons, see the documentation of the <i>booktabs</i> package (again); vertical rules in tables are in any case even more trickily coded than are @@ -48,5 +48,5 @@ document. <dt><tt><i>booktabs.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/booktabs.zip">macros/latex/contrib/booktabs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/booktabs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/booktabs/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=rulethk">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=rulethk</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=rulethk">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=rulethk</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-run-fn-nos.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-run-fn-nos.html new file mode 100644 index 00000000000..452c465d1d5 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-run-fn-nos.html @@ -0,0 +1,25 @@ +<head> +<title>UK TeX FAQ -- question label run-fn-nos</title> +</head><body> +<h3>Not resetting footnote numbers per chapter</h3> +<p/>Some classes (for example, <i>book</i> and <i>report</i>) set up a +different set of footnotes per chapter, by resetting the footnote +number at the start of the chapter. This is essentially the same +action as that of +<a href="FAQ-running-nos.html">equation, figure and table numbers</a>, +except that footnote numbers don’t get “decorated” with the chapter +number, as happens with those other numbers. +<p/>The solution is the same: use the <i>chngcntr</i> package; since the +numbers aren’t “decorated” you can use the <code>\</code><code>counterwithout*</code> +variant; the code: +<blockquote> +<pre> +\counterwithout*{footnote}{chapter} +</pre> +</blockquote><p> +is all you need +<dl> +<dt><tt><i>chngcntr.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/chngcntr.sty">macros/latex/contrib/misc/chngcntr.sty</a> +</dl> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=run-fn-nos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=run-fn-nos</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-runheadtoobig.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-runheadtoobig.html index fcd240d77bb..dd45e61d98b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-runheadtoobig.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-runheadtoobig.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label runheadtoobig</title> </head><body> <h3>My section title is too wide for the page header</h3> -<p>By default, LaTeX sectioning commands make the chapter or section +<p/>By default, LaTeX sectioning commands make the chapter or section title available for use by page headers and the like. Page headers operate in a rather constrained area, and it’s common for titles too be too big to fit: the LaTeX sectioning commands therefore take an @@ -16,19 +16,19 @@ If the <<i>short title</i>> is present, it is used both for the table of contents and for the page heading. The usual answer to people who complain that their title is too big for the running head is to suggest that they the optional argument. -<p>However, using the same text for the table of contents as for the +<p/>However, using the same text for the table of contents as for the running head may also be unsatisfactory: if your chapter titles are seriously long (like those of a Victorian novel), a valid and rational scheme is to have a shortened table of contents entry, and a really terse entry in the running head. -<p>One of the problems is the tendency of page headings to be set in +<p/>One of the problems is the tendency of page headings to be set in capitals (which take up more space); so why not set headings as written for “ordinary” reading? It’s not possible to do so with unmodified LaTeX, but the <i>fancyhdr</i> package provides a command <code>\</code><code>nouppercase</code> for use in its header (and footer) lines to suppress LaTeX’s uppercasing tendencies. Classes in the <i>KOMA-script</i> bundle don’t uppercase in the first place. -<p>In fact, the sectioning commands use ‘mark’ commands to pass +<p/>In fact, the sectioning commands use ‘mark’ commands to pass information to the page headers. For example, <code>\</code><code>chapter</code> uses <code>\</code><code>chaptermark</code>, <code>\</code><code>section</code> uses <code>\</code><code>sectionmark</code>, and so on. With this knowledge, one can achieve a three-layer structure for chapters: @@ -39,7 +39,7 @@ this knowledge, one can achieve a three-layer structure for chapters: </pre> </blockquote><p> which should supply the needs of every taste. -<p>Chapters, however, have it easy: hardly any book design puts a page +<p/>Chapters, however, have it easy: hardly any book design puts a page header on a chapter start page. In the case of sections, one has typically to take account of the nature of the <code>\</code><code>*mark</code> commands: the thing that goes in the heading is the first mark on the page (or, @@ -57,13 +57,13 @@ the recipe for sections is more tiresome: pages; note that here, you need the optional argument to <code>\</code><code>section</code>, even if “<em>middling version</em>” is in fact the same text as “<em>long version”</em>.) -<p>A similar arrangement is necessary even for chapters if the class +<p/>A similar arrangement is necessary even for chapters if the class you’re using is odd enough that it puts a page header on a chapter’s opening page. -<p>Note that the <i>titlesec</i> package manages the running heads in +<p/>Note that the <i>titlesec</i> package manages the running heads in a completely different fashion; users of that package should refer to the documentation. -<p>The <i>memoir</i> class avoids all the silliness by providing an +<p/>The <i>memoir</i> class avoids all the silliness by providing an extra optional argument for chapter and sectioning commands, for example: <blockquote> @@ -80,6 +80,6 @@ tailor the header text to fit, with very little trouble. <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>titlesec.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titlesec.zip">macros/latex/contrib/titlesec</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titlesec.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/titlesec/">browse</a>) </dl> -<p> +<p/> <p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=runheadtoobig">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=runheadtoobig</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-running-nos.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-running-nos.html index 1a47dabf32b..35460003b8b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-running-nos.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-running-nos.html @@ -2,12 +2,36 @@ <title>UK TeX FAQ -- question label running-nos</title> </head><body> <h3>Running equation, figure and table numbering</h3> -<p>Many LaTeX classes (including the standard <i>book</i> class) +<p/>Many LaTeX classes (including the standard <i>book</i> class) number things per chapter; so figures in chapter 1 are numbered 1.1, 1.2, and so on. Sometimes this is not appropriate for the user’s needs. -<p>Short of rewriting the whole class, one may use one of the -<i>removefr</i> and <i>remreset</i> packages; both define a +<p/>Short of rewriting the whole class, one may use the <i>chngctr</i> +package, which provides commands <code>\</code><code>counterwithin</code> (which +establishes this nested numbering relationship) and +<code>\</code><code>counterwithout</code> (which undoes it). +<p/>So if you have figures numbered by chapter as 1.1, 1.2, 2.1, ..., +the command +<blockquote> +<pre> +\counterwithout{figure}{chapter} +</pre> +</blockquote><p> +will convert them to figures 1, 2, 3, .... (Note that the command +has also removed the chapter number from the counter’s definition.) +<p/>More elaborate use could change things numbered per section to things +numbered per chapter: +<blockquote> +<pre> +\counterwithout{equation}{section} +\counterwithin{equation}{chapter} +</pre> +</blockquote><p> +(assuming there was a class that did such a thing in the first place...) +<p/>The <i>chngcntr</i> approach doesn’t involve much programming, and +the enthusiastic LaTeX programmer might choose to try the technique +that we had to use before the advent of <i>chngcntr</i>. Each of +the packages <i>removefr</i> and <i>remreset</i> defines a <code>\</code><code>@removefromreset</code> command, and having included the package one writes something like: <blockquote> @@ -28,7 +52,7 @@ way in which the figure number (in this case) is printed: </blockquote><p> (remember to do the whole job, for every counter you want to manipulate, within <code>\</code><code>makeatletter</code> ... <code>\</code><code>makeatother</code>). -<p>The technique may also be used to change where in a multilevel +<p/>This technique, too, may be used to change where in a multilevel structure a counter is reset. Suppose your class numbers figures as <<i>chapter</i>>.<<i>section</i>>.<<i>figure</i>>, and you want figures numbered per chapter, try: @@ -43,10 +67,6 @@ numbered per chapter, try: </blockquote><p> (the command <code>\</code><code>@addtoreset</code> is a part of LaTeX itself). -<p>The <i>chngcntr</i> package provides a simple means to access the -two sorts of changes discussed, defining <code>\</code><code>counterwithin</code> and -<code>\</code><code>counterwithout</code> commands; the <i>memoir</i> class also provides -these functions. <dl> <dt><tt><i>chngcntr.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/chngcntr.sty">macros/latex/contrib/misc/chngcntr.sty</a> <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) @@ -55,5 +75,5 @@ these functions. <code>\</code><code>input{removefr}</code>) <dt><tt><i>remreset.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.zip">macros/latex/contrib/carlisle</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/carlisle.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/carlisle/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=running-nos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=running-nos</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=running-nos">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=running-nos</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-scriptfonts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-scriptfonts.html index 255a34df42d..f0b21c4a397 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-scriptfonts.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-scriptfonts.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label scriptfonts</title> </head><body> <h3>Better script fonts for maths</h3> -<p>The font selected by <code>\</code><code>mathcal</code> is the only script font ‘built +<p/>The font selected by <code>\</code><code>mathcal</code> is the only script font ‘built in’. However, there are other useful calligraphic fonts included with modern TeX distributions. <dl> @@ -10,13 +10,13 @@ modern TeX distributions. distributions; the fonts are part of the AMS font set) gives a slightly curlier font than the default. The package changes the font that is selected by <code>\</code><code>mathcal</code>. -<p> Type 1 versions of the fonts are available in the AMS fonts +<p/> Type 1 versions of the fonts are available in the AMS fonts distribution. <dt>RSFS<dd> The <i>mathrsfs</i> package uses a really fancy script font (the name stands for “Ralph Smith’s Formal Script”) which is already part of most modern TeX distributions. The package creates a new command <code>\</code><code>mathscr</code>. -<p> Type 1 versions of the font have been made available by Taco +<p/> Type 1 versions of the font have been made available by Taco Hoekwater. <dt>Zapf Chancery<dd> is the standard PostScript calligraphic font. There is no package but you can easily make it available by means of the @@ -34,7 +34,7 @@ modern TeX distributions. \DeclareMathAlphabet{\mathscr}{OT1}{pzc}% {m}{it} </pre> -<p> Adobe Zapf Chancery (which the above examples use) is distributed in +<p/> Adobe Zapf Chancery (which the above examples use) is distributed in any but the most basic PostScript printers. A substantially identical font (to the extent that the same metrics may be used) is available from URW and is distributed with @@ -45,11 +45,11 @@ Examples of the available styles are available on CTAN. <dt><tt><i>eucal.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/latex/eucal.sty">fonts/amsfonts/latex/eucal.sty</a> <dt><tt><i>euler fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/sources/euler.zip">fonts/amsfonts/sources/euler</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/amsfonts/sources/euler.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/sources/euler/">browse</a>) <dt><tt><i>euler fonts, in Type 1 format</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/ps-type1/">fonts/amsfonts/ps-type1/</a> -<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/ghostscript/">nonfree/support/ghostscript/</a> +<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/">support/ghostscript/</a> <dt><tt><i>mathrsfs.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/jknappen.zip">macros/latex/contrib/jknappen</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/jknappen.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/jknappen/">browse</a>) <dt><tt><i>rsfs fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/rsfs.zip">fonts/rsfs</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/rsfs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/rsfs/">browse</a>) <dt><tt><i>rsfs fonts, in Type 1 format</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/rsfs/ps-type1/hoekwater.zip">fonts/rsfs/ps-type1/hoekwater</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/rsfs/ps-type1/hoekwater.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/rsfs/ps-type1/hoekwater/">browse</a>) <dt><tt><i>Script font examples</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/symbols/math/scriptfonts.pdf">info/symbols/math/scriptfonts.pdf</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=scriptfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=scriptfonts</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=scriptfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=scriptfonts</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-seccntfmt.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-seccntfmt.html index 53143de4145..76dcaabad19 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-seccntfmt.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-seccntfmt.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label seccntfmt</title> </head><body> <h3>Adjusting the presentation of section numbers</h3> -<p>The general issues of adjusting the appearance of section headings are +<p/>The general issues of adjusting the appearance of section headings are pretty complex, and are covered in the question on <a href="FAQ-secthead.html">the style of section headings</a>. -<p>However, people regularly want merely to change the way the section +<p/>However, people regularly want merely to change the way the section number appears in the heading, and some such people don’t mind writing out a few macros. This answer is for <em>them</em>. -<p>The section number is typeset using the +<p/>The section number is typeset using the <a href="FAQ-atsigns.html">LaTeX internal</a> <code>\</code><code>@seccntformat</code> command, which is given the “name” (section, @@ -26,7 +26,7 @@ simple modification of the command: } </pre> </blockquote><p> -<p>Many people (for some reason) want a stop after a section number, but +<p/>Many people (for some reason) want a stop after a section number, but not after a subsection number, or any of the others. To do this, one must make <code>\</code><code>@seccntformat</code> switch according to its argument. The following technique for doing the job is slightly @@ -60,12 +60,12 @@ definition as the original “all levels alike” version: Note that all the command definitions of this answer are dealing in <a href="FAQ-atsigns.html">LaTeX internal commands</a>, so the above code should be in a package file, for preference. -<p>The <i>Koma-script</i> classes have different commands for specifying +<p/>The <i>Koma-script</i> classes have different commands for specifying changes to section number presentation: <code>\</code><code>partformat</code>, <code>\</code><code>chapterformat</code> and <code>\</code><code>othersectionlevelsformat</code>, but otherwise their facilities are similar to those of “raw” LaTeX. <dl> <dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=seccntfmt">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=seccntfmt</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=seccntfmt">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=seccntfmt</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secindent.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secindent.html index ef165878a7f..ae503fd40c2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secindent.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secindent.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label secindent</title> </head><body> <h3>Indent after section headings</h3> -<p>LaTeX implements a style that doesn’t indent the first paragraph +<p/>LaTeX implements a style that doesn’t indent the first paragraph after a section heading. There are coherent reasons for this, but not everyone likes it. The <i>indentfirst</i> package @@ -11,5 +11,5 @@ indented. <dl> <dt><tt><i>indentfirst.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secindent">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secindent</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secindent">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secindent</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secnumdep.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secnumdep.html index f3ac98d273b..e45ad2c9e51 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secnumdep.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secnumdep.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label secnumdep</title> </head><body> <h3>Unnumbered sections in the Table of Contents</h3> -<p>The way the relevant parts of sectioning commands work is exemplified +<p/>The way the relevant parts of sectioning commands work is exemplified by the way the <code>\</code><code>chapter</code> command uses the counter <code>secnumdepth</code> (described in Appendix C of the LaTeX manual): <ol> @@ -16,7 +16,7 @@ by the way the <code>\</code><code>chapter</code> command uses the counter <code </ol> Other sectioning commands are similar, but with other values used in the test. -<p>So a simple way to get headings of funny ‘sections’ such as prefaces +<p/>So a simple way to get headings of funny ‘sections’ such as prefaces in the table of contents is to use the counter: <blockquote> <pre> @@ -27,9 +27,9 @@ in the table of contents is to use the counter: Unfortunately, you have to set <code>secnumdepth</code> back to its usual value (which is 2 in the standard styles) before you do any ‘section’ which you want to be numbered. -<p>Similar settings are made, automatically, in the LaTeX book class by +<p/>Similar settings are made, automatically, in the LaTeX book class by the <code>\</code><code>frontmatter</code> and <code>\</code><code>backmatter</code> commands. -<p>The value of the counter <code>tocdepth</code> controls which headings +<p/>The value of the counter <code>tocdepth</code> controls which headings will be finally printed in the table of contents. This normally has to be set in the preamble and is a constant for the document. The package <i>tocvsec2</i> package provides a convenient interface to @@ -37,13 +37,13 @@ allow you to change the <code>secnumdepth</code> and/or the <code>tocdepth</code> counter values at any point in the body of the document; this provides convenient independent controls over the sectional numbering and the table of contents. -<p>The package <i>abstract</i> (see +<p/>The package <i>abstract</i> (see <a href="FAQ-onecolabs.html">one-column abstracts</a>) includes an option to add the <code>abstract</code> to the table of contents, while the package <i>tocbibind</i> has options to include the table of contents itself, the <code>bibliography</code>, <code>index</code>, etc., to the table of contents. -<p>The <i>KOMA-Script</i> classes have commands <code>\</code><code>addchap</code> and +<p/>The <i>KOMA-Script</i> classes have commands <code>\</code><code>addchap</code> and <code>\</code><code>addsec</code>, which work like <code>\</code><code>chapter</code> and <code>\</code><code>section</code> but aren’t numbered. The <i>memoir</i> class incorporates the facilities of all three of the <i>abstract</i>, <i>tocbibind</i> and @@ -55,5 +55,5 @@ of all three of the <i>abstract</i>, <i>tocbibind</i> and <dt><tt><i>tocbibind.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocbibind.zip">macros/latex/contrib/tocbibind</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocbibind.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tocbibind/">browse</a>) <dt><tt><i>tocvsec2.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocvsec2.zip">macros/latex/contrib/tocvsec2</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocvsec2.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tocvsec2/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secnumdep">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secnumdep</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secnumdep">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secnumdep</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secthead.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secthead.html index bbf44221cc7..738c87c0158 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secthead.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-secthead.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label secthead</title> </head><body> <h3>The style of section headings</h3> -<p>Suppose that the editor of your favourite journal has specified that section +<p/>Suppose that the editor of your favourite journal has specified that section headings must be centred, in small capitals, and subsection headings ragged right in italic, but that you don’t want to get involved in the sort of programming described in section 2.2 of <em>The LaTeX Companion</em> @@ -24,37 +24,37 @@ probably satisfy your editor. Define yourself new commands and then use <code>\</code><code>ssection</code> and <code>\</code><code>ssubsection</code> in place of <code>\</code><code>section</code> and <code>\</code><code>subsection</code>. This isn’t perfect: section numbers remain in bold, and starred forms need a separate redefinition. -<p>The <i>titlesec</i> package offers a structured approach to the +<p/>The <i>titlesec</i> package offers a structured approach to the problem, based on redefinition of the sectioning and chapter commands themselves. This approach allows it to offer radical adjustment: its options provide (in effect) a toolbox for designing your own sectioning commands’ output. -<p>The <i>sectsty</i> package provides a more simply structured set of +<p/>The <i>sectsty</i> package provides a more simply structured set of tools; while it is less powerful than is <i>titlesec</i>, it is perhaps preferable for minor adjustments, since you can use it after having read a smaller proportion of the manual. -<p>The <i>fncychap</i> package provides a nice collection of customised +<p/>The <i>fncychap</i> package provides a nice collection of customised chapter heading designs. The <i>anonchap</i> package provides a simple means of typesetting chapter headings “like section headings” (i.e., without the “Chapter” part of the heading); the <i>tocbibind</i> package provides the same commands, in pursuit of another end. Unfortunately, <i>fncychap</i> is not attuned to the existence of front- and backmatter in <i>book</i> class documents. -<p>The <i>memoir</i> class includes facilities that match +<p/>The <i>memoir</i> class includes facilities that match <i>sectsty</i> and <i>titlesec</i>, as well as a bundle of chapter heading styles (including an <i>anonchap</i>-equivalent). The <i>KOMA-script</i> classes also have sets of tools that provide equivalent functionality, notably formatting specifications <code>\</code><code>partformat</code>, <code>\</code><code>chapterformat</code>, <code>\</code><code>sectionformat</code>, ..., as well as several useful overall formatting specifications defined in class options. -<p>Finally, the indefatigable Vincent Zoonekynd supplies examples of how +<p/>Finally, the indefatigable Vincent Zoonekynd supplies examples of how to program alternative <a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_chapter/0.html">chapter heading styles</a> and <a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_section/0.html">section heading styles</a>. The web pages are not useful to users unless they are willing to do their own LaTeX programming. -<p>The documentation of <i>fncychap</i> is distributed as a separate +<p/>The documentation of <i>fncychap</i> is distributed as a separate PostScript file. <dl> <dt><tt><i>anonchap.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/anonchap.sty">macros/latex/contrib/misc/anonchap.sty</a> @@ -65,5 +65,5 @@ PostScript file. <dt><tt><i>titlesec.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titlesec.zip">macros/latex/contrib/titlesec</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titlesec.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/titlesec/">browse</a>) <dt><tt><i>tocbibind.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocbibind.zip">macros/latex/contrib/tocbibind</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocbibind.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tocbibind/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secthead">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secthead</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secthead">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=secthead</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-semanticnest.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-semanticnest.html index 63eb90037d0..13c48eee5fd 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-semanticnest.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-semanticnest.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label semanticnest</title> </head><body> <h3>Capacity exceeded [semantic nest ...]</h3> -<p> +<p/> <pre> ! TeX capacity exceeded, sorry [semantic nest size=100]. ... @@ -12,7 +12,7 @@ you can ask a wizard to enlarge me. Even though TeX suggests (as always) that enlargement by a wizard may help, this message usually results from a broken macro or bad parameters to an otherwise working macro. -<p>The “semantic nest” TeX talks about is the nesting +<p/>The “semantic nest” TeX talks about is the nesting of boxes within boxes. A stupid macro can provoke the error pretty easily: <blockquote> @@ -40,10 +40,10 @@ The repeated lines are broken at exactly the offending macro; of course the loop need not be as simple as this — if <code>\</code><code>silly</code> calls <code>\</code><code>dopy</code> which boxes <code>\</code><code>silly</code>, the effect is just the same and alternate lines in the traceback are broken at alternate positions. -<p>There are in fact two items being consumed when you nest boxes: the +<p/>There are in fact two items being consumed when you nest boxes: the other is the grouping level. Whether you exhaust your <em>semantic nest</em> or your permitted <em>grouping levels</em> first is controlled entirely by the relative size of the two different sets of buffers in your (La)TeX executable. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=semanticnest">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=semanticnest</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=semanticnest">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=semanticnest</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-setURL.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-setURL.html index 7102c270cc1..3314113ce97 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-setURL.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-setURL.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label setURL</title> </head><body> <h3>Typesetting URLs</h3> -<p>URLs tend to be very long, and contain characters that would +<p/>URLs tend to be very long, and contain characters that would naturally prevent them being hyphenated even if they weren’t typically set in <code>\</code><code>ttfamily</code>, verbatim. Therefore, without special treatment, they often produce wildly overfull <code>\</code><code>hbox</code>es, and their typeset representation is awful. -<p>There are three packages that help solve this problem: +<p/>There are three packages that help solve this problem: <ul> <li> The <i>path</i> package, which defines a <code>\</code><code>path</code> command. The command defines each potential break character as a @@ -16,7 +16,7 @@ representation is awful. disadvantage is fragility in LaTeX moving arguments. The <a href="FAQ-eplain.html">Eplain macros</a> — define a similar <code>\</code><code>path</code> command. -<p> <i>Path</i>, though it works in simple situations, makes no +<p/> <i>Path</i>, though it works in simple situations, makes no attempt to work with LaTeX (it is irremediably fragile). Despite its long and honourable history, it is no longer recommended for LaTeX use. @@ -30,7 +30,7 @@ representation is awful. within moving arguments. Note that, because the operation is conducted in maths mode, spaces within the URL argument are ignored unless special steps are taken. -<p> It is possible to use the <i>url</i> package in Plain TeX, +<p/> It is possible to use the <i>url</i> package in Plain TeX, with the assistance of the <i>miniltx</i> package (which was originally developed for using the LaTeX graphics package in Plain TeX). A small patch is also necessary: the required @@ -45,19 +45,29 @@ representation is awful. of <i>url</i>, in a context where the typeset text forms the anchor of a link. </ul> -<p>The author of this answer prefers the (rather newer) <i>url</i> +<p/>The author of this answer prefers the (rather newer) <i>url</i> package (directly or indirectly); both <i>path</i> and <i>url</i> work well with Plain TeX (though of course, the fancy LaTeX facilities of <i>url</i> don’t have much place there). (<i>hyperref</i> isn’t available in a version for use with Plain TeX.) -<p>Documentation of both <i>path</i> and <i>url</i> is in the -package files. +<p/>Note that neither <code>\</code><code>path</code> (from package <i>path</i>) nor <code>\</code><code>url</code> (from +package <i>url</i>) is robust (in the LaTeX sense). If you need +a URL to go in a moving argument, you need the command +<code>\</code><code>urldef</code> from the <i>url</i> package. So one might write: +<blockquote> +<pre> +\urldef\faqhome\url{http://www.tex.ac.uk/faq} +</pre> +</blockquote><p> +after which, <code>\</code><code>faqhome</code> is robust. +<p/>Documentation of both package <i>path</i> and package <i>url</i> +is in the package files. <dl> <dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>) <dt><tt><i>miniltx.tex</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/plain/graphics.zip">macros/plain/graphics</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/graphics.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/graphics/">browse</a>) <dt><tt><i>path.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/path.sty">macros/latex/contrib/misc/path.sty</a> <dt><tt><i>url.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/url.sty">macros/latex/contrib/misc/url.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=setURL">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=setURL</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=setURL">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=setURL</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slashbox.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slashbox.html index 543e20a95dc..763d9b4eb2c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slashbox.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slashbox.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label slashbox</title> </head><body> <h3>Diagonal separation in corner cells of tables</h3> -<p>You want to label both the top or bottom row and the left- or +<p/>You want to label both the top or bottom row and the left- or rightmost column, somewhere at the corner of the table where the row and column meet. A simple way to achieve the result is to construct the table with an arrangement of rules (and possibly <code>\</code><code>multicolumn</code> @@ -30,12 +30,12 @@ commands <code>\</code><code>slashbox</code> and <code>\</code><code>backslashbo labels as arguments. It draws a picture with the two labels on either side of a slanting line; the command (and hence the picture) may be placed in the corner cell, where the labelled row and column meet. -<p>The package isn’t the world’s neatest: it uses LaTeX +<p/>The package isn’t the world’s neatest: it uses LaTeX <code>picture</code> mode to draw its line, and picture mode has many tedious restrictions (and doesn’t, in all honesty, produce particularly good pictures). Load slashbox with the <i>pict2e</i> package, and at least the picture quality will be improved. -<p>Documentation of <i>slashbox</i> is less than satisfactory: a +<p/>Documentation of <i>slashbox</i> is less than satisfactory: a LaTeX source file of rather startling starkness accompanies the package file in the distribution. It does, however, process to a DVI file that gives some idea of how the <code>\</code><code>slashbox</code> may be @@ -47,5 +47,5 @@ regard.) <dl> <dt><tt><i>slashbox.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/slashbox.zip">macros/latex/contrib/slashbox</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/slashbox.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/slashbox/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=slashbox">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=slashbox</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=slashbox">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=slashbox</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slidecls.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slidecls.html index 111576c1c02..b4eb438aa6c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slidecls.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-slidecls.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label slidecls</title> </head><body> <h3>Producing slides</h3> -<p>Lamport’s original LaTeX had a separate program (SliTeX) for +<p/>Lamport’s original LaTeX had a separate program (SliTeX) for producing slides; it dates from the age when colour effects were produced by printing separate slides in different-coloured inks, and overlaying them, and was just about acceptable back then. When @@ -11,17 +11,17 @@ program went away, and its functionality was supplied by the <i>slides</i> class. While this makes life a little easier for system administrators, it does nothing for the inferior functionality of the class: no-one “who knows” uses <i>slides</i> nowadays. -<p>The ‘classic’ alternatives have been <i>seminar</i> and <i>foils</i> +<p/>The ‘classic’ alternatives have been <i>seminar</i> and <i>foils</i> (originally known as FoilTeX). Both were originally designed to produce output on acetate foils, though subsequent work has provided environments in which they can be used with screen projectors (see below). -<p>The advent of Microsoft <i>PowerPoint</i> (feeble though early +<p/>The advent of Microsoft <i>PowerPoint</i> (feeble though early versions of it were) has created a demand for “dynamic” slides — images that develop their content in a more elaborate fashion than by merely replacing one foil with the next in the way that was the norm when <i>slides</i>, <i>foils</i> and <i>seminar</i> were designed. -<p>The <i>prosper</i> class builds on <i>seminar</i> to provide dynamic +<p/>The <i>prosper</i> class builds on <i>seminar</i> to provide dynamic effects and the like; it retains the ability to provide PDF for a projected presentation, or to print foils for a foil-based presentation. The add-on package <i>ppr-prv</i> adds “preview” @@ -31,14 +31,14 @@ mends a few bugs, and adds several facilities and slide design styles. The (relatively new) <i>powerdot</i> class is designed as a replacement for <i>prosper</i> and <i>HA-prosper</i>, co-authored by the author of <i>HA-prosper</i>. -<p><i>Beamer</i> is a relatively easy-to-learn, yet powerful, class that +<p/><i>Beamer</i> is a relatively easy-to-learn, yet powerful, class that (as its name implies) was designed for use with projection displays. It needs the <i>pgf</i> package (for graphics support), which in turn requires <i>xcolor</i>; while this adds to the tedium of installing <i>beamer</i> “from scratch”, both are good additions to a modern LaTeX installation. <i>Beamer</i> has reasonable facilities for producing printed copies of slides. -<p><i>Talk</i> is another highly functional, yet easy-to-learn class +<p/><i>Talk</i> is another highly functional, yet easy-to-learn class which claims to differ from the systems mentioned above, such as <i>beamer</i>, in that it doesn’t impose a slide style on you. You get to specify a bunch of slide styles, and you can switch from one to @@ -46,26 +46,30 @@ the other between slides, as you need. (The class itself provides just the one style, in the package <i>greybars</i>: the author hopes users will contribute their own styles, based on <i>greybars</i>.) -<p><i>Ppower4</i> (commonly known as <i>pp4</i>) is a +<p/><i>Ppower4</i> (commonly known as <i>pp4</i>) is a <i>Java</i>-based support program that will postprocess PDF, to ‘animate’ the file at places you’ve marked with commands from one of the <i>pp4</i> packages. The commands don’t work on PDF that has come from <i>dvips</i> output; they work with PDF generated by PDFLaTeX, VTeX LaTeX, or <i>dvipdfm</i> running on LaTeX output. -<p><i>Pdfscreen</i> and <i>texpower</i> are add-on pakages that +<p/><i>Pdfscreen</i> and <i>texpower</i> are add-on pakages that permit dynamic effects in documents formatted in “more modest” classes; <i>pdfscreen</i> will even allow you to plug “presentation effects” into an <i>article</i>-class document. -<p> +<p/> -<p>A more detailed examination of the alternatives (including examples +<p/>A more detailed examination of the alternatives (including examples of code using many of them) may be found at Michael Wiedmann’s fine <a href="http://www.miwie.org/presentations/presentations.html">http://www.miwie.org/presentations/presentations.html</a> +<p/>ConTeXt users will find that much (if not all) of what they need is +already in ConTeXt itself; there’s a useful summary of what’s +available, with examples, in +<a href="http://wiki.contextgarden.net/Presentation_Styles">http://wiki.contextgarden.net/Presentation_Styles</a> <dl> <dt><tt><i>beamer.cls</i></tt><dd>Download all of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/beamer.zip">macros/latex/contrib/beamer</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/beamer.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/beamer/">browse</a>) -<dt><tt><i>foils.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/macros/latex/contrib/foiltex.zip">nonfree/macros/latex/contrib/foiltex</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/macros/latex/contrib/foiltex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/macros/latex/contrib/foiltex/">browse</a>) +<dt><tt><i>foils.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/foiltex.zip">macros/latex/contrib/foiltex</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/foiltex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/foiltex/">browse</a>) <dt><tt><i>greybars.sty</i></tt><dd>distributed with <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/talk.zip">macros/latex/contrib/talk</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/talk.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/talk/">browse</a>) <dt><tt><i>HA-prosper.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ha-prosper.zip">macros/latex/contrib/ha-prosper</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ha-prosper.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ha-prosper/">browse</a>) @@ -79,5 +83,5 @@ of code using many of them) may be found at Michael Wiedmann’s fine <dt><tt><i>texpower</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/texpower.zip">macros/latex/contrib/texpower</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/texpower.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/texpower/">browse</a>) <dt><tt><i>xcolor.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xcolor.zip">macros/latex/contrib/xcolor</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xcolor.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xcolor/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=slidecls">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=slidecls</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=slidecls">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=slidecls</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-sortbib.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-sortbib.html index 1619687feb0..f39dca0af3d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-sortbib.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-sortbib.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label sortbib</title> </head><body> <h3>Sorting lists of citations</h3> -<p>BibTeX has a sorting function, and most BibTeX styles sort the +<p/>BibTeX has a sorting function, and most BibTeX styles sort the citation list they produce; most people find this desirable. -<p>However, it is perfectly possible to write a +<p/>However, it is perfectly possible to write a <code>thebibliography</code> environment that <em>looks</em> as if it came from BibTeX, and many people do so (in order to save time in the short term). -<p>The problem arises when <code>thebibliography</code>-writers decide +<p/>The problem arises when <code>thebibliography</code>-writers decide their citations need to be sorted. A common misapprehension is to insert <code>\</code><code>bibliographystyle{alpha}</code> (or similar) and expect the typeset output to be sorted in some magical way. BibTeX @@ -16,5 +16,5 @@ doesn’t work that way! — if you write <code>thebibliography</code>, you get to sort its contents. BibTeX will only sort the contents of a <code>thebibliography</code> environment when it creates it, to be inserted from a <code>.bbl</code> file by a <code>\</code><code>bibliography</code> command. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=sortbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=sortbib</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=sortbib">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=sortbib</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spaftend.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spaftend.html index dd26d8d5880..d4f7d75150b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spaftend.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spaftend.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label spaftend</title> </head><body> <h3>There’s a space added after my environment</h3> -<p>You’ve written your own environment <code>env</code>, and it works +<p/>You’ve written your own environment <code>env</code>, and it works except that a space appears at the start of the first line of typeset text after <code>\</code><code>end{env}</code>. This doesn’t happen with similar LaTeX-supplied environments. -<p>You could impose the restriction that your users always put a +<p/>You could impose the restriction that your users always put a “<code>%</code>” sign after the environment ... but LaTeX environments don’t require that, either. -<p>The LaTeX environments’ “secret” is an internal flag which causes +<p/>The LaTeX environments’ “secret” is an internal flag which causes the unwanted spaces to be ignored. Fortunately, you don’t have to use the internal form: since 1996, LaTeX has had a user command <code>\</code><code>ignorespacesafterend</code>, which sets the internal flag. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spaftend">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spaftend</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spaftend">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spaftend</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-specials.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-specials.html index 37cdc5c574f..bc6435d4918 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-specials.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-specials.html @@ -2,26 +2,34 @@ <title>UK TeX FAQ -- question label specials</title> </head><body> <h3><code>\</code><code>special</code> commands</h3> -<p>TeX provides the means to express things that device drivers can +<p/>TeX provides the means to express things that device drivers can do, but about which TeX itself knows nothing. For example, TeX itself knows nothing about how to include PostScript figures into documents, or how to set the colour of printed text; but some device drivers do. -<p>Such things are introduced to your document by means of <code>\</code><code>special</code> -commands; all that TeX does with these commands is to expand their +<p/>Instructions for such things are introduced to your document by means +of <code>\</code><code>special</code> commands; all that TeX does with these commands is +to expand their arguments and then pass the command to the DVI file. In most cases, there are macro packages provided (often with the driver) that -provide a comprehensible interface to the <code>\</code><code>special</code>; for example, +provide a human-friendly interface to the <code>\</code><code>special</code>; for example, there’s little point including a figure if you leave no gap for it in your text, and changing colour proves to be a particularly fraught -operation that requires real wizardry. LaTeX2e +operation that requires real wizardry. LaTeX2e has standard graphics and colour packages that make figure inclusion, -rotation and scaling, and colour typesetting via <code>\</code><code>special</code>s all easy. -<p>The allowable arguments of <code>\</code><code>special</code> depend on the device driver +rotation and scaling, and colour typesetting relatively +straightforward, despite the rather daunting <code>\</code><code>special</code> commands +involved. (ConTeXt provides similar support, though not by way of +packages.) +<p/>The allowable arguments of <code>\</code><code>special</code> depend on the device driver you’re using. Apart from the examples above, there are <code>\</code><code>special</code> commands in the emTeX drivers (e.g., <i>dvihplj</i>, <i>dviscr</i>, <em>etc</em>.) that will draw lines at arbitrary orientations, and commands in <i>dvitoln03</i> that permit the page to be set in landscape orientation. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=specials">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=specials</a> +<p/>Note that <code>\</code><code>special</code> provides rather different facilities in PDFTeX +operation: since there is no device driver around, in this context. +In PDFTeX, <code>\</code><code>special</code> is only needed to generated PDF for +which there is no existing defined PDFTeX operation. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=specials">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=specials</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spell.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spell.html index 49fb51a7c8f..9bea493d68c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spell.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spell.html @@ -2,22 +2,22 @@ <title>UK TeX FAQ -- question label spell</title> </head><body> <h3>Spelling checkers for work with TeX</h3> -<p>For Unix, <i>ispell</i> has long the program of choice; it is well +<p/>For Unix, <i>ispell</i> was long the program of choice; it is well integrated with <i>emacs</i>, and deals with some TeX syntax. -However, it is increasingly challenged by <i>aspell</i>, which was -designed as a successor, and certainly performs better on most -metrics; there remains some question as to its performance with -(La)TeX sources. -<p>For Windows, there is a good spell checker incorporated into many of +However, it has more-or-less been replaced everywhere, by +<i>aspell</i>, which was designed as a successor, and certainly +performs better on most metrics; there remains some question as to its +performance with (La)TeX sources. +<p/>For Windows, there is a good spell checker incorporated into many of the <a href="FAQ-editors.html">shell/editor</a> combinations that are available. The spell checker from the (now defunct) 4AllTeX shell remains available as a separate package, <i>4spell</i>. -<p>For the Macintosh, <i>Excalibur</i> is the program of choice. It +<p/>For the Macintosh, <i>Excalibur</i> is the program of choice. It will run in native mode on both sorts of Macintosh. The distribution comes with dictionaries for several languages. -<p>The VMS Pascal program <i>spell</i> makes special cases of +<p/>The VMS Pascal program <i>spell</i> makes special cases of some important features of LaTeX syntax. -<p>For MSDOS, there are several programs. <i>Amspell</i> can be +<p/>For MSDOS, there are several programs. <i>Amspell</i> can be called from within an editor, and <i>jspell</i> is an extended version of <i>ispell</i>. <dl> @@ -32,5 +32,5 @@ version of <i>ispell</i>. <a href="ftp://cam.ctan.org/tex-archive/support/vmspell.zip">support/vmspell</a> (<a href="ftp://cam.ctan.org/tex-archive/support/vmspell.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/vmspell/">browse</a>) <dt><tt><i>winedt</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/win32/winedt/winedt32.exe">systems/win32/winedt/winedt32.exe</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spell">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spell</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spell">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spell</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spinmacro.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spinmacro.html index 1f75263bada..9dc949a38a4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spinmacro.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-spinmacro.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label spinmacro</title> </head><body> <h3>Spaces in macros</h3> -<p>It’s very easy to write macros that produce space in the typeset +<p/>It’s very easy to write macros that produce space in the typeset output where it’s neither desired nor expected. Spaces introduced by macros are particularly insidious because they don’t amalgamate with spaces around the macro (unlike consecutive spaces that you @@ -10,14 +10,14 @@ type), so your output can have a single bloated space that proves to be made up of two or even more spaces that haven’t amalgamated. And of course, your output can also have a space where none was wanted at all. -<p>Spaces are produced, inside a macro as elsewhere, by space or tab +<p/>Spaces are produced, inside a macro as elsewhere, by space or tab characters, or by end-of-line characters. There are two basic rules to remember when writing a macro: first, the rules for ignoring spaces when you’re typing macros are just the same as the rules that apply when you’re typing ordinary text, and second, rules for ignoring spaces do <em>not</em> apply to spaces produced while a macro is being obeyed (“expanded”). -<p>Spaces are ignored in vertical mode (between paragraphs), at the +<p/>Spaces are ignored in vertical mode (between paragraphs), at the beginning of a line, and after a command name. Since sequences of spaces are collapsed into one, it ‘feels as if’ spaces are ignored if they follow another space. Space can have syntactic meaning after @@ -26,7 +26,7 @@ certain sorts of non-braced arguments (e.g., <em>count</em> and control words (e.g., in <code>\</code><code>hbox</code> <code>to</code>, so again we have instances where it ‘feels as if’ spaces are being ignored when they’re merely working quietly for their living. -<p>Consider the following macro, fairly faithfully adapted from one that +<p/>Consider the following macro, fairly faithfully adapted from one that appeared on <i>comp.text.tex</i>: <blockquote> @@ -59,7 +59,7 @@ mandatory argument of <code>\</code><code>makebox</code> and the space immediate same argument. He had written his macro in that way to emphasise the meaning of its various parts; unfortunately the meaning was rather lost in the problems the macro caused. -<p>The principal technique for suppressing spaces is the use of +<p/>The principal technique for suppressing spaces is the use of <code>%</code> characters: everything after a <code>%</code> is ignored, even the end of line itself (so that not even the end of line can contribute an unwanted space). The @@ -100,10 +100,10 @@ spaces: Beware of the (common) temptation to place a space <em>before</em> a <code>%</code> character: if you do this you might as well omit the <code>%</code> altogether. -<p>In “real life”, of course, the spaces that appear in macros are far +<p/>In “real life”, of course, the spaces that appear in macros are far more cryptic than those in the example above. The most common spaces arise from unprotected line ends, and this is an error that occasionally appears even in macros written by the most accomplished programmers. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spinmacro">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spinmacro</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spinmacro">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spinmacro</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-splitfoot.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-splitfoot.html index 2cdb88851f0..a88f7736c8a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-splitfoot.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-splitfoot.html @@ -2,21 +2,21 @@ <title>UK TeX FAQ -- question label splitfoot</title> </head><body> <h3>Why does LaTeX split footnotes across pages?</h3> -<p>LaTeX splits footnotes when it can think of nothing better to do. +<p/>LaTeX splits footnotes when it can think of nothing better to do. Typically, when this happens, the footnote mark is at the bottom of the page, and the complete footnote would overfill the page. LaTeX could try to salvage this problem by making the page short of both the footnote and the line with the footnote mark, but its priorities told it that splitting the footnote would be preferable. -<p>As always, the best solution is to change your text so that the +<p/>As always, the best solution is to change your text so that the problem doesn’t occur in the first place. Consider whether the text that bears the footnote could move earlier in the current page, or on to the next page. -<p>If this isn’t possible, you might want to change LaTeX’s perception +<p/>If this isn’t possible, you might want to change LaTeX’s perception of its priorities: they’re controlled by <code>\</code><code>interfootnotelinepenalty</code> — the larger it is, the less willing LaTeX is to split footnotes. -<p>Setting +<p/>Setting <blockquote> <pre> \interfootnotelinepenalty=10000 @@ -25,7 +25,7 @@ LaTeX is to split footnotes. inhibits split footnotes altogether, which will cause ‘<code>Underfull</code> <code>\</code><code>vbox</code>’ messages unless you also specify <code>\</code><code>raggedbottom</code>. The default value of the penalty is <code>100</code>, which is rather mild. -<p>An alternative technique is to juggle with the actual size of the +<p/>An alternative technique is to juggle with the actual size of the pages. <code>\</code><code>enlargethispage</code> changes the size of the current page by its argument (for example, you might say <code>\</code><code>enlargethispage{<code>\</code><code>baselineskip</code>}</code> to add a single line @@ -35,10 +35,10 @@ the current page could force the offending text to the next page; increasing the size of the page may allow the footnote to be included in its entirety. It may be necessary to change the size of more than one page. -<p>The <i>fnbreak</i> package detects (and generates warnings about) +<p/>The <i>fnbreak</i> package detects (and generates warnings about) split footnotes. <dl> <dt><tt><i>fnbreak.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fnbreak.zip">macros/latex/contrib/fnbreak</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/fnbreak.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fnbreak/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=splitfoot">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=splitfoot</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=splitfoot">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=splitfoot</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-srchpdf.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-srchpdf.html index e0fbdcddfd9..2ac60dbd765 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-srchpdf.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-srchpdf.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label srchpdf</title> </head><body> <h3>Searching PDF files</h3> -<p>In principle, you can search a PDF file: the text of the file +<p/>In principle, you can search a PDF file: the text of the file is available to the viewer, and at least some viewers provide a search facility. (It’s not the fastest thing in the world, but it does help in some circumstances.) -<p>However, there is a problem: the viewer wants to look at Unicode text, +<p/>However, there is a problem: the viewer wants to look at Unicode text, but no ordinary TeX-based system deals in Unicode text. Fortunately for us Anglophones, this is is hardly ever a problem for our text, since even Knuth’s “OT1” encoding matches ASCII (and hence @@ -15,14 +15,14 @@ However, using the inflected characters of Continental European languages, or anything that doesn’t use a Latin alphabet, there is potential for problems, since TeX’s view of what a font is doesn’t map PDF’s and the reader won’t understand... -<p>... Unless you use the <i>cmap</i> package with PDFLaTeX, +<p/>... Unless you use the <i>cmap</i> package with PDFLaTeX, that is. The package will instruct PDFTeX to load character maps into your PDF for output fonts encoded according to the T1 (Western European Languages), T2A, T2B, or T2C (Cyrillic Languages), or T5 (Vietnamese) encodings. If your document uses such encodings, viewers that can search will use the maps to interpret what they find in the file. -<p>Unfortunately, the package only works with fonts that are directly +<p/>Unfortunately, the package only works with fonts that are directly encoded, such as the <i>cm-super</i> distribution. Fonts like Adobe Times Roman (which are encoded for (La)TeX use via virtual fonts) are not amenable to this treatment. @@ -30,6 +30,6 @@ are not amenable to this treatment. <dt><tt><i>cmap.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cmap.zip">macros/latex/contrib/cmap</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cmap.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cmap/">browse</a>) <dt><tt><i>cm-super fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.zip">fonts/ps-type1/cm-super</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super/">browse</a>) </dl> -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=srchpdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=srchpdf</a> +<p/> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=srchpdf">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=srchpdf</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-struttab.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-struttab.html index 8861d86c821..670afd22834 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-struttab.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-struttab.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label struttab</title> </head><body> <h3>Spacing lines in tables</h3> -<p>(La)TeX mechanisms for maintaining the space between lines (the +<p/>(La)TeX mechanisms for maintaining the space between lines (the “<em>leading</em>”) rely on TeX’s paragraph builder, which compares the shape of consecutive lines and adjusts the space between them. -<p>These mechanisms can’t work in exactly the same way when (La)TeX is +<p/>These mechanisms can’t work in exactly the same way when (La)TeX is building a table, because the paragraph builder doesn’t get to see the lines themselves. As a result, tables sometimes typeset with lines uncomfortably close together (or occasionally ridiculously far apart). -<p>Traditional (moving metal type) typographers would adjust the spacing +<p/>Traditional (moving metal type) typographers would adjust the spacing between lines of a table by use of a “<em>strut</em>” (a metal spacer). A TeX user can do exactly the same thing: most macro packages define a <code>\</code><code>strut</code> command, that defines a space appropriate @@ -17,7 +17,7 @@ to the current size of the text; placing a <code>\</code><code>strut</code> comm end of a troublesome row is the simplest solution to the problem — if it works. Other solutions below are LaTeX-specific, but some may be simply translated to Plain TeX commands. -<p>If your table exhibits a systematic problem (i.e., every row is wrong +<p/>If your table exhibits a systematic problem (i.e., every row is wrong by the same amount) use <code>\</code><code>extrarowheight</code>, which is defined by the <i>array</i> package: <blockquote> @@ -28,7 +28,7 @@ by the same amount) use <code>\</code><code>extrarowheight</code>, which is defi \begin{tabular}{....} </pre> </blockquote><p> -<p>To correct a single row whose maladjustment isn’t corrected by a +<p/>To correct a single row whose maladjustment isn’t corrected by a <code>\</code><code>strut</code> command, you can define your own, using <code>\</code><code>rule{0pt}{length}</code> — which is a near approximation to the command that goes inside a <code>\</code><code>strut</code>. The <i>bigstrut</i> package @@ -36,14 +36,14 @@ defines a strut command that you can use for this purpose: <code>\</code><code>bigstrut</code> on its own opens up both above and below the current line; <code>\</code><code>bigstrut[t]</code> opens up above the line, <code>\</code><code>bigstrut[b]</code> opens up below the line. -<p>General solutions are available, however. The <i>tabls</i> package +<p/>General solutions are available, however. The <i>tabls</i> package automatically generates an appropriately-sized strut at the end of each row. Its disadvantages are that it’s really rather slow in operation (since it gets in the way of everything within tables) and its (lack of) compatibility with other packages. -<p>The <i>cellspace</i> does a (possibly inferior) job by defining a -new table/array column type “S”, which you apply to each column -specification. So, for example, +<p/>The <i>cellspace</i> package does a (possibly inferior) job by +defining a new table/array column type “S”, which you apply to each +column specification. So, for example, <blockquote> <pre> \cmdinvoke{begin}{tabular}{l l l p{3cm}} @@ -58,7 +58,7 @@ would become and so on. This technique shows promise of not interfering so much with other packages, but this author has heard of no reports from the field. -<p>The <i>booktabs</i> package comes with a thought-provoking essay +<p/>The <i>booktabs</i> package comes with a thought-provoking essay about how tables should be designed. Since table row-spacing problems most often appear in collisions with rules, the author’s thesis, that LaTeX users tend too often to rule their tables, is @@ -66,7 +66,7 @@ interesting. The package provides rule commands to support the author’s scheme, but deals with inter-row spacing too. The most recent release of <i>booktabs</i> sports compatibility with packages such as <i>longtable</i>. -<p>Documentation of both <i>bigstrut</i> and <i>tabls</i> may be +<p/>Documentation of both <i>bigstrut</i> and <i>tabls</i> may be found as comments in the package files themselves. <dl> <dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) @@ -75,5 +75,5 @@ found as comments in the package files themselves. <dt><tt><i>cellspace.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cellspace.zip">macros/latex/contrib/cellspace</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/cellspace.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/cellspace/">browse</a>) <dt><tt><i>tabls.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/tabls.sty">macros/latex/contrib/misc/tabls.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=struttab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=struttab</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=struttab">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=struttab</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-subsubsub.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-subsubsub.html index 93fa590fe8a..b93f11eb629 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-subsubsub.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-subsubsub.html @@ -2,22 +2,22 @@ <title>UK TeX FAQ -- question label subsubsub</title> </head><body> <h3>How to create a <code>\</code><code>subsubsubsection</code></h3> -<p>LaTeX’s set of “sections” stops at the level of +<p/>LaTeX’s set of “sections” stops at the level of <code>\</code><code>subsubsection</code>. This reflects a design decision by Lamport — for, after all, who can reasonably want a section with such huge strings of numbers in front of it? -<p>In fact, LaTeX standard classes <em>do</em> define “sectioning” +<p/>In fact, LaTeX standard classes <em>do</em> define “sectioning” levels lower than <code>\</code><code>subsubsection</code>, but they don’t format them like sections (they’re not numbered, and the text is run-in after the heading). These deeply inferior section commands are <code>\</code><code>paragraph</code> and <code>\</code><code>subparagraph</code>; you can (if you <em>must</em>) arrange that these two commands produce numbered headings, so that you can use them as <code>\</code><code>subsubsubsection</code>s and lower. -<p>The <i>titlesec</i> allows you to adjust the definitions of the +<p/>The <i>titlesec</i> allows you to adjust the definitions of the sectioning macros, and it may be used to transform a <code>\</code><code>paragraph</code>’s typesetting so that it looks like that of a <code>\</code><code>section</code>. -<p>If you want to program the change yourself, you’ll find that the +<p/>If you want to program the change yourself, you’ll find that the commands (<code>\</code><code>section</code> all the way down to <code>\</code><code>subparagraph</code>) are defined in terms of the internal <code>\</code><code>@startsection</code> command, which takes 6 arguments. Before attempting this sort of work, you are well @@ -29,5 +29,5 @@ discusses use of <code>\</code><code>@startsection</code> for this sort of thing <dt><tt><i>LaTeX source</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.zip">macros/latex/base</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/base.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/base/">browse</a>) <dt><tt><i>titlesec.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titlesec.zip">macros/latex/contrib/titlesec</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titlesec.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/titlesec/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subsubsub">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subsubsub</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subsubsub">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subsubsub</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-subverttoks.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-subverttoks.html index cb8a2813e20..6becedead22 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-subverttoks.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-subverttoks.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label subverttoks</title> </head><body> <h3>Subverting a token register</h3> -<p>A common requirement is to “subvert” a token register that other +<p/>A common requirement is to “subvert” a token register that other macros may use. The requirement arises when you want to add something to a system token register (<code>\</code><code>output</code> or <code>\</code><code>every*</code>), but know that other macros use the token register, too. (A common requirement is to work on <code>\</code><code>everypar</code>, but LaTeX changes <code>\</code><code>everypar</code> at every touch and turn.) -<p>The following technique, due to David Kastrup, does what you need, and +<p/>The following technique, due to David Kastrup, does what you need, and allows an independent package to play the exact same game: <blockquote> <pre> @@ -36,7 +36,7 @@ As you can see, the package (<i>mypkg</i>) <li> points the token <code>\</code><code>everypar</code> at the new token register. </ul> and away we go. -<p>The form <code>\</code><code>mypkg@...</code> is (sort of) blessed for LaTeX package +<p/>The form <code>\</code><code>mypkg@...</code> is (sort of) blessed for LaTeX package internal names, which is why this example uses macros of that form. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subverttoks">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subverttoks</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subverttoks">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=subverttoks</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-symbols.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-symbols.html index fb854467f81..455acf5f569 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-symbols.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-symbols.html @@ -5,13 +5,13 @@ <!-- assignment circular integral degrees diagonal dots Fourier transform --> <!-- Laplace greater less complex integer natural real --> <!-- cent euro --> -<p>There is a wide range of symbols available for use with TeX, most +<p/>There is a wide range of symbols available for use with TeX, most of which are not shown (or even mentioned) in (La)TeX books. <em>The Comprehensive LaTeX Symbol List</em> (by Scott Pakin <em>et al.</em>) illustrates over 2000 symbols, and details the commands and packages needed to produce them. -<p>Other questions in this FAQ offer specific help on kinds of +<p/>Other questions in this FAQ offer specific help on kinds of symbols: <ul> <li> <a href="FAQ-scriptfonts.html">Script fonts for mathematics</a> @@ -23,5 +23,5 @@ symbols: versions in both PostScript and PDF forms for both A4 and letter paper. </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=symbols">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=symbols</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=symbols">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=symbols</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-t1enc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-t1enc.html index 1021587adfb..e4512fbd8d0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-t1enc.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-t1enc.html @@ -2,26 +2,26 @@ <title>UK TeX FAQ -- question label t1enc</title> </head><body> <h3>Why use <i>fontenc</i> rather than <i>t1enc</i>?</h3> -<p>In the very earliest days of LaTeX2e, the only way to use the +<p/>In the very earliest days of LaTeX2e, the only way to use the T1 encoding was <i>t1enc</i>; with the summer 1994 “production” release, the <i>fontenc</i> package appeared, and provided comprehensive support for use of the encoding. -<p>Nevertheless, the <i>t1enc</i> package remains (as part of the +<p/>Nevertheless, the <i>t1enc</i> package remains (as part of the LaTeX 2.09 compatibility code), but it does very little: it merely selects font encoding T1, and leaves to the user the business of generating the character codes required. -<p>Generating such character codes could be a simple matter, <em>if</em> +<p/>Generating such character codes could be a simple matter, <em>if</em> the T1 encoding matched any widely-supported encoding standard, since in that case, one might expect one’s keyboard to generate the character codes. However, the T1 encoding is a mix of several standard encodings, and includes code points in areas of the table which standard encodings specifically exclude, so no T1 keyboards have been (or ever will be) manufactured. -<p>By contrast, the <i>fontenc</i> package generates the T1 +<p/>By contrast, the <i>fontenc</i> package generates the T1 code points from ordinary LaTeX commands (e.g., it generates the <code>é</code> character codepoint from the command <code>\’</code><code>e</code>). So, unless you have program-generated T1 input, use <code>\</code><code>usepackage[T1]{fontenc}</code> rather than <code>\</code><code>usepackage{t1enc}</code>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=t1enc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=t1enc</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=t1enc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=t1enc</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tabacc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tabacc.html index 5a683dc7c53..5b1e5fd09f1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tabacc.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tabacc.html @@ -2,18 +2,18 @@ <title>UK TeX FAQ -- question label tabacc</title> </head><body> <h3>Accents misbehave in <code>tabbing</code></h3> -<p>So you are constructing a <code>tabbing</code> environment, and you +<p/>So you are constructing a <code>tabbing</code> environment, and you have the need of some diacriticised text — perhaps something as simple as <code>\</code><code>’{e}</code> — and the accent disappears because it has been interpreted as a <code>tabbing</code> command, and everything goes wrong. -<p>This is really a rather ghastly feature of the <code>tabbing</code> +<p/>This is really a rather ghastly feature of the <code>tabbing</code> environment; in order to type accented characters you need to use the <code>\</code><code>a</code> kludge: so <code>\</code><code>a’{e}</code> inside <code>tabbing</code> for <code>\</code><code>’{e}</code> outside, and similarly <code>\</code><code>a‘</code> for <code>\</code><code>‘</code> and <code>\</code><code>a=</code> for <code>\</code><code>=</code>. This whole procedure is of course hideous and error-prone. -<p>The simplest alternative is to type in an encoding that has the +<p/>The simplest alternative is to type in an encoding that has the diacriticised characters in it, and to use an appropriate encoding definition file in the <i>inputenc</i> package. So for example, type: @@ -30,7 +30,7 @@ for: </blockquote><p> and the internal mechanisms of the <i>inputenc</i> package will put the right version of the accent command in there. -<p>A witty reversal of the r\^oles is introduced by the package +<p/>A witty reversal of the r\^oles is introduced by the package <i>Tabbing</i> (note the capital “T”): it provides a <code>Tabbing</code> environment which duplicates <code>tabbing</code>, but all the single-character commands become @@ -48,5 +48,5 @@ example would therefore become: <dl> <dt><tt><i>Tabbing.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/Tabbing.zip">macros/latex/contrib/Tabbing</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/Tabbing.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/Tabbing/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabacc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabacc</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabacc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabacc</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tabcellalign.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tabcellalign.html index e2409e9b54b..5687db12009 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tabcellalign.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tabcellalign.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label tabcellalign</title> </head><body> <h3>How to alter the alignment of tabular cells</h3> -<p>One often needs to alter the alignment of a tabular <code>p</code> (‘paragraph’) +<p/>One often needs to alter the alignment of a tabular <code>p</code> (‘paragraph’) cell, but problems at the end of a table row are common. With a <code>p</code> cell that looks like: <blockquote> @@ -20,23 +20,7 @@ meaning to something incompatible. Note that the problem only arises in the last cell of a row: since each cell is set into a box, its settings are lost at the <code>&</code> (or <code>\\</code>) that terminates it. -<p>The simple (old) solution is to preserve the meaning of <code>\\</code>: -<blockquote> -<pre> -\newcommand\PBS[1]{\let\temp=\\% - #1% - \let\\=\temp -} -</pre> -</blockquote><p> -which one uses as: -<blockquote> -<pre> -... & \PBS\centering blah ... \\ -</pre> -</blockquote><p> -(for example). -<p>The technique using <code>\</code><code>PBS</code> was developed in the days of LaTeX 2.09 +<p/><p/>The technique using <code>\</code><code>PBS</code> was developed in the days of LaTeX 2.09 because the actual value of <code>\\</code> that the <code>tabular</code> environment uses was only available as an internal command. Nowadays, the value is a public command, and you can in principle use it @@ -46,62 +30,44 @@ explicitly: ... & \centering blah ... \tabularnewline </pre> </blockquote><p> -which may be incorporated into a simple macro as: -<blockquote> -<pre> -\newcommand{\RBS}{\let\\=\tabularnewline} -</pre> -</blockquote><p> -and used as -<blockquote> -<pre> -... & \centering\RBS blah ... \\ -</pre> -</blockquote><p> -(note, you Preserve backslash with <code>\</code><code>PBS</code> <em>before</em> the command -that changes it, and Restore it with <code>\</code><code>RBS</code> <em>after</em> the -command; in fact, <code>\</code><code>RBS</code> is marginally preferable, but the old -trick lingers on). -<p>The <code>\</code><code>PBS</code> and <code>\</code><code>RBS</code> tricks also serve well in <i>array</i> -package “field format” preamble specifications: +<p/>The <i>array</i> package provides a command <code>\</code><code>arraybackslash</code> +which restores <code>\\</code> to its correct (within table) meaning; +the command may be used in <i>array</i>’s “field format” preamble +specifications: <blockquote> <pre> -\begin{tabular}{... >{\centering\RBS}p{50mm}} +\begin{tabular}{... >{\centering\arraybackslash}p{50mm}} ... </pre> </blockquote><p> -or +<p/>The <code>\</code><code>tabularnewline</code> and <code>\</code><code>arraybackslash</code> commands are +(somewhat) modern additions to LaTeX and the <i>array</i> +package, respectively. If neither is available, the user may try the +(old) solution which preserves the meaning of <code>\\</code>: <blockquote> - +<pre> +\newcommand\PBS[1]{\let\temp=\\% + #1% + \let\\=\temp +} +</pre> </blockquote><p> +which one uses within a table as: <blockquote> <pre> -\begin{tabular}{... >{\PBS\centering}p{50mm}} -... +... & \PBS\centering blah ... \\ </pre> </blockquote><p> -In the <i>tabularx</i> and <i>tabulary</i> packages, there’s a -command <code>\</code><code>arraybackslash</code> that has same effect as <code>\</code><code>RBS</code> (above); -so in those packages, one might say: +or in the preamble as: <blockquote> - <pre> -\begin{tabular}{... >{\centering\arraybackslash}p{50mm}} -... +\begin{tabular}{...>{\PBS\centering}p{5cm}} </pre> </blockquote><p> -in place of the example above; in fact, the very latest (2003/12/01) -release of array.sty also provides a <code>\</code><code>tabularnewline</code> command, -that has the “basic tabular/array” meaning of ‘\\’. - -The command does rather lack brevity, but at least you don’t have to -define it for yourself. <dl> <dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) -<dt><tt><i>tabularx.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) -<dt><tt><i>tabulary.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tabulary.zip">macros/latex/contrib/tabulary</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tabulary.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tabulary/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabcellalign">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabcellalign</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabcellalign">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tabcellalign</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tds.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tds.html index 8bae9c1f84a..e02bfeab6fe 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tds.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tds.html @@ -2,9 +2,9 @@ <title>UK TeX FAQ -- question label tds</title> </head><body> <h3>What is the TDS?</h3> -<p> TDS stands for the TeX Directory Structure, which is a standard +<p/> TDS stands for the TeX Directory Structure, which is a standard way of organising all the TeX-related files on a computer system. -<p> Most modern distributions conform to the TDS, which +<p/> Most modern distributions conform to the TDS, which provides for both a ‘standard’ and a (set of) ‘local’ hierarchies of directories containing TeX-related files. The TDS reserves the name <code>texmf</code> as the name of the root directory @@ -17,13 +17,13 @@ be at <i>/opt/texmf</i>, or a similar location, but in each case the TeX files will be under the <i>/texmf</i> subdirectory. -<p>There may be more than on ‘local’ hierarchy in which additional files +<p/>There may be more than on ‘local’ hierarchy in which additional files can be stored. In the extreme an installation can have a local hierarchy and each user can also have an individual local hierarchy. The location of any local hierarchy is not only system dependent but also user dependent. Again, though, all files should be put under a local <i>/texmf</i> directory. -<p>The TDS is published as the output of a TUG +<p/>The TDS is published as the output of a TUG <a href="FAQ-TUGstar.html">Technical Working Group</a>. You may browse an <a href="http://tug.org/tds/">on-line version</a> of the standard, and copies in several other formats (including source) are @@ -31,5 +31,5 @@ available on CTAN. <dl> <dt><tt><i>TDS specification</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/tds.zip">tds</a> (<a href="ftp://cam.ctan.org/tex-archive/tds.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/tds/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tds">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tds</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tds">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tds</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tempinst.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tempinst.html index c91246a3eb9..486616de040 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tempinst.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tempinst.html @@ -2,22 +2,22 @@ <title>UK TeX FAQ -- question label tempinst</title> </head><body> <h3>“Temporary” installation of (La)TeX files</h3> -<p>Operating systems and applications need to know where to find files: +<p/>Operating systems and applications need to know where to find files: many files that they need are “just named” — the user doesn’t necessarily know <em>where</em> they are, but knows to ask for them. The commonest case, of course, is the commands whose names you type to a shell (yes, even Windows’ “MSDOS prompt”) are using a shell to read what you type: many of the commands simply involve loading and executing a file, and the <code>PATH</code> variable tells the shell where to find those files. -<p>Modern TeX implementations come with a bunch of search paths +<p/>Modern TeX implementations come with a bunch of search paths built in to them. In most circumstances these paths are adequate, but one sometimes needs to extend them to pick up files in strange places: for example, we may wish to try a new bundle of packages -before <a href="FAQ-instpackages.html">installing them ‘properly’</a>. To do +before <a href="FAQ-installthings.html">installing them ‘properly’</a>. To do this, we need to change the relevant path as TeX perceives it. However, we don’t want to throw away TeX’s built-in path (all of a sudden, TeX won’t know how to deal with all sorts of things). -<p>To <em>extend</em> a TeX path, we define an operating system +<p/>To <em>extend</em> a TeX path, we define an operating system environment variable in ‘path format’, but leaving a gap which TeX will fill with its built-in value for the path. The commonest case is that we want to place our extension in front of the path, so that our @@ -38,7 +38,7 @@ temporary files directory; in the Unix case, the “empty slot” is designated by putting the path separator ‘<code>:</code>’ on its own at the end of the line, while in the Windows case, the technique is the same, but the path separator is ‘<code>;</code>’. -<p>Note that in either sort of system, the change will only affect +<p/>Note that in either sort of system, the change will only affect instances of TeX that are started from the shell where the environment variable was set. If you run TeX from another window, it will use the original input path. To make a change of input path @@ -46,12 +46,12 @@ that will “stick” for all windows, set the environment variable in your login script or profile (or whatever) in a Unix system and log out and in again, or in <i>autoexec.bat</i> in a Windows system, and reboot the system. -<p>While all of the above has talked about where TeX finds its macro +<p/>While all of the above has talked about where TeX finds its macro files, it’s applicable to pretty much any sort of file any TeX-related program reads — there are lots of these paths, and of their corresponding environment variables. In a <i>web2c</i>-based system, the copious annotations in the <i>texmf.cnf</i> system configuration file help you to learn which path names correspond to which type of file. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tempinst">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tempinst</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tempinst">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tempinst</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-texcad.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-texcad.html index 6a988a38bdc..2a000e3c3b6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-texcad.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-texcad.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label texcad</title> </head><body> <h3>TeXCAD, a drawing package for LaTeX</h3> -<p>TeXCAD is a program for the PC which enables the user to draw diagrams +<p/>TeXCAD is a program for the PC which enables the user to draw diagrams on screen using a mouse or arrow keys, with an on-screen menu of available picture-elements. Its output is code for the LaTeX <code>picture</code> environment. @@ -11,10 +11,10 @@ the emTeX driver-family <a href="FAQ-specials.html"><code>\</code><code>special</code>s</a>. TeXCAD is part of the emTeX distribution. -<p>A Unix port of the program (<i>xtexcad</i>) has been made. +<p/>A Unix port of the program (<i>xtexcad</i>) has been made. <dl> <dt><tt><i>emtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex.zip">systems/msdos/emtex</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/emtex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/emtex/">browse</a>) <dt><tt><i>xtexcad</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/graphics/xtexcad/xtexcad-2.4.1.tar.gz">nonfree/graphics/xtexcad/xtexcad-2.4.1.tar.gz</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texcad">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texcad</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texcad">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texcad</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-texinfo.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-texinfo.html index 6dbba11a410..d7149ff4db7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-texinfo.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-texinfo.html @@ -2,19 +2,19 @@ <title>UK TeX FAQ -- question label texinfo</title> </head><body> <h3>What is Texinfo?</h3> -<p>Texinfo is a documentation system that uses one source file to produce +<p/>Texinfo is a documentation system that uses one source file to produce both on-line information and printed output. So instead of writing two different documents, one for the on-line help and the other for a typeset manual, you need write only one document source file. When the work is revised, you need only revise one document. By convention, Texinfo source file names end with a <code>.texi</code> or <code>.texinfo</code> extension. -<p>Texinfo is a macro language, somewhat similar to LaTeX, but with +<p/>Texinfo is a macro language, somewhat similar to LaTeX, but with slightly less expressive power. Its appearance is of course rather similar to any TeX-based macro language, except that its macros start with <code>@</code> rather than the <code>\</code> that’s more commonly used in TeX systems. -<p>You can write and format Texinfo files into Info files within GNU +<p/>You can write and format Texinfo files into Info files within GNU <i>emacs</i>, and read them using the <i>emacs</i> Info reader. You can also format Texinfo files into Info files using <i>makeinfo</i> and read them using <i>info</i>, so you’re not @@ -24,10 +24,10 @@ Texinfo sources into HTML: the language is a far better fit to HTML than is LaTeX, so that the breast-beating agonies of <a href="FAQ-LaTeX2HTML.html">converting LaTeX to HTML</a> are largely avoided. -<p>Finally, of course, you can also print the files, or convert them to +<p/>Finally, of course, you can also print the files, or convert them to PDF using PDFTeX. <dl> <dt><tt><i>Texinfo distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/texinfo/texinfo.zip">macros/texinfo/texinfo</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/texinfo/texinfo.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/texinfo/texinfo/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texinfo">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texinfo</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texinfo">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texinfo</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textflow.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textflow.html index a73658155b9..0e288e130bd 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textflow.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textflow.html @@ -2,28 +2,28 @@ <title>UK TeX FAQ -- question label textflow</title> </head><body> <h3>Flowing text around figures in LaTeX</h3> -<p>There are several LaTeX packages that purport to do this, but they +<p/>There are several LaTeX packages that purport to do this, but they all have their limitations because the TeX machine isn’t really designed to solve this sort of problem. Piet van Oostrum has conducted a survey of the available packages; he recommends: -<p><dl> +<p/><dl> <dt><code>floatflt</code><dd> <i>floatflt</i> is an improved version (for LaTeX2e) of <i>floatfig.sty</i>, and its syntax is: -<p><pre> +<p/><pre> \begin{floatingfigure}[options]{width of figure} figure contents \end{floatingfigure} </pre> -<p>There is a (more or less similar) <code>floatingtable</code> +<p/>There is a (more or less similar) <code>floatingtable</code> environment. -<p>The tables or figures can be set left or right, or alternating on +<p/>The tables or figures can be set left or right, or alternating on even/odd pages in a double-sided document. -<p>The package works with the <code>multicol</code> package, but doesn’t work well +<p/>The package works with the <code>multicol</code> package, but doesn’t work well in the neighbourhood of list environments (unless you change your LaTeX document). <dt><code>wrapfig</code><dd> <i>wrapfig</i> has syntax: -<p><blockquote> +<p/><blockquote> <pre> \begin{wrapfigure}[height of figure in lines]{l|r,...}[overhang]{width} figure, caption, etc. @@ -32,7 +32,7 @@ LaTeX document). </blockquote><p> The syntax of the <code>wraptable</code> environment is similar. -<p> Height can be omitted, in which case it will be calculated by the +<p/> Height can be omitted, in which case it will be calculated by the package; the package will use the greater of the specified and the actual width. The <code>{l</code><em>,</em><code>r</code><em>,etc</em>.<code>}</code> parameter can also be specified as <code>i</code><em>(nside)</em> or <code>o</code><em>(utside)</em> for @@ -40,22 +40,22 @@ LaTeX document). the picture should float. The overhang allows the figure to be moved into the margin. The figure or table will entered into the list of figures or tables if you use the <code>\</code><code>caption</code> command. -<p> The environments do not work within list environments that end +<p/> The environments do not work within list environments that end before the figure or table has finished, but can be used in a parbox or minipage, and in twocolumn format. <dt><code>picins</code><dd> <i>Picins</i> is part of a large bundle that allows inclusion of pictures (e.g., with shadow boxes, various MSDOS formats, etc.). The command is: -<p> <blockquote> +<p/> <blockquote> <code>\parpic(width,height)(x-off,y-off)[Options][Position]{Picture}</code><br> </blockquote><p> <em>Paragraph text</em> -<p> All parameters except the <em>Picture</em> are optional. The picture +<p/> All parameters except the <em>Picture</em> are optional. The picture can be positioned left or right, boxed with a rectangle, oval, shadowbox, dashed box, and a caption can be given which will be included in the list of figures. -<p> Unfortunately (for those of us whose understanding of German is not +<p/> Unfortunately (for those of us whose understanding of German is not good), the documentation is in German. Piet van Oostrum has written an English summary. </dl> @@ -66,5 +66,5 @@ LaTeX document). summary]<a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/picins/picins.txt">macros/latex209/contrib/picins/picins.txt</a> <dt><tt><i>wrapfig.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/wrapfig.zip">macros/latex/contrib/wrapfig</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/wrapfig.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/wrapfig/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=textflow">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=textflow</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=textflow">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=textflow</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textrace.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textrace.html index 420ce39eee7..129c1fe5838 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textrace.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-textrace.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label textrace</title> </head><body> <h3>Making outline fonts from Metafont</h3> -<p><i>TeXtrace</i>, originally developed by Péter Szabó, is a +<p/><i>TeXtrace</i>, originally developed by Péter Szabó, is a bundle of Unix scripts that use Martin Weber’s freeware boundary tracing package <a href="http://autotrace.sourceforge.net"><i>autotrace</a></i> to @@ -19,7 +19,7 @@ EC/TC font set <i>tt2001</i> and Vladimir Volovich’s CM-Super set, which covers the EC, TC, and the Cyrillic LH font sets (for details of both of which sets, see <a href="FAQ-type1T1.html">“8-bit” type 1 fonts</a>). -<p>Another system, which arrived slightly later, is +<p/>Another system, which arrived slightly later, is <a href="http://www.cs.uu.nl/~hanwen/mftrace/"><i>mftrace</a></i>: this is a small <i>Python</i> program that does the same job. <i>Mftrace</i> may use either <i>autotrace</i> (like @@ -28,7 +28,7 @@ this is a small <i>Python</i> program that does the same job. the initial outlines to process. <i>Mftrace</i> is said to be more flexible, and easier to use, than is <i>TeXtrace</i>, but both systems are increasingly being used to provide Type 1 fonts to the public domain. -<p>The <i>MetaType1</i> system aims to use Metafont font sources, by way +<p/>The <i>MetaType1</i> system aims to use Metafont font sources, by way of MetaPost and a bunch of scripts and so on, to produce high-quality Type 1 fonts. The first results, the <a href="FAQ-type1T1.html"><i>Latin Modern</i> fonts</a>, are now @@ -37,5 +37,5 @@ in MetaType1 format. <dl> <dt><tt><i>MetaType1</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/metatype1.zip">fonts/utilities/metatype1</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/metatype1.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/metatype1/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=textrace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=textrace</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=textrace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=textrace</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tfm.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tfm.html index ab244bb42ba..9019d6f8677 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tfm.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tfm.html @@ -2,14 +2,17 @@ <title>UK TeX FAQ -- question label tfm</title> </head><body> <h3>What are TFM files?</h3> -<p>TFM stands for TeX Font Metrics; TFM files hold +<p/>TFM stands for TeX Font Metrics; TFM files hold information about the sizes of the characters of the font in question, and about ligatures and kerns within that font. One TFM file is needed for each font used by TeX, that is for each design (point) -size for each weight for each family; one TFM file serves for all -magnifications, so that there are (typically) fewer TFM files than -there are PK files. The important point is that TFM files are -used by TeX (LaTeX, etc.), but are not, generally, needed by the -printer driver. -<p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tfm">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tfm</a> +size for each weight for each family; each TFM file serves for all +magnifications of ‘its’ font, so that there are (typically) fewer +TFM files than there are PK files. TeX (LaTeX, etc.) +itself needs only to know about the sizes of characters and their +interactions with each other, but not what characters look like. By +contrast, TFM files are not, in principle, needed by the +DVI driver, which needs to know about the glyphs that each +character selects, so as to print or display them. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tfm">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tfm</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-the-commands.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-the-commands.html index 4525754246e..bba7f14641b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-the-commands.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-the-commands.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label the-commands</title> </head><body> <h3>Redefining counters’ <code>\</code><code>the-</code>commands</h3> -<p>Whenever you request a new LaTeX counter, LaTeX creates a bunch +<p/>Whenever you request a new LaTeX counter, LaTeX creates a bunch of behind-the-scenes commands, as well as definining the counter itself. -<p>Among other things, <code>\</code><code>newcounter{</code><em>fred</em><code>}</code> creates a command +<p/>Among other things, <code>\</code><code>newcounter{</code><em>fred</em><code>}</code> creates a command <code>\</code><code>the</code><code><em>fred</em></code>, which expands to “the value of <code><em>fred</em></code>” when you’re typesetting. -<p>The definition of <code>\</code><code>the</code><code><em>fred</em></code> should express the +<p/>The definition of <code>\</code><code>the</code><code><em>fred</em></code> should express the value of the counter: it is almost always always a mistake to use the command to produce anything else. The value may reasonably be expressed as an arabic, a roman or a greek number, as an alphabetic @@ -16,19 +16,19 @@ expression, or even as a sequence (or pattern of) symbols. If you need a decision process on whether to re-define <code>\</code><code>the</code><code><em>fred</em></code>, consider what might happen when you do so. -<p>So, for example, if you want your section numbers to be terminated by +<p/>So, for example, if you want your section numbers to be terminated by a period, you could make <code>\</code><code>thesection</code> expand with a terminating period. However, such a change to <code>\</code><code>thesection</code> makes the definition of <code>\</code><code>thesubsection</code> look distinctly odd: you are going to find yourself redefining things left, right and centre. Rather, use the standard techniques for <a href="FAQ-seccntfmt.html">adjusting the presentation of section numbers</a>. -<p>Or, suppose you want the page number to appear at the bottom of each +<p/>Or, suppose you want the page number to appear at the bottom of each page surrounded by dashes (“<code>-</code><code>- nnn -</code><code>-</code>”). Would you want to achieve this by redefining <code>\</code><code>thepage</code>, given the likely appearance of the table of contents with the dashes attached every page number, or of the modified <code>\</code><code>pageref</code> references. In this case, the modification is best done by redefining the page style itself, perhaps <a href="FAQ-fancyhdr.html">package <i>fancyhdr</i></a>. -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=the-commands">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=the-commands</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=the-commands">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=the-commands</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-theoremfmt.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-theoremfmt.html index a8f10674f9e..485457a83e8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-theoremfmt.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-theoremfmt.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label theoremfmt</title> </head><body> <h3>Roman theorems</h3> -<p>If you want to take advantage of the powerful <code>\</code><code>newtheorem</code> command +<p/>If you want to take advantage of the powerful <code>\</code><code>newtheorem</code> command without the constraint that the contents of the theorem is in a sloped font (for example, to use it to create remarks, examples, proofs, ...) then you can use the AMSLaTeX <i>amsthm</i> package @@ -21,5 +21,5 @@ The <i>ntheorem</i> package provides roman theorems directly. <dt><tt><i>ntheorem.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntheorem.zip">macros/latex/contrib/ntheorem</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ntheorem.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ntheorem/">browse</a>) <dt><tt><i>theorem.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=theoremfmt">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=theoremfmt</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=theoremfmt">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=theoremfmt</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-thesis.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-thesis.html index 578a461e79a..fe7573cc45a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-thesis.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-thesis.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label thesis</title> </head><body> <h3>Formatting a thesis in LaTeX</h3> -<p>Thesis styles are usually very specific to your University, so it’s +<p/>Thesis styles are usually very specific to your University, so it’s usually not profitable to ask around for a package outside your own University. Since many Universities (in their eccentric way) still require double-spacing, you may care to refer to @@ -14,5 +14,5 @@ able to produce an æsthetically pleasing document anyway!) <dl> <dt><tt><i>UC thesis style</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ucthesis.zip">macros/latex/contrib/ucthesis</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ucthesis.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ucthesis/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=thesis">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=thesis</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=thesis">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=thesis</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-time.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-time.html index 1747975ce30..6617bca3e6e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-time.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-time.html @@ -2,21 +2,21 @@ <title>UK TeX FAQ -- question label time</title> </head><body> <h3>Printing the time</h3> -<p>TeX has a primitive register that contains “the number of minutes +<p/>TeX has a primitive register that contains “the number of minutes since midnight”; with this knowledge it’s a moderately simple programming job to print the time (one that no self-respecting Plain TeX user would bother with anyone else’s code for). -<p>However, LaTeX provides no primitive for “time”, so the +<p/>However, LaTeX provides no primitive for “time”, so the non-programming LaTeX user needs help. -<p>Two packages are available, both providing ranges of ways of printing +<p/>Two packages are available, both providing ranges of ways of printing the date, as well as of the time: this question will concentrate on the time-printing capabilities, and interested users can investigate the documentation for details about dates. -<p>The <i>datetime</i> package defines two time-printing functions: +<p/>The <i>datetime</i> package defines two time-printing functions: <code>\</code><code>xxivtime</code> (for 24-hour time), <code>\</code><code>ampmtime</code> (for 12-hour time) and <code>\</code><code>oclock</code> (for time-as-words, albeit a slightly eccentric set of words). -<p>The <i>scrtime</i> package (part of the compendious +<p/>The <i>scrtime</i> package (part of the compendious <i>KOMA-Script</i> bundle) takes a package option (<code>12h</code> or <code>24h</code>) to specify how times are to be printed. The command <code>\</code><code>thistime</code> then prints the time appropriately (though there’s no @@ -27,5 +27,5 @@ hours and minutes: the default is of course <code>:</code>. <dt><tt><i>datetime.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/datetime.zip">macros/latex/contrib/datetime</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/datetime.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/datetime/">browse</a>) <dt><tt><i>scrtime.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=time">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=time</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=time">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=time</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-titlsty.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-titlsty.html index d0e4440b3a3..8d30d1c7ef1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-titlsty.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-titlsty.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label titlsty</title> </head><body> <h3>The style of document titles</h3> -<p>The <i>titling</i> package provides a number of facilities that +<p/>The <i>titling</i> package provides a number of facilities that permit manipulation of the appearance of a <code>\</code><code>maketitle</code> command, the <code>\</code><code>thanks</code> commands within it, and so on. The package also defines a <code>titlingpage</code> environment, that offers something in between the standard classes’ <code>titlepage</code> option and the <code>titlepage</code> environment, and is itself somewhat configurable. -<p>The memoir class includes all the functionality of the +<p/>The memoir class includes all the functionality of the <i>titling</i> package, while the <i>KOMA-script</i> classes have their own range of different titling styles. -<p>Finally, the indefatigable Vincent Zoonekynd supplies examples of how +<p/>Finally, the indefatigable Vincent Zoonekynd supplies examples of how to program alternative <a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_title/0.html">title styles</a>. The web page is not useful to users unless they are willing to do @@ -21,5 +21,5 @@ their own LaTeX programming. <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>titling.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titling.zip">macros/latex/contrib/titling</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/titling.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/titling/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=titlsty">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=titlsty</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=titlsty">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=titlsty</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tmupfl.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tmupfl.html index 44c8a404516..681de21a071 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tmupfl.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tmupfl.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label tmupfl</title> </head><body> <h3>“Too many unprocessed floats”</h3> -<p>If LaTeX responds to a <code>\</code><code>begin{figure}</code> or +<p/>If LaTeX responds to a <code>\</code><code>begin{figure}</code> or <code>\</code><code>begin{table}</code> command with the error message <pre> ! LaTeX Error: Too many unprocessed floats. @@ -15,7 +15,7 @@ has a limited amount of storage for ‘floats’ (figures, tables, or floats you’ve defined yourself with the <i>float</i> package); if you don’t let it ever actually typeset any floats, it will run out of space. -<p>This failure usually occurs in extreme cases of +<p/>This failure usually occurs in extreme cases of <a href="FAQ-floats.html">floats moving “wrongly”</a>; @@ -27,11 +27,11 @@ changed, so that placement out of order would mean figure numbers appearing out of order in the document (and in the list of figures, or whatever). So a simple failure to place a figure means that no subsequent figure can be placed; and hence (eventually) the error. -<p>Techniques for solving the problem are discussed in the +<p/>Techniques for solving the problem are discussed in the <a href="FAQ-floats.html">floats question</a> already referenced. -<p>The error also occurs in a +<p/>The error also occurs in a long sequence of <code>figure</code> or <code>table</code> environments, with no intervening text. Unless the environments will fit “here” (and you’ve allowed @@ -40,11 +40,11 @@ will never be an opportunity for LaTeX to reconsider placement. (Of course, the floats can’t all fit “here” if the sequence is sufficiently prolonged: once the page fills, LaTeX won’t place any more floats, leading to the error. -<p>Techniques for resolution may involve redefining the floats using the +<p/>Techniques for resolution may involve redefining the floats using the <i>float</i> package’s <code>[H]</code> float qualifier, but you are unlikely to get away without using <code>\</code><code>clearpage</code> from time to time. <dl> <dt><tt><i>float.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tmupfl">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tmupfl</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tmupfl">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tmupfl</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toascii.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toascii.html index bc378c856d4..39104b0ba0b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toascii.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toascii.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label toascii</title> </head><body> <h3>Conversion from (La)TeX to plain text</h3> -<p>The aim here is to emulate the Unix <i>nroff</i>, which formats +<p/>The aim here is to emulate the Unix <i>nroff</i>, which formats text as best it can for the screen, from the same input as the Unix typesetting program <i>troff</i>. -<p>Converting DVI to plain text is the basis of many of these +<p/>Converting DVI to plain text is the basis of many of these techniques; sometimes the simple conversion provides a good enough response. Options are: <ul> @@ -20,27 +20,27 @@ A common problem is the hyphenation that TeX inserts when typesetting something: since the output is inevitably viewed using fonts that don’t match the original, the hyphenation usually looks silly. -<p>Ralph Droms provides a <i>txt</i> bundle of things in support of +<p/>Ralph Droms provides a <i>txt</i> bundle of things in support of ASCII generation, but it doesn’t do a good job with tables and mathematics. An alternative is the <i>screen</i> package. -<p>Another possibility is to +<p/>Another possibility is to use the LaTeX-to-ASCII conversion program, <i>l2a</i>, although this is really more of a de-TeXing program. -<p>The canonical de-TeXing program is <i>detex</i>, which removes +<p/>The canonical de-TeXing program is <i>detex</i>, which removes all comments and control sequences from its input before writing it to its output. Its original purpose was to prepare input for a dumb spelling checker, and it’s only usable for preparing useful ASCII versions of a document in highly restricted circumstances. -<p><i>Tex2mail</i> is slightly more than a de-TeXer — it’s a +<p/><i>Tex2mail</i> is slightly more than a de-TeXer — it’s a <i>Perl</i> script that converts TeX files into plain text files, expanding various mathematical symbols (sums, products, integrals, sub/superscripts, fractions, square roots, ...) into “ASCII art” that spreads over multiple lines if necessary. The result is more readable to human beings than the flat-style TeX code. -<p>Another significant possibility is to use one of the +<p/>Another significant possibility is to use one of the <a href="FAQ-LaTeX2HTML.html">HTML-generation solutions</a>, and then to use a browser such as <i>lynx</i> to dump the resulting HTML as plain text. @@ -48,11 +48,11 @@ HTML as plain text. <dt><tt><i>catdvi</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/catdvi.zip">dviware/catdvi</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/catdvi.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/catdvi/">browse</a>) <dt><tt><i>crudetype</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/crudetype.zip">dviware/crudetype</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/crudetype.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/crudetype/">browse</a>) <dt><tt><i>detex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/detex.zip">support/detex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/detex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/detex/">browse</a>) -<dt><tt><i>dvi2tty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/dviware/dvi2tty.zip">nonfree/dviware/dvi2tty</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/dviware/dvi2tty.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/dviware/dvi2tty/">browse</a>) +<dt><tt><i>dvi2tty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvi2tty.zip">dviware/dvi2tty</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvi2tty.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvi2tty/">browse</a>) <dt><tt><i>l2a</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/l2a.zip">support/l2a</a> (<a href="ftp://cam.ctan.org/tex-archive/support/l2a.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/l2a/">browse</a>) <dt><tt><i>screen.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex209/contrib/misc/screen.sty">macros/latex209/contrib/misc/screen.sty</a> <dt><tt><i>tex2mail</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/tex2mail.zip">support/tex2mail</a> (<a href="ftp://cam.ctan.org/tex-archive/support/tex2mail.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/tex2mail/">browse</a>) <dt><tt><i>txt</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/txt.zip">support/txt</a> (<a href="ftp://cam.ctan.org/tex-archive/support/txt.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/txt/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toascii">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toascii</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toascii">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toascii</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocbibind.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocbibind.html index 94604f49f27..82a5b21fffd 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocbibind.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocbibind.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label tocbibind</title> </head><body> <h3>Bibliography, index, etc., in TOC</h3> -<p>The standard LaTeX classes (and many others) use <code>\</code><code>section*</code> or +<p/>The standard LaTeX classes (and many others) use <code>\</code><code>section*</code> or <code>\</code><code>chapter*</code> for auto-generated parts of the document (the tables of contents, lists of figures and tables, the bibliography and the index). As a result, these items aren’t numbered (which most people don’t mind), and (more importantly) they don’t appear in the table of contents. -<p>The correct solution (as always) is to have a class of your own that +<p/>The correct solution (as always) is to have a class of your own that formats your document according to your requirements. The macro to do the job (<code>\</code><code>addcontentsline</code>) is fairly simple, but there is always an issue of ensuring that the contents entry quotes the correct page. @@ -32,16 +32,30 @@ one page long. Instead, one should say: document is single-sided — in that case, it’s a synonym for <code>\</code><code>clearpage</code>). Ensuring that the entry refers to the right place is trickier still in a <code>\</code><code>section</code>-based class. -<p>The common solution, therefore, is to use the <i>tocbibind</i> +<p/>If you are using <i>hyperref</i> (which will link entries in the +table of contents to the relevant place in the file), a slight +adjustment is necessary: +<blockquote> +<pre> +\phantomsection +\cleardoublepage +\addcontentsline{toc}{chapter}{Bibliography} +\bibliography{frooble} +</pre> +</blockquote><p> +The extra command (<code>\</code><code>phantomsection</code>) gives <i>hyperref</i> +something to “hold on to” when making the link. +<p/>The common solution, therefore, is to use the <i>tocbibind</i> package, which provides many facilities to control the way these entries appear in the table of contents. -<p>Classes of the <i>KOMA-script</i> bundle provide this functionality +<p/>Classes of the <i>KOMA-script</i> bundle provide this functionality as a set of class options; the <i>memoir</i> class includes <i>tocbibind</i> itself. <dl> +<dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>) <dt><tt><i>KOMA script bundle</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.zip">macros/latex/contrib/koma-script</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/koma-script.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/koma-script/">browse</a>) <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>tocbibind.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocbibind.zip">macros/latex/contrib/tocbibind</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocbibind.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tocbibind/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocbibind">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocbibind</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocbibind">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocbibind</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloft.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloft.html index e09250a0d02..c82806db738 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloft.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloft.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label tocloft</title> </head><body> <h3>The format of the Table of Contents, etc.</h3> -<p>The formats of entries in the table of contents (TOC) are +<p/>The formats of entries in the table of contents (TOC) are controlled by a number of internal commands (discussed in section 2.3 of <a href="FAQ-books.html"><em>The LaTeX Companion</em></a>. The commands <code>\</code><code>@pnumwidth</code>, <code>\</code><code>@tocrmarg</code> and <code>\</code><code>@dotsep</code> control the space @@ -14,12 +14,12 @@ is the name of a sectional heading (such as <code>chapter</code> or heading, including the space for section numbers. All these internal commands may be individually redefined to give the effect that you want. -<p>Alternatively, the package <i>tocloft</i> provides a set of +<p/>Alternatively, the package <i>tocloft</i> provides a set of user-level commands that may be used to change the TOC formatting. Since exactly the same mechanisms are used for the List of Figures and List of Tables, the layout of these sections may be controlled in the same way. -<p>The <i>KOMA-Script</i> classes provides an optional variant structure +<p/>The <i>KOMA-Script</i> classes provides an optional variant structure for the table of contents, and calculates the space needed for the numbers automatically. The <i>memoir</i> class includes the functionality of <i>tocloft</i>. @@ -28,5 +28,5 @@ of <i>tocloft</i>. <dt><tt><i>memoir.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) <dt><tt><i>tocloft.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocloft.zip">macros/latex/contrib/tocloft</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/tocloft.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/tocloft/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloft">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloft</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloft">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloft</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloftwrong.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloftwrong.html index 883710a4caa..99f465581e9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloftwrong.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tocloftwrong.html @@ -2,17 +2,17 @@ <title>UK TeX FAQ -- question label tocloftwrong</title> </head><body> <h3>Numbers too large in table of contents, etc.</h3> -<p>LaTeX constructs the table of contents, list of figures, tables, +<p/>LaTeX constructs the table of contents, list of figures, tables, and similar tables, on the basis of a layout specified in the class. As a result, they do <em>not</em> react to the sizes of things in them, as they would if a <code>tabular</code> environment (or something similar) was used. -<p>This arrangement can provoke problems, most commonly with deep section +<p/>This arrangement can provoke problems, most commonly with deep section nesting or very large page numbers: the numbers in question just don’t fit in the space allowed for them in the class. -<p>A separate answer discusses +<p/>A separate answer discusses <a href="FAQ-tocloft.html">re-designing the tables</a> and those techniques can be employed to make the numbers fit. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloftwrong">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloftwrong</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloftwrong">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tocloftwrong</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toodeep.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toodeep.html index 47c1b59cf28..cd84fa8cb06 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toodeep.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toodeep.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label toodeep</title> </head><body> <h3>“Too deeply nested”</h3> -<p>This error appears when you start a LaTeX list. -<p>LaTeX keeps track of the nesting of one list inside another. There +<p/>This error appears when you start a LaTeX list. +<p/>LaTeX keeps track of the nesting of one list inside another. There is a set of list formatting parameters built-in for application to each of the list nesting levels; the parameters determine indentation, item separation, and so on. The <code>list</code> environment (the basis for list environments like <code>itemize</code> and <code>enumerate</code>) “knows” there are only 6 of these sets. -<p>There are also different label definitions for the +<p/>There are also different label definitions for the <code>enumerate</code> and <code>itemize</code> environments at their own private levels of nesting. Consider this example: <blockquote> @@ -45,14 +45,14 @@ parameters for indentation, it also <em>knows</em> that there are only 4 types of labels each, for the environments <code>enumerate</code> and <code>itemize</code> (this “knowledge” spells out a requirement for class writers, since the class supplies the sets of parameters). -<p>From the above, we can deduce that there are several ways we can run +<p/>From the above, we can deduce that there are several ways we can run out of space: we can have 6 lists (of any sort) nested, and try to start a new one; we can have 4 <code>enumerate</code> environments somewhere among the set of nested lists, and try to add another one; and we can have 4 <code>itemize</code> environments somewhere among the set of nested lists, and try to add another one. -<p>What can be done about the problem? Not much, short of rewriting +<p/>What can be done about the problem? Not much, short of rewriting LaTeX — you really need to rewrite your document in a slightly less labyrinthine way. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toodeep">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toodeep</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toodeep">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=toodeep</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-topgraph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-topgraph.html index f2ca26d9665..c8257657fe0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-topgraph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-topgraph.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label topgraph</title> </head><body> <h3>Top-aligning imported graphics</h3> -<p>When TeX sets a line of anything, it ensures that the base-line of +<p/>When TeX sets a line of anything, it ensures that the base-line of each object in the line is at the same level as the base-line of the final object. (Apart, of course, from <code>\</code><code>raisebox</code> commands...) -<p>Most imported graphics have their base-line set at the bottom of the +<p/>Most imported graphics have their base-line set at the bottom of the picture. When using packages such as <i>subfig</i>, one often wants to align figures by their tops. The following odd little bit of code does this: @@ -23,7 +23,7 @@ The <code>\</code><code>vtop</code> primitive sets the base-line of the resultin that of the first “line” in it; the <code>\</code><code>vskip</code> creates the illusion of an empty line, so <code>\</code><code>vtop</code> makes the very top of the box into the base-line. -<p>In cases where the graphics are to be aligned with text, there is a +<p/>In cases where the graphics are to be aligned with text, there is a case for making the base-line one ex-height below the top of the box, as in: <blockquote> @@ -46,7 +46,7 @@ the <i>calc</i> package: </pre> </blockquote><p> (this has the same effect as the text-align version, above). -<p>The fact is, <em>you</em> may choose where the base-line ends up. This +<p/>The fact is, <em>you</em> may choose where the base-line ends up. This answer merely shows you sensible choices you might make. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=topgraph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=topgraph</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=topgraph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=topgraph</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tradesyms.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tradesyms.html index 1b56e248067..dfea790f4fb 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tradesyms.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tradesyms.html @@ -2,21 +2,21 @@ <title>UK TeX FAQ -- question label tradesyms</title> </head><body> <h3>How to get copyright, trademark, etc.</h3> -<p>The “ +<p/>The “ <a href="FAQ-symbols.html">Comprehensive symbol list</a>”, lists the symbol commands <code>\</code><code>textcopyright</code>, <code>\</code><code>textregistered</code> and <code>\</code><code>texttrademark</code>, which are available in TS1-encoded fonts, and which are enabled using the <i>textcomp</i> package. -<p>In fact, all three commands are enabled in default LaTeX, but the +<p/>In fact, all three commands are enabled in default LaTeX, but the glyphs you get aren’t terribly beautiful. In particular, <code>\</code><code>textregistered</code> behaves oddly when included in bold text (for example, in a section heading), since it is composed of a small-caps letter, which typically degrades to a regular shape letter when asked to set in a bold font. This means that the glyph becomes a circled “r”, whereas the proper symbol is a circled “R”. -<p>This effect is of course avoided by use of <i>textcomp</i>. -<p>Another problem arises if you want <code>\</code><code>textregistered</code> in a +<p/>This effect is of course avoided by use of <i>textcomp</i>. +<p/>Another problem arises if you want <code>\</code><code>textregistered</code> in a superscript position (to look similar to <code>\</code><code>texttrademark</code>). Using a maths-mode superscript to do this provokes lots of pointless errors: you <em>must</em> use @@ -25,6 +25,6 @@ errors: you <em>must</em> use \textsuperscript{\textregistered} </pre> </blockquote><p> -<p> -<p><p><p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tradesyms">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tradesyms</a> +<p/> +<p/><p/><p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tradesyms">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tradesyms</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-triptrap.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-triptrap.html index 951d14392bc..8170bd9165f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-triptrap.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-triptrap.html @@ -2,15 +2,15 @@ <title>UK TeX FAQ -- question label triptrap</title> </head><body> <h3>How can I be sure it’s really TeX?</h3> -<p>TeX (and Metafont and MetaPost) are written in a +<p/>TeX (and Metafont and MetaPost) are written in a <a href="FAQ-lit.html">‘literate’ programming</a> language called Web which is designed to be portable across a wide range of computer systems. How, then, is a new version of TeX checked? -<p>Of course, any sensible software implementor will have his own suite +<p/>Of course, any sensible software implementor will have his own suite of tests to check that his software runs: those who port TeX and its friends to other platforms do indeed perform such tests. -<p>Knuth, however, provides a ‘conformance test’ for both TeX +<p/>Knuth, however, provides a ‘conformance test’ for both TeX (<code>trip</code>) and Metafont (<code>trap</code>). He characterises these as ‘torture tests’: they are designed not to @@ -18,11 +18,11 @@ check the obvious things that ordinary typeset documents, or font designs, will exercise, but rather to explore small alleyways off the main path through the code of TeX. They are, to the casual reader, pretty incomprehensible! -<p>Once an implementation of TeX has passed its <code>trip</code> test, or an +<p/>Once an implementation of TeX has passed its <code>trip</code> test, or an implementation of Metafont has passed its <code>trap</code> test, then it may in principe be distributed as a working version. (In practice, any distributor would test new versions against “real” documents or fonts, too; <code>trip</code> and <code>trap</code> don’t actually test any for real world problems. -<p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=triptrap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=triptrap</a> +<p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=triptrap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=triptrap</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tutbitslatex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tutbitslatex.html index f1a62ae86f5..eacc105e158 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tutbitslatex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tutbitslatex.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label tutbitslatex</title> </head><body> <h3>Specialised (La)TeX tutorials</h3> -<p>The AMS publishes a “Short Math Guide for LaTeX”, which is +<p/>The AMS publishes a “Short Math Guide for LaTeX”, which is available (in several formats) via <a href="http://www.ams.org/tex/short-math-guide.html">http://www.ams.org/tex/short-math-guide.html</a> -<p>Herbert Voss is developing a parallel document, that is also very +<p/>Herbert Voss is developing a parallel document, that is also very useful; it’s part of his “<a href="FAQ-doc-dirs.html">tips and tricks</a>” and a copy is maintained on CTAN. -<p>Two documents written more than ten years apart about font usage in +<p/>Two documents written more than ten years apart about font usage in TeX are worth reading: <a href="href=’http://www.tug.org/TUGboat/Articles/tb14-2/tb39rahtz-nfss.pdf">Essential NFSS</a> by Sebastian Rahtz, and @@ -17,24 +17,24 @@ by Sebastian Rahtz, and cast in the form of an FAQ, by Walter Schmidt. A general compendium of font information (including the two above) may be found on the <a href="http://www.tug.org/fonts/">TUG web site</a>. -<p>Peter Smith’s +<p/>Peter Smith’s “<a href="http://www.phil.cam.ac.uk/teaching_staff/Smith/LaTeX/">LaTeX for Logicians</a>” covers a rather smaller subject area, but is similarly comprehensive (mostly by links to documents on relevant topics, rather than as a monolithic document). -<p>Keith Reckdahl’s “Using Imported Graphics in LaTeX2e” is an +<p/>Keith Reckdahl’s “Using Imported Graphics in LaTeX2e” is an excellent introduction to graphics use. It’s available on CTAN, but the sources aren’t available (promised “some time soon”). -<p>Kjell Magne Fauske offers a set of examples of the use of the drawing +<p/>Kjell Magne Fauske offers a set of examples of the use of the drawing packages <a href="FAQ-drawing.html">PGF and TikZ</a>; the <a href="http://www.fauskes.net/pgftikzexamples/">examples catalogue</a> includes examples (with output) from the package documentation as well as code written by the author himself. -<p>Vincent Zoonekynd provides a set of excellent (and graphic) tutorials +<p/>Vincent Zoonekynd provides a set of excellent (and graphic) tutorials on the programming of <a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_title/0.html">title page styles</a>, <a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_chapter/0.html">chapter heading styles</a> @@ -42,7 +42,7 @@ and <a href="http://zoonek.free.fr/LaTeX/LaTeX_samples_section/0.html">section heading styles</a>. In each file, there is a selection of graphics representing an output style, and for each style, the code that produces it is shown. -<p>An invaluable step-by-step setup guide for establishing a “work +<p/>An invaluable step-by-step setup guide for establishing a “work flow” through your (La)TeX system, so that output appears at the correct size and position on standard-sized paper, and that the print quality is satisfactory, is Mike Shell’s <i>testflow</i>. The @@ -53,24 +53,24 @@ complete kit is available on CTAN (distributed with the author’s macros for papers submitted for IEEE publications). The issues are also covered in a later <a href="FAQ-dvips-pdf.html">FAQ answer</a>. -<p>Documentation of Japanese TeX use appears at least twice on the web: +<p/>Documentation of Japanese TeX use appears at least twice on the web: Haruhiko Okumura’s page on <a href="http://oku.edu.mie-u.ac.jp/~okumura/texfaq/japanese/">typesetting Japanese with Omega</a> (the parent page is in Japanese, so out of the scope of this FAQ). -<p>One “Tim” documents pTeX (a TeX system widely used in Japan) +<p/>One “Tim” documents pTeX (a TeX system widely used in Japan) in his “<a href="http://www.users.waitrose.com/~nihilist/English_Notes_on_pTex.pdf">English notes on pTeX</a>”. -<p>Some university departments make their local documentation available +<p/>Some university departments make their local documentation available on the web. Most straightforwardly, there’s the simple translation of existing documentation into HTML, for example the INFO documentation of the (La)TeX installation, of which a sample is the LaTeX documentation available at <a href="http://www.tac.dk/cgi-bin/info2www?(latex)">http://www.tac.dk/cgi-bin/info2www?(latex)</a> -<p>More ambitiously, some university departments have enthusiastic +<p/>More ambitiously, some university departments have enthusiastic documenters who make public record of their (La)TeX support. For example, Tim Love (of Cambridge University Engineering Department) maintains his @@ -88,5 +88,5 @@ deparment’s pages at <dt><tt><i>testflow</i></tt><dd><a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/IEEEtran/testflow/">macros/latex/contrib/IEEEtran/testflow/</a> <dt><tt><i>Herbert Voss’s Maths tutorial</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/math/voss/mathmode/Mathmode.pdf">info/math/voss/mathmode/Mathmode.pdf</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutbitslatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutbitslatex</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutbitslatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutbitslatex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tutorialstar.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tutorialstar.html index efa17ba88f2..a40e4a8ec57 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tutorialstar.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tutorialstar.html @@ -2,24 +2,24 @@ <title>UK TeX FAQ -- question label tutorials*</title> </head><body> <h3>(La)TeX Tutorials, etc.</h3> -<p>From a situation where every (La)TeX user <em>had</em> to buy a book +<p/>From a situation where every (La)TeX user <em>had</em> to buy a book if she was not to find herself groping blindly along, we now have what almost amounts to an embarrassment of riches of online documentation. The following answers attempt to create lists of sources “by topic”. -<p>First we have introductory manuals, for +<p/>First we have introductory manuals, for <a href="FAQ-man-tex.html">Plain TeX</a> and <a href="FAQ-man-latex.html">LaTeX</a>. -<p>Next comes a selection of +<p/>Next comes a selection of <a href="FAQ-tutbitslatex.html">“specialised” (La)TeX tutorials</a>, each of which concentrates on a single LaTeX topic. -<p>A couple of reference documents (it would be good to have more) are +<p/>A couple of reference documents (it would be good to have more) are listed in an <a href="FAQ-ref-doc.html">answer of their own</a>. -<p>Next comes the (rather new) field of +<p/>Next comes the (rather new) field of <a href="FAQ-doc-wiki.html">TeX-related WIKIs</a>. -<p>A rather short list gives us a +<p/>A rather short list gives us a <a href="FAQ-typo-style.html">Typography style tutorial</a>. -<p>Finally, we have a set of links to +<p/>Finally, we have a set of links to <a href="FAQ-doc-dirs.html">Directories of (La)TeX information</a>, and details of some “<a href="FAQ-ol-books.html">books</a>” that were once published conventionally, but are now available on-line. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutorials*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutorials*</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutorials*">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutorials*</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-twooptarg.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-twooptarg.html index 16c3aae2ed0..bb7b1a8208c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-twooptarg.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-twooptarg.html @@ -2,18 +2,19 @@ <title>UK TeX FAQ -- question label twooptarg</title> </head><body> <h3>More than one optional argument</h3> -<p>If you’ve already read +<p/>If you’ve already read “<a href="FAQ-moren9.html">breaking the 9-argument limit</a>”. -you can probably guess the solution to this problem: command relaying. -<p>LaTeX allows commands with a single optional argument thus: +you can probably guess the “simple” solution to this problem: +command relaying. +<p/>LaTeX allows commands with a single optional argument thus: <pre> \newcommand{\blah}[1][Default]{...} </pre> -<p>You may legally call such a command either with its optional argument +<p/>You may legally call such a command either with its optional argument present, as -<code>\</code><code>blah[nonDefault]</code> or as <code>\</code><code>blah</code>; in the latter case, the -code of <code>\</code><code>blah</code> will have an argument of <code>Default</code>. -<p>To define a command with two optional arguments, we use the relaying +<code>\</code><code>blah[nonDefault]</code> or without, as <code>\</code><code>blah</code>; in the latter +case, the code of <code>\</code><code>blah</code> will have an argument of <code>Default</code>. +<p/>To define a command with two optional arguments, we use the relaying technique, as follows: <pre> \newcommand{\blah}[1][Default1]{% @@ -30,32 +31,48 @@ technique, as follows: Of course, <code>\</code><code>BlahRelay</code> may have as many mandatory arguments as are allowed, after allowance for the one taken up with its own optional argument — that is, 8. -<p>Variants of <code>\</code><code>newcommand</code> (and friends), with names like +<p/>Variants of <code>\</code><code>newcommand</code> (and friends), with names like <code>\</code><code>newcommandtwoopt</code>, are available in the <i>twoopt</i> package. However, if you can, it’s probably better to learn to write the commands yourself, just to see why they’re not even a good idea from the programming point of view. -<p>A command with two optional arguments strains the limit of what’s +<p/>A command with two optional arguments strains the limit of what’s sensible: obviously you can extend the technique to provide as many optional arguments as your fevered imagination can summon. However, see the comments on the use of the <i>keyval</i> package, in “<a href="FAQ-moren9.html">breaking the 9-argument limit</a>”, which offers an alternative way forward. -<p>If you must, however, consider the <i>optparams</i> package; +<p/>If you must, however, consider the <i>optparams</i> or +<i>xargs</i> packages. <i>Optparams</i> provides a <code>\</code><code>optparams</code> command that you use as an intermediate in defining commands with up to nine optional arguments. The documentation shows examples of commands with four optional arguments (and this from an author who has his own key-value package!). -<p>An alternative approach is offered by Scott Pakin’s +<p/>The <i>xargs</i> package uses a key-value package +(<i>xkeyval</i>) to <em>define</em> the layout of the optional +arguments. Thus +<blockquote> +<pre> +\usepackage{xargs} +... +\newcommandx{\foo}[3][1=1, 3=n]{...} +</pre> +</blockquote><p> +defines a command <code>\</code><code>foo</code> that has an optional first argument +(default 1), a mandatory second argument, and an optional third +argument (default n). +<p/>An alternative approach is offered by Scott Pakin’s <i>newcommand</i> program, which takes a command name and a definition of a set of command arguments (in a fairly readily-understood language), and emits (La)TeX macros which enable the command to be defined. The command requires that a -<i>Python</i> system be installed on your computer. +<i>Python</i> interpreter (etc.) be installed on your computer. <dl> <dt><tt><i>newcommand.py</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/newcommand.zip">support/newcommand</a> (<a href="ftp://cam.ctan.org/tex-archive/support/newcommand.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/newcommand/">browse</a>) <dt><tt><i>optparams.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sauerj.zip">macros/latex/contrib/sauerj</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/sauerj.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/sauerj/">browse</a>) <dt><tt><i>twoopt.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>) +<dt><tt><i>xargs.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xargs.zip">macros/latex/contrib/xargs</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xargs.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xargs/">browse</a>) +<dt><tt><i>xkeyval.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xkeyval.zip">macros/latex/contrib/xkeyval</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/xkeyval.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/xkeyval/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=twooptarg">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=twooptarg</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=twooptarg">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=twooptarg</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-type1T1.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-type1T1.html index e4b473f275d..3f394430699 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-type1T1.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-type1T1.html @@ -3,7 +3,7 @@ </head><body> <h3>Finding ‘8-bit’ Type 1 fonts</h3> <!-- eight --> -<p>Elsewhere, answers to these FAQs recommend that you use an +<p/>Elsewhere, answers to these FAQs recommend that you use an ‘8-bit’ font to permit <a href="FAQ-hyphenaccents.html">accentuation of inflected languages</a>, and also recommend the use of Type 1 fonts to ensure that @@ -16,14 +16,14 @@ a good approach to the Cork encoding (see below). Now, however, we have “true” Type 1 fonts available: as always, we have an embarrassment of riches with three free alternatives, and one commercial and one shareware version. -<p><i>CM-super</i> is an +<p/><i>CM-super</i> is an auto-traced set which encompasses all of the T1 and TS1 encodings as well as the T2* series (the family of encodings that cover languages based on Cyrillic alphabets). These fonts are pretty easy to install (the installation instructions are clear), but they are huge: don’t try to install them if you’re short of disc space. -<p><i>CM-LGC</i> is a similar “super-font” set, but of much more +<p/><i>CM-LGC</i> is a similar “super-font” set, but of much more modest size; it covers T1, TS1 and T2{A} encodings (as does <i>CM-super</i>, and also covers the LGR encoding (for typesetting Greek, based on Claudio Beccari’s Metafont @@ -34,10 +34,10 @@ the sizes supported by the original EC (a huge range); scaling. There is an inevitable loss of quality inherent in this approach, but for the disc-space-challenged machine, <i>CM-LGC</i> is an obvious choice. -<p><i>Tt2001</i> is a simple scan of the EC and TC +<p/><i>Tt2001</i> is a simple scan of the EC and TC fonts, and has some virtues — it’s noticeably smaller than <i>CM-super</i> while being less stark than <i>CM-LGC</i>. -<p><i>Latin</i> <i>Modern</i> is produced using the +<p/><i>Latin</i> <i>Modern</i> is produced using the program <a href="FAQ-textrace.html"><i>MetaType1</i></a>. The <i>Latin</i> <i>Modern</i> set comes with T1, TS1 LY1 encoded variants (as well as a variant using the Polish @@ -50,7 +50,7 @@ design sizes as is <i>CM-LGC</i> — <i>Latin</i> original <i>CM</i> fonts. It’s hard to argue with the choice: Knuth’s range of sizes has stood the test of time, and is one of the bases on which the excellence of the TeX system rests. -<p><a href="FAQ-virtualfonts.html">Virtual fonts</a> help us deal with the problem, +<p/><a href="FAQ-virtualfonts.html">Virtual fonts</a> help us deal with the problem, since they allow us to map “bits of DVI file” to single characters in the virtual font; so we can create an “é” character by recreating the DVI commands that would result from the code @@ -63,7 +63,7 @@ character, you’ll find something unexpected (typically the accent and the ‘base’ characters separated by a space) when you <i>paste</i> the result. However, if you can live with this difficulty, virtual fonts are a useful and straightforward solution to the problem. -<p>There are two virtual-font offerings of CM-based 8-bit +<p/>There are two virtual-font offerings of CM-based 8-bit fonts — the <i>ae</i> (“almost EC”) and <i>zefonts</i> sets; the <i>zefonts</i> set has wider coverage (though the <i>ae</i> set may be extended to offer guillemets by @@ -72,18 +72,18 @@ as <code>eth</code> and <code>thorn</code> (used in, for example, in Icelandic), but the <i>aecompl</i> package works with the <i>ae</i> fonts to provide the missing characters from the EC fonts (i.e., as bitmaps). -<p>The sole remaining commercial CM-like 8-bit font comes from +<p/>The sole remaining commercial CM-like 8-bit font comes from Micropress, who offer the complete EC set in Type 1 format, as part of their range of outline versions of fonts that were originally distributed in Metafont format. See <a href="FAQ-commercial.html">“commercial distributions”</a>. -<p>The shareware +<p/>The shareware <a href="FAQ-TeXsystems.html">BaKoMa TeX distribution</a> offers a set of Type 1 EC fonts, as an extra shareware option. (As far as the present author can tell, these fonts are <em>only</em> available to users of BaKoMa TeX: they are stored in an archive format that seems not to be publicly available.) -<p>Finally, you can use one of the myriad text fonts available in Type 1 +<p/>Finally, you can use one of the myriad text fonts available in Type 1 format (with appropriate PSNFSS metrics for T1 encoding, or metrics for some other 8-bit encoding such as LY1). However, if you use someone else’s text font (even something as simple as @@ -94,7 +94,7 @@ see <a href="FAQ-psfchoice.html">“choice of scalable fonts”</a>. <dt><tt><i>ae fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ae.zip">fonts/ae</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ae.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ae/">browse</a>) <dt><tt><i>aecompl.sty</i></tt><dd>Distributed with <a href="ftp://cam.ctan.org/tex-archive/fonts/ae.zip">fonts/ae</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ae.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ae/">browse</a>) <dt><tt><i>aeguill.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/aeguill.zip">macros/latex/contrib/aeguill</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/aeguill.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/aeguill/">browse</a>) -<dt><tt><i>BaKoMa fonts</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/systems/win32/bakoma/fonts/">nonfree/systems/win32/bakoma/fonts/</a> +<dt><tt><i>BaKoMa fonts</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/systems/win32/bakoma/fonts/">systems/win32/bakoma/fonts/</a> <dt><tt><i>CM-LGC fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-lgc.zip">fonts/ps-type1/cm-lgc</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-lgc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-lgc/">browse</a>) <dt><tt><i>CM-super fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.zip">fonts/ps-type1/cm-super</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/cm-super.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/cm-super/">browse</a>) (beware: very large download) @@ -102,5 +102,5 @@ see <a href="FAQ-psfchoice.html">“choice of scalable fonts”</a>. <dt><tt><i>tt2001 fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/tt2001.zip">fonts/ps-type1/tt2001</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/ps-type1/tt2001.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/ps-type1/tt2001/">browse</a>) <dt><tt><i>zefonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/zefonts.zip">fonts/zefonts</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/zefonts.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/zefonts/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=type1T1">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=type1T1</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=type1T1">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=type1T1</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typebooks.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typebooks.html index 62aa732d656..149c2bebcb0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typebooks.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typebooks.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label typebooks</title> </head><body> <h3>Books on Type</h3> -<p> The following is a partial listing of books on typography in general. +<p/> The following is a partial listing of books on typography in general. Of these, Bringhurst seems to be the one most often recommended. <dl> <dt>The Elements of Typographic Style<dd>by Robert Bringhurst @@ -22,7 +22,7 @@ Of these, Bringhurst seems to be the one most often recommended. (<a href="http://www.kindersleyworkshop.co.uk/">The Cardozo Kindersley Workshop</a> 2001, ISBN 1-874426-139) </dl> -<p> There are many catalogues of type specimens but the following books provide +<p/> There are many catalogues of type specimens but the following books provide a more interesting overall view of types in general and some of their history. <dl> <dt>Alphabets Old & New<dd>by Lewis F. Day @@ -44,8 +44,8 @@ a more interesting overall view of types in general and some of their history. <dt>A Short History of the Printed Word<dd>by Warren Chappell and Robert Bringhurst (Hartley & Marks, 1999, ISBN 0-88179-154-7) </dl> -<p> The above lists are limited to books published in English. Typographic +<p/> The above lists are limited to books published in English. Typographic styles are somewhat language-dependent, and similarly the ‘interesting’ fonts depend on the particular writing system involved. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typebooks">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typebooks</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typebooks">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typebooks</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typend.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typend.html index 7111e0d217c..76ef208ec98 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typend.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typend.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label typend</title> </head><body> <h3>“Please type a command or say <code>\</code><code>end</code>”</h3> -<p>Sometimes, when you are running (La)TeX, it will abruptly stop and +<p/>Sometimes, when you are running (La)TeX, it will abruptly stop and present you with a prompt (by default, just a <code>*</code> character). Many people (including this author) will reflexively hit the ‘return’ key, pretty much immediately, and of course this is no help at all — @@ -11,7 +11,7 @@ TeX just says: (Please type a command or say `\end') </pre> and prompts you again. -<p>What’s happened is that your (La)TeX file has finished prematurely, +<p/>What’s happened is that your (La)TeX file has finished prematurely, and TeX has fallen back to a supposed including file, from the terminal. This could have happened simply because you’ve omitted the <code>\</code><code>bye</code> (Plain TeX), <code>\</code><code>end{document}</code> (LaTeX), or @@ -19,19 +19,19 @@ whatever. Other common errors are failure to close the braces round a command’s argument, or (in LaTeX) failure to close a verbatim environment: in such cases you’ve already read and accepted an error message about encountering end of file while scanning something. -<p>If the error is indeed because you’ve forgotten to end your document, +<p/>If the error is indeed because you’ve forgotten to end your document, you can insert the missing text: if you’re running Plain TeX, the advice, to “say <code>\</code><code>end</code>” is good enough: it will kill the run; if you’re running LaTeX, the argument will be necessary: <code>\</code><code>end{document}</code>. -<p>However, as often as not this isn’t the problem, and (short of +<p/>However, as often as not this isn’t the problem, and (short of debugging the source of the document before ending) brute force is probably necessary. Excessive force (killing the job that’s running TeX) is to be avoided: there may well be evidence in the -<code>.log</code> file that will be useful in determining what the problem is — -so the aim is to persuade TeX to shut itself down and hence flush -all log output to file. -<p>If you can persuade TeX to read it, an end-of-file indication +<code>.log</code> file that will be useful in determining what the +problem is — so the aim is to persuade TeX to shut itself down +and hence flush all log output to file. +<p/>If you can persuade TeX to read it, an end-of-file indication (control-<code>D</code> under Unix, control-<code>Z</code> under Windows) will provoke TeX to report an error and exit immediately. Otherwise you should attempt to provoke an error dialogue, from which you can exit (using @@ -39,5 +39,5 @@ the <code>x</code> ‘command’). An accessible error could well be in illegal character: what it is will depend on what macros you are running. If you can’t make that work, try a silly command name or two. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typend">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typend</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typend">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typend</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typo-style.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typo-style.html index e0e65e0f561..37d738baf04 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typo-style.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-typo-style.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label typo-style</title> </head><body> <h3>Typography tutorials</h3> -<p>There’s also (at least one) typographic style tutorial available on +<p/>There’s also (at least one) typographic style tutorial available on the Web, the excellent “<a href="http://www.nbcs.rutgers.edu/~hedrick/typography/typography.janson-syntax.107514.pdf">Guidelines for Typography in NBCS</a>”. In fact, its @@ -14,12 +14,12 @@ ambition to supplant such excellent books as <a href="FAQ-typebooks.html">Bringhurst’s</a>, but the document (though it does contain its Rutgers-local matter) is a fine introduction to the issues of producing readable documents. -<p>Peter Wilson’s manual for his <i>memoir</i> class has a lengthy +<p/>Peter Wilson’s manual for his <i>memoir</i> class has a lengthy introductory section on typographic considerations, which is a fine tutorial, written by someone who is aware of the issues as they apply to (La)TeX users. <dl> <dt><tt><i>memoir distribution</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/memoir.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/memoir/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typo-style">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typo-style</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typo-style">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typo-style</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underline.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underline.html index 122b9ca74c5..f3d4e83a58d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underline.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underline.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label underline</title> </head><body> <h3>Underlined text won’t break</h3> -<p>Knuth made no provision for underlining text: he took the view that +<p/>Knuth made no provision for underlining text: he took the view that underlining is not a typesetting operation, but rather one that provides emphasis on typewriters, which typically offer but one typeface. The corresponding technique in typeset text is to switch from upright to italic text (or vice-versa): the LaTeX command <code>\</code><code>emph</code> does just that to its argument. -<p>Nevertheless, typographically illiterate people (such as those that +<p/>Nevertheless, typographically illiterate people (such as those that specify double-spaced <a href="FAQ-linespace.html">thesis styles</a>) continue to require underlining of us, so LaTeX as distributed @@ -16,7 +16,7 @@ defines an <code>\</code><code>underline</code> command that applies the mathema ‘underbar’ operation to text. This technique is not entirely satisfactory, however: the text gets stuck into a box, and won’t break at line end. -<p>Two packages are available that solve this problem. The +<p/>Two packages are available that solve this problem. The <i>ulem</i> package redefines the <code>\</code><code>emph</code> command to underline its argument; the underlined text thus produced behaves as ordinary emphasised text, and will break over the @@ -24,7 +24,7 @@ end of a line. (The package is capable of other peculiar effects, too: read its documentation, contained within the file itself.) The <i>soul</i> package defines an <code>\</code><code>ul</code> command (after which the package is, in part, named) that underlines running text. -<p>Beware of <i>ulem</i>’s default behaviour, which is to convert the +<p/>Beware of <i>ulem</i>’s default behaviour, which is to convert the <code>\</code><code>emph</code> command into an underlining command; this can be avoided by loading the package with: <pre> @@ -35,5 +35,5 @@ Documentation of <i>ulem</i> is in the package itself. <dt><tt><i>ulem.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/ulem.sty">macros/latex/contrib/misc/ulem.sty</a> <dt><tt><i>soul.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/soul.zip">macros/latex/contrib/soul</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/soul.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/soul/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=underline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=underline</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=underline">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=underline</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underscore.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underscore.html index 3db463adced..6e76c707fb7 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underscore.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-underscore.html @@ -2,26 +2,26 @@ <title>UK TeX FAQ -- question label underscore</title> </head><body> <h3>How to use the underscore character</h3> -<p>The underscore character <code>_</code> is ordinarily used in +<p/>The underscore character <code>_</code> is ordinarily used in TeX to indicate a subscript in maths mode; if you type <code>_</code> in the course of ordinary text, TeX will complain. If you’re writing a document which will contain a large number of underscore characters, the prospect of typing <code>\</code><code>_</code> (or, worse, <code>\</code><code>textunderscore</code>) for every one of them will daunt most ordinary people. -<p>Moderately skilled macro programmers can readily generate a quick hack +<p/>Moderately skilled macro programmers can readily generate a quick hack to permit typing <code>_</code> to mean ‘text underscore’. However, the code <em>is</em> somewhat tricky, and more importantly there are significant points where it’s easy to get it wrong. There is therefore a package <i>underscore</i> which provides a general solution to this requirement. -<p>There is a problem, though: OT1 text fonts don’t contain an +<p/>There is a problem, though: OT1 text fonts don’t contain an underscore character, unless they’re in the typewriter version of the encoding (used by fixed-width fonts such as <code>cmtt</code>). So either you must ensure that your underscore characters only occur in text set in a typewriter font, or you must use a fuller encoding, such as T1, which has an underscore character in every font. -<p>If the requirement is only for occasional uses of underscores, it may +<p/>If the requirement is only for occasional uses of underscores, it may be acceptable to use the following construct: <blockquote> <pre> @@ -37,5 +37,5 @@ about section headings and the like. <dl> <dt><tt><i>underscore.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/underscore.sty">macros/latex/contrib/misc/underscore.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=underscore">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=underscore</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=underscore">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=underscore</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-unkgrfextn.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-unkgrfextn.html index 9626ce6f63a..e7a74af855f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-unkgrfextn.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-unkgrfextn.html @@ -2,25 +2,46 @@ <title>UK TeX FAQ -- question label unkgrfextn</title> </head><body> <h3>“Unknown graphics extension”</h3> -<p>The LaTeX graphics package deals with several different types of +<p/>The LaTeX graphics package deals with several different types of DVI (or other) output drivers; each one of them has a potential to deal with a different selection of graphics formats. The package therefore has to be told what graphics file types its output driver knows about; this is usually done in the <<i>driver</i>><code>.def</code> file corresponding to the output driver you’re using. -<p>The error message arises, then, if you have a graphics file whose +<p/>The error message arises, then, if you have a graphics file whose extension doesn’t correspond with one your driver knows about. Most often, this is because you’re being optimistic: asking <i>dvips</i> to deal with a <code>.png</code> file, or PDFTeX to deal with a <code>.eps</code> file: the solution in this case is to transform the graphics file to a format your driver knows about. -<p>If you happen to <em>know</em> that your device driver deals with the +<p/>If you happen to <em>know</em> that your device driver deals with the format of your file, you are probably falling foul of a limitation of the file name parsing code that the graphics package uses. Suppose you want to include a graphics file <i>home.bedroom.eps</i> using the <i>dvips</i> driver; the package will conclude that your file’s -extension is <i>.bedroom.eps</i>, and will complain. To get around -this limitation, you have three alternatives: +extension is <code>.bedroom.eps</code>, and will complain. +<p/>The <i>grffile</i> package deals with the last problem (and +others — see the package documentation); using the package, you may +write: +<blockquote> +<pre> +\usepackage{graphicx} +\usepackage{grffile} +... +\includegraphics{home.bedroom.eps} +</pre> +</blockquote><p> +or you may even write +<blockquote> +<pre> +\includegraphics{home.bedroom} +</pre> +</blockquote><p> +and <i>graphicx</i> will find a <code>.eps</code> or <code>.pdf</code> +(or whatever) version, according to what version of (La)TeX you’re +running. +<p/>If for some reason you can’t use <i>grffile</i>, you have three +unsatisfactory alternatives: <ul> <li> Rename the file — for example <i>home.bedroom.eps</i>-> <i>home-bedroom.eps</i> @@ -36,5 +57,8 @@ this limitation, you have three alternatives: \includegraphics[type=eps,ext=.eps,read=.eps]{home.bedroom} </pre> </ul> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=unkgrfextn">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=unkgrfextn</a> +<dl> +<dt><tt><i>grffile.sty</i></tt><dd>Distributed as part of the <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/oberdiek.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/oberdiek/">browse</a>) collection +</dl> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=unkgrfextn">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=unkgrfextn</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uploads.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uploads.html index b7b308ee26c..ecce4105cf8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uploads.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uploads.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label uploads</title> </head><body> <h3>Contributing a file to the archives</h3> -<p>You have something to submit to the archive — great! Before we even +<p/>You have something to submit to the archive — great! Before we even start, here’s a check-list of things to sort out: <ol> <li> Licence: in the spirit of TeX, we hope for free software; in @@ -11,9 +11,9 @@ start, here’s a check-list of things to sort out: <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/licenses.html">list of “standard” licence statements</a>. <li> Documentation: it’s good for users to be able to browse documentation before downloading a package. You need at least a - plain text <i>README</i> file (exactly that name); best is a + plain text <i>README</i> file (exactly that name); in addition a PDF file of the package documentation, prepared for screen - reading. + reading, is highly desirable. <li> Name: endless confusion is caused by name clashes. If your package has the same name as one already on CTAN, or if your package installation generates files of the same name as something @@ -22,34 +22,42 @@ start, here’s a check-list of things to sort out: they may nag you to change the name, or to negotiate a take-over with the author of the original package. <a href="FAQ-findfiles.html">Browse the archive</a> to ensure uniqueness. -<p> The name you choose should also (as far as possible) be somewhat +<p/> The name you choose should also (as far as possible) be somewhat descriptive of what your submission actually <em>does</em>; while “descriptiveness” is to some extent in the eye of the beholder, it’s clear that names such as <i>mypackage</i> or <i>jiffy</i> aren’t suitable. </ol> -<p>If you are able to use anonymous <i>ftp</i>, get yourself a copy of -the file <i>README.uploads</i> from any -<a href="FAQ-archives.html">CTAN archive</a>. The file tells you +<p/>If you are able to use anonymous <i>ftp</i>, you can upload that +way. The file <i>README.uploads</i> on CTAN tells you where to upload, what to upload, and how to notify the CTAN management about what you want doing with your upload. -<p>You may also upload via the Web: each of the principle CTAN +<p/>You may also upload via the Web: each of the principal CTAN sites offers an upload page — choose from <a href="http://www.ctan.org/upload.html">http://www.ctan.org/upload.html</a>, <a href="http://www.dante.de/CTAN/upload.html">http://www.dante.de/CTAN/upload.html</a> or <a href="http://www.tex.ac.uk/upload.html">http://www.tex.ac.uk/upload.html</a>; the pages lead you through the -process, showing you the information you need to supply. -<p>If you can use neither of these methods, ask advice of the +process, showing you the information you need to supply. This method +enforces one file per upload: if you had intended to upload lots of +files, you need to bundle them into an ‘archive’ file of some sort; +acceptable formats are <code>.zip</code> and <code>.tar.gz</code> (or +<code>.tar.bz2</code>). +<p/>If you can use neither of these methods, or if you find something +confusing, ask advice of the <a href="mailto:ctan@dante.de">CTAN management</a>: -if the worst comes to the worst, it may be possible to mail a contribution. -<p>If it’s appropriate (if your package is large, or regularly updated), +if the worst comes to the worst, it may be possible to mail a +contribution. This really is a last-resort route: none of the +CTAN sites is anyone’s regular workstation, so if you mail to +one of the maintainers, that maintainer then has to upload to +CTAN. +<p/>If it’s appropriate (if your package is large, or regularly updated), the CTAN management can arrange to <i>mirror</i> your contribution direct into the archive. At present this may only be -done if your contribution is available via <code>ftp</code>, and of course the -directory structure on your archive must ‘fit’. +done if your contribution is available via <i>ftp</i>, and of +course the directory structure on your repository must ‘fit’. <dl> <dt><tt><i>README.uploads</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/README.uploads">README.uploads</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=uploads">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=uploads</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=uploads">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=uploads</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-upquot.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-upquot.html index 541f1c1994d..2a664630d7e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-upquot.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-upquot.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label upquot</title> </head><body> <h3>Realistic quotes for verbatim listings</h3> -<p>The <code>cmtt</code> font has “curly” quotes, +<p/>The <code>cmtt</code> font has “curly” quotes, which are pleasing on the eye, but don’t really tally with what one sees on a modern <i>xterm</i>. -<p>The appearance of these quotes is critical in program listings, +<p/>The appearance of these quotes is critical in program listings, particularly in those of Unix-like shell scripts. The <i>upquote</i> package modifies the behaviour of the <code>verbatim</code> environment so that the output is a clearer @@ -14,5 +14,5 @@ representation of what the user must type. <dl> <dt><tt><i>upquote.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/upquote/upquote.sty">macros/latex/contrib/upquote/upquote.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=upquot">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=upquot</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=upquot">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=upquot</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-useMF.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-useMF.html index 6a07528d172..9b13dc58fe0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-useMF.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-useMF.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label useMF</title> </head><body> <h3>Getting Metafont to do what you want</h3> -<p>Metafont allows you to create your own fonts, and most TeX users +<p/>Metafont allows you to create your own fonts, and most TeX users will never need to use it. Metafont, unlike TeX, requires some customisation: each output device for which you will be generating fonts needs a mode associated with it. Modes are defined using the @@ -37,7 +37,7 @@ similar; for example, it will be on MSDOS systems) which should be moved to the directory containing the base files on your system (note that some systems have two or more such directories, one for each ‘size’ of Metafont used). -<p>Now you need to make sure Metafont loads this new base when it starts up. If +<p/>Now you need to make sure Metafont loads this new base when it starts up. If Metafont loads the <code>plain</code> base by default on your system, then you’re ready to go. Under Unix (using the default <i>web2c</i> distribution @@ -45,7 +45,7 @@ distribution this does indeed happen, but we could for instance define a command <i>mf</i> which executes <code>virmf &plain</code> loading the <code>plain</code> base file. -<p>The usual way to create a font with <code>plain</code> Metafont is to start +<p/>The usual way to create a font with <code>plain</code> Metafont is to start it with the line <pre> @@ -71,7 +71,7 @@ escaped, so this would typically look something like <pre> mf '\mode=epson; mag=magstep 1; input cmr10' </pre> -<p>If you don’t have <i>inimf</i> or need a special mode that isn’t +<p/>If you don’t have <i>inimf</i> or need a special mode that isn’t in the base, you can put its commands in a file (<em>e.g.</em>, <i>ln03.mf</i>) and invoke it on the fly with the <code>\smode</code> command. For example, to create <i>cmr10.300gf</i> for an LN03 printer, using @@ -97,10 +97,10 @@ prove useful if you acquire a new printer and want to experiment with parameters, or for some other reason are regularly editing the parameters you’re using. Once you’ve settled on an appropriate set of parameters, you should use them to rebuild the base file that you use. -<p>Other sources of help are mentioned in +<p/>Other sources of help are mentioned in <a href="FAQ-mfptutorials.html">Metafont and MetaPost Tutorials</a>. <dl> <dt><tt><i>modes.mf</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/modes/modes.mf">fonts/modes/modes.mf</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=useMF">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=useMF</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=useMF">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=useMF</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usebibtex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usebibtex.html index 62e7c62c1d0..29f3864ad4c 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usebibtex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usebibtex.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label usebibtex</title> </head><body> <h3>“Normal” use of BibTeX from LaTeX</h3> -<p>To create a bibliography for your document, you need to perform a +<p/>To create a bibliography for your document, you need to perform a sequence of steps, some of which seem a bit odd. If you choose to use BibTeX, the sequence is: -<p>First: you need a BibTeX bibliography file (a <code>.bib</code> file) — see +<p/>First: you need a BibTeX bibliography file (a <code>.bib</code> file) — see “<a href="FAQ-buildbib.html">creating a BibTeX file</a>”. -<p>Second: you must write your LaTeX document to include a declaration +<p/>Second: you must write your LaTeX document to include a declaration of the ‘style’ of bibliography, citations, and a reference to the bibliography file mentioned in the step 1. So we may have a LaTeX file containing: @@ -27,24 +27,24 @@ Note: we have bibliography style <i>plain</i>, above, which is nearly the simplest of the lot: a sample text, showing the sorts of style choices available, can be found on Ken Turner’s web site: <a href="http://www.cs.stir.ac.uk/~kjt/software/latex/showbst.html">http://www.cs.stir.ac.uk/~kjt/software/latex/showbst.html</a> -<p>Third: you must process the file. +<p/>Third: you must process the file. <blockquote> <pre> latex myfile </pre> </blockquote><p> As LaTeX processes the file, the <code>\</code><code>bibliographystyle</code> command -writes a note of the style to the <code>.aux</code> file; each <code>\</code><code>cite</code> command -writes a note of the citation to the <code>.aux</code> file, and the -<code>\</code><code>bibliography</code> command writes a note of which <code>.bib</code> file is to be -used, to the <code>.aux</code> file. -<p>Note that, at this stage, LaTeX isn’t “resolving” any of the +writes a note of the style to the <code>.aux</code> file; each +<code>\</code><code>cite</code> command writes a note of the citation to the +<code>.aux</code> file, and the <code>\</code><code>bibliography</code> command writes a note +of which <code>.bib</code> file is to be used, to the <code>.aux</code> file. +<p/>Note that, at this stage, LaTeX isn’t “resolving” any of the citations: at every <code>\</code><code>cite</code> command, LaTeX will warn you of the undefined citation, and when the document finishes, there will be a further warning of undefined references. -<p> +<p/> -<p>Fourth: you must run BibTeX: +<p/>Fourth: you must run BibTeX: <blockquote> <pre> bibtex myfile @@ -54,28 +54,28 @@ Don’t try to tell BibTeX anything but the file name: say <code>bibtex myfile.aux</code> (because you know it’s going to read the <code>.aux</code> file) and BibTeX will blindly attempt to process <code>myfile.aux.aux</code>. -<p>BibTeX will scan the <code>.aux</code> file; it will find which bibliography +<p/>BibTeX will scan the <code>.aux</code> file; it will find which bibliography style it needs to use, and will “compile” that style; it will note the citations; it will find which bibliography files it needs, and will run through them matching citations to entries in the bibliography; and finally it will sort the entries that have been cited (if the bibliography style specifies that they should be sorted), and outputs the resulting details to a <code>.bbl</code> file. -<p>Fifth: you run LaTeX again. It warns, again, that each citation is +<p/>Fifth: you run LaTeX again. It warns, again, that each citation is (still) undefined, but when it gets to the <code>\</code><code>bibliography</code> command, it finds a <code>.bbl</code> file, and reads it. As it encounters each <code>\</code><code>bibitem</code> command in the file, it notes a definition of the citation. -<p>Sixth: you run LaTeX yet again. This time, it finds values for all +<p/>Sixth: you run LaTeX yet again. This time, it finds values for all the citations, in its <code>.aux</code> file. Other things being equal, you’re done... until you change the file. -<p>If, while editing, you change any of the citations, or add new ones, +<p/>If, while editing, you change any of the citations, or add new ones, you need to go through the process above from steps 3 (first run of LaTeX) to 6, again, before the document is once again stable. These four mandatory runs of LaTeX make processing a document with a bibliography even more tiresome than the normal two runs required to resolve labels. -<p>To summarise: processing to resolve citations requires: LaTeX; +<p/>To summarise: processing to resolve citations requires: LaTeX; BibTeX; LaTeX; LaTeX. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usebibtex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usebibtex</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usebibtex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usebibtex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uselmfonts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uselmfonts.html index 604f8e5530f..aa74b0f99cc 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uselmfonts.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-uselmfonts.html @@ -2,27 +2,27 @@ <title>UK TeX FAQ -- question label uselmfonts</title> </head><body> <h3>Using the Latin Modern fonts</h3> -<p>The <i>lm</i> fonts are an exciting addition to +<p/>The <i>lm</i> fonts are an exciting addition to the armoury of the (La)TeX user: high quality outlines of fonts that were until recently difficult to obtain, all in a free and relatively compact package. However, the spartan information file that comes with the fonts remarks “It is presumed that a potential user knows what to do with all these files”. This answer aims to fill in the requirements: the job is really not terribly difficult. -<p>Note that teTeX distributions, from version 3.0, already have the +<p/>Note that teTeX distributions, from version 3.0, already have the <i>lm</i> fonts: all you need do is use them. The fonts may also be installed via the package manager, in a current MiKTeX system. The remainder of this answer, then, is for people who don’t use such systems. -<p>The font (and related) files appear on CTAN as a set of +<p/>The font (and related) files appear on CTAN as a set of single-entry <a href="FAQ-tds.html">TDS trees</a> — <i>fonts</i>, <i>dvips</i>, <i>tex</i> and <i>doc</i>. The <i>doc</i> subtree really need not be copied (it’s really a pair of sample files), but copy the other three into your existing Local <code>$TEXMF</code> tree, and -<a href="FAQ-instpackages.html">update the filename database</a>. -<p>Now, incorporate the fonts in the set searched by PDFLaTeX, +<a href="FAQ-inst-wlcf.html">update the filename database</a>. +<p/>Now, incorporate the fonts in the set searched by PDFLaTeX, <i>dvips</i>, <i>dvipdfm</i>, your previewers and Type 1-to-PK conversion programs, by <ul> @@ -43,7 +43,7 @@ Type 1-to-PK conversion programs, by Then execute the command <code>initexmf --mkmaps</code>, and the job is done. </ul> -<p>To use the fonts in a LaTeX document, you should +<p/>To use the fonts in a LaTeX document, you should <blockquote> <code>\</code><code>usepackage{lmodern}</code> </blockquote><p> @@ -62,6 +62,6 @@ no support for using fonts according to the OT1 encoding. <dl> <dt><tt><i>Latin Modern fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/lm.zip">fonts/lm</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/lm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/lm/">browse</a>) </dl> -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=uselmfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=uselmfonts</a> +<p/> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=uselmfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=uselmfonts</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepictex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepictex.html index 0ea68358b47..9f5bf31140e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepictex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepictex.html @@ -1,12 +1,12 @@ <head> <title>UK TeX FAQ -- question label usepictex</title> </head><body> -<h3>Why can’t I load PiCTeX?</h3> -<p>PiCTeX is a resource hog; fortunately, most modern TeX +<h3>Why can’t I load PicTeX?</h3> +<p/>PicTeX is a resource hog; fortunately, most modern TeX implementations offer generous amounts of space, and most modern computers are pretty fast, so users aren’t too badly affected by its performance. -<p>However, PiCTeX has the further unfortunate tendency to fill up +<p/>However, PicTeX has the further unfortunate tendency to fill up TeX’s fixed-size arrays — notably the array of 256 ‘dimension’ registers. This is a particular problem when you’re using <i>pictex.sty</i> with LaTeX and some other packages that also need @@ -23,28 +23,28 @@ extending TeX itself. <a href="FAQ-etex.html">e-TeX</a> and <a href="FAQ-omegaleph.html">Omega</a> both do this, as does <a href="FAQ-commercial.html">MicroPress Inc’s VTeX</a>. -<p>It’s actually quite practical (with most modern distributions) to use +<p/>It’s actually quite practical (with most modern distributions) to use e-TeX’s extended register set: use package <i>etex</i> (which comes with e-TeX distributions) and the allocation mechanism is -altered to cope with the larger register set: PiCTeX will now load. -<p>If you’re in some situation where you can’t use e-TeX, you need to change -PiCTeX; unfortunately PiCTeX’s author is no longer active in the +altered to cope with the larger register set: PicTeX will now load. +<p/>If you’re in some situation where you can’t use e-TeX, you need to change +PicTeX; unfortunately PicTeX’s author is no longer active in the TeX world, so one must resort to patching. There are two solutions available. -<p>The ConTeXt module <i>m-pictex.tex</i> (for Plain TeX and +<p/>The ConTeXt module <i>m-pictex.tex</i> (for Plain TeX and variants) or the corresponding LaTeX <i>m-pictex</i> package provide an ingenious solution to the problem based on hacking the code of <code>\</code><code>newdimen</code> itself. -<p>Alternatively, Andreas Schell’s <i>pictexwd</i> and related -packages replace PiCTeX with a version that uses 33 fewer +<p/>Alternatively, Andreas Schell’s <i>pictexwd</i> and related +packages replace PicTeX with a version that uses 33 fewer <code>\</code><code>dimen</code> registers; so use <i>pictexwd</i> in place of <i>pictex</i> (either as a LaTeX package, or as a file to read into Plain TeX). -<p>And how does one use PiCTeX anyway, given that the +<p/>And how does one use PicTeX anyway, given that the manual is so <a href="FAQ-docpictex.html">hard to come by</a>? Fortunately for us all, the <i>MathsPic</i> system may be used to translate a somewhat different language into -PiCTeX commands; and the <i>MathsPic</i> manual is free (and +PicTeX commands; and the <i>MathsPic</i> manual is free (and part of the distribution). <i>MathsPic</i> is available either as a <i>Basic</i> program for DOS, or as a <i>Perl</i> program for other systems (including Windows, nowadays). @@ -54,5 +54,5 @@ program for other systems (including Windows, nowadays). <dt><tt><i>MathsPic</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/graphics/mathspic.zip">graphics/mathspic</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/mathspic.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/mathspic/">browse</a>) <dt><tt><i>pictexwd.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/graphics/pictex/addon.zip">graphics/pictex/addon</a> (<a href="ftp://cam.ctan.org/tex-archive/graphics/pictex/addon.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/graphics/pictex/addon/">browse</a>) </dl> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepictex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepictex</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepictex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepictex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepsfont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepsfont.html index 512f60c3142..56621c87624 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepsfont.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepsfont.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label usepsfont</title> </head><body> <h3>Using PostScript fonts with TeX</h3> -<p>In order to use PostScript fonts, TeX needs +<p/>In order to use PostScript fonts, TeX needs <em>metric</em> (called TFM) files. Several sets of metrics are available from the archives; for mechanisms for generating new ones, see <a href="FAQ-metrics.html">metrics for PostScript fonts</a>. You @@ -10,7 +10,7 @@ also need the fonts themselves; PostScript printers come with a set of fonts built in, but to extend your repertoire you almost invariably need to buy from one of the many commercial font vendors (see, for example, <a href="FAQ-psfchoice.html">“choice of fonts”</a>). -<p>If you use LaTeX2e, the best way to get PostScript fonts into your +<p/>If you use LaTeX2e, the best way to get PostScript fonts into your document is to use the PSNFSS package maintained by Walter Schmidt. The LaTeX3 project team declare that PSNFSS is “required”, and bug reports may be submitted via the @@ -28,23 +28,23 @@ and font description (<i>.fd</i>) files for each font family you want to use. For convenience, metrics for the ‘common 35’ PostScript fonts found in most PostScript printers are provided with PSNFSS, packaged as the “Laserwriter set”. -<p>For older versions of LaTeX there are various schemes, of which the +<p/>For older versions of LaTeX there are various schemes, of which the simplest to use is probably the PSLaTeX macros distributed with <i>dvips</i>. -<p>For Plain TeX, you load whatever fonts you like; if the encoding of +<p/>For Plain TeX, you load whatever fonts you like; if the encoding of the fonts is not the same as Computer Modern it will be up to you to redefine various macros and accents, or you can use the font re-encoding mechanisms available in many drivers and in <i>ps2pk</i> and <i>afm2tfm</i>. -<p>Victor Eijkhout’s <a href="FAQ-lollipop.html">Lollipop package</a> +<p/>Victor Eijkhout’s <a href="FAQ-lollipop.html">Lollipop package</a> supports declaration of font families and styles in a similar way to LaTeX’s NFSS, and so is easy to use with PostScript fonts. -<p>Some common problems encountered are discussed elsewhere +<p/>Some common problems encountered are discussed elsewhere (see <a href="FAQ-psfontprob.html">problems with PS fonts</a>). <dl> <dt><tt><i>Metrics for the ‘Laserwriter’ set of 35 fonts</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss/lw35nfss.zip">macros/latex/required/psnfss/lw35nfss.zip</a> -<dt><tt><i>lollipop</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/nonfree/macros/lollipop.zip">nonfree/macros/lollipop</a> (<a href="ftp://cam.ctan.org/tex-archive/nonfree/macros/lollipop.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/nonfree/macros/lollipop/">browse</a>) +<dt><tt><i>lollipop</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/lollipop.zip">macros/lollipop</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/lollipop.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/lollipop/">browse</a>) <dt><tt><i>psnfss</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss.zip">macros/latex/required/psnfss</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/psnfss.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/psnfss/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepsfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepsfont</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepsfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=usepsfont</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidcol.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidcol.html index b7fa1c548c9..7ddbf95f1b8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidcol.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidcol.html @@ -2,15 +2,15 @@ <title>UK TeX FAQ -- question label varwidcol</title> </head><body> <h3>Variable-width columns in tables</h3> -<p>This is a slightly different take on the problem addressed in +<p/>This is a slightly different take on the problem addressed in “<a href="FAQ-fixwidtab.html">fixed-width tables</a>” — here we have a column whose size we can’t absolutely predict when we design the document. -<p>While the basic techniques (the <i>tabularx</i>, <i>tabulary</i> +<p/>While the basic techniques (the <i>tabularx</i>, <i>tabulary</i> and <i>ltxtable</i> packages) are the same for this problem as for the fixed-width <em>table</em> problem, there’s one extra tool that we can call to our aid, which may be preferable in some situations. -<p>Suppose we have data in one column which we read from an external +<p/>Suppose we have data in one column which we read from an external source, and the source itself isn’t entirely predictable. The data in the column may end up pretty narrow in every row of the table, or it may be wide enough that the table would run over the edge of the page; @@ -19,7 +19,7 @@ in case”, by defining a fixed size for the table. We would like the column to be as small as possible, but have the possibility to spread to a maximum width and (if even that width is exceeded) turn into a <code>p</code>-style column. -<p>The <i>varwidth</i> package, discussed in +<p/>The <i>varwidth</i> package, discussed in “<a href="FAQ-varwidth.html">automatic sizing of minipages</a>”, provides a solution. If you load it together with the LaTeX “required” <i>array</i> package, i.e.: @@ -57,5 +57,5 @@ a second line in the third row. <dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) <dt><tt><i>varwidth.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/varwidth.sty">macros/latex/contrib/misc/varwidth.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidcol">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidcol</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidcol">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidcol</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidth.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidth.html index 2ea18c72591..e07dcc94418 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidth.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-varwidth.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label varwidth</title> </head><body> <h3>Automatic sizing of <code>minipage</code></h3> -<p>The <code>minipage</code> environment requires you to specify the +<p/>The <code>minipage</code> environment requires you to specify the width of the “page” you’re going to create. This is sometimes inconvenient: you would like to occupy less space, if possible, but <code>minipage</code> sets a box that is exactly the width you specified. -<p>The <i>pbox</i> package defines a <code>\</code><code>pbox</code> whose width is exactly +<p/>The <i>pbox</i> package defines a <code>\</code><code>pbox</code> whose width is exactly that of the longest enclosed line, subject to a maximum width that you give it. So while <code>\</code><code>parbox{2cm}{Hello\\world!}</code> produces a box of width exactly <code>2cm</code>, @@ -18,7 +18,7 @@ text, at least). The package also provides a like the standard <code>\</code><code>settowidth</code> command), and a <code>\</code><code>widthofpbox</code> function analagous to the <code>\</code><code>widthof</code> command for use with the <i>calc</i> package. -<p>The <i>eqparbox</i> package extends <i>pbox</i>’s idea, by +<p/>The <i>eqparbox</i> package extends <i>pbox</i>’s idea, by allowing you to set a series of boxes, all with the same (minimised) width. (Note that it doesn’t accept a limiting maximum width parameter.) The package documentation shows the following example @@ -48,7 +48,7 @@ may be used to produce sensible-looking columns that mix <code>c</code>-, entry, by making the fixed-width rows an <i>eqparbox</i> group, and making the last from a <code>\</code><code>parbox</code> using the width that’s been measured for the group. -<p>The <i>varwidth</i> package defines a <code>varwidth</code> +<p/>The <i>varwidth</i> package defines a <code>varwidth</code> environment which sets the content of the box to match a “narrower natural width” if it finds one. (You give it the same parameters as you would give <code>minipage</code>: in effect, it is a ‘drop-in’ @@ -57,7 +57,7 @@ replacement.) <i>Varwidth</i> provides its own ragged text command: text in the last line of the paragraph (thus producing lines with more nearly equal lengths than typically happens with <code>\</code><code>raggedright</code> itself). -<p>The documentation (in the package file) lists various restrictions and +<p/>The documentation (in the package file) lists various restrictions and things still to be done, but the package is already proving useful for a variety of jobs. <dl> @@ -65,6 +65,6 @@ a variety of jobs. <dt><tt><i>pbox.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pbox.zip">macros/latex/contrib/pbox</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/pbox.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/pbox/">browse</a>) <dt><tt><i>varwidth.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/varwidth.sty">macros/latex/contrib/misc/varwidth.sty</a> </dl> -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidth">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidth</a> +<p/> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidth">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=varwidth</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbfile.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbfile.html index ce82fb7b42c..e5a36b9f191 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbfile.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbfile.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label verbfile</title> </head><body> <h3>Including a file verbatim in LaTeX</h3> -<p>A good way is to use Rainer Schöpf’s <i>verbatim</i> package, +<p/>A good way is to use Rainer Schöpf’s <i>verbatim</i> package, which provides a command <code>\verbatiminput</code> that takes a file name as argument: <blockquote> @@ -27,13 +27,13 @@ finds: </blockquote><p> of course, this is little use for inputting (La)TeX source code... -<p>The <i>moreverb</i> package extends the <i>verbatim</i> package, +<p/>The <i>moreverb</i> package extends the <i>verbatim</i> package, providing a <code>listing</code> environment and a <code>\</code><code>listinginput</code> command, which line-number the text of the file. The package also has a <code>\</code><code>verbatimtabinput</code> command, that honours TAB characters in the input (the package’s <code>listing</code> environment and the <code>\</code><code>listinginput</code> command also both honour TAB). -<p>The <i>sverb</i> package provides verbatim input (without recourse +<p/>The <i>sverb</i> package provides verbatim input (without recourse to the facilities of the <i>verbatim</i> package): <blockquote> <pre> @@ -42,13 +42,13 @@ to the facilities of the <i>verbatim</i> package): \verbinput{verb.txt} </pre> </blockquote><p> -<p>The <i>fancyvrb</i> package offers configurable implementations of +<p/>The <i>fancyvrb</i> package offers configurable implementations of everything <i>verbatim</i>, <i>sverb</i> and <i>moreverb</i> have, and more besides. It is nowadays the package of choice for the discerning typesetter of verbatim text, but its wealth of facilities makes it a complex beast and study of the documentation is strongly advised. -<p>The <i>memoir</i> class includes the relevant functionality of the +<p/>The <i>memoir</i> class includes the relevant functionality of the <i>verbatim</i> and <i>moreverb</i> packages. <dl> <dt><tt><i>alltt.sty</i></tt><dd>Part of the LaTeX distribution. @@ -58,5 +58,5 @@ advised. <dt><tt><i>sverb.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.zip">macros/latex/contrib/mdwtools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/mdwtools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/mdwtools/">browse</a>) <dt><tt><i>verbatim.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbfile">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbfile</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbfile">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbfile</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbwithin.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbwithin.html index 988287f42ce..f6379c0d327 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbwithin.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-verbwithin.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label verbwithin</title> </head><body> <h3>Why doesn’t verbatim work within ...?</h3> -<p>The LaTeX verbatim commands work by changing category codes. Knuth +<p/>The LaTeX verbatim commands work by changing category codes. Knuth says of this sort of thing “Some care is needed to get the timing right...”, since once the category code has been assigned to a character, it doesn’t change. So <code>\</code><code>verb</code> and @@ -43,14 +43,14 @@ barfoo provokes errors like ‘File ended while scanning use of <code>\</code><code>@xverbatim</code>’, as <code>\</code><code>begin{verbatim}</code> fails to see its matching <code>\</code><code>end{verbatim}</code>. -<p>This is why the LaTeX book insists that verbatim +<p/>This is why the LaTeX book insists that verbatim commands must not appear in the argument of any other command; they aren’t just fragile, they’re quite unusable in any command parameter, regardless of <a href="FAQ-protect.html"><code>\</code><code>protect</code>ion</a>. (The <code>\</code><code>verb</code> command tries hard to detect if you’re misusing it; unfortunately, it can’t always do so, and the error message is therefore not a reliable indication of problems.) -<p>The first question to ask yourself is: “is <code>\</code><code>verb</code> actually +<p/>The first question to ask yourself is: “is <code>\</code><code>verb</code> actually necessary?”. <ul> <li> If <code>\</code><code>texttt{<em>your text</em>}</code> produces the same result @@ -58,8 +58,9 @@ necessary?”. <code>\</code><code>verb</code> in the first place. <li> If you’re using <code>\</code><code>verb</code> to typeset a URL or email address or the like, then the <code>\</code><code>url</code> command from the - <a href="FAQ-setURL.html"><i>url</i> package</a> will help: it doesn’t suffer - from the problems of <code>\</code><code>verb</code>. + <i>url</i> will help: it doesn’t suffer from all the problems of + <code>\</code><code>verb</code>, though it’s still not robust; + ”<a href="FAQ-setURL.html">typesetting URLs</a>” offers advice here. <li> If you’re putting <code>\</code><code>verb</code> into the argument of a boxing command (such as <code>\</code><code>fbox</code>), consider using the <code>lrbox</code> environment: @@ -74,7 +75,7 @@ necessary?”. </pre> </blockquote><p> </ul> -<p>Otherwise, there are three partial solutions to the problem. +<p/>Otherwise, there are three partial solutions to the problem. <ul> <li> Some packages have macros which are designed to be responsive to verbatim text in their arguments. For example, @@ -86,13 +87,13 @@ necessary?”. clash with other packages: for example, <code>\</code><code>VerbatimFootnotes</code> interacts poorly with the <code>para</code> option to the <i>footmisc</i> package. -<p> The <i>memoir</i> class defines its <code>\</code><code>footnote</code> command so that +<p/> The <i>memoir</i> class defines its <code>\</code><code>footnote</code> command so that it will accept verbatim in its arguments, without any supporting package. <li> The <i>fancyvrb</i> package defines a command <code>\</code><code>SaveVerb</code>, with a corresponding <code>\</code><code>UseVerb</code> command, that allow you to save and then to reuse the content of its argument; for details of this extremely powerful facility, see the package documentation. -<p> Rather simpler is the <i>verbdef</i> package, which defines a +<p/> Rather simpler is the <i>verbdef</i> package, which defines a (robust) command which expands to the verbatim argument given. <li> If you have a single character that is giving trouble (in its absence you could simply use <code>\</code><code>texttt</code>), consider using @@ -102,7 +103,7 @@ necessary?”. won’t, however, work in a moving argument, and no amount of <a href="FAQ-protect.html"><code>\</code><code>protect</code>ion</a> will make it work in such a case. -<p> A robust alternative is: +<p/> A robust alternative is: <blockquote> <pre> \chardef\us=`\_ @@ -124,5 +125,5 @@ package files. <dt><tt><i>url.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/url.sty">macros/latex/contrib/misc/url.sty</a> <dt><tt><i>verbdef.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/misc/verbdef.sty">macros/latex/contrib/misc/verbdef.sty</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbwithin">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbwithin</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbwithin">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbwithin</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertposfp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertposfp.html index 0f2b1b7afb7..131da7afdf5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertposfp.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertposfp.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label vertposfp</title> </head><body> <h3>Vertical layout of float pages</h3> -<p>By default, LaTeX vertically centres the floats on a float page; +<p/>By default, LaTeX vertically centres the floats on a float page; the present author is not alone in not liking this arrangement. Unfortunately, the control of the positioning is “buried” in LaTeX-internal commands, so some care is needed to change the layout. -<p>Float pages use three LaTeX lengths (i.e., TeX skips) to define +<p/>Float pages use three LaTeX lengths (i.e., TeX skips) to define their layout: <dl> <dt><code>\</code><code>@fptop</code><dd> defines the distance from the @@ -19,14 +19,14 @@ their layout: </dl> (In fact, the output routine places a skip of <code>\</code><code>@fpsep</code> above each float, so the <code>\</code><code>@fptop</code> skip is always followed by a correction for that.) -<p><p>The LaTeX defaults are:<br> +<p/><p/>The LaTeX defaults are:<br> <code>\</code><code>@fptop</code> = <code>0pt + 1fil</code><br> <code>\</code><code>@fpsep</code> = <code>8pt + 2fil</code><br> <code>\</code><code>@fpbot</code> = <code>0pt + 1fil</code><br> so that the gaps expand to fill the space not occupied by floats, but if there is more than one float on the page, the gap between them will expand to twice the space at top and bottom. -<p>Those who understand this stuff will be able to play elaborate games, +<p/>Those who understand this stuff will be able to play elaborate games, but the commonest requirement, that the floats start at the top of the page, is a simple thing to do: <blockquote> @@ -40,8 +40,8 @@ Surprisingly, you may find this setting leaves your floats too high on the page. One can justify a value of <code>5pt</code> (in place of <code>0pt</code>) — it’s roughly the difference between <code>\</code><code>topskip</code> and the height of normal (<code>10pt</code>) text. -<p>Note that this is a “global” setting (best established in a class +<p/>Note that this is a “global” setting (best established in a class file, or at worst in the document preamble); making the change for a single float page is likely (at the least) to be rather tricky. -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertposfp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertposfp</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertposfp">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertposfp</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertspacefloat.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertspacefloat.html index 96ce6729283..bd77a1823ae 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertspacefloat.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-vertspacefloat.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label vertspacefloat</title> </head><body> <h3>Extra vertical space in floats</h3> -<p>A common complaint is that extra vertical space has crept into +<p/>A common complaint is that extra vertical space has crept into <code>figure</code> or <code>table</code> floating environments. More common still are users who post code that introduces this extra space, and <em>haven’t noticed the problem</em>! -<p>The trouble arises from the fact that the <code>center</code> +<p/>The trouble arises from the fact that the <code>center</code> environment (and its siblings <code>flushleft</code> and <code>flushright</code>) are actually based on LaTeX’s list-handling code; and lists always separate themselves from the @@ -35,7 +35,7 @@ or worse still: </pre> </blockquote><p> unwarranted vertical space is going to appear. -<p>The solution is to let the float and the objects in it position +<p/>The solution is to let the float and the objects in it position themselves, and to use “generic” layout commands rather than their list-based encapsulations. <blockquote> @@ -48,10 +48,10 @@ list-based encapsulations. </pre> </blockquote><p> (which even involves less typing). -<p>This alternative code will work with any LaTeX package. It will +<p/>This alternative code will work with any LaTeX package. It will not work with obsolete (pre-LaTeX2e) packages such as <i>psfig</i> or <i>epsf</i> — see <a href="FAQ-impgraph.html">graphics inclusion</a> for discussion of the genesis of <code>\</code><code>includegraphics</code>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertspacefloat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertspacefloat</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertspacefloat">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=vertspacefloat</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-virtualfonts.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-virtualfonts.html index 2e370d305c5..dc3ae3f7377 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-virtualfonts.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-virtualfonts.html @@ -2,48 +2,48 @@ <title>UK TeX FAQ -- question label virtualfonts</title> </head><body> <h3>Virtual fonts</h3> -<p>Virtual fonts for TeX were first implemented by David Fuchs in the -early days of TeX, but for most people they date from when Knuth -redefined the format, and wrote some support software, in 1989 (he +<p/>Virtual fonts provide a means of collecting bits and pieces together +to make the glyphs of a font: the bits and pieces may be other glyphs, +rules and other “basic” typesetting commands, and the positioning +information that specifies how everything comes together. +<p/>Things that match the concept of virtual fonts for TeX were first +implemented by David Fuchs in the very early days. However, for practical +purposes for the rest of us, virtual fonts date from when Knuth +specified a format and wrote some support software, in 1989 (he published an article in <i>TUGboat</i> at the time, and a plain text copy is available on CTAN). -<p>Virtual fonts provide a way of telling TeX about something more +<p/>Virtual fonts provide a way of telling TeX about something more complicated than just a one-to-one character mapping. The entities you define in a virtual font look like characters to TeX (they appear -with their sizes in a font metric file), but the DVI processor may +with their sizes in a TFM file), but the DVI processor may expand them to something quite different. -<p>Specifically, TeX itself only looks at a TFM file that -contains details of how the virtual font will appear: but of course, -TeX only cares about the metrics of a character, so its demands are -pretty small. The acro{DVI} processor, however, has to understand the +<p/>From the virtual font file, the DVI processor learns details of what is in the virtual font, so as to know “what to draw, -where”. So, for every virtual font read by a DVI driver, -there has to be a TFM file to be read by TeX. -(PDFTeX, of course, needs both the TFM and the -translation of the virtual font, since it does the whole job in the -one program.) -<p>You can use a virtual font: +where”. The virtual font may contain commands: <ul> -<li> simply just to remap the glyphs of a single font, +<li> just to remap the glyphs of a single font, <li> to make a composite font with glyphs drawn from several - different onts, or + different fonts, or <li> to build up an effect in arbitrarily complicated ways (since a virtual font may contain anything which is legal in a DVI file). </ul> -<p>In practice, the most common use of virtual fonts is to remap +<p/> + +In practice, the most common use of virtual fonts is to remap Adobe Type 1 fonts (see <a href="FAQ-metrics.html">font metrics</a>), though there has also been useful useful work building ‘fake’ maths fonts (by bundling glyphs from several fonts into a single virtual font). Virtual Computer Modern fonts, making a <a href="FAQ-ECfonts.html">Cork encoded</a> font from Knuth’s originals by using remapping and fragments of DVI for single-glyph ‘accented -characters’, were the first “Type 1 format” versions available. -<p>Virtual fonts are normally created in a single ASCII +characters’, were the first “Type 1 format” Cork-encoded Computer +Modern fonts available. +<p/>Virtual fonts are normally created in a single ASCII VPL (Virtual Property List) file, which includes both sets of information. The <i>vptovf</i> program is then used to the create the binary TFM and VF files. -<p>A “how-to” document, explaining how to generate a VPL, +<p/>A “how-to” document, explaining how to generate a VPL, describes the endless hours of fun that may be had, doing the job by hand. Despite the pleasures to be had of the manual method, the commonest way (nowadays) of generating VPL files is to use the @@ -59,5 +59,5 @@ fonts (it uses TeX to parse a description of the virtual font, and <dt><tt><i>Virtual fonts “how to”</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/virtualfontshowto/virtualfontshowto.txt">info/virtualfontshowto/virtualfontshowto.txt</a> <dt><tt><i>qdtexvpl</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/qdtexvpl.zip">fonts/utilities/qdtexvpl</a> (<a href="ftp://cam.ctan.org/tex-archive/fonts/utilities/qdtexvpl.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/fonts/utilities/qdtexvpl/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=virtualfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=virtualfonts</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=virtualfonts">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=virtualfonts</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-watermark.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-watermark.html index d04725819e0..fb996352f51 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-watermark.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-watermark.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label watermark</title> </head><body> <h3>‘Watermarks’ on every page</h3> -<p>It’s often useful to place some text (such as ‘DRAFT’) in the +<p/>It’s often useful to place some text (such as ‘DRAFT’) in the background of every page of a document. For LaTeX users, this can be achieved with the <i>draftcopy</i> package. This can deal with many types of DVI processors (in the same way that the graphics @@ -12,15 +12,15 @@ Unfortunately, however, the package relies on PostScript specials, and will therefore fail if you are viewing your document with <i>xdvi</i>, and won’t even compile if you’re using PDFLaTeX. (PDFLaTeX users need one of the other solutions below.) -<p>The <i>wallpaper</i> package builds on <i>eso-pic</i> (see +<p/>The <i>wallpaper</i> package builds on <i>eso-pic</i> (see below). Apart from the single-image backdrops described above (“wallpapers”, of course, to this package), the package provides facilities for tiling images. All its commands come in pairs: one for “general” use, and one applying to the current page only. -<p>The <i>draftwatermark</i> package uses the same author’s +<p/>The <i>draftwatermark</i> package uses the same author’s <i>everypage</i> package to provide a simple interface for adding textual (‘DRAFT’-like) watermarks. -<p>More elaborate watermarks may be achieved using the <i>eso-pic</i> +<p/>More elaborate watermarks may be achieved using the <i>eso-pic</i> package, which in turn uses the package <i>everyshi</i>, or by using <i>everypage</i>. <i>Eso-pic</i> attaches a <code>picture</code> environment to every page as it is shipped out; @@ -28,7 +28,7 @@ you can put things into that environment. The package provides commands for placing things at certain useful points (like “text upper left” or “text centre”) in the picture, but you’re at liberty to do what you like. -<p><i>Everypage</i> allows you to add “something” to every page, or +<p/><i>Everypage</i> allows you to add “something” to every page, or to a particular page; you therefore need to construct your own apparatus for anything complicated. <dl> @@ -39,5 +39,5 @@ apparatus for anything complicated. <dt><tt><i>everyshi.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.zip">macros/latex/contrib/ms</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ms.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ms/">browse</a>) <dt><tt><i>wallpaper.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/wallpaper.zip">macros/latex/contrib/wallpaper</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/wallpaper.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/wallpaper/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=watermark">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=watermark</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=watermark">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=watermark</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wdnohyph.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wdnohyph.html index 9eb25cbd83a..35e272da889 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wdnohyph.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wdnohyph.html @@ -2,10 +2,10 @@ <title>UK TeX FAQ -- question label wdnohyph</title> </head><body> <h3>Preventing hyphenation of a particular word</h3> -<p>It’s quite possible for (<em>any</em>) hyphenation of a particular word +<p/>It’s quite possible for (<em>any</em>) hyphenation of a particular word to seem “completely wrong”, so that you want to prevent it being hyphenated. -<p>If the word occurs in just one place, put it in a box: +<p/>If the word occurs in just one place, put it in a box: <blockquote> <pre> \mbox{oddword} @@ -14,7 +14,7 @@ hyphenated. (Plain TeX users should use <code>\</code><code>hbox</code>, and take care at the start of paragraphs.) However, boxing the word is not really advisable unless you are sure it only occurs once. -<p>If the word occurs commonly, the best choice is to assert a +<p/>If the word occurs commonly, the best choice is to assert a non-hyphenation for it: <blockquote> <pre> @@ -23,7 +23,7 @@ non-hyphenation for it: </blockquote><p> This hyphenation exception (with no break points) will be used in preference to what TeX’s hyphenation algorithm may come up with. -<p>In a multilingual document, repeat the exception specification for +<p/>In a multilingual document, repeat the exception specification for each language the word may appear in. So: <blockquote> <pre> @@ -36,5 +36,19 @@ each language the word may appear in. So: </blockquote><p> (note that <i>babel</i> will select the default language for the document — English, in this case — at <code>\</code><code>begin{document}</code>.) -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wdnohyph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wdnohyph</a> +<p/>A particular instance of this requirement is avoiding the hyphenation +of acronyms; a general rule for those that concoct acronyms seems to +be to make the capital-letter sequence read as near as is possible +like a “real” word, but hyphenating an acronym often looks silly. +The TeX flag <code>\</code><code>uchyph</code> is designed for suppressing such +behaviour: +<blockquote> +<pre> +\uchyph=0 +</pre> +</blockquote><p> +will stop hyphenation of upper-case words. (Note that Plain TeX +syntax is needed here: there’s no LaTeX alternative for setting +this value.) +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wdnohyph">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wdnohyph</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-webpkgs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-webpkgs.html index 3e471cbff85..0146ff376f5 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-webpkgs.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-webpkgs.html @@ -2,28 +2,28 @@ <title>UK TeX FAQ -- question label webpkgs</title> </head><body> <h3>WEB systems for various languages</h3> -<p>TeX is written in the programming language WEB; WEB +<p/>TeX is written in the programming language WEB; WEB is a tool to implement the concept of “literate programming”. Knuth’s original implementation will be in any respectable distribution of TeX, but the sources of the two tools (<i>tangle</i> and <i>weave</i>), together with a manual outlining the programming techniques, may be had from CTAN. -<p><i>CWEB</i>, by Silvio Levy, is a WEB for C programs. -<p>Spidery WEB, by Norman Ramsey, supports many +<p/><i>CWEB</i>, by Silvio Levy, is a WEB for C programs. +<p/>Spidery WEB, by Norman Ramsey, supports many languages including Ada, <code>awk</code>, and C and, while not in the public domain, is usable without charge. It is now superseded by <i>noweb</i> (also by Norman Ramsay) which incorporates the lessons learned in implementing spidery WEB, and which is a simpler, equally powerful, tool. -<p><i>FWEB</i>, by John Krommes, is a version for Fortran, +<p/><i>FWEB</i>, by John Krommes, is a version for Fortran, Ratfor, and C. -<p><i>Scheme</i><i>WEB</i>, by John Ramsdell, is a Unix filter that +<p/><i>Scheme</i><i>WEB</i>, by John Ramsdell, is a Unix filter that translates SchemeWEB into LaTeX source or Scheme source. -<p><i>APLWEB</i> is a version of WEB for APL. -<p><i>FunnelWeb</i> is a version of WEB that is language independent. -<p>Other language independent versions of WEB are <i>nuweb</i> (which +<p/><i>APLWEB</i> is a version of WEB for APL. +<p/><i>FunnelWeb</i> is a version of WEB that is language independent. +<p/>Other language independent versions of WEB are <i>nuweb</i> (which is written in ANSI C). -<p><i>Tweb</i> is a WEB for Plain TeX macro files, using +<p/><i>Tweb</i> is a WEB for Plain TeX macro files, using <i>noweb</i>. <dl> <dt><tt><i>aplweb</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/web/apl/aplweb.zip">web/apl/aplweb</a> (<a href="ftp://cam.ctan.org/tex-archive/web/apl/aplweb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/web/apl/aplweb/">browse</a>) @@ -38,6 +38,6 @@ is written in ANSI C). <dt><tt><i>tweb</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/web/tweb.zip">web/tweb</a> (<a href="ftp://cam.ctan.org/tex-archive/web/tweb.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/web/tweb/">browse</a>) <dt><tt><i>weave</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/knuth/web.zip">systems/knuth/web</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/knuth/web.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/knuth/web/">browse</a>) </dl> -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=webpkgs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=webpkgs</a> +<p/> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=webpkgs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=webpkgs</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-weirdhyphen.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-weirdhyphen.html index e1d747e3803..b722d797144 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-weirdhyphen.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-weirdhyphen.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label weirdhyphen</title> </head><body> <h3>Weird hyphenation of words</h3> -<p>If your words are being h-yphenated, like this, with jus-t single +<p/>If your words are being h-yphenated, like this, with jus-t single letters at the beginning or the end of the word, you may have a version mismatch problem. TeX’s hyphenation system changed between version 2.9 @@ -14,10 +14,10 @@ best plan is to upgrade to LaTeX2e. If for some reason you can’t, the last version of LaTeX 2.09 (released on 25 March 1992) is still available (for the time being at least) and ought to solve this problem. -<p>If you’re using LaTeX2e, the problem probably arises from your +<p/>If you’re using LaTeX2e, the problem probably arises from your <code>hyphen.cfg</code> file, which has to be created if you’re using a multi-lingual version. -<p>A further source of oddity can derive from the 1995 release of +<p/>A further source of oddity can derive from the 1995 release of <a href="FAQ-ECfonts.html">Cork-encoded fonts</a>, which introduced an alternative hyphen character. The LaTeX2e configuration files in the font release specified use of the @@ -30,5 +30,5 @@ solution, again, is to upgrade your LaTeX. <dt><tt><i>LaTeX 2.09</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/obsolete/macros/latex209/distribs/latex209.tar.gz">obsolete/macros/latex209/distribs/latex209.tar.gz</a> <dt><tt><i>plain.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/plain/base.zip">macros/plain/base</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/plain/base.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/plain/base/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=weirdhyphen">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=weirdhyphen</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=weirdhyphen">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=weirdhyphen</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-what-TDS.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-what-TDS.html new file mode 100644 index 00000000000..54a5adca4f3 --- /dev/null +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-what-TDS.html @@ -0,0 +1,82 @@ +<head> +<title>UK TeX FAQ -- question label what-TDS</title> +</head><body> +<h3>Which tree to use</h3> +<p/>In almost all cases, new material that you install should go into the +“local” tree of your (La)TeX installation. The root directory +will be named something like: +<blockquote> +<pre> +teTeX or TeX-live: /usr/share/texmf-local/ or + /usr/local/share/texmf/ +MiKTeX: c:\localtexmf\ +</pre> +</blockquote><p> +You can ask a Unix-alike system (such as teTeX or TeX-live) where +it believes a local tree should be: +<blockquote> +<pre> +kpsewhich -expand-var "\$TEXMFLOCAL" +</pre> +</blockquote><p> +the output being the actual path, for example: +<blockquote> +<pre> +/usr/local/share/texmf +</pre> +</blockquote><p> +on the workstation the author is using today. +<p/>In a MiKTeX installation, the location will in fact typically be +something you specified yourself when you installed MiKTeX in the +first place, but you may find you need to create one. The MiKTeX +“Settings” window ( + <code>Start</code>-> + <code>Programs</code>-> + <code>MiKTeX</code>-> + <code>Settings</code>) +has a tab “<code>Roots</code>”; that tab gives a list of current +TDS roots (they’re typically not called +<code>texmf</code>-anything). If there’s not one there with +“<code>local</code>” in its name, create an appropriate one (say +“<code>Local TeX Files</code>”), and register it using the window’s +“<code>Add</code>” button. The +<a href="http://docs.miktex.org/faq/maintenance.html">Miktex FAQ</a> +suggests that you should create +<code>C:textbackslashLocal TeX Files</code>, which is good if you +manage your own machine, but often not even possible in corporate, or +similar, environments where you will need to create a directory +somewhere <em>you</em>, rather than the system, control). +<p/>There are circumstances when you might not wish to do this: +<ul> +<li> if the package, or whatever, is “personal” (for example, + something commercial that has been licensed to you alone, or + something you’re developing yourself), the package should go in your + <a href="FAQ-privinst.html">“home” TEXMF tree</a>; +<li> if you have no privilege to write to the local tree, you are + again unlikely to be able to put the package anywhere other than + your home tree; or +<li> if you <em>know</em> that the package you are installing is a + replacement for the copy on the TEXMF tree of your (La)TeX + distribution, you should replace the existing copy in the + TEXMF tree. +</ul> +The reason one would put things on a local tree is to avoid their +disappearance if the system is upgraded (or otherwise re-installed). +<p/>The reason one might place upgrades the distribution’s main tree is to +avoid confusion. Suppose you were to place the file on the local +tree, and then install a new version of the distribution — you might +have an effect like: +<ul> +<li> distribution comes with package version n; +<li> you install package version n+1 on the local tree; and +<li> the updated distribution comes with package version n+2. +</ul> +In such a situation, you will find yourself using version +n+1 (from the local tree) <em>after</em> the new +distribution has been installed. +<p/>If you install in the local tree, the only way to avoid such problems +is to carefully purge the local tree when installing a new +distribution. This is tedious, if you’re maintaining a large +installation. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=what-TDS">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=what-TDS</a> +</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatTeX.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatTeX.html index 105c1eb31db..18536d7d135 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatTeX.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatTeX.html @@ -2,19 +2,19 @@ <title>UK TeX FAQ -- question label whatTeX</title> </head><body> <h3>What is TeX?</h3> -<p>TeX is a typesetting system written by +<p/>TeX is a typesetting system written by <a href="http://sunburn.stanford.edu/~knuth/">Donald E. Knuth</a>, who says in the Preface to his book on TeX (see <a href="FAQ-books.html">books about TeX</a>) that it is “<em>intended for the creation of beautiful books — and especially for books that contain a lot of mathematics</em>”. -<p>Knuth is Emeritus Professor of the Art of Computer Programming at +<p/>Knuth is Emeritus Professor of the Art of Computer Programming at Stanford University in California, USA. Knuth developed the first version of TeX in 1978 to deal with revisions to his series “the Art of Computer Programming”. The idea proved popular and Knuth produced a second version (in 1982) which is the basis of what we use today. -<p>Knuth developed a system of +<p/>Knuth developed a system of ‘<a href="FAQ-lit.html">literate programming</a>’ to write TeX, and he provides the literate (WEB) source of TeX free of charge, together with tools for processing the <code>web</code> source into something @@ -25,7 +25,7 @@ computers; and in order that one may have some confidence in the ports, Knuth supplied a <a href="FAQ-triptrap.html">test</a> by means of which one may judge the fidelity of a TeX system. TeX and its documents are therefore highly portable. -<p>TeX is a macro processor, and offers its users a powerful +<p/>TeX is a macro processor, and offers its users a powerful programming capability. For this reason, TeX on its own is a pretty difficult beast to deal with, so Knuth provided a package of macros for use with TeX called Plain TeX; Plain TeX is @@ -34,5 +34,5 @@ TeX, together with some demonstration versions of higher-level commands (the latter are better regarded as models than used as-is). When people say they’re “programming in TeX”, they usually mean they’re programming in Plain TeX. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatTeX">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatTeX</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatTeX">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatTeX</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatbst.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatbst.html index 237543fb78f..71e450dd0cb 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatbst.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatbst.html @@ -2,18 +2,18 @@ <title>UK TeX FAQ -- question label whatbst</title> </head><body> <h3>Choosing a bibliography style</h3> -<p>A large proportion of people are satisfied with one of Patashnik’s +<p/>A large proportion of people are satisfied with one of Patashnik’s original “standard” styles, <i>plain</i>, <i>unsrt</i>, <i>abbrv</i> and <i>alpha</i>. However, no style in that set supports the “author-date” citation style that is popular in many fields; but there are a very large number of contributed styles available, that <em>do</em> support the format. -<p>(Note that author-date styles arose because the simple and clear +<p/>(Note that author-date styles arose because the simple and clear citation style that <i>plain</i> produces is so awkward in a traditional manuscript preparation scenario. However, TeX-based document production does away with all those difficulties, leaving us free once again to use the simple option.) -<p>Fortunately, help is at hand, on the Web, with this problem: +<p/>Fortunately, help is at hand, on the Web, with this problem: <ul> <li> a sample text, showing the sorts of style choices available, can be found on @@ -27,7 +27,7 @@ free once again to use the simple option.) “<a href="http://web.reed.edu/cis/help/LaTeX/bibtexstyles.html">Choosing a BibTeX style</a>”. </ul> -<p>Of course, these pages don’t cover everything; the problem the +<p/>Of course, these pages don’t cover everything; the problem the inquisitive user faces, in fact, is to find what the various available styles actually do. This is best achieved (if the links above don’t help) by using <i>xampl.bib</i> from the BibTeX documentation @@ -47,9 +47,9 @@ hand using this “standard” bibliography. For style will produce a representative sample of the citations the style will produce. (Because <i>xampl.bib</i> is so extreme in some of its “examples”, the BibTeX run will also give you an interesting -selection of BibTeX’s error messages\dots) +selection of BibTeX’s error messages...) <dl> <dt><tt><i>xampl.bib</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/biblio/bibtex/distribs/doc/xampl.bib">biblio/bibtex/distribs/doc/xampl.bib</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatbst">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatbst</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatbst">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatbst</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatenc.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatenc.html index aa0b55306ac..275f5b60c95 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatenc.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatenc.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label whatenc</title> </head><body> <h3>What are encodings?</h3> -<p>Let’s start by defining two concepts, the <em>character</em> and the +<p/>Let’s start by defining two concepts, the <em>character</em> and the <em>glyph</em>. The character is the abstract idea of the ‘atom’ of a language or other dialogue: so it might be a letter in an alphabetic @@ -14,15 +14,15 @@ relationship between the glyph and the character, so while the precise shape of the glyph can be affected by many other factors, such as the capabilities of the writing medium and the designer’s style, the essence of the underlying character must be retained. -<p>Whenever a computer has to represent characters, someone has to define +<p/>Whenever a computer has to represent characters, someone has to define the relationship between a set of numbers and the characters they represent. This is the essence of an encoding: it is a mapping between a set of numbers and a set of things to be represented. -<p>TeX of course deals in encoded characters all the time: the +<p/>TeX of course deals in encoded characters all the time: the characters presented to it in its input are encoded, and it emits encoded characters in its DVI (or PDF) output. These encodings have rather different properties. -<p>The TeX input stream was pretty unruly back in the days when Knuth +<p/>The TeX input stream was pretty unruly back in the days when Knuth first implemented the language. Knuth himself prepared documents on terminals that produced all sorts of odd characters, and as a result TeX contains some provision for translating the input encoding to @@ -35,7 +35,7 @@ contain characters that can’t appear in the TeX system’s input stream. Somehow, these characters have to be dealt with — so an input character like “é” needs to be interpreted by TeX in a way that that at least mimics the way it interprets “<code>\</code><code>’</code><code>e</code>”. -<p>The TeX output stream is in a somewhat different situation: +<p/>The TeX output stream is in a somewhat different situation: characters in it are to be used to select glyphs from the fonts to be used. Thus the encoding of the output stream is notionally a font encoding (though the font in question may be a @@ -47,7 +47,7 @@ transcription of what arrived in the input, but the output stream also contains the product of commands in the input, and translations of the input such as ligatures like <code>fi</code>. -<p>Font encodings became a hot topic when the +<p/>Font encodings became a hot topic when the <a href="FAQ-ECfonts.html">Cork encoding</a> appeared, because of the possibility of suppressing <code>\</code><code>accent</code> commands in the output stream (and hence improving the @@ -57,11 +57,11 @@ interrupted by the <code>\</code><code>accent</code> commands — see <a href="FAQ-hyphen.html">“how does hyphenation work”</a>). To take advantage of the diacriticised characters represented in the fonts, it is necessary to arrange that whenever the -command sequence “<code>\’</code><code>e</code>” has been input +command sequence “<code>\</code><code>’</code><code>e</code>” has been input (explicitly, or implicitly via the sort of mapping of input mentioned above), the character that codes the position of the “é” glyph is used. -<p>Thus we could have the odd arrangement that the diacriticised character in +<p/>Thus we could have the odd arrangement that the diacriticised character in the TeX input stream is translated into TeX commands that would generate something looking like the input character; this sequence of TeX commands is then translated back again into a single @@ -74,5 +74,5 @@ the second precisely undo it, but it doesn’t always happen that way: most font encodings can’t match the corresponding input encoding nearly so well, and the two packages provide the sort of symmetry the LaTeX system needs. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatenc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatenc</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatenc">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatenc</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatpdftex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatpdftex.html index 016b068fa76..6e59347c7ed 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatpdftex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whatpdftex.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label whatpdftex</title> </head><body> <h3>What is PDFTeX?</h3> -<p>PDFTeX has entered the main stream of TeX distributions: most +<p/>PDFTeX has entered the main stream of TeX distributions: most LaTeX and ConTeXt users nowadays use PDFTeX whether they know it or not (more precisely, they use an amalgam of PDFTeX and <a href="FAQ-etex.html">e-TeX</a>). So what is PDFTeX? -<p>PDFTeX is a development of TeX that is capable of generating +<p/>PDFTeX is a development of TeX that is capable of generating typeset PDF output in place of DVI. PDFTeX has other capabilities, most notably in the area of fine typographic detail (for example, its support for @@ -14,17 +14,18 @@ detail (for example, its support for but its greatest impact to date has been in the area of PDF output. -<p>PDFTeX started as a topic for -Han The Thanh’s Master’s thesis, +<p/>PDFTeX started as a topic for Hàn The Thành’s Master’s thesis, and seems first to have been published in <i>TUGboat</i> 18(4), in 1997 (though it was certainly discussed at the TUG’96 conference in Russia). -<p>While the world was making good use of “pre-releases” of PDFTeX, +<p/>While the world was making good use of “pre-releases” of PDFTeX, Thành used it as a test-bed for the micro-typography which was the prime subject of his Ph.D. research. Since Thành was finally awarded his Ph.D., day-to-day maintenance and development of PDFTeX 1.0 (and later) has been in the hands of a group of PDFTeX maintainers (which includes Thành); the group has managed to maintain a stable platform for general use. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatpdftex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatpdftex</a> +<p/>Development of PDFTeX has (in essence) stopped: the brave new world +is to be <a href="FAQ-luatex.html">LuaTeX</a>. +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatpdftex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatpdftex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whereFAQ.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whereFAQ.html index f44d8ba7a39..2696295bd96 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whereFAQ.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whereFAQ.html @@ -2,39 +2,39 @@ <title>UK TeX FAQ -- question label whereFAQ</title> </head><body> <h3>Where to find FAQs</h3> -<p>Bobby Bodenheimer’s article, from which this FAQ was developed, used +<p/>Bobby Bodenheimer’s article, from which this FAQ was developed, used to be posted (nominally monthly) to newsgroup <i>comp.text.tex</i>. The (long obsolete) last posted copy of that article is kept on CTAN for auld lang syne. -<p> +<p/> The sources of the present FAQ are available from CTAN. -<p>This FAQ and others are regularly mentioned, on +<p/>This FAQ and others are regularly mentioned, on <i>comp.text.tex</i> and elsewhere, in a “pointer FAQ” which is also saved at <a href="http://tug.org/tex-ptr-faq">http://tug.org/tex-ptr-faq</a> -<p>A 2006 innovation from Scott Pakin is the “visual” LaTeX FAQ. +<p/>A 2006 innovation from Scott Pakin is the “visual” LaTeX FAQ. This is a document with (mostly rubbish) text formatted so as to highlight things we discuss here, and providing Acrobat hyper-links to the relevant answers in this FAQ on the Web. The visual FAQ is provided in PDF format, on CTAN; it works best using Adobe Acrobat Reader 7 (or later); some features are missing with other readers, or with earlier versions of Acrobat Reader -<p>Another excellent information source, available in English, is the +<p/>Another excellent information source, available in English, is the <a href="http://tex.loria.fr">(La)TeX navigator</a>. -<p>Both the Francophone TeX usergroup Gutenberg and the Czech/Slovak +<p/>Both the Francophone TeX usergroup Gutenberg and the Czech/Slovak usergroup CS-TUG have published translations of this FAQ, with extensions appropriate to their languages. -<p>Herbert Voss’s excellent +<p/>Herbert Voss’s excellent <a href="http://texnik.de/">LaTeX tips and tricks</a> provides excellent advice on most topics one might imagine (though it’s not strictly a FAQ) — highly recommended for most ordinary mortals’ use. -<p>The Open Directory Project (ODP) maintains a list of sources of +<p/>The Open Directory Project (ODP) maintains a list of sources of (La)TeX help, including FAQs. View the TeX area at <a href="http://dmoz.org/Computers/Software/Typesetting/TeX/">http://dmoz.org/Computers/Software/Typesetting/TeX/</a> -<p>Other non-English FAQs are available (off-CTAN): +<p/>Other non-English FAQs are available (off-CTAN): <dl> <dt>German<dd>Posted regularly to <i>de.comp.tex</i>, and archived on CTAN; the FAQ also appears at @@ -48,7 +48,7 @@ ordinary mortals’ use. <dt>Spanish<dd>See <a href="http://apolo.us.es/CervanTeX/FAQ/">http://apolo.us.es/CervanTeX/FAQ/</a> <dt>Czech<dd>See <a href="http://www.fi.muni.cz/cstug/csfaq/">http://www.fi.muni.cz/cstug/csfaq/</a> </dl> -<p>Resources available on CTAN are: +<p/>Resources available on CTAN are: <dl> <dt><tt><i>Dante FAQ</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/help/de-tex-faq.zip">help/de-tex-faq</a> (<a href="ftp://cam.ctan.org/tex-archive/help/de-tex-faq.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/de-tex-faq/">browse</a>) <dt><tt><i>French FAQ</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/help/LaTeX-FAQ-francaise.zip">help/LaTeX-FAQ-francaise</a> (<a href="ftp://cam.ctan.org/tex-archive/help/LaTeX-FAQ-francaise.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/help/LaTeX-FAQ-francaise/">browse</a>) @@ -57,5 +57,5 @@ ordinary mortals’ use. <a href="ftp://cam.ctan.org/tex-archive/obsolete/help/TeX,_LaTeX,_etc.:_Frequently_Asked_Questions_with_Answers">obsolete/help/TeX,_LaTeX,_etc.:_Frequently_Asked_Questions_with_Answers</a> <dt><tt><i>The visual FAQ</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/info/visualFAQ/visualFAQ.pdf">info/visualFAQ/visualFAQ.pdf</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whereFAQ">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whereFAQ</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whereFAQ">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whereFAQ</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wherefiles.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wherefiles.html deleted file mode 100644 index a3c090f3880..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wherefiles.html +++ /dev/null @@ -1,76 +0,0 @@ -<head> -<title>UK TeX FAQ -- question label wherefiles</title> -</head><body> -<h3>Where to put new files</h3> -<p>Where precisely you put files that you have downloaded does -depend on what TeX distribution you have. However, -assuming that you have one of the modern TDS-compliant -distributions (such as teTeX or MiKTeX) there are -some general rules that you can follow: -<p> - - - -(1) Always install new files in a local <i>texmf</i> -tree. The root directory will be named something like: -<pre> - teTeX: /usr/share/texmf-local/ or - /usr/local/share/texmf/ - fpTeX: c:\Programs\TeXLive\texmf-local\ - MiKTeX: c:\localtexmf\ -</pre> -(In fact, a teTeX system can be asked to tell you what its local -root is; on a Unix system, the command to use is: -<blockquote> -<pre> -kpsewhich -expand-var "\$TEXMFLOCAL" -</pre> -</blockquote><p> -the output being the actual path.) -<p>Let’s write <code>$TEXMF</code> for this root, whatever it is for your system. -<p> -(2) In your local texmf tree, imitate the directory structure in your -main tree. Here are some examples of where files of given extensions -should go: -<pre> -.sty, .cls or .fd: $TEXMF/tex/latex/<package>/ -.dvi, .ps or .pdf: $TEXMF/doc/latex/<package>/ -.mf: $TEXMF/fonts/source/<supplier>/<font>/ -.tfm: $TEXMF/fonts/tfm/<supplier>/<font>/ -.vf: $TEXMF/fonts/vf/<supplier>/<font>/ -.afm: $TEXMF/fonts/afm/<supplier>/<font>/ -.pfb: $TEXMF/fonts/type1/<supplier>/<font>/ -.ttf: $TEXMF/fonts/truetype/<supplier>/<font>/ -.pool, .fmt, .base or .mem: $TEXMF/web2c -</pre> -and for modern systems (distributed in 2005 or later, such as -teTeX 3.0, using TDS v1.1 layouts): -<pre> -.map: $TEXMF/fonts/map/<syntax>/<bundle>/ -.enc: $TEXMF/fonts/enc/<syntax>/<bundle>/ -</pre> -Where of course <<i>package</i>>, <<i>font</i>> and <<i>supplier</i>> depend -upon what’s appropriate for the individual file. The <<i>syntax</i>> -(for <code>.map</code> and <code>.enc</code> files) is a categorisation based -on the way the files are written; typically, it’s the name of a -program such as <i>dvips</i> or <i>pdftex</i>. -<p>“Straight” (La)TeX input can take other forms than the <code>.sty</code>, -<code>.cls</code> or <code>.fd</code> listed above, too. Examples are -<code>.sto</code> and <code>.clo</code> for package and class options, -<code>.cfg</code> for configuration information, and so on. -<p>Note that <<i>font</i>> may stand for a single font or an entire family: -for example, files for all of Knuth’s Computer Modern fonts are to be -found in <code>.../public/cm</code>, with various prefixes as appropriate. -<p>The font “supplier” <em>public</em> is a sort of hold-all for -“free fonts produced for use with (La)TeX”: as well as Knuth’s -fonts, <em>public</em>’s directory holds fonts designed by others -(originally, but no longer exclusively, in Metafont). -<p>Some packages have configuration files (commonly with file suffix -<code>.cfg</code>), and occasionally other run-time files. The package -documentation <em>should</em> mention these things, but sometimes -doesn’t. A common exception is the <code>.drv</code> file, used by some -packages as part of the documentation building process; this is a -hang-over from the pre-LaTeX2e predecessor of the package -documentation process. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wherefiles">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wherefiles</a> -</body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wholerow.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wholerow.html index 56c88778cb5..dffcf55605b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wholerow.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wholerow.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label wholerow</title> </head><body> <h3>How to change a whole row of a table</h3> -<p>Each cell of a table is set in a box, so that a change of font style +<p/>Each cell of a table is set in a box, so that a change of font style (or whatever) only lasts to the end of the cell. If one has a many-celled table, or a long one which needs lots of rows emphasising, putting a font style change command in every cell will be impossibly tedious. -<p>With the <i>array</i> package, you can define column modifiers +<p/>With the <i>array</i> package, you can define column modifiers which will change the font style for a whole <em>column</em>. However, with a bit of subtlety, one can make such modifiers affect rows rather than columns. So, we set things up by: @@ -45,5 +45,5 @@ always work. <dl> <dt><tt><i>array.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wholerow">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wholerow</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wholerow">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wholerow</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-why-inp-font.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-why-inp-font.html index 84e67750a80..461dd6b7b60 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-why-inp-font.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-why-inp-font.html @@ -2,15 +2,15 @@ <title>UK TeX FAQ -- question label why-inp-font</title> </head><body> <h3>Why bother with <i>inputenc</i> and <i>fontenc</i>?</h3> -<p>The standard input encoding for Western Europe (pending the arrival of +<p/>The standard input encoding for Western Europe (pending the arrival of Unicode) is ISO 8859–1 (commonly known by the standard’s subtitle ‘Latin-1’). Latin-1 is remarkably close, in the codepoints it covers, to the (La)TeX T1 encoding. -<p>In this circumstance, why should one bother with <i>inputenc</i> +<p/>In this circumstance, why should one bother with <i>inputenc</i> and <i>fontenc</i>? Since they’re pretty exactly mirroring each other, one could do away with both, and use just <i>t1enc</i>, despite its <a href="FAQ-t1enc.html">shortcomings</a>. -<p>One doesn’t do this for a variety of small reasons: +<p/>One doesn’t do this for a variety of small reasons: <dl> <dt>Confusion<dd> You’ve been happily working in this mode, and for some reason find you’re to switch to writing in German: the effect @@ -27,5 +27,5 @@ despite its <a href="FAQ-t1enc.html">shortcomings</a>. </dl> The <i>inputenc</i>–<i>fontenc</i> combination seems slow and cumbersome, but it’s safe. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=why-inp-font">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=why-inp-font</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=why-inp-font">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=why-inp-font</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whyfree.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whyfree.html index 1eacd739f63..64e06c868c6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whyfree.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-whyfree.html @@ -2,19 +2,19 @@ <title>UK TeX FAQ -- question label whyfree</title> </head><body> <h3>If TeX is so good, how come it’s free?</h3> -<p>It’s free because Knuth chose to make it so. He is nevertheless +<p/>It’s free because Knuth chose to make it so. He is nevertheless apparently happy that others should earn money by selling TeX-based services and products. While several valuable TeX-related tools and packages are offered subject to restrictions imposed by the GNU General Public Licence (‘Copyleft’), TeX itself is not subject to Copyleft. -<p>There are commercial versions of TeX available; for some users, +<p/>There are commercial versions of TeX available; for some users, it’s reassuring to have paid support. What is more, some of the commercial implementations have features that are not available in free versions. (The reverse is also true: some free implementations have features not available commercially.) -<p>This FAQ concentrates on ‘free’ distributions of TeX, but we +<p/>This FAQ concentrates on ‘free’ distributions of TeX, but we do at least list the <a href="FAQ-commercial.html">major vendors</a>. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whyfree">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whyfree</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whyfree">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whyfree</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widefigs.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widefigs.html index 8dc654619f7..520cd27f9d4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widefigs.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widefigs.html @@ -2,16 +2,16 @@ <title>UK TeX FAQ -- question label widefigs</title> </head><body> <h3>Wide figures in two-column documents</h3> -<p>Floating figures and tables ordinarily come out the same width as the +<p/>Floating figures and tables ordinarily come out the same width as the page, but in two-column documents they’re restricted to the width of the column. This is sometimes not good enough; so there are alternative versions of the float environments — in two-column documents, <code>figure*</code> provides a floating page-wide figure (and <code>table*</code> a page-wide table) which will do the necessary. -<p>The “<code>*</code>”ed float environments can only appear at the top of a page, +<p/>The “<code>*</code>”ed float environments can only appear at the top of a page, or on a whole page — <code>h</code> or <code>b</code> float placement directives are simply ignored. -<p>Unfortunately, page-wide equations can only be accommodated inside +<p/>Unfortunately, page-wide equations can only be accommodated inside float environments. You should include them in <code>figure</code> environments, or use the <i>float</i> or <i>ccaption</i>package to define a new float type. @@ -19,5 +19,5 @@ new float type. <dt><tt><i>ccaption.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ccaption.zip">macros/latex/contrib/ccaption</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/ccaption.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/ccaption/">browse</a>) <dt><tt><i>float.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/float.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/float/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widefigs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widefigs</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widefigs">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widefigs</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widows.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widows.html index d6275c61b16..357ae7d857e 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widows.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-widows.html @@ -2,14 +2,14 @@ <title>UK TeX FAQ -- question label widows</title> </head><body> <h3>Controlling widows and orphans</h3> -<p>Widows (the last line of a paragraph at the start of a page) and +<p/>Widows (the last line of a paragraph at the start of a page) and orphans (the first line of paragraph at the end of a page) interrupt the reader’s flow, and are generally considered “bad form”; (La)TeX takes some precautions to avoid them, but completely automatic prevention is often impossible. If you are typesetting your own text, consider whether you can bring yourself to change the wording slightly so that the page break will fall differently. -<p>The page maker, when forming a page, takes account of +<p/>The page maker, when forming a page, takes account of <code>\</code><code>widowpenalty</code> and <code>\</code><code>clubpenalty</code> (which relates to orphans!). These penalties are usually set to the moderate value of <code>150</code>; this offers mild discouragement of bad breaks. You can increase the values @@ -21,17 +21,17 @@ penalty will seldom win. Therefore, for typical layouts, there are only two sensible settings for the penalties: finite (150 or 500, it doesn’t matter which) to allow widows and orphans, and infinite (10000 or greater) to forbid them. -<p>The problem can be avoided by allowing +<p/>The problem can be avoided by allowing the pagemaker to run pages short, by using the <code>\</code><code>raggedbottom</code> directive; however, many publishers insist on the default <code>\</code><code>flushbottom</code>; it is seldom acceptable to introduce stretchability into the vertical list, except at points (such as section headings) where the document design explicitly permits it. -<p>Once you’ve exhausted the automatic measures, and have a final draft +<p/>Once you’ve exhausted the automatic measures, and have a final draft you want to “polish”, you should proceed to manual measures. To get rid of an orphan is simple: precede the paragraph with <code>\</code><code>clearpage</code> and the paragraph can’t start in the wrong place. -<p>Getting rid of a widow can be more tricky. If the paragraph is a long +<p/>Getting rid of a widow can be more tricky. If the paragraph is a long one, it may be possible to set it ‘tight’: say <code>\</code><code>looseness</code><code>=-1</code> immediately after the last word of the paragraph. If that doesn’t work, try adjusting the page size: @@ -43,5 +43,5 @@ get the whole paragraph on one page. Reducing the size of the page by increasing the line length by one, seldom seems to work — the looser paragraph typically has a one-word final line, which doesn’t look much better than the straight widow.) -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widows">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widows</a> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widows">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=widows</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wordcount.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wordcount.html index 009eb58bd82..36b42d6fb41 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wordcount.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wordcount.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label wordcount</title> </head><body> <h3>How many words have you written?</h3> -<p>One often has to submit a document (e.g., a paper or a dissertation) +<p/>One often has to submit a document (e.g., a paper or a dissertation) under some sort of constraint about its size. Sensible people set a constraint in terms of numbers of pages, but there are some that persist in limiting the numbers of words you type. -<p>A simple solution to the requirement can be achieved following a +<p/>A simple solution to the requirement can be achieved following a simple observation: the powers that be are unlikely to count all the words of a document submitted to them. Therefore, a statistical method can be employed: find how many words there are on a full page; @@ -16,7 +16,7 @@ integer); multiply the two. However, if the document to be submitted is to determine the success of the rest of one’s life, it takes a brave person to thumb their nose at authority quite so comprehensively... -<p>The simplest method is to strip out the (La)TeX markup, and to count +<p/>The simplest method is to strip out the (La)TeX markup, and to count what’s left. On a Unix-like system, this may be done using <i>detex</i> and the built-in <i>wc</i>: <pre> @@ -27,7 +27,7 @@ The <i>latexcount</i> script does the same sort of job, in one easily configured (see documentation inside the script). <i>Winedt</i> (see <a href="FAQ-editors.html">editors and shells</a>) provides this functionality direct in the Windows environment. -<p>Simply stripping (La)TeX markup isn’t entirely reliable, however: +<p/>Simply stripping (La)TeX markup isn’t entirely reliable, however: that markup itself may contribute typeset words, and this could be a problem. The <i>wordcount</i> package contains a Bourne shell (i.e., typically Unix) script for running a @@ -38,6 +38,6 @@ accurate automatic counting as you can get. <dt><tt><i>detex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/detex.zip">support/detex</a> (<a href="ftp://cam.ctan.org/tex-archive/support/detex.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/detex/">browse</a>) <dt><tt><i>wordcount</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/wordcount.zip">macros/latex/contrib/wordcount</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/wordcount.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/wordcount/">browse</a>) </dl> -<p> -<p><p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wordcount">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wordcount</a> +<p/> +<p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wordcount">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wordcount</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-writecls.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-writecls.html index 846e1509a5e..492b1347ae9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-writecls.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-writecls.html @@ -2,11 +2,11 @@ <title>UK TeX FAQ -- question label writecls</title> </head><body> <h3>Learning to write LaTeX classes and packages</h3> -<p>There’s nothing particularly magic about the commands you use when +<p/>There’s nothing particularly magic about the commands you use when writing a package, so you can simply bundle up a set of LaTeX <code>\</code><code>(re)newcommand</code> and <code>\</code><code>(re)newenvironment</code> commands, put them in a file <i>package.sty</i> and you have a package. -<p>However, any but the most trivial package will require rather more +<p/>However, any but the most trivial package will require rather more sophistication. Some details of LaTeX commands for the job are to be found in ‘LaTeX2e for class and package writers’ (<i>clsguide</i>, part of the LaTeX documentation distribution). @@ -20,23 +20,24 @@ source of LaTeX may be prepared by processing the file <i>source2e.tex</i> in the LaTeX distribution, but individual files in the distribution may be processed separately with LaTeX, like any well-constructed <a href="FAQ-dtx.html"><code>.dtx</code> file</a>. -<p>Writing good classes is not easy; it’s a good idea to read some +<p/>Writing good classes is not easy; it’s a good idea to read some established ones (<i>classes.dtx</i>, for example, is the documented source of the standard classes other than <i>Letter</i>, and may itself be formatted with LaTeX). Classes that are not part of the distribution are commonly based on ones that are, and start by loading the standard class with <code>\</code><code>LoadClass</code> — an example of this technique may be seen in <i>ltxguide.cls</i> -<p>An -<a href="http://www.tug.org/pracjourn/2006-4/flynn/flynn.pdf">annotated version of <i>article</a></i>, -as it appears in <i>classes.dtx</i>, was published in the PracTeX -Journal 2006, No. 4. The article is by Peter Flynn, and offers a -slightly easier way in to understanding <i>classes.dtx</i> +<p/>An +<a href="http://tug.org/TUGboat/Articles/tb28-1/tb88flynn.pdf">annotated version of <i>article</a></i>, +as it appears in <i>classes.dtx</i>, was published in +<i>TUGboat</i> 28(1). The article, by Peter Flynn, which is some help in +understanding <i>classes.dtx</i> <dl> <dt><tt><i>classes.dtx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/base/classes.dtx">macros/latex/base/classes.dtx</a> +<dt><tt><i>clsguide.pdf</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/doc/clsguide.pdf">macros/latex/doc/clsguide.pdf</a> <dt><tt><i>ltxguide.cls</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/base/ltxguide.cls">macros/latex/base/ltxguide.cls</a> <dt><tt><i>LaTeX documentation</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/doc.zip">macros/latex/doc</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/doc.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/doc/">browse</a>) <dt><tt><i>source2e.tex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/base/source2e.tex">macros/latex/base/source2e.tex</a> </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=writecls">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=writecls</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=writecls">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=writecls</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wrongpn.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wrongpn.html index 6eb4a8d9fe4..9acc7076e44 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wrongpn.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-wrongpn.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label wrongpn</title> </head><body> <h3>Page number is wrong at start of page</h3> -<p>This is a long story, whose sources are deep inside the workings of +<p/>This is a long story, whose sources are deep inside the workings of TeX itself; it all derives from the TeX’s striving to generate the best possible output. -<p>The page number is conventionally stored in <code>\</code><code>count0</code>; LaTeX +<p/>The page number is conventionally stored in <code>\</code><code>count0</code>; LaTeX users see this as the counter <code>page</code>, and may typeset its value using <code>\</code><code>thepage</code>. -<p>The number (that is to say, <code>\</code><code>count0</code>) is only updated when TeX +<p/>The number (that is to say, <code>\</code><code>count0</code>) is only updated when TeX actually outputs a page. TeX only even tries to do this when it detects a hint that it may be a good thing to do. From TeX’s point of view, the end of a paragraph is a good time to consider outputting @@ -19,7 +19,7 @@ hand makes some optimisations possible.) As a result, <code>\</code><code>count page (the exception is where the page number has been “forcibly” changed, either by changing its value directly, or by breaking the page where TeX wouldn’t necessarily have chosen to break). -<p>LaTeX provides a safe way of referring to the page number, by using +<p/>LaTeX provides a safe way of referring to the page number, by using label references. So, rather than writing: <blockquote> <pre> @@ -35,5 +35,5 @@ Here is page \pageref{here}\label{here}. (note: no space between the <code>\</code><code>pageref</code> and the <code>\</code><code>label</code>, since that could potentially end up as a page-break space itself, which rather defeats the purpose of the exercise!). -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wrongpn">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wrongpn</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wrongpn">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=wrongpn</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xetex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xetex.html index 8e28391e537..f7b87439694 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xetex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xetex.html @@ -2,19 +2,20 @@ <title>UK TeX FAQ -- question label xetex</title> </head><body> <h3>The XeTeX project</h3> -<p>XeTeX (by Jonathan Kew) is a successor to the shareware TeX/GX -program. It is a Unicode-based (UTF-8) TeX implementation which -is able to make use of Mac OS X AAT (Apple Advanced Typography) -<code>.dfonts</code> and OpenType fonts. It uses Apple’s Quartz system -(which facilitates the afore-mentioned font access) to generate -PDF output. -<p>A Linux version has been announced (2006); that version of course -can’t use AAT fonts, and relies on OpenType fonts alone. -<p>The project has a <a href="http://scripts.sil.org/xetex">web site</a> for +<p/>XeTeX (by Jonathan Kew) is a successor to the shareware TeX/GX +program for Macintoshes. It is a Unicode-based (UTF-8) TeX +implementation which is able to make use of Mac OS X AAT +(Apple Advanced Typography) <code>.dfonts</code> and OpenType fonts. It +uses Apple’s Quartz system (which facilitates the afore-mentioned font +access) to generate PDF output. XeTeX supports Unicode +character sets and bidirectional typesetting, and is widely used by +people studying linguistics, as well as an increasing range of people +working in other fields. +<p/>A Linux and Unix-system version is available in TeX-live 2007; that +version (of course) relies on OpenType fonts alone. A version is +planned for MiKTeX version 2.7 (currently planned for December 2007). +<p/>The project has a <a href="http://scripts.sil.org/xetex">web site</a> for the user who wants more than this simple answer, and you can also sign up to a <a href="http://www.tug.org/mailman/listinfo/xetex">mailing list</a>. -<p> -<p> - -<p><p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=xetex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=xetex</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=xetex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=xetex</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xspace.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xspace.html index e3cc9c77a6a..ff4cbfb70d1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xspace.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-xspace.html @@ -2,12 +2,12 @@ <title>UK TeX FAQ -- question label xspace</title> </head><body> <h3>Commands gobble following space</h3> -<p>People are forever surprised that simple commands gobble the space +<p/>People are forever surprised that simple commands gobble the space after them: this is just the way it is. The effect arises from the way TeX works, and Lamport describes a solution (place a pair of braces after a command’s invocation) in the description of LaTeX syntax. Thus the requirement is in effect part of the definition of LaTeX. -<p>This FAQ, +<p/>This FAQ, for example, is written with definitions that <em>require</em> one to type <code>\</code><code>fred{}</code> @@ -16,12 +16,12 @@ of whether the following space is required: however, this FAQ is written by highly dedicated (and, some would say, eccentric) people. Many users find all those braces become very tedious very quickly, and would really rather not type them all. -<p>An alternative structure, that doesn’t violate the design of LaTeX, +<p/>An alternative structure, that doesn’t violate the design of LaTeX, is to say <code>\</code><code>fred</code><code>\</code><code> </code> — the <code>\</code><code> </code> command is “self terminating” (like <code>\</code><code>\</code>) and you don’t need braces after <em>it</em>. Thus one can reduce to one the extra characters one needs to type. -<p>If even that one character is too many, the package <i>xspace</i> +<p/>If even that one character is too many, the package <i>xspace</i> defines a command <code>\</code><code>xspace</code> that guesses whether there should have been a space after it, and if so introduces that space. So @@ -42,7 +42,7 @@ and we find \restenergy available to us... The <code>\</code><code>xspace</code> command must be the last thing in your macro definition (as in the example); it’s not completely foolproof, but it copes with most obvious situations in running text. -<p>The <i>xspace</i> package doesn’t save you anything if you only use +<p/>The <i>xspace</i> package doesn’t save you anything if you only use a modified macro once or twice within your document. In any case, be careful with usage of <code>\</code><code>xspace</code> — it changes your input syntax, which can be confusing, notably to a collaborating author @@ -52,5 +52,5 @@ don’t). Of course, no command built into LaTeX or into any <dl> <dt><tt><i>xspace.sty</i></tt><dd>Distributed as part of <a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.zip">macros/latex/required/tools</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/required/tools.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/required/tools/">browse</a>) </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=xspace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=xspace</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=xspace">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=xspace</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-y2k.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-y2k.html index db789c10e78..6a2fc01eff3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-y2k.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-y2k.html @@ -2,7 +2,7 @@ <title>UK TeX FAQ -- question label y2k</title> </head><body> <h3>Are TeX and friends Y2K compliant?</h3> -<p><dl> +<p/><dl> <dt>Crashing:<dd> None of TeX, Metafont or MetaPost can themselves crash due to any change whatever in the date of any sort. <dt>Timestamps:<dd> In the original sources, a 2-digit year was @@ -10,7 +10,7 @@ printed in logfiles. These items should not be of general concern, since the only use of the date format file is to produce the log output, and the log file is designed for human readers only. -<p> Knuth announced in 1998 that implementators could +<p/> Knuth announced in 1998 that implementators could alter this code without fear of being accused of non-compliance. Nearly all implementations that are being actively maintained had been modified to generate 4-digit years in the format file and the @@ -26,10 +26,10 @@ “the current year of our Lord”, which is the only correct meaning for <code>\</code><code>year</code> for those implementations which can supply a meaningful value, which is to say nearly all of them. -<p> In short, TeX implementations should provide a value in <code>\</code><code>year</code> +<p/> In short, TeX implementations should provide a value in <code>\</code><code>year</code> giving the 4-digit year Anno Domini, or the value 1776 if the platform does not support a date function. -<p> Note that if the system itself fails to deliver a correct date to +<p/> Note that if the system itself fails to deliver a correct date to TeX, then <code>\</code><code>year</code> will of course return an incorrect value. TeX cannot be considered Y2K compliant, in this sense, on a system that is not itself Y2K compliant. @@ -39,9 +39,9 @@ performs such calculations in a small number of places; the calculations performed in the current (supported) version of LaTeX are known to be Y2K compliant. -<p> Other macros and macro packages should be individually checked. +<p/> Other macros and macro packages should be individually checked. <dt>External software:<dd> Software such as DVI translators needs to be individually checked. </dl> -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=y2k">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=y2k</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=y2k">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=y2k</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-zerochap.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-zerochap.html index fc4378c261a..a8fd0ecdc70 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-zerochap.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-zerochap.html @@ -2,17 +2,17 @@ <title>UK TeX FAQ -- question label zerochap</title> </head><body> <h3>Why are my sections numbered 0.1 ...?</h3> -<p>This happens when your document is using the standard <i>book</i> or +<p/>This happens when your document is using the standard <i>book</i> or <i>report</i> class (or one similar), and you’ve got a <code>\</code><code>section</code> before your first <code>\</code><code>chapter</code>. -<p>What happens is, that the class numbers sections as +<p/>What happens is, that the class numbers sections as “<<i>chapter no</i>>.<<i>section no</i>>”, and until the first chapter has appeared, the chapter number is 0. -<p>If you’re doing this, it’s quite likely that the <i>article</i> class +<p/>If you’re doing this, it’s quite likely that the <i>article</i> class is for you; try it and see. Otherwise, give your sections a ‘superior’ chapter, or do away with section numbering by using <code>\</code><code>section*</code> instead. An alternative way of avoiding numbering is discussed in “<a href="FAQ-secnumdep.html">unnumbered sections in the table of contents</a>”. -<p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=zerochap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=zerochap</a> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=zerochap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=zerochap</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/index.html b/Master/texmf-doc/doc/english/FAQ-en/html/index.html index da4e7e2732b..d663bc845e6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/index.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/index.html @@ -1,24 +1,24 @@ <h2>Introduction</h2> -<p>This is a set of Frequently Asked Questions (FAQ) for +<p/>This is a set of Frequently Asked Questions (FAQ) for English-speaking users of TeX. The questions answered here cover a wide range of topics, but the actual typesetting issues are mostly covered from the viewpoint of a LaTeX user. -<p>You may use the FAQ +<p/>You may use the FAQ <ul> <li> by reading a printed document, -<li> by browsing a PDF file: copies, with hyperlinks to assist - browsing, are to be found on CTAN at <a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq/newfaq.pdf">help/uk-tex-faq/newfaq.pdf</a> - (formatted for A4 paper) or at <a href="ftp://cam.ctan.org/tex-archive/help/uk-tex-faq/letterfaq.pdf">help/uk-tex-faq/letterfaq.pdf</a> (formatted for - North American “letter” paper), or +<li> by viewing a PDF file, with hyperlinks to assist + browsing: copies are available formatted for printing on + <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/newfaq.pdf">A4 paper</a> or on + <a href="http://www.tex.ac.uk/tex-archive/help/uk-tex-faq/letterfaq.pdf">North American “letter” paper</a>, or <li> by using the FAQ’s web interface (base URL: <a href="http://www.tex.ac.uk/faq">http://www.tex.ac.uk/faq</a>); this version provides simple search capabilities, as well as a link to Google for a more sophisticated search restricted to the FAQ itself, or -<li> via Scott Pakin’s \CTANhref{visualFAQ}{Visual FAQ}. +<li> via Scott Pakin’s <a href="http://www.tex.ac.uk/tex-archive/info/visualFAQ/visualFAQ.pdf">Visual FAQ</a>. </ul> -<p> +<p/> <b>Caveat: Acquiring files</b> -<p>Most answers in this FAQ provide links for downloading +<p/>Most answers in this FAQ provide links for downloading software; a large proportion of these links direct you to entire directories on the CTAN archives. Unfortunately, some browsers issue a sequence of commands that causes CTAN servers to deny @@ -28,25 +28,25 @@ therefore offers three possible links for downloading directories (that aren’t already designated “browse only”): the links give you <code>.zip</code> and <code>.tar.gz</code> archives, and a link for browsing the directory. -<p>Fortunately, CTAN is switching to statically-generated +<p/>Fortunately, CTAN is switching to statically-generated directory archive files; many directories mentioned in this FAQ will also exist as <code>.zip</code> files on the archives, and won’t fall foul of the browser problem. Of course, if the <code>.zip</code> file does not exist, and the browser is playing up, you will need to use the “browse” link. -<p> -<p><b>Origins</b> -<p>The FAQ was originated by the Committee of the UK TeX +<p/> +<p/><b>Origins</b> +<p/>The FAQ was originated by the Committee of the UK TeX Users’ Group (UK TUG) as a development of a regular posting to the <em>Usenet</em> newsgroup <i>comp.text.tex</i> that was maintained for some time by Bobby Bodenheimer. The first UK version was much re-arranged and corrected from the original, and little of Bodenheimer’s work now remains. -<p>Most members of the committee of UK TUG, over the years -since 1994, have contributed to this FAQ to some extent. The -following people, who have never been members of the committee, have -also contributed help or advice: +<p/>The following people (at least — there are almost certainly others +whose names weren’t correctly recorded) have contributed help or +advice on the development of the FAQ: Donald Arseneau, +Rosemary Bailey, Barbara Beeton, Karl Berry, Giuseppe Bilotta, @@ -62,26 +62,31 @@ Anthony Goreham, Norman Gray, Eitan Gurari, William Hammond, +John Hammond, +Troy Henderson, Hartmut Henkel, John Hobby, Morten Høgholm, Berthold Horn, Ian Hutchinson, Werner Icking, +Alan Jeffrey, Regnor Jernsletten, David Kastrup, Oleg Katsitadze, Isaac Khabaza, Ulrich Klauer, Markus Kohm, +Ryszard Kubiak, Simon Law, Daniel Luecking, +Aditya Mahajan, Sanjoy Mahajan, Andreas Matthias, Brooks Moses, Iain Murray, Vilar Camara Neto, - +Dick Nickalls, Ted Nieland, Hans Nordhaug, Pat Rau, @@ -90,12 +95,15 @@ Piet van Oostrum, Scott Pakin, Oren Patashnik, Steve Peter, +Sebastian Rahtz, Philip Ratcliffe, +Chris Rowley, José Carlos Santos, Walter Schmidt, Hans-Peter Schröcker, Joachim Schrod, Maarten Sneep, +Axel Sommerfeldt, James Szinger, Ulrik Vieth, Mike Vulis, @@ -103,470 +111,484 @@ Chris Walker, Peter Wilson, Rick Zaccone and Reinhard Zierke. -<p> -<p><h3>The Background</h3><ul> -<li><a href="FAQ-whatTeX.html">What is TeX?</a> -<li><a href="FAQ-TeXpronounce.html">How should I pronounce “TeX”?</a> -<li><a href="FAQ-MF.html">What is Metafont?</a> -<li><a href="FAQ-MP.html">What is MetaPost?</a> -<li><a href="FAQ-triptrap.html">How can I be sure it’s really TeX?</a> -<li><a href="FAQ-y2k.html">Are TeX and friends Y2K compliant?</a> -<li><a href="FAQ-etex.html">What is e-TeX?</a> -<li><a href="FAQ-whatpdftex.html">What is PDFTeX?</a> -<li><a href="FAQ-latex.html">What is LaTeX?</a> -<li><a href="FAQ-latex2e.html">What is LaTeX2e?</a> -<li><a href="FAQ-latexpronounce.html">How should I pronounce “LaTeX(2e)”?</a> -<li><a href="FAQ-plainvltx.html">Should I use Plain TeX or LaTeX?</a> -<li><a href="FAQ-LaTeXandPlain.html">How does LaTeX relate to Plain TeX?</a> -<li><a href="FAQ-context.html">What is ConTeXt?</a> -<li><a href="FAQ-AMSpkg.html">What are the AMS packages (AMSTeX, <em>etc</em>.)?</a> -<li><a href="FAQ-eplain.html">What is Eplain?</a> -<li><a href="FAQ-lollipop.html">What is Lollipop?</a> -<li><a href="FAQ-texinfo.html">What is Texinfo?</a> -<li><a href="FAQ-whyfree.html">If TeX is so good, how come it’s free?</a> -<li><a href="FAQ-TeXfuture.html">What is the future of TeX?</a> -<li><a href="FAQ-readtex.html">Reading (La)TeX files</a> -<li><a href="FAQ-notWYSIWYG.html">Why is TeX not a WYSIWYG system?</a> -<li><a href="FAQ-TUGstar.html">TeX User Groups</a> +<p/> +<p/><h3>The Background</h3><ul> +<li><a href="FAQ-whatTeXhtml">What is TeX?</a> +<li><a href="FAQ-TeXpronouncehtml">How should I pronounce “TeX”?</a> +<li><a href="FAQ-MFhtml">What is Metafont?</a> +<li><a href="FAQ-MPhtml">What is MetaPost?</a> +<li><a href="FAQ-triptraphtml">How can I be sure it’s really TeX?</a> +<li><a href="FAQ-y2khtml">Are TeX and friends Y2K compliant?</a> +<li><a href="FAQ-etexhtml">What is e-TeX?</a> +<li><a href="FAQ-whatpdftexhtml">What is PDFTeX?</a> +<li><a href="FAQ-latexhtml">What is LaTeX?</a> +<li><a href="FAQ-latex2ehtml">What is LaTeX2e?</a> +<li><a href="FAQ-latexpronouncehtml">How should I pronounce “LaTeX(2e)”?</a> +<li><a href="FAQ-plainvltxhtml">Should I use Plain TeX or LaTeX?</a> +<li><a href="FAQ-LaTeXandPlainhtml">How does LaTeX relate to Plain TeX?</a> +<li><a href="FAQ-contexthtml">What is ConTeXt?</a> +<li><a href="FAQ-AMSpkghtml">What are the AMS packages (AMSTeX, <em>etc</em>.)?</a> +<li><a href="FAQ-eplainhtml">What is Eplain?</a> +<li><a href="FAQ-lollipophtml">What is Lollipop?</a> +<li><a href="FAQ-texinfohtml">What is Texinfo?</a> +<li><a href="FAQ-whyfreehtml">If TeX is so good, how come it’s free?</a> +<li><a href="FAQ-TeXfuturehtml">What is the future of TeX?</a> +<li><a href="FAQ-readtexhtml">Reading (La)TeX files</a> +<li><a href="FAQ-notWYSIWYGhtml">Why is TeX not a WYSIWYG system?</a> +<li><a href="FAQ-TUGstarhtml">TeX User Groups</a> </ul><h3>Documentation and Help</h3><ul> -<li><a href="FAQ-books.html">Books on TeX and its relations</a> -<li><a href="FAQ-typebooks.html">Books on Type</a> -<li><a href="FAQ-whereFAQ.html">Where to find FAQs</a> -<li><a href="FAQ-gethelp.html">How to get help</a> -<li><a href="FAQ-mailliststar.html">Specialist mailing lists</a> -<li><a href="FAQ-askquestion.html">How to ask a question</a> -<li><a href="FAQ-minxampl.html">How to make a “minimum example”</a> -<li><a href="FAQ-tutorialstar.html">(La)TeX Tutorials, etc.</a> -<li><a href="FAQ-man-tex.html">Online introductions: Plain TeX</a> -<li><a href="FAQ-man-latex.html">Online introductions: LaTeX</a> -<li><a href="FAQ-tutbitslatex.html">Specialised (La)TeX tutorials</a> -<li><a href="FAQ-ref-doc.html">Reference documents</a> -<li><a href="FAQ-doc-wiki.html">WIKI pages for TeX and friends</a> -<li><a href="FAQ-typo-style.html">Typography tutorials</a> -<li><a href="FAQ-doc-dirs.html">Directories of (La)TeX information</a> -<li><a href="FAQ-ol-books.html">Freely available (La)TeX books</a> -<li><a href="FAQ-pkgdoc.html">Documentation of packages</a> -<li><a href="FAQ-writecls.html">Learning to write LaTeX classes and packages</a> -<li><a href="FAQ-mfptutorials.html">Metafont and MetaPost Tutorials</a> -<li><a href="FAQ-BibTeXing.html">BibTeX Documentation</a> -<li><a href="FAQ-symbols.html">Where can I find the symbol for ...</a> -<li><a href="FAQ-docpictex.html">The PiCTeX manual</a> +<li><a href="FAQ-bookshtml">Books on TeX and its relations</a> +<li><a href="FAQ-typebookshtml">Books on Type</a> +<li><a href="FAQ-whereFAQhtml">Where to find FAQs</a> +<li><a href="FAQ-gethelphtml">How to get help</a> +<li><a href="FAQ-mailliststarhtml">Specialist mailing lists</a> +<li><a href="FAQ-askquestionhtml">How to ask a question</a> +<li><a href="FAQ-minxamplhtml">How to make a “minimum example”</a> +<li><a href="FAQ-tutorialstarhtml">(La)TeX Tutorials, etc.</a> +<li><a href="FAQ-man-texhtml">Online introductions: Plain TeX</a> +<li><a href="FAQ-man-latexhtml">Online introductions: LaTeX</a> +<li><a href="FAQ-tutbitslatexhtml">Specialised (La)TeX tutorials</a> +<li><a href="FAQ-ref-dochtml">Reference documents</a> +<li><a href="FAQ-doc-wikihtml">WIKI pages for TeX and friends</a> +<li><a href="FAQ-typo-stylehtml">Typography tutorials</a> +<li><a href="FAQ-doc-dirshtml">Directories of (La)TeX information</a> +<li><a href="FAQ-ol-bookshtml">Freely available (La)TeX books</a> +<li><a href="FAQ-pkgdochtml">Documentation of packages</a> +<li><a href="FAQ-writeclshtml">Learning to write LaTeX classes and packages</a> +<li><a href="FAQ-mfptutorialshtml">Metafont and MetaPost Tutorials</a> +<li><a href="FAQ-BibTeXinghtml">BibTeX Documentation</a> +<li><a href="FAQ-symbolshtml">Where can I find the symbol for ...</a> +<li><a href="FAQ-docpictexhtml">The PicTeX manual</a> </ul><h3>Bits and pieces of (La)TeX</h3><ul> -<li><a href="FAQ-dvi.html">What is a DVI file?</a> -<li><a href="FAQ-driver.html">What is a driver?</a> -<li><a href="FAQ-pk.html">What are PK files?</a> -<li><a href="FAQ-tfm.html">What are TFM files?</a> -<li><a href="FAQ-virtualfonts.html">Virtual fonts</a> -<li><a href="FAQ-specials.html"><code>\</code><code>special</code> commands</a> -<li><a href="FAQ-hyphen.html">How does hyphenation work in TeX?</a> -<li><a href="FAQ-clsvpkg.html">What are LaTeX classes and packages?</a> -<li><a href="FAQ-dtx.html">Documented LaTeX sources (<code>.dtx</code> files)</a> -<li><a href="FAQ-whatenc.html">What are encodings?</a> -<li><a href="FAQ-ECfonts.html">What are the EC fonts?</a> -<li><a href="FAQ-tds.html">What is the TDS?</a> -<li><a href="FAQ-eps.html">What is “Encapsulated PostScript” (“EPS”)</a> -<li><a href="FAQ-adobetypen.html">Adobe font formats</a> -<li><a href="FAQ-resolns.html">What are “resolutions”</a> -<li><a href="FAQ-fontname.html">What is the “Berry naming scheme”</a> +<li><a href="FAQ-dvihtml">What is a DVI file?</a> +<li><a href="FAQ-driverhtml">What is a DVI driver?</a> +<li><a href="FAQ-pkhtml">What are PK files?</a> +<li><a href="FAQ-tfmhtml">What are TFM files?</a> +<li><a href="FAQ-virtualfontshtml">Virtual fonts</a> +<li><a href="FAQ-specialshtml"><code>\</code><code>special</code> commands</a> +<li><a href="FAQ-hyphenhtml">How does hyphenation work in TeX?</a> +<li><a href="FAQ-clsvpkghtml">What are LaTeX classes and packages?</a> +<li><a href="FAQ-dtxhtml">Documented LaTeX sources (<code>.dtx</code> files)</a> +<li><a href="FAQ-whatenchtml">What are encodings?</a> +<li><a href="FAQ-ECfontshtml">What are the EC fonts?</a> +<li><a href="FAQ-tdshtml">What is the TDS?</a> +<li><a href="FAQ-epshtml">What is “Encapsulated PostScript” (“EPS”)</a> +<li><a href="FAQ-adobetypenhtml">Adobe font formats</a> +<li><a href="FAQ-resolnshtml">What are “resolutions”</a> +<li><a href="FAQ-fontnamehtml">What is the “Berry naming scheme”</a> </ul><h3>Acquiring the Software</h3><ul> -<li><a href="FAQ-archives.html">Repositories of TeX material</a> -<li><a href="FAQ-nonfree.html">What’s the CTAN <code>nonfree</code> tree?</a> -<li><a href="FAQ-uploads.html">Contributing a file to the archives</a> -<li><a href="FAQ-findfiles.html">Finding (La)TeX files</a> -<li><a href="FAQ-findfont.html">Finding new fonts</a> -<li><a href="FAQ-CD.html">The TeX Live distribution</a> +<li><a href="FAQ-archiveshtml">Repositories of TeX material</a> +<li><a href="FAQ-nonfreehtml">What’s the CTAN <code>nonfree</code> tree?</a> +<li><a href="FAQ-uploadshtml">Contributing a file to the archives</a> +<li><a href="FAQ-findfileshtml">Finding (La)TeX files</a> +<li><a href="FAQ-findfonthtml">Finding new fonts</a> +<li><a href="FAQ-CDhtml">The TeX collection</a> </ul><h3>TeX Systems</h3><ul> -<li><a href="FAQ-TeXsystems.html">(La)TeX for different machines</a> -<li><a href="FAQ-editors.html">TeX-friendly editors and shells</a> -<li><a href="FAQ-commercial.html">Commercial TeX implementations</a> +<li><a href="FAQ-TeXsystemshtml">(La)TeX for different machines</a> +<li><a href="FAQ-editorshtml">TeX-friendly editors and shells</a> +<li><a href="FAQ-commercialhtml">Commercial TeX implementations</a> </ul><h3>DVI Drivers and Previewers</h3><ul> -<li><a href="FAQ-dvips.html">DVI to PostScript conversion programs</a> -<li><a href="FAQ-HPdrivers.html">DVI drivers for HP LaserJet</a> -<li><a href="FAQ-otherprinters.html">Output to “other” printers</a> -<li><a href="FAQ-previewers.html">DVI previewers</a> -<li><a href="FAQ-dvi-bmp.html">Generating bitmaps from DVI</a> +<li><a href="FAQ-dvipshtml">DVI to PostScript conversion programs</a> +<li><a href="FAQ-HPdrivershtml">DVI drivers for HP LaserJet</a> +<li><a href="FAQ-otherprintershtml">Output to “other” printers</a> +<li><a href="FAQ-previewershtml">DVI previewers</a> +<li><a href="FAQ-dvi-bmphtml">Generating bitmaps from DVI</a> </ul><h3>Support Packages for TeX</h3><ul> -<li><a href="FAQ-fig.html">Fig, a (La)TeX-friendly drawing package</a> -<li><a href="FAQ-texcad.html">TeXCAD, a drawing package for LaTeX</a> -<li><a href="FAQ-spell.html">Spelling checkers for work with TeX</a> -<li><a href="FAQ-wordcount.html">How many words have you written?</a> +<li><a href="FAQ-fightml">Fig, a (La)TeX-friendly drawing package</a> +<li><a href="FAQ-texcadhtml">TeXCAD, a drawing package for LaTeX</a> +<li><a href="FAQ-spellhtml">Spelling checkers for work with TeX</a> +<li><a href="FAQ-wordcounthtml">How many words have you written?</a> </ul><h3>Literate programming</h3><ul> -<li><a href="FAQ-lit.html">What is Literate Programming?</a> -<li><a href="FAQ-webpkgs.html">WEB systems for various languages</a> +<li><a href="FAQ-lithtml">What is Literate Programming?</a> +<li><a href="FAQ-webpkgshtml">WEB systems for various languages</a> </ul><h3>Format conversions</h3><ul> -<li><a href="FAQ-toascii.html">Conversion from (La)TeX to plain text</a> -<li><a href="FAQ-SGML2TeX.html">Conversion from SGML or HTML to TeX</a> -<li><a href="FAQ-LaTeX2HTML.html">Conversion from (La)TeX to HTML</a> -<li><a href="FAQ-fmtconv.html">Other conversions to and from (La)TeX</a> -<li><a href="FAQ-readML.html">Using TeX to read SGML or XML directly</a> -<li><a href="FAQ-recovertex.html">Retrieving (La)TeX from DVI, etc.</a> -<li><a href="FAQ-LaTeXtoPlain.html">Translating LaTeX to Plain TeX</a> +<li><a href="FAQ-toasciihtml">Conversion from (La)TeX to plain text</a> +<li><a href="FAQ-SGML2TeXhtml">Conversion from SGML or HTML to TeX</a> +<li><a href="FAQ-LaTeX2HTMLhtml">Conversion from (La)TeX to HTML</a> +<li><a href="FAQ-fmtconvhtml">Other conversions to and from (La)TeX</a> +<li><a href="FAQ-readMLhtml">Using TeX to read SGML or XML directly</a> +<li><a href="FAQ-recovertexhtml">Retrieving (La)TeX from DVI, etc.</a> +<li><a href="FAQ-LaTeXtoPlainhtml">Translating LaTeX to Plain TeX</a> </ul><h3>Installing (La)TeX files</h3><ul> -<li><a href="FAQ-instpackages.html">Installing a new package</a> -<li><a href="FAQ-wherefiles.html">Where to put new files</a> -<li><a href="FAQ-miktexinst.html">Installing MiKTeX “known packages”</a> -<li><a href="FAQ-tempinst.html">“Temporary” installation of (La)TeX files</a> -<li><a href="FAQ-privinst.html">“Private” installations of files</a> -<li><a href="FAQ-instfont.html">Installing a new font</a> -<li><a href="FAQ-instmffont.html">Installing a font provided as Metafont source</a> -<li><a href="FAQ-instprinterfont.html">Installing a PostScript printer built-in font</a> -<li><a href="FAQ-inst1cm.html">Installing the Bluesky versions of the CM fonts</a> -<li><a href="FAQ-instt1font.html">Installing a Type 1 font</a> +<li><a href="FAQ-installthingshtml">Installing things on a (La)TeX system</a> +<li><a href="FAQ-install-findhtml">Finding packages to install</a> +<li><a href="FAQ-install-unpackhtml">Unpacking LaTeX packages</a> +<li><a href="FAQ-install-dochtml">Generating package documentation</a> +<li><a href="FAQ-inst-wlcfhtml">Installing files “where (La)TeX can find them”</a> +<li><a href="FAQ-what-TDShtml">Which tree to use</a> +<li><a href="FAQ-install-wherehtml">Where to install packages</a> +<li><a href="FAQ-inst-tidyhtml">Tidying up after installation</a> +<li><a href="FAQ-inst-miktexhtml">Installing MiKTeX “known packages”</a> +<li><a href="FAQ-tempinsthtml">“Temporary” installation of (La)TeX files</a> +<li><a href="FAQ-privinsthtml">“Private” installations of files</a> +<li><a href="FAQ-instfonthtml">Installing a new font</a> +<li><a href="FAQ-instmffonthtml">Installing a font provided as Metafont source</a> +<li><a href="FAQ-instprinterfonthtml">Installing a PostScript printer built-in font</a> +<li><a href="FAQ-inst1cmhtml">Installing the Bluesky versions of the CM fonts</a> +<li><a href="FAQ-instt1fonthtml">Installing a Type 1 font</a> </ul><h3>Fonts</h3><ul> </ul><h4>Metafont fonts</h4><ul> -<li><a href="FAQ-useMF.html">Getting Metafont to do what you want</a> -<li><a href="FAQ-keepfonts.html">Which font files should be kept</a> -<li><a href="FAQ-getbitmap.html">Acquiring bitmap fonts</a> +<li><a href="FAQ-useMFhtml">Getting Metafont to do what you want</a> +<li><a href="FAQ-keepfontshtml">Which font files should be kept</a> +<li><a href="FAQ-getbitmaphtml">Acquiring bitmap fonts</a> </ul><h4>Adobe Type 1 (“PostScript”) fonts</h4><ul> -<li><a href="FAQ-usepsfont.html">Using PostScript fonts with TeX</a> -<li><a href="FAQ-PSpreview.html">Previewing files using Type 1 fonts</a> -<li><a href="FAQ-metrics.html">TeX font metric files for PostScript fonts</a> -<li><a href="FAQ-psfontprob.html">Deploying Type 1 fonts</a> -<li><a href="FAQ-psfchoice.html">Choice of scalable outline fonts</a> -<li><a href="FAQ-charshift.html">Weird characters in <i>dvips</i> output</a> +<li><a href="FAQ-usepsfonthtml">Using PostScript fonts with TeX</a> +<li><a href="FAQ-PSpreviewhtml">Previewing files using Type 1 fonts</a> +<li><a href="FAQ-metricshtml">TeX font metric files for PostScript fonts</a> +<li><a href="FAQ-psfontprobhtml">Deploying Type 1 fonts</a> +<li><a href="FAQ-psfchoicehtml">Choice of scalable outline fonts</a> +<li><a href="FAQ-charshifthtml">Weird characters in <i>dvips</i> output</a> </ul><h4>Macros for using fonts</h4><ul> -<li><a href="FAQ-fonts-pln.html">Using non-standard fonts in Plain TeX</a> +<li><a href="FAQ-fonts-plnhtml">Using non-standard fonts in Plain TeX</a> </ul><h4>Particular font families</h4><ul> -<li><a href="FAQ-concrete.html">Using the “Concrete” fonts</a> -<li><a href="FAQ-uselmfonts.html">Using the Latin Modern fonts</a> +<li><a href="FAQ-concretehtml">Using the “Concrete” fonts</a> +<li><a href="FAQ-uselmfontshtml">Using the Latin Modern fonts</a> </ul><h3>Hypertext and PDF</h3><ul> -<li><a href="FAQ-hyper.html">Making hypertext documents from TeX</a> -<li><a href="FAQ-acrobat.html">Making Acrobat PDF documents from (La)TeX</a> -<li><a href="FAQ-dvips-pdf.html">Quality of PDF from PostScript</a> -<li><a href="FAQ-fuzzy-type3.html">The wrong type of fonts in PDF</a> -<li><a href="FAQ-fuzzy-gs.html">Fuzzy fonts because <i>Ghostscript</i> too old</a> -<li><a href="FAQ-fuzzy-T1.html">Fonts go fuzzy when you switch to T1</a> -<li><a href="FAQ-distill-prob.html">Characters missing from PDF output</a> -<li><a href="FAQ-type1T1.html">Finding ‘8-bit’ Type 1 fonts</a> -<li><a href="FAQ-pkfix.html">Replacing Type 3 fonts in PostScript</a> -<li><a href="FAQ-pdfpagelabels.html"><i>Hyperref</i> and repeated page numbers</a> -<li><a href="FAQ-srchpdf.html">Searching PDF files</a> +<li><a href="FAQ-hyperhtml">Making hypertext documents from TeX</a> +<li><a href="FAQ-acrobathtml">Making Acrobat PDF documents from (La)TeX</a> +<li><a href="FAQ-dvips-pdfhtml">Quality of PDF from PostScript</a> +<li><a href="FAQ-fuzzy-type3html">The wrong type of fonts in PDF</a> +<li><a href="FAQ-fuzzy-gshtml">Fuzzy fonts because <i>Ghostscript</i> too old</a> +<li><a href="FAQ-fuzzy-T1html">Fonts go fuzzy when you switch to T1</a> +<li><a href="FAQ-distill-probhtml">Characters missing from PDF output</a> +<li><a href="FAQ-type1T1html">Finding ‘8-bit’ Type 1 fonts</a> +<li><a href="FAQ-pkfixhtml">Replacing Type 3 fonts in PostScript</a> +<li><a href="FAQ-pdfpagelabelshtml"><i>Hyperref</i> and repeated page numbers</a> +<li><a href="FAQ-srchpdfhtml">Searching PDF files</a> </ul><h3>Graphics</h3><ul> -<li><a href="FAQ-impgraph.html">How to import graphics into (La)TeX documents</a> -<li><a href="FAQ-dvipsgraphics.html">Imported graphics in <i>dvips</i></a> -<li><a href="FAQ-pdftexgraphics.html">Imported graphics in PDFLaTeX</a> -<li><a href="FAQ-dvipdfmgraphics.html">Imported graphics in <i>dvipdfm</i></a> -<li><a href="FAQ-graphicspath.html">Importing graphics from “somewhere else”</a> -<li><a href="FAQ-graph-pspdf.html">Portable imported graphics</a> -<li><a href="FAQ-repeatgrf.html">Repeated graphics in a document</a> -<li><a href="FAQ-grmaxwidth.html">Limit the width of imported graphics</a> -<li><a href="FAQ-topgraph.html">Top-aligning imported graphics</a> -<li><a href="FAQ-mpprologues.html">Displaying MetaPost output in <i>ghostscript</i></a> -<li><a href="FAQ-drawing.html">Drawing with TeX</a> -<li><a href="FAQ-drawFeyn.html">Drawing Feynman diagrams in LaTeX</a> -<li><a href="FAQ-labelfig.html">Labelling graphics</a> +<li><a href="FAQ-impgraphhtml">How to import graphics into (La)TeX documents</a> +<li><a href="FAQ-dvipsgraphicshtml">Imported graphics in <i>dvips</i></a> +<li><a href="FAQ-pdftexgraphicshtml">Imported graphics in PDFLaTeX</a> +<li><a href="FAQ-dvipdfmgraphicshtml">Imported graphics in <i>dvipdfm</i></a> +<li><a href="FAQ-graphicspathhtml">Importing graphics from “somewhere else”</a> +<li><a href="FAQ-graph-pspdfhtml">Portable imported graphics</a> +<li><a href="FAQ-repeatgrfhtml">Repeated graphics in a document</a> +<li><a href="FAQ-grmaxwidthhtml">Limit the width of imported graphics</a> +<li><a href="FAQ-topgraphhtml">Top-aligning imported graphics</a> +<li><a href="FAQ-mpprologueshtml">Displaying MetaPost output in <i>ghostscript</i></a> +<li><a href="FAQ-drawinghtml">Drawing with TeX</a> +<li><a href="FAQ-drawFeynhtml">Drawing Feynman diagrams in LaTeX</a> +<li><a href="FAQ-labelfightml">Labelling graphics</a> </ul><h3>Bibliographies and citations</h3><ul> </ul><h4>Creating bibliographies</h4><ul> -<li><a href="FAQ-buildbib.html">Creating a BibTeX bibliography file</a> -<li><a href="FAQ-custbib.html">Creating a bibliography style</a> -<li><a href="FAQ-capbibtex.html">Capitalisation in BibTeX</a> -<li><a href="FAQ-bibaccent.html">Accents in bibliographies</a> -<li><a href="FAQ-bibstrtl.html">‘String too long’ in BibTeX</a> -<li><a href="FAQ-manyauthor.html">BibTeX doesn’t understand lists of names</a> -<li><a href="FAQ-citeURL.html">URLs in BibTeX bibliographies</a> -<li><a href="FAQ-bibplain.html">Using BibTeX with Plain TeX</a> -<li><a href="FAQ-makebib.html">Reconstructing <code>.bib</code> files</a> -<li><a href="FAQ-bibprefixsort.html">BibTeX sorting and name prefixes</a> -<li><a href="FAQ-bibtranscinit.html">Transcribed initials in BibTeX</a> +<li><a href="FAQ-buildbibhtml">Creating a BibTeX bibliography file</a> +<li><a href="FAQ-custbibhtml">Creating a bibliography style</a> +<li><a href="FAQ-capbibtexhtml">Capitalisation in BibTeX</a> +<li><a href="FAQ-bibaccenthtml">Accents in bibliographies</a> +<li><a href="FAQ-bibstrtlhtml">‘String too long’ in BibTeX</a> +<li><a href="FAQ-manyauthorhtml">BibTeX doesn’t understand lists of names</a> +<li><a href="FAQ-citeURLhtml">URLs in BibTeX bibliographies</a> +<li><a href="FAQ-bibplainhtml">Using BibTeX with Plain TeX</a> +<li><a href="FAQ-makebibhtml">Reconstructing <code>.bib</code> files</a> +<li><a href="FAQ-bibprefixsorthtml">BibTeX sorting and name prefixes</a> +<li><a href="FAQ-bibtranscinithtml">Transcribed initials in BibTeX</a> </ul><h4>Creating citations</h4><ul> -<li><a href="FAQ-usebibtex.html">“Normal” use of BibTeX from LaTeX</a> -<li><a href="FAQ-whatbst.html">Choosing a bibliography style</a> -<li><a href="FAQ-chapbib.html">Separate bibliographies per chapter?</a> -<li><a href="FAQ-multbib.html">Multiple bibliographies?</a> -<li><a href="FAQ-bibinline.html">Putting bibliography entries in text</a> -<li><a href="FAQ-citesort.html">Sorting and compressing citations</a> -<li><a href="FAQ-mcite.html">Multiple citations</a> -<li><a href="FAQ-backref.html">References from the bibliography to the citation</a> -<li><a href="FAQ-sortbib.html">Sorting lists of citations</a> -<li><a href="FAQ-compactbib.html">Reducing spacing in the bibliography</a> -<li><a href="FAQ-bibtocorder.html">Table of contents rearranges “<i>unsrt</i>” ordering</a> -<li><a href="FAQ-i18nbib.html">Non-english bibliographies</a> -<li><a href="FAQ-formbiblabel.html">Format of numbers in the bibliography</a> +<li><a href="FAQ-usebibtexhtml">“Normal” use of BibTeX from LaTeX</a> +<li><a href="FAQ-whatbsthtml">Choosing a bibliography style</a> +<li><a href="FAQ-chapbibhtml">Separate bibliographies per chapter?</a> +<li><a href="FAQ-multbibhtml">Multiple bibliographies?</a> +<li><a href="FAQ-bibinlinehtml">Putting bibliography entries in text</a> +<li><a href="FAQ-citesorthtml">Sorting and compressing citations</a> +<li><a href="FAQ-mcitehtml">Multiple citations</a> +<li><a href="FAQ-backrefhtml">References from the bibliography to the citation</a> +<li><a href="FAQ-sortbibhtml">Sorting lists of citations</a> +<li><a href="FAQ-compactbibhtml">Reducing spacing in the bibliography</a> +<li><a href="FAQ-bibtocorderhtml">Table of contents rearranges “<i>unsrt</i>” ordering</a> +<li><a href="FAQ-i18nbibhtml">Non-english bibliographies</a> +<li><a href="FAQ-formbiblabelhtml">Format of numbers in the bibliography</a> </ul><h4>Manipulating whole bibliographies</h4><ul> -<li><a href="FAQ-nocitestar.html">Listing all your BibTeX entries</a> -<li><a href="FAQ-htmlbib.html">Making HTML of your Bibliography</a> +<li><a href="FAQ-nocitestarhtml">Listing all your BibTeX entries</a> +<li><a href="FAQ-htmlbibhtml">Making HTML of your Bibliography</a> </ul><h3>Adjusting the typesetting</h3><ul> </ul><h4>Alternative document classes</h4><ul> -<li><a href="FAQ-replstdcls.html">Replacing the standard classes</a> -<li><a href="FAQ-slidecls.html">Producing slides</a> -<li><a href="FAQ-poster.html">Creating posters with LaTeX</a> -<li><a href="FAQ-thesis.html">Formatting a thesis in LaTeX</a> -<li><a href="FAQ-journalpaper.html">Setting papers for journals</a> -<li><a href="FAQ-multidoc.html">A ‘report’ from lots of ‘article’s</a> -<li><a href="FAQ-cv.html"><em>Curriculum Vitae</em> (Résumé)</a> -<li><a href="FAQ-letterclass.html">Letters and the like</a> -<li><a href="FAQ-extsizes.html">Other “document font” sizes?</a> +<li><a href="FAQ-replstdclshtml">Replacing the standard classes</a> +<li><a href="FAQ-slideclshtml">Producing slides</a> +<li><a href="FAQ-posterhtml">Creating posters with LaTeX</a> +<li><a href="FAQ-thesishtml">Formatting a thesis in LaTeX</a> +<li><a href="FAQ-journalpaperhtml">Setting papers for journals</a> +<li><a href="FAQ-multidochtml">A ‘report’ from lots of ‘article’s</a> +<li><a href="FAQ-cvhtml"><em>Curriculum Vitae</em> (Résumé)</a> +<li><a href="FAQ-letterclasshtml">Letters and the like</a> +<li><a href="FAQ-extsizeshtml">Other “document font” sizes?</a> </ul><h4>Document structure</h4><ul> -<li><a href="FAQ-titlsty.html">The style of document titles</a> -<li><a href="FAQ-secthead.html">The style of section headings</a> -<li><a href="FAQ-appendix.html">Appendixes</a> -<li><a href="FAQ-secindent.html">Indent after section headings</a> -<li><a href="FAQ-subsubsub.html">How to create a <code>\</code><code>subsubsubsection</code></a> -<li><a href="FAQ-captsty.html">The style of captions</a> -<li><a href="FAQ-fancyhdr.html">Alternative head- and footlines in LaTeX</a> -<li><a href="FAQ-widefigs.html">Wide figures in two-column documents</a> -<li><a href="FAQ-onecolabs.html">1-column abstract in 2-column document</a> -<li><a href="FAQ-reallyblank.html">Really blank pages between chapters</a> -<li><a href="FAQ-balance.html">Balancing columns at the end of a document</a> -<li><a href="FAQ-runheadtoobig.html">My section title is too wide for the page header</a> -<li><a href="FAQ-nofm.html">Page numbering “<<i>n</i>> of <<i>m</i>>”</a> -<li><a href="FAQ-pagebychap.html">Page numbering by chapter</a> +<li><a href="FAQ-titlstyhtml">The style of document titles</a> +<li><a href="FAQ-sectheadhtml">The style of section headings</a> +<li><a href="FAQ-appendixhtml">Appendixes</a> +<li><a href="FAQ-secindenthtml">Indent after section headings</a> +<li><a href="FAQ-subsubsubhtml">How to create a <code>\</code><code>subsubsubsection</code></a> +<li><a href="FAQ-captstyhtml">The style of captions</a> +<li><a href="FAQ-fancyhdrhtml">Alternative head- and footlines in LaTeX</a> +<li><a href="FAQ-widefigshtml">Wide figures in two-column documents</a> +<li><a href="FAQ-onecolabshtml">1-column abstract in 2-column document</a> +<li><a href="FAQ-reallyblankhtml">Really blank pages between chapters</a> +<li><a href="FAQ-balancehtml">Balancing columns at the end of a document</a> +<li><a href="FAQ-runheadtoobightml">My section title is too wide for the page header</a> +<li><a href="FAQ-nofmhtml">Page numbering “<<i>n</i>> of <<i>m</i>>”</a> +<li><a href="FAQ-pagebychaphtml">Page numbering by chapter</a> </ul><h4>Page layout</h4><ul> -<li><a href="FAQ-papersize.html">Printer paper sizes</a> -<li><a href="FAQ-changemargin.html">Changing the margins in LaTeX</a> -<li><a href="FAQ-marginpkgs.html">Packages to set up page designs</a> -<li><a href="FAQ-marginmanual.html">How to set up page layout “by hand”</a> -<li><a href="FAQ-chngmargonfly.html">Changing margins “on the fly”</a> -<li><a href="FAQ-nopageno.html">How to get rid of page numbers</a> -<li><a href="FAQ-psatempty.html"><code>\pagestyle{empty}</code> on first page in LaTeX</a> -<li><a href="FAQ-crop.html">How to create crop marks</a> -<li><a href="FAQ-watermark.html">‘Watermarks’ on every page</a> -<li><a href="FAQ-landscape.html">Typesetting things in landscape orientation</a> -<li><a href="FAQ-abspos.html">Putting things at fixed positions on the page</a> -<li><a href="FAQ-nopagebrk.html">Preventing page breaks between lines</a> -<li><a href="FAQ-parallel.html">Parallel setting of text</a> -<li><a href="FAQ-epigraph.html">Typesetting epigraphs</a> -<li><a href="FAQ-outszwrng.html">(La)TeX PDF output prints at wrong size</a> +<li><a href="FAQ-papersizehtml">Printer paper sizes</a> +<li><a href="FAQ-changemarginhtml">Changing the margins in LaTeX</a> +<li><a href="FAQ-marginpkgshtml">Packages to set up page designs</a> +<li><a href="FAQ-marginmanualhtml">How to set up page layout “by hand”</a> +<li><a href="FAQ-chngmargonflyhtml">Changing margins “on the fly”</a> +<li><a href="FAQ-nopagenohtml">How to get rid of page numbers</a> +<li><a href="FAQ-psatemptyhtml"><code>\pagestyle{empty}</code> on first page in LaTeX</a> +<li><a href="FAQ-crophtml">How to create crop marks</a> +<li><a href="FAQ-watermarkhtml">‘Watermarks’ on every page</a> +<li><a href="FAQ-landscapehtml">Typesetting things in landscape orientation</a> +<li><a href="FAQ-absposhtml">Putting things at fixed positions on the page</a> +<li><a href="FAQ-nopagebrkhtml">Preventing page breaks between lines</a> +<li><a href="FAQ-parallelhtml">Parallel setting of text</a> +<li><a href="FAQ-epigraphhtml">Typesetting epigraphs</a> +<li><a href="FAQ-outszwrnghtml">(La)TeX PDF output prints at wrong size</a> </ul><h4>Spacing of characters and lines</h4><ul> -<li><a href="FAQ-linespace.html">Double-spaced documents in LaTeX</a> -<li><a href="FAQ-letterspace.html">Changing the space between letters</a> -<li><a href="FAQ-ragright.html">Setting text ragged right</a> -<li><a href="FAQ-flushboth.html">Cancelling <code>\</code><code>ragged</code> commands</a> +<li><a href="FAQ-linespacehtml">Double-spaced documents in LaTeX</a> +<li><a href="FAQ-letterspacehtml">Changing the space between letters</a> +<li><a href="FAQ-ragrighthtml">Setting text ragged right</a> +<li><a href="FAQ-flushbothhtml">Cancelling <code>\</code><code>ragged</code> commands</a> </ul><h4>Typesetting specialities</h4><ul> -<li><a href="FAQ-verbfile.html">Including a file verbatim in LaTeX</a> -<li><a href="FAQ-linenos.html">Including line numbers in typeset output</a> -<li><a href="FAQ-codelist.html">Code listings in LaTeX</a> -<li><a href="FAQ-algorithms.html">Typesetting pseudocode in LaTeX</a> -<li><a href="FAQ-makeindex.html">Generating an index in (La)TeX</a> -<li><a href="FAQ-setURL.html">Typesetting URLs</a> -<li><a href="FAQ-music.html">Typesetting music in TeX</a> -<li><a href="FAQ-parskip.html">Zero paragraph indent</a> -<li><a href="FAQ-dropping.html">Big letters at the start of a paragraph</a> -<li><a href="FAQ-dec_comma.html">The comma as a decimal separator</a> -<li><a href="FAQ-breakbox.html">Breaking boxes of text</a> -<li><a href="FAQ-overstrike.html">Overstriking characters</a> -<li><a href="FAQ-upquot.html">Realistic quotes for verbatim listings</a> -<li><a href="FAQ-time.html">Printing the time</a> -<li><a href="FAQ-the-commands.html">Redefining counters’ <code>\</code><code>the-</code>commands</a> +<li><a href="FAQ-verbfilehtml">Including a file verbatim in LaTeX</a> +<li><a href="FAQ-linenoshtml">Including line numbers in typeset output</a> +<li><a href="FAQ-codelisthtml">Code listings in LaTeX</a> +<li><a href="FAQ-algorithmshtml">Typesetting pseudocode in LaTeX</a> +<li><a href="FAQ-makeindexhtml">Generating an index in (La)TeX</a> +<li><a href="FAQ-setURLhtml">Typesetting URLs</a> +<li><a href="FAQ-musichtml">Typesetting music in TeX</a> +<li><a href="FAQ-parskiphtml">Zero paragraph indent</a> +<li><a href="FAQ-droppinghtml">Big letters at the start of a paragraph</a> +<li><a href="FAQ-dec_commahtml">The comma as a decimal separator</a> +<li><a href="FAQ-breakboxhtml">Breaking boxes of text</a> +<li><a href="FAQ-overstrikehtml">Overstriking characters</a> +<li><a href="FAQ-upquothtml">Realistic quotes for verbatim listings</a> +<li><a href="FAQ-timehtml">Printing the time</a> +<li><a href="FAQ-the-commandshtml">Redefining counters’ <code>\</code><code>the-</code>commands</a> </ul><h4>Tables of contents and indexes</h4><ul> -<li><a href="FAQ-tocloft.html">The format of the Table of Contents, etc.</a> -<li><a href="FAQ-secnumdep.html">Unnumbered sections in the Table of Contents</a> -<li><a href="FAQ-tocbibind.html">Bibliography, index, etc., in TOC</a> -<li><a href="FAQ-minitoc.html">Table of contents, etc., per chapter</a> -<li><a href="FAQ-multind.html">Multiple indexes</a> +<li><a href="FAQ-toclofthtml">The format of the Table of Contents, etc.</a> +<li><a href="FAQ-secnumdephtml">Unnumbered sections in the Table of Contents</a> +<li><a href="FAQ-tocbibindhtml">Bibliography, index, etc., in TOC</a> +<li><a href="FAQ-minitochtml">Table of contents, etc., per chapter</a> +<li><a href="FAQ-multindhtml">Multiple indexes</a> </ul><h4>Labels and references</h4><ul> -<li><a href="FAQ-nameref.html">Referring to things by their name</a> -<li><a href="FAQ-extref.html">Referring to labels in other documents</a> +<li><a href="FAQ-namerefhtml">Referring to things by their name</a> +<li><a href="FAQ-extrefhtml">Referring to labels in other documents</a> </ul><h3>How do I do...?</h3><ul> </ul><h4>Mathematics</h4><ul> -<li><a href="FAQ-proof.html">Proof environment</a> -<li><a href="FAQ-theoremfmt.html">Roman theorems</a> -<li><a href="FAQ-newfunction.html">Defining a new log-like function in LaTeX</a> -<li><a href="FAQ-braket.html">Set specifications and Dirac brackets</a> -<li><a href="FAQ-cancellation.html">Cancelling terms in maths expressions</a> -<li><a href="FAQ-mathsize.html">Adjusting maths font sizes</a> -<li><a href="FAQ-mathlips.html">Ellipses</a> -<li><a href="FAQ-limits.html">Sub- and superscript positioning for operators</a> -<li><a href="FAQ-mathstext.html">Text inside maths</a> -<li><a href="FAQ-reuseq.html">Re-using an equation</a> -<li><a href="FAQ-brkinline.html">Line-breaking in in-line maths</a> +<li><a href="FAQ-proofhtml">Proof environment</a> +<li><a href="FAQ-theoremfmthtml">Roman theorems</a> +<li><a href="FAQ-newfunctionhtml">Defining a new log-like function in LaTeX</a> +<li><a href="FAQ-brakethtml">Set specifications and Dirac brackets</a> +<li><a href="FAQ-cancellationhtml">Cancelling terms in maths expressions</a> +<li><a href="FAQ-mathsizehtml">Adjusting maths font sizes</a> +<li><a href="FAQ-mathlipshtml">Ellipses</a> +<li><a href="FAQ-limitshtml">Sub- and superscript positioning for operators</a> +<li><a href="FAQ-mathstexthtml">Text inside maths</a> +<li><a href="FAQ-reuseqhtml">Re-using an equation</a> +<li><a href="FAQ-brkinlinehtml">Line-breaking in in-line maths</a> +<li><a href="FAQ-mathonlyrefhtml">Numbers for referenced equations only</a> </ul><h4>Lists</h4><ul> -<li><a href="FAQ-enumerate.html">Fancy enumeration lists</a> -<li><a href="FAQ-complist.html">How to reduce list spacing</a> -<li><a href="FAQ-interruptlist.html">Interrupting enumerated lists</a> +<li><a href="FAQ-enumeratehtml">Fancy enumeration lists</a> +<li><a href="FAQ-complisthtml">How to adjust list spacing</a> +<li><a href="FAQ-interruptlisthtml">Interrupting enumerated lists</a> </ul><h4>Tables, figures and diagrams</h4><ul> -<li><a href="FAQ-destable.html">The design of tables</a> -<li><a href="FAQ-fixwidtab.html">Fixed-width tables</a> -<li><a href="FAQ-varwidcol.html">Variable-width columns in tables</a> -<li><a href="FAQ-struttab.html">Spacing lines in tables</a> -<li><a href="FAQ-longtab.html">Tables longer than a single page</a> -<li><a href="FAQ-tabcellalign.html">How to alter the alignment of tabular cells</a> -<li><a href="FAQ-rulethk.html">The thickness of rules in LaTeX tables</a> -<li><a href="FAQ-textflow.html">Flowing text around figures in LaTeX</a> -<li><a href="FAQ-slashbox.html">Diagonal separation in corner cells of tables</a> -<li><a href="FAQ-wholerow.html">How to change a whole row of a table</a> -<li><a href="FAQ-multirow.html">Merging cells in a column of a table</a> +<li><a href="FAQ-destablehtml">The design of tables</a> +<li><a href="FAQ-fixwidtabhtml">Fixed-width tables</a> +<li><a href="FAQ-varwidcolhtml">Variable-width columns in tables</a> +<li><a href="FAQ-struttabhtml">Spacing lines in tables</a> +<li><a href="FAQ-longtabhtml">Tables longer than a single page</a> +<li><a href="FAQ-tabcellalignhtml">How to alter the alignment of tabular cells</a> +<li><a href="FAQ-rulethkhtml">The thickness of rules in LaTeX tables</a> +<li><a href="FAQ-textflowhtml">Flowing text around figures in LaTeX</a> +<li><a href="FAQ-slashboxhtml">Diagonal separation in corner cells of tables</a> +<li><a href="FAQ-wholerowhtml">How to change a whole row of a table</a> +<li><a href="FAQ-multirowhtml">Merging cells in a column of a table</a> </ul><h4>Floating tables, figures, etc.</h4><ul> -<li><a href="FAQ-floatpages.html">Floats on their own on float pages</a> -<li><a href="FAQ-vertspacefloat.html">Extra vertical space in floats</a> -<li><a href="FAQ-2colfloat.html">Placing two-column floats at bottom of page</a> -<li><a href="FAQ-mcfloat.html">Floats in multicolumn setting</a> -<li><a href="FAQ-dpfloat.html">Facing floats on 2-page spread</a> -<li><a href="FAQ-vertposfp.html">Vertical layout of float pages</a> +<li><a href="FAQ-floatpageshtml">Floats on their own on float pages</a> +<li><a href="FAQ-vertspacefloathtml">Extra vertical space in floats</a> +<li><a href="FAQ-2colfloathtml">Placing two-column floats at bottom of page</a> +<li><a href="FAQ-mcfloathtml">Floats in multicolumn setting</a> +<li><a href="FAQ-dpfloathtml">Facing floats on 2-page spread</a> +<li><a href="FAQ-vertposfphtml">Vertical layout of float pages</a> +<li><a href="FAQ-figureherehtml">Figure (or table) <em>exactly</em> where I want it</a> </ul><h4>Footnotes</h4><ul> -<li><a href="FAQ-footintab.html">Footnotes in tables</a> -<li><a href="FAQ-ftnsect.html">Footnotes in LaTeX section headings</a> -<li><a href="FAQ-ftncapt.html">Footnotes in captions</a> -<li><a href="FAQ-repfootnote.html">Footnotes whose texts are identical</a> -<li><a href="FAQ-multfoot.html">More than one sequence of footnotes</a> -<li><a href="FAQ-footnpp.html">Footnotes numbered “per page”</a> +<li><a href="FAQ-footintabhtml">Footnotes in tables</a> +<li><a href="FAQ-ftnsecthtml">Footnotes in LaTeX section headings</a> +<li><a href="FAQ-ftncapthtml">Footnotes in captions</a> +<li><a href="FAQ-repfootnotehtml">Footnotes whose texts are identical</a> +<li><a href="FAQ-multfoothtml">More than one sequence of footnotes</a> +<li><a href="FAQ-footnpphtml">Footnotes numbered “per page”</a> +<li><a href="FAQ-run-fn-noshtml">Not resetting footnote numbers per chapter</a> </ul><h4>Document management</h4><ul> -<li><a href="FAQ-filename.html">What’s the name of this file</a> -<li><a href="FAQ-filesused.html">All the files used by this document</a> -<li><a href="FAQ-changebars.html">Marking changed parts of your document</a> -<li><a href="FAQ-conditional.html">Conditional compilation and “comments”</a> -<li><a href="FAQ-docotherdir.html">Bits of document from other directories</a> -<li><a href="FAQ-RCS.html">Version control using RCS, CVS or <i>Subversion</i></a> -<li><a href="FAQ-make.html">Makefiles for LaTeX documents</a> -<li><a href="FAQ-howmanypp.html">How many pages are there in my document?</a> -<li><a href="FAQ-inclplain.html">Including Plain TeX files in LaTeX</a> +<li><a href="FAQ-filenamehtml">What’s the name of this file</a> +<li><a href="FAQ-filesusedhtml">All the files used by this document</a> +<li><a href="FAQ-changebarshtml">Marking changed parts of your document</a> +<li><a href="FAQ-conditionalhtml">Conditional compilation and “comments”</a> +<li><a href="FAQ-docotherdirhtml">Bits of document from other directories</a> +<li><a href="FAQ-RCShtml">Version control using RCS, CVS or <i>Subversion</i></a> +<li><a href="FAQ-makehtml">Makefiles for LaTeX documents</a> +<li><a href="FAQ-howmanypphtml">How many pages are there in my document?</a> +<li><a href="FAQ-inclplainhtml">Including Plain TeX files in LaTeX</a> </ul><h4>Hyphenation</h4><ul> -<li><a href="FAQ-nohyph.html">My words aren’t being hyphenated</a> -<li><a href="FAQ-weirdhyphen.html">Weird hyphenation of words</a> -<li><a href="FAQ-oddhyphen.html">(Merely) peculiar hyphenation</a> -<li><a href="FAQ-hyphenaccents.html">Accented words aren’t hyphenated</a> -<li><a href="FAQ-newlang.html">Using a new language with Babel</a> -<li><a href="FAQ-hyphoff.html">Stopping all hyphenation</a> -<li><a href="FAQ-wdnohyph.html">Preventing hyphenation of a particular word</a> -<li><a href="FAQ-hyphexcept.html">Hyphenation exceptions</a> +<li><a href="FAQ-nohyphhtml">My words aren’t being hyphenated</a> +<li><a href="FAQ-weirdhyphenhtml">Weird hyphenation of words</a> +<li><a href="FAQ-oddhyphenhtml">(Merely) peculiar hyphenation</a> +<li><a href="FAQ-hyphenaccentshtml">Accented words aren’t hyphenated</a> +<li><a href="FAQ-newlanghtml">Using a new language with Babel</a> +<li><a href="FAQ-hyphoffhtml">Stopping all hyphenation</a> +<li><a href="FAQ-wdnohyphhtml">Preventing hyphenation of a particular word</a> +<li><a href="FAQ-hyphexcepthtml">Hyphenation exceptions</a> </ul><h4>Odds and ends</h4><ul> -<li><a href="FAQ-logos.html">Typesetting all those TeX-related logos</a> -<li><a href="FAQ-bold-extras.html">How to do bold-tt or bold-sc</a> -<li><a href="FAQ-varwidth.html">Automatic sizing of <code>minipage</code></a> +<li><a href="FAQ-logoshtml">Typesetting all those TeX-related logos</a> +<li><a href="FAQ-bold-extrashtml">How to do bold-tt or bold-sc</a> +<li><a href="FAQ-varwidthhtml">Automatic sizing of <code>minipage</code></a> </ul><h3>Symbols, etc.</h3><ul> -<li><a href="FAQ-numbersets.html">Symbols for the number sets</a> -<li><a href="FAQ-scriptfonts.html">Better script fonts for maths</a> -<li><a href="FAQ-boldgreek.html">Setting bold Greek letters in LaTeX</a> -<li><a href="FAQ-prinvalint.html">The Principal Value Integral symbol</a> -<li><a href="FAQ-underscore.html">How to use the underscore character</a> -<li><a href="FAQ-atsign.html">How to type an ‘@’ sign?</a> -<li><a href="FAQ-euro.html">Typesetting the Euro sign</a> -<li><a href="FAQ-tradesyms.html">How to get copyright, trademark, etc.</a> +<li><a href="FAQ-numbersetshtml">Symbols for the number sets</a> +<li><a href="FAQ-scriptfontshtml">Better script fonts for maths</a> +<li><a href="FAQ-boldgreekhtml">Setting bold Greek letters in LaTeX</a> +<li><a href="FAQ-prinvalinthtml">The Principal Value Integral symbol</a> +<li><a href="FAQ-underscorehtml">How to use the underscore character</a> +<li><a href="FAQ-atsignhtml">How to type an ‘@’ sign?</a> +<li><a href="FAQ-eurohtml">Typesetting the Euro sign</a> +<li><a href="FAQ-tradesymshtml">How to get copyright, trademark, etc.</a> </ul><h3>Macro programming</h3><ul> </ul><h4>“Generic” macros and techniques</h4><ul> -<li><a href="FAQ-findwidth.html">Finding the width of a letter, word, or phrase</a> -<li><a href="FAQ-patch.html">Patching existing commands</a> -<li><a href="FAQ-compjobnam.html">Comparing the “job name”</a> -<li><a href="FAQ-isitanum.html">Is the argument a number?</a> -<li><a href="FAQ-hash.html">Defining macros within macros</a> -<li><a href="FAQ-spinmacro.html">Spaces in macros</a> -<li><a href="FAQ-moren9.html">How to break the 9-argument limit</a> -<li><a href="FAQ-activechars.html">Defining characters as macros</a> -<li><a href="FAQ-actinarg.html">Active characters in command arguments</a> -<li><a href="FAQ-csname.html">Defining a macro from an argument</a> -<li><a href="FAQ-cvtlatex.html">Transcribing LaTeX command definitions</a> -<li><a href="FAQ-empty.html">Detecting that something is empty</a> -<li><a href="FAQ-ifpdf.html">Am I using PDFTeX?</a> -<li><a href="FAQ-subverttoks.html">Subverting a token register</a> -<li><a href="FAQ-isdef.html">Is this command defined?</a> +<li><a href="FAQ-findwidthhtml">Finding the width of a letter, word, or phrase</a> +<li><a href="FAQ-patchhtml">Patching existing commands</a> +<li><a href="FAQ-compjobnamhtml">Comparing the “job name”</a> +<li><a href="FAQ-isitanumhtml">Is the argument a number?</a> +<li><a href="FAQ-hashhtml">Defining macros within macros</a> +<li><a href="FAQ-spinmacrohtml">Spaces in macros</a> +<li><a href="FAQ-moren9html">How to break the 9-argument limit</a> +<li><a href="FAQ-activecharshtml">Defining characters as macros</a> +<li><a href="FAQ-actinarghtml">Active characters in command arguments</a> +<li><a href="FAQ-csnamehtml">Defining a macro from an argument</a> +<li><a href="FAQ-cvtlatexhtml">Transcribing LaTeX command definitions</a> +<li><a href="FAQ-emptyhtml">Detecting that something is empty</a> +<li><a href="FAQ-ifpdfhtml">Am I using PDFTeX?</a> +<li><a href="FAQ-subverttokshtml">Subverting a token register</a> +<li><a href="FAQ-isdefhtml">Is this command defined?</a> </ul><h4>LaTeX macro tools and techniques</h4><ul> -<li><a href="FAQ-plninltx.html">Using Plain or primitive commands in LaTeX</a> -<li><a href="FAQ-atsigns.html"><code>\</code><code>@</code> and <code>@</code> in macro names</a> -<li><a href="FAQ-protect.html">What’s the reason for ‘protection’?</a> -<li><a href="FAQ-edef.html"><code>\</code><code>edef</code> does not work with <code>\</code><code>protect</code></a> -<li><a href="FAQ-ltxcmds.html">The definitions of LaTeX commands</a> -<li><a href="FAQ-oarglikesect.html">Optional arguments like <code>\</code><code>section</code></a> -<li><a href="FAQ-twooptarg.html">More than one optional argument</a> -<li><a href="FAQ-cmdstar.html">Commands defined with * options</a> -<li><a href="FAQ-ltxabbrv.html">LaTeX internal “abbreviations”, etc.</a> -<li><a href="FAQ-ltxhash.html">Defining LaTeX commands within other commands</a> +<li><a href="FAQ-plninltxstarhtml">Using Plain or primitive commands in LaTeX</a> +<li><a href="FAQ-atsignshtml"><code>\</code><code>@</code> and <code>@</code> in macro names</a> +<li><a href="FAQ-protecthtml">What’s the reason for ‘protection’?</a> +<li><a href="FAQ-edefhtml"><code>\</code><code>edef</code> does not work with <code>\</code><code>protect</code></a> +<li><a href="FAQ-ltxcmdshtml">The definitions of LaTeX commands</a> +<li><a href="FAQ-oarglikesecthtml">Optional arguments like <code>\</code><code>section</code></a> +<li><a href="FAQ-twooptarghtml">More than one optional argument</a> +<li><a href="FAQ-cmdstarhtml">Commands defined with * options</a> +<li><a href="FAQ-ltxabbrvhtml">LaTeX internal “abbreviations”, etc.</a> +<li><a href="FAQ-ltxhashhtml">Defining LaTeX commands within other commands</a> </ul><h4>LaTeX macro programming</h4><ul> -<li><a href="FAQ-fixnam.html">How to change LaTeX’s “fixed names”</a> -<li><a href="FAQ-latexwords.html">Changing the words <i>babel</i> uses</a> -<li><a href="FAQ-running-nos.html">Running equation, figure and table numbering</a> -<li><a href="FAQ-labelctr.html">Making labels from a counter</a> -<li><a href="FAQ-oddpage.html">Finding if you’re on an odd or an even page</a> -<li><a href="FAQ-labelformat.html">How to change the format of labels</a> -<li><a href="FAQ-seccntfmt.html">Adjusting the presentation of section numbers</a> -<li><a href="FAQ-spaftend.html">There’s a space added after my environment</a> -<li><a href="FAQ-labundef.html">Finding if a label is undefined</a> -<li><a href="FAQ-addtoreset.html">Master and slave counters</a> +<li><a href="FAQ-fixnamhtml">How to change LaTeX’s “fixed names”</a> +<li><a href="FAQ-latexwordshtml">Changing the words <i>babel</i> uses</a> +<li><a href="FAQ-running-noshtml">Running equation, figure and table numbering</a> +<li><a href="FAQ-labelctrhtml">Making labels from a counter</a> +<li><a href="FAQ-oddpagehtml">Finding if you’re on an odd or an even page</a> +<li><a href="FAQ-labelformathtml">How to change the format of labels</a> +<li><a href="FAQ-seccntfmthtml">Adjusting the presentation of section numbers</a> +<li><a href="FAQ-spaftendhtml">There’s a space added after my environment</a> +<li><a href="FAQ-labundefhtml">Finding if a label is undefined</a> +<li><a href="FAQ-addtoresethtml">Master and slave counters</a> +<li><a href="FAQ-fontsizehtml">Fonts at arbitrary sizes</a> +<li><a href="FAQ-latexqualhtml">The quality of your LaTeX</a> </ul><h3>Things are Going Wrong...</h3><ul> </ul><h4>Getting things to fit</h4><ul> -<li><a href="FAQ-enlarge.html">Enlarging TeX</a> -<li><a href="FAQ-usepictex.html">Why can’t I load PiCTeX?</a> +<li><a href="FAQ-enlargehtml">Enlarging TeX</a> +<li><a href="FAQ-usepictexhtml">Why can’t I load PicTeX?</a> </ul><h4>Making things stay where you want them</h4><ul> -<li><a href="FAQ-floats.html">Moving tables and figures in LaTeX</a> -<li><a href="FAQ-underline.html">Underlined text won’t break</a> -<li><a href="FAQ-widows.html">Controlling widows and orphans</a> +<li><a href="FAQ-floatshtml">Moving tables and figures in LaTeX</a> +<li><a href="FAQ-underlinehtml">Underlined text won’t break</a> +<li><a href="FAQ-widowshtml">Controlling widows and orphans</a> </ul><h4>Things have “gone away”</h4><ul> -<li><a href="FAQ-oldfontnames.html">Old LaTeX font references such as <code>\</code><code>tenrm</code></a> -<li><a href="FAQ-missssymb.html">Missing symbol commands</a> -<li><a href="FAQ-msxy.html">Where are the <code>msx</code> and <code>msy</code> fonts?</a> -<li><a href="FAQ-amfonts.html">Where are the <code>am</code> fonts?</a> +<li><a href="FAQ-oldfontnameshtml">Old LaTeX font references such as <code>\</code><code>tenrm</code></a> +<li><a href="FAQ-missssymbhtml">Missing symbol commands</a> +<li><a href="FAQ-msxyhtml">Where are the <code>msx</code> and <code>msy</code> fonts?</a> +<li><a href="FAQ-amfontshtml">Where are the <code>am</code> fonts?</a> </ul><h3>Why does it <em>do</em> that?</h3><ul> </ul><h4>Common errors</h4><ul> -<li><a href="FAQ-crossref.html">LaTeX gets cross-references wrong</a> -<li><a href="FAQ-newlineargs.html">Start of line goes awry</a> -<li><a href="FAQ-verbwithin.html">Why doesn’t verbatim work within ...?</a> -<li><a href="FAQ-noline.html">No line here to end</a> -<li><a href="FAQ-2colfltorder.html">Two-column float numbers out of order</a> -<li><a href="FAQ-tabacc.html">Accents misbehave in <code>tabbing</code></a> -<li><a href="FAQ-alreadydef.html">Package reports “command already defined”</a> -<li><a href="FAQ-zerochap.html">Why are my sections numbered 0.1 ...?</a> -<li><a href="FAQ-breaklinks.html">Link text doesn’t break at end line</a> -<li><a href="FAQ-wrongpn.html">Page number is wrong at start of page</a> -<li><a href="FAQ-matchbrak.html">My brackets don’t match</a> +<li><a href="FAQ-crossrefhtml">LaTeX gets cross-references wrong</a> +<li><a href="FAQ-newlineargshtml">Start of line goes awry</a> +<li><a href="FAQ-verbwithinhtml">Why doesn’t verbatim work within ...?</a> +<li><a href="FAQ-nolinehtml">No line here to end</a> +<li><a href="FAQ-2colfltorderhtml">Two-column float numbers out of order</a> +<li><a href="FAQ-tabacchtml">Accents misbehave in <code>tabbing</code></a> +<li><a href="FAQ-alreadydefhtml">Package reports “command already defined”</a> +<li><a href="FAQ-zerochaphtml">Why are my sections numbered 0.1 ...?</a> +<li><a href="FAQ-breaklinkshtml">Link text doesn’t break at end line</a> +<li><a href="FAQ-wrongpnhtml">Page number is wrong at start of page</a> +<li><a href="FAQ-matchbrakhtml">My brackets don’t match</a> </ul><h4>Common misunderstandings</h4><ul> -<li><a href="FAQ-include.html">What’s going on in my <code>\</code><code>include</code> commands?</a> -<li><a href="FAQ-paraparam.html">Why does it ignore paragraph parameters?</a> -<li><a href="FAQ-casechange.html">Case-changing oddities</a> -<li><a href="FAQ-splitfoot.html">Why does LaTeX split footnotes across pages?</a> -<li><a href="FAQ-marginparside.html">Getting <code>\</code><code>marginpar</code> on the right side</a> -<li><a href="FAQ-misschar.html">Where have my characters gone?</a> -<li><a href="FAQ-rerun.html">“Rerun” messages won’t go away</a> -<li><a href="FAQ-xspace.html">Commands gobble following space</a> -<li><a href="FAQ-overfull.html">(La)TeX makes overfull lines</a> -<li><a href="FAQ-exscale.html">Maths symbols don’t scale up</a> -<li><a href="FAQ-linespread.html">Why doesn’t <code>\</code><code>linespread</code> work?</a> -<li><a href="FAQ-baselinepar.html">Only one <code>\</code><code>baselineskip</code> per paragraph</a> -<li><a href="FAQ-tocloftwrong.html">Numbers too large in table of contents, etc.</a> -<li><a href="FAQ-gutter.html">Why is the inside margin so narrow?</a> +<li><a href="FAQ-includehtml">What’s going on in my <code>\</code><code>include</code> commands?</a> +<li><a href="FAQ-paraparamhtml">Why does it ignore paragraph parameters?</a> +<li><a href="FAQ-casechangehtml">Case-changing oddities</a> +<li><a href="FAQ-splitfoothtml">Why does LaTeX split footnotes across pages?</a> +<li><a href="FAQ-marginparsidehtml">Getting <code>\</code><code>marginpar</code> on the right side</a> +<li><a href="FAQ-misscharhtml">Where have my characters gone?</a> +<li><a href="FAQ-rerunhtml">“Rerun” messages won’t go away</a> +<li><a href="FAQ-xspacehtml">Commands gobble following space</a> +<li><a href="FAQ-overfullhtml">(La)TeX makes overfull lines</a> +<li><a href="FAQ-exscalehtml">Maths symbols don’t scale up</a> +<li><a href="FAQ-linespreadhtml">Why doesn’t <code>\</code><code>linespread</code> work?</a> +<li><a href="FAQ-baselineparhtml">Only one <code>\</code><code>baselineskip</code> per paragraph</a> +<li><a href="FAQ-tocloftwronghtml">Numbers too large in table of contents, etc.</a> +<li><a href="FAQ-gutterhtml">Why is the inside margin so narrow?</a> </ul><h4>Why shouldn’t I?</h4><ul> -<li><a href="FAQ-t1enc.html">Why use <i>fontenc</i> rather than <i>t1enc</i>?</a> -<li><a href="FAQ-why-inp-font.html">Why bother with <i>inputenc</i> and <i>fontenc</i>?</a> -<li><a href="FAQ-eqnarray.html">Why not use <code>eqnarray</code>?</a> -<li><a href="FAQ-dolldoll.html">Why use <code>\</code><code>[</code> ...<code>\</code><code>]</code> in place of <code>$$</code> ...<code>$$</code>?</a> -<li><a href="FAQ-2letterfontcmd.html">What’s wrong with <code>\</code><code>bf</code>, <code>\</code><code>it</code>, etc.?</a> -<li><a href="FAQ-newfont.html">What’s wrong with <code>\</code><code>newfont</code>?</a> +<li><a href="FAQ-t1enchtml">Why use <i>fontenc</i> rather than <i>t1enc</i>?</a> +<li><a href="FAQ-why-inp-fonthtml">Why bother with <i>inputenc</i> and <i>fontenc</i>?</a> +<li><a href="FAQ-eqnarrayhtml">Why not use <code>eqnarray</code>?</a> +<li><a href="FAQ-dolldollhtml">Why use <code>\</code><code>[</code> ...<code>\</code><code>]</code> in place of <code>$$</code> ...<code>$$</code>?</a> +<li><a href="FAQ-2letterfontcmdhtml">What’s wrong with <code>\</code><code>bf</code>, <code>\</code><code>it</code>, etc.?</a> +<li><a href="FAQ-newfontstarhtml">What’s wrong with <code>\</code><code>newfont</code>?</a> </ul><h3>The joy of TeX errors</h3><ul> -<li><a href="FAQ-erroradvice.html">How to approach errors</a> -<li><a href="FAQ-errstruct.html">The structure of TeX error messages</a> -<li><a href="FAQ-extrabrace.html">An extra ‘<code>}</code>’??</a> -<li><a href="FAQ-semanticnest.html">Capacity exceeded [semantic nest ...]</a> -<li><a href="FAQ-noroom.html">No room for a new ‘<em>thing</em>’</a> -<li><a href="FAQ-epsf.html"><code>epsf</code> gives up after a bit</a> -<li><a href="FAQ-badhyph.html">Improper <code>\</code><code>hyphenation</code> will be flushed</a> -<li><a href="FAQ-tmupfl.html">“Too many unprocessed floats”</a> -<li><a href="FAQ-atvert.html"><code>\</code><code>spacefactor</code> complaints</a> -<li><a href="FAQ-endingroup.html"><code>\</code><code>end</code> occurred inside a group</a> -<li><a href="FAQ-nonum.html">“Missing number, treated as zero”</a> -<li><a href="FAQ-typend.html">“Please type a command or say <code>\</code><code>end</code>”</a> -<li><a href="FAQ-unkgrfextn.html">“Unknown graphics extension”</a> -<li><a href="FAQ-nodollar.html">“Missing <code>$</code> inserted”</a> -<li><a href="FAQ-fontunavail.html">Warning: “Font shape ... not available”</a> -<li><a href="FAQ-buffovl.html">Unable to read an entire line</a> -<li><a href="FAQ-formatstymy.html">“Fatal format file error; I’m stymied”</a> -<li><a href="FAQ-nonpdfsp.html">Non-PDF special ignored!</a> -<li><a href="FAQ-8000.html">Mismatched mode ljfour and resolution 8000</a> -<li><a href="FAQ-toodeep.html">“Too deeply nested”</a> -<li><a href="FAQ-inputlev.html">Capacity exceeded — input levels</a> -<li><a href="FAQ-hyperdupdest.html">PDFTeX destination ... ignored</a> -<li><a href="FAQ-altabcr.html">Alignment tab changed to <code>\</code><code>cr</code></a> -<li><a href="FAQ-divzero.html">Graphics division by zero</a> -<li><a href="FAQ-missbegdoc.html">Missing <code>\</code><code>begin</code><code>{document}</code></a> -<li><a href="FAQ-normalszmiss.html"><code>\</code><code>normalsize</code> not defined</a> -<li><a href="FAQ-manymathalph.html">Too many math alphabets</a> -<li><a href="FAQ-ouparmd.html">Not in outer par mode</a> -<li><a href="FAQ-errmissitem.html">Perhaps a missing <code>\</code><code>item</code>?</a> -<li><a href="FAQ-errparnum.html">Illegal parameter number in definition</a> -<li><a href="FAQ-fllost.html">Float(s) lost</a> -<li><a href="FAQ-optionclash.html">Option clash for package</a> +<li><a href="FAQ-erroradvicehtml">How to approach errors</a> +<li><a href="FAQ-errstructhtml">The structure of TeX error messages</a> +<li><a href="FAQ-extrabracehtml">An extra ‘<code>}</code>’??</a> +<li><a href="FAQ-semanticnesthtml">Capacity exceeded [semantic nest ...]</a> +<li><a href="FAQ-noroomhtml">No room for a new ‘<em>thing</em>’</a> +<li><a href="FAQ-epsfhtml"><code>epsf</code> gives up after a bit</a> +<li><a href="FAQ-badhyphhtml">Improper <code>\</code><code>hyphenation</code> will be flushed</a> +<li><a href="FAQ-tmupflhtml">“Too many unprocessed floats”</a> +<li><a href="FAQ-atverthtml"><code>\</code><code>spacefactor</code> complaints</a> +<li><a href="FAQ-endingrouphtml"><code>\</code><code>end</code> occurred inside a group</a> +<li><a href="FAQ-nonumhtml">“Missing number, treated as zero”</a> +<li><a href="FAQ-typendhtml">“Please type a command or say <code>\</code><code>end</code>”</a> +<li><a href="FAQ-unkgrfextnhtml">“Unknown graphics extension”</a> +<li><a href="FAQ-nodollarhtml">“Missing <code>$</code> inserted”</a> +<li><a href="FAQ-fontunavailhtml">Warning: “Font shape ... not available”</a> +<li><a href="FAQ-buffovlhtml">Unable to read an entire line</a> +<li><a href="FAQ-formatstymyhtml">“Fatal format file error; I’m stymied”</a> +<li><a href="FAQ-nonpdfsphtml">Non-PDF special ignored!</a> +<li><a href="FAQ-8000html">Mismatched mode ljfour and resolution 8000</a> +<li><a href="FAQ-toodeephtml">“Too deeply nested”</a> +<li><a href="FAQ-inputlevhtml">Capacity exceeded — input levels</a> +<li><a href="FAQ-hyperdupdesthtml">PDFTeX destination ... ignored</a> +<li><a href="FAQ-altabcrhtml">Alignment tab changed to <code>\</code><code>cr</code></a> +<li><a href="FAQ-divzerohtml">Graphics division by zero</a> +<li><a href="FAQ-missbegdochtml">Missing <code>\</code><code>begin</code><code>{document}</code></a> +<li><a href="FAQ-normalszmisshtml"><code>\</code><code>normalsize</code> not defined</a> +<li><a href="FAQ-manymathalphhtml">Too many math alphabets</a> +<li><a href="FAQ-ouparmdhtml">Not in outer par mode</a> +<li><a href="FAQ-errmissitemhtml">Perhaps a missing <code>\</code><code>item</code>?</a> +<li><a href="FAQ-errparnumhtml">Illegal parameter number in definition</a> +<li><a href="FAQ-fllosthtml">Float(s) lost</a> +<li><a href="FAQ-optionclashhtml">Option clash for package</a> +<li><a href="FAQ-checksumhtml">Checksum mismatch in font</a> +<li><a href="FAQ-entercompmodehtml">Entering compatibility mode</a> </ul><h3>Current TeX-related projects</h3><ul> -<li><a href="FAQ-LaTeX3.html">The LaTeX3 project</a> -<li><a href="FAQ-mathml.html">Future WWW technologies and (La)TeX</a> -<li><a href="FAQ-textrace.html">Making outline fonts from Metafont</a> -<li><a href="FAQ-WYGexpts.html">The TeX document preparation environment</a> -<li><a href="FAQ-ant.html">The ANT typesetting system</a> -<li><a href="FAQ-extex.html">The ExTeX project</a> -<li><a href="FAQ-omegaleph.html">Omega and Aleph</a> -<li><a href="FAQ-luatex.html">PDFTeX becomes LUATeX</a> -<li><a href="FAQ-xetex.html">The XeTeX project</a> +<li><a href="FAQ-LaTeX3html">The LaTeX project</a> +<li><a href="FAQ-mathmlhtml">Future WWW technologies and (La)TeX</a> +<li><a href="FAQ-textracehtml">Making outline fonts from Metafont</a> +<li><a href="FAQ-WYGexptshtml">The TeX document preparation environment</a> +<li><a href="FAQ-anthtml">The ANT typesetting system</a> +<li><a href="FAQ-extexhtml">The ExTeX project</a> +<li><a href="FAQ-omegalephhtml">Omega and Aleph</a> +<li><a href="FAQ-luatexhtml">PDFTeX becomes LuaTeX</a> +<li><a href="FAQ-xetexhtml">The XeTeX project</a> +<li><a href="FAQ-biblatexhtml">Replacing the BibTeX–LaTeX mechanism</a> </ul><h3>You’re still stuck?</h3><ul> -<li><a href="FAQ-noans.html">You don’t understand the answer</a> -<li><a href="FAQ-newans.html">Submitting new material for the FAQ</a> -<li><a href="FAQ-latexbug.html">Reporting a LaTeX bug</a> -<li><a href="FAQ-bug.html">What to do if you find a bug</a> +<li><a href="FAQ-noanshtml">You don’t understand the answer</a> +<li><a href="FAQ-newanshtml">Submitting new material for the FAQ</a> +<li><a href="FAQ-latexbughtml">Reporting a LaTeX bug</a> +<li><a href="FAQ-bughtml">What to do if you find a bug</a> </ul> <hr><address> @@ -575,5 +597,5 @@ Reinhard Zierke. "<a href="FAQ-noans.html">Improving the FAQ</a>" or "<a href="FAQ-newans.html">Extending the FAQ</a>". <p> - This is FAQ version 3.16c-1, last modified on 2006-12-18. + This is FAQ version 3.17, last modified on 2007-11-05. </address> diff --git a/Master/texmf-doc/doc/english/FAQ-en/markup-syntax b/Master/texmf-doc/doc/english/FAQ-en/markup-syntax index 4c2c2e7ff65..087f32fd945 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/markup-syntax +++ b/Master/texmf-doc/doc/english/FAQ-en/markup-syntax @@ -21,11 +21,12 @@ Rules for presentation of text - even if you prefer \TeX\ to ensure the name's delimited - even if the name's immediately followed by punctuation -3. Don't change the shortvrb character from `|'. You will perhaps - note that various of the path/address-type commands are defined - with | as argument delimiter; if the definition of shortvrb is - changed, all of those commands, and all of the \CTANref commands - will fall in a neat little heap on the floor. +3. Don't change the shortvrb character from `|'; it interacts with + other definitions. + +4. Avoid shortvrb syntax, anyway ... most common uses are now covered + by specific macros; if a need arises, more such macros can be + developed, rather than using shortvrb. Rules for managing the text --------------------------- @@ -48,8 +49,6 @@ filectan.tex Declarations of the locations of individual files on dirctan.tex Declarations of the directories on CTAN archives faq.sty The main package -texnames.sty An update of the file most recently edited by Nelson - Beebe This pre-production version of the text is printed (by default) in Adobe Times Roman, etc. An alternative font may by used by setting @@ -77,11 +76,15 @@ The faq is written in LaTeX. Commands to use are: gets typeset in respect of a \CTANref (and what becomes the anchor of an html link to retrieve the referenced thing). +\CTANdirectory*{tag}{directory-path} + + As \CTANdirectory, but appears in HTML as "browse directory" only + \CTANref{tag} (and the ctanrefs environment) make reference to a <tag> defined by a \CTANfile or \CTANdirectory - command; should usually appear in a ctanrefs environment at the end - of a question. Refer to the files with markup such as \Package, + command; will usually appear in a ctanrefs environment at the end of + an answer. Refer to the files with markup such as \Package, \Class or \ProgName in the body of the question, and then say: \begin{ctanrefs} \item[blah.sty]\CTANref{blah} @@ -89,27 +92,32 @@ The faq is written in LaTeX. Commands to use are: \Question[label]{question-title} - Set the title of a question, and (optionally) define a label for it - (in fact, an unusual sort of subsection command). The [label] is - (now) mandatory, and must be prefixed by "Q-" (as in + Set the title of a question, and define a label for it (in fact, an + unusual sort of subsection command). The [label] is (now) + mandatory, and must be prefixed by "Q-" (as in \Question[Q-newans]{Submitting new material for the FAQ}). \Qref[intro-text]{anchor-text}{label} Refer to a question. The <intro-text> is set before the reference, - and is "see question" by default. The <anchor-text> is used in the - html variant of the document as the anchor for jumping to the - labelled question (it's not used in the LaTeX processing). The - <label> is defined somewhere in the document as a \Question - command's optional argument + and is "see question" by default. The <anchor-text> is used in + hyper-enabled output, as the anchor for jumping to the labelled + question. The <label> is defined somewhere in the document as a + \Question command's (nominally) optional argument. + +\Qref*{anchor-text}{label} + + Refer to a question. In hyper-enabled output, results are the same + as for \Qref; in DVI output, produces + anchor-text (see question <label>) + special care being taken with surrounding quotes. \TUGboat{} <vol>(<number>) - TUGboat reference (we have surprisingly many, quite apart from Seb's - adverts for 16(3) ;-). Really does have that syntax \TUGboat{} - 16(3), though as far as the exiciting translator is concerned, the - command ends at \TUGboat{} so it doesn't matter if it gets split as - I just did... + TUGboat reference (we have surprisingly many). Really does have + that syntax \TUGboat{} 16(3), though as far as the HTML translator + is concerned, the command ends at \TUGboat{} so it doesn't matter if + it gets split across lines. Environment booklabel @@ -127,6 +135,11 @@ Environment htmlversion Text to appear in HTML but not in the typeset versions of the FAQ. (The body of the environment will be processed before appearing in the HTML output, just the same as text for joint use.) + Similar are: +Environment dviversion (DVI output only) +Environment pdfversion (PDF output only) +Environment narrowversion (DVI output only -- narrow since 2-col output) +Environment wideversion (HTML or PDF output only) \nothtml{text} @@ -148,13 +161,15 @@ Environment htmlversion \cmdinvoke{cmd name}<arguments> - Typesets a complete command invocation. The LaTeX macro will take - arbitrary sequences of optional and mandatory arguments, but the - HTML processor will (at present) only take + Typesets a complete command invocation, and all its arguments. + The LaTeX macro will take arbitrary sequences of optional and + mandatory arguments, but while the HTML processor will deal with a + wide range of variants, its stunning simplemindedness means it's + always good to check such output. + +\cmdinvoke*{cmd name}<arguments> - \cmdinvoke{cmd}{mandatory} - \cmdinvoke{cmd}[optional]{mandatory} - \cmdinvoke{cmd}{mandatory1}{mandatory2} + As \cmdinvoke, but arguments are typeset with \emph \checked{intials}{date} @@ -165,13 +180,13 @@ Environment htmlversion For labelling questions. Doesn't currently have any effect at all. -\Email|<name>@<address>| -\FTP|<site-address>| -\File|<file-path>| -\path|<file-path>| -\Newsgroup|<usenet-group-name| -\URL{<protocol>://site/path} -\mailto|email@ddress| +\Email{<name>@<address>} +\FTP{<site-address>} +\File{file-path>} +\path{file-path>} +\Newsgroup{usenet-group-name} +\URL{protocol>://site/path} +\mailto{mail@ddress} All these things typeset their argument in typewriter, but allowing line-splitting at appropriate characters (using url.sty). The last @@ -179,11 +194,9 @@ Environment htmlversion versions of the FAQ; \Email is for formatting a name (e.g., a finger identifier) that the reader is _not_ supposed to mail. -\Package|package name| (no .sty) -\Class|class name| (no .cls) -\ProgName|executable command name| -or... -\Package{...}, \Class{....}, \ProgName{...} +\Package{ackage name}(no .sty) +\Class{lass name} (no .cls) +\ProgName{executable command name} Set the item in an appropriate fashion. _Please_ use these commands wherever appropriate. @@ -207,6 +220,7 @@ Typesetting things, arguments in braces: Typesetting environments: quote, description, itemize, enumerate, verbatim + Other odds and ends: $\pi$, $...$, \$, \#, \ , \&, ~ [just produces a space] diff --git a/Master/texmf-doc/doc/english/FAQ-en/newfaq.aux b/Master/texmf-doc/doc/english/FAQ-en/newfaq.aux deleted file mode 100644 index 8a1514d5fce..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/newfaq.aux +++ /dev/null @@ -1,875 +0,0 @@ -\relax -\@writefile{toc}{\contentsline {section}{\numberline {A}Introduction}{5}} -\@writefile{toc}{\contentsline {section}{\numberline {B}The Background}{5}} -\@writefile{toc}{\contentsline {question}{\numberline {1}What is \TeX {}?}{5}} -\newlabel{Q-whatTeX}{{1}{5}} -\@writefile{toc}{\contentsline {question}{\numberline {2}How should I pronounce ``\TeX {}''?}{6}} -\newlabel{Q-TeXpronounce}{{2}{6}} -\@writefile{toc}{\contentsline {question}{\numberline {3}What is \MF {}?}{6}} -\newlabel{Q-MF}{{3}{6}} -\@writefile{toc}{\contentsline {question}{\numberline {4}What is \MP {}?}{6}} -\newlabel{Q-MP}{{4}{6}} -\@writefile{toc}{\contentsline {question}{\numberline {5}How can I be sure it's really \TeX {}?}{6}} -\newlabel{Q-triptrap}{{5}{6}} -\@writefile{toc}{\contentsline {question}{\numberline {6}Are \TeX {} and friends Y2K compliant?}{6}} -\newlabel{Q-y2k}{{6}{6}} -\@writefile{toc}{\contentsline {question}{\numberline {7}What is e-\TeX {}?}{7}} -\newlabel{Q-etex}{{7}{7}} -\@writefile{toc}{\contentsline {question}{\numberline {8}What is PDF\TeX {}?}{7}} -\newlabel{Q-whatpdftex}{{8}{7}} -\@writefile{toc}{\contentsline {question}{\numberline {9}What is La\TeX {}?}{7}} -\newlabel{Q-latex}{{9}{7}} -\@writefile{toc}{\contentsline {question}{\numberline {10}What is \LaTeXe {}?}{7}} -\newlabel{Q-latex2e}{{10}{7}} -\@writefile{toc}{\contentsline {question}{\numberline {11}How should I pronounce ``La\TeX {}(2e{})''?}{7}} -\newlabel{Q-latexpronounce}{{11}{7}} -\@writefile{toc}{\contentsline {question}{\numberline {12}Should I use Plain \TeX {} or La\TeX {}?}{7}} -\newlabel{Q-plainvltx}{{12}{7}} -\@writefile{toc}{\contentsline {question}{\numberline {13}How does La\TeX {} relate to Plain \TeX {}?}{8}} -\newlabel{Q-LaTeXandPlain}{{13}{8}} -\@writefile{toc}{\contentsline {question}{\numberline {14}What is Con\TeX {}t{}?}{8}} -\newlabel{Q-context}{{14}{8}} -\@writefile{toc}{\contentsline {question}{\numberline {15}What are the \acro {AMS} packages (AMS\TeX {}, \emph {etc}.)?}{8}} -\newlabel{Q-AMSpkg}{{15}{8}} -\@writefile{toc}{\contentsline {question}{\numberline {16}What is Eplain{}?}{8}} -\newlabel{Q-eplain}{{16}{8}} -\@writefile{toc}{\contentsline {question}{\numberline {17}What is Lollipop?}{9}} -\newlabel{Q-lollipop}{{17}{9}} -\@writefile{toc}{\contentsline {question}{\numberline {18}What is Texinfo?}{9}} -\newlabel{Q-texinfo}{{18}{9}} -\@writefile{toc}{\contentsline {question}{\numberline {19}If \TeX {} is so good, how come it's free?}{9}} -\newlabel{Q-whyfree}{{19}{9}} -\@writefile{toc}{\contentsline {question}{\numberline {20}What is the future of \TeX {}?}{9}} -\newlabel{Q-TeXfuture}{{20}{9}} -\@writefile{toc}{\contentsline {question}{\numberline {21}Reading (La)\TeX {} files}{9}} -\newlabel{Q-readtex}{{21}{9}} -\@writefile{toc}{\contentsline {question}{\numberline {22}Why is \TeX {} not a \WYSIWYG {} system?}{10}} -\newlabel{Q-notWYSIWYG}{{22}{10}} -\@writefile{toc}{\contentsline {question}{\numberline {23}\TeX {} User Groups}{10}} -\newlabel{Q-TUG*}{{23}{10}} -\@writefile{toc}{\contentsline {section}{\numberline {C}Documentation and Help}{10}} -\@writefile{toc}{\contentsline {question}{\numberline {24}Books on \TeX {} and its relations}{10}} -\newlabel{Q-books}{{24}{10}} -\@writefile{toc}{\contentsline {question}{\numberline {25}Books on Type}{11}} -\newlabel{Q-typebooks}{{25}{11}} -\@writefile{toc}{\contentsline {question}{\numberline {26}Where to find \acro {FAQ}s}{12}} -\newlabel{Q-whereFAQ}{{26}{12}} -\@writefile{toc}{\contentsline {question}{\numberline {27}How to get help}{12}} -\newlabel{Q-gethelp}{{27}{12}} -\@writefile{toc}{\contentsline {question}{\numberline {28}Specialist mailing lists}{13}} -\newlabel{Q-maillists*}{{28}{13}} -\@writefile{toc}{\contentsline {question}{\numberline {29}How to ask a question}{13}} -\newlabel{Q-askquestion}{{29}{13}} -\@writefile{toc}{\contentsline {question}{\numberline {30}How to make a ``minimum example''}{13}} -\newlabel{Q-minxampl}{{30}{13}} -\@writefile{toc}{\contentsline {question}{\numberline {31}(La)\TeX {} Tutorials, etc.}{14}} -\newlabel{Q-tutorials*}{{31}{14}} -\@writefile{toc}{\contentsline {question}{\numberline {32}Online introductions: Plain \TeX {}}{14}} -\newlabel{Q-man-tex}{{32}{14}} -\@writefile{toc}{\contentsline {question}{\numberline {33}Online introductions: La\TeX {}}{14}} -\newlabel{Q-man-latex}{{33}{14}} -\@writefile{toc}{\contentsline {question}{\numberline {34}Specialised (La)\TeX {} tutorials}{14}} -\newlabel{Q-tutbitslatex}{{34}{14}} -\@writefile{toc}{\contentsline {question}{\numberline {35}Reference documents}{15}} -\newlabel{Q-ref-doc}{{35}{15}} -\@writefile{toc}{\contentsline {question}{\numberline {36}WIKI pages for \TeX {} and friends}{15}} -\newlabel{Q-doc-wiki}{{36}{15}} -\@writefile{toc}{\contentsline {question}{\numberline {37}Typography tutorials}{15}} -\newlabel{Q-typo-style}{{37}{15}} -\@writefile{toc}{\contentsline {question}{\numberline {38}Directories of (La)\TeX {} information}{16}} -\newlabel{Q-doc-dirs}{{38}{16}} -\@writefile{toc}{\contentsline {question}{\numberline {39}Freely available (La)\TeX {} books}{16}} -\newlabel{Q-ol-books}{{39}{16}} -\@writefile{toc}{\contentsline {question}{\numberline {40}Documentation of packages}{16}} -\newlabel{Q-pkgdoc}{{40}{16}} -\@writefile{toc}{\contentsline {question}{\numberline {41}Learning to write La\TeX {} classes and packages}{16}} -\newlabel{Q-writecls}{{41}{16}} -\@writefile{toc}{\contentsline {question}{\numberline {42}\MF {} and \MP {} Tutorials}{17}} -\newlabel{Q-mfptutorials}{{42}{17}} -\@writefile{toc}{\contentsline {question}{\numberline {43}Bib\TeX {} Documentation}{17}} -\newlabel{Q-BibTeXing}{{43}{17}} -\@writefile{toc}{\contentsline {question}{\numberline {44}Where can I find the symbol for\,\dots {}}{17}} -\newlabel{Q-symbols}{{44}{17}} -\@writefile{toc}{\contentsline {question}{\numberline {45}The PiC\TeX {} manual}{18}} -\newlabel{Q-docpictex}{{45}{18}} -\@writefile{toc}{\contentsline {section}{\numberline {D}Bits and pieces of (La)\TeX {}}{18}} -\@writefile{toc}{\contentsline {question}{\numberline {46}What is a \acro {DVI} file?}{18}} -\newlabel{Q-dvi}{{46}{18}} -\@writefile{toc}{\contentsline {question}{\numberline {47}What is a driver?}{18}} -\newlabel{Q-driver}{{47}{18}} -\@writefile{toc}{\contentsline {question}{\numberline {48}What are \acro {PK} files?}{18}} -\newlabel{Q-pk}{{48}{18}} -\@writefile{toc}{\contentsline {question}{\numberline {49}What are \acro {TFM} files?}{18}} -\newlabel{Q-tfm}{{49}{18}} -\@writefile{toc}{\contentsline {question}{\numberline {50}Virtual fonts}{18}} -\newlabel{Q-virtualfonts}{{50}{18}} -\@writefile{toc}{\contentsline {question}{\numberline {51}\csx {special} commands}{19}} -\newlabel{Q-specials}{{51}{19}} -\@writefile{toc}{\contentsline {question}{\numberline {52}How does hyphenation work in \TeX {}?}{19}} -\newlabel{Q-hyphen}{{52}{19}} -\@writefile{toc}{\contentsline {question}{\numberline {53}What are La\TeX {} classes and packages?}{19}} -\newlabel{Q-clsvpkg}{{53}{19}} -\@writefile{toc}{\contentsline {question}{\numberline {54}Documented La\TeX {} sources (\texttt {.dtx} files)}{19}} -\newlabel{Q-dtx}{{54}{19}} -\@writefile{toc}{\contentsline {question}{\numberline {55}What are encodings?}{20}} -\newlabel{Q-whatenc}{{55}{20}} -\@writefile{toc}{\contentsline {question}{\numberline {56}What are the \acro {EC} fonts?}{20}} -\newlabel{Q-ECfonts}{{56}{20}} -\@writefile{toc}{\contentsline {question}{\numberline {57}What is the \acro {TDS}?}{21}} -\newlabel{Q-tds}{{57}{21}} -\@writefile{toc}{\contentsline {question}{\numberline {58}What is ``Encapsulated PostScript{}'' (``\acro {EPS}'')}{21}} -\newlabel{Q-eps}{{58}{21}} -\@writefile{toc}{\contentsline {question}{\numberline {59}Adobe font formats}{21}} -\newlabel{Q-adobetypen}{{59}{21}} -\@writefile{toc}{\contentsline {question}{\numberline {60}What are ``resolutions''}{22}} -\newlabel{Q-resolns}{{60}{22}} -\@writefile{toc}{\contentsline {question}{\numberline {61}What is the ``Berry naming scheme''}{22}} -\newlabel{Q-fontname}{{61}{22}} -\@writefile{toc}{\contentsline {section}{\numberline {E}Acquiring the Software}{22}} -\@writefile{toc}{\contentsline {question}{\numberline {62}Repositories of \TeX {} material}{22}} -\newlabel{Q-archives}{{62}{22}} -\@writefile{toc}{\contentsline {question}{\numberline {63}What's the \acro {CTAN} \texttt {nonfree} tree?}{22}} -\newlabel{Q-nonfree}{{63}{22}} -\@writefile{toc}{\contentsline {question}{\numberline {64}Contributing a file to the archives}{23}} -\newlabel{Q-uploads}{{64}{23}} -\@writefile{toc}{\contentsline {question}{\numberline {65}Finding (La)\TeX {} files}{23}} -\newlabel{Q-findfiles}{{65}{23}} -\@writefile{toc}{\contentsline {question}{\numberline {66}Finding new fonts}{23}} -\newlabel{Q-findfont}{{66}{23}} -\@writefile{toc}{\contentsline {question}{\numberline {67}The \TeX {}\nobreakspace {}Live distribution}{24}} -\newlabel{Q-CD}{{67}{24}} -\@writefile{toc}{\contentsline {section}{\numberline {F}\TeX {} Systems}{24}} -\@writefile{toc}{\contentsline {question}{\numberline {68}(La)\TeX {} for different machines}{24}} -\newlabel{Q-TeXsystems}{{68}{24}} -\@writefile{toc}{\contentsline {question}{\numberline {69}\TeX {}-friendly editors and shells}{25}} -\newlabel{Q-editors}{{69}{25}} -\@writefile{toc}{\contentsline {question}{\numberline {70}Commercial \TeX {} implementations}{26}} -\newlabel{Q-commercial}{{70}{26}} -\@writefile{toc}{\contentsline {section}{\numberline {G}\acro {DVI} Drivers and Previewers}{27}} -\@writefile{toc}{\contentsline {question}{\numberline {71}\acro {DVI} to PostScript{} conversion programs}{27}} -\newlabel{Q-dvips}{{71}{27}} -\@writefile{toc}{\contentsline {question}{\numberline {72}\acro {DVI} drivers for \acro {HP} LaserJet}{27}} -\newlabel{Q-HPdrivers}{{72}{27}} -\@writefile{toc}{\contentsline {question}{\numberline {73}Output to ``other'' printers}{27}} -\newlabel{Q-otherprinters}{{73}{27}} -\@writefile{toc}{\contentsline {question}{\numberline {74}\acro {DVI} previewers}{27}} -\newlabel{Q-previewers}{{74}{27}} -\@writefile{toc}{\contentsline {question}{\numberline {75}Generating bitmaps from \acro {DVI}}{28}} -\newlabel{Q-dvi-bmp}{{75}{28}} -\@writefile{toc}{\contentsline {section}{\numberline {H}Support Packages for \TeX {}}{28}} -\@writefile{toc}{\contentsline {question}{\numberline {76}Fig, a (La)\TeX {}-friendly drawing package}{28}} -\newlabel{Q-fig}{{76}{28}} -\@writefile{toc}{\contentsline {question}{\numberline {77}\TeX {}\acro {CAD}, a drawing package for La\TeX {}}{28}} -\newlabel{Q-texcad}{{77}{28}} -\@writefile{toc}{\contentsline {question}{\numberline {78}Spelling checkers for work with \TeX {}}{28}} -\newlabel{Q-spell}{{78}{28}} -\@writefile{toc}{\contentsline {question}{\numberline {79}How many words have you written?}{29}} -\newlabel{Q-wordcount}{{79}{29}} -\@writefile{toc}{\contentsline {section}{\numberline {I}Literate programming}{29}} -\@writefile{toc}{\contentsline {question}{\numberline {80}What is Literate Programming?}{29}} -\newlabel{Q-lit}{{80}{29}} -\@writefile{toc}{\contentsline {question}{\numberline {81}\acro {WEB} systems for various languages}{29}} -\newlabel{Q-webpkgs}{{81}{29}} -\@writefile{toc}{\contentsline {section}{\numberline {J}Format conversions}{29}} -\@writefile{toc}{\contentsline {question}{\numberline {82}Conversion from (La)\TeX {} to plain text}{29}} -\newlabel{Q-toascii}{{82}{29}} -\@writefile{toc}{\contentsline {question}{\numberline {83}Conversion from \acro {SGML} or \acro {HTML} to \TeX {}}{30}} -\newlabel{Q-SGML2TeX}{{83}{30}} -\@writefile{toc}{\contentsline {question}{\numberline {84}Conversion from (La)\TeX {} to \acro {HTML}}{30}} -\newlabel{Q-LaTeX2HTML}{{84}{30}} -\@writefile{toc}{\contentsline {question}{\numberline {85}Other conversions to and from (La)\TeX {}}{31}} -\newlabel{Q-fmtconv}{{85}{31}} -\@writefile{toc}{\contentsline {question}{\numberline {86}Using \TeX {} to read \acro {SGML} or \acro {XML} directly}{31}} -\newlabel{Q-readML}{{86}{31}} -\@writefile{toc}{\contentsline {question}{\numberline {87}Retrieving (La)\TeX {} from \acro {DVI}, etc.}{32}} -\newlabel{Q-recovertex}{{87}{32}} -\@writefile{toc}{\contentsline {question}{\numberline {88}Translating La\TeX {} to Plain \TeX {}}{32}} -\newlabel{Q-LaTeXtoPlain}{{88}{32}} -\@writefile{toc}{\contentsline {section}{\numberline {K}Installing (La)\TeX {} files}{32}} -\@writefile{toc}{\contentsline {question}{\numberline {89}Installing a new package}{32}} -\newlabel{Q-instpackages}{{89}{32}} -\@writefile{toc}{\contentsline {question}{\numberline {90}Where to put new files}{33}} -\newlabel{Q-wherefiles}{{90}{33}} -\@writefile{toc}{\contentsline {question}{\numberline {91}Installing MiKTeX{} ``known packages''}{33}} -\newlabel{Q-miktexinst}{{91}{33}} -\@writefile{toc}{\contentsline {question}{\numberline {92}``Temporary'' installation of (La)\TeX {} files}{33}} -\newlabel{Q-tempinst}{{92}{33}} -\@writefile{toc}{\contentsline {question}{\numberline {93}``Private'' installations of files}{34}} -\newlabel{Q-privinst}{{93}{34}} -\@writefile{toc}{\contentsline {question}{\numberline {94}Installing a new font}{35}} -\newlabel{Q-instfont}{{94}{35}} -\@writefile{toc}{\contentsline {question}{\numberline {95}Installing a font provided as \MF {} source}{35}} -\newlabel{Q-instmffont}{{95}{35}} -\@writefile{toc}{\contentsline {question}{\numberline {96}Installing a PostScript{} printer built-in font}{35}} -\newlabel{Q-instprinterfont}{{96}{35}} -\@writefile{toc}{\contentsline {question}{\numberline {97}Installing the Bluesky versions of the CM\nobreakspace {}fonts}{35}} -\newlabel{Q-inst1cm}{{97}{35}} -\@writefile{toc}{\contentsline {question}{\numberline {98}Installing a Type\nobreakspace {}1 font}{36}} -\newlabel{Q-instt1font}{{98}{36}} -\@writefile{toc}{\contentsline {section}{\numberline {L}Fonts}{36}} -\@writefile{toc}{\contentsline {subsection}{\numberline {L.1}\MF {} fonts}{36}} -\@writefile{toc}{\contentsline {question}{\numberline {99}Getting \MF {} to do what you want}{36}} -\newlabel{Q-useMF}{{99}{36}} -\@writefile{toc}{\contentsline {question}{\numberline {100}Which font files should be kept}{37}} -\newlabel{Q-keepfonts}{{100}{37}} -\@writefile{toc}{\contentsline {question}{\numberline {101}Acquiring bitmap fonts}{37}} -\newlabel{Q-getbitmap}{{101}{37}} -\@writefile{toc}{\contentsline {subsection}{\numberline {L.2}Adobe Type\nobreakspace {}1 (``PostScript{}'') fonts}{38}} -\@writefile{toc}{\contentsline {question}{\numberline {102}Using PostScript{} fonts with \TeX {}}{38}} -\newlabel{Q-usepsfont}{{102}{38}} -\@writefile{toc}{\contentsline {question}{\numberline {103}Previewing files using Type 1 fonts}{38}} -\newlabel{Q-PSpreview}{{103}{38}} -\@writefile{toc}{\contentsline {question}{\numberline {104}\TeX {} font metric files for PostScript{} fonts}{38}} -\newlabel{Q-metrics}{{104}{38}} -\@writefile{toc}{\contentsline {question}{\numberline {105}Deploying Type 1 fonts}{39}} -\newlabel{Q-psfontprob}{{105}{39}} -\@writefile{toc}{\contentsline {question}{\numberline {106}Choice of scalable outline fonts}{39}} -\newlabel{Q-psfchoice}{{106}{39}} -\@writefile{toc}{\contentsline {question}{\numberline {107}Weird characters in \ProgName {dvips} output}{42}} -\newlabel{Q-charshift}{{107}{42}} -\@writefile{toc}{\contentsline {subsection}{\numberline {L.3}Macros for using fonts}{42}} -\@writefile{toc}{\contentsline {question}{\numberline {108}Using non-standard fonts in Plain \TeX {}}{42}} -\newlabel{Q-fonts-pln}{{108}{42}} -\@writefile{toc}{\contentsline {subsection}{\numberline {L.4}Particular font families}{43}} -\@writefile{toc}{\contentsline {question}{\numberline {109}Using the ``Concrete'' fonts}{43}} -\newlabel{Q-concrete}{{109}{43}} -\@writefile{toc}{\contentsline {question}{\numberline {110}Using the Latin Modern fonts}{43}} -\newlabel{Q-uselmfonts}{{110}{43}} -\@writefile{toc}{\contentsline {section}{\numberline {M}Hypertext and \acro {PDF}}{43}} -\@writefile{toc}{\contentsline {question}{\numberline {111}Making hypertext documents from \TeX {}}{43}} -\newlabel{Q-hyper}{{111}{43}} -\@writefile{toc}{\contentsline {question}{\numberline {112}Making Acrobat \acro {PDF} documents from (La)\TeX {}}{44}} -\newlabel{Q-acrobat}{{112}{44}} -\@writefile{toc}{\contentsline {question}{\numberline {113}Quality of \acro {PDF} from PostScript{}}{44}} -\newlabel{Q-dvips-pdf}{{113}{44}} -\@writefile{toc}{\contentsline {question}{\numberline {114}The wrong type of fonts in \acro {PDF}}{45}} -\newlabel{Q-fuzzy-type3}{{114}{45}} -\@writefile{toc}{\contentsline {question}{\numberline {115}Fuzzy fonts because \ProgName {Ghostscript} too old}{45}} -\newlabel{Q-fuzzy-gs}{{115}{45}} -\@writefile{toc}{\contentsline {question}{\numberline {116}Fonts go fuzzy when you switch to \acro {T}1}{45}} -\newlabel{Q-fuzzy-T1}{{116}{45}} -\@writefile{toc}{\contentsline {question}{\numberline {117}Characters missing from \acro {PDF} output}{46}} -\newlabel{Q-distill-prob}{{117}{46}} -\@writefile{toc}{\contentsline {question}{\numberline {118}Finding `8-bit' Type\nobreakspace {}1 fonts}{46}} -\newlabel{Q-type1T1}{{118}{46}} -\@writefile{toc}{\contentsline {question}{\numberline {119}Replacing Type 3 fonts in PostScript{}}{47}} -\newlabel{Q-pkfix}{{119}{47}} -\@writefile{toc}{\contentsline {question}{\numberline {120}\ProgName {Hyperref} and repeated page numbers}{47}} -\newlabel{Q-pdfpagelabels}{{120}{47}} -\@writefile{toc}{\contentsline {question}{\numberline {121}Searching \acro {PDF} files}{47}} -\newlabel{Q-srchpdf}{{121}{47}} -\@writefile{toc}{\contentsline {section}{\numberline {N}Graphics}{47}} -\@writefile{toc}{\contentsline {question}{\numberline {122}How to import graphics into (La)\TeX {} documents}{47}} -\newlabel{Q-impgraph}{{122}{47}} -\@writefile{toc}{\contentsline {question}{\numberline {123}Imported graphics in \ProgName {dvips}}{48}} -\newlabel{Q-dvipsgraphics}{{123}{48}} -\@writefile{toc}{\contentsline {question}{\numberline {124}Imported graphics in PDFLa\TeX {}}{48}} -\newlabel{Q-pdftexgraphics}{{124}{48}} -\@writefile{toc}{\contentsline {question}{\numberline {125}Imported graphics in \ProgName {dvipdfm}}{49}} -\newlabel{Q-dvipdfmgraphics}{{125}{49}} -\@writefile{toc}{\contentsline {question}{\numberline {126}Importing graphics from ``somewhere else''}{49}} -\newlabel{Q-graphicspath}{{126}{49}} -\@writefile{toc}{\contentsline {question}{\numberline {127}Portable imported graphics}{50}} -\newlabel{Q-graph-pspdf}{{127}{50}} -\@writefile{toc}{\contentsline {question}{\numberline {128}Repeated graphics in a document}{50}} -\newlabel{Q-repeatgrf}{{128}{50}} -\@writefile{toc}{\contentsline {question}{\numberline {129}Limit the width of imported graphics}{50}} -\newlabel{Q-grmaxwidth}{{129}{50}} -\@writefile{toc}{\contentsline {question}{\numberline {130}Top-aligning imported graphics}{50}} -\newlabel{Q-topgraph}{{130}{50}} -\@writefile{toc}{\contentsline {question}{\numberline {131}Displaying \MP {} output in \ProgName {ghostscript}}{51}} -\newlabel{Q-mpprologues}{{131}{51}} -\@writefile{toc}{\contentsline {question}{\numberline {132}Drawing with \TeX {}}{51}} -\newlabel{Q-drawing}{{132}{51}} -\@writefile{toc}{\contentsline {question}{\numberline {133}Drawing Feynman diagrams in La\TeX {}}{52}} -\newlabel{Q-drawFeyn}{{133}{52}} -\@writefile{toc}{\contentsline {question}{\numberline {134}Labelling graphics}{52}} -\newlabel{Q-labelfig}{{134}{52}} -\@writefile{toc}{\contentsline {section}{\numberline {O}Bibliographies and citations}{53}} -\@writefile{toc}{\contentsline {subsection}{\numberline {O.1}Creating bibliographies}{53}} -\@writefile{toc}{\contentsline {question}{\numberline {135}Creating a Bib\TeX {} bibliography file}{53}} -\newlabel{Q-buildbib}{{135}{53}} -\@writefile{toc}{\contentsline {question}{\numberline {136}Creating a bibliography style}{53}} -\newlabel{Q-custbib}{{136}{53}} -\@writefile{toc}{\contentsline {question}{\numberline {137}Capitalisation in Bib\TeX {}}{53}} -\newlabel{Q-capbibtex}{{137}{53}} -\@writefile{toc}{\contentsline {question}{\numberline {138}Accents in bibliographies}{54}} -\newlabel{Q-bibaccent}{{138}{54}} -\@writefile{toc}{\contentsline {question}{\numberline {139}`String too long' in Bib\TeX {}}{54}} -\newlabel{Q-bibstrtl}{{139}{54}} -\@writefile{toc}{\contentsline {question}{\numberline {140}Bib\TeX {} doesn't understand lists of names}{54}} -\newlabel{Q-manyauthor}{{140}{54}} -\@writefile{toc}{\contentsline {question}{\numberline {141}\acro {URL}s in Bib\TeX {} bibliographies}{54}} -\newlabel{Q-citeURL}{{141}{54}} -\@writefile{toc}{\contentsline {question}{\numberline {142}Using Bib\TeX {} with Plain \TeX {}}{55}} -\newlabel{Q-bibplain}{{142}{55}} -\@writefile{toc}{\contentsline {question}{\numberline {143}Reconstructing \texttt {.bib} files}{55}} -\newlabel{Q-makebib}{{143}{55}} -\@writefile{toc}{\contentsline {question}{\numberline {144}Bib\TeX {} sorting and name prefixes}{55}} -\newlabel{Q-bibprefixsort}{{144}{55}} -\@writefile{toc}{\contentsline {question}{\numberline {145}Transcribed initials in Bib\TeX {}}{56}} -\newlabel{Q-bibtranscinit}{{145}{56}} -\@writefile{toc}{\contentsline {subsection}{\numberline {O.2}Creating citations}{56}} -\@writefile{toc}{\contentsline {question}{\numberline {146}``Normal'' use of Bib\TeX {} from La\TeX {}}{56}} -\newlabel{Q-usebibtex}{{146}{56}} -\@writefile{toc}{\contentsline {question}{\numberline {147}Choosing a bibliography style}{56}} -\newlabel{Q-whatbst}{{147}{56}} -\@writefile{toc}{\contentsline {question}{\numberline {148}Separate bibliographies per chapter?}{57}} -\newlabel{Q-chapbib}{{148}{57}} -\@writefile{toc}{\contentsline {question}{\numberline {149}Multiple bibliographies?}{57}} -\newlabel{Q-multbib}{{149}{57}} -\@writefile{toc}{\contentsline {question}{\numberline {150}Putting bibliography entries in text}{58}} -\newlabel{Q-bibinline}{{150}{58}} -\@writefile{toc}{\contentsline {question}{\numberline {151}Sorting and compressing citations}{58}} -\newlabel{Q-citesort}{{151}{58}} -\@writefile{toc}{\contentsline {question}{\numberline {152}Multiple citations}{59}} -\newlabel{Q-mcite}{{152}{59}} -\@writefile{toc}{\contentsline {question}{\numberline {153}References from the bibliography to the citation}{59}} -\newlabel{Q-backref}{{153}{59}} -\@writefile{toc}{\contentsline {question}{\numberline {154}Sorting lists of citations}{59}} -\newlabel{Q-sortbib}{{154}{59}} -\@writefile{toc}{\contentsline {question}{\numberline {155}Reducing spacing in the bibliography}{59}} -\newlabel{Q-compactbib}{{155}{59}} -\@writefile{toc}{\contentsline {question}{\numberline {156}Table of contents rearranges ``\ProgName {unsrt}'' ordering}{59}} -\newlabel{Q-bibtocorder}{{156}{59}} -\@writefile{toc}{\contentsline {question}{\numberline {157}Non-english bibliographies}{60}} -\newlabel{Q-i18nbib}{{157}{60}} -\@writefile{toc}{\contentsline {question}{\numberline {158}Format of numbers in the bibliography}{60}} -\newlabel{Q-formbiblabel}{{158}{60}} -\@writefile{toc}{\contentsline {subsection}{\numberline {O.3}Manipulating whole bibliographies}{60}} -\@writefile{toc}{\contentsline {question}{\numberline {159}Listing all your Bib\TeX {} entries}{60}} -\newlabel{Q-nocite*}{{159}{60}} -\@writefile{toc}{\contentsline {question}{\numberline {160}Making \acro {HTML} of your Bibliography}{60}} -\newlabel{Q-htmlbib}{{160}{60}} -\@writefile{toc}{\contentsline {section}{\numberline {P}Adjusting the typesetting}{61}} -\@writefile{toc}{\contentsline {subsection}{\numberline {P.1}Alternative document classes}{61}} -\@writefile{toc}{\contentsline {question}{\numberline {161}Replacing the standard classes}{61}} -\newlabel{Q-replstdcls}{{161}{61}} -\@writefile{toc}{\contentsline {question}{\numberline {162}Producing slides}{61}} -\newlabel{Q-slidecls}{{162}{61}} -\@writefile{toc}{\contentsline {question}{\numberline {163}Creating posters with La\TeX {}}{61}} -\newlabel{Q-poster}{{163}{61}} -\@writefile{toc}{\contentsline {question}{\numberline {164}Formatting a thesis in La\TeX {}}{62}} -\newlabel{Q-thesis}{{164}{62}} -\@writefile{toc}{\contentsline {question}{\numberline {165}Setting papers for journals}{62}} -\newlabel{Q-journalpaper}{{165}{62}} -\@writefile{toc}{\contentsline {question}{\numberline {166}A `report' from lots of `article's}{62}} -\newlabel{Q-multidoc}{{166}{62}} -\@writefile{toc}{\contentsline {question}{\numberline {167}\emph {Curriculum Vitae} (R\'esum\'e)}{63}} -\newlabel{Q-cv}{{167}{63}} -\@writefile{toc}{\contentsline {question}{\numberline {168}Letters and the like}{63}} -\newlabel{Q-letterclass}{{168}{63}} -\@writefile{toc}{\contentsline {question}{\numberline {169}Other ``document font'' sizes?}{63}} -\newlabel{Q-extsizes}{{169}{63}} -\@writefile{toc}{\contentsline {subsection}{\numberline {P.2}Document structure}{63}} -\@writefile{toc}{\contentsline {question}{\numberline {170}The style of document titles}{63}} -\newlabel{Q-titlsty}{{170}{63}} -\@writefile{toc}{\contentsline {question}{\numberline {171}The style of section headings}{64}} -\newlabel{Q-secthead}{{171}{64}} -\@writefile{toc}{\contentsline {question}{\numberline {172}Appendixes}{64}} -\newlabel{Q-appendix}{{172}{64}} -\@writefile{toc}{\contentsline {question}{\numberline {173}Indent after section headings}{65}} -\newlabel{Q-secindent}{{173}{65}} -\@writefile{toc}{\contentsline {question}{\numberline {174}How to create a \csx {subsubsubsection}}{65}} -\newlabel{Q-subsubsub}{{174}{65}} -\@writefile{toc}{\contentsline {question}{\numberline {175}The style of captions}{65}} -\newlabel{Q-captsty}{{175}{65}} -\@writefile{toc}{\contentsline {question}{\numberline {176}Alternative head- and footlines in La\TeX {}}{66}} -\newlabel{Q-fancyhdr}{{176}{66}} -\@writefile{toc}{\contentsline {question}{\numberline {177}Wide figures in two-column documents}{66}} -\newlabel{Q-widefigs}{{177}{66}} -\@writefile{toc}{\contentsline {question}{\numberline {178}1-column abstract in 2-column document}{66}} -\newlabel{Q-onecolabs}{{178}{66}} -\@writefile{toc}{\contentsline {question}{\numberline {179}Really blank pages between chapters}{66}} -\newlabel{Q-reallyblank}{{179}{66}} -\@writefile{toc}{\contentsline {question}{\numberline {180}Balancing columns at the end of a document}{67}} -\newlabel{Q-balance}{{180}{67}} -\@writefile{toc}{\contentsline {question}{\numberline {181}My section title is too wide for the page header}{67}} -\newlabel{Q-runheadtoobig}{{181}{67}} -\@writefile{toc}{\contentsline {question}{\numberline {182}Page numbering ``\ensuremath {\delimiter "426830A }\emph {n}\ensuremath {\delimiter "526930B } of \ensuremath {\delimiter "426830A }\emph {m}\ensuremath {\delimiter "526930B }''}{68}} -\newlabel{Q-nofm}{{182}{68}} -\@writefile{toc}{\contentsline {question}{\numberline {183}Page numbering by chapter}{68}} -\newlabel{Q-pagebychap}{{183}{68}} -\@writefile{toc}{\contentsline {subsection}{\numberline {P.3}Page layout}{68}} -\@writefile{toc}{\contentsline {question}{\numberline {184}Printer paper sizes}{68}} -\newlabel{Q-papersize}{{184}{68}} -\@writefile{toc}{\contentsline {question}{\numberline {185}Changing the margins in La\TeX {}}{69}} -\newlabel{Q-changemargin}{{185}{69}} -\@writefile{toc}{\contentsline {question}{\numberline {186}Packages to set up page designs}{69}} -\newlabel{Q-marginpkgs}{{186}{69}} -\@writefile{toc}{\contentsline {question}{\numberline {187}How to set up page layout ``by hand''}{69}} -\newlabel{Q-marginmanual}{{187}{69}} -\@writefile{toc}{\contentsline {question}{\numberline {188}Changing margins ``on the fly''}{69}} -\newlabel{Q-chngmargonfly}{{188}{69}} -\@writefile{toc}{\contentsline {question}{\numberline {189}How to get rid of page numbers}{70}} -\newlabel{Q-nopageno}{{189}{70}} -\@writefile{toc}{\contentsline {question}{\numberline {190}\psatempty {} on first page in La\TeX {}}{70}} -\newlabel{Q-ps@empty}{{190}{70}} -\@writefile{toc}{\contentsline {question}{\numberline {191}How to create crop marks}{71}} -\newlabel{Q-crop}{{191}{71}} -\@writefile{toc}{\contentsline {question}{\numberline {192}`Watermarks' on every page}{71}} -\newlabel{Q-watermark}{{192}{71}} -\@writefile{toc}{\contentsline {question}{\numberline {193}Typesetting things in landscape orientation}{71}} -\newlabel{Q-landscape}{{193}{71}} -\@writefile{toc}{\contentsline {question}{\numberline {194}Putting things at fixed positions on the page}{72}} -\newlabel{Q-abspos}{{194}{72}} -\@writefile{toc}{\contentsline {question}{\numberline {195}Preventing page breaks between lines}{72}} -\newlabel{Q-nopagebrk}{{195}{72}} -\@writefile{toc}{\contentsline {question}{\numberline {196}Parallel setting of text}{73}} -\newlabel{Q-parallel}{{196}{73}} -\@writefile{toc}{\contentsline {question}{\numberline {197}Typesetting epigraphs}{73}} -\newlabel{Q-epigraph}{{197}{73}} -\@writefile{toc}{\contentsline {question}{\numberline {198}(La)\TeX {} \acro {PDF} output prints at wrong size}{73}} -\newlabel{Q-outszwrng}{{198}{73}} -\@writefile{toc}{\contentsline {subsection}{\numberline {P.4}Spacing of characters and lines}{74}} -\@writefile{toc}{\contentsline {question}{\numberline {199}Double-spaced documents in La\TeX {}}{74}} -\newlabel{Q-linespace}{{199}{74}} -\@writefile{toc}{\contentsline {question}{\numberline {200}Changing the space between letters}{74}} -\newlabel{Q-letterspace}{{200}{74}} -\@writefile{toc}{\contentsline {question}{\numberline {201}Setting text ragged right}{74}} -\newlabel{Q-ragright}{{201}{74}} -\@writefile{toc}{\contentsline {question}{\numberline {202}Cancelling \csx {ragged} commands}{74}} -\newlabel{Q-flushboth}{{202}{74}} -\@writefile{toc}{\contentsline {subsection}{\numberline {P.5}Typesetting specialities}{75}} -\@writefile{toc}{\contentsline {question}{\numberline {203}Including a file verbatim in La\TeX {}}{75}} -\newlabel{Q-verbfile}{{203}{75}} -\@writefile{toc}{\contentsline {question}{\numberline {204}Including line numbers in typeset output}{75}} -\newlabel{Q-linenos}{{204}{75}} -\@writefile{toc}{\contentsline {question}{\numberline {205}Code listings in La\TeX {}}{75}} -\newlabel{Q-codelist}{{205}{75}} -\@writefile{toc}{\contentsline {question}{\numberline {206}Typesetting pseudocode in La\TeX {}}{76}} -\newlabel{Q-algorithms}{{206}{76}} -\@writefile{toc}{\contentsline {question}{\numberline {207}Generating an index in (La)\TeX {}}{77}} -\newlabel{Q-makeindex}{{207}{77}} -\@writefile{toc}{\contentsline {question}{\numberline {208}Typesetting \acro {URL}s}{77}} -\newlabel{Q-setURL}{{208}{77}} -\@writefile{toc}{\contentsline {question}{\numberline {209}Typesetting music in \TeX {}}{77}} -\newlabel{Q-music}{{209}{77}} -\@writefile{toc}{\contentsline {question}{\numberline {210}Zero paragraph indent}{78}} -\newlabel{Q-parskip}{{210}{78}} -\@writefile{toc}{\contentsline {question}{\numberline {211}Big letters at the start of a paragraph}{78}} -\newlabel{Q-dropping}{{211}{78}} -\@writefile{toc}{\contentsline {question}{\numberline {212}The comma as a decimal separator}{78}} -\newlabel{Q-dec_comma}{{212}{78}} -\@writefile{toc}{\contentsline {question}{\numberline {213}Breaking boxes of text}{79}} -\newlabel{Q-breakbox}{{213}{79}} -\@writefile{toc}{\contentsline {question}{\numberline {214}Overstriking characters}{79}} -\newlabel{Q-overstrike}{{214}{79}} -\@writefile{toc}{\contentsline {question}{\numberline {215}Realistic quotes for verbatim listings}{79}} -\newlabel{Q-upquot}{{215}{79}} -\@writefile{toc}{\contentsline {question}{\numberline {216}Printing the time}{79}} -\newlabel{Q-time}{{216}{79}} -\@writefile{toc}{\contentsline {question}{\numberline {217}Redefining counters' \csx {the-}commands}{79}} -\newlabel{Q-the-commands}{{217}{79}} -\@writefile{toc}{\contentsline {subsection}{\numberline {P.6}Tables of contents and indexes}{80}} -\@writefile{toc}{\contentsline {question}{\numberline {218}The format of the Table of Contents, etc.}{80}} -\newlabel{Q-tocloft}{{218}{80}} -\@writefile{toc}{\contentsline {question}{\numberline {219}Unnumbered sections in the Table of Contents}{80}} -\newlabel{Q-secnumdep}{{219}{80}} -\@writefile{toc}{\contentsline {question}{\numberline {220}Bibliography, index, etc., in \acro {TOC}}{80}} -\newlabel{Q-tocbibind}{{220}{80}} -\@writefile{toc}{\contentsline {question}{\numberline {221}Table of contents, etc., per chapter}{81}} -\newlabel{Q-minitoc}{{221}{81}} -\@writefile{toc}{\contentsline {question}{\numberline {222}Multiple indexes}{81}} -\newlabel{Q-multind}{{222}{81}} -\@writefile{toc}{\contentsline {subsection}{\numberline {P.7}Labels and references}{82}} -\@writefile{toc}{\contentsline {question}{\numberline {223}Referring to things by their name}{82}} -\newlabel{Q-nameref}{{223}{82}} -\@writefile{toc}{\contentsline {question}{\numberline {224}Referring to labels in other documents}{82}} -\newlabel{Q-extref}{{224}{82}} -\@writefile{toc}{\contentsline {section}{\numberline {Q}How do I do\dots {}?}{82}} -\@writefile{toc}{\contentsline {subsection}{\numberline {Q.1}Mathematics}{82}} -\@writefile{toc}{\contentsline {question}{\numberline {225}Proof environment}{82}} -\newlabel{Q-proof}{{225}{82}} -\@writefile{toc}{\contentsline {question}{\numberline {226}Roman theorems}{83}} -\newlabel{Q-theoremfmt}{{226}{83}} -\@writefile{toc}{\contentsline {question}{\numberline {227}Defining a new log-like function in La\TeX {}}{83}} -\newlabel{Q-newfunction}{{227}{83}} -\@writefile{toc}{\contentsline {question}{\numberline {228}Set specifications and Dirac brackets}{83}} -\newlabel{Q-braket}{{228}{83}} -\@writefile{toc}{\contentsline {question}{\numberline {229}Cancelling terms in maths expressions}{83}} -\newlabel{Q-cancellation}{{229}{83}} -\@writefile{toc}{\contentsline {question}{\numberline {230}Adjusting maths font sizes}{83}} -\newlabel{Q-mathsize}{{230}{83}} -\@writefile{toc}{\contentsline {question}{\numberline {231}Ellipses}{84}} -\newlabel{Q-mathlips}{{231}{84}} -\@writefile{toc}{\contentsline {question}{\numberline {232}Sub- and superscript positioning for operators}{84}} -\newlabel{Q-limits}{{232}{84}} -\@writefile{toc}{\contentsline {question}{\numberline {233}Text inside maths}{84}} -\newlabel{Q-mathstext}{{233}{84}} -\@writefile{toc}{\contentsline {question}{\numberline {234}Re-using an equation}{85}} -\newlabel{Q-reuseq}{{234}{85}} -\@writefile{toc}{\contentsline {question}{\numberline {235}Line-breaking in in-line maths}{86}} -\newlabel{Q-brkinline}{{235}{86}} -\@writefile{toc}{\contentsline {subsection}{\numberline {Q.2}Lists}{86}} -\@writefile{toc}{\contentsline {question}{\numberline {236}Fancy enumeration lists}{86}} -\newlabel{Q-enumerate}{{236}{86}} -\@writefile{toc}{\contentsline {question}{\numberline {237}How to reduce list spacing}{86}} -\newlabel{Q-complist}{{237}{86}} -\@writefile{toc}{\contentsline {question}{\numberline {238}Interrupting enumerated lists}{87}} -\newlabel{Q-interruptlist}{{238}{87}} -\@writefile{toc}{\contentsline {subsection}{\numberline {Q.3}Tables, figures and diagrams}{88}} -\@writefile{toc}{\contentsline {question}{\numberline {239}The design of tables}{88}} -\newlabel{Q-destable}{{239}{88}} -\@writefile{toc}{\contentsline {question}{\numberline {240}Fixed-width tables}{88}} -\newlabel{Q-fixwidtab}{{240}{88}} -\@writefile{toc}{\contentsline {question}{\numberline {241}Variable-width columns in tables}{89}} -\newlabel{Q-varwidcol}{{241}{89}} -\@writefile{toc}{\contentsline {question}{\numberline {242}Spacing lines in tables}{89}} -\newlabel{Q-struttab}{{242}{89}} -\@writefile{toc}{\contentsline {question}{\numberline {243}Tables longer than a single page}{90}} -\newlabel{Q-longtab}{{243}{90}} -\@writefile{toc}{\contentsline {question}{\numberline {244}How to alter the alignment of tabular cells}{90}} -\newlabel{Q-tabcellalign}{{244}{90}} -\@writefile{toc}{\contentsline {question}{\numberline {245}The thickness of rules in La\TeX {} tables}{91}} -\newlabel{Q-rulethk}{{245}{91}} -\@writefile{toc}{\contentsline {question}{\numberline {246}Flowing text around figures in La\TeX {}}{91}} -\newlabel{Q-textflow}{{246}{91}} -\@writefile{toc}{\contentsline {question}{\numberline {247}Diagonal separation in corner cells of tables}{92}} -\newlabel{Q-slashbox}{{247}{92}} -\@writefile{toc}{\contentsline {question}{\numberline {248}How to change a whole row of a table}{92}} -\newlabel{Q-wholerow}{{248}{92}} -\@writefile{toc}{\contentsline {question}{\numberline {249}Merging cells in a column of a table}{92}} -\newlabel{Q-multirow}{{249}{92}} -\@writefile{toc}{\contentsline {subsection}{\numberline {Q.4}Floating tables, figures, etc.}{93}} -\@writefile{toc}{\contentsline {question}{\numberline {250}Floats on their own on float pages}{93}} -\newlabel{Q-floatpages}{{250}{93}} -\@writefile{toc}{\contentsline {question}{\numberline {251}Extra vertical space in floats}{93}} -\newlabel{Q-vertspacefloat}{{251}{93}} -\@writefile{toc}{\contentsline {question}{\numberline {252}Placing two-column floats at bottom of page}{93}} -\newlabel{Q-2colfloat}{{252}{93}} -\@writefile{toc}{\contentsline {question}{\numberline {253}Floats in multicolumn setting}{94}} -\newlabel{Q-mcfloat}{{253}{94}} -\@writefile{toc}{\contentsline {question}{\numberline {254}Facing floats on 2-page spread}{94}} -\newlabel{Q-dpfloat}{{254}{94}} -\@writefile{toc}{\contentsline {question}{\numberline {255}Vertical layout of float pages}{94}} -\newlabel{Q-vertposfp}{{255}{94}} -\@writefile{toc}{\contentsline {subsection}{\numberline {Q.5}Footnotes}{94}} -\@writefile{toc}{\contentsline {question}{\numberline {256}Footnotes in tables}{94}} -\newlabel{Q-footintab}{{256}{94}} -\@writefile{toc}{\contentsline {question}{\numberline {257}Footnotes in La\TeX {} section headings}{95}} -\newlabel{Q-ftnsect}{{257}{95}} -\@writefile{toc}{\contentsline {question}{\numberline {258}Footnotes in captions}{95}} -\newlabel{Q-ftncapt}{{258}{95}} -\@writefile{toc}{\contentsline {question}{\numberline {259}Footnotes whose texts are identical}{95}} -\newlabel{Q-repfootnote}{{259}{95}} -\@writefile{toc}{\contentsline {question}{\numberline {260}More than one sequence of footnotes}{96}} -\newlabel{Q-multfoot}{{260}{96}} -\@writefile{toc}{\contentsline {question}{\numberline {261}Footnotes numbered ``per page''}{96}} -\newlabel{Q-footnpp}{{261}{96}} -\@writefile{toc}{\contentsline {subsection}{\numberline {Q.6}Document management}{96}} -\@writefile{toc}{\contentsline {question}{\numberline {262}What's the name of this file}{96}} -\newlabel{Q-filename}{{262}{96}} -\@writefile{toc}{\contentsline {question}{\numberline {263}All the files used by this document}{97}} -\newlabel{Q-filesused}{{263}{97}} -\@writefile{toc}{\contentsline {question}{\numberline {264}Marking changed parts of your document}{97}} -\newlabel{Q-changebars}{{264}{97}} -\@writefile{toc}{\contentsline {question}{\numberline {265}Conditional compilation and ``comments''}{98}} -\newlabel{Q-conditional}{{265}{98}} -\@writefile{toc}{\contentsline {question}{\numberline {266}Bits of document from other directories}{99}} -\newlabel{Q-docotherdir}{{266}{99}} -\@writefile{toc}{\contentsline {question}{\numberline {267}Version control using \acro {RCS}, \acro {CVS} or \ProgName {Subversion}}{100}} -\newlabel{Q-RCS}{{267}{100}} -\@writefile{toc}{\contentsline {question}{\numberline {268}Makefiles for La\TeX {} documents}{100}} -\newlabel{Q-make}{{268}{100}} -\@writefile{toc}{\contentsline {question}{\numberline {269}How many pages are there in my document?}{100}} -\newlabel{Q-howmanypp}{{269}{100}} -\@writefile{toc}{\contentsline {question}{\numberline {270}Including Plain \TeX {} files in La\TeX {}}{101}} -\newlabel{Q-inclplain}{{270}{101}} -\@writefile{toc}{\contentsline {subsection}{\numberline {Q.7}Hyphenation}{101}} -\@writefile{toc}{\contentsline {question}{\numberline {271}My words aren't being hyphenated}{101}} -\newlabel{Q-nohyph}{{271}{101}} -\@writefile{toc}{\contentsline {question}{\numberline {272}Weird hyphenation of words}{101}} -\newlabel{Q-weirdhyphen}{{272}{101}} -\@writefile{toc}{\contentsline {question}{\numberline {273}(Merely) peculiar hyphenation}{102}} -\newlabel{Q-oddhyphen}{{273}{102}} -\@writefile{toc}{\contentsline {question}{\numberline {274}Accented words aren't hyphenated}{102}} -\newlabel{Q-hyphenaccents}{{274}{102}} -\@writefile{toc}{\contentsline {question}{\numberline {275}Using a new language with Babel}{102}} -\newlabel{Q-newlang}{{275}{102}} -\@writefile{toc}{\contentsline {question}{\numberline {276}Stopping all hyphenation}{102}} -\newlabel{Q-hyphoff}{{276}{102}} -\@writefile{toc}{\contentsline {question}{\numberline {277}Preventing hyphenation of a particular word}{103}} -\newlabel{Q-wdnohyph}{{277}{103}} -\@writefile{toc}{\contentsline {question}{\numberline {278}Hyphenation exceptions}{103}} -\newlabel{Q-hyphexcept}{{278}{103}} -\@writefile{toc}{\contentsline {subsection}{\numberline {Q.8}Odds and ends}{104}} -\@writefile{toc}{\contentsline {question}{\numberline {279}Typesetting all those \TeX {}-related logos}{104}} -\newlabel{Q-logos}{{279}{104}} -\@writefile{toc}{\contentsline {question}{\numberline {280}How to do bold-tt or bold-sc}{104}} -\newlabel{Q-bold-extras}{{280}{104}} -\@writefile{toc}{\contentsline {question}{\numberline {281}Automatic sizing of \texttt {minipage}}{104}} -\newlabel{Q-varwidth}{{281}{104}} -\@writefile{toc}{\contentsline {section}{\numberline {R}Symbols, etc.}{105}} -\@writefile{toc}{\contentsline {question}{\numberline {282}Symbols for the number sets}{105}} -\newlabel{Q-numbersets}{{282}{105}} -\@writefile{toc}{\contentsline {question}{\numberline {283}Better script fonts for maths}{106}} -\newlabel{Q-scriptfonts}{{283}{106}} -\@writefile{toc}{\contentsline {question}{\numberline {284}Setting bold Greek letters in La\TeX {}}{106}} -\newlabel{Q-boldgreek}{{284}{106}} -\@writefile{toc}{\contentsline {question}{\numberline {285}The Principal Value Integral symbol}{106}} -\newlabel{Q-prinvalint}{{285}{106}} -\@writefile{toc}{\contentsline {question}{\numberline {286}How to use the underscore character}{106}} -\newlabel{Q-underscore}{{286}{106}} -\@writefile{toc}{\contentsline {question}{\numberline {287}How to type an `@' sign?}{107}} -\newlabel{Q-atsign}{{287}{107}} -\@writefile{toc}{\contentsline {question}{\numberline {288}Typesetting the Euro sign}{107}} -\newlabel{Q-euro}{{288}{107}} -\@writefile{toc}{\contentsline {question}{\numberline {289}How to get copyright, trademark, etc.}{107}} -\newlabel{Q-tradesyms}{{289}{107}} -\@writefile{toc}{\contentsline {section}{\numberline {S}Macro programming}{108}} -\@writefile{toc}{\contentsline {subsection}{\numberline {S.1}``Generic'' macros and techniques}{108}} -\@writefile{toc}{\contentsline {question}{\numberline {290}Finding the width of a letter, word, or phrase}{108}} -\newlabel{Q-findwidth}{{290}{108}} -\@writefile{toc}{\contentsline {question}{\numberline {291}Patching existing commands}{108}} -\newlabel{Q-patch}{{291}{108}} -\@writefile{toc}{\contentsline {question}{\numberline {292}Comparing the ``job name''}{108}} -\newlabel{Q-compjobnam}{{292}{108}} -\@writefile{toc}{\contentsline {question}{\numberline {293}Is the argument a number?}{108}} -\newlabel{Q-isitanum}{{293}{108}} -\@writefile{toc}{\contentsline {question}{\numberline {294}Defining macros within macros}{109}} -\newlabel{Q-hash}{{294}{109}} -\@writefile{toc}{\contentsline {question}{\numberline {295}Spaces in macros}{110}} -\newlabel{Q-spinmacro}{{295}{110}} -\@writefile{toc}{\contentsline {question}{\numberline {296}How to break the 9-argument limit}{110}} -\newlabel{Q-moren9}{{296}{110}} -\@writefile{toc}{\contentsline {question}{\numberline {297}Defining characters as macros}{111}} -\newlabel{Q-activechars}{{297}{111}} -\@writefile{toc}{\contentsline {question}{\numberline {298}Active characters in command arguments}{112}} -\newlabel{Q-actinarg}{{298}{112}} -\@writefile{toc}{\contentsline {question}{\numberline {299}Defining a macro from an argument}{112}} -\newlabel{Q-csname}{{299}{112}} -\@writefile{toc}{\contentsline {question}{\numberline {300}Transcribing La\TeX {} command definitions}{113}} -\newlabel{Q-cvtlatex}{{300}{113}} -\@writefile{toc}{\contentsline {question}{\numberline {301}Detecting that something is empty}{113}} -\newlabel{Q-empty}{{301}{113}} -\@writefile{toc}{\contentsline {question}{\numberline {302}Am I using PDF\TeX {}?}{113}} -\newlabel{Q-ifpdf}{{302}{113}} -\@writefile{toc}{\contentsline {question}{\numberline {303}Subverting a token register}{114}} -\newlabel{Q-subverttoks}{{303}{114}} -\@writefile{toc}{\contentsline {question}{\numberline {304}Is this command defined?}{114}} -\newlabel{Q-isdef}{{304}{114}} -\@writefile{toc}{\contentsline {subsection}{\numberline {S.2}La\TeX {} macro tools and techniques}{115}} -\@writefile{toc}{\contentsline {question}{\numberline {305}Using Plain or primitive commands in La\TeX {}}{115}} -\newlabel{Q-plninltx}{{305}{115}} -\@writefile{toc}{\contentsline {question}{\numberline {306}\csx {@} and \texttt {@} in macro names}{115}} -\newlabel{Q-atsigns}{{306}{115}} -\@writefile{toc}{\contentsline {question}{\numberline {307}What's the reason for `protection'?}{116}} -\newlabel{Q-protect}{{307}{116}} -\@writefile{toc}{\contentsline {question}{\numberline {308}\csx {edef} does not work with \csx {protect}}{116}} -\newlabel{Q-edef}{{308}{116}} -\@writefile{toc}{\contentsline {question}{\numberline {309}The definitions of La\TeX {} commands}{116}} -\newlabel{Q-ltxcmds}{{309}{116}} -\@writefile{toc}{\contentsline {question}{\numberline {310}Optional arguments like \csx {section}}{117}} -\newlabel{Q-oarglikesect}{{310}{117}} -\@writefile{toc}{\contentsline {question}{\numberline {311}More than one optional argument}{117}} -\newlabel{Q-twooptarg}{{311}{117}} -\@writefile{toc}{\contentsline {question}{\numberline {312}Commands defined with * options}{118}} -\newlabel{Q-cmdstar}{{312}{118}} -\@writefile{toc}{\contentsline {question}{\numberline {313}La\TeX {} internal ``abbreviations'', etc.}{118}} -\newlabel{Q-ltxabbrv}{{313}{118}} -\@writefile{toc}{\contentsline {question}{\numberline {314}Defining La\TeX {} commands within other commands}{118}} -\newlabel{Q-ltxhash}{{314}{118}} -\@writefile{toc}{\contentsline {subsection}{\numberline {S.3}La\TeX {} macro programming}{119}} -\@writefile{toc}{\contentsline {question}{\numberline {315}How to change La\TeX {}'s ``fixed names''}{119}} -\newlabel{Q-fixnam}{{315}{119}} -\@writefile{toc}{\contentsline {question}{\numberline {316}Changing the words \ProgName {babel} uses}{119}} -\newlabel{Q-latexwords}{{316}{119}} -\@writefile{toc}{\contentsline {question}{\numberline {317}Running equation, figure and table numbering}{119}} -\newlabel{Q-running-nos}{{317}{119}} -\@writefile{toc}{\contentsline {question}{\numberline {318}Making labels from a counter}{120}} -\newlabel{Q-labelctr}{{318}{120}} -\@writefile{toc}{\contentsline {question}{\numberline {319}Finding if you're on an odd or an even page}{120}} -\newlabel{Q-oddpage}{{319}{120}} -\@writefile{toc}{\contentsline {question}{\numberline {320}How to change the format of labels}{120}} -\newlabel{Q-labelformat}{{320}{120}} -\@writefile{toc}{\contentsline {question}{\numberline {321}Adjusting the presentation of section numbers}{121}} -\newlabel{Q-seccntfmt}{{321}{121}} -\@writefile{toc}{\contentsline {question}{\numberline {322}There's a space added after my environment}{121}} -\newlabel{Q-spaftend}{{322}{121}} -\@writefile{toc}{\contentsline {question}{\numberline {323}Finding if a label is undefined}{121}} -\newlabel{Q-labundef}{{323}{121}} -\@writefile{toc}{\contentsline {question}{\numberline {324}Master and slave counters}{122}} -\newlabel{Q-addtoreset}{{324}{122}} -\@writefile{toc}{\contentsline {section}{\numberline {T}Things are Going Wrong\dots {}}{122}} -\@writefile{toc}{\contentsline {subsection}{\numberline {T.1}Getting things to fit}{122}} -\@writefile{toc}{\contentsline {question}{\numberline {325}Enlarging \TeX {}}{122}} -\newlabel{Q-enlarge}{{325}{122}} -\@writefile{toc}{\contentsline {question}{\numberline {326}Why can't I load PiC\TeX {}?}{123}} -\newlabel{Q-usepictex}{{326}{123}} -\@writefile{toc}{\contentsline {subsection}{\numberline {T.2}Making things stay where you want them}{123}} -\@writefile{toc}{\contentsline {question}{\numberline {327}Moving tables and figures in La\TeX {}}{123}} -\newlabel{Q-floats}{{327}{123}} -\@writefile{toc}{\contentsline {question}{\numberline {328}Underlined text won't break}{124}} -\newlabel{Q-underline}{{328}{124}} -\@writefile{toc}{\contentsline {question}{\numberline {329}Controlling widows and orphans}{124}} -\newlabel{Q-widows}{{329}{124}} -\@writefile{toc}{\contentsline {subsection}{\numberline {T.3}Things have ``gone away''}{124}} -\@writefile{toc}{\contentsline {question}{\numberline {330}Old La\TeX {} font references such as \csx {tenrm}}{124}} -\newlabel{Q-oldfontnames}{{330}{124}} -\@writefile{toc}{\contentsline {question}{\numberline {331}Missing symbol commands}{124}} -\newlabel{Q-missssymb}{{331}{124}} -\@writefile{toc}{\contentsline {question}{\numberline {332}Where are the \texttt {msx} and \texttt {msy} fonts?}{125}} -\newlabel{Q-msxy}{{332}{125}} -\@writefile{toc}{\contentsline {question}{\numberline {333}Where are the \texttt {am} fonts?}{125}} -\newlabel{Q-amfonts}{{333}{125}} -\@writefile{toc}{\contentsline {section}{\numberline {U}Why does it \emph {do} that?}{125}} -\@writefile{toc}{\contentsline {subsection}{\numberline {U.1}Common errors}{125}} -\@writefile{toc}{\contentsline {question}{\numberline {334}La\TeX {} gets cross-references wrong}{125}} -\newlabel{Q-crossref}{{334}{125}} -\@writefile{toc}{\contentsline {question}{\numberline {335}Start of line goes awry}{125}} -\newlabel{Q-newlineargs}{{335}{125}} -\@writefile{toc}{\contentsline {question}{\numberline {336}Why doesn't verbatim work within\,\dots {}?}{126}} -\newlabel{Q-verbwithin}{{336}{126}} -\@writefile{toc}{\contentsline {question}{\numberline {337}No line here to end}{126}} -\newlabel{Q-noline}{{337}{126}} -\@writefile{toc}{\contentsline {question}{\numberline {338}Two-column float numbers out of order}{127}} -\newlabel{Q-2colfltorder}{{338}{127}} -\@writefile{toc}{\contentsline {question}{\numberline {339}Accents misbehave in \texttt {tabbing}}{127}} -\newlabel{Q-tabacc}{{339}{127}} -\@writefile{toc}{\contentsline {question}{\numberline {340}Package reports ``command already defined''}{128}} -\newlabel{Q-alreadydef}{{340}{128}} -\@writefile{toc}{\contentsline {question}{\numberline {341}Why are my sections numbered 0.1\,\dots {}?}{128}} -\newlabel{Q-zerochap}{{341}{128}} -\@writefile{toc}{\contentsline {question}{\numberline {342}Link text doesn't break at end line}{128}} -\newlabel{Q-breaklinks}{{342}{128}} -\@writefile{toc}{\contentsline {question}{\numberline {343}Page number is wrong at start of page}{128}} -\newlabel{Q-wrongpn}{{343}{128}} -\@writefile{toc}{\contentsline {question}{\numberline {344}My brackets don't match}{129}} -\newlabel{Q-matchbrak}{{344}{129}} -\@writefile{toc}{\contentsline {subsection}{\numberline {U.2}Common misunderstandings}{129}} -\@writefile{toc}{\contentsline {question}{\numberline {345}What's going on in my \csx {include} commands?}{129}} -\newlabel{Q-include}{{345}{129}} -\@writefile{toc}{\contentsline {question}{\numberline {346}Why does it ignore paragraph parameters?}{129}} -\newlabel{Q-paraparam}{{346}{129}} -\@writefile{toc}{\contentsline {question}{\numberline {347}Case-changing oddities}{130}} -\newlabel{Q-casechange}{{347}{130}} -\@writefile{toc}{\contentsline {question}{\numberline {348}Why does La\TeX {} split footnotes across pages?}{130}} -\newlabel{Q-splitfoot}{{348}{130}} -\@writefile{toc}{\contentsline {question}{\numberline {349}Getting \csx {marginpar} on the right side}{130}} -\newlabel{Q-marginparside}{{349}{130}} -\@writefile{toc}{\contentsline {question}{\numberline {350}Where have my characters gone?}{131}} -\newlabel{Q-misschar}{{350}{131}} -\@writefile{toc}{\contentsline {question}{\numberline {351}``Rerun'' messages won't go away}{131}} -\newlabel{Q-rerun}{{351}{131}} -\@writefile{toc}{\contentsline {question}{\numberline {352}Commands gobble following space}{131}} -\newlabel{Q-xspace}{{352}{131}} -\@writefile{toc}{\contentsline {question}{\numberline {353}(La)\TeX {} makes overfull lines}{131}} -\newlabel{Q-overfull}{{353}{131}} -\@writefile{toc}{\contentsline {question}{\numberline {354}Maths symbols don't scale up}{132}} -\newlabel{Q-exscale}{{354}{132}} -\@writefile{toc}{\contentsline {question}{\numberline {355}Why doesn't \csx {linespread} work?}{133}} -\newlabel{Q-linespread}{{355}{133}} -\@writefile{toc}{\contentsline {question}{\numberline {356}Only one \csx {baselineskip} per paragraph}{133}} -\newlabel{Q-baselinepar}{{356}{133}} -\@writefile{toc}{\contentsline {question}{\numberline {357}Numbers too large in table of contents, etc.}{133}} -\newlabel{Q-tocloftwrong}{{357}{133}} -\@writefile{toc}{\contentsline {question}{\numberline {358}Why is the inside margin so narrow?}{133}} -\newlabel{Q-gutter}{{358}{133}} -\@writefile{toc}{\contentsline {subsection}{\numberline {U.3}Why shouldn't I?}{134}} -\@writefile{toc}{\contentsline {question}{\numberline {359}Why use \ProgName {fontenc} rather than \ProgName {t1enc}?}{134}} -\newlabel{Q-t1enc}{{359}{134}} -\@writefile{toc}{\contentsline {question}{\numberline {360}Why bother with \ProgName {inputenc} and \ProgName {fontenc}?}{134}} -\newlabel{Q-why-inp-font}{{360}{134}} -\@writefile{toc}{\contentsline {question}{\numberline {361}Why not use \texttt {eqnarray}?}{134}} -\newlabel{Q-eqnarray}{{361}{134}} -\@writefile{toc}{\contentsline {question}{\numberline {362}Why use \csx {[}\,\dots {}\csx {]} in place of \texttt {\$\$}\,\dots {}\texttt {\$\$}?}{134}} -\newlabel{Q-dolldoll}{{362}{134}} -\@writefile{toc}{\contentsline {question}{\numberline {363}What's wrong with \csx {bf}, \csx {it}, etc.?}{135}} -\newlabel{Q-2letterfontcmd}{{363}{135}} -\@writefile{toc}{\contentsline {question}{\numberline {364}What's wrong with \csx {newfont}?}{135}} -\newlabel{Q-newfont}{{364}{135}} -\@writefile{toc}{\contentsline {section}{\numberline {V}The joy of \TeX {} errors}{136}} -\@writefile{toc}{\contentsline {question}{\numberline {365}How to approach errors}{136}} -\newlabel{Q-erroradvice}{{365}{136}} -\@writefile{toc}{\contentsline {question}{\numberline {366}The structure of \TeX {} error messages}{136}} -\newlabel{Q-errstruct}{{366}{136}} -\@writefile{toc}{\contentsline {question}{\numberline {367}An extra `\texttt {\char 125\relax {}}'??}{137}} -\newlabel{Q-extrabrace}{{367}{137}} -\@writefile{toc}{\contentsline {question}{\numberline {368}Capacity exceeded [semantic nest\,\dots {}]}{137}} -\newlabel{Q-semanticnest}{{368}{137}} -\@writefile{toc}{\contentsline {question}{\numberline {369}No room for a new `\emph {thing}'}{137}} -\newlabel{Q-noroom}{{369}{137}} -\@writefile{toc}{\contentsline {question}{\numberline {370}\texttt {epsf} gives up after a bit}{138}} -\newlabel{Q-epsf}{{370}{138}} -\@writefile{toc}{\contentsline {question}{\numberline {371}Improper \csx {hyphenation} will be flushed}{138}} -\newlabel{Q-badhyph}{{371}{138}} -\@writefile{toc}{\contentsline {question}{\numberline {372}``Too many unprocessed floats''}{138}} -\newlabel{Q-tmupfl}{{372}{138}} -\@writefile{toc}{\contentsline {question}{\numberline {373}\csx {spacefactor} complaints}{138}} -\newlabel{Q-atvert}{{373}{138}} -\@writefile{toc}{\contentsline {question}{\numberline {374}\csx {end} occurred inside a group}{139}} -\newlabel{Q-endingroup}{{374}{139}} -\@writefile{toc}{\contentsline {question}{\numberline {375}``Missing number, treated as zero''}{139}} -\newlabel{Q-nonum}{{375}{139}} -\@writefile{toc}{\contentsline {question}{\numberline {376}``Please type a command or say \csx {end}''}{139}} -\newlabel{Q-typend}{{376}{139}} -\@writefile{toc}{\contentsline {question}{\numberline {377}``Unknown graphics extension''}{140}} -\newlabel{Q-unkgrfextn}{{377}{140}} -\@writefile{toc}{\contentsline {question}{\numberline {378}``Missing \texttt {\$} inserted''}{140}} -\newlabel{Q-nodollar}{{378}{140}} -\@writefile{toc}{\contentsline {question}{\numberline {379}Warning: ``Font shape \dots {}\ not available''}{140}} -\newlabel{Q-fontunavail}{{379}{140}} -\@writefile{toc}{\contentsline {question}{\numberline {380}Unable to read an entire line}{141}} -\newlabel{Q-buffovl}{{380}{141}} -\@writefile{toc}{\contentsline {question}{\numberline {381}``Fatal format file error; I'm stymied''}{141}} -\newlabel{Q-formatstymy}{{381}{141}} -\@writefile{toc}{\contentsline {question}{\numberline {382}Non-\acro {PDF} special ignored!}{141}} -\newlabel{Q-nonpdfsp}{{382}{141}} -\@writefile{toc}{\contentsline {question}{\numberline {383}Mismatched mode ljfour and resolution 8000}{142}} -\newlabel{Q-8000}{{383}{142}} -\@writefile{toc}{\contentsline {question}{\numberline {384}``Too deeply nested''}{142}} -\newlabel{Q-toodeep}{{384}{142}} -\@writefile{toc}{\contentsline {question}{\numberline {385}Capacity exceeded\nobreakspace {}--- input levels}{142}} -\newlabel{Q-inputlev}{{385}{142}} -\@writefile{toc}{\contentsline {question}{\numberline {386}PDF\TeX {} destination \dots {} ignored}{142}} -\newlabel{Q-hyperdupdest}{{386}{142}} -\@writefile{toc}{\contentsline {question}{\numberline {387}Alignment tab changed to \csx {cr}}{143}} -\newlabel{Q-altabcr}{{387}{143}} -\@writefile{toc}{\contentsline {question}{\numberline {388}Graphics division by zero}{143}} -\newlabel{Q-divzero}{{388}{143}} -\@writefile{toc}{\contentsline {question}{\numberline {389}Missing \csx {begin}\texttt {\char 123\relax {document}\char 125\relax }}{143}} -\newlabel{Q-missbegdoc}{{389}{143}} -\@writefile{toc}{\contentsline {question}{\numberline {390}\csx {normalsize} not defined}{143}} -\newlabel{Q-normalszmiss}{{390}{143}} -\@writefile{toc}{\contentsline {question}{\numberline {391}Too many math alphabets}{144}} -\newlabel{Q-manymathalph}{{391}{144}} -\@writefile{toc}{\contentsline {question}{\numberline {392}Not in outer par mode}{144}} -\newlabel{Q-ouparmd}{{392}{144}} -\@writefile{toc}{\contentsline {question}{\numberline {393}Perhaps a missing \csx {item}?}{144}} -\newlabel{Q-errmissitem}{{393}{144}} -\@writefile{toc}{\contentsline {question}{\numberline {394}Illegal parameter number in definition}{145}} -\newlabel{Q-errparnum}{{394}{145}} -\@writefile{toc}{\contentsline {question}{\numberline {395}Float(s) lost}{145}} -\newlabel{Q-fllost}{{395}{145}} -\@writefile{toc}{\contentsline {question}{\numberline {396}Option clash for package}{145}} -\newlabel{Q-optionclash}{{396}{145}} -\@writefile{toc}{\contentsline {section}{\numberline {W}Current \TeX {}-related projects}{146}} -\@writefile{toc}{\contentsline {question}{\numberline {397}The La\TeX {}3 project}{146}} -\newlabel{Q-LaTeX3}{{397}{146}} -\@writefile{toc}{\contentsline {question}{\numberline {398}Future \acro {WWW} technologies and (La)\TeX {}}{146}} -\newlabel{Q-mathml}{{398}{146}} -\@writefile{toc}{\contentsline {question}{\numberline {399}Making outline fonts from \MF {}}{147}} -\newlabel{Q-textrace}{{399}{147}} -\@writefile{toc}{\contentsline {question}{\numberline {400}The \TeX {} document preparation environment}{147}} -\newlabel{Q-WYGexpts}{{400}{147}} -\@writefile{toc}{\contentsline {question}{\numberline {401}The \textsf {ANT} typesetting system}{148}} -\newlabel{Q-ant}{{401}{148}} -\@writefile{toc}{\contentsline {question}{\numberline {402}The Ex\TeX {} project}{148}} -\newlabel{Q-extex}{{402}{148}} -\@writefile{toc}{\contentsline {question}{\numberline {403}Omega and Aleph}{148}} -\newlabel{Q-omegaleph}{{403}{148}} -\@writefile{toc}{\contentsline {question}{\numberline {404}PDF\TeX {} becomes \acro {LUA}\TeX {}}{148}} -\newlabel{Q-luatex}{{404}{148}} -\@writefile{toc}{\contentsline {question}{\numberline {405}The XeTeX project}{149}} -\newlabel{Q-xetex}{{405}{149}} -\@writefile{toc}{\contentsline {section}{\numberline {X}You're still stuck?}{149}} -\@writefile{toc}{\contentsline {question}{\numberline {406}You don't understand the answer}{149}} -\newlabel{Q-noans}{{406}{149}} -\@writefile{toc}{\contentsline {question}{\numberline {407}Submitting new material for the \acro {FAQ}}{149}} -\newlabel{Q-newans}{{407}{149}} -\@writefile{toc}{\contentsline {question}{\numberline {408}Reporting a La\TeX {} bug}{149}} -\newlabel{Q-latexbug}{{408}{149}} -\@writefile{toc}{\contentsline {question}{\numberline {409}What to do if you find a bug}{150}} -\newlabel{Q-bug}{{409}{150}} -\newlabel{lastquestion}{{409}{150}} diff --git a/Master/texmf-doc/doc/english/FAQ-en/newfaq.pdf b/Master/texmf-doc/doc/english/FAQ-en/newfaq.pdf Binary files differdeleted file mode 100644 index 54cab85bacb..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/newfaq.pdf +++ /dev/null diff --git a/Master/texmf-doc/doc/english/FAQ-en/sanitize.pl b/Master/texmf-doc/doc/english/FAQ-en/sanitize.pl deleted file mode 100644 index 7a2ed1ccf82..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/sanitize.pl +++ /dev/null @@ -1,195 +0,0 @@ -# $Id: sanitize.pl,v 1.11 2003/06/20 10:51:44 rf Exp rf $ - -# provides the sanitize_line function used by all texfaq2* files -# -# will not compile standing alone - -# Convert a LaTeX line to HTML: - -sub sanitize_line { - s"\&"\&\;"g; - s"\<"\<\;"g; - s"\>"\>\;"g; - if ($converting && !$ignoring) { - s"\\vspace\*\{[^\}]*\}""g; - s"``"\""g; - s"''"\""g; - s"^\s*$"<p>"; - s"\%.*""; - s"\\obracesymbol\{\}"\&lbrace\;"g; - s"\\cbracesymbol\{\}"\&rbrace\;"g; - s"\\\{"\&lbrace\;"g; - s"\\\}"\&rbrace\;"g; - s"\\ae\{\}"\æ\;"g; - s"\\AllTeX\{\}"(La)TeX"g; - s"\\twee\{\}"2e"g; - s"\\LaTeXe\{\}"LaTeX2e"g; - s"\\LaTeXo\{\}"LaTeX 2.09"g; - s"\\MF\{\}"Metafont"g; - s"\\MP\{\}"MetaPost"g; - s"\\BV\{\}"<i>Baskerville</i>"g; - s"\\TUGboat\{\}"<i>TUGboat</i>"g; - s"\\PDFTeX\{\}"PDFTeX"g; - s"\\PDFLaTeX\{\}"PDFLaTeX"g; - s"\\CONTeXT\{\}"ConTeXt"g; - s"\\NTS\{\}"<i>NTS</i>"g; - s"\\eTeX\{\}"e-TeX"g; - s"\\Eplain\{\}"Eplain"g; - s"\\TeXsis\{\}"TeXsis"g; - s"\\YandY\{\}"Y&Y"g; - s"\\WYSIWYG\{\}"WYSIWYG"g; - s"\\PS\{\}"PostScript"g; - s"\\dots\{\}"..."g; - s"\\ldots\{\}"..."g; - s"\\large""g; - s"\\pounds\{\}"£"g; - s"\\arrowhyph\{\}"-> "g; - s"\\protect""g; - s"\-\-\-"\-"g; - s"\-\-"\-"g; - s"\\(\w+)\{\}"$1"g; - s"\\\"a"\ä\;"g; - s"\\\"o"\ö\;"g; - s"\\\'e"\é\;"g; - s"\\\^e"\ê\;"g; - s"\\\'o"\ó\;"g; - s"\\ss"\ß\;"g; - s"`"'"g; - s"\\label\{[^\}]*\}""g; - s"\\acro\{([^\}]*)\}"$1"g; - s"\\ensuremath\{([^\}]*)\}"$1"g; - s"\\emph\{([^\}]*)\}"<em>$1</em>"g; - s"\\textit\{([^\}]*)\}"<em>$1</em>"g; - s"\\textsl\{([^\}]*)\}"<em>$1</em>"g; - s"\\meta\{([^\}]*)\}"<\;<em>$1</em>>\;"g; - s"\\texttt\{([^\}]*)\}"<code>$1</code>"g; - s"\\textbf\{([^\}]*)\}"<b>$1</b>"g; - s"\\csx\{([^\}]*)\}"<code>\\$1</code>"g; - s"\\parens\{([^\}]*)\}"$1"g; - s"\\oparen\{\}""g; - s"\\cparen\{\}""g; - s"\~"\\textasciitilde{}"g if s"\\href\{([^\}]*)\}\{([^\}]*)\}"<a href=\"$1\">$2</a>"; - s"\\Q\{([^\}]*)\}""g; - s"\\checked\{([^\}]*)\}\{([^\}]*)\}""g; - s"\\footnote\{([^\}]*)\}""g; - s"\\thinspace\{\}" "g; - s"\\section\{([^\}]*)\}""g; - s"\\subsection\{([^\}]*)\}""g; - s"\$\\pi\$"<i>pi</i>"g; - s"\$([^\$]*)\$"<i>$1</i>"g; - s"\\ISBN\{([^\}]*)\}"ISBN $1"g; - s"\\ProgName\|([^\|]*)\|"<i>$1</i>"g; - s"\\ProgName\{([^\}]*)\}"<i>$1</i>"g; - s"\\FontName\|([^\|]*)\|"<i>$1</i>"g; - s"\\FontName\{([^\}]*)\}"<i>$1</i>"g; - s"\\Package\|([^\|]*)\|"<i>$1</i>"g; - s"\\Package\{([^\}]*)\}"<i>$1</i>"g; - s"\\Class\|([^\|]*)\|"<i>$1</i>"g; - s"\\Class\{([^\}]*)\}"<i>$1</i>"g; - s"\\Email\|([^\|]*)\|"<i>$1</i>"g; - s"\\mailto\|([^\|]*)\|"<a href\=\"mailto:$1\"><i>$1</i></a>"g; - s"\\File\|([^\|]*)\|"<i>$1</i>"g; - s"\\Newsgroup\|([^\|]*)\|"<i>$1</i>"g; - s"\~"\\textasciitilde{}"g if s"\\URL\{([^\}]*)\}"\<a href\=\"$1\"\>$1\<\/a\>"g; - s"\\FTP\|([^\|]*)\|"\<a href\=\"ftp\:\/\/$1\/\"\>$1\<\/a\>"g; - s"\\CTAN\{([^\|]*)\}"\<a href\=\"ftp\://$arch/$root/$1\/\"\>$1\<\/a\>"g; - s"\\Qref\[([^\]]*)\]\{([^\}]*)\}\{([^\}]*)\}"<a href\=\"$qref{$3}\">$2</a>"g; - s"\\Qref\{([^\}]*)\}\{([^\}]*)\}"<a href\=\"$qref{$2}\">$1</a>"g; - s"\\cmdinvoke\{([^\}]*)\}\{([^\}]*)\}\{([^\}]*)\}\{([^\}]*)\}\{([^\}]*)\}"<code>\\$1\{$2\}\{$3\}\{$4\}\{$5\}</code>"g; - s"\\cmdinvoke\{([^\}]*)\}\[([^\]]*)\]\{([^\}]*)\}"<code>\\$1\[$2\]\{$3\}</code>"g; - s"\\cmdinvoke\{([^\}]*)\}\{([^\}]*)\}\[([^\]]*)\]"<code>\\$1\{$2\}\[$3\]</code>"g; - s"\\cmdinvoke\{([^\}]*)\}\{([^\}]*)\}\{([^\}]*)\}"<code>\\$1\{$2\}\{$3\}</code>"g; - s"\\cmdinvoke\{([^\}]*)\}\{([^\}]*)\}"<code>\\$1\{$2\}</code>"g; - s"\\cmdinvoke\{([^\}]*)\}\[([^\]]*)\]"<code>\\$1\[$2\]</code>"g; - s"\\cmdinvoke\*\{([^\}]*)\}\{([^\}]*)\}\{([^\}]*)\}"<code>\\$1\{</code><em>$2</em><code>\}\{</code><em>$3</em><code>\}</code>"g; - s"\\environment\{([^\}]*)\}"<code>$1</code>"g; - s"\\pkgoption\{([^\}]*)\}"<code>$1</code>"g; - s"\\path\|([^\|]*)\|"<i>$1</i>"g; - s"\\begin\{htmlversion\}.*\n""g; - s"\\end\{htmlversion\}.*\n""g; - s"\\begin\{quote\}"<blockquote>"g; - s"\\end\{quote\}"</blockquote>"g; - s"\\begin\{description\}"<dl>"g; - s"\\end\{description\}"</dl>"g; - s"\\begin\{booklist\}"<dl>"g; - s"\\end\{booklist\}"</dl>"g; - s"\\begin\{proglist\}"<dl>"g; - s"\\end\{proglist\}"</dl>"g; - s"\\begin\{itemize\}"<ul>"g; - s"\\end\{itemize\}"</ul>"g; - s"\\begin\{enumerate\}"<ol>"g; - s"\\end\{enumerate\}"</ol>"g; - s"\\item\s*\[\\normalfont\{\}([^\]]*)\]"<dt>$1<dd>"g; - s"\\item\s*\[([^\]]*)\]"<dt>$itemset$1$enditemset<dd>"g; - s"\\item"<li>"g; - s"\\\\(\[[^\]]*\])?"<br>"g; - s"\|([^\|]+)\|"<code>$1</code>"g; - s"\\\_"\_"g; - s"\\textpercent"\%"g; # can't have \% in source... - s"\\\$"\$"g; - s"\\\#"\#"g; - s"\\ " "g; - s"\\\&"\&"g; - s"\\\@""g; - s"\\\;" "g; - s"\\\," "g; - s"\~" "g; - s"\\nobreakspace" "g; - s"\\textasciitilde"\~"g; - s"\\textbar"\|"g; - s"\\cs\<code\>"<code>\\"g; - s"\&lbrace\;"\{"; - s"\&rbrace\;"\}"; - s"\\symbol\{([^\}]*)\}"$SymbolChar{$1}"g; - s"\{\}""g; - s"\\keywords\{([^\}]*)\}"<!-- $1 -->"g; - s"\\relax""g; - - s"\\hphantom\{[^\}]*\}""g; - s"\\nothtml\{[^\}]*\}""g; - s"\\latexhtml\{[^\}]*\}\{([^\}]*)\}"$1"g; - s"\\htmlonly\{([^\}]*)\}"$1"g; - } - if ( s"\\begin\{ctanrefs\}"<dl>"g ) { - $itemset = "<tt><i>"; - $enditemset = "</i></tt>"; - } - if ( s"\\end\{ctanrefs\}"</dl>"g ) { - $itemset = ""; - $enditemset = ""; - } - - while ( /\\CTANref\{([^\}]*)\}/ ) { - my $repl=generate_CTAN_ref("$1"); - s/\\CTANref\{([^\}]*)\}/$repl/; - } - - $converting = 0 if s"\\begin\{verbatim\}"<pre>"g; - $converting = 1 if s"\\end\{verbatim\}"</pre>"g; - $ignoring++ if s"\\htmlignore""g; - $ignoring-- if s"\\endhtmlignore""g; - $ignoring++ if s"\\begin\{comment\}""g; - $ignoring-- if s"\\end\{comment\}""g; - $ignoring++ if s"\\begin\{footnoteenv\}""g; - $ignoring-- if s"\\end\{footnoteenv\}""g; - $_ = "" if $ignoring; -} - -sub generate_CTAN_ref { - if ( $ctanref_plus{$1} > 0 ) { - $ret = "\<a href\=\"$proto_1://$arch_root$ctanref{$1}"; - $ret .= "$fmt_1\"\>$ctanref{$1}\<\/a\>"; - $ret .= " (\<a href\=\"$proto_2://$arch_root$ctanref{$1}$fmt_2\"\>$fmt_2_name\<\/a\>"; - $ret .= ", \<a href\=\"$proto_3://$host_d/$this_root/$ctanref{$1}$fmt_3\"\>$fmt_3_name\<\/a\>)"; - } elsif ( $ctanref_plus{$1} = 0 ) { - $ret = "\<a href\=\"$proto_d://$host_d/$this_root/$ctanref{$1}\"\>" . - "$ctanref{$1}\<\/a\>"; - } else { - $ret = "\<a href\=\"$proto_f://$arch_root$ctanref{$1}\"\>" . - "$ctanref{$1}\<\/a\>"; - } - - $ret; -} - -1; diff --git a/Master/texmf-doc/doc/english/FAQ-en/stupid_names.sty b/Master/texmf-doc/doc/english/FAQ-en/stupid_names.sty deleted file mode 100644 index c3cad7a0249..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/stupid_names.sty +++ /dev/null @@ -1,225 +0,0 @@ -% a package derived from nelson beebe's texnames.sty; the name -% -\ProvidesPackage{stupid_names}[2004/02/26 v0.00001] -% -% This has a chance of working in different styles and sizes, although -% it's not perfect. If \sc actually selects a caps-and-small caps font, -% we want to use lowercase letters (to get the small caps). But if \sc -% selects a smaller point size, we want to use uppercase letters. -% \uppercasesc is called on every letter we typeset in \sc, so both -% forms can be accommodated. -\ifx\sc\undefined - \def\sc{% - % If there is no \scriptfont for the current family, use a fixed - % font. What more can we do? - \expandafter\ifx\the\scriptfont\fam\nullfont - \font\temp = cmr7 \temp - \else - \the\scriptfont\fam - \fi - \def\uppercasesc{\char\uccode`}% - }% -\fi -\ifx\uppercasesc\undefined - \let\uppercasesc = \relax -\fi -% -% In the following, we first give the ``official'' definition, -% then follow it with spelling variants. Alternate definitions -% are discarded in favor of the official one. Each family is -% separated by a line like the following one. -% -%======================================================================= -% -% Only change from plain.tex is the \spacefactor assignment (suggested -% by Phil Taylor), so that \TeX at the end of a sentence isn't treated -% as an abbreviation. -% -\def\TeX{T\kern-.1667em\lower.5ex\hbox{E}\kern-.125emX\spacefactor1000 }% -% -%======================================================================= -% From the AMS tex/ams/amslatex/fontsel/nfssinst.tex file: -% hacked by RF 1994/03/31 -\ifx\mathcal\undefined - \def\mathcal#1{{\cal #1}} -\fi -\ifx\AmS\undefined - \def\AmS{$\mathcal{A}$\kern-.1667em\lower.5ex\hbox - {$\mathcal{M}$}\kern-.125em$\mathcal{S}$} -\fi -\ifx\AMS\undefined \let\AMS=\AmS \fi -\ifx\AmSLaTeX\undefined - \def\AmSLaTeX{\AmS-\LaTeX} -\fi -\ifx\AMSLaTeX\undefined \let\AMSLaTeX=\AmSLaTeX \fi -%======================================================================= -% -% Mike Spivak's amstex/amstex.tex 1.1d [26-Aug-1988] has -% \def\AmSTeX{{\textfontii A}\kern-.1667em\lower.5ex\hbox -% {\textfontii M}\kern-.125em{\textfontii S}-\TeX} -% and 2.1 [05-Apr-1991] has an equivalent definition. -% AmSTeX's \textfontii is exactly the same as \cal, which -% all TeX variants understand. -% -\ifx\AmSTeX\undefined - \def\AmSTeX{\AmS-\TeX}% -\fi -% -% Leslie Lamport's latex/tmanual.tex [10-Jul-1984] (an early -% draft of the book) defines it in uppercase with the standard -% definition. -\ifx\AMSTEX\undefined \let\AMSTEX=\AmSTeX \fi -% -% Barbara Beeton's latex/deproc.sty [24-Apr-1986] and inputs/tugbot.sty -% [11-Jan-1988] uses this spelling, but the definition -% \leavevmode\hbox{$\mathcal{A}\kern-.2em\lower.376ex \hbox{$\mathcal{ -% M}$}\kern-.2em\mathcal{S}$-\TeX} -\ifx\AMSTeX\undefined \let\AMSTeX=\AmSTeX \fi -% -%======================================================================= -% -% The definitions of \BibTeX and \SLiTeX in Leslie Lamport's -% latex/local.tex lower the E by 0.7ex, while \TeX in plain.tex lowers -% it by 0.5ex. Oren Patashnik's bibtex/btxdoc.tex and bibtex/btxhak.tex -% [08-Feb-1988] and bibtex/bibtex.web 0.99c [xx-Feb-1988] use this same -% name and definition, but Oren said using \TeX here is ok. (Curiously, -% LaTeX itself does not define macros for any TeXware except LaTeX and -% TeX!) -\ifx\BibTeX\undefined - \ifx\textsc\undefined - \def\BibTeX{B{\sc \uppercasesc i\kern-.025em \uppercasesc b}\kern-.08em - \TeX}% - \else - \def\BibTeX{\textsc{Bib}\kern-.08em - \TeX}% - \fi -\fi -% -% Leslie Lamport uses this spelling in latex.tex, but not as a -% macro. We include it for consistency with AMSTeX. -\ifx\BIBTeX\undefined \let\BIBTeX=\BibTeX \fi -% -% Leslie Lamport's latex/slides.tex [05-Jun-1984], -% latex/tmanual.tex [10-Jul-1984] (an early draft of the book), -% and latex/lerrata.tex [23-Jul-1985] have this spelling, but the -% definition BIB\kern-.1em\TeX. -\ifx\BIBTEX\undefined \let\BIBTEX=\BibTeX \fi -% -%======================================================================= -% -% From tugboat.com 1.08 [24-Oct-1990]. -\ifx\LAMSTeX\undefined - \def\LAMSTeX{L\raise.42ex\hbox{\kern-.3em\the\scriptfont2 A}% - \kern-.2em\lower.376ex\hbox{\the\textfont2 M}% - \kern-.125em {\the\textfont2 S}-\TeX}% -\fi -% -\ifx\LamSTeX\undefined \let\LamSTeX=\LAMSTeX \fi -% -% This variant seems likely to appear: -\ifx\LAmSTeX\undefined \let\LAmSTeX=\LAMSTeX \fi -% -%======================================================================= -% -% The definition from latex.tex (LATEX VERSION 2.09 <14 January 1991>) -% and bibtex.web 0.99c [xx-Feb-1988] lowers the E slightly more than -% \TeX, but consistency seems more desirable. See comments at \BibTeX. -% Different definitions are given by latex/deproc.sty [24-Apr-1986], -% amstex/man.sty [15-Dec-1986] inputs/tugbot.sty [11-Jan-1988], and -% latex/tugboat.com 1.08 [24-Oct-1990]. -% -% note: this definition doesn't have a variant based on \textsc, since -% anything that's LaTeX2e-compatible ought to have it anyway... -% -\ifx\LaTeX\undefined - \def\LaTeX{L\kern-.36em\raise.3ex\hbox{\sc \uppercasesc a}\kern-.15em\TeX}% -\fi -% -% latex/slides.tex [05-Jun-1984] and latex/lerrata.tex [23-Jul-1985] -% have this spelling, but different definitions -\ifx\LATEX\undefined \let\LATEX=\LaTeX \fi -% -% LaTeX 2e `standard' logo (euuccchhhh!) -\ifx\LaTeXe\undefined - \def\LaTeXe{\LaTeX\kern.15em 2${}_{\textstyle\varepsilon}$} -\fi -% -% and a corresponding thing for LaTeX _explicitly_ 2.09 -% -\ifx\LaTeXo\undefined - \def\LaTeXo{\LaTeX\kern.15em 2.09} -\fi -% -%======================================================================= -% -% Don Knuth's mf.web 2.7 [xx-Sep-1990] and Barbara Beeton's -% latex/deproc.sty [24-Apr-1986] use an equivalent of this definition. -% The font is variously named \logo, \manfnt, and \mf. plain.tex -% preloads \manfnt. manfnt has the letters A, E, F, M, N, O, T in -% various sizes plus extra symbols for Don Knuth's books Computers and -% Typesetting, and Concrete Mathematics, while logo10 has only those -% letters in one size. AmSTeX uses \logo in amsppt.sty and imappt.sty, -% so we should avoid it, and tugboat.com uses \mf for {\smc Metafont}. -% We therefore use \manfnt here, defining it if necessary. QUESTION: -% should we use manfnt, or logo10? -\ifx\MF\undefined - \ifx\manfnt\undefined - \font\manfnt=logo10 - \fi - \ifx\manfntsl\undefined - \font\manfntsl=logosl10 - \fi - \def\MF{{\ifdim\fontdimen1\font>0pt \let\manfnt = \manfntsl \fi - {\manfnt META}\-{\manfnt FONT}}\spacefactor1000 }% -\fi -% -% I cannot find any `official' uses of this alternate, but it -% seems likely that people will use it. -\ifx\METAFONT\undefined \let\METAFONT=\MF \fi -% -%======================================================================= -% -% Leslie Lamport's latex/slides.tex [05-Jun-1984]. His -% latex/lerrata.tex [23-Jul-1985] and latex/tmanual.tex -% [10-Jul-1984] (an early draft of the book) define it as -% SLI\TeX! The LaTeX User's Guide and Reference Manual (1986) -% appears to use small caps, and possibly kerning, for Sli. -% I need to ask Leslie to suggest a preferred definition. -\ifx\SLITEX\undefined - \ifx\textsc\undefined - \def\SLITEX{S\kern-.065em L\kern-.18em\raise.32ex\hbox{\textsc{i}}% - \kern-.03em\TeX}% - \else - \def\SLITEX{S\kern-.065em L\kern-.18em\raise.32ex\hbox{i}% - \kern-.03em\TeX}% - \fi -\fi -% -% latex/local.tex (sample Local Guide) [27-Oct-1988] uses -% this name, but defines it as -% {\rm S\kern-.06em{\sc l\kern-.035emi}\kern-.06em T\kern -% -.1667em\lower.7ex\hbox{E}\kern-.125emX} -% with an extra-low E, and kerned Sli in small caps. Is this -% what the LaTeX User's Guide and Reference Manual (1986) used? -\ifx\SLiTeX\undefined \let\SLiTeX=\SLITEX \fi -% -% latex/slitex.tex [08-Jun-1988] uses SliTeX in typeouts, -% but not as a macro -- what a way to confuse the user. -\ifx\SliTeX\undefined \let\SliTeX=\SLITEX \fi -% -% I cannot find a use of this one, but it seems a likely -% candidate anyway, and is consistent with AMSTeX and BIBTeX. -\ifx\SLITeX\undefined \let\SLITeX=\SLITEX \fi -% -%======================================================================= -% -% from pictex.tex: -\ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi -\ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi -% -% from fantasy-land: -\ifx\VorTeX\undefined \def\VorTeX{V\kern-2.7pt\lower.5ex\hbox{O\kern-1.4pt R}% - \kern-2.6ptT\kern-.1667em\lower.5ex\hbox{E}\kern-.125emX} \fi -% -\endinput -%=========================[End of texnames.sty]========================= diff --git a/Master/texmf-doc/doc/english/FAQ-en/texfaq2file b/Master/texmf-doc/doc/english/FAQ-en/texfaq2file deleted file mode 100644 index af50d6fdffc..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/texfaq2file +++ /dev/null @@ -1,297 +0,0 @@ -#!/usr/bin/perl -# -# ======================================================================== -# @perl-file{ -# author = "Alan Jeffrey", -# version = "0.19", -# date = "15 January 1996", -# time = "12:26:55 GMT", -# filename = "texfaq2html", -# address = "School of Cognitive and Computing Sciences -# University of Sussex -# Brighton BN1 9QH -# UK", -# FAX = "+44 1273 671320" -# email = "alanje@cogs.sussex.ac.uk", -# codetable = "ISO/ASCII", -# keywords = "LaTeX FAQ HTML", -# supported = "yes", -# abstract = "This perl script converts the UKTUG TeX FAQ -# LaTeX source document into HTML, on the fly." -# package = "stands alone", -# dependencies = "faqbody.tex, newfaq.aux, dirctan.tex, -# filectan,tex", -# } -# ======================================================================== - -# A script to provide a searchable WWW interface to the the UKTUG TeX -# FAQ file. -# -# The script takes parameters in the form of the QUERY_STRING environment -# variable. - -# Copyright 1994 Alan Jeffrey -# Maintenance, since 1997, Robin Fairbairns - -require "sanitize.pl"; - -# The site-specific stuff: - -$default_web = "www.tex.ac.uk"; -$href_script="http://$default_web/cgi-bin/texfaq2html"; -$home = "$ENV{FAQ_HOME}" || "/home/rf/tex/faq"; -$texfaq = "faqbody.tex"; -$auxfaq = "newfaq.aux"; -$ctandir = "dirctan.tex"; -$ctanfiles = "filectan.tex"; -$archive_list = "archive.list"; - -# derived: - -$faqhtml = $home . "/html"; - -# defaults; these have to be allowed by the $archive_list file - -$default_archive = "cam.ctan.org"; -$fmt_1 = ".tar.gz"; -$fmt_2 = ".zip"; -$fmt_2_name = "zip"; -$fmt_3 = "/"; -$fmt_3_name = "browse"; - -# protocols for transferring files, browsing directories -$proto_f = "ftp"; -$host_f = $default_archive; -$proto_d = "http"; -$host_d = $default_web; - -$proto_1 = $proto_2 = $proto_f; -$host_1 = $host_2 = $host_f; -$proto_3 = $proto_d; -$host_3 = $host_d; - -# table of symbols we believe in -%SymbolChar = ( - 92 => "\\", - 123 => "\{", - 125 => "\}" -); - -# This script produces HTML, but we're sending the stuff to file -# so we needn't tell anyone -# -# print ("Content-type: text/html\n\n"); - -# By default, we convert LaTeX to HTML. - -$converting = 1; -$ignoring = 0; -$sectioning = 0; - -# two things used in conversion of \item[ ] - -$itemset = ""; -$enditemset = ""; - -# Get the list of CTAN directories: - -open (CTANDIR, "$home/$ctandir") - || &oh_dear ("Couldn't open $ctandir"); - -while (<CTANDIR>) { - if ( /\\CTANdirectory\{([^\}]*)\}\{([^\}]*)\}/ ) { - $ctanref{$1} = "$2"; - $ctanref_plus{$1} = 1; - } elsif ( /\\CTANdirectory\*\{([^\}]*)\}\{([^\}]*)\}/ ) { - $ctanref{$1} = "$2/"; - $ctanref_plus{$1} = 0; - } -} - -# Get the list of CTAN files - -open (CTANFILES, "$home/$ctanfiles") - || &oh_dear ("Couldn't open $ctanfiles"); - -while (<CTANFILES>) { - - if ( /\\CTANfile\{([^\}]*)\}\{([^\}]*)\}/ ) { - $ctanref{$1} = "$2"; - $ctanref_plus{$1} = -1; - } -} - -# Get the list of allowable archives - -open (ARCHIVE_LIST, "$home/$archive_list") - || &oh_dear ("Couldn't open $archive_list"); - -while (<ARCHIVE_LIST>) { - chop; - ($archive, $root_dir) = split(/\s+/, $_, 2); - $archive_root{$archive} = $root_dir; -} -unless ( $this_root = $archive_root{$default_archive} ) { - &oh_dear("Archive $default_archive isn't in my list") } -$arch_root = "$default_archive/$this_root/"; - -# Get the Qrefs: - -open (AUXFAQ, "$home/$auxfaq") - || &oh_dear ("Couldn't open $auxfaq"); - - -while (<AUXFAQ>) { - if (/\\newlabel\{([^\}]*)\}\{\{([^\}]*)\}/) { - next if ( !( ($this_Qlabel = $1) =~ /^Q-/ ) ); - $this_label = substr $this_Qlabel, 1; - $qref{$this_Qlabel} = "FAQ$this_label.html"; - } -} - -# Open the FAQ file: - -open (TEXFAQ, "$home/$texfaq") - || &oh_dear ("Couldn't open $texfaq"); - -# Run through to the introduction, grabbing useful info. - -while (<TEXFAQ>) { - last if /\\section\{Introduction\}/; - $fileversion=$1 if /\\def\\faqfileversion\{([^\}]*)\}/; - $filedate=$1 if /\\def\\faqfiledate\{([^\}]*)\}/; -} - -# open main html file - -open (FAQ, ">$faqhtml/index.html") || - oh_dear ("couldn't open output file $faqhtml/index.html"); - -printf FAQ (" -<html><head> -<title>TeX Frequently Asked Questions</title> -</head><body> -<h1 align=\"center\">Welcome to the UK List of<br> - TeX Frequently Asked Questions</h1> -"); - -# Blast out the introduction until we get to the first section. - -print FAQ "<h2>Introduction</h2>\n"; -while (<TEXFAQ>) { - last if /\\section\{([^\}]*)\}/; - &sanitize_line; - print FAQ; -} - -# start the index of questions ($_ still left over from last read from file) -/\\section\{([^\}]*)\}/; -$_ = $1; -&sanitize_line; -print FAQ "<h3>$_</h3><ul>\n"; - -# first pass, we have a file open by default -$faq_file_open = 1; - -while ( $faq_file_open ) { - - # no question yet open - $qfile_open = 0; - - while (<TEXFAQ>) { - if ($converting) { - if ( /^\s*\\section\{(.*)\}\s*$/ ) { - $_=$1; - &sanitize_line; - print FAQ "</ul><h3>$_</h3><ul>\n"; - $_=""; - } elsif ( /^\s*\\subsection\{(.*)\}\s*$/ ) { - $_=$1; - &sanitize_line; - print FAQ "</ul><h4>$_</h4><ul>\n"; - $_=""; - } - } - - &sanitize_line; - if (/^\s*\\Question\[([^]]*)\]\{(.*)\}\s*$/) { - $qnum++; - $next_qlabel = substr $1, 2; - $entry = "<li><a href=\"FAQ-$next_qlabel.html\">$2</a>\n"; - print FAQ $entry; - if ($qfile_open) { - print QFILE "<p>This question on the Web: ", - "<a href=\"http://www.tex.ac.uk/cgi-bin/texfaq2html?label=", - $qlabel,"\">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=", - $qlabel,"</a>\n"; - print QFILE "</body>\n"; - close QFILE; - } - $qlabel = $next_qlabel; - open (QFILE, ">$faqhtml/FAQ-$qlabel.html") || - oh_dear ("couldn't open file for question $qnum"); - $qfile_open=1; - printf QFILE ("<head> -<title>UK TeX FAQ -- question label $qlabel</title> -</head><body> -<h3>$2</h3> -"); - } else { - if ($qfile_open) { print QFILE; } - } - } - - if ($qfile_open) { - print QFILE "</body>\n"; - close QFILE; - } - - # now: are there any other file names in ARGV? - if ( $#ARGV >= 0 ) { - close TEXFAQ; - $next_file = $ARGV[0]; - open (TEXFAQ, "$home/$next_file") || - oh_dear ("Couldn't open $home/$next_file"); - shift; - } else { - $faq_file_open = 0; - } -} - -# finish off the index.html file listing all questions -print FAQ "</ul>\n"; - -# report number of questions processed - print "$qnum questions processed\n"; - -# An error report: - -sub oh_dear { - print $_[0], "\n"; - die $_; -} - - -# Print a tail. - -printf FAQ (" -<hr><address> - Maintenance of the - <a href=\"http://www.tex.ac.uk/faq\">TeX FAQ</a> - is coordinated by Robin Fairbairns.<p> -"); - -$qref_noans=$qref{"Q-noans"}; -$qref_newans=$qref{"Q-newans"}; - -printf FAQ (" - Comments, suggestions, or error reports? -- see - \"<a href=\"%s\">Improving the FAQ</a>\" or - \"<a href=\"%s\">Extending the FAQ</a>\". -<p> - This is FAQ version $fileversion, last modified on $filedate. -</address> -</body></html> -", $qref_noans, $qref_newans); - -# That's it! diff --git a/Master/texmf-doc/doc/english/FAQ-en/texfaq2html b/Master/texmf-doc/doc/english/FAQ-en/texfaq2html deleted file mode 100644 index f8e2f5d7181..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/texfaq2html +++ /dev/null @@ -1,434 +0,0 @@ -#!/usr/bin/perl -# -# ======================================================================== -# @perl-file{ -# author = "Alan Jeffrey", -# version = "0.19", -# date = "15 January 1996", -# time = "12:26:55 GMT", -# filename = "texfaq2html", -# address = "School of Cognitive and Computing Sciences -# University of Sussex -# Brighton BN1 9QH -# UK", -# FAX = "+44 1273 671320" -# email = "alanje@cogs.sussex.ac.uk", -# codetable = "ISO/ASCII", -# keywords = "LaTeX FAQ HTML", -# supported = "yes", -# abstract = "This perl script converts the UKTUG TeX FAQ -# LaTeX source document into HTML, on the fly." -# package = "stands alone", -# dependencies = "faqbody.tex, newfaq.aux, dirctan.tex, -# filectan,tex", -# } -# ======================================================================== - -# A script to provide a searchable WWW interface to the the UKTUG TeX -# FAQ file. -# -# The script takes parameters in the form of the QUERY_STRING environment -# variable. - -# Copyright 1994 Alan Jeffrey -# Maintenance, since 1997, Robin Fairbairns - -require "sanitize.pl"; - -# The site-specific stuff: - -$default_web = "www.tex.ac.uk"; -$href_script="http://$default_web/cgi-bin/texfaq2html"; -$home = "$ENV{FAQ_HOME}" || "/anfs/www/VH-tex/faq-source"; -$texfaq = "faqbody.tex"; -$auxfaq = "newfaq.aux"; -$ctandir = "dirctan.tex"; -$ctanfiles = "filectan.tex"; -$archive_list = "archive.list"; - -# defaults; these have to be allowed by the $archive_list file - -$default_archive = "cam.ctan.org"; -$fmt_1 = ".tar.gz"; -$fmt_2 = ".zip"; -$fmt_2_name = "zip"; -$fmt_3 = "/"; -$fmt_3_name = "browse"; - -# protocols for transferring files, browsing directories -$proto_f = "ftp"; -$host_f = $default_archive; -$proto_d = "http"; -$host_d = $default_web; - -$proto_1 = $proto_2 = $proto_f; -$host_1 = $host_2 = $host_f; -$proto_3 = $proto_d; -$host_3 = $host_d; - -# table of symbols we believe in -%SymbolChar = ( - 92 => "\\", - 123 => "\{", - 125 => "\}" -); - -# This script produces HTML: - -print ("Content-type: text/html\n\n"); - -# Parse the arguments, and substitute hex(nn) for %nn: - -$_=$ENV{QUERY_STRING}; - -while (/(\b\w*)\=([^\&]*)/g) { - ($key,$val)=($1,$2); - $val =~ s/\+/ /g; - $val =~ s/\%(\w\w)/sprintf("%c",hex($&))/eg; - $key =~ s/^archive$/a/; - $keys{$key} = $val; -} - -$original_keyword = $keys{'keyword'}; -$original_keyword =~ s/ /\+/g; -$keyword = $keys{'keyword'}; -$keyword =~ s/\+/ /g; -$introduction = $keys{'introduction'}; -$question = $keys{'question'}; -$label = $keys{'label'}; - -if ( $arch = $keys{'a'} ) { - $got_arch = 1; - $xtra_k = '&a=' . $arch } -else { - $arch = $default_archive } - -grep ($question{$_}=1, split(/\s+/,$question)); -grep ($label{"Q-$_"}=1, split(/\s+/,$label)); - -# By default, we convert LaTeX to HTML. - -$converting = 1; -$ignoring = 0; -$sectioning = 0; - -# two things used in conversion of \item[ ] - -$itemset = ""; -$enditemset = ""; - -# Get the list of CTAN directories: - -open (CTANDIR, "$home/$ctandir") - || &oh_dear ("Couldn't open $ctandir"); - -while (<CTANDIR>) { - if ( /\\CTANdirectory\{([^\}]*)\}\{([^\}]*)\}/ ) { - $ctanref{$1} = "$2"; - $ctanref_plus{$1} = 1; - } elsif ( /\\CTANdirectory\*\{([^\}]*)\}\{([^\}]*)\}/ ) { - $ctanref{$1} = "$2/"; - $ctanref_plus{$1} = 0; - } -} - -# Get the list of CTAN files - -open (CTANFILES, "$home/$ctanfiles") - || &oh_dear ("Couldn't open $ctanfiles"); - -while (<CTANFILES>) { - - if ( /\\CTANfile\{([^\}]*)\}\{([^\}]*)\}/ ) { - $ctanref{$1} = "$2"; - $ctanref_plus{$1} = -1; - } -} - -# Get the list of allowable archives - -open (ARCHIVE_LIST, "$home/$archive_list") - || &oh_dear ("Couldn't open $archive_list"); - -while (<ARCHIVE_LIST>) { - chop; - ($archive, $root_dir) = split(/\s+/, $_, 2); - $archive_root{$archive} = $root_dir; -} -unless ( $this_root = $archive_root{$arch} ) { - &oh_dear("Archive $arch isn't in my list") } -$arch_root = "$arch/$this_root/"; - -# Get the Qrefs: - -open (AUXFAQ, "$home/$auxfaq") - || &oh_dear ("Couldn't open $auxfaq"); - -$last_question = -1; -$labels = ""; - -while (<AUXFAQ>) { - if (/\\newlabel\{([^\}]*)\}\{\{([^\}]*)\}/) { - $last_question = $2; - next if ( !( ($this_Qlabel = $1) =~ /^Q-/ ) ); - $this_label = $this_Qlabel; - $this_label =~ s/^Q-//; - $label_list{$last_question} = $this_label . $xtra_k; - $question{$last_question}=1 if $label{$this_Qlabel}; - if ($question{$last_question}) { - $qref{$this_Qlabel} = "#[$this_Qlabel]"; - $labels .= "+" . $this_label; - } else { - $qref{$this_Qlabel} = - "$href_script?label=$this_label$xtra_k"; - } - } -} - -# $labels to hold a (list of) label names for these question(s) -$labels =~ s/^\+//; - -# Open the FAQ file: - -open (TEXFAQ, "$home/$texfaq") - || &oh_dear ("Couldn't open $texfaq"); - -# Run through to the introduction, grabbing useful info. - -while (<TEXFAQ>) { - last if /\\section\{Introduction\}/; - $fileversion=$1 if /\\def\\faqfileversion\{([^\}]*)\}/; - $filedate=$1 if /\\def\\faqfiledate\{([^\}]*)\}/; -} - -# Print the title (and build up some information for the trailer): - -$next_question = $previous_question = -1; - -$title_modifier=""; -if ($question || $label) { - $question_count=0; - foreach $key ( keys %question ) { - $question_count++; - $title_modifier=" -- question label \"$label_list{$key}\""; - $next_question = $key + 1; - if ( $key > 1 ) { - $previous_question = $key - 1; - } - } - if ( $question_count > 1 ) { - $title_modifier=""; - $next_question = $previous_question = -1; - $url_name = "these questions"; - } else { - $url_name = "this question"; - } -} - -if ( $next_question > 0 && - $next_question > $last_question ) { $next_question = -1 }; - -printf (" -<html><head> -<title>TeX Frequently Asked Questions $title_modifier</title> -</head><body> -<h1 align=\"center\">Welcome to the UK List of<br> - TeX Frequently Asked Questions<br> - on the Web</h1> -"); - -# Blast out the introduction until we get to the first section. - -if ($introduction) { - print "<center>Skip to <a href=#search>Search</a>"; - if ( $question || $label || $keyword ) { - print "\n"; - } else { - print " or <a href=#questions>List of questions</a></center>\n"; - } - print "<h2>Introduction</h2>\n"; - while (<TEXFAQ>) { - last if /\\section/; - &sanitize_line; - print; - } -} else { - $_ = ""; -} - -# Produce the form. - -printf " -<h2><a name=search>Searching</a></h2> -<form action=\"$href_script\" method=get> -The index of Frequently Asked Questions about TeX is searchable.<br> -Please enter your keyword here:"; -if ( $got_arch ) { - printf "\n<input type=hidden name=a value=\"$arch\">"; -} -print <<SEARCHES; -<input type=\"text\" name=\"keyword\"> -then press here: <input type=\"submit\" value=\"search\">, or: -</form> -<!-- Search Google --> -<center> -<FORM method=GET action="http://www.google.com/search"> -<TABLE bgcolor="#FFFFFF"><tr><td> -<A HREF="http://www.google.com/"> -<IMG SRC="http://www.google.com/logos/Logo_40wht.gif" -border="0" ALT="Google" align="absmiddle"></A> -<INPUT TYPE="text" name="q" size="25" maxlength="255" value=""> -<INPUT TYPE="hidden" name="q" value="TeX Frequently Asked Questions"> -<INPUT TYPE="hidden" name="sitesearch" value="tex.ac.uk"> -<INPUT TYPE="hidden" name="as_eq" value="matches"> -<INPUT type="submit" name="btnG" VALUE="Google Search"> -</td></tr></TABLE> -</FORM> -</center> -<!-- Search Google --> -<hr> - -SEARCHES - - -if ($question || $label) { - do { - if (s/^\s*\\Question(\[.*\])?\{(.*)\}\s*$/$2/) { - $qnum++; - &sanitize_line; - if ($question{$qnum}) { - print "<h2>"; - print "<a name=\"$1\">" if $1; - print; - print "</a>" if $1; - print "</h2>\n"; - } - } elsif ($question{$qnum}) { - $printed = 1; - &sanitize_line; - print; - } - } while (<TEXFAQ>); - print "<p>\n"; - if ( ! $printed ) { - print "<h2>Warning</h2>\n"; - print "There is no question '$question'!<p>\n" - if $question; - print "There is no question with label '$label'!<p>\n" - if $label; - } -} else { - if ($keyword) { - $_=$keyword; - sanitize_line; - print "Questions matching the expression '"; - print; - print "'"; - foreach $kwd ( split /\+/, $keyword ) { - $kwds{$kwd} = 1; - } - } else { - $kwds{"."} = 1; - $sectioning = 1; - } - print "<ul>"; - $firstsection = 1; - do { - if ($sectioning && $converting) { - if (/^\s*\\section\{(.*)\}\s*$/ ) { - $_=$1; - &sanitize_line; - if ( $firstsection ) { - print "</ul><h3><a name=questions>$_</a></h3><ul>\n"; - $firstsection = 0; - } else { - print "</ul><h3>$_</h3><ul>\n"; - } - $_=""; - } elsif ( /^\s*\\subsection\{(.*)\}\s*$/ ) { - $_=$1; - &sanitize_line; - print "</ul><h4>$_</h4><ul>\n"; - $_=""; - } - } - &sanitize_line; - if (/^\s*\\Question(\[.*\])?\{(.*)\}\s*$/) { - $qnum++; - $entry = "<li><a href=\"$href_script?label=$label_list{$qnum}$xtra_k\">$2</a>\n"; - } - foreach $kwd ( keys %kwds ) { - if (/$kwd/i && $qnum) { - print $entry; - $entry = ""; - $matches{$qnum} = 1; - last; - } - } - } while (<TEXFAQ>); - print "</ul>"; - @matches=sort(keys(%matches)); - if ($#matches == -1) { - print "<em>There were no matches.</em><p>\n"; - } elsif ($#matches == 0) { - print "There was one match.<p>\n"; - } else { - $stupid_perl = @matches; - print "There were $stupid_perl matches. ", - "You can get all of them by pressing ", - "<a href=\"$href_script?question=", - (join("+",@matches)),$xtra_k, - "\">here</a>.<p>\n"; - } -} - -# An error report: - -sub oh_dear { - print "<i>This shouldn\'t happen!</i><p>\n", - $_[0], - "\n<p>Please report this!\n"; - die $_; -} - -# print links to other questions - - -# Print a tail. - -printf(" -<hr><address> - Maintenance of the - <a href=\"http://www.tex.ac.uk/faq\">TeX FAQ</a> - is coordinated by Robin Fairbairns.<p> -"); -if ( $next_question >0 && $previous_question > 0 ) { - print "Go to <a href=\"$href_script?label=$label_list{$previous_question}\">\ - previous question</a>, or - <a href=\"$href_script?label=$label_list{$next_question}\">\ - next question</a>"; -} -elsif ( $next_question > 0 ) { - print "Go to <a href=\"$href_script?label=$label_list{$next_question}\">\ - next question</a>"; -} -elsif ( $previous_question > 0 ) { - print "Go to <a href=\"$href_script?label=$label_list{$previous_question}\">\ - previous question</a>"; -} -print "<p>\n"; - -if ( $question || $label ) { - print "URL for $url_name: $href_script?label=$labels<p>\n"; -} - -printf(" - Comments, suggestions, or error reports? - see - \"<a href=\"$href_script?label=noans+newans\">how to improve the FAQ</a>\". -<p> - This is FAQ version $fileversion, last modified on $filedate. -</address> -</body></html> -"); - -# That's it! diff --git a/Master/texmf-doc/doc/english/FAQ-en/texnames.sty b/Master/texmf-doc/doc/english/FAQ-en/texnames.sty deleted file mode 100644 index 395751126a5..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/texnames.sty +++ /dev/null @@ -1,328 +0,0 @@ -% /u/sy/beebe/tex/texnames/texnames.sty, Sat Oct 26 11:19:21 1991 -% Edit by Nelson H. F. Beebe <beebe@magna.math.utah.edu> -%%% ==================================================================== -%%% @TeX-style-file{ -%%% author = "Nelson H. F. Beebe", -%%% version = "1.09", -%%% date = "16 March 1993", -%%% time = "10:08:05 MST", -%%% filename = "texnames.sty", -%%% address = "Center for Scientific Computing -%%% Department of Mathematics -%%% South Physics Building -%%% University of Utah -%%% Salt Lake City, UT 84112 -%%% USA -%%% Tel: (801) 581-5254 -%%% FAX: (801) 581-4148", -%%% checksum = "15888 291 1374 12268", -%%% email = "beebe@magna.math.utah.edu (Internet)", -%%% codetable = "ISO/ASCII", -%%% keywords = "TeX names", -%%% supported = "yes", -%%% docstring = "This style file for AmSTeX, LaTeX, and TeX -%%% defines macros for the names of TeX -%%% and METAFONT programs, in several -%%% letter-case variants: -%%% -%%% \AMSTEX, \AMSTeX, \AmSTeX -%%% \BIBTEX, \BIBTeX, \BibTeX -%%% \LAMSTeX, \LAmSTeX -%%% \LaTeX, \LATEX -%%% \METAFONT, \MF -%%% \SLITEX, \SLITeX, \SLiTeX, \SliTeX -%%% -%%% It will NOT redefine any macro that -%%% already exists, so it can be included -%%% harmlessly after other style files. -%%% -%%% In AmSTeX or Plain TeX, just do -%%% -%%% \input texnames.sty -%%% -%%% In LaTeX, do -%%% -%%% \documentstyle[...,texnames]{...} -%%% -%%% This file grew out of original work by -%%% -%%% Richard Furuta -%%% Department of Computer Science -%%% University of Maryland -%%% College Park, MD 20742 -%%% -%%% furuta@mimsy.umd.edu -%%% seismo!umcp-cs!furuta -%%% -%%% 22 October 1986, first release (1.00) -%%% -%%% 1 April 1987 (1.01): Modified by William -%%% LeFebvre, Rice University to include -%%% definitions for BibTeX and SLiTeX, as they -%%% appear in the LaTeX Local User's Guide -%%% template (the file latex/local.tex in -%%% standard distributions) -%%% -%%% 26 October 1991 (1.02): Modified by -%%% Nelson H. F. Beebe <beebe@math.utah.edu> to -%%% add several new macro names, and adapt for -%%% use with Plain TeX and AmSTeX. -%%% -%%% 26 October 1991 (1.03): Add \LaTeX and -%%% \LATEX -%%% -%%% 25 November 1991 (1.04): Add \LamSTeX -%%% and \LAMSTeX -%%% -%%% 27 January 1991 (1.05 and 1.06): Add slanted -%%% font support for \MF. Make several comment -%%% changes. Add a couple of missing % at end -%%% of line, and replace blank lines by empty -%%% comments. -%%% -%%% 30 December 1992 (1.07): Use \TeX in -%%% definitions of \BibTeX and \LaTeX. Remove -%%% occurrences of \rm. Change \sc to use -%%% \scriptfont instead of hardwiring cmcsc10. -%%% Use \cal for \LAMSTeX. -%%% -%%% 1 March 1993 (1.08): Consolidate \ifx's onto -%%% single lines for brevity. Add -%%% \spacefactor1000 to definitions for \TeX and \MF. -%%% -%%% 16 March 1993 (1.09): Add \AmS, \AMS, \AmSLaTeX, -%%% and \AMSLaTeX. -%%% -%%% The checksum field above contains a CRC-16 -%%% checksum as the first value, followed by the -%%% equivalent of the standard UNIX wc (word -%%% count) utility output of lines, words, and -%%% characters. This is produced by Robert -%%% Solovay's checksum utility.", -%%% -%%% } -%%% ==================================================================== -% -\immediate\write16{This is texnames.sty, Version 1.09 <16 March 1993>}% -% -% This has a chance of working in different styles and sizes, although -% it's not perfect. If \sc actually selects a caps-and-small caps font, -% we want to use lowercase letters (to get the small caps). But if \sc -% selects a smaller point size, we want to use uppercase letters. -% \uppercasesc is called on every letter we typeset in \sc, so both -% forms can be accommodated. -\ifx\sc\undefined - \def\sc{% - % If there is no \scriptfont for the current family, use a fixed - % font. What more can we do? - \expandafter\ifx\the\scriptfont\fam\nullfont - \font\temp = cmr7 \temp - \else - \the\scriptfont\fam - \fi - \def\uppercasesc{\char\uccode`}% - }% -\fi -\ifx\uppercasesc\undefined - \let\uppercasesc = \relax -\fi -% -% In the following, we first give the ``official'' definition, -% then follow it with spelling variants. Alternate definitions -% are discarded in favor of the official one. Each family is -% separated by a line like the following one. -% -%======================================================================= -% -% Only change from plain.tex is the \spacefactor assignment (suggested -% by Phil Taylor), so that \TeX at the end of a sentence isn't treated -% as an abbreviation. -% -\def\TeX{T\kern-.1667em\lower.5ex\hbox{E}\kern-.125emX\spacefactor1000 }% -% -%======================================================================= -% From the AMS tex/ams/amslatex/fontsel/nfssinst.tex file: -% hacked by RF 1994/03/31 -\ifx\mathcal\undefined - \def\mathcal#1{{\cal #1}} -\fi -\ifx\AmS\undefined - \def\AmS{$\mathcal{A}$\kern-.1667em\lower.5ex\hbox - {$\mathcal{M}$}\kern-.125em$\mathcal{S}$} -\fi -\ifx\AMS\undefined \let\AMS=\AmS \fi -\ifx\AmSLaTeX\undefined - \def\AmSLaTeX{\AmS-\LaTeX} -\fi -\ifx\AMSLaTeX\undefined \let\AMSLaTeX=\AmSLaTeX \fi -%======================================================================= -% -% Mike Spivak's amstex/amstex.tex 1.1d [26-Aug-1988] has -% \def\AmSTeX{{\textfontii A}\kern-.1667em\lower.5ex\hbox -% {\textfontii M}\kern-.125em{\textfontii S}-\TeX} -% and 2.1 [05-Apr-1991] has an equivalent definition. -% AmSTeX's \textfontii is exactly the same as \cal, which -% all TeX variants understand. -% -\ifx\AmSTeX\undefined - \def\AmSTeX{\AmS-\TeX}% -\fi -% -% Leslie Lamport's latex/tmanual.tex [10-Jul-1984] (an early -% draft of the book) defines it in uppercase with the standard -% definition. -\ifx\AMSTEX\undefined \let\AMSTEX=\AmSTeX \fi -% -% Barbara Beeton's latex/deproc.sty [24-Apr-1986] and inputs/tugbot.sty -% [11-Jan-1988] uses this spelling, but the definition -% \leavevmode\hbox{$\mathcal{A}\kern-.2em\lower.376ex \hbox{$\mathcal{ -% M}$}\kern-.2em\mathcal{S}$-\TeX} -\ifx\AMSTeX\undefined \let\AMSTeX=\AmSTeX \fi -% -%======================================================================= -% -% The definitions of \BibTeX and \SLiTeX in Leslie Lamport's -% latex/local.tex lower the E by 0.7ex, while \TeX in plain.tex lowers -% it by 0.5ex. Oren Patashnik's bibtex/btxdoc.tex and bibtex/btxhak.tex -% [08-Feb-1988] and bibtex/bibtex.web 0.99c [xx-Feb-1988] use this same -% name and definition, but Oren said using \TeX here is ok. (Curiously, -% LaTeX itself does not define macros for any TeXware except LaTeX and -% TeX!) -\ifx\BibTeX\undefined - \ifx\textsc\undefined - \def\BibTeX{B{\sc \uppercasesc i\kern-.025em \uppercasesc b}\kern-.08em - \TeX}% - \else - \def\BibTeX{\textsc{Bib}\kern-.08em - \TeX}% - \fi -\fi -% -% Leslie Lamport uses this spelling in latex.tex, but not as a -% macro. We include it for consistency with AMSTeX. -\ifx\BIBTeX\undefined \let\BIBTeX=\BibTeX \fi -% -% Leslie Lamport's latex/slides.tex [05-Jun-1984], -% latex/tmanual.tex [10-Jul-1984] (an early draft of the book), -% and latex/lerrata.tex [23-Jul-1985] have this spelling, but the -% definition BIB\kern-.1em\TeX. -\ifx\BIBTEX\undefined \let\BIBTEX=\BibTeX \fi -% -%======================================================================= -% -% From tugboat.com 1.08 [24-Oct-1990]. -\ifx\LAMSTeX\undefined - \def\LAMSTeX{L\raise.42ex\hbox{\kern-.3em\the\scriptfont2 A}% - \kern-.2em\lower.376ex\hbox{\the\textfont2 M}% - \kern-.125em {\the\textfont2 S}-\TeX}% -\fi -% -\ifx\LamSTeX\undefined \let\LamSTeX=\LAMSTeX \fi -% -% This variant seems likely to appear: -\ifx\LAmSTeX\undefined \let\LAmSTeX=\LAMSTeX \fi -% -%======================================================================= -% -% The definition from latex.tex (LATEX VERSION 2.09 <14 January 1991>) -% and bibtex.web 0.99c [xx-Feb-1988] lowers the E slightly more than -% \TeX, but consistency seems more desirable. See comments at \BibTeX. -% Different definitions are given by latex/deproc.sty [24-Apr-1986], -% amstex/man.sty [15-Dec-1986] inputs/tugbot.sty [11-Jan-1988], and -% latex/tugboat.com 1.08 [24-Oct-1990]. -% -% note: this definition doesn't have a variant based on \textsc, since -% anything that's LaTeX2e-compatible ought to have it anyway... -% -\ifx\LaTeX\undefined - \def\LaTeX{L\kern-.36em\raise.3ex\hbox{\sc \uppercasesc a}\kern-.15em\TeX}% -\fi -% -% latex/slides.tex [05-Jun-1984] and latex/lerrata.tex [23-Jul-1985] -% have this spelling, but different definitions -\ifx\LATEX\undefined \let\LATEX=\LaTeX \fi -% -% LaTeX 2e `standard' logo (euuccchhhh!) -\ifx\LaTeXe\undefined - \def\LaTeXe{\LaTeX\kern.15em 2${}_{\textstyle\varepsilon}$} -\fi -% -% and a corresponding thing for LaTeX _explicitly_ 2.09 -% -\ifx\LaTeXo\undefined - \def\LaTeXo{\LaTeX\kern.15em 2.09} -\fi -% -%======================================================================= -% -% Don Knuth's mf.web 2.7 [xx-Sep-1990] and Barbara Beeton's -% latex/deproc.sty [24-Apr-1986] use an equivalent of this definition. -% The font is variously named \logo, \manfnt, and \mf. plain.tex -% preloads \manfnt. manfnt has the letters A, E, F, M, N, O, T in -% various sizes plus extra symbols for Don Knuth's books Computers and -% Typesetting, and Concrete Mathematics, while logo10 has only those -% letters in one size. AmSTeX uses \logo in amsppt.sty and imappt.sty, -% so we should avoid it, and tugboat.com uses \mf for {\smc Metafont}. -% We therefore use \manfnt here, defining it if necessary. QUESTION: -% should we use manfnt, or logo10? -\ifx\MF\undefined - \ifx\manfnt\undefined - \font\manfnt=logo10 - \fi - \ifx\manfntsl\undefined - \font\manfntsl=logosl10 - \fi - \def\MF{{\ifdim\fontdimen1\font>0pt \let\manfnt = \manfntsl \fi - {\manfnt META}\-{\manfnt FONT}}\spacefactor1000 }% -\fi -% -% I cannot find any `official' uses of this alternate, but it -% seems likely that people will use it. -\ifx\METAFONT\undefined \let\METAFONT=\MF \fi -% -%======================================================================= -% -% Leslie Lamport's latex/slides.tex [05-Jun-1984]. His -% latex/lerrata.tex [23-Jul-1985] and latex/tmanual.tex -% [10-Jul-1984] (an early draft of the book) define it as -% SLI\TeX! The LaTeX User's Guide and Reference Manual (1986) -% appears to use small caps, and possibly kerning, for Sli. -% I need to ask Leslie to suggest a preferred definition. -\ifx\SLITEX\undefined - \ifx\textsc\undefined - \def\SLITEX{S\kern-.065em L\kern-.18em\raise.32ex\hbox{\textsc{i}}% - \kern-.03em\TeX}% - \else - \def\SLITEX{S\kern-.065em L\kern-.18em\raise.32ex\hbox{i}% - \kern-.03em\TeX}% - \fi -\fi -% -% latex/local.tex (sample Local Guide) [27-Oct-1988] uses -% this name, but defines it as -% {\rm S\kern-.06em{\sc l\kern-.035emi}\kern-.06em T\kern -% -.1667em\lower.7ex\hbox{E}\kern-.125emX} -% with an extra-low E, and kerned Sli in small caps. Is this -% what the LaTeX User's Guide and Reference Manual (1986) used? -\ifx\SLiTeX\undefined \let\SLiTeX=\SLITEX \fi -% -% latex/slitex.tex [08-Jun-1988] uses SliTeX in typeouts, -% but not as a macro -- what a way to confuse the user. -\ifx\SliTeX\undefined \let\SliTeX=\SLITEX \fi -% -% I cannot find a use of this one, but it seems a likely -% candidate anyway, and is consistent with AMSTeX and BIBTeX. -\ifx\SLITeX\undefined \let\SLITeX=\SLITEX \fi -% -%======================================================================= -% -% from pictex.tex: -\ifx\PiC\undefined \def\PiC{P\kern-.12em\lower.5ex\hbox{I}\kern-.075emC} \fi -\ifx\PiCTeX\undefined \def\PiCTeX{\PiC\kern-.11em\TeX} \fi -% -% from fantasy-land: -\ifx\VorTeX\undefined \def\VorTeX{V\kern-2.7pt\lower.5ex\hbox{O\kern-1.4pt R}% - \kern-2.6ptT\kern-.1667em\lower.5ex\hbox{E}\kern-.125emX} \fi -% -\endinput -%=========================[End of texnames.sty]========================= diff --git a/Master/texmf-doc/doc/english/FAQ-en/updates.tex b/Master/texmf-doc/doc/english/FAQ-en/updates.tex deleted file mode 100644 index b87434a8c0e..00000000000 --- a/Master/texmf-doc/doc/english/FAQ-en/updates.tex +++ /dev/null @@ -1,45 +0,0 @@ -\section{Updates to the FAQ} - -The list of frequently-asked questions that was published as -Baskerville volume~4, number~6, should be maintained if it's to retain -its usefulness. - -While I can do at least some of this for myself, I would welcome -comments on: -\begin{itemize} -\item Questions that weren't ansswered in the original, but should - have been, and -\item Errors in the original. -\end{itemize} - -To kick the ball off, here's one of each type. - -New question: Typesetting a degree sign in \LaTeXe{}. - -Answer: The following macro will do the job - -| \newcommand{\degree}[1][]{\ensuremath{{#1}^\circ}}| - -Errata in the original: - -The question on ``getting \MF{} to do what you want'' refers you to the -CTAN file~|documentation/metafont_for_beginners.tex|; the file is in -fact~|info/metafont-for-beginners.tex| - -The question on ``Mailing lists about \TeX{} and its friends'' has two -errors in it. - -\begin{itemize} -\item The UK\TeX{} list has now ceased publication, and its content - has now been taken over by the \TeX{}hax list. -\item The description of the |ctt-digest| and |info-tex| lists, and - their relation to the newsgroup |comp.text.tex| is confusing. - |info-tex| does \emph{not} receive postings to |comp.text.tex|, - and therefore the content of |ctt-digest| will typically contain - much material that isn't present in |info-tex|. However, - messages mailed to |info-tex| appear in |comp.text.tex|, and - therefore (ultimately) appear in |ctt-digest|. -\end{itemize} - -Thanks to Allan Reese and Barbara Beeton for pointing me towards these -problems. diff --git a/Master/tlpkg/bin/ctan2tds b/Master/tlpkg/bin/ctan2tds index c68c54b9221..db61f1579d2 100755 --- a/Master/tlpkg/bin/ctan2tds +++ b/Master/tlpkg/bin/ctan2tds @@ -40,7 +40,8 @@ chdir $startdir || die "chdir($startdir) failed: $!"; # back to raw # can have their own subroutine. # %special = ( - 'Catalogue', "&MAKEcatalog", + 'Catalogue', "&MAKECatalogue", + 'FAQ-en', "&MAKEFAQen", 'HA-prosper', '&MAKEhaprosper', 'IEEEtran', "&MAKEIEEEtran", 'LingTrees', "die 'skipping, requires python'", @@ -414,6 +415,7 @@ chdir $startdir || die "chdir($startdir) failed: $!"; # back to raw $standardsource='\.fdd|\.dtx|\.ins|\.c$|Makefile|\.drv'; %specialsource= ( + 'FAQ-en', 'NULL', 'ae', "$standardsource|\.mtx|\.etx|\.tex|clean|go|install|makepl", 'amsldoc-vn', 'NULL', 'apl', ".*", # just get everything, seems simplest @@ -750,6 +752,7 @@ $standardmakeindex='\.ist'; # packages which need special .tex/.sty files installed $standardtex='\.cfg|\.sty|\.clo|\.ldf|\.cls|\.def|\.fd$'; %specialtex= ( + 'FAQ-en', 'NULL', 'abbr', '\.tex', 'abstyles', "apreambl.tex", # not a4c.sty 'ae', '\.fd$|\.sty', @@ -1196,6 +1199,7 @@ $standardclean = '\.head|\.tmp|\.dvi|\.log|\.out|\.aux|\.toc|\.lof|\.lot' # that the files were removed. These are checked after runins. %moreclean = ( 'AkkTeX' => 'still to do, sorry', + 'FAQ-en' => '.*\.pdf', 'bbcard' => 'bbcard.tpm', 'chessboard' => 'chessboard.pdf', 'chessfss' => 'chessfonts_gallery.pdf|chessfss.pdf', @@ -1307,7 +1311,7 @@ sub set_dir_defaults $standarddocfmt = $standardsourcefmt = "fonts"; $guess = "$standarddocfmt for docfmt/srcfmt"; - } elsif ($ctan_dir =~ m!/info/!) { + } elsif ($ctan_dir =~ m!/(info|help)/!) { $standarddest = "texmf-doc"; $guess = "$standarddest for dest"; @@ -1657,7 +1661,7 @@ sub runjob { # remove additional files matching something in $moreclean # create a README.TEXLIVE which lists the removed files # -# remove all files matching something in $killpatt. +# remove all files matching something in $KILLPATT. # also remove .ps files for which we have a .pdf. # sub killfiles @@ -2596,7 +2600,7 @@ sub MAKEelhyphen { print "YOU-MUST-DO! $package: add to texmf/tpm/collection-langgreek.tpm\n"; } -sub MAKEcatalog { +sub MAKECatalogue { # this simply copies source files $DEST="$TDS/catalogue/texmf-doc"; chdir($packagedir) || die ("ERROR: cannot open directory"); @@ -2618,6 +2622,12 @@ sub MAKEcatalog { } } +sub MAKEFAQen +{ + &donormal (); + &SYSTEM ("tar xzf FAQ-html.tar.gz && rm FAQ-html.tar.gz"); +} + # all the lshort translations are pretty similar. sub MAKElshort { print "MAKElshort $package\n"; diff --git a/Master/tlpkg/tlpsrc/FAQ-en.tlpsrc b/Master/tlpkg/tlpsrc/FAQ-en.tlpsrc index 44d9b199b5e..fdf4e565c48 100644 --- a/Master/tlpkg/tlpsrc/FAQ-en.tlpsrc +++ b/Master/tlpkg/tlpsrc/FAQ-en.tlpsrc @@ -1,2 +1,3 @@ name FAQ-en category Documentation +catalogue uk-tex-faq |