diff options
| author | Karl Berry <karl@freefriends.org> | 2011-02-19 00:37:41 +0000 |
|---|---|---|
| committer | Karl Berry <karl@freefriends.org> | 2011-02-19 00:37:41 +0000 |
| commit | 8f846f8a8c7b2774059df2db0f153948e98cccf1 (patch) | |
| tree | ff1781fa9b83db1e66c931962c18f57ae3428294 | |
| parent | 09eb455bf0a899e9231b600e1326d5e0e4a67aca (diff) | |
FAQ-en 3.21 (18feb11)
git-svn-id: svn://tug.org/texlive/trunk@21459 c570f23f-e606-0410-a88d-b1316a301751
95 files changed, 2318 insertions, 1290 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.21 b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.21 new file mode 100644 index 00000000000..1d7abd0014c --- /dev/null +++ b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.21 @@ -0,0 +1,47 @@ +Changes since version 3.20 + +New answers: + +Label spawnprog: the \write18 mechanism for spawning programs + +Label whatengine: am I running pdfTeX, XeTeX or luaTeX? + +Label write: the \write primitive for writing text files + +Relabelled answers: + <none> + +Revised answers: + +Label biblatex: mention bibtex8, even though biblatex+biber are winning + +Label codelist: extend coverage of minted package (and Pygments) + +Label commercial: remove Y&Y (not commercial any longer) + +Label dpfloat: mention floatpage package + +Label drawing: mention "embedded source" packages for asy, gplot, mp + +Label editors: rationalise, removing "wildcard" + +Label filename: add currfile, remove "DIY" code (which never worked right) + +Label floats: update discussion of morefloats package, mention etex.sty + +Label fmtconv: mention openoffice route for MS-word + +Label gethelp: link "latex community" and "latex stack exchange" + +Label graphicspath: rephrase discussion of \graphicspath + +Label instt1font: attempt to clarify updmap vs. updmap-sys + +Label labelfig: mention (new) lpic package + +Label latex2html: link to info on tug.org (note tex4ht now sourced there) + +Label mathml: link to info on tug.org + +Label music: rewritten following rearrangements on ctan + +Label nopagebrk: discuss \pagebreak, \nopagebreak (!) + +Label papergeom: discuss dvipdfm and its extensions + +Label psfchoice: report one (at least) known problem with [pt]xfonts + +Label pspreview: simplify, given that it's far less of a problem now + +Label ref-doc remove link to NASA latex ref, add link to gna.org one + +Label textflow: mention cutwin package + +Label tmupfl: mention morefloats package, with caveats + +Label verbwithin: mention cprotect package + +Label WYGexpts: drop "activetex" -- seems no longer available + +Label zerochap: rewrite for clarification + +Deleted answers: + +Label ifpdf: subsumed in new "whatengine" answer (link rerouted there) + +Label lollipop: no longer relevant (a pity) + +Web interface, etc.: + Some LaTeX command translations were broken, and have been mended + Work has started on a major reorganisation of the "fonts" section + +Robin Fairbairns diff --git a/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog b/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog index f617a292225..954c4ca0391 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog +++ b/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog @@ -1,9 +1,370 @@ +2011-02-18 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * gather-faqbody.tex: today's date (must stop dithering) + +2011-02-17 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-ctan): proposed new answer to replace existing + q-archives, or to provide background for a revision of that + +2011-02-15 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-install.tex (q-instt1font): clarify updmap situation (perhaps) + (q-inst1cm): minor editorial + + * faq-fonts.tex (q-pspreview): simplify, given that most browsers can + do the job on their own, nowadays + +2011-02-14 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-fonts.tex (q-psfchoice): preliminary adjustments + + * sanitize-beta.pl (sanitize_line): add \ttype and \otype + + * faq.sty: add \ttype and \otype, add a few comments + + * faq-fonts.tex (q-usepsfont): a spot more tweaking + (subsection{mf fonts}): moved to end of section (was first subsect) + +2011-02-14 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-backgrnd.tex: remove q-lollipop + + * faq-fonts.tex (q-usepsfont): remove reference to lollipop, tidy + + * dirctan.tex: add lpic + + * faq-graphics.tex (q-labelfig): mention lpic + + * add-general.tex (q-whatfloats): editorial + (q-outputrtn): more editorial + +2011-02-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-bits+pieces.tex (q-spawnprog): minor editorial + +2011-02-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-bits+pieces.tex (q-write,q-spawnprog): new, from add-general + + * faq-mac-prog.tex (q-whatengine): new, from add-general, replaces + q-ifpdf + + * dirctan.tex: remove acorn, epson + + * filectan.tex: remove miktex-usb + + * faq-biblio.tex (q-custbib): mention biblatex as an alternative route + +2011-02-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-litprog.tex (section{Literate programming}): + + * dirctan.tex: add catalogue ref for ps2pk,ghostscript,gsftopk,fweb and + noweb + remove all entries for derivatives of noweb (leaving noweb itself...) + + * faq-backgrnd.tex (q-whatpdftex): use \The {} in thanh's name + + * faq-wdidt.tex (q-why-inp-font): \ss -> \ss {} + + * faq-docs.tex,faq-graphics.tex (various): vo\ss -> vo\ss {} + + * faq-how-do-i.tex (q-wholerow): space after \textasciicircum (euch) + + * sanitize-beta.pl (sanitize_line): correct delimiter in pattern that + (seems to match) any letter-command name with empty arg [why is that + there in the first place?]; also correct \textasciicircum and \ss + patterns to require a space at the end (pro tem, at least); add \The + +2011-02-09 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * add-general.tex (q-whatfloats): editorial tidies prior to moving + to main body + (q-write and q-write18): editorial, mostly + + * faq-t-g-wr.tex (q-floats): editorial stuff + +2011-02-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * dirctan.tex: add etex-pkg + + * faq-t-g-wr.tex (q-floats): note interaction between morefloats and + etex packages + + * faq-projects.tex (q-mathml): lowercase tex4ht in ctanrefs (for + consistency with other instances) + (q-wygexpts): remove ref to activetex, seems to have disappeared in its + original form + + * faq-fmt-conv.tex (q-fmtconv): add web ref to tex4ht dev stuff in + ctanrefs for question + +2011-01-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-how-do-i.tex (q-filename): remove the broken code and simply + report that "it's not easy" ;-) + +2011-01-13 Robin Fairbairns <rf10@battam> + + * add-general.tex (q-write18): new proposed question + (q-write): on reflection, we need this preface to q-write18 + + * sanitize-beta.pl (sanitize_line): catch up with changes to faq.sty + + * faq.sty: lc versions of \progname, \package and \class + +2011-01-12 Robin Fairbairns <rf10@battam> + + * dirctan.tex: add cprotect; remote convert, cortex-email.dir, conrado + + * faq-wdidt.tex (q-verbwithin): mention cprotect + +2010-12-29 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-adj-types.tex (q-codelist): extend words about minted/Pygments + +2010-12-27 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * add-general.tex (q-whatfloats): more fiddling + +2010-12-26 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-docs.tex: re-do tidies re. bibtex setup + +2010-12-23 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-docs.tex (q-bibtexing): rewrite to deal with bibtex setup + + * faq-biblio.tex (q-custbib): replace bibtex-doc link with just bibtex + + * dirctan.tex: correct cat link for filehook, add bibtex + + * filectan.tex: correct xampl-bib + +2010-12-19 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * add-general.tex (q-whatengine): new answer to replace q-ifpdf + +2010-12-12 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-adj-types.tex (q-papergeom): update for the various extensions of + dvipdfm and rewrite descriptions + +2010-12-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-texsys.tex (q-editors): re-ordered, rationalised a bit, removed + "wildcard" bullet + (q-commercial): clear up debris after removing y&y + +2010-12-09 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-how-do-i.tex (q-filename): add currfile, mention fink gives way + + * faq-backgrnd.tex (q-texthings): correct typo from yesterday + + * dirctan.tex: add currfile, filehook, restore latex4jed (hah!) + +2010-12-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: removed latex4jed, larch, laserjet, since they irritated + me and won't ever be used + + * faq-backgrnd.tex (q-texthings}: link to tug.org/levels.html, context + executable now texmfstart, i'm told + + * faq-docs.tex (q-ref-doc): the nasa latex thing is no more; remove it + and add a ref to karl's thing at gna.org (and on ctan) + +2010-12-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-fonts.tex (q-psfchoice): remove text about docs for [pt]xfonts + (now available via catalogue), mention bad spacing + +2010-12-02 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-whatfloats): add sketch of mechanism + +2010-11-30 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-graphics.tex (q-drawing): mention asymptote, egplot and emp as + inline graphics mechanisms + + * faq-adj-types.tex (q-music): correct "current" musixtex link + + * gather-faqbody.tex: v3.21, today (probably shan't release until after + christmas, but...) + + * filectan.tex: remove vertbars (now own dir); simpl-latex now pdf + + * dirctan.tex: add cutwin, vertbars, egplot; biblatex[-contrib] now on + m/l/c + + * faq-how-do-i.tex (q-textflow): mention cutwin + +2010-11-23 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-xml2tex): more work on peter f's input + +2010-11-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * dirctan.tex: add cat link for html2latex + +2010-11-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * add-general.tex (subsection{Format conversions}): new q-xml2tex + +2010-11-13 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-fmt-conv.tex (q-readml): minor editorial + +2010-10-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * dirctan.tex: add cat link to catdvi (ho ho) + +2010-10-28 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-projects.tex (q-mathml): point to tug page in ctanrefs + + * faq-fmt-conv.tex (q-latex2html): add pointer to real tug.org page + on tex4ht (hence real location), in ctanrefs + + * filectan.tex: tex4ht now on obsolete + + * dirctan.tex: add memdesign + + * faq-docs.tex (q-typo-style): memdesign rather than memman + +2010-10-22 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-adj-types.tex (q-nopagebrk): discuss \pagebreak, \nopagebreak + +2010-10-07 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-whatfloats): a start of a first stab + + * faq-adj-types.tex (q-music): large rehash around musixtex and opustex + +2010-10-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-jot-err.tex (q-tmupfl,q-atvert): tidies, incl indent'n of quotes + +2010-10-04 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * filectan.tex: remove morefloats, parskip, path, printlen + + * dirctan.tex: add morefloats, parskip, path, printlen; new location + for musixtex-egler + + * faq-jot-err.tex (q-tmupfl): mention morefloats, with caveats + +2010-10-02 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-t-g-wr.tex (q-floats): updated morefloat, mention etex + restrictions-regardless-of-number-of-registers + +2010-09-28 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * add-general.tex (q-onna-stick): comment-out the entire question -- + moot now (i think, but am not _certain_) + + * faq-graphics.tex (q-graphicspath): rephrase discussion of + \graphicspath's (potential) problems + +2010-09-28 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-outputrtn): new potential answer + +2010-09-27 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-graphics.tex (q-drawing): mention asyfig, too + + * dirctan.tex: add asyfig and emp + + * faq-graphics.tex (q-drawing): mention emp + +2010-09-24 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: transmute latex-help-texinfo to latex2e-... + + * add-general.tex (q-getnff): new answer for the font installation mess + + * faq-wdidt.tex (q-zerochap): reword for better comprehensibility + +2010-09-21 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-fmt-conv.tex (q-fmtconv): add openoffice route for ms-word + +2010-09-14 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-how-do-i.tex (q-filename): editorial, incl. emphasise latex form + of \input, only + +2010-09-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + * filectan.tex: remove cat link from miktex-setup (confusion); remove + miktex-usb (no longer needed) + +2010-09-09 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-projects.tex (q-biblatex): mention bibtex8, refine biblatex/biber + + * dirctan.tex: add bibtex8 + +2010-09-07 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * sanitize-beta.pl (sanitize_line): add translation for \bibtex + + * faq.sty: add \bibtex + + * faq-projects.tex (q-biblatex): rehash to reflect current realities + (biblatex+biber take over the world) + +2010-09-01 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * add-general.tex (q-detknize): yet more diddling + +2010-08-31 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-intro.tex: add gregor zattler, anonymise "not covered" comment + + * faq-bits+pieces.tex (q-adobetypen): typo + +2010-08-29 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * dirctan.tex: add fltpage + + * faq-how-do-i.tex (q-dpfloat): mention fltpage + +2010-08-27 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-detknize): printing the contents of a macro + + * faq-docs.tex (q-gethelp): add latex community and stack exchange to + the list of places to ask + +2010-08-19 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-wdidt.tex (q-baselinepar): editorial work ("an quote environ...") + +2010-08-18 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-detknize): rewrite last sentence + + * faq.sty: use tmp/comment.cut instead of comment.sty's default; this + is a big win when reading files over nfs, if tmp -> /tmp + 2010-08-17 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + * texfaq2html: bring up-to-date from -beta + + * sanitize.pl: bring up-to-date from -beta + * gather-faqbody.tex: v3.20 (let's live dangerously!), today * mk-makefile: add -t option + [RELEASE 3.20] + 2010-08-15 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> * faq-intro.tex (section improvement; general typos): add siart for @@ -2551,7 +2912,7 @@ RELEASE 3.19a * 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 diff --git a/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex b/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex index 368000da96e..41c0a200e48 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex @@ -1,4 +1,4 @@ -% $Id: dirctan.tex,v 1.237 2010/08/12 18:14:24 rf10 Exp rf10 $ +% $Id: dirctan.tex,v 1.255 2011/02/14 20:53:28 rf10 Exp $ % % protect ourself against being read twice \csname readCTANdirs\endcsname @@ -20,7 +20,6 @@ \CTANdirectory{abstract}{macros/latex/contrib/abstract}[abstract] \CTANdirectory{abstyles}{biblio/bibtex/contrib/abstyles} \CTANdirectory{accents}{support/accents} -\CTANdirectory*{acorn}{obsolete/systems/acorn} \CTANdirectory{acronym}{macros/latex/contrib/acronym}[acronym] \CTANdirectory*{ada}{web/ada/aweb} \CTANdirectory{addindex}{indexing/addindex} @@ -58,6 +57,7 @@ \CTANdirectory*{aspell}{support/aspell}[aspell] \CTANdirectory{astro}{fonts/astro} \CTANdirectory{asymptote}{graphics/asymptote}[asymptote] +\CTANdirectory{asyfig}{macros/latex/contrib/asyfig}[asyfig] \CTANdirectory{atari}{systems/atari} \CTANdirectory*{atari-cstex}{systems/atari/cs-tex}[atari-cstex] \CTANdirectory*{auctex}{support/auctex}[auctex] @@ -97,11 +97,13 @@ \CTANdirectory{bibextract}{biblio/bibtex/utils/bibextract} \CTANdirectory{bibgerm}{biblio/bibtex/contrib/germbib} \CTANdirectory{bibindex}{biblio/bibtex/utils/bibindex} -\CTANdirectory{biblatex}{macros/latex/exptl/biblatex}[biblatex] -\CTANdirectory*{biblatex-contrib}{macros/latex/exptl/biblatex-contrib} +\CTANdirectory{biblatex}{macros/latex/contrib/biblatex}[biblatex] +\CTANdirectory*{biblatex-contrib}{macros/latex/contrib/biblatex-contrib} \CTANdirectory{biblio}{info/biblio} \CTANdirectory{biblist}{macros/latex209/contrib/biblist} \CTANdirectory{bibsort}{biblio/bibtex/utils/bibsort} +\CTANdirectory{bibtex}{biblio/bibtex/base}[bibtex] +\CTANdirectory*{bibtex8}{biblio/bibtex/8-bit}[bibtex8bit] \CTANdirectory{bibtex-doc}{biblio/bibtex/contrib/doc}[bibtex] \CTANdirectory{bibtool}{biblio/bibtex/utils/bibtool} \CTANdirectory{bibtools}{biblio/bibtex/utils/bibtools} @@ -151,7 +153,7 @@ \CTANdirectory{carlisle}{macros/latex/contrib/carlisle}[carlisle] \CTANdirectory{cascover}{macros/plain/contrib/cascover} \CTANdirectory{casslbl}{macros/plain/contrib/casslbl} -\CTANdirectory{catdvi}{dviware/catdvi} +\CTANdirectory{catdvi}{dviware/catdvi}[catdvi] \CTANdirectory{ccaption}{macros/latex/contrib/ccaption}[ccaption] \CTANdirectory{ccfonts}{macros/latex/contrib/ccfonts}[ccfonts] \CTANdirectory{cellular}{macros/plain/contrib/cellular} @@ -209,11 +211,8 @@ \CTANdirectory{concmath}{macros/latex/contrib/concmath}[concmath] \CTANdirectory{concmath-f}{fonts/concmath}[concmath-fonts] \CTANdirectory{concrete}{fonts/concrete}[concrete] -\CTANdirectory{conrado}{web/noweb/contrib/conrado} \CTANdirectory{context}{macros/context}[context] -\CTANdirectory{convert}{support/convert} -\CTANdirectory{cortex-email.dir}{language/typingtex/cortex-email.dir} -%[fonts/courier] +\CTANdirectory{cprotect}{macros/latex/contrib/cprotect}[cprotect] \CTANdirectory{cptex}{macros/generic/cptex} \CTANdirectory{crop}{macros/latex/contrib/crop}[crop] \CTANdirectory*{crosstex}{biblio/crosstex}[crosstex] @@ -224,10 +223,12 @@ \CTANdirectory{ctable}{macros/latex/contrib/ctable}[ctable] \CTANdirectory{ctan}{help/ctan} \CTANdirectory{cun}{fonts/cun} +\CTANdirectory{currfile}{macros/latex/contrib/currfile}[currfile] \CTANdirectory{currvita}{macros/latex/contrib/currvita}[currvita] \CTANdirectory{curve}{macros/latex/contrib/curve}[curve] \CTANdirectory{curves}{macros/latex/contrib/curves} \CTANdirectory{custom-bib}{macros/latex/contrib/custom-bib}[custom-bib] +\CTANdirectory{cutwin}{macros/latex/contrib/cutwin}[cutwin] \CTANdirectory{cweb}{web/c_cpp/cweb} \CTANdirectory{cweb-p}{web/c_cpp/cweb-p} \CTANdirectory{cypriote}{fonts/cypriote} @@ -237,7 +238,6 @@ \CTANdirectory{dante-faq}{help/de-tex-faq} \CTANdirectory{databases}{biblio/bibtex/databases} \CTANdirectory{datetime}{macros/latex/contrib/datetime} -\CTANdirectory{davelove}{web/noweb/contrib/davelove} \CTANdirectory{db2tex}{support/db2tex} \CTANdirectory{dblfloatfix}{macros/latex/contrib/dblfloatfix}[dblfloatfix] \CTANdirectory{dbtex}{support/dbtex} @@ -312,10 +312,11 @@ \CTANdirectory{ednotes}{macros/latex/contrib/ednotes}[ednotes] \CTANdirectory{eepic}{macros/latex/contrib/eepic}[eepic] \CTANdirectory{ega2mf}{fonts/utilities/ega2mf} +\CTANdirectory{egplot}{macros/latex/contrib/egplot}[egplot] \CTANdirectory{eiad}{fonts/eiad} -\CTANdirectory{elsevier}{macros/latex/contrib/elsevier} \CTANdirectory{elvish}{fonts/elvish} \CTANdirectory{elwell}{fonts/utilities/afmtopl/elwell} +\CTANdirectory{emp}{macros/latex/contrib/emp}[emp] \CTANdirectory{emptypage}{macros/latex/contrib/emptypage}[emptypage] \CTANdirectory{emt2tex}{systems/msdos/emtex-contrib/emt2tex} \CTANdirectory{emtex}{systems/msdos/emtex} @@ -332,7 +333,6 @@ \CTANdirectory{eplain}{macros/eplain}[eplain] \CTANdirectory{epmtex}{systems/os2/epmtex} \CTANdirectory{epslatex}{info/epslatex}[epslatex] -\CTANdirectory{epson}{dviware/epson} \CTANdirectory*{epstopdf}{support/epstopdf}[epstopdf] \CTANdirectory{eqparbox}{macros/latex/contrib/eqparbox}[eqparbox] \CTANdirectory{ergotex}{systems/msdos/ergotex} @@ -340,6 +340,7 @@ \CTANdirectory{eso-pic}{macros/latex/contrib/eso-pic}[eso-pic] \CTANdirectory{et}{support/et} \CTANdirectory{etex}{systems/e-tex}[etex] +\CTANdirectory{etex-pkg}{macros/latex/contrib/etex-pkg}[etex-pkg] \CTANdirectory{ethiopia}{language/ethiopia} \CTANdirectory{ethtex}{language/ethiopia/ethtex} \CTANdirectory{etoolbox}{macros/latex/contrib/etoolbox}[etoolbox] @@ -371,6 +372,7 @@ \CTANdirectory{fig2mf}{graphics/fig2mf} \CTANdirectory{fig2mfpic}{graphics/fig2mfpic} \CTANdirectory{figflow}{macros/plain/contrib/figflow}[figflow] +\CTANdirectory{filehook}{macros/latex/contrib/filehook}[filehook] \CTANdirectory{fink}{macros/latex/contrib/fink}[fink] \CTANdirectory{first-latex-doc}{info/first-latex-doc} \CTANdirectory{fix2col}{macros/latex/contrib/fix2col}[fix2col] @@ -379,6 +381,7 @@ \CTANdirectory{floatflt}{macros/latex/contrib/floatflt}[floatflt] \CTANdirectory{flow}{support/flow} \CTANdirectory{flowfram}{macros/latex/contrib/flowfram}[flowfram] +\CTANdirectory{fltpage}{macros/latex/contrib/fltpage}[fltpage] \CTANdirectory{fnbreak}{macros/latex/contrib/fnbreak}[fnbreak] \CTANdirectory{fncychap}{macros/latex/contrib/fncychap}[fncychap] \CTANdirectory{fncylab}{macros/latex/contrib/fncylab} @@ -401,13 +404,13 @@ \CTANdirectory{funnelweb}{web/funnelweb} \CTANdirectory{futhark}{fonts/futhark} \CTANdirectory{futhorc}{fonts/futhorc} -\CTANdirectory{fweb}{web/fweb} +\CTANdirectory{fweb}{web/fweb}[fweb] \CTANdirectory{gellmu}{support/gellmu}[gellmu] \CTANdirectory{genfam}{support/genfam} \CTANdirectory{geometry}{macros/latex/contrib/geometry}[geometry] \CTANdirectory{germbib}{biblio/bibtex/contrib/germbib} \CTANdirectory{gfs}{info/examples/FirstSteps} % gratzer's -\CTANdirectory*{ghostscript}{support/ghostscript} +\CTANdirectory*{ghostscript}{support/ghostscript/GPL}[ghostscript-GPL] \CTANdirectory{glo+idxtex}{indexing/glo+idxtex}[idxtex] \CTANdirectory{gnuplot}{graphics/gnuplot} \CTANdirectory{go}{fonts/go} @@ -419,8 +422,7 @@ \CTANdirectory{gray}{fonts/cm/utilityfonts/gray} \CTANdirectory{greek}{fonts/greek} \CTANdirectory{greektex}{fonts/greek/greektex} -\CTANdirectory{gregory}{web/noweb/contrib/gregory} -\CTANdirectory{gsftopk}{fonts/utilities/gsftopk} +\CTANdirectory{gsftopk}{fonts/utilities/gsftopk}[gsftopk] \CTANdirectory*{gsview}{support/ghostscript/ghostgum}[gsview] \CTANdirectory{gut}{usergrps/gut} \CTANdirectory*{gv}{support/gv}[gv] @@ -444,7 +446,7 @@ \CTANdirectory{hpgl2ps}{graphics/hpgl2ps} \CTANdirectory{hptex}{macros/hptex} \CTANdirectory{hptomf}{support/hptomf} -\CTANdirectory{html2latex}{support/html2latex} +\CTANdirectory{html2latex}{support/html2latex}[html2latex] \CTANdirectory{htmlhelp}{info/htmlhelp} \CTANdirectory{hvfloat}{macros/latex/contrib/hvfloat}[hvfloat] \CTANdirectory{hvmath}{fonts/micropress/hvmath}[hvmath-fonts] @@ -480,11 +482,9 @@ \CTANdirectory{jadetex}{macros/jadetex} \CTANdirectory{jemtex2}{systems/msdos/jemtex2} \CTANdirectory{jknappen-macros}{macros/latex/contrib/jknappen} -\CTANdirectory{jonkrom}{web/noweb/contrib/jonkrom} \CTANdirectory{jpeg2ps}{support/jpeg2ps}[jpeg2ps] \CTANdirectory{jspell}{support/jspell}[jspell] \CTANdirectory{jurabib}{macros/latex/contrib/jurabib}[jurabib] -\CTANdirectory{kaelin}{web/noweb/contrib/kaelin} \CTANdirectory{kamal}{support/kamal} \CTANdirectory{kane}{dviware/kane} \CTANdirectory{karta}{fonts/karta} @@ -513,13 +513,11 @@ \CTANdirectory{lacheck}{support/lacheck} \CTANdirectory{lametex}{support/lametex} \CTANdirectory{lamstex}{macros/lamstex} -\CTANdirectory{latex}{macros/latex/base} -\CTANdirectory{latex4jed}{support/jed} -\CTANdirectory{larch}{web/spiderweb/src/larch} -\CTANdirectory{laserjet}{dviware/laserjet} \CTANdirectory{lastpage}{macros/latex/contrib/lastpage}[lastpage] +\CTANdirectory{latex}{macros/latex/base} \CTANdirectory{latex-essential}{info/latex-essential} -\CTANdirectory{latex-help-texinfo}{info/latex-help-texinfo} +\CTANdirectory{latex2e-help-texinfo}{info/latex2e-help-texinfo}[latex2e-help-texinfo] +\CTANdirectory{latex4jed}{support/jed}[latex4jed] \CTANdirectory*{latex-tds}{macros/latex/contrib/latex-tds}[latex-tds] \CTANdirectory*{latex2html}{support/latex2html}[latex2html] \CTANdirectory{latex2rtf}{support/latex2rtf} @@ -532,7 +530,6 @@ \CTANdirectory{latexmk}{support/latexmk}[latexmk] \CTANdirectory{lecturer}{macros/generic/lecturer}[lecturer] \CTANdirectory{ledmac}{macros/latex/contrib/ledmac}[ledmac] -\CTANdirectory{leew}{web/noweb/contrib/leew} \CTANdirectory{lettrine}{macros/latex/contrib/lettrine}[lettrine] \CTANdirectory{levy}{fonts/greek/levy} \CTANdirectory{lextex}{macros/plain/contrib/lextex} @@ -544,6 +541,7 @@ \CTANdirectory{lm}{fonts/lm}[lm] \CTANdirectory{lollipop}{macros/lollipop}[lollipop] \CTANdirectory{lookbibtex}{biblio/bibtex/utils/lookbibtex} +\CTANdirectory{lpic}{macros/latex/contrib/lpic}[lpic] \CTANdirectory{lsedit}{support/lsedit} \CTANdirectory{lshort}{info/lshort/english}[lshort-english] \CTANdirectory*{lshort-parent}{info/lshort}[lshort] @@ -578,6 +576,7 @@ \CTANdirectory{mciteplus}{macros/latex/contrib/mciteplus}[mciteplus] \CTANdirectory{mctex}{support/mctex} \CTANdirectory{mdwtools}{macros/latex/contrib/mdwtools}[mdwtools] +\CTANdirectory{memdesign}{info/memdesign}[memdesign] \CTANdirectory{memoir}{macros/latex/contrib/memoir}[memoir] \CTANdirectory{messtex}{support/messtex} \CTANdirectory{metafont}{systems/mac/metafont} @@ -608,6 +607,7 @@ \CTANdirectory{models}{macros/text1/models} \CTANdirectory{moderncv}{macros/latex/contrib/moderncv}[moderncv] \CTANdirectory{modes}{fonts/modes} +\CTANdirectory{morefloats}{macros/latex/contrib/morefloats}[morefloats] \CTANdirectory{moreverb}{macros/latex/contrib/moreverb}[moreverb] \CTANdirectory{mparhack}{macros/latex/contrib/mparhack}[mparhack] \CTANdirectory{mps2eps}{support/mps2eps} @@ -621,8 +621,8 @@ \CTANdirectory{multibib}{macros/latex/contrib/multibib}[multibib] \CTANdirectory{multirow}{macros/latex/contrib/multirow}[multirow] \CTANdirectory{musictex}{macros/musictex}[musictex] -\CTANdirectory{musixtex-egler}{macros/musixtex/egler} -\CTANdirectory{musixtex-taupin}{macros/musixtex/taupin}[musixtex] +\CTANdirectory{musixtex-egler}{obsolete/macros/musixtex/egler} +\CTANdirectory{musixtex}{macros/musixtex}[musixtex] \CTANdirectory{mutex}{macros/mtex} \CTANdirectory{mxedruli}{fonts/georgian/mxedruli} \CTANdirectory{nag}{macros/latex/contrib/nag}[nag] @@ -638,7 +638,7 @@ \CTANdirectory{nopageno}{macros/latex/contrib/nopageno}[nopageno] \CTANdirectory{norbib}{biblio/bibtex/contrib/norbib} \CTANdirectory{notoccite}{macros/latex/contrib/notoccite}[notoccite] -\CTANdirectory{noweb}{web/noweb} +\CTANdirectory{noweb}{web/noweb}[noweb] \CTANdirectory{nrc}{macros/latex/contrib/nrc} \CTANdirectory{ntg}{usergrps/ntg} \CTANdirectory{ntgclass}{macros/latex/contrib/ntgclass}[ntgclass] @@ -668,8 +668,10 @@ \CTANdirectory{pandora}{fonts/pandora} \CTANdirectory{paralist}{macros/latex/contrib/paralist}[paralist] \CTANdirectory{parallel}{macros/latex/contrib/parallel}[parallel] +\CTANdirectory{parskip}{macros/latex/contrib/parskip}[parskip] \CTANdirectory{passivetex}{macros/xmltex/contrib/passivetex}[passivetex] \CTANdirectory{patchcmd}{macros/latex/contrib/patchcmd}[patchcmd] +\CTANdirectory{path}{macros/generic/path}[path] \CTANdirectory{pbm2tex}{support/pbm2tex} \CTANdirectory{pbmtopk}{graphics/pbmtopk} \CTANdirectory{pbox}{macros/latex/contrib/pbox}[pbox] @@ -714,6 +716,7 @@ \CTANdirectory{preview}{macros/latex/contrib/preview}[preview] \CTANdirectory{print-fine}{support/print-fine} \CTANdirectory{printbib}{biblio/bibtex/utils/printbib} +\CTANdirectory{printlen}{macros/latex/contrib/printlen}[printlen] \CTANdirectory{printsamples}{fonts/utilities/mf2ps/doc/printsamples} \CTANdirectory{program}{macros/latex/contrib/program}[program] \CTANdirectory{proofs}{macros/generic/proofs} @@ -723,7 +726,7 @@ \CTANdirectory{prosper}{macros/latex/contrib/prosper}[prosper] \CTANdirectory{ps-type3}{fonts/cm/ps-type3} \CTANdirectory{ps2mf}{fonts/utilities/ps2mf} -\CTANdirectory{ps2pk}{fonts/utilities/ps2pk} +\CTANdirectory{ps2pk}{fonts/utilities/ps2pk}[ps2pk] \CTANdirectory{psbook}{systems/msdos/dviware/psbook} \CTANdirectory{psbox}{macros/generic/psbox} \CTANdirectory{pseudocode}{macros/latex/contrib/pseudocode}[pseudocode] @@ -865,7 +868,8 @@ \CTANdirectory{utopia}{fonts/utopia}[utopia] \CTANdirectory{varisize}{macros/plain/contrib/varisize}[varisize] \CTANdirectory{vc}{support/vc}[vc] -\CTANdirectory{verbdef}{macros/latex/contrib/verbdef} +\CTANdirectory{verbdef}{macros/latex/contrib/verbdef}[verbdef] +\CTANdirectory{vertbars}{macros/latex/contrib/vertbars}[vertbars] \CTANdirectory{vita}{macros/latex/contrib/vita}[vita] \CTANdirectory{vmargin}{macros/latex/contrib/vmargin}[vmargin] \CTANdirectory{vmspell}{support/vmspell}[vmspell] diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex index cbaf0bdca62..75c2064b556 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex @@ -1,4 +1,4 @@ -% $Id: faq-adj-types.tex,v 1.23 2010/08/12 18:14:24 rf10 Exp rf10 $ +% $Id: faq-adj-types.tex,v 1.28 2011/01/04 00:27:59 rf10 Exp rf10 $ \section{Adjusting the typesetting} @@ -1377,7 +1377,8 @@ Unfortunately, most of the core software predates \PDFTeX{}, so not even \PDFLaTeX{} sets the correct values into those variables, to match the paper size specified in a \csx{documentclass} option. -The \acro{DVI} drivers \ProgName{dvips} and \ProgName{dvipdfm} define +The \acro{DVI} drivers \ProgName{dvips}, \ProgName{dvipdfm} and its +extensions (\ProgName{dvipdfmx} and \ProgName{xdvipdfmx}) define \csx{special} commands for the document to specify its own paper size; so in those cases, as when \PDFTeX{} or V\TeX{} is being used, the paper size can be programmed by the document. Users who wish to, may @@ -1395,21 +1396,26 @@ engine, there are package options which instruct \Package{geometry} which \csx{special} commands to use. (Note that the options are ignored if you are using either \PDFLaTeX{} or V\TeX{}.) -So, the resolution of the problem is to add +So, the resolution of the problem, when you are using \latex{}, is to add \begin{quote} \begin{verbatim} -\usepackage[dvixxx,...]{geometry} +\usepackage[processor-option,...]{geometry} \end{verbatim} \end{quote} -(where \pkgoption{dvixxx} is your current favourite \acro{DVI} -driver~--- \Package{geometry} knows about \pkgoption{dvips} and -\pkgoption{dvipdfm}), and the document will run correctly with -\LaTeX{}. If you're using \PDFLaTeX{}, load with +Where \pkgoption{processor-option} tells the package what will produce +your (\PS{} or \acro{PDF} driver~--- \Package{geometry} knows about +\pkgoption{dvips} and \pkgoption{dvipdfm} (\pkgoption{dvipdfm} also +serves for the extension \ProgName{dvipdfmx} and +\ProgName{xdvipdfmx}). + +If you're using \PDFLaTeX{}, \xetex{} or V\TeX{}, load with \begin{quote} \begin{verbatim} -\usepackage[pdftex,...]{geometry} +\usepackage[program-option,...]{geometry} \end{verbatim} \end{quote} +where \pkgoption{program-option} is \pkgoption{pdftex}, +\pkgoption{xetex} or \pkgoption{vtex}. Needless to say, both the ``big'' classes (\Class{koma-script} and \Class{memoir}) provide their own ways to get the paper size @@ -1923,14 +1929,14 @@ are subverted by \environment{samepage}). Naturally, if \environment{samepage} \emph{does} work, it is capable of leaving stuff jutting out at the bottom of the page. -A convenient trick is to set all the relevant stuff in a \csx{parbox} -(or a \environment{minipage} if it contains things like verbatim text -that may not be in the argument of a \csx{parbox}). The resulting box -certainly \emph{won't} 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. +Another convenient trick is to set all the relevant stuff in a +\csx{parbox} (or a \environment{minipage} if it contains things like +verbatim text that may not be used in the argument of a \csx{parbox}). +The resulting box certainly \emph{won't} 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. -Why do neither of these obvious things work? Because \TeX{} can't +Why do neither of these obvious things work?~--- Because \TeX{} can't really distinguish between infinitely awful things. \environment{Samepage} will make any possible break point ``infinitely bad'' and boxes don't even offer the option of breaks, but if the @@ -2007,13 +2013,23 @@ 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 the rather few words he says on the subject in the \TeX{}book) one can decide, case by case, how to deal with problems at the last -proof-reading stage. The alternatives are to insert \csx{clearpage} -commands as necessary, or to use \csx{enlargethispage}. Supposing you -have a line or two that stray: issue the command -\cmdinvoke{enlargethispage}{2\csx{baselineskip}} and two lines are -added to the page you're typesetting. It depends on the document -whether this looks impossibly awful or entirely acceptable, but the -command remains a useful item in the armoury. +proof-reading stage. At this stage, you can manually alter page +breaking, using either \csx{pagebreak} or \csx{clearpage}, or you can +place a \csx{nopagebreak} command to suppress unfortunate breaks. +Otherwise, you can make small adjustments to the page geometry, using +\csx{enlargethispage}. Supposing you have a line or two that stray: +issue the command \cmdinvoke{enlargethispage}{2\csx{baselineskip}} and +two lines are added to the page you're typesetting. Whether this +looks impossibly awful or entirely acceptable depends on the document +context, but the command remains a useful item in the armoury. + +Note that both \csx{pagebreak} and \csx{nopagebreak} take an optional +number argument to adjust how the command is to be interpreted. Thus +\cmdinvoke{pagebreak}[0], the command `suggests' that a page break +might be worth doing, whereas \cmdinvoke{pagebreak}[4] `demands' a +page break. Similarly \cmdinvoke{nopagebreak}[0] makes a suggestion, +while \cmdinvoke{nopagebreak}[4] is a demand. In both commands, the +default value of the optional argument is 4. \begin{ctanrefs} \item[memoir.cls]\CTANref{memoir} \item[needspace.sty]\CTANref{needspace} @@ -2515,8 +2531,13 @@ Documentation is available on the % ! line break The \Package{minted} package is a relatively recent addition. It requires that documents be pre-processed using an external -(\ProgName{python}) script, % ! line break +(\ProgName{python}) script, \href{http://pygments.org/}{\ProgName{Pygments}}. +\ProgName{Pygments}, in turn, needs a ``lexer'' that knows the +language you want to process; lots of these are available, for the +more commonly-used languages, and there is advice on ``rolling your +own'' on the % ! line break. +<a href='http://pygments.org/docs/lexerdevelopment/'>\ProgName{Pygments} site</a> The \ProgName{lgrind} system is another well-established pre-compiler, with all the facilities one might need and a wide repertoire of @@ -2820,21 +2841,30 @@ developed Music\TeX{}, which allows the typesetting of polyphonic and other multiple-stave music; Music\TeX{} remains available, but is most definitely no longer recommended. -Music\TeX{} has been superseded by its successor MusiX\TeX{}, 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 Music\TeX{} -uses. Daniel Taupin's is the only version of MusiX\TeX{} currently -being developed (the original author, Andreas Egler, had an -alternative version, but he is now working on a different package -altogether). - -Input to Musix\TeX{} is extremely tricky stuff, and Don Simons' -preprocessor \ProgName{pmx} is the preferred method of creating input -for Taupin's version. \ProgName{Pmx} greatly eases use of -Musix\TeX{}, but it doesn't support the full range of Musix\TeX{}'s -facilities directly; however, it does allow in-line Musix\TeX{} code -in \ProgName{pmx} sources. +Music\TeX{} has been superseded by a further development called +MusiX\TeX{}, which is a three-pass system (with a processor program +that computes values for the element spacing in the music, and sorts +out spaces and ties (which Music\tex{} does ``woodenly''~--- playing +from a Music\tex{}-typeset page is entirely possible, but the look of +the slurs is very unsatisfying). Thus Musix\tex{} achieves finer +control than is possible with the unmodified \TeX{}-based mechanism +that Music\TeX{} uses. + +The original author of Musix\tex{}, Andreas Egler, withdrew from +development of the package; he has a further package Opus\tex{} (not +on \acro{CTAN}) which is focused on typesetting Gregorian chant and +the like. + +Daniel Taupin forked his development of MusiX\TeX{}, and his is the +only version currently maintained (by Daniel's successors, since +Daniel died). + +Input to MusiX\TeX{} is tricky stuff, and Don Simons' preprocessor +\ProgName{pmx} is the preferred method of creating input for Taupin's +version. \ProgName{Pmx} greatly eases use of MusiX\TeX{}, but it +doesn't support the full range of MusiX\TeX{}'s facilities directly; +however, it does allow in-line MusiX\TeX{} code in \ProgName{pmx} +sources. Dirk Laurie's \ProgName{M-Tx} allows preparation of music with lyrics; it operates ``on top of'' \ProgName{pmx} @@ -2853,14 +2883,14 @@ Music\TeX{} source code. There is a mailing list (\Email{TeX-music@icking-music-archive.org}) for discussion of typesetting music in \TeX{}; it mostly covers -Musix\TeX{} and related systems. To subscribe, use +MusiX\TeX{} and related systems. To subscribe, use \URL{http://icking-music-archive.org/mailman/listinfo/tex-music/} An alternative (free) means of embedding music examples into \AllTeX{} documents is \href{http://www.lilypond.org}{Lilypond}. Lilypond is (at heart) a batch music typesetting system with plain text input that does most of its work without TeX. Lilypond's input syntax is far -less cryptic than is Musix\TeX{}'s, and it handles much more stuff +less cryptic than is MusiX\TeX{}'s, and it handles much more stuff automatically, yielding the same or better quality with less effort. Lilypond can also produce basic \acro{MIDI} output. \begin{ctanrefs} @@ -2869,7 +2899,7 @@ Lilypond can also produce basic \acro{MIDI} output. \item[midi2tex]\CTANref{midi2tex} \item[musictex]\CTANref{musictex} % ! line breaks -\item[musixtex \nothtml{\rmfamily}(Taupin's version)]\CTANref{musixtex-taupin} +\item[musixtex \nothtml{\rmfamily}(Taupin's version)]\CTANref{musixtex} \item[musixtex \nothtml{\rmfamily}(Egler's version)]\CTANref{musixtex-egler} \item[mutex]\CTANref{mutex} \item[pmx]\CTANref{pmx} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex index 3612c0209ed..b1ba743417a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex @@ -1,4 +1,4 @@ -% $Id: faq-backgrnd.tex,v 1.5 2010/02/08 22:24:15 rf10 Exp $ +% $Id: faq-backgrnd.tex,v 1.10 2011/02/14 20:53:28 rf10 Exp $ \section{The Background} @@ -208,7 +208,7 @@ that you are likely to encounter: long-since-obsolete (since 1994) version (cf.~% \Qref[question]{What is \LaTeXe{}?}{Q-latex2e} for more information). - \item[\CONTeXT{} (executable: \ProgName{texexec})] + \item[\CONTeXT{} (executable: \ProgName{texmfstart})] See \Qref[question]{What is \CONTeXT{}?}{Q-context}. @@ -321,8 +321,10 @@ executable---probably \ProgName{latex} or \ProgName{pdflatex}---to produce an output file. The executable came bundled as part of a \TeX{} distribution such as \miktex{}, which includes various other \TeX{}-related components. -\LastEdit{2009-06-11} +This question is also covered in a page on the \acro{TUG} site, +``\href{http://tug.org/levels.html}{the Levels of \tex{}}''. +\LastEdit{2010-12-08} \Question[Q-triptrap]{How can I be sure it's really \TeX{}?} @@ -341,7 +343,7 @@ of tests to check that his software runs: those who port \TeX{} and its friends to other platforms do indeed perform such tests. Knuth, however, provides a `conformance test' for both \TeX{} -(\texttt{trip}) and \MF{} (\texttt{trap}). +(\Package{trip}) and \MF{} (\Package{trap}). %%% Is there a similar one for \MP{}? He characterises these as `torture tests': they are designed not to check the obvious things that ordinary typeset documents, or font @@ -349,12 +351,13 @@ 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! -Once an implementation of \TeX{} has passed its \texttt{trip} test, or an -implementation of \MF{} has passed its \texttt{trap} test, then it may -in principle be distributed as a working version. (In practice, any -distributor would test new versions against ``real'' documents or -fonts, too; \texttt{trip} and \texttt{trap} don't actually test any -for real world problems. +Once an implementation of \TeX{} has passed its \Package{trip} test, or +an implementation of \MF{} has passed its \Package{trap} test, then it +may in principle be distributed as a working version. (In practice, +any distributor would test new versions against ``real'' documents or +fonts, too; while \Package{trip} and \Package{trap} test bits of +pathways within the program, they don't actually test for any real +world problem.) \Question[Q-y2k]{Are \TeX{} and friends Y2K compliant?} @@ -473,7 +476,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 H\`an \The{} Th\`anh'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). @@ -620,6 +623,7 @@ Dutch, German, French, or Italian, and to use different typesetting engines (\PDFTeX{}, Xe\TeX{}, Aleph and \LuaTeX{}) without changing the user interface. \CONTeXT{} is developed rapidly, often in response to requests from the user community. +\LastEdit{2010-12-08} %%% RF's original version %% developed by Hans Hagen, originally to @@ -723,40 +727,6 @@ also a mailing list~--- sign up, or browse the list archives, via \item[\nothtml{\rmfamily}\Eplain{} distribution]\CTANref{eplain} \end{ctanrefs} -\Question[Q-lollipop]{What is Lollipop?} - -Lollipop is a macro package written by Victor Eijkhout; it was used in -the production of his book ``\emph{\TeX{} by Topic}'' (see -\Qref[question]{\AllTeX{} Tutorials}{Q-ol-books}). The manual says of -it: -\begin{quote} - Lollipop is `\TeX{} made easy'. Lollipop is a macro package that - functions as a toolbox for writing \TeX{} macros. It was my - intention to make macro writing so easy that implementing a fully - new layout in \TeX{} would become a matter of less than an hour for - 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. - - 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. -\end{quote} - -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{}\@ -\endhtmlignore -\begin{htmlversion} -it taking over from \LaTeX{} is detectable\dots{} -\end{htmlversion} -An article about Lollipop appeared in \TUGboat{} 13(3). -\begin{ctanrefs} -\item[\nothtml{\rmfamily}Lollipop distribution]\CTANref{lollipop} -\end{ctanrefs} - \Question[Q-texinfo]{What is Texinfo?} Texinfo is a documentation system that uses one source file to produce diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-biblio.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-biblio.tex index d27c54f6564..8f94cd6d17c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-biblio.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-biblio.tex @@ -1,4 +1,4 @@ -% $Id: faq-biblio.tex,v 1.8 2010/07/08 20:29:21 rf10 Exp rf10 $ +% $Id: faq-biblio.tex,v 1.10 2011/02/13 23:08:45 rf10 Exp $ \section{Bibliographies and citations} @@ -89,9 +89,8 @@ in this endeavour: \Question[Q-custbib]{Creating a bibliography style} It \emph{is} possible to write your own: the standard bibliography -styles are distributed in a commented form, and there is a description -of the language (see -% beware line-wrap +styles are distributed in a form with many comments, and there is a description +of the language in the \bibtex{} distribution (see % ! line wrap \Qref[question]{BibTeX documentation}{Q-BibTeXing}). However, it must be admitted that the language in which \BibTeX{} styles are written is pretty obscure, and one would not recommend @@ -105,8 +104,16 @@ to produce a file of instructions, with which you can generate your 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. + +An alternative, which is increassingly often recommended, to use +\Qref*{\Package{biblatex}}{Q-biblatex}. \Package{Biblatex} offers +many hooks for adjusting the format of the output of your `basic' +\bibtex{} style, and a collection of `contributed' styles have also +started to appear. \begin{ctanrefs} -\item[\nothtml{\normalfont}\BibTeX{} documentation]\CTANref{bibtex-doc} +\item[biblatex.sty]\CTANref{biblatex} +\item[biblatex \nothtml{\normalfont}contributed styles]\CTANref{biblatex-contrib} +\item[\nothtml{\normalfont}\BibTeX{} documentation]\CTANref{bibtex} \item[makebst.tex]Distributed with \CTANref{custom-bib} \end{ctanrefs} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-bits+pieces.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-bits+pieces.tex index 3bdf54ad03d..3f0a98bb4e3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-bits+pieces.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-bits+pieces.tex @@ -1,4 +1,4 @@ -% $Id: faq-bits+pieces.tex,v 1.6 2010/07/18 22:32:02 rf10 Exp rf10 $ +% $Id: faq-bits+pieces.tex,v 1.8 2011/02/13 23:08:45 rf10 Exp $ \section{Bits and pieces of \AllTeX{}} @@ -251,6 +251,120 @@ there is no device driver around. There \emph{is} a concept of \acro{PDF} specials, but in most cases \csx{special} will provoke a warning when used in \PDFTeX{}. +\Question[Q-write]{Writing (text) files from \tex{}} + +\TeX{} allows you to write to output files from within your document. +The facility is handy in many circumstances, but it is vital for +several of the things \latex{} (and indeed almost any higher-level +\tex{}-based macro package) does for you. + +The basic uses of writing to an external file are ``obvious''~--- +remembering titles of sections for a table of contents, remembering +label names and corresponding section or figure numbers, all for a +later run of your document. However, the ``non-obvious'' thing is +easy to forget: that page numbers, in \tex{}, are slippery beasts, and +have to be captured with some care. The trick is that \csx{write} +operations are only executed as the page is sent to the \acro{DVI} +or \acro{PDF} file. Thus, if you arrange that your page-number macro +(\csx{thepage}, in \latex{}) is not expanded until the page is +written, then the number written is correct, since that time is where +\tex{} guarantees the page number tallies with the page being sent +out. + +Now, there are times when you want to write something straight away: +for example, to interact with the user. \TeX{} captures that +requirement, too, with the primitive \csx{immediate}: +\begin{quote} +\begin{verbatim} +\immediate\write\terminal{I'm waiting...} +\end{verbatim} +\end{quote} +writes a ``computer-irritates-user'' message, to the terminal. + +Which brings us to the reason for that \csx{terminal}. \TeX{} can +``\csx{write}'' up to 16 streams simultaneously, and that argument to +\csx{write} says which is to be used. Macro packages provide the +means of allocating streams for your use: \plaintex{} provides a macro +\csx{newwrite}\csx{streamname}, which sets \csx{streamname} as +the stream number. In fact, \csx{terminal} (or its equivalent) is the +first output stream ever set up (in most macro packages): it is never +attached to a file, and if \tex{} is asked to write to \emph{any} +stream that isn't attached to a file it will send the output to the +terminal (and the log). + +\Question[Q-spawnprog]{Spawning programs from \AllTeX{}: \csx{write18}} + +The \tex{} \Qref*{\csx{write} primitive instruction}{Q-write} is used +to write to different file `streams'; TeX refers to each open file by +a number, not by a file name (although most of the time we hide this). +Originally, \tex{} would write to a file connected to a stream +numbered 0--15. More recently, a special ``stream 18'' has been +implemented: it is not writing to a file, but rather tells TeX to ask +the operating system to do something. To run a command, we put it as +the argument to \csx{write18}. So to run the \progname{epstopdf} +program on a file with name stored as \csx{epsfilename}, we would +write: +\begin{quote} +\begin{verbatim} +\write18{epstopf \epsfilename} +\end{verbatim} +\end{quote} +When using something like the \Package{epstopdf} package, the `stream' +write operation is hidden away and you don't need to worry about the +exact way it's done. + +However, there is a security issue. If you download some \alltex{} code from +the Internet, can you be sure that there is not some command in it +(perhaps in a hidden way) to do stuff that might be harmful to your +\acro{PC} (let's say: delete everything on the hard disk!)? In the +face of this problem, both \miktex{} and \tex{}~Live have, for some +time, disabled \csx{write18} by default. To turn the facility on, +both distributions support an additional argument when starting \tex{} +from the command shell: +\begin{quote} +\begin{verbatim} +(pdf)(la)tex --shell-escape <file> +\end{verbatim} +\end{quote} +The problem with this is that many people use \alltex{} via a graphical +editor, so to use \csx{write18} for a file the editor's settings must +be changed. Of course, the settings need restoring after the file is +processed: you defeat the point of the original protection, that way. + +The latest \miktex{} (version 2.9), and \tex{}~Live (2010 release) get +around this by having a special ``limited'' version of \csx{write18} +enabled `out of the box'. The idea is to allow only a pre-set list of +commands (for example, \BibTeX{}, \progname{epstopdf}, \tex{} itself, +and so on). Those on the list are regarded as safe enough to allow, +whereas anything else (for example deleting files) still needs to be +authorised by the user. This seems to be a good balance: most people +most of the time will not need to worry about \csx{write18} at all, +but it will be available for things like \Package{epstopdf}. + +Note that the \tex{} system may tell you that the mechanism is in use: +\begin{wideversion} +\begin{quote} +\begin{verbatim} +This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010) + restricted \write18 enabled. +\end{verbatim} +\end{quote} +\end{wideversion} +\begin{narrowversion} +\begin{quote} +\begin{verbatim} +This is pdfTeX, Version 3.1415926-1.40.11 + (TeX Live 2010) + restricted \write18 enabled. +\end{verbatim} +\end{quote} +\end{narrowversion} +when it starts. +\begin{ctanrefs} +\item[epstopdf.sty]Distributed with Heiko Oberdiek's packages + \CTANref{oberdiek} +\end{ctanrefs} + \Question[Q-hyphen]{How does hyphenation work in \TeX{}?} Everyone knows what hyphenation is: we see it in most books we read, @@ -627,7 +741,7 @@ Adobe has specified a number of formats for files to represent fonts in \PS{} files; this question doesn't attempt to be encyclopaedic, so we only discuss the two formats most commonly encountered in the \AllTeX{} context, types~1 and 3. In particular, we don't discuss the -OpenType format, whose has many advantages have only in the last year +OpenType format, whose many advantages have only in the last year or two been readily accessible to most \AllTeX{} users (by means of \begin{wideversion} the widely-used \Qref{\xetex{}}{Q-xetex} and the more experimental diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex index e85707b25f2..ddf243bb948 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-docs.tex @@ -1,4 +1,4 @@ -% $id:$ +% $Id: faq-docs.tex,v 1.15 2011/02/10 23:01:29 rf10 Exp rf10 $ \section{Documentation and Help} @@ -78,7 +78,7 @@ For \LaTeX{}, see: \item[The \LaTeX{} Graphics Companion:]% \emph{Illustrating documents with \TeX{} and \PS{}} by Michel Goossens, Sebastian Rahtz, Frank Mittelbach, Denis Roegel and - Herbert Vo\ss{} (second edition, Addison-Wesley, 2007, + 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 @@ -241,7 +241,7 @@ Both the Francophone \TeX{} user group Gutenberg and the Czech/Slovak user group CS-TUG have published translations of this \acro{FAQ}, with extensions appropriate to their languages. -Herbert Vo\ss{}'s excellent % beware line break +Herbert Vo\ss {}'s excellent % beware line break \href{http://texnik.de/}{\LaTeX{} tips and tricks} provides excellent advice on most topics one might imagine (though it's not strictly a \acro{FAQ})~--- highly recommended for most @@ -300,7 +300,7 @@ Each catalogue entry has a brief description of the package, and links to any known documentation on the net. In fact, a large proportion of \acro{CTAN} package directories now include documentation, so it's often worth looking at the catalogue entry for a package you're considering -using (where possible, each in package link in the main body of these +using (where possible, each package link in the main body of these \acro{FAQ}s \hyperflat{has a link to}{shows the \acro{URL} of} the relevant catalogue entry). @@ -310,7 +310,7 @@ newsgroup \Newsgroup{comp.text.tex} via \href{http://groups.google.com/group/comp.text.tex}{Google groups}, and the mailing list \texttt{texhax} via its \href{http://tug.org/pipermail/texhax/}{archive}, or (as a long shot) -the archives of ancient posts on \acro{CTAN}. +the archives of its ancient posts on \acro{CTAN}. If those ``back question'' searches fail, you'll have to ask the world at large. To ask a question on \Newsgroup{comp.text.tex}, you can use @@ -321,6 +321,13 @@ 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. +Other alternative sources are the % ! line break +\href{http://www.latex-community.org/}{``\LaTeX{} community'' site} or +\href{http://tex.stackexchange.com/}{\TeX{}, \LaTeX{} and friends Q\&A site}. +Neither of these is particularly long-established (the ``friends'' +site is still in \latexhtml{\ensuremath{\beta}-state}{beta state} at +the time of writing), but they're already popular and helpful. + Do \textbf{not} try mailing the % ! line break \Qref*{\LaTeX{} project team}{Q-LaTeX3}, the maintainers of the \texlive{} or \miktex{} distributions @@ -642,7 +649,7 @@ available (in several formats) via \URL{http://www.ams.org/tex/amslatex.html} (the ``Additional Documentation'' about half-way down the page. -Herbert Vo\ss{} has written an extensive guide to mathematics in +Herbert Vo\ss {} has written an extensive guide to mathematics in \LaTeX{} (a German version of which is published as a book). The guide is part of his ``\Qref*{tips and tricks}{Q-doc-dirs}'' and a copy is maintained on \acro{CTAN}. @@ -742,7 +749,7 @@ deparment's pages at \begin{ctanrefs} \item[\nothtml{\rmfamily}Graphics in \LaTeXe{}]\CTANref{epslatex} \item[testflow]\CTANref{testflow} -\item[\nothtml{\rmfamily}Herbert Vo\ss{}'s Maths tutorial]\CTANref{voss-mathmode} +\item[\nothtml{\rmfamily}Herbert Vo\ss {}'s Maths tutorial]\CTANref{voss-mathmode} \end{ctanrefs} \Question[Q-ref-doc]{Reference documents} @@ -765,20 +772,20 @@ basic \LaTeX{} use. (It's laid out very compactly for printing on N.\ American `letter'; printed on \acro{ISO} \acro{A}4, using Adobe Acrobat's ``shrink to fit'', it strains aged eyes\dots{}) -Similarly, there's no completely reliable command-organised reference -to \LaTeX{}. The page (provided by \acro{NASA}) % ! line break -\href{http://www.giss.nasa.gov/latex/}{Hypertext Help with LaTeX} is -recently much improved. It still talks in \LaTeXo{}-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. +For command organised references to \LaTeX{}, Karl Berry (et +al)'s % !line break +\href{http://home.gna.org/latexrefman}{LaTeX reference manual} is (to +an extent) work in progress, but is generally reliable. -Another \LaTeXe{} reference (provided by the Emerson Center of Emory -University) is: % ! line break +The reference provided by the Emerson Center of Emory +University), % ! line break \href{http://www.emerson.emory.edu/services/latex/latex2e/latex2e_toc.html}{LaTeXe help} +also looks good. \begin{ctanrefs} \item[\nothtml{\rmfamily}Cheat sheet]\CTANref{latexcheat} +\item[\nothtml{\rmfamily}LaTeX reference manual]\CTANref{latex2e-help-texinfo} \end{ctanrefs} +\LastEdit{2010-12-08} \Question[Q-doc-wiki]{\acro{WIKI} books for \TeX{} and friends} @@ -798,10 +805,12 @@ they both seem useful reference sources. \Question[Q-typo-style]{Typography tutorials} -Peter Wilson's manual for his \Class{memoir} 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 \AllTeX{} users. +Peter Wilson's article \Package{memdesign} 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 +\AllTeX{} users. (\Package{Memdesign} now distributed separately from +the manual for his \Class{memoir} class, but was originally part of +that manual) There's also (at least one) typographic style tutorial available on the Web, the excellent % ! line break @@ -816,7 +825,7 @@ ambition to supplant such excellent books as contain its Rutgers-local matter) is a fine introduction to the issues of producing readable documents. \begin{ctanrefs} -\item[memoir \nothtml{\rmfamily}distribution]\CTANref{memoir} +\item[memdesign]\CTANref{memdesign} \end{ctanrefs} \Question[Q-doc-dirs]{Directories of \AllTeX{} information} @@ -829,10 +838,6 @@ set comprises two parts, ``Text'' and ``Graphics'', so far. Once, there were other links like that, but all the others have faded away, leaving the \acro{TUG} India set in splendid isolation. -% Herbert Vo\ss{}'s excellent % beware line break -% \href{http://texnik.de/}{\LaTeX{} tips and tricks} is an excellent -% source of small articles on the use of \LaTeX{}. - \Question[Q-ol-books]{Freely available \AllTeX{} books} People have long argued for \AllTeX{} books to be made available on @@ -1039,33 +1044,34 @@ written more as a document, and presented in \acro{PDF}. \item[\nothtml{\rmfamily}Vincent Zoonekynd's examples]\CTANref{zoon-mp-eg} \end{ctanrefs} -\Question[Q-BibTeXing]{\BibTeX{} Documentation} +\Question[Q-BibTeXing]{\bibtex{} Documentation} -\BibTeX{}, a program originally designed to produce bibliographies in +\bibtex{}, a program originally designed to produce bibliographies in conjunction with \LaTeX{}, is explained in Section~4.3 and Appendix~B of Leslie Lamport's \LaTeX{} manual. -The document ``\BibTeX{}ing'', contained in the file \File{btxdoc.tex}, +The document ``\bibtex{}ing'', in the \bibtex{} distribution (look for +\File{btxdoc}), expands on the chapter in Lamport's book. \emph{The \LaTeX{} Companion} -also has information on \BibTeX{} and writing \BibTeX{} style files. +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 -\File{btxhak.tex}, explains the postfix stack-based language used to -write \BibTeX{} styles (\File{.bst} files). The file \File{btxbst.doc} +The document ``Designing \bibtex{} Styles'', also in the \bibtex{} +distribution (look for +\File{btxhak}, explains the postfix stack-based language used to +write \bibtex{} styles (\File{.bst} files). The file\File{btxbst.doc}, +also in the \bibtex{} distribution, 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}. +\Package{abbrv}, \Package{alpha}, and \Package{unsrt}); it also +contains their documentation. 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}. A summary and \acro{FAQ} -(\File{btxFAQ}), by Michael Shell and David Hoadley, is also to be -recommended. +may also be found on \acro{CTAN}. A summary and \acro{FAQ} by Michael +Shell and David Hoadley, is also to be recommended. \begin{ctanrefs} -\item[\nothtml{\rmfamily}\BibTeX{} documentation]\CTANref{bibtex-doc} -\item[btxFAQ.pdf]\CTANref{bibtex-faq} +\item[\nothtml{\rmfamily}\BibTeX{} distribution]\CTANref{bibtex} +\item[\nothtml{\rmfamily}Shell and Hoadley's FAQ]\CTANref{bibtex-faq} \item[\nothtml{\rmfamily}Tame the BeaST]\CTANref{ttb-pdf} \end{ctanrefs} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex index d4005502fd0..6ef86d322d0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex @@ -1,4 +1,4 @@ -% $Id: faq-fmt-conv.tex,v 1.1 2009/06/13 20:56:40 rf10 Exp $ +% $Id: faq-fmt-conv.tex,v 1.5 2011/02/08 22:17:17 rf10 Exp rf10 $ \section{Format conversions} @@ -186,7 +186,7 @@ For today, possible packages are: \ProgName{flex}. The distribution consists of a single \acro{C} source (or a compiled executable), which is easy to install and very fast-running. -\item[\ProgName{Tex4ht}]a compiled program that supports either +\item[\ProgName{TeX4ht}]a compiled program that supports either \LaTeX{} or \plaintex{}, by processing a \acro{DVI} file; it uses bitmaps for mathematics, but can also use other technologies where appropriate. Written by Eitan Gurari, it parses the \acro{DVI} @@ -220,7 +220,7 @@ The World Wide Web Consortium maintains a list of ``filters'' to \begin{ctanrefs} \item[latex2html]Browse \CTANref{latex2html} \item[plasTeX]Browse \CTANref{plastex} -\item[tex4ht]\CTANref{tex4ht} +\item[tex4ht]\CTANref{tex4ht} (but see \url{http://tug.org/tex4ht/}) \item[tth]\CTANref{tth} \end{ctanrefs} @@ -262,11 +262,25 @@ The World Wide Web Consortium maintains a list of ``filters'' to \TeX{}2\acro{RTF} is supported on various Unix platforms and under Windows~3.1 \item[Microsoft Word] A rudimentary (free) program for converting - MS-Word to \LaTeX{} is \ProgName{wd2latex}, which runs on \MSDOS{}. + \acro{MS-W}ord to \LaTeX{} is \ProgName{wd2latex}, which runs on \MSDOS{}; + it probably produces output destined for an archaic version of + \acro{MS-W}ord (the program itself was archived in 1991). + + The current preferred free-software method is a two-stage process: + \begin{itemize} + \item Convert \latex{} to \ProgName{OpenOffice} format, using the + \ProgName{tex4ht} command \ProgName{oolatex}; + \item open the result in \ProgName{OpenOffice} and `save as' a + \acro{MS-W}ord document. + \end{itemize} + (Note that \ProgName{OpenOffice} itself is \emph{not} on + \acro{CTAN}; see \url{http://www.openoffice.org/}, though most + \ProgName{linux} systems offer it as a ready-to-install bundle.) + \ProgName{Word2}\emph{\TeX{}} and \emph{\TeX{}}\ProgName{2Word} are shareware translators from % beware line break - \href{http://www.chikrii.com/}{Chikrii Softlab}; users' reports are - very positive. + \href{http://www.chikrii.com/}{Chikrii Softlab}; positive users' + reports have been noted (but not recently). The excellent \ProgName{tex4ht} will generate OpenOffice \acro{ODT} format, which can be used as an intermediate to producing Word @@ -319,6 +333,7 @@ translated to or from this one. \ProgName{FrameMaker} provides \item[rtf2latex2e]\CTANref{rtf2latex2e} \item[rtf2tex]\CTANref{rtf2tex} \item[tex2rtf]\CTANref{tex2rtf} +\item[tex4ht]\CTANref{tex4ht} (but see \url{http://tug.org/tex4ht/}) \item[tr2latex]\CTANref{tr2latex} \item[wd2latex]\CTANref{wd2latex} \item[wp2latex]\CTANref{wp2latex} @@ -330,13 +345,15 @@ translated to or from this one. \ProgName{FrameMaker} provides This can nowadays be done, with a certain amount of clever macro programming. David Carlisle's \Package{xmltex} is the prime example; -it offers a practical solution to typesetting -\acro{XML} files. +it offers a solution (of sorts) for typesetting \acro{XML} files. One use of a \TeX{} that can typeset \acro{XML} files is as a backend processor for \acro{XSL} formatting objects, serialized as \acro{XML}. Sebastian Rahtz's Passive\TeX{} uses \Package{xmltex} to achieve this end. + +However, modern usage would proceed via \acro{XSL} or \acro{XSLT}2 to +produce a formattable version. \begin{ctanrefs} \item[xmltex]\CTANref{xmltex} \item[passivetex]\CTANref{passivetex} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex index 87bb8025575..f420d621beb 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex @@ -1,260 +1,25 @@ -% $Id: faq-fonts.tex,v 1.8 2010/07/08 20:29:21 rf10 Exp rf10 $ +% $Id: faq-fonts.tex,v 1.12 2011/02/15 20:56:41 rf10 Exp rf10 $ \section{Fonts} -\subsection{\MF{} fonts} - -\Question[Q-useMF]{Getting \MF{} to do what you want} - -\MF{} allows you to create your own fonts, and most \TeX{} users -will never need to use it~--- modern \AllTeX{} systems contain -rather few \MF{} fonts of any significance, and when \MF{} output is -needed the font generation is done, automatically, ``on the fly''. - -If you find you have some special requirement that the system doesn't -satisfy, you need to know about \MF{} in rather more detail. \MF{}, -unlike \TeX{}, requires customisation for each output device: such -customisation is conventionally held in a ``mode'' associated with the -device. Modes are commonly defined using the \texttt{mode\_def} -convention described on page~94 of \emph{The \MF{}book} % ! line break -(see \Qref[question]{\TeX{}-related books}{Q-books}). You will need -a file, conventionally called \File{local.mf}, containing all the -\texttt{mode\_def}s you will be using. In the unlikely event that -\File{local.mf} doesn't already exist, Karl Berry's collection of -modes (\File{modes.mf}) is a good starting point -(it can be used as a `\File{local.mf}' without modification in a -typical modern implementation of \MF{}). Lists of -settings for various output devices are also published periodically in -\textsl{TUGboat} (see \Qref[question]{\acro{TUG}}{Q-TUG*}). Now create -a \texttt{plain} base file using \ProgName{mf} (in ``initialisation'' -mode), \texttt{plain.mf}, and \texttt{local.mf}: -\begin{htmlversion} -\begin{quote} -\begin{verbatim} -% mf -ini -This is METAFONT... -**plain # you type plain -(output) -*input local # you type this -(output) -*dump # you type this -Beginning to dump on file plain... -(output) -\end{verbatim} -\end{quote} -\end{htmlversion} -\htmlignore -\begin{list}{}{}\item\relax - \texttt{\% mf -ini}\\ - This is METAFONT\dots{}\\{} - \fullline{**\texttt{plain}\hss you type `\texttt{plain}'} - (\emph{output})\\{} - \fullline{*\texttt{input local}\hss you type this} - (\emph{output})\\{} - \fullline{*\texttt{dump}\hss you type this} - Beginning to dump on file plain\dots{}\\{} - (\emph{output}) -\end{list}\par -\endhtmlignore -This will create a base file named \File{plain.base} -(or something similar; for example, it will be \File{PLAIN.BAS} -on \MSDOS{} systems). Move the file to the directory containing -the base files on your system. - -Now you need to make sure \MF{} loads this new base when it starts up. If -\MF{} loads the \texttt{plain} base by default on your system, then you're -ready to go. Under Unix (using the default \texlive{} (and earlier) -distributions this does indeed happen, but we could for instance -define a command \ProgName{plainmf}% -\begin{footnoteenv} - On the grounds that a command \ProgName{plain} could be misconstrued - as a reference to \plaintex{} -\end{footnoteenv} -which executes `\texttt{mf -base=plain}' (or, in more traditional -style `\texttt{mf \&plain}') which loads the \texttt{plain} base -file. - -The usual way to create a font with \MF{} (with an appropriate base -file loaded) is to start \MF{}'s input with the -\begin{narrowversion} - lines - \begin{quote} - \csx{mode}\texttt{=<mode name>;}\\ - \texttt{mag=<magnification>;}\\ - \texttt{input <font file name>} - \end{quote} -\end{narrowversion} -\begin{wideversion} -line -\begin{verbatim} -\mode=<mode name>; mag=<magnification>; input <font file name> -\end{verbatim} -\end{wideversion} -in response to the `\texttt{**}' prompt or on the \MF{} command line. (If -\texttt{<mode name>} is unknown or omitted, the mode defaults to -`proof' mode and \MF{} will produce an output file called % ! line break -\File{<font file name>.2602gf}) -The \texttt{<magnification>} is a floating point number or -`magstep' (magsteps are defined in \emph{The \MF{}book} and -\emph{The \TeX{}book}). -If \texttt{mag=<magnification>} is omitted, then the default -is 1~(magstep 0). For example, to generate cmr10 at 12pt for an Epson -printer you might type -\begin{quote} -\begin{verbatim} -mf \mode=epson; mag=magstep 1; input cmr10 -\end{verbatim} -\end{quote} -Note that under Unix the \texttt{\textbackslash } and \texttt{;} -characters must usually be quoted or escaped, so this would typically -look something like -\begin{quote} -\begin{verbatim} - mf '\mode=epson; mag=magstep 1; input cmr10' -\end{verbatim} -\end{quote} -If you need a special mode that isn't in the base, you can put its -commands in a file (\emph{e.g.}, \File{ln03.mf}) and invoke it on the -fly with the \csx{smode} command. For example, to create -\File{cmr10.300gf} for an \acro{LN}03 printer, using the file -\begin{quote} -\begin{verbatim} -% This is ln03.mf as of 1990/02/27 -% mode_def courtesy of John Sauter -proofing:=0; -fontmaking:=1; -tracingtitles:=0; -pixels_per_inch:=300; -blacker:=0.65; -fillin:=-0.1; -o_correction:=.5; -\end{verbatim} -\end{quote} -(note the absence of the \texttt{mode\_def} and \texttt{enddef} -commands), you would type -\begin{quote} -\begin{verbatim} -mf \smode="ln03"; input cmr10 -\end{verbatim} -\end{quote} -This technique isn't one you should regularly use, but it may -prove useful if you acquire a new printer and want to experiment with -parameters, or for some other reason are regularly editing the -parameters you're using. Once you've settled on an appropriate set of -parameters, you should use them to rebuild the base file that you use. - -Other sources of help are discussed in our list of % ! line break -\Qref*{\MF{} and \MP{} Tutorials}{Q-mfptutorials}. -\begin{ctanrefs} -\item[modes.mf]\CTANref{modes-file} -\end{ctanrefs} - -\Question[Q-keepfonts]{Which font files should be kept} - -\MF{} produces from its run three files, a metrics (\acro{TFM}) file, a -generic font (\acro{GF}) file, and a log file; all of these files have the -same base name as does the input (\emph{e.g.}, if the input file was -\File{cmr10.mf}, the outputs will be \File{cmr10.tfm}, -\File{cmr10.nnngf}% -\begin{footnoteenv} - Note that the file name may be transmuted by such operating systems - as \MSDOS{}, which don't permit long file names -\end{footnoteenv} -and \File{cmr10.log}). - -For \TeX{} to use the font, you need a \acro{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 \acro{TFM} file; these files are -all the same, so you only need to keep one of them. - -To preview or to produce printed output, the \acro{DVI} processor will need a -font raster file; this is what the \acro{GF} file provides. However, while -there used (once upon a time) to be \acro{DVI} processors that could use -\acro{GF} files, modern processors use packed raster (\acro{PK}) files. -Therefore, you need to generate a \acro{PK} file from the \acro{GF} file; the -program \ProgName{gftopk} does this for you, and once you've done that you -may throw the \acro{GF} file away. - -The log file should never need to be used, unless there was some sort -of problem in the \MF{} run, and need not be ordinarily kept. - -\Question[Q-getbitmap]{Acquiring bitmap fonts} - -When \acro{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 \acro{CTAN}. -(There are separate sets for write-black and write-white printers, as -well as sets at 120~dpi and 240~dpi.) - -Over the years, there have been regular requests that \acro{CTAN} should hold -a wider range of resolutions, but they were resisted for two reasons: -\begin{itemize} -\item The need to decide which printers to generate fonts for. The - broad-brush approach taken for 300~dpi printers was (more or less) - justified back then, given the dominance of certain printer - `engines', but nowadays one could not make any such assumption. -\item Given the above, justifying the space taken up by a huge array - of bitmap fonts. -\end{itemize} -Fortunately, \AllTeX{} distribution technology has put a stop to these -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 \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, 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 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 released -for general public use by their originators \YandY{} and Bluesky Research, -in association with the \acro{AMS} and other scientific publishers -(they are nowadays available under the SIL's Open Fonts Licence). The -two sets contain slightly different ranges of fonts, but you are -advised to use the -\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*{``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]Distributed as part of - \CTANref{amsfonts} -\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} -\Question[Q-usepsfont]{Using \PS{} fonts with \protect\TeX{}} +\Question[Q-usepsfont]{Using Adobe Type 1 fonts with \protect\TeX{}} -In order to use \PS{} fonts, \TeX{} needs -\emph{metric} (called \acro{TFM}) files. Several sets of metrics are +In order to use any font, \TeX{} needs a +\emph{metric} file (\acro{TFM} file). Several sets of metrics for +common Adobe Type 1 fonts are available from the archives; for mechanisms for generating new ones, see \Qref[question]{metrics for \PS{} fonts}{Q-metrics}. You also need the fonts themselves; \PS{} printers come with a set of -fonts built in, but to extend your repertoire you almost invariably +fonts built in, but to extend your repertoire you usually need to buy from one of the many commercial font vendors (see, for example, \Qref[question]{``choice of fonts''}{Q-psfchoice}). -If you use \LaTeXe{}, the best way to get \PS{} fonts into your -document is to use the \acro{PSNFSS} package maintained by Walter -Schmidt. The \LaTeX{}3 project team declare that \acro{PSNFSS} is -``required'', and bug reports may be submitted via the % line break +If you use \LaTeXe{}, access to your printer's fonts is offered by the +\acro{PSNFSS} package; the \LaTeX{}3 project team declare that +\acro{PSNFSS} is a ``required'' part of a \latex{} distribution, and +bug reports may be submitted via the % ! line break \Qref*{\LaTeX{} bugs system}{Q-latexbug}. \acro{PSNFSS} gives you a set of packages for changing the default roman, sans-serif and typewriter fonts; \emph{e.g}., the @@ -280,60 +45,54 @@ redefine various macros and accents, or you can use the font re-encoding mechanisms available in many drivers and in \ProgName{ps2pk} and \ProgName{afm2tfm}. -Victor Eijkhout's \Qref*{Lollipop package}{Q-lollipop} -supports declaration of font families and styles in a similar way to -\LaTeX{}'s \acro{NFSS}, and so is easy to use with \PS{} fonts. - Some common problems encountered are discussed elsewhere (see \Qref[question]{problems with \acro{PS} fonts}{Q-psfontprob}). \begin{ctanrefs} \item[Metrics for the `Laserwriter' set of 35 fonts]\CTANref{lw35nfss-zip} -\item[lollipop]\CTANref{lollipop} \item[psnfss]\CTANref{psnfss} \end{ctanrefs} \Question[Q-PSpreview]{Previewing files using Type 1 fonts} -Until recently, free \TeX{} previewers have only been capable of -displaying bitmap \acro{PK} fonts, but current versions of -\ProgName{xdvi} sport a Type~1 font renderer. -%% \YandY{}'s commercial -%% previewer \Qref*{\acro{DVIW}indo}{Q-commercial} has in the past used -%% \ProgName{Adobe} \ProgName{Type} \ProgName{Manager} to display Type~1 -%% fonts directly and now uses the system-provided font renderer -%% available in Windows~2000 and~XP. - -Other (free) previewers of the current generation offer automatic -generation of the requisite \acro{PK} files (using \ProgName{gsftopk}, -or similar, behind the scenes). If your previewer isn't capable of -this, you have three options: +Originally, free \TeX{} previewers were only capable of displaying +bitmap (\acro{PK}) fonts, but free Type~1 font rendering software has +been available for some time, and many previewers now use such +facilities. + +The alternative, for previewers, is automatic generation of the +requisite \acro{PK} files (using \ProgName{gsftopk}, or similar, +behind the scenes). + +In the unlikely event that your previewer isn't capable of either, you +have a couple options: \begin{itemize} \item Convert the \acro{DVI} file to \PS{} and use a \PS{} previewer. Some systems offer this capability as standard, but most people will need to use a separate previewer such as \ProgName{ghostscript} or \ProgName{ghostscript}-based viewers such as \ProgName{gv} or shareware offering \ProgName{GSview}. -\item Under Windows on a \acro{PC}, or on a Macintosh, let Adobe Type Manager - display the fonts (textures, on the Macintosh, works like this). -%% , and under -%% Windows you can use \YandY{}'s \ProgName{dviwindo} for bitmap-free -%% previewing. -\begin{narrowversion} % really hyper - (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.) -\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 - \acro{PK} bitmap fonts which your previewer - will understand. This can produce excellent results, also suitable - for printing with non-\PS{} devices. Check the legalities of - this if you have purchased the fonts. +% \item Under Windows on a \acro{PC}, or on a Macintosh, let Adobe Type Manager +% display the fonts (textures, on the Macintosh, works like this). +% %% , and under +% %% Windows you can use \YandY{}'s \ProgName{dviwindo} for bitmap-free +% %% previewing. +% \begin{narrowversion} % really hyper +% (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.) +% \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 \acro{PK} bitmap fonts which + your previewer will understand (a process similar to the way some + browsers fo the job `automatically') This can produce excellent results, + also suitable for printing with non-\PS{} devices. (Note: if you + purchased the fonts, it is advisable to check that their licence + permits you to convert them, for private use, in this way.) \end{itemize} \begin{ctanrefs} \item[ghostscript]Browse \CTANref{ghostscript} @@ -341,10 +100,9 @@ this, you have three options: \item[GSview]Browse \CTANref{gsview} \item[gv]Browse \CTANref{gv} \item[ps2pk]\CTANref{ps2pk} -\item[xdvi]\CTANref{xdvi} \end{ctanrefs} -\Question[Q-metrics]{\protect\TeX{} font metric files for \PS{} fonts} +\Question[Q-metrics]{\TeX{} font metric files for Type 1 fonts} Reputable font vendors such as Adobe supply metric files for each font, in \acro{AFM} (Adobe Font Metric) form; these can be converted @@ -759,9 +517,9 @@ working on them, and several problems have been identified: \item[pxfonts set version 1.0](26 fonts) by Young Ryu\\ The \FontName{pxfonts} set consists of \begin{itemize} - \item virtual text fonts using \FontName{Adobe} \FontName{Palatino} (or the \acro{URW} - replacement used by \ProgName{ghostscript}) with modified plus, - equal and slash symbols; + \item virtual text fonts using \FontName{Adobe} \FontName{Palatino} + (or the \acro{URW} replacement used by \ProgName{ghostscript}) + with modified plus, equal and slash symbols; \item maths alphabets using \FontName{Palatino}; \item maths fonts of all symbols in the computer modern maths fonts (\FontName{cmsy}, \FontName{cmmi}, \FontName{cmex} and the Greek @@ -777,14 +535,11 @@ working on them, and several problems have been identified: \FontName{txfonts} set should be installed whenever \FontName{pxfonts} are. \LaTeX{}, \ProgName{dvips} and \PDFTeX{} support files are included. -\begin{narrowversion} % really non-hyper version - Documentation - (\URL{http://mirrors.ctan.org/fonts/pxfonts/doc/pxfontsdocA4.pdf}) -\end{narrowversion} -\begin{wideversion} - \href{http://mirrors.ctan.org/fonts/pxfonts/doc/pxfontsdocA4.pdf}{Documentation} -\end{wideversion} - is readily available. + + The fonts are not perfect; the widths assigned to the characters in + the \extension{tfm} file are wrong for some glyphs; this can cause + sequences of characters to ``look wrong'', or in some cases even to + overlap. The fonts are licensed under the \acro{GPL}; use in published documents is permitted. @@ -805,14 +560,11 @@ working on them, and several problems have been identified: \end{itemize} The text fonts are available in \acro{OT}1, \acro{T}1 and \acro{LY}1 encodings, and \acro{TS} encoded symbols are also available. -\begin{narrowversion} % really non-hyper version - Documentation - (\URL{http://mirrors.ctan.org/fonts/txfonts/doc/txfontsdocA4.pdf}) -\end{narrowversion} -\begin{wideversion} - \href{http://mirrors.ctan.org/fonts/txfonts/doc/txfontsdocA4.pdf}{Documentation} -\end{wideversion} - is readily available. + + The fonts are not perfect; the widths assigned to the characters in + the \extension{tfm} file are wrong for some glyphs; this can cause + sequences of characters to ``look wrong'', or in some cases even to + overlap. The fonts are licensed under the \acro{GPL}; use in published documents is permitted. @@ -820,13 +572,13 @@ working on them, and several problems have been identified: The \ProgName{txfontsb} bundles \ProgName{txfonts}, extended to provide a Small Caps set, Old-Style numbers and Greek text (from the GNU Freefont set). -\begin{narrowversion} % really non-hyper version +\begin{flatversion} Documentation (\URL{http://mirrors.ctan.org/fonts/txfontsb/doc/txfontsb/txfontsb.pdf}) -\end{narrowversion} -\begin{wideversion} +\end{flatversion} +\begin{hyperversion} \href{http://mirrors.ctan.org/fonts/txfontsb/doc/txfontsb/txfontsb.pdf}{Documentation} -\end{wideversion} +\end{hyperversion} is available for this variant, too. \end{booklist} Finally, one must not forget: @@ -854,12 +606,14 @@ The fonts may not render well (or at all, under \acro{ATM}), may not have the `standard' complement of 228 glyphs, or may not include metric files (which you need to make \acro{TFM} files). -TrueType remains the ``native'' format for Windows. Some \TeX{} +\ttype{} was for a long time the ``native'' format for Windows, but +MicroSoft joined the development of the \otype{} specification, and +`modern' windows will work happily with fonts in either format. Some \TeX{} implementations such as \Qref*{True\TeX{}}{Q-commercial} use TrueType versions of Computer Modern and Times Maths fonts to render \TeX{} documents in Windows without the need for additional system software like -\acro{ATM}. (When used on a system running Windows~XP, True\TeX{} can -also use Type~1 fonts.) +\acro{ATM}. (When used on a system running Windows~XP or later, +True\TeX{} can also use Adobe Type~1 fonts.) 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 @@ -1172,3 +926,237 @@ no support for using fonts according to the \acro{OT}1 encoding. \item[\nothtml{\rmfamily}Latin Modern fonts]\CTANref{lm} \end{ctanrefs} +\subsection{\MF{} fonts} + +\Question[Q-useMF]{Getting \MF{} to do what you want} + +\MF{} allows you to create your own fonts, and most \TeX{} users +will never need to use it~--- modern \AllTeX{} systems contain +rather few \MF{} fonts of any significance, and when \MF{} output is +needed the font generation is done, automatically, ``on the fly''. + +If you find you have some special requirement that the system doesn't +satisfy, you need to know about \MF{} in rather more detail. \MF{}, +unlike \TeX{}, requires customisation for each output device: such +customisation is conventionally held in a ``mode'' associated with the +device. Modes are commonly defined using the \texttt{mode\_def} +convention described on page~94 of \emph{The \MF{}book} % ! line break +(see \Qref[question]{\TeX{}-related books}{Q-books}). You will need +a file, conventionally called \File{local.mf}, containing all the +\texttt{mode\_def}s you will be using. In the unlikely event that +\File{local.mf} doesn't already exist, Karl Berry's collection of +modes (\File{modes.mf}) is a good starting point +(it can be used as a `\File{local.mf}' without modification in a +typical modern implementation of \MF{}). Lists of +settings for various output devices are also published periodically in +\textsl{TUGboat} (see \Qref[question]{\acro{TUG}}{Q-TUG*}). Now create +a \texttt{plain} base file using \ProgName{mf} (in ``initialisation'' +mode), \texttt{plain.mf}, and \texttt{local.mf}: +\begin{htmlversion} +\begin{quote} +\begin{verbatim} +% mf -ini +This is METAFONT... +**plain # you type plain +(output) +*input local # you type this +(output) +*dump # you type this +Beginning to dump on file plain... +(output) +\end{verbatim} +\end{quote} +\end{htmlversion} +\htmlignore +\begin{list}{}{}\item\relax + \texttt{\% mf -ini}\\ + This is METAFONT\dots{}\\{} + \fullline{**\texttt{plain}\hss you type `\texttt{plain}'} + (\emph{output})\\{} + \fullline{*\texttt{input local}\hss you type this} + (\emph{output})\\{} + \fullline{*\texttt{dump}\hss you type this} + Beginning to dump on file plain\dots{}\\{} + (\emph{output}) +\end{list}\par +\endhtmlignore +This will create a base file named \File{plain.base} +(or something similar; for example, it will be \File{PLAIN.BAS} +on \MSDOS{} systems). Move the file to the directory containing +the base files on your system. + +Now you need to make sure \MF{} loads this new base when it starts up. If +\MF{} loads the \texttt{plain} base by default on your system, then you're +ready to go. Under Unix (using the default \texlive{} (and earlier) +distributions this does indeed happen, but we could for instance +define a command \ProgName{plainmf}% +\begin{footnoteenv} + On the grounds that a command \ProgName{plain} could be misconstrued + as a reference to \plaintex{} +\end{footnoteenv} +which executes `\texttt{mf -base=plain}' (or, in more traditional +style `\texttt{mf \&plain}') which loads the \texttt{plain} base +file. + +The usual way to create a font with \MF{} (with an appropriate base +file loaded) is to start \MF{}'s input with the +\begin{narrowversion} + lines + \begin{quote} + \csx{mode}\texttt{=<mode name>;}\\ + \texttt{mag=<magnification>;}\\ + \texttt{input <font file name>} + \end{quote} +\end{narrowversion} +\begin{wideversion} +line +\begin{verbatim} +\mode=<mode name>; mag=<magnification>; input <font file name> +\end{verbatim} +\end{wideversion} +in response to the `\texttt{**}' prompt or on the \MF{} command line. (If +\texttt{<mode name>} is unknown or omitted, the mode defaults to +`proof' mode and \MF{} will produce an output file called % ! line break +\File{<font file name>.2602gf}) +The \texttt{<magnification>} is a floating point number or +`magstep' (magsteps are defined in \emph{The \MF{}book} and +\emph{The \TeX{}book}). +If \texttt{mag=<magnification>} is omitted, then the default +is 1~(magstep 0). For example, to generate cmr10 at 12pt for an Epson +printer you might type +\begin{quote} +\begin{verbatim} +mf \mode=epson; mag=magstep 1; input cmr10 +\end{verbatim} +\end{quote} +Note that under Unix the \texttt{\textbackslash } and \texttt{;} +characters must usually be quoted or escaped, so this would typically +look something like +\begin{quote} +\begin{verbatim} + mf '\mode=epson; mag=magstep 1; input cmr10' +\end{verbatim} +\end{quote} +If you need a special mode that isn't in the base, you can put its +commands in a file (\emph{e.g.}, \File{ln03.mf}) and invoke it on the +fly with the \csx{smode} command. For example, to create +\File{cmr10.300gf} for an \acro{LN}03 printer, using the file +\begin{quote} +\begin{verbatim} +% This is ln03.mf as of 1990/02/27 +% mode_def courtesy of John Sauter +proofing:=0; +fontmaking:=1; +tracingtitles:=0; +pixels_per_inch:=300; +blacker:=0.65; +fillin:=-0.1; +o_correction:=.5; +\end{verbatim} +\end{quote} +(note the absence of the \texttt{mode\_def} and \texttt{enddef} +commands), you would type +\begin{quote} +\begin{verbatim} +mf \smode="ln03"; input cmr10 +\end{verbatim} +\end{quote} +This technique isn't one you should regularly use, but it may +prove useful if you acquire a new printer and want to experiment with +parameters, or for some other reason are regularly editing the +parameters you're using. Once you've settled on an appropriate set of +parameters, you should use them to rebuild the base file that you use. + +Other sources of help are discussed in our list of % ! line break +\Qref*{\MF{} and \MP{} Tutorials}{Q-mfptutorials}. +\begin{ctanrefs} +\item[modes.mf]\CTANref{modes-file} +\end{ctanrefs} + +\Question[Q-keepfonts]{Which font files should be kept} + +\MF{} produces from its run three files, a metrics (\acro{TFM}) file, a +generic font (\acro{GF}) file, and a log file; all of these files have the +same base name as does the input (\emph{e.g.}, if the input file was +\File{cmr10.mf}, the outputs will be \File{cmr10.tfm}, +\File{cmr10.nnngf}% +\begin{footnoteenv} + Note that the file name may be transmuted by such operating systems + as \MSDOS{}, which don't permit long file names +\end{footnoteenv} +and \File{cmr10.log}). + +For \TeX{} to use the font, you need a \acro{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 \acro{TFM} file; these files are +all the same, so you only need to keep one of them. + +To preview or to produce printed output, the \acro{DVI} processor will need a +font raster file; this is what the \acro{GF} file provides. However, while +there used (once upon a time) to be \acro{DVI} processors that could use +\acro{GF} files, modern processors use packed raster (\acro{PK}) files. +Therefore, you need to generate a \acro{PK} file from the \acro{GF} file; the +program \ProgName{gftopk} does this for you, and once you've done that you +may throw the \acro{GF} file away. + +The log file should never need to be used, unless there was some sort +of problem in the \MF{} run, and need not be ordinarily kept. + +\Question[Q-getbitmap]{Acquiring bitmap fonts} + +When \acro{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 \acro{CTAN}. +(There are separate sets for write-black and write-white printers, as +well as sets at 120~dpi and 240~dpi.) + +Over the years, there have been regular requests that \acro{CTAN} should hold +a wider range of resolutions, but they were resisted for two reasons: +\begin{itemize} +\item The need to decide which printers to generate fonts for. The + broad-brush approach taken for 300~dpi printers was (more or less) + justified back then, given the dominance of certain printer + `engines', but nowadays one could not make any such assumption. +\item Given the above, justifying the space taken up by a huge array + of bitmap fonts. +\end{itemize} +Fortunately, \AllTeX{} distribution technology has put a stop to these +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 \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, 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 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 released +for general public use by their originators \YandY{} and Bluesky Research, +in association with the \acro{AMS} and other scientific publishers +(they are nowadays available under the SIL's Open Fonts Licence). The +two sets contain slightly different ranges of fonts, but you are +advised to use the \Package{bluesky} set except when \Package{bakoma} +is for some reason absolutely unavoidable. In recent years, several +other `\MF{}' fonts have been converted to Type~1 format; it's +uncommon ever to need to generate bitmap fonts for any purpose other +than previewing (see % ! line wrap +\Qref*{``previewing documents with Type~1 fonts''}{Q-PSpreview}), +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 with +wider ranges of glyphs to offer. +\begin{ctanrefs} +\item[\nothtml{\rmfamily}BaKoMa fonts]\CTANref{bakoma} +\item[\nothtml{\rmfamily}Bluesky fonts]Distributed as part of + \CTANref{amsfonts} +\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} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex index eac0022cce9..ded17f9673c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-graphics.tex @@ -1,4 +1,4 @@ -% $Id: faq-graphics.tex,v 1.5 2010/07/08 20:29:21 rf10 Exp rf10 $ +% $Id: faq-graphics.tex,v 1.10 2011/02/14 20:53:28 rf10 Exp $ \section{Graphics} @@ -201,7 +201,7 @@ An alternative solution is to use \ProgName{purifyeps}, a included directly. Sadly, \ProgName{purifyeps} doesn't work for all \extension{eps} files. -Good coverage of the problem is to be found in Herbert Vo\ss{}' +Good coverage of the problem is to be found in Herbert Vo\ss {}'s \href{http://pstricks.tug.org/main.cgi?file=pdf/pdfoutput}{\acro{PDF} support page}, which is targeted at the use of \Package{pstricks} in \PDFLaTeX{}, and also covers the \Package{pstricks}-specific package @@ -363,28 +363,36 @@ The alternative is to use the \Package{graphics} package command of the \Package{graphicx} and the \Package{epsfig} packages. The syntax of \csx{graphicspath}'s one argument is slightly odd: it's a sequence of paths (typically relative paths), each of which is -enclosed in braces. A slightly odd sample, given in the -\Package{graphics} bundle documentation, is: +enclosed in braces. A slightly odd example (slightly modified from one +given in the \Package{graphics} bundle documentation) is: \begin{quote} \begin{verbatim} -\graphicspath{{eps/}{tiff/}} +\graphicspath{{eps/}{png/}} \end{verbatim} \end{quote} -however, if the security checks on your \AllTeX{} system allow, the -path may be anything you choose (rather than strictly relative, like -those above); note that the trailing ``\texttt{/}'' \emph{is} required. +which will search for graphics files in subdirectories \File{eps} and +\File{png} of the directory in which \latex{} is running. (Note that +the trailing ``\texttt{/}'' \emph{is} required.) + +(Note that some \AllTeX{} systems will only allow you to use files in +the current directory and its sub-directories, for security reasons. +However, \csx{graphicspath} imposes no such restriction: as far as +\emph{it} is concerned, you can access files anywhere.) Be aware that \csx{graphicspath} does not affect the operations of graphics macros other than those from the graphics bundle~--- in particular, those of the outdated \Package{epsf} and \Package{psfig} packages are immune. -The disadvantage of the \csx{graphicspath} method is inefficiency. The -package will call \AllTeX{} 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. +The slight disadvantage of the \csx{graphicspath} method is +inefficiency. The package will call \AllTeX{} once for each entry in +the list to look for a file, which of course slows things. Further, +\AllTeX{} remembers the name of any file it's asked to look up, thus +effectively losing memory, so that in the limit a document that uses a +huge number of graphical inputs could be embarrassed by lack of +memory. (Such ``memory starvation'' is pretty unlikely with any +ordinary document in a reasonably modern \AllTeX{} system, but it +should be borne in mind.) If your document is split into a variety of directories, and each directory has its associated graphics, the \Package{import} package @@ -733,6 +741,10 @@ of drawing, and setup, here are a few systems you may consider: all the power of \MF{}, but it generates \PS{} figures; \MP{} is nowadays part of most serious \AllTeX{} distributions. Knuth uses it for all his work\dots{} + + Note that you can ``embed'' \MP{} source in your document (i.e., + keep it in-line with your \latex{} code), using the \Package{emp} + package. \item \ProgName{Mfpic}; you liked \MF{}, but can't understand the language? The package makes up \MF{} or \MP{} code for you within using familiar-looking \TeX{} macros. Not \emph{quite} the @@ -744,12 +756,48 @@ of drawing, and setup, here are a few systems you may consider: other \TeX{} drawing packages, but is an entirely new implementation, which is not as hard on memory, is much more readable (and is fully documented). +\item You fancy the idea of embedding the source of drawings (as with + \Package{emp}, but you like another drawing tool? In principle, + it's possible to do the same with other tools; for example + \Package{asyfig} allows you to embed % ! line break + \ProgName{asymptote} code in your document. \end{itemize} + +Some of the free-standing graphics applications may also be used +(effectively) in-line in \latex{} documents; examples are +\begin{booklist} +\item[asymptote]A package, \Package{asymptote}, defines an environment + \environment{asy} which arranges that its contents are included + (after ``enough'' runs, in the \latex{} way). + + Basically, you write + \begin{quote} + \cmdinvoke{begin}{asy} + \texttt{\meta{asymptote code}} + \cmdinvoke{end}{asy} + \end{quote} + and then execute +\begin{quote} +\begin{verbatim} +latex document +asy document-*.asy +latex document +\end{verbatim} +\end{quote} +\item[egplot]Allows you to incorporate \ProgName{\acro{GNU}plot} + code in your document, again for processing outside of \latex{}; the + design of this package was strongly influenced by that of \Package{emp} +\item[emp]Another of the same, this time for \MP{} graphics. +\end{booklist} \begin{ctanrefs} +\item[asymptote.sty]\CTANref{asymptote} \item[dratex.sty]\CTANref{dratex} +\item[egplot]\CTANref{egplot} +\item[emp]\CTANref{emp} \item[epic.sty]\CTANref{epic} \item[eepic.sty]\CTANref{eepic} \item[eepicemu.sty]\CTANref{eepic} +\item[emp.sty]\CTANref{emp} \item[mfpic]\CTANref{mfpic} \item[preview.sty]\CTANref{preview} \item[pspicture.sty]\CTANref{pspicture} @@ -854,7 +902,14 @@ 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. +The \Package{lpic} package is somewhat similar to \Package{overpic}; +it defines an environment \environment{lpic} (which places your +graphic for you): within the environment you may use the command +\csx{lbl} to position \latex{} material at appropriate places over the +graphic. + \Package{Pstricks} can of course do everything that \Package{overpic} +or \Package{lpic} can, with all the flexibility of \PS{} programming that it offers The \Package{pstricks} web site has a page with several % ! line break \href{http://pstricks.tug.org/main.cgi?file=Examples/overlay}{examples of labelling} @@ -870,6 +925,7 @@ with the do-it-yourself approach. \item[auto-pst-pdf.sty]\CTANref{auto-pst-pdf} \item[iTe]\CTANref{ite} \item[laprint]Distributed with \CTANref{psfragx} +\item[lpic.sty]\CTANref{lpic} \item[overpic.sty]\CTANref{overpic} \item[psfrag.sty]\CTANref{psfrag} \item[psfragx.sty]\CTANref{psfragx} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex index 6dfa7525cd6..ba0b48c2c66 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-how-do-i.tex @@ -1,4 +1,4 @@ -% $Id: faq-how-do-i.tex,v 1.16 2010/08/14 20:22:55 rf10 Exp rf10 $ +% $Id: faq-how-do-i.tex,v 1.24 2011/02/10 23:01:29 rf10 Exp rf10 $ \section{How do I do\dots{}?} @@ -1558,6 +1558,17 @@ in the neighbourhood of list environments (unless you change your good), the documentation is in German. Piet van Oostrum has written a summary in English. \end{description} +All of the above deal insertions at one or other margin; they are able +to take advantage of the \tex{} \csx{parshape} primitive that allows +you to adjust the margins of the text of a paragraph, by line (Knuth +provides an example of such use, with text typeset in a circle, +half-overlapping the margin, in chapter~14 of the \tex{}book). To +place insertions in the middle of a paragraph requires effort of an +entirely different sort; the \Package{cutwin} package does this for +you. It requires a set of ``part line widths'' (two per line), and +typesets the ``cutout'' section of the paragraph line by line. The +examples in the package documentation look enticing. + \plaintex{} users only have one option: \Package{figflow} (which doesn't work in \LaTeX{}). \Package{Figflow} only offers flowed figures at the start of the paragraph, but it seems perfectly @@ -1568,6 +1579,7 @@ functional. Syntax is (the user is responsible for having the dimensions correct, and for ensuring the figure fits on the page). \begin{ctanrefs} +\item[cutwin.sty]\CTANref{cutwin} \item[figflow.tex]\CTANref{figflow} \item[floatflt.sty]\CTANref{floatflt} \item[picins.sty]\CTANref{picins} @@ -1616,16 +1628,18 @@ package, and at least the picture quality will be improved. Documentation of \Package{slashbox} 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 -\acro{DVI} file that gives some idea of how the \csx{slashbox} may be -expected to look. (The third example in the file shows the effect of +package file in the distribution, and the distribution includes that +file processed to a \acro{PDF} file for reading over the net, if +necessary. (The third example in the file shows the effect of \environment{picture} mode's restrictions: the dividing line doesn't go from corner to corner in the box: to correct this requires revision of \Package{slashbox}~--- \Package{pict2e} alone doesn't help in this regard.) \begin{ctanrefs} +\item[pict2e.sty]\CTANref{pict2e} \item[slashbox.sty]\CTANref{slashbox} \end{ctanrefs} +\LastEdit{2010-11-02} \Question[Q-wholerow]{How to change a whole row of a table} @@ -1665,7 +1679,7 @@ than columns. So, we set things up by: \end{wideversion} \end{quote} Now, we put `\texttt{\$}' before the first column specifier; and we -put `\texttt{\textasciicircum{}}' +put `\texttt{\textasciicircum }' before the modifiers of subsequent ones. We then use \csx{rowstyle} at the start of each row we want to modify: \begin{quote} @@ -2009,7 +2023,7 @@ running off the end of the column at the end of the \Question[Q-dpfloat]{Facing floats on 2-page spread} -If a pair of floats are to be forced to form a 2-page spread (in a +If a pair of floats need 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 \Package{dpfloat} package provides for this: the construction to use is: @@ -2027,10 +2041,38 @@ this: the construction to use is: \end{figure} \end{verbatim} \end{quote} -The construction has no effect unless the standard class option -\pkgoption{twoside} is in effect. +The construction has no effect on documents with class option +\pkgoption{oneside} (\pkgoption{twoside} is the default for +\Class{book} class). + +A special case of this requirement places the caption for a float on +the next page. (This is useful if you have a float that ``only just'' +fits the page.) You can (with a certain amount of twiddling) make +this work with \Package{dpfloat}, but the \Package{fltpage} package is +specially designed for the job: +\begin{quote} +\begin{verbatim} +\documentclass[twoside]{article} +\usepackage[leftFloats]{fltpage} +\begin{document} +... +\begin{FPfigure} + \includegraphics{my-huge-figure} + \caption{Whew! That was a big one!} +\end{FPfigure} +... +\end{document} +\end{verbatim} +\end{quote} +That example should produce a caption +\begin{quote} + Figure \emph{n (facing page)}: Whew! \dots{} +\end{quote} +(Note, however, that the package is an old one, and declares itself to +be a beta release. I seems to work, but\dots{}) \begin{ctanrefs} \item[dpfloat.sty]\CTANref{dpfloat} +\item[fltpage.sty]\CTANref{fltpage} \end{ctanrefs} \Question[Q-vertposfp]{Vertical layout of float pages} @@ -2532,93 +2574,114 @@ since the syntax of the \csx{input} command is so peculiar. In the case of \LaTeX{}, the input commands have pretty regular syntax, and the simplest \Qref*{patching techniques}{Q-patch} can be -used on them. - -If you're not inputting things from a file that's already been input, -the job is almost trivial: -\begin{quote} -\begin{verbatim} -\def\ThisFile{\jobname} -\let\OldInput\input -\renewcommand{\input}[1]{% - \renewcommand{\ThisFile}{#1}% - \OldInput#1% -} -\end{verbatim} -\end{quote} -With that, the macro \csx{ThisFile} always contains the last thing -input: it starts pointing at the base file of your document -(\csx{jobname}), and thereafter changes every time you use -\cmdinvoke*{input}{file}. Note that this is not satisfactory if your -document contains things \emph{other} than \csx{input} commands. For -example, in: -\begin{quote} -\begin{verbatim} -\documentclass{article} -... (macros above) -\begin{document} -\input{preamble} -<body of document> -\input{postamble} -\end{document} -\end{verbatim} -\end{quote} -\csx{ThisFile} contains \texttt{postamble} throughout the % !line break -\meta{body of document}. - -Most ordinary users will quickly become irritated with the simplicity -of of the \csx{ThisFile} 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 \csx{ThisFile} to what the -previous file was before returning. -\begin{quote} -\begin{verbatim} -\def\ThisFile{\jobname} -\newcounter{FileStack} -\let\OrigInput\input -\renewcommand{\input}[1]{% - \stackinput{#1}{\OrigInput}% -} -\newcommand{\stackinput}[2]{% - \stepcounter{FileStack}% - \expandafter\let - \csname NameStack\theFileStack\endcsname - \ThisFile - \def\ThisFile{#1}% - #2#1% - \expandafter\let\expandafter - \ThisFile - \csname NameStack\theFileStack\endcsname - \addtocounter{FileStack}{-1}% -} -\end{verbatim} -\end{quote} -To do the same for \csx{include}, we need the simple addition: -\begin{quote} -\begin{verbatim} -\let\OrigInclude\include -\renewcommand{\include}[1]{% - \stackinput{#1}{\OrigInclude}% -} -\end{verbatim} -\end{quote} -Both examples of patching \csx{input} assume you always use -\LaTeX{} syntax, i.e., always use braces around the argument. +used on them. (Note that latex{}'s \csx{input} command is itself a +patch on top of the \plaintex{} command. Our patches apply to the +\latex{} version of the command, which is used as \cmdinvoke*{input}{file}) -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 `\extension{tex}'), use the commands: -\begin{quote} -\begin{verbatim} -\def\striptexext#1.tex{#1} -... -\edef\ThisFile{\expandafter\stripext\finkfile} -\end{verbatim} -\end{quote} +%% If you only have one level of input (you never input things from a +%% file that was itself input), the job is almost trivial: +%% \begin{quote} +%% \begin{verbatim} +%% \def\ThisFile{\jobname} +%% \let\OldInput\input +%% \renewcommand{\input}[1]{% +%% \renewcommand{\ThisFile}{#1}% +%% \OldInput#1% +%% } +%% \end{verbatim} +%% \end{quote} +%% With that, the macro \csx{ThisFile} always contains the last thing +%% input: it starts pointing at the base file of your document +%% (\csx{jobname}), and thereafter changes every time you use +%% \cmdinvoke*{input}{file}. Note that this is not satisfactory if your +%% document contains things \emph{other} than \csx{input} commands. For +%% example, in: +%% \begin{quote} +%% \begin{verbatim} +%% \documentclass{article} +%% ... (macros above) +%% \begin{document} +%% \input{preamble} +%% <body of document> +%% \input{postamble} +%% \end{document} +%% \end{verbatim} +%% \end{quote} +%% \csx{ThisFile} contains ``\texttt{preamble}'' throughout the % !line break +%% \meta{body of document}. + +%% Most ordinary users will quickly become irritated with the simplicity +%% of of the \csx{ThisFile} 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 \csx{ThisFile} to what the +%% previous file was before returning. +%% \begin{quote} +%% \begin{verbatim} +%% \def\ThisFile{\jobname} +%% \newcounter{FileStack} +%% \let\OrigInput\input +%% \renewcommand{\input}[1]{% +%% \stackinput{#1}{\OrigInput}% +%% } +%% \newcommand{\stackinput}[2]{% +%% \stepcounter{FileStack}% +%% \expandafter\let +%% \csname NameStack\theFileStack\endcsname +%% \ThisFile +%% \def\ThisFile{#1}% +%% #2#1% +%% \expandafter\let\expandafter +%% \ThisFile +%% \csname NameStack\theFileStack\endcsname +%% \addtocounter{FileStack}{-1}% +%% } +%% \end{verbatim} +%% \end{quote} +%% To do the same for \csx{include}, we need the simple addition: +%% \begin{quote} +%% \begin{verbatim} +%% \let\OrigInclude\include +%% \renewcommand{\include}[1]{% +%% \stackinput{#1}{\OrigInclude}% +%% } +%% \end{verbatim} +%% \end{quote} +%% Remember, both examples of patching \csx{input} assume you always use +%% \LaTeX{} syntax, i.e., always use braces around the argument. + +It is possible to keep track of the name of the file currently being +processed, but it's surprisingly difficult (these \acro{FAQ}s offered +code, for a long time, that just didn't work in many cases). + +The \Package{currfile} package provides a regular means of keeping +track of the details of the current file (its name in +\csx{currfilename}, directory in \csx{currfiledir}, as well as the +file `base' name (less its extension) and its extension). +\Package{Currfile} does this with the help of a second package, +\Package{filehook}, which spots file operations that use \csx{input}, +\csx{InputIfFileExists} and \csx{include}, as well as package and +class loading. + +The \Package{FiNK} (``File Name Keeper'') package keeps track of the +file name and extension, in a macro \csx{finkfile}. \Package{FiNK} is +now deprecated, in favour of \Package{currfile}, but remains available +for use in old documents. +% +%% If you need the +%% unadorned file name (without its `\extension{tex}'), use the commands: +%% \begin{quote} +%% \begin{verbatim} +%% \def\striptexext#1.tex{#1} +%% ... +%% \edef\ThisFile{\expandafter\stripext\finkfile} +%% \end{verbatim} +%% \end{quote} +% The \Package{FiNK} bundle includes a \File{fink.el} that provides support under \ProgName{emacs} with \acro{AUC}-\TeX{}. \begin{ctanrefs} +\item[currfile.sty]\CTANref{currfile} +\item[filehook.sty]\CTANref{filehook} \item[fink.sty]\CTANref{fink} \end{ctanrefs} @@ -3033,8 +3096,8 @@ following minimal solution: \begin{wideversion} \begin{verbatim} \def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}} -\RCS$Revision: 1.16 $ % or any RCS keyword -\RCS$Date: 2010/08/14 20:22:55 $ +\RCS$Revision: 1.24 $ % or any RCS keyword +\RCS$Date: 2011/02/10 23:01:29 $ ... \date{Revision \RCSRevision, \RCSDate} \end{verbatim} @@ -3044,8 +3107,8 @@ following minimal solution: \def\RCS$#1: #2 ${\expandafter \def\csname RCS#1\endcsname{#2}% } -\RCS$Revision: 1.16 $ % or any RCS keyword -\RCS$Date: 2010/08/14 20:22:55 $ +\RCS$Revision: 1.24 $ % or any RCS keyword +\RCS$Date: 2011/02/10 23:01:29 $ ... \date{Revision \RCSRevision, \RCSDate} \end{verbatim} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex index cd2341c6cd2..63656fccd22 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-install.tex @@ -1,4 +1,4 @@ -% $Id: faq-install.tex,v 1.8 2009/12/25 00:29:51 rf10 Exp $ +% $Id: faq-install.tex,v 1.9 2011/02/15 20:56:41 rf10 Exp rf10 $ \section{Installing \AllTeX{} files} @@ -854,7 +854,7 @@ much of what follows will be familiar: \end{verbatim} but if you are lucky, you will be starting from a distribution from \acro{CTAN} and there is a corresponding \extension{tds.zip} file: - using the \acro{TDS}-file saves the bother of deciding where to put + using this \acro{TDS}-file saves the bother of deciding where to put your files in the \acro{TDS} tree. \item Regenerate the file indexes (as described in \Qref[question]{package installation}{Q-inst-wlcf}). @@ -867,9 +867,11 @@ much of what follows will be familiar: updmap-sys --enable Map <fname>.map \end{verbatim} \end{quote} - as root. (Do \emph{not} use plain \ProgName{updmap}: it's a - potent source of confusion, setting up different map sets - for different users.) + as root. (If you \emph{can} use \ProgName{updmap-sys}~--- do; if + not~--- presumably because your \alltex{} system was set up by + someone else~--- you have to fall back on plain \ProgName{updmap}, + but be aware that it's a potent source of confusion, setting up + map sets that might be changed behind your back.) \item On a current \miktex{} system, update the system file \File{updmap.cfg}, using the shell command \begin{quote} @@ -921,16 +923,15 @@ at a ``command prompt'' (\ProgName{shell}, in a Unix-style system, If the command works at all, the console output of the command will include a sequence of Type~1 font file names, listed as -\texttt{<cmr10.pfb>} and so on; this is \ProgName{dvips} telling you -it's copying information from the Type~1 font, and you need do no -more. +\texttt{<\emph{path}/cmr10.pfb>} and so on; this is \ProgName{dvips} +telling you it's copying information from the Type~1 font, and you +need do no more. If the test has failed, you need to install your own set of the fonts; the distribution (including all the fonts the \acro{AMS} designed and produced themselves) is now described as \Package{amsfonts}. The bundle contains metric and map files~--- all you need to \Qref*{install the fonts}{Q-instt1font}. - \begin{ctanrefs} \item[AMS and CM fonts, in Type 1 format]\CTANref{amsfonts} \end{ctanrefs} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex index f615d7100b1..3deb4b4dead 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-intro.tex @@ -1,4 +1,4 @@ -% $Id: faq-intro.tex,v 1.17 2010/08/16 22:04:13 rf10 Exp rf10 $ +% $Id: faq-intro.tex,v 1.17 2010/09/01 17:30:33 rf10 Exp rf10 $ % this environment is for the benefit of new-style file generation \begin{introduction} @@ -162,12 +162,14 @@ Mike Vulis, % details of micropress offerings Chris Walker, % revtex alert, ite suggestion (q-labelfig) Peter Wilson, % several, incl functionality of memoir Joseph Wright, % help with keyval, l3keys, etc. -Rick Zaccone and +Rick Zaccone, +Gregor Zattler % typo spotted +and Reinhard Zierke. -That list does \emph{not} cover the many people whose ideas I have +That list does \emph{not} cover the many people whose ideas were encountered on various lists, newsgroups or (lately) web forums. Many -such people have helped me, perhaps simply to alert me to an area in -which I need to work. +such people have helped, even if simply to highlight an area in which +\acro{FAQ} work would be useful. \endhtmlignore \end{introduction} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex index 76ff3fc3a98..16518615c1c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex @@ -1,4 +1,4 @@ -% $Id: faq-jot-err.tex,v 1.5 2010/08/16 22:04:13 rf10 Exp rf10 $ +% $Id: faq-jot-err.tex,v 1.7 2010/10/06 20:51:19 rf10 Exp rf10 $ \section{The joy of \TeX{} errors} @@ -463,91 +463,116 @@ character by the time the hyphenation gets to look at it. If \LaTeX{} responds to a \cmdinvoke{begin}{figure} or \cmdinvoke{begin}{table} command with the error message -\begin{htmlversion} -\begin{verbatim} -! LaTeX Error: Too many unprocessed floats. - -See the LaTeX manual or LaTeX Companion for explanation. -\end{verbatim} -\end{htmlversion} -\htmlignore -\ifpdf +\begin{quote} +\begin{wideversion} \begin{verbatim} ! LaTeX Error: Too many unprocessed floats. See the LaTeX manual or LaTeX Companion for explanation. \end{verbatim} -\else +\end{wideversion} +\begin{narrowversion} \begin{verbatim} ! LaTeX Error: Too many unprocessed floats. See the LaTeX manual or LaTeX Companion -... for explanation. +... for explanation. \end{verbatim} -\fi -\endhtmlignore -your figures (or tables) are failing to be placed properly. \LaTeX{} +\end{narrowversion} +\end{quote} +your figures (or tables) are not being placed properly. \LaTeX{} has a limited amount of storage for `floats' (figures, tables, or floats you've defined yourself with the \Package{float} package); if -you don't let it ever actually typeset any floats, it will run out of -space. +something you have done has prevented \latex{} from typesetting +floats, it will run out of storage space. -This failure usually occurs in extreme cases of -% beware line break -\nothtml{floats moving ``wrongly'' (see }% -\Qref[question]{floats moving ``wrongly''}{Q-floats}\latexhtml{);}{;} +This failure usually occurs in extreme cases of % ! line break +\Qref*{floats moving ``wrongly''}{Q-floats}; \LaTeX{} has found it can't place a float, and floats of the same type -have piled up behind it. \LaTeX{}'s idea is to ensure that caption -numbers are sequential in the document: the caption number is -allocated when the figure (or whatever) is created, and can't be -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. - -Techniques for solving the problem are discussed in the -\nothtml{floats question (}% -\Qref[\htmlonly]{floats question}{Q-floats}\nothtml{)} -already referenced. - -The error also occurs in a -long sequence of \environment{figure} or \environment{table} -environments, with no intervening -text. Unless the environments will fit ``here'' (and you've allowed -them to go ``here''), there will never be a page break, and so there -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. +have piled up behind it. + +How does this happen?~--- \LaTeX{} guarantees that caption numbers are +sequential in the document, but the caption number is allocated when +the figure (or whatever) is created, and can't be changed. Thus, if +floats are placed out of order, their caption numbers would also +appear out of order in the body of the document (and in the list of +figures, or whatever). As a result, enforcement of the guarantee +means that simple failure to place a float means that no subsequent +float can be placed; and hence (eventually) the error. + +Techniques for solving the problem are discussed in the % ! line break +\Qref*{floats question}{Q-floats} already referenced. + +An alternative \emph{may} be to use the \Package{morefloats} package. +The package will allocate more ``float skeletons'' than \latex{} +does by default; each such skeleton may then be used to store a +float. Beware that even with \Package{morefloats}, the number you can +allocate is limited; even with the \Package{etex} package (which makes +available many more registers, etc., than \latex{} does by default; +\etex{} can create lots more registers, but none of those ``beyond +the original \TeX{} default'' may be used in float skeletons). Thus, +\Package{etex} may offer some relief, but it can \emph{not} be +regarded as a panacea + +The error also occurs in a long sequence of float environments, with +no intervening text. Unless the environments will fit ``here'' (and +you've allowed them to go ``here''), there will never be a page break, +and so there 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. Techniques for resolution may involve redefining the floats using the \Package{float} package's \texttt{[H]} float qualifier, but you are unlikely to get away without using \csx{clearpage} from time to time. \begin{ctanrefs} \item[float.sty]\CTANref{float} +\item[morefloats.sty]\CTANref{morefloats} \end{ctanrefs} \Question[Q-atvert]{\csx{spacefactor} complaints} The errors +\begin{quote} +\begin{narrowversion} +\begin{verbatim} +! You can't use `\spacefactor' in +... vertical mode. +\@->\spacefactor + \@m +\end{verbatim} +\end{narrowversion} +\begin{wideversion} \begin{verbatim} ! You can't use `\spacefactor' in vertical mode. \@->\spacefactor \@m \end{verbatim} +\end{wideversion} +\end{quote} or +\begin{quote} \begin{verbatim} ! You can't use `\spacefactor' in math mode. \@->\spacefactor \@m \end{verbatim} +\end{quote} or simply +\begin{quote} \begin{verbatim} ! Improper \spacefactor. ... \end{verbatim} -bites the \LaTeX{} programmer who uses an internal command without taking -``precautions''. The problem is discussed in detail in +\end{quote} +bite the \LaTeX{} programmer who uses an internal command without +taking ``precautions''. An internal-style command such as \csx{@foo} +has been defined or used in a private macro, and it is interpreted as +\csx{@}, followed by the `text' \texttt{foo}. (\csx{@} is used, for +real, to set up end-of-sentence space in some circumstances; it uses +\csx{spacefactor} to do that.) + +The problem is discussed in detail in % beware line wrap ``\Qref*[question]{\texttt{@} in macro names}{Q-atsigns}'', together with solutions. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-litprog.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-litprog.tex index 06b0c348412..96fe03cfa38 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-litprog.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-litprog.tex @@ -1,4 +1,4 @@ -% $Id: faq-litprog.tex,v 1.1 2009/06/13 20:56:39 rf10 Exp $ +% $Id: faq-litprog.tex,v 1.2 2011/02/10 23:04:12 rf10 Exp rf10 $ \section{Literate programming} @@ -41,6 +41,10 @@ outlining the programming techniques, may be had from \acro{CTAN}. \acro{\ProgName{CWEB}}, by Silvio Levy, is a \acro{WEB} for \acro{C} programs. +\acro{\ProgName{FWEB}}, by John Krommes, is a version for Fortran, +Ratfor,\acro{C}, \acro{C}++, working with \latex{}; it was derived +from \ProgName{CWEB}. + Spidery \acro{WEB}, by Norman Ramsey, supports many languages including Ada, \texttt{awk}, and \acro{C} and, while not in the public domain, is usable without charge. It is @@ -48,9 +52,6 @@ now superseded by \ProgName{noweb} (also by Norman Ramsay) which incorporates the lessons learned in implementing spidery \acro{WEB}, and which is a simpler, equally powerful, tool. -\acro{\ProgName{FWEB}}, by John Krommes, is a version for Fortran, -Ratfor, and \acro{C}. - \ProgName{Scheme}\acro{\ProgName{WEB}}, by John Ramsdell, is a Unix filter that translates Scheme\acro{WEB} into \LaTeX{} source or Scheme source. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex index 1d6cb2c2aeb..d2e379eed88 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-mac-prog.tex @@ -1,4 +1,4 @@ -% $Id: faq-mac-prog.tex,v 1.12 2010/04/12 22:33:01 rf10 Exp rf10 $ +% $Id: faq-mac-prog.tex,v 1.13 2011/02/13 23:08:45 rf10 Exp $ \section{Macro programming} @@ -1375,11 +1375,43 @@ lamented Mike Downes. \item[memoir.cls]\CTANref{memoir} \end{ctanrefs} -\Question[Q-ifpdf]{Am I using \PDFTeX{}?} +\Question[Q-whatengine]{Am I using \pdftex{}, \xetex{} or \luatex{}?} +\AliasQuestion{Q-ifpdf} -It's often useful to know whether your macros are operating within -\PDFTeX{} or within (``normal'') \TeX{}; getting the right answer is -surprisingly tricky. +You often need to know what ``engine'' your macros are running on (the +engine is the \tex{}-derivative or \tex{}-alike processor that +typesets your document). The reason that you need to know is that the +set of functions available in each engine is different. Thus, for +\tex{} macros to run on any engine, they need to ``know'' what they +can and cannot do, which depends on the engine in use. Getting the +right answer is surprisingly tricky (see below for an elaboration of +one apparently simple test). + +There is now a comprehensive set of packages that answer the question +for you. They all create a \tex{} conditional command: +\begin{itemize} +\item \Package{ifpdf} creates a command \csx{ifpdf}, +\item \Package{ifxetex} creates a command \csx{ifxetex} and +\item \Package{ifluatex} creates a command \csx{ifluatex}. +\end{itemize} +These \tex{} commands may be used within the \latex{} conditional +framework, as (for example): +\begin{quote} + \csx{ifthenelse}\texttt{\char`\{}\cmdinvoke{boolean}{pdf}\texttt{\char`\}\char`\{\meta{if pdf}\char`\}\char`\{\meta{not pdf}\char`\}} +\end{quote} + +The \Package{ifxetex} package also provides a command +\csx{RequireXeTeX} which creates an error if the code is not running +under \xetex{}; while the other packages don't provide such a command, +it's not really difficult to write one for yourself. + +% khalighi's iftex package, too -- \require's for all engines, but i'm +% not entirely sure of the conditionals, so "for later" if at all + +Now for those who want to do the job for themselves: here's a +discussion of doing the job for \pdftex{} and \csx{ifpdf}~--- the +eager programmer can regenerate \csx{ifxetex} or \csx{ifluatex} in the +same fashion. It's not recommended\dots Suppose you need to test whether your output will be \acro{PDF} or \acro{DVI}. The natural thing is to check whether you have access to @@ -1448,15 +1480,6 @@ output, you also need to know about the value of \csx{pdfoutput}: \fi \end{verbatim} \end{quote} -The above is, in essence, what Heiko Oberdiek's \Package{ifpdf} -package does; the reasoning is the \acro{FAQ}'s interpretation of -Heiko's explanation. - -As an aside: there are now analogous packages \Package{ifxetex} and -\Package{ifluatex}, for the two up-and-coming \TeX{}-like engines (see -the ``\TeX{} project'' answers covering % ! line break -\Qref[\xetex{}~--- question]{\xetex{}}{Q-xetex}, and -\Qref[\LuaTeX{}~--- question]{\LuaTeX{}}{Q-luatex}). \begin{ctanrefs} \item[ifpdf.sty]Distributed as part Heiko Oberdiek's bundle \CTANref{oberdiek}[ifpdf] diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex index c3aff8dad9e..7d789e1389a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-projects.tex @@ -1,4 +1,4 @@ -% $Id: faq-projects.tex,v 1.12 2010/06/02 23:10:24 rf10 Exp rf10 $ +% $Id: faq-projects.tex,v 1.15 2011/02/08 22:17:17 rf10 Exp rf10 $ \section{Current \TeX{}-related projects} @@ -162,7 +162,7 @@ support for new Web standards. \item[GELLMU]\CTANref{gellmu} \item[MathTeX]\CTANref{MathTeX} \item[MimeTeX]\CTANref{MimeTeX} -\item[TeX4HT]\CTANref{tex4ht} +\item[tex4ht]\CTANref{tex4ht} (but see \url{http://tug.org/tex4ht/}) \end{ctanrefs} \Question[Q-textrace]{Making outline fonts from \MF{}} @@ -207,7 +207,6 @@ in MetaType1 format. \Question[Q-WYGexpts]{The \TeX{} document preparation environment} - ``\Qref*{Why \TeX{} is not \WYSIWYG{}}{Q-notWYSIWYG}'' outlines the reasons (or excuses) for the huge disparity of user interface between ``typical'' \TeX{} environments and commercial word @@ -262,11 +261,7 @@ tracking with automatic fast recompilations (through the use of dumped formats) is \href{http://pauillac.inria.fr/whizzytex/}{\Package{WhizzyTeX}} which is best used with a previewer by the -same author. A simpler package in a similar spirit is called -\href{http://www.activetex.org/}{\Package{InstantPreview}} and makes -use of a continuously running copy of \TeX{} -(under the moniker of \texttt{TeX daemon}) instead of dumping formats to -achieve its speed. +same author. Another \ProgName{emacs} package called \href{http://preview-latex.sourceforge.net}{\Package{preview-latex}} @@ -461,7 +456,9 @@ Few would deny that \BibTeX{} is ripe for renewal: as originally conceived, it was a program for creating bibliographies for technical documents, in English. People have contributed mechanisms for a degree of multilingual use (whose techniques are arcane, and quite -likely inextensible); and specialist \BibTeX{} style files are +likely inextensible), while an extension (\ProgName{bibtex8}) allows +use with 8-bit character codes, thus providing some multilingual +capabilities. In addition, specialist \BibTeX{} style files are available for use in non-technical papers. \BibTeX{} uses a style language whose mechanisms are unfamiliar to @@ -474,71 +471,72 @@ Oren Patashnik (the author of \BibTeX{}) summarises the issues as he sees them, in a % !line break \href{http://tug.org/TUGboat/Articles/tb24-1/patashnik.pdf}{\acro{TUG} conference paper from 2003} that seems to suggest that we might expect a -\BibTeX{}~1.0\dots{}which hasn't (yet) appeared. +\BibTeX{}~1.0 \dots{} which hasn't (yet) appeared. In the absence of \BibTeX{}~1.0, what do we need from the bibliography system of the future?~--- simple: a superset of what \BibTeX{} does -(or can be made to do), implemented in a simpler style language, with -coherent multilingual capabilities. +(or can be made to do), preferably implementing a simpler style +language, and with coherent multilingual capabilities. + +There are two parts to a bibliography system; processing the database +of citations, and typesetting the results. The existing \bibtex{} +system provides a means of processing the database, and there are +macros built into \latex{}, as well as many \latex{} packages, that +process the results. + +Of the direct \BibTeX{} replacements, only two have been submitted to +\acro{CTAN}: Cross\TeX{} and \ProgName{biber}. -Of the direct \BibTeX{} replacements, the only one whose authors have -sufficient confidence to submit to \acro{CTAN} is Cross\TeX{}. Cross\TeX{}'s language feels familiar to the existing user of \BibTeX{}, but it's redesigned in an object-oriented style, and looks -(to a non-user) as if it may well be adequately flexible. +(to a non-user) as if it may well be adequately flexible. It is said +to operate as a \bibtex{} replacement. Cross\TeX{}'s team respond to queries, and seem well aware of the -need for multilingual support. Cross\TeX{} is probably a development -to watch. - -Two interesting alternative approaches, that the author has -investigated, are \Package{amsrefs} and \Package{biblatex}. -\Package{Amsrefs} does away with \BibTeX{} altogether, while -\Package{biblatex} (at least for now) 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.) +need for multilingual support, though it isn't currently offered. + +\ProgName{Biber} is intimately associated with the \latex{} package +\Package{biblatex}; it is logically a \bibtex{} replacement, but is also +capable of using bibliography databases in its own +\ProgName{biblatexml} (\acro{XML}-based) format. \Package{Biblatex} +can also use \bibtex{}, but \ProgName{biber} opens up a far wider +range of possibilities, including full Unicode support. + +\Package{Biblatex} is a processor for the output of an application +such as \ProgName{biber} or \bibtex{}; the style of citations and of +the bibliography itself (in your document) is determined by the way +your \Package{biblatex} style has been set up, not on some +\bibtex{}-\latex{} package combination. \Package{Biblatex}'s +structure thus eliminates the collections of \BibTeX{} styles, at a +stroke; it 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 provides answers to +many of the questions asked in the bibliography sections of these +\acro{FAQ}s. + +\Package{Biblatex} was 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 \emph{de facto} +set of expert users is already establishing itself. A set of +contributed styles has appeared, which cover some of the trickier +bibliography styles. The road map of the project shows that we are +now working on the final \emph{beta} releases before the ``stable'' +\Package{biblatex}~1.0. + +Finally, \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{} simply to sort the citations using -\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. A set of contributed styles has -appeared, which cover some of the trickier bibliography styles. The -road map of the project shows one more \emph{beta} release before the -``stable'' \Package{biblatex}~1.0. - -A related project is -\href{http://biblatex-biber.sourceforge.net/}{\ProgName{biber}} -(it's called \ProgName{biblatex-biber} on SourceForge simply to -distinguish it from an older, defunct, \BibTeX{} replacement -project). \ProgName{Biber} is a \ProgName{Perl}-based system to -produce a \BibTeX{} replacement that is specifically tuned to the -requirements of \Package{biblatex}. While it supports the -`traditional' \BibTeX{} interface, \ProgName{biber} provides an -interface language designed for \Package{biblatex}, including use of -Unicode to ease the generation of multilingual citations. \begin{ctanrefs} \item[amsrefs.sty]\CTANref{amsrefs} \item[biber]\CTANref{biber} \item[biblatex.sty]\CTANref{biblatex} +\item[bibtex8]\CTANref{bibtex8} \item[\nothtml{\rmfamily}biblatex contributions]\CTANref{biblatex-contrib} \item[\nothtml{\rmfamily}CrossTeX]\CTANref{crosstex} \end{ctanrefs} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex index 6bc78ba7267..6f6353a9ac1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex @@ -1,4 +1,4 @@ -% $Id: faq-t-g-wr.tex,v 1.7 2010/08/16 22:04:13 rf10 Exp rf10 $ +% $Id: faq-t-g-wr.tex,v 1.9 2011/02/08 22:17:17 rf10 Exp rf10 $ \section{Things are Going Wrong\dots{}} @@ -99,6 +99,7 @@ part of the distribution). \ProgName{MathsPic} is available either as a \ProgName{Basic} program for \acro{DOS}, or as a \ProgName{Perl} program for other systems (including Windows, nowadays). \begin{ctanrefs} +\item[etex.sty]\CTANref{etex-pkg} \item[m-pictex.sty]Distributed as part of \CTANref{context-tmf} \item[m-pictex.tex]Distributed as part of \CTANref{context-tmf} \item[MathsPic]\CTANref{mathspic} @@ -179,8 +180,24 @@ equally well to tables, or to ``non-standard'' floats defined by the resort if the other possibilities below don't help. \item If you would actually \emph{like} great blocks of floats at the end of each of your chapters, try the \Package{morefloats} package; - this `simply' increases the number of floating inserts that \LaTeX{} - can handle at one time (from~18 to~36). + this allows you to increase the number of floating inserts that \LaTeX{} + can handle at one time (from its original value of~18, in + \LaTeXe{}). Note that, even with \etex{}'s greater supply of + registers, there is still a modest limit on the total number of + floating inserts (\etex{} increases the total number of registers + available, but inserts don't work if they are constructed from + registers in the extended range). + + Caveat: if you are using \Package{etex} to increase the number of + registers available, you need to ``reserve'' some inserts for + \Package{morefloats}: something like: + \begin{quote} +\begin{verbatim} +\usepackage{etex} +\reserveinserts{18} +\usepackage{morefloats} +\end{verbatim} + \end{quote} \item If you actually \emph{wanted} all your figures to float to the end (\emph{e.g}., for submitting a draft copy of a paper), don't rely on \LaTeX{}'s mechanism: get the \Package{endfloat} package to do @@ -189,6 +206,7 @@ equally well to tables, or to ``non-standard'' floats defined by the \begin{ctanrefs} \item[afterpage.sty]Distributed as part of \CTANref{2etools}[afterpage] \item[endfloat.sty]\CTANref{endfloat} +\item[etex.sty]\CTANref{etex-pkg} \item[flafter.sty]Part of the \LaTeX{} distribution \item[float.sty]\CTANref{float} \item[morefloats.sty]\CTANref{morefloats} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-texsys.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-texsys.tex index a388d273943..661a23e47f5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-texsys.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-texsys.tex @@ -1,4 +1,4 @@ -% $Id: faq-texsys.tex,v 1.11 2010/08/16 22:04:13 rf10 Exp rf10 $ +% $Id: faq-texsys.tex,v 1.12 2010/12/11 23:49:08 rf10 Exp rf10 $ \section{\TeX{} Systems} @@ -316,19 +316,20 @@ personal selection: window manager provides \acro{GUI} ``shell-like'' facilities, in a similar way to the widely-praised \ProgName{Winedt} (see below); details (and downloads) are available from the project's - \href{http://kile.sourceforge.net/}{home on SourceForge}. A newer - system (by \ProgName{Kile}'s original author), - \href{http://www.xm1math.net/texmaker/}{\ProgName{texmaker}} doesn't - rely on \acro{KDE}'s facilities, and so may be more easily portable. -\item[\MSDOS{}] \TeX{}shell is a simple, - easily-customisable environment, which can be used with the editor - of your choice. - - You can also use \acro{GNU}~\ProgName{emacs} and \acro{AUC}-\TeX{} - under \MSDOS{}. -\item[Windows '9x, NT, etc.]\ProgName{TeXnicCenter} is a (free) + \href{http://kile.sourceforge.net/}{home on SourceForge}. + + \acro{TUG} is sponsoring the development of a cross-platform editor + and shell, modelled on the excellent \texshop{} for the Macintosh. + While this program, + \href{http://www.tug.org/texworks/}{\texworks{}}, is still under + development, it is already quite usable: if you're looking for a + \AllTeX{} development environment, and are willing to step beyond + the boundaries, it may be for you. +\item[Windows-32]\ProgName{TeXnicCenter} is a (free) \TeX{}-oriented development system, uniting a powerful platform for executing \AllTeX{} and friends with a configurable editor. + + \texworks{} (see above) is also available for Windows systems. \ProgName{Winedt}, a shareware package, is also highly spoken of. It too provides a shell for the use of \TeX{} and related programs, @@ -339,29 +340,21 @@ personal selection: Both \ProgName{emacs} and \ProgName{vim} are available in versions for Windows systems. -\item[\acro{OS/}2] \ProgName{epmtex} offers an \acro{OS/}2-specific shell. -\item[Macintosh] The commercial Textures provides an excellent integrated - Macintosh environment with its own editor. More powerful still (as an - editor) is the shareware \ProgName{Alpha} which is - extensible enough to let you perform almost any \TeX{}-related job. It - works well with Oz\TeX{}. From release 2.2.0 (at least), Textures - works with \macosx{}. - - For \macosx{} users, the free tool of choice appears to be - \href{http://www.uoregon.edu/~koch/texshop/texshop.html}{\texshop{}}, which +\item[Macintosh] For \macosx{} users, the free tool of choice appears to be + \href{http://pages.uoregon.edu/koch/texshop/index.html}{\texshop{}}, which combines an editor and a shell with a coherent philosophy of dealing 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 also available for use on Macintosh systems. -\item[Wildcard] \acro{TUG} is sponsoring the development of a - cross-platform editor and shell, modelled on the excellent - \texshop{} for the Macintosh. While this program, - \href{http://www.tug.org/texworks/}{\texworks{}}, is still under - development, it is already quite usable: if you're looking for a - \AllTeX{} development environment, and are willing to step beyond - the boundaries, it may be for you. + + The commercial Textures provides an excellent integrated Macintosh + environment with its own editor. More powerful still (as an editor) + is the shareware \ProgName{Alpha} which is extensible enough to let + you perform almost any \TeX{}-related job. It also works well with + Oz\TeX{}. From release 2.2.0 (at least), Textures works under \macosx{}. +\item[\acro{OS/}2] \ProgName{epmtex} offers an \acro{OS/}2-specific shell. \end{description} Atari, Amiga and \acro{N}e\acro{XT} users also have nice environments. \LaTeX{} users looking for \ProgName{make}-like @@ -371,13 +364,13 @@ facilities should review the answer on 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~--- -\begin{wideversion} +\begin{hyperversion} see ``\Qref{creating a bibliography file}{Q-buildbib}''. -\end{wideversion} -\begin{narrowversion} +\end{hyperversion} +\begin{flatversion} these are discussed in % ! line break ``\Qref*{creating a bibliography file}{Q-buildbib}''. -\end{narrowversion} +\end{flatversion} \begin{ctanrefs} \item[alpha]\CTANref{alpha} \item[auctex]\CTANref{auctex} @@ -420,20 +413,6 @@ also have email, and normal telephone and fax support. Web: \URL{http://www.truetex.com/} \end{quote} Source: Mail from Richard Kinch, August 2004. -%% \item[\acro{PC}; \YandY{} \TeX{}] ``Bitmap free \TeX{} for Windows.'' -%% \begin{quote} -%% \YandY{}, Inc.\\ -%% 106 Indian Hill, \acro{MA} 01741-1747\\ -%% \acro{USA}\\[.25\baselineskip] -%% Tel: 800-742-4059 (within North America)\\ -%% Tel: +1 978-371-3286\\ -%% Fax: +1 978-371-2004\\ -%% Email: \mailto{sales-help@YandY.com} and -%% \nothtml{\\ \hphantom{Email: }}% -%% \mailto{tech-help@YandY.com}\\ -%% Web: \URL{http://www.YandY.com/} -%% \end{quote} -%% Source: Confirmed with \YandY{}, February 2003 \item[pc\TeX{}] Long-established: pc\TeX{}32 is a Windows implementation. \begin{quote} Personal \TeX{} Inc\\ diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex index 42b53018a4a..8b998fc5ce3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex @@ -1,4 +1,4 @@ -% $Id: faq-wdidt.tex,v 1.5 2010/04/28 06:13:10 rf10 Exp rf10 $ +% $Id: faq-wdidt.tex,v 1.10 2011/02/10 23:01:29 rf10 Exp rf10 $ \section{Why does it \emph{do} that?} @@ -156,7 +156,8 @@ matching \cmdinvoke{end}{verbatim}. This is why the \LaTeX{} book insists that verbatim commands must not appear in the argument of any other command; they -aren't just fragile, they're quite unusable in any command parameter, +aren't just fragile, they're quite unusable in any ``normal'' command +parameter, regardless of \Qref*{\csx{protect}ion}{Q-protect}. (The \csx{verb} 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 @@ -175,7 +176,7 @@ necessary?''. ``\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: + environmen)t: \begin{quote} \begin{verbatim} \newsavebox{\mybox} @@ -188,7 +189,22 @@ necessary?''. \end{quote} \end{itemize} -Otherwise, there are three partial solutions to the problem. +If you can't avoid verbatim, the \csx{cprotect} command (from the +package \Package{cprotect}) might help. The package manages to make a +macro read a verbatim argument in a ``sanitised'' way by the simple +medium of prefixing the macro with \csx{cprotect}: +\begin{quote} +\begin{verbatim} +\cprotect\section{Using \verb|verbatim|} +\end{verbatim} +\end{quote} +The package (at the time this author tested it) was still under +development (though it \emph{does} work in this simple case) and +deserves consideration in most cases; the package documentation gives +more details. + +Other than the \Package{cprotect} package, there are three partial +solutions to the problem: \begin{itemize} \item Some packages have macros which are designed to be responsive to verbatim text in their arguments. For example, @@ -234,9 +250,8 @@ Otherwise, there are three partial solutions to the problem. like percent signs for which \AllTeX{} already provides robust macros). \end{itemize} -Documentation of both \Package{url} and \Package{verbdef} is in the -package files. \begin{ctanrefs} +\item[cprotect.sty]\CTANref{cprotect} \item[fancyvrb.sty]\CTANref{fancyvrb} \item[memoir.cls]\CTANref{memoir} \item[url.sty]\CTANref{url} @@ -499,11 +514,13 @@ before your first \csx{chapter}. What happens is, that the class numbers sections as % ! line break ``\meta{chapter no}.\meta{section no}'', and until the first -chapter has appeared, the chapter number is 0. +\csx{chapter} has appeared, the chapter number is 0. (If you +use\csx{chapter*}, which doesn't number the chapter it produces, the +problem still arises.) -If you're doing this, it's quite likely that the \Class{article} class -is for you; try it and see. Otherwise, give your sections a -`superior' chapter, or do away with section numbering by using +If you're doing this, it's possible that the \Class{article} class +is for you; try it and see. Otherwise, put a \csx{chapter} before +your sections, or do away with section numbering by using \csx{section*} instead. An alternative way of avoiding numbering is discussed in % ! line break ``\Qref*{unnumbered sections in the table of contents}{Q-secnumdep}''. @@ -1350,7 +1367,7 @@ Paragraph text ... \end{verbatim} \end{quote} This technique \emph{only} works for such very short intrusions; if -you need several lines, you should convert your intrusion into an +you need several lines, you should convert your intrusion into a \environment{quote} environment, since it's not possible to provide a \csx{strut} command for every line of the intrusion, in a sensible way, so proceed by: @@ -1424,8 +1441,8 @@ is different from those around it: Main body of text... \end{verbatim} \end{quote} -Again, the problem is solved by inserting a paragraph marker in -the text with a different size: +Again, the problem is solved by ending the paragraph in the same group +as the text with a different size: \begin{quote} \begin{verbatim} {\Large (Extended) IMPORTANT DETAILS ...\par} @@ -1547,7 +1564,7 @@ One doesn't do this for a variety of small reasons: \begin{description} \item[Confusion] You've been happily working in this mode, and for some reason find you're to switch to writing in German: the effect - of using ``\texttt{\ss}'' is somewhat startling, since \acro{T}1 + of using ``\texttt{\ss {}}'' is somewhat startling, since \acro{T}1 and Latin-1 treat the codepoint differently. \item[Compatibility] You find yourself needing to work with a colleague in Eastern Europe: their keyboard is likely to be set to diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq.sty b/Master/texmf-dist/doc/generic/FAQ-en/faq.sty index 838abce5e10..96cefbe66d2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq.sty +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq.sty @@ -1,4 +1,4 @@ -% $Id: faq.sty,v 1.124 2010/08/07 11:23:14 rf10 Exp rf10 $ +% $Id: faq.sty,v 1.128 2011/02/14 23:49:27 rf10 Exp rf10 $ % % This is the LaTeX package that deals with the eccentricities of mark % up of the UK TeX FAQ. @@ -102,6 +102,7 @@ \def\WYSIWYG{WYSIWYG}% \def\AMSTeX{AmSTeX}% \def\BibTeX{BibTeX}% + \def\bibtex{BibTeX}% \def\PiCTeX{PiCTeX}% \def\CDROM{CD-ROM}% \def\TeXXeT{TeXXeT}% @@ -157,6 +158,8 @@ %% \fi \DeclareRobustCommand\MF{Meta\-Font} \DeclareRobustCommand\MP{Meta\-Post} +\newcommand\ttype{TrueType} +\newcommand\otype{OpenType} \let\textlogo\textmd % % define substitutes for stupid_names @@ -164,6 +167,7 @@ \newcommand\AMSTeX{AMS\TeX} \newcommand\AMSLaTeX{AMS\LaTeX} \newcommand\BibTeX{Bib\TeX} +\newcommand\bibtex{Bib\TeX} \newcommand\PiCTeX{PiC\TeX} \newcommand\texlive{\TeX{} Live} % and... @@ -176,6 +180,7 @@ % % we define conditional stuff using Eijkhout's package \RequirePackage{comment} +\def\CommentCutFile{tmp/comment.cut} % use this in place of ./comment.cut \excludecomment{htmlversion} \includecomment{typesetversion} \ifpdf @@ -193,6 +198,8 @@ \includecomment{dviversion} \includecomment{narrowversion} \fi +% +% dummy environment for separating the intro \newenvironment{introduction}{}{} % % but we also want short versions, like LaTeX2HTML's @@ -581,13 +588,19 @@ \def\UrlFont{\rmfamily\itshape}\csname Url@do\endcsname \Url } +\let\progname\ProgName %%\else %% \DeclareUrlCommand\@ProgName{\def\UrlFont{\rmfamily\itshape}} %% \DeclareRobustCommand\ProgName{\@ProgName} %%\fi \let\Package\ProgName % pro tem +\let\package\Package + \let\Class\Package % ... +\let\class\Class + \let\FontName\Package % ... +% \let\fontname\FontName % ahh, ... no! % another little oddity (from doc.sty originally, iirc) \newcommand\meta[1]{\ensuremath{\langle}\emph{#1}\ensuremath{\rangle}} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex b/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex index 1294c448cca..239fab741a4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex @@ -1,4 +1,4 @@ -% $Id: filectan.tex,v 1.128 2010/08/12 18:14:24 rf10 Exp rf10 $ +% $Id: filectan.tex,v 1.133 2011/02/13 23:08:45 rf10 Exp $ % % protect ourself against being read twice \csname readCTANfiles\endcsname @@ -63,11 +63,9 @@ \CTANfile{mf-list}{info/metafont-list} \CTANfile{miktex-portable}{systems/win32/miktex/setup/miktex-portable.exe} \CTANfile{miktex-setup}{systems/win32/miktex/setup/setup.exe}[miktex] -\CTANfile{miktex-usb}{info/MiKTeX+Ghostscript+GSview+USB-drive-HOWTO.txt} \CTANfile{mil}{info/mil/mil.pdf} \CTANfile{mil-short}{info/Math_into_LaTeX-4/Short_Course.pdf}[math-into-latex-4] \CTANfile{modes-file}{fonts/modes/modes.mf}[modes] -\CTANfile{morefloats}{macros/latex/contrib/misc/morefloats.sty}[morefloats] \CTANfile{mpsproof}{graphics/metapost/contrib/misc/mpsproof.tex}[mpsproof] \CTANfile{mtw}{info/makingtexwork/mtw-1.0.1-html.tar.gz} \CTANfile{multind}{macros/latex209/contrib/misc/multind.sty}[multind] @@ -75,24 +73,21 @@ \CTANfile{nextpage}{macros/latex/contrib/misc/nextpage.sty}[nextpage] \CTANfile{noTeX}{biblio/bibtex/utils/misc/noTeX.bst}[notex] \CTANfile{numline}{obsolete/macros/latex/contrib/numline/numline.sty}[numline] -\CTANfile{parskip}{macros/latex/contrib/misc/parskip.sty}[parskip] \CTANfile{patch}{macros/generic/misc/patch.doc}[patch] -\CTANfile{path}{macros/latex/contrib/misc/path.sty}[path] \CTANfile{picins-summary}{macros/latex209/contrib/picins/picins.txt} \CTANfile{pk300}{fonts/cm/pk/pk300.zip} \CTANfile{pk300w}{fonts/cm/pk/pk300w.zip} -\CTANfile{printlen}{macros/latex/contrib/misc/printlen.sty}[printlen] \CTANfile{removefr}{macros/latex/contrib/fragments/removefr.tex}[removefr] \CTANfile{resume}{obsolete/macros/latex209/contrib/resume/resume.sty} \CTANfile{savesym}{macros/latex/contrib/savesym/savesym.sty}[savesym] \CTANfile{screensty}{macros/latex209/contrib/misc/screen.sty}[screen] \CTANfile{selectp}{macros/latex/contrib/misc/selectp.sty}[selectp] \CTANfile{setspace}{macros/latex/contrib/setspace/setspace.sty}[setspace] -\CTANfile{simpl-latex}{info/simplified-latex/simplified-intro.ps}[simplified-latex] +\CTANfile{simpl-latex}{info/simplified-latex/simplified-intro.pdf}[simplified-latex] \CTANfile{sober}{macros/latex209/contrib/misc/sober.sty}[sober] \CTANfile{tex2bib}{biblio/bibtex/utils/tex2bib/tex2bib}[tex2bib] \CTANfile{tex2bib-doc}{biblio/bibtex/utils/tex2bib/README} -\CTANfile{tex4ht}{support/TeX4ht/tex4ht-all.zip}[tex4ht] +\CTANfile{tex4ht}{obsolete/support/TeX4ht/tex4ht-all.zip}[tex4ht] \CTANfile{texlive-unix}{systems/texlive/tlnet/install-tl-unx.tar.gz} \CTANfile{texlive-windows}{systems/texlive/tlnet/install-tl.zip} \CTANfile{texnames}{info/biblio/texnames.sty} @@ -108,11 +103,10 @@ \CTANfile{varwidth}{macros/latex/contrib/misc/varwidth.sty}[varwidth] \CTANfile{version}{macros/latex/contrib/misc/version.sty}[version] \CTANfile{versions}{macros/latex/contrib/versions/versions.sty}[versions] -\CTANfile{vertbars}{macros/latex/contrib/misc/vertbars.sty}[vertbars] \CTANfile{vf-howto}{info/virtualfontshowto/virtualfontshowto.txt} \CTANfile{vf-knuth}{info/knuth/virtual-fonts}[vf-knuth] \CTANfile{visualFAQ}{info/visualFAQ/visualFAQ.pdf}[visualfaq] \CTANfile{voss-mathmode}{info/math/voss/mathmode/Mathmode.pdf} \CTANfile{wujastyk-txh}{digests/texhax/txh/wujastyk.txh} -\CTANfile{xampl-bib}{biblio/bibtex/distribs/doc/xampl.bib} +\CTANfile{xampl-bib}{biblio/bibtex/base/xampl.bib} \CTANfile{xtexcad}{graphics/xtexcad/xtexcad-2.4.1.tar.gz} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex b/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex index 5c26ff018ee..0f1ddf649a2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/gather-faqbody.tex @@ -1,4 +1,4 @@ -\def\faqfileversion{3.20} \def\faqfiledate{2010-08-17} +\def\faqfileversion{3.21} \def\faqfiledate{2011-02-18} % % The above line defines the file version and date, and must remain % the first line with any `assignment' in the file, or things will diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-BibTeXing.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-BibTeXing.html index ca469508e80..2b1e667e8ce 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-BibTeXing.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-BibTeXing.html @@ -5,26 +5,27 @@ <p/>BibTeX, a program originally designed to produce bibliographies in conjunction with LaTeX, is explained in Section 4.3 and Appendix B of Leslie Lamport’s LaTeX manual. -The document “BibTeXing”, contained in the file <i>btxdoc.tex</i>, +The document “BibTeXing”, in the BibTeX distribution (look for +<i>btxdoc</i>), expands on the chapter in Lamport’s book. <em>The LaTeX Companion</em> also has information on BibTeX and writing BibTeX style files. (See <a href="FAQ-books.html">TeX-related books</a> for details of both books.) -<p/>The document “Designing BibTeX Styles”, contained in the file -<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> +<p/>The document “Designing BibTeX Styles”, also in the BibTeX +distribution (look for +<i>btxhak</i>, explains the postfix stack-based language used to +write BibTeX styles (<i>.bst</i> files). The file<i>btxbst.doc</i>, +also in the BibTeX distribution, 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. +<i>abbrv</i>, <i>alpha</i>, and <i>unsrt</i>); it also +contains their documentation. <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. A summary and FAQ -(<i>btxFAQ</i>), by Michael Shell and David Hoadley, is also to be -recommended. +may also be found on CTAN. A summary and FAQ by Michael +Shell and David Hoadley, is also to be recommended. <dl> -<dt><tt><i>BibTeX documentation</i></tt><dd><a href="http://mirror.ctan.org/biblio/bibtex/contrib/doc.zip">biblio/bibtex/contrib/doc</a> (or <a href="http://mirror.ctan.org/biblio/bibtex/contrib/doc/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/bibtex.html">catalogue entry</a> -<dt><tt><i>btxFAQ.pdf</i></tt><dd><a href="http://mirror.ctan.org/biblio/bibtex/contrib/doc/btxFAQ.pdf">biblio/bibtex/contrib/doc/btxFAQ.pdf</a> +<dt><tt><i>BibTeX distribution</i></tt><dd><a href="http://mirror.ctan.org/biblio/bibtex/base.zip">biblio/bibtex/base</a> (or <a href="http://mirror.ctan.org/biblio/bibtex/base/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/bibtex.html">catalogue entry</a> +<dt><tt><i>Shell and Hoadley’s FAQ</i></tt><dd><a href="http://mirror.ctan.org/biblio/bibtex/contrib/doc/btxFAQ.pdf">biblio/bibtex/contrib/doc/btxFAQ.pdf</a> <dt><tt><i>Tame the BeaST</i></tt><dd><a href="http://mirror.ctan.org/info/bibtex/tamethebeast/ttb_en.pdf">info/bibtex/tamethebeast/ttb_en.pdf</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/tamethebeast.html">catalogue entry</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> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html index d73e16d95b3..76afb0b8aaa 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-LaTeX2HTML.html @@ -43,7 +43,7 @@ browsing may be brighter — see <i>flex</i>. The distribution consists of a single C source (or a compiled executable), which is easy to install and very fast-running. -<dt><i>Tex4ht</i><dd>a compiled program that supports either +<dt><i>TeX4ht</i><dd>a compiled program that supports either LaTeX or Plain TeX, by processing a DVI file; it uses bitmaps for mathematics, but can also use other technologies where appropriate. Written by Eitan Gurari, it parses the DVI @@ -76,7 +76,7 @@ HTML, with sections on (La)TeX and BibTeX — see <dl> <dt><tt><i>latex2html</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/latex2html">support/latex2html</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/latex2html.html">catalogue entry</a> <dt><tt><i>plasTeX</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/plastex">support/plastex</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/plastex.html">catalogue entry</a> -<dt><tt><i>tex4ht</i></tt><dd><a href="http://mirror.ctan.org/support/TeX4ht/tex4ht-all.zip">support/TeX4ht/tex4ht-all.zip</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/tex4ht.html">catalogue entry</a> +<dt><tt><i>tex4ht</i></tt><dd><a href="http://mirror.ctan.org/obsolete/support/TeX4ht/tex4ht-all.zip">obsolete/support/TeX4ht/tex4ht-all.zip</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/tex4ht.html">catalogue entry</a> (but see <a href="http://tug.org/tex4ht/">http://tug.org/tex4ht/</a>) <dt><tt><i>tth</i></tt><dd><a href="http://mirror.ctan.org/support/tth/dist.zip">support/tth/dist</a> (or <a href="http://mirror.ctan.org/support/tth/dist/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/tth.html">catalogue entry</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> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-PSpreview.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-PSpreview.html index 7cf5c5de0b9..116e1fd8b03 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-PSpreview.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-PSpreview.html @@ -2,48 +2,50 @@ <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 -displaying bitmap PK fonts, but current versions of -<i>xdvi</i> sport a Type 1 font renderer. - - - - - -<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: +<p/>Originally, free TeX previewers were only capable of displaying +bitmap (PK) fonts, but free Type 1 font rendering software has +been available for some time, and many previewers now use such +facilities. +<p/>The alternative, for previewers, is automatic generation of the +requisite PK files (using <i>gsftopk</i>, or similar, +behind the scenes). +<p/>In the unlikely event that your previewer isn’t capable of either, you +have a couple options: <ul> <li> Convert the DVI file to PostScript and use a PostScript previewer. Some systems offer this capability as standard, but most people will need to use a separate previewer such as <i>ghostscript</i> or <i>ghostscript</i>-based viewers such as <i>gv</i> or shareware offering <i>GSview</i>. -<li> Under Windows on a PC, or on a Macintosh, let Adobe Type Manager - display the fonts (textures, on the Macintosh, works like this). - (See <a href="FAQ-commercial.html">commercial suppliers</a> for details.) -<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 - PK bitmap fonts which your previewer - will understand. This can produce excellent results, also suitable - for printing with non-PostScript devices. Check the legalities of - this if you have purchased the fonts. + + + + + + + + +<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 PK bitmap fonts which + your previewer will understand (a process similar to the way some + browsers fo the job ‘automatically’) This can produce excellent results, + also suitable for printing with non-PostScript devices. (Note: if you + purchased the fonts, it is advisable to check that their licence + permits you to convert them, for private use, in this way.) </ul> <dl> -<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/ghostscript">support/ghostscript</a> -<dt><tt><i>gsftopk</i></tt><dd><a href="http://mirror.ctan.org/fonts/utilities/gsftopk.zip">fonts/utilities/gsftopk</a> (or <a href="http://mirror.ctan.org/fonts/utilities/gsftopk/">browse the directory</a>) +<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/ghostscript/GPL">support/ghostscript/GPL</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/ghostscript-GPL.html">catalogue entry</a> +<dt><tt><i>gsftopk</i></tt><dd><a href="http://mirror.ctan.org/fonts/utilities/gsftopk.zip">fonts/utilities/gsftopk</a> (or <a href="http://mirror.ctan.org/fonts/utilities/gsftopk/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/gsftopk.html">catalogue entry</a> <dt><tt><i>GSview</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/ghostscript/ghostgum">support/ghostscript/ghostgum</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/gsview.html">catalogue entry</a> <dt><tt><i>gv</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/gv">support/gv</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/gv.html">catalogue entry</a> -<dt><tt><i>ps2pk</i></tt><dd><a href="http://mirror.ctan.org/fonts/utilities/ps2pk.zip">fonts/utilities/ps2pk</a> (or <a href="http://mirror.ctan.org/fonts/utilities/ps2pk/">browse the directory</a>) -<dt><tt><i>xdvi</i></tt><dd><a href="http://mirror.ctan.org/dviware/xdvi">dviware/xdvi</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/xdvi.html">catalogue entry</a> +<dt><tt><i>ps2pk</i></tt><dd><a href="http://mirror.ctan.org/fonts/utilities/ps2pk.zip">fonts/utilities/ps2pk</a> (or <a href="http://mirror.ctan.org/fonts/utilities/ps2pk/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/ps2pk.html">catalogue entry</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> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-RCS.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-RCS.html index 789090a0c41..d05b40eea6c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-RCS.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-RCS.html @@ -20,8 +20,8 @@ following minimal solution: <blockquote> <pre> \def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}} -\RCS$Revision: 1.16 $ % or any RCS keyword -\RCS$Date: 2010/08/14 20:22:55 $ +\RCS$Revision: 1.24 $ % or any RCS keyword +\RCS$Date: 2011/02/10 23:01:29 $ ... \date{Revision \RCSRevision, \RCSDate} </pre> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-SGML2TeX.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-SGML2TeX.html index 6231da75959..ec3b1daad72 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-SGML2TeX.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-SGML2TeX.html @@ -59,7 +59,7 @@ source is available on CTAN. 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="http://mirror.ctan.org/support/html2latex.zip">support/html2latex</a> (or <a href="http://mirror.ctan.org/support/html2latex/">browse the directory</a>) +<dt><tt><i>html2latex source</i></tt><dd><a href="http://mirror.ctan.org/support/html2latex.zip">support/html2latex</a> (or <a href="http://mirror.ctan.org/support/html2latex/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/html2latex.html">catalogue entry</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> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-WYGexpts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-WYGexpts.html index bcf65c96e58..2acbac7c55e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-WYGexpts.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-WYGexpts.html @@ -2,7 +2,7 @@ <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/>“<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. @@ -52,11 +52,7 @@ tracking with automatic fast recompilations (through the use of dumped formats) is <a href="http://pauillac.inria.fr/whizzytex/"><i>WhizzyTeX</a></i> which is best used with a previewer by the -same author. A simpler package in a similar spirit is called -<a href="http://www.activetex.org/"><i>InstantPreview</a></i> and makes -use of a continuously running copy of TeX -(under the moniker of <code>TeX daemon</code>) instead of dumping formats to -achieve its speed. +same author. <p/>Another <i>emacs</i> package called <a href="http://preview-latex.sourceforge.net"><i>preview-latex</a></i> tries to solve diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acrobat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acrobat.html index d0a4da7c91b..1892837e1ae 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acrobat.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-acrobat.html @@ -72,7 +72,7 @@ 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="http://mirror.ctan.org/dviware/dvipdfm.zip">dviware/dvipdfm</a> (or <a href="http://mirror.ctan.org/dviware/dvipdfm/">browse the directory</a>) <dt><tt><i>dvipdfmx</i></tt><dd><a href="http://mirror.ctan.org/dviware/dvipdfmx.zip">dviware/dvipdfmx</a> (or <a href="http://mirror.ctan.org/dviware/dvipdfmx/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/dvipdfmx.html">catalogue entry</a> -<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/ghostscript">support/ghostscript</a> +<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/ghostscript/GPL">support/ghostscript/GPL</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/ghostscript-GPL.html">catalogue entry</a> <dt><tt><i>GSview</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/ghostscript/ghostgum">support/ghostscript/ghostgum</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/gsview.html">catalogue entry</a> <dt><tt><i>gv</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/gv">support/gv</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/gv.html">catalogue entry</a> <dt><tt><i>hyper.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/hyper.zip">macros/latex/contrib/hyper</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/hyper/">browse the directory</a>) diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-adobetypen.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-adobetypen.html index 0bcaee6c2df..ab4c3dc41e0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-adobetypen.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-adobetypen.html @@ -7,7 +7,7 @@ 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 have only in the last year +OpenType format, whose many advantages have only in the last year or two been readily accessible to most (La)TeX users (by means of the widely-used <a href="FAQ-xetex.html">XeTeX</a> and the more experimental <a href="FAQ-luatex.html">LuaTeX</a>). diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atvert.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atvert.html index 0d150b9def6..6fc5f0915f7 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atvert.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-atvert.html @@ -3,24 +3,36 @@ </head><body> <h3><code>\</code><code>spacefactor</code> complaints</h3> <p/>The errors +<blockquote> + <pre> ! You can't use `\spacefactor' in vertical mode. \@->\spacefactor \@m </pre> +</blockquote><p> or +<blockquote> <pre> ! You can't use `\spacefactor' in math mode. \@->\spacefactor \@m </pre> +</blockquote><p> or simply +<blockquote> <pre> ! Improper \spacefactor. ... </pre> -bites the LaTeX programmer who uses an internal command without taking -“precautions”. The problem is discussed in detail in +</blockquote><p> +bite the LaTeX programmer who uses an internal command without +taking “precautions”. An internal-style command such as <code>\</code><code>@foo</code> +has been defined or used in a private macro, and it is interpreted as +<code>\</code><code>@</code>, followed by the ‘text’ <code>foo</code>. (<code>\</code><code>@</code> is used, for +real, to set up end-of-sentence space in some circumstances; it uses +<code>\</code><code>spacefactor</code> to do that.) +<p/>The problem is discussed in detail in “<a href="FAQ-atsigns.html"><code>@</code> in macro names</a>”, together with solutions. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-baselinepar.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-baselinepar.html index 8b17ba3c0f6..8bad8d3334a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-baselinepar.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-baselinepar.html @@ -30,7 +30,7 @@ Paragraph text ... </pre> </blockquote><p> This technique <em>only</em> works for such very short intrusions; if -you need several lines, you should convert your intrusion into an +you need several lines, you should convert your intrusion into a <code>quote</code> environment, since it’s not possible to provide a <code>\</code><code>strut</code> command for every line of the intrusion, in a sensible way, so proceed by: @@ -101,8 +101,8 @@ is different from those around it: Main body of text... </pre> </blockquote><p> -Again, the problem is solved by inserting a paragraph marker in -the text with a different size: +Again, the problem is solved by ending the paragraph in the same group +as the text with a different size: <blockquote> <pre> {\Large (Extended) IMPORTANT DETAILS ...\par} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-biblatex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-biblatex.html index e4fc38f3088..57d8130f8b2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-biblatex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-biblatex.html @@ -10,7 +10,9 @@ be ready for “real-world” use. conceived, it was a program for creating bibliographies for technical documents, in English. People have contributed mechanisms for a degree of multilingual use (whose techniques are arcane, and quite -likely inextensible); and specialist BibTeX style files are +likely inextensible), while an extension (<i>bibtex8</i>) allows +use with 8-bit character codes, thus providing some multilingual +capabilities. In addition, specialist BibTeX style files are available for use in non-technical papers. <p/>BibTeX uses a style language whose mechanisms are unfamiliar to most current programmers: it’s difficult to learn, but since there are @@ -21,63 +23,63 @@ arcane TeX macro language). sees them, in a <a href="http://tug.org/TUGboat/Articles/tb24-1/patashnik.pdf">TUG conference paper from 2003</a> that seems to suggest that we might expect a -BibTeX 1.0…which hasn’t (yet) appeared. +BibTeX 1.0 … which hasn’t (yet) appeared. <p/>In the absence of BibTeX 1.0, what do we need from the bibliography system of the future? — simple: a superset of what BibTeX does -(or can be made to do), implemented in a simpler style language, with -coherent multilingual capabilities. -<p/>Of the direct BibTeX replacements, the only one whose authors have -sufficient confidence to submit to CTAN is CrossTeX. -CrossTeX’s language feels familiar to the existing user of +(or can be made to do), preferably implementing a simpler style +language, and with coherent multilingual capabilities. +<p/>There are two parts to a bibliography system; processing the database +of citations, and typesetting the results. The existing BibTeX +system provides a means of processing the database, and there are +macros built into LaTeX, as well as many LaTeX packages, that +process the results. +<p/>Of the direct BibTeX replacements, only two have been submitted to +CTAN: CrossTeX and <i>biber</i>. +<p/>CrossTeX’s language feels familiar to the existing user of BibTeX, but it’s redesigned in an object-oriented style, and looks -(to a non-user) as if it may well be adequately flexible. +(to a non-user) as if it may well be adequately flexible. It is said +to operate as a BibTeX replacement. <p/>CrossTeX’s team respond to queries, and seem well aware of the -need for multilingual support. CrossTeX is probably a development -to watch. -<p/>Two interesting alternative approaches, that the author has -investigated, are <i>amsrefs</i> and <i>biblatex</i>. -<i>Amsrefs</i> does away with BibTeX altogether, while -<i>biblatex</i> (at least for now) makes rather limited use of -BibTeX. Both are heavily dependent on LaTeX’s support. -<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.) +need for multilingual support, though it isn’t currently offered. +<p/><i>Biber</i> is intimately associated with the LaTeX package +<i>biblatex</i>; it is logically a BibTeX replacement, but is also +capable of using bibliography databases in its own +<i>biblatexml</i> (XML-based) format. <i>Biblatex</i> +can also use BibTeX, but <i>biber</i> opens up a far wider +range of possibilities, including full Unicode support. +<p/><i>Biblatex</i> is a processor for the output of an application +such as <i>biber</i> or BibTeX; the style of citations and of +the bibliography itself (in your document) is determined by the way +your <i>biblatex</i> style has been set up, not on some +BibTeX-LaTeX package combination. <i>Biblatex</i>’s +structure thus eliminates the collections of BibTeX styles, at a +stroke; it 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 provides answers to +many of the questions asked in the bibliography sections of these +FAQs. +<p/><i>Biblatex</i> was 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 <em>de facto</em> +set of expert users is already establishing itself. A set of +contributed styles has appeared, which cover some of the trickier +bibliography styles. The road map of the project shows that we are +now working on the final <em>beta</em> releases before the “stable” +<i>biblatex</i> 1.0. +<p/>Finally, <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 simply to sort the citations using -<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. A set of contributed styles has -appeared, which cover some of the trickier bibliography styles. The -road map of the project shows one more <em>beta</em> release before the -“stable” <i>biblatex</i> 1.0. -<p/>A related project is -<a href="http://biblatex-biber.sourceforge.net/"><i>biber</a></i> -(it’s called <i>biblatex-biber</i> on SourceForge simply to -distinguish it from an older, defunct, BibTeX replacement -project). <i>Biber</i> is a <i>Perl</i>-based system to -produce a BibTeX replacement that is specifically tuned to the -requirements of <i>biblatex</i>. While it supports the -‘traditional’ BibTeX interface, <i>biber</i> provides an -interface language designed for <i>biblatex</i>, including use of -Unicode to ease the generation of multilingual citations. <dl> <dt><tt><i>amsrefs.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/amsrefs.zip">macros/latex/contrib/amsrefs</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/amsrefs/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/amsrefs.html">catalogue entry</a> <dt><tt><i>biber</i></tt><dd><a href="http://mirror.ctan.org/biblio/biber.zip">biblio/biber</a> (or <a href="http://mirror.ctan.org/biblio/biber/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/biber.html">catalogue entry</a> -<dt><tt><i>biblatex.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/exptl/biblatex.zip">macros/latex/exptl/biblatex</a> (or <a href="http://mirror.ctan.org/macros/latex/exptl/biblatex/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/biblatex.html">catalogue entry</a> -<dt><tt><i>biblatex contributions</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/exptl/biblatex-contrib">macros/latex/exptl/biblatex-contrib</a> +<dt><tt><i>biblatex.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/biblatex.zip">macros/latex/contrib/biblatex</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/biblatex/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/biblatex.html">catalogue entry</a> +<dt><tt><i>bibtex8</i></tt><dd><a href="http://mirror.ctan.org/biblio/bibtex/8-bit">biblio/bibtex/8-bit</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/bibtex8bit.html">catalogue entry</a> +<dt><tt><i>biblatex contributions</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/biblatex-contrib">macros/latex/contrib/biblatex-contrib</a> <dt><tt><i>CrossTeX</i></tt><dd><a href="http://mirror.ctan.org/biblio/crosstex">biblio/crosstex</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/crosstex.html">catalogue entry</a> </dl> <p/><p/> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-books.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-books.html index 3be50b267c4..a16cd63e6b4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-books.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-books.html @@ -71,7 +71,7 @@ For LaTeX, see: <dt>The LaTeX Graphics Companion:<dd> <em>Illustrating documents with TeX and PostScript</em> by Michel Goossens, Sebastian Rahtz, Frank Mittelbach, Denis Roegel and - Herbert Voss (second edition, Addison-Wesley, 2007, + Herbert Voß (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 diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buffovl.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buffovl.html index 3151b205312..771431a5d62 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buffovl.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-buffovl.html @@ -47,7 +47,7 @@ than a given length; so the solution is just to edit the file. 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://mirror.ctan.org/support/ghostscript">support/ghostscript</a> +<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/ghostscript/GPL">support/ghostscript/GPL</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/ghostscript-GPL.html">catalogue entry</a> <dt><tt><i>GSview</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/ghostscript/ghostgum">support/ghostscript/ghostgum</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/gsview.html">catalogue entry</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> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changebars.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changebars.html index 1c377242673..0672db80ee6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changebars.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-changebars.html @@ -77,7 +77,7 @@ accept or reject selected changes only. <dt><tt><i>latexdiff, latexrevise</i></tt><dd><a href="http://mirror.ctan.org/support/latexdiff.zip">support/latexdiff</a> (or <a href="http://mirror.ctan.org/support/latexdiff/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/latexdiff.html">catalogue entry</a> <dt><tt><i>lineno.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/lineno.zip">macros/latex/contrib/lineno</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/lineno/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/lineno.html">catalogue entry</a> <dt><tt><i>memoir.cls</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/memoir/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/memoir.html">catalogue entry</a> -<dt><tt><i>vertbars.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/misc/vertbars.sty">macros/latex/contrib/misc/vertbars.sty</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/vertbars.html">catalogue entry</a> +<dt><tt><i>vertbars.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/vertbars.zip">macros/latex/contrib/vertbars</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/vertbars/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/vertbars.html">catalogue entry</a> <dt><tt><i>winedt</i></tt><dd><a href="http://mirror.ctan.org/systems/win32/winedt">systems/win32/winedt</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/winedt.html">catalogue entry</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> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-codelist.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-codelist.html index 802bb8e59dc..a46e27bda88 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-codelist.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-codelist.html @@ -60,8 +60,13 @@ Documentation is available on the <a href="http://www.andre-simon.de/"><i>highlight</a> project site</i>. <p/>The <i>minted</i> package is a relatively recent addition. It requires that documents be pre-processed using an external -(<i>python</i>) script, +(<i>python</i>) script, <a href="http://pygments.org/"><i>Pygments</a></i>. +<i>Pygments</i>, in turn, needs a “lexer” that knows the +language you want to process; lots of these are available, for the +more commonly-used languages, and there is advice on “rolling your +own” on the +<a href=’http://pygments.org/docs/lexerdevelopment/’><i>Pygments</i> site</a> <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 diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-commercial.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-commercial.html index c2b7937d109..61917d27450 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-commercial.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-commercial.html @@ -28,20 +28,6 @@ also have email, and normal telephone and fax support. Web: <a href="http://www.truetex.com/">http://www.truetex.com/</a> </blockquote><p> Source: Mail from Richard Kinch, August 2004. - - - - - - - - - - - - - - <dt>pcTeX<dd> Long-established: pcTeX32 is a Windows implementation. <blockquote> Personal TeX Inc<br> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-context.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-context.html index d6760742d6e..593530b7113 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-context.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-context.html @@ -23,6 +23,7 @@ Dutch, German, French, or Italian, and to use different typesetting engines (PDFTeX, XeTeX, Aleph and LuaTeX) without changing the user interface. ConTeXt is developed rapidly, often in response to requests from the user community. +<p><em>This answer last edited: 2010-12-08</em></p> <p/> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-custbib.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-custbib.html index b3db0c6e4f4..2a4f50df3a7 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-custbib.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-custbib.html @@ -3,9 +3,8 @@ </head><body> <h3>Creating a bibliography style</h3> <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 - +styles are distributed in a form with many comments, and there is a description +of the language in the BibTeX distribution (see <a href="FAQ-BibTeXing.html">BibTeX documentation</a>). However, it must be admitted that the language in which BibTeX styles are written is pretty obscure, and one would not recommend @@ -18,8 +17,15 @@ to produce a file of instructions, with which you can generate your own <code>.bst</code> file. This technique doesn’t offer entirely new styles of document, but the system’s “master BibTeX styles” already offer significantly more than the BibTeX standard set. +<p/>An alternative, which is increassingly often recommended, to use +<a href="FAQ-biblatex.html"><i>biblatex</i></a>. <i>Biblatex</i> offers +many hooks for adjusting the format of the output of your ‘basic’ +BibTeX style, and a collection of ‘contributed’ styles have also +started to appear. <dl> -<dt><tt><i>BibTeX documentation</i></tt><dd><a href="http://mirror.ctan.org/biblio/bibtex/contrib/doc.zip">biblio/bibtex/contrib/doc</a> (or <a href="http://mirror.ctan.org/biblio/bibtex/contrib/doc/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/bibtex.html">catalogue entry</a> +<dt><tt><i>biblatex.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/biblatex.zip">macros/latex/contrib/biblatex</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/biblatex/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/biblatex.html">catalogue entry</a> +<dt><tt><i>biblatex contributed styles</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/biblatex-contrib">macros/latex/contrib/biblatex-contrib</a> +<dt><tt><i>BibTeX documentation</i></tt><dd><a href="http://mirror.ctan.org/biblio/bibtex/base.zip">biblio/bibtex/base</a> (or <a href="http://mirror.ctan.org/biblio/bibtex/base/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/bibtex.html">catalogue entry</a> <dt><tt><i>makebst.tex</i></tt><dd>Distributed with <a href="http://mirror.ctan.org/macros/latex/contrib/custom-bib.zip">macros/latex/contrib/custom-bib</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/custom-bib/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/custom-bib.html">catalogue entry</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> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-dirs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-dirs.html index aabfa0a34e7..e5349507ed7 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-dirs.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-doc-dirs.html @@ -8,8 +8,5 @@ from <a href="http://www.tug.org.in/tutorials.html">http://www.tug.org.in/tutori set comprises two parts, “Text” and “Graphics”, so far. <p/>Once, there were other links like that, but all the others have faded away, leaving the TUG India set in splendid isolation. -<p/> - - <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-dist/doc/generic/FAQ-en/html/FAQ-dpfloat.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dpfloat.html index a0b69a2f585..8f9814bbb09 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dpfloat.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-dpfloat.html @@ -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 need 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: @@ -20,10 +20,37 @@ this: the construction to use is: \end{figure} </pre> </blockquote><p> -The construction has no effect unless the standard class option -<code>twoside</code> is in effect. +The construction has no effect on documents with class option +<code>oneside</code> (<code>twoside</code> is the default for +<i>book</i> class). +<p/>A special case of this requirement places the caption for a float on +the next page. (This is useful if you have a float that “only just” +fits the page.) You can (with a certain amount of twiddling) make +this work with <i>dpfloat</i>, but the <i>fltpage</i> package is +specially designed for the job: +<blockquote> +<pre> +\documentclass[twoside]{article} +\usepackage[leftFloats]{fltpage} +\begin{document} +... +\begin{FPfigure} + \includegraphics{my-huge-figure} + \caption{Whew! That was a big one!} +\end{FPfigure} +... +\end{document} +</pre> +</blockquote><p> +That example should produce a caption +<blockquote> + Figure <em>n (facing page)</em>: Whew! … +</blockquote><p> +(Note, however, that the package is an old one, and declares itself to +be a beta release. I seems to work, but…) <dl> <dt><tt><i>dpfloat.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/dpfloat.zip">macros/latex/contrib/dpfloat</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/dpfloat/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/dpfloat.html">catalogue entry</a> +<dt><tt><i>fltpage.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/fltpage.zip">macros/latex/contrib/fltpage</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/fltpage/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/fltpage.html">catalogue entry</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> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawing.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawing.html index 8e0245aecb6..2714ba016a8 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawing.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-drawing.html @@ -63,6 +63,9 @@ of drawing, and setup, here are a few systems you may consider: all the power of Metafont, but it generates PostScript figures; MetaPost is nowadays part of most serious (La)TeX distributions. Knuth uses it for all his work… +<p/> Note that you can “embed” MetaPost source in your document (i.e., + keep it in-line with your LaTeX code), using the <i>emp</i> + package. <li> <i>Mfpic</i>; you liked Metafont, but can’t understand the language? The package makes up Metafont or MetaPost code for you within using familiar-looking TeX macros. Not <em>quite</em> the @@ -74,12 +77,46 @@ of drawing, and setup, here are a few systems you may consider: other TeX drawing packages, but is an entirely new implementation, which is not as hard on memory, is much more readable (and is fully documented). +<li> You fancy the idea of embedding the source of drawings (as with + <i>emp</i>, but you like another drawing tool? In principle, + it’s possible to do the same with other tools; for example + <i>asyfig</i> allows you to embed + <i>asymptote</i> code in your document. </ul> +<p/>Some of the free-standing graphics applications may also be used +(effectively) in-line in LaTeX documents; examples are <dl> +<dt>asymptote<dd>A package, <i>asymptote</i>, defines an environment + <code>asy</code> which arranges that its contents are included + (after “enough” runs, in the LaTeX way). +<p/> Basically, you write + <blockquote> + <code>\</code><code>begin{asy}</code> + <code><<i>asymptote code</i>></code> + <code>\</code><code>end{asy}</code> + </blockquote><p> + and then execute +<blockquote> +<pre> +latex document +asy document-*.asy +latex document +</pre> +</blockquote><p> +<dt>egplot<dd>Allows you to incorporate <i>GNUplot</i> + code in your document, again for processing outside of LaTeX; the + design of this package was strongly influenced by that of <i>emp</i> +<dt>emp<dd>Another of the same, this time for MetaPost graphics. +</dl> +<dl> +<dt><tt><i>asymptote.sty</i></tt><dd><a href="http://mirror.ctan.org/graphics/asymptote.zip">graphics/asymptote</a> (or <a href="http://mirror.ctan.org/graphics/asymptote/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/asymptote.html">catalogue entry</a> <dt><tt><i>dratex.sty</i></tt><dd><a href="http://mirror.ctan.org/graphics/dratex.zip">graphics/dratex</a> (or <a href="http://mirror.ctan.org/graphics/dratex/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/dratex.html">catalogue entry</a> +<dt><tt><i>egplot</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/egplot.zip">macros/latex/contrib/egplot</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/egplot/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/egplot.html">catalogue entry</a> +<dt><tt><i>emp</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/emp.zip">macros/latex/contrib/emp</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/emp/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/emp.html">catalogue entry</a> <dt><tt><i>epic.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/epic.zip">macros/latex/contrib/epic</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/epic/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/epic.html">catalogue entry</a> <dt><tt><i>eepic.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/eepic.zip">macros/latex/contrib/eepic</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/eepic/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/eepic.html">catalogue entry</a> <dt><tt><i>eepicemu.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/eepic.zip">macros/latex/contrib/eepic</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/eepic/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/eepic.html">catalogue entry</a> +<dt><tt><i>emp.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/emp.zip">macros/latex/contrib/emp</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/emp/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/emp.html">catalogue entry</a> <dt><tt><i>mfpic</i></tt><dd><a href="http://mirror.ctan.org/graphics/mfpic.zip">graphics/mfpic</a> (or <a href="http://mirror.ctan.org/graphics/mfpic/">browse the directory</a>) <dt><tt><i>preview.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/preview.zip">macros/latex/contrib/preview</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/preview/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/preview.html">catalogue entry</a> <dt><tt><i>pspicture.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/pspicture.zip">macros/latex/contrib/pspicture</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/pspicture/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/pspicture.html">catalogue entry</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-editors.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-editors.html index 0eeec553de0..389c794409a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-editors.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-editors.html @@ -38,18 +38,18 @@ personal selection: window manager provides GUI “shell-like” facilities, in a similar way to the widely-praised <i>Winedt</i> (see below); details (and downloads) are available from the project’s - <a href="http://kile.sourceforge.net/">home on SourceForge</a>. A newer - system (by <i>Kile</i>’s original author), - <a href="http://www.xm1math.net/texmaker/"><i>texmaker</a></i> doesn’t - rely on KDE’s facilities, and so may be more easily portable. -<dt>MSDOS<dd> TeXshell is a simple, - easily-customisable environment, which can be used with the editor - of your choice. -<p/> You can also use GNU <i>emacs</i> and AUC-TeX - under MSDOS. -<dt>Windows ’9x, NT, etc.<dd><i>TeXnicCenter</i> is a (free) + <a href="http://kile.sourceforge.net/">home on SourceForge</a>. +<p/> TUG is sponsoring the development of a cross-platform editor + and shell, modelled on the excellent TeXshop for the Macintosh. + While this program, + <a href="http://www.tug.org/texworks/">TeXworks</a>, is still under + development, it is already quite usable: if you’re looking for a + (La)TeX development environment, and are willing to step beyond + the boundaries, it may be for you. +<dt>Windows-32<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/> TeXworks (see above) is also available for Windows systems. <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. The editor can @@ -58,27 +58,19 @@ personal selection: “next-generation” (La)TeX applications). <p/> Both <i>emacs</i> and <i>vim</i> are available in versions for Windows systems. -<dt>OS/2<dd> <i>epmtex</i> offers an OS/2-specific shell. -<dt>Macintosh<dd> The commercial Textures provides an excellent integrated - Macintosh environment with its own editor. More powerful still (as an - 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. From release 2.2.0 (at least), Textures - works with Mac OS/X. -<p/> For Mac OS/X users, the free tool of choice appears to be - <a href="http://www.uoregon.edu/~koch/texshop/texshop.html">TeXshop</a>, which +<dt>Macintosh<dd> For Mac OS/X users, the free tool of choice appears to be + <a href="http://pages.uoregon.edu/koch/texshop/index.html">TeXshop</a>, which combines an editor and a shell with a coherent philosophy of dealing 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. -<dt>Wildcard<dd> TUG is sponsoring the development of a - cross-platform editor and shell, modelled on the excellent - TeXshop for the Macintosh. While this program, - <a href="http://www.tug.org/texworks/">TeXworks</a>, is still under - development, it is already quite usable: if you’re looking for a - (La)TeX development environment, and are willing to step beyond - the boundaries, it may be for you. +<p/> The commercial Textures provides an excellent integrated Macintosh + environment with its own editor. More powerful still (as an editor) + is the shareware <i>Alpha</i> which is extensible enough to let + you perform almost any TeX-related job. It also works well with + OzTeX. From release 2.2.0 (at least), Textures works under Mac OS/X. +<dt>OS/2<dd> <i>epmtex</i> offers an OS/2-specific shell. </dl> Atari, Amiga and NeXT users also have nice environments. LaTeX users looking for <i>make</i>-like @@ -93,7 +85,7 @@ access to your BibTeX files — <dt><tt><i>alpha</i></tt><dd><a href="http://mirror.ctan.org/systems/mac/support/alpha">systems/mac/support/alpha</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/alpha.html">catalogue entry</a> <dt><tt><i>auctex</i></tt><dd><a href="http://mirror.ctan.org/support/auctex">support/auctex</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/auctex.html">catalogue entry</a> <dt><tt><i>epmtex</i></tt><dd><a href="http://mirror.ctan.org/systems/os2/epmtex.zip">systems/os2/epmtex</a> (or <a href="http://mirror.ctan.org/systems/os2/epmtex/">browse the directory</a>) -<dt><tt><i>LaTeX4Jed</i></tt><dd><a href="http://mirror.ctan.org/support/jed.zip">support/jed</a> (or <a href="http://mirror.ctan.org/support/jed/">browse the directory</a>) +<dt><tt><i>LaTeX4Jed</i></tt><dd><a href="http://mirror.ctan.org/support/jed.zip">support/jed</a> (or <a href="http://mirror.ctan.org/support/jed/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/latex4jed.html">catalogue entry</a> <dt><tt><i>Nedit LaTeX support</i></tt><dd><a href="http://mirror.ctan.org/support/NEdit-LaTeX-Extensions.zip">support/NEdit-LaTeX-Extensions</a> (or <a href="http://mirror.ctan.org/support/NEdit-LaTeX-Extensions/">browse the directory</a>) <dt><tt><i>TeXnicCenter</i></tt><dd><a href="http://mirror.ctan.org/systems/win32/TeXnicCenter">systems/win32/TeXnicCenter</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/texniccenter.html">catalogue entry</a> <dt><tt><i>TeXshell</i></tt><dd><a href="http://mirror.ctan.org/systems/msdos/texshell.zip">systems/msdos/texshell</a> (or <a href="http://mirror.ctan.org/systems/msdos/texshell/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/texshell.html">catalogue entry</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filename.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filename.html index 807ac5b8872..81f528daa1e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filename.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-filename.html @@ -19,90 +19,109 @@ file name. This is particularly difficult in the case of Plain TeX, since the syntax of the <code>\</code><code>input</code> command is so peculiar. <p/>In the case of LaTeX, the input commands have pretty regular syntax, and the simplest <a href="FAQ-patch.html">patching techniques</a> can be -used on them. -<p/>If you’re not inputting things from a file that’s already been input, -the job is almost trivial: -<blockquote> -<pre> -\def\ThisFile{\jobname} -\let\OldInput\input -\renewcommand{\input}[1]{% - \renewcommand{\ThisFile}{#1}% - \OldInput#1% -} -</pre> -</blockquote><p> -With that, the macro <code>\</code><code>ThisFile</code> always contains the last thing -input: it starts pointing at the base file of your document -(<code>\</code><code>jobname</code>), and thereafter changes every time you use -<code>\</code><code>input{</code><em>file</em><code>}</code>. Note that this is not satisfactory if your -document contains things <em>other</em> than <code>\</code><code>input</code> commands. For -example, in: -<blockquote> -<pre> -\documentclass{article} -... (macros above) -\begin{document} -\input{preamble} -<body of document> -\input{postamble} -\end{document} -</pre> -</blockquote><p> -<code>\</code><code>ThisFile</code> contains <code>postamble</code> throughout the -<<i>body of document</i>>. -<p/>Most ordinary users will quickly become irritated with the simplicity -of of the <code>\</code><code>ThisFile</code> mechanism above. The following code is more -cunning: it maintains details of the files you’ve ‘come through’ to -get to where you are, and it restores <code>\</code><code>ThisFile</code> to what the -previous file was before returning. -<blockquote> -<pre> -\def\ThisFile{\jobname} -\newcounter{FileStack} -\let\OrigInput\input -\renewcommand{\input}[1]{% - \stackinput{#1}{\OrigInput}% -} -\newcommand{\stackinput}[2]{% - \stepcounter{FileStack}% - \expandafter\let - \csname NameStack\theFileStack\endcsname - \ThisFile - \def\ThisFile{#1}% - #2#1% - \expandafter\let\expandafter - \ThisFile - \csname NameStack\theFileStack\endcsname - \addtocounter{FileStack}{-1}% -} -</pre> -</blockquote><p> -To do the same for <code>\</code><code>include</code>, we need the simple addition: -<blockquote> -<pre> -\let\OrigInclude\include -\renewcommand{\include}[1]{% - \stackinput{#1}{\OrigInclude}% -} -</pre> -</blockquote><p> -Both examples of patching <code>\</code><code>input</code> assume you always use -LaTeX syntax, i.e., always use braces around the argument. -<p/>The <i>FiNK</i> (“File Name Keeper”) package provides a -regular means of keeping track of the current file name (with its -extension), in a macro <code>\</code><code>finkfile</code>. If you need the unadorned file -name (without its ‘<code>.tex</code>’), use the commands: -<blockquote> -<pre> -\def\striptexext#1.tex{#1} -... -\edef\ThisFile{\expandafter\stripext\finkfile} -</pre> -</blockquote><p> +used on them. (Note that latex’s <code>\</code><code>input</code> command is itself a +patch on top of the Plain TeX command. Our patches apply to the +LaTeX version of the command, which is used as <code>\</code><code>input{</code><em>file</em><code>}</code>) +<p/> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<p/> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +<p/>It is possible to keep track of the name of the file currently being +processed, but it’s surprisingly difficult (these FAQs offered +code, for a long time, that just didn’t work in many cases). +<p/>The <i>currfile</i> package provides a regular means of keeping +track of the details of the current file (its name in +<code>\</code><code>currfilename</code>, directory in <code>\</code><code>currfiledir</code>, as well as the +file ‘base’ name (less its extension) and its extension). +<i>Currfile</i> does this with the help of a second package, +<i>filehook</i>, which spots file operations that use <code>\</code><code>input</code>, +<code>\</code><code>InputIfFileExists</code> and <code>\</code><code>include</code>, as well as package and +class loading. +<p/>The <i>FiNK</i> (“File Name Keeper”) package keeps track of the +file name and extension, in a macro <code>\</code><code>finkfile</code>. <i>FiNK</i> is +now deprecated, in favour of <i>currfile</i>, but remains available +for use in old documents. + + + + + + + + + + + The <i>FiNK</i> bundle includes a <i>fink.el</i> that provides support under <i>emacs</i> with AUC-TeX. <dl> +<dt><tt><i>currfile.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/currfile.zip">macros/latex/contrib/currfile</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/currfile/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/currfile.html">catalogue entry</a> +<dt><tt><i>filehook.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/filehook.zip">macros/latex/contrib/filehook</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/filehook/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/filehook.html">catalogue entry</a> <dt><tt><i>fink.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/fink.zip">macros/latex/contrib/fink</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/fink/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/fink.html">catalogue entry</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> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floats.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floats.html index 8def4b57e1f..d5e5101102e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floats.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-floats.html @@ -72,8 +72,23 @@ equally well to tables, or to “non-standard” floats defined by the resort if the other possibilities below don’t help. <li> If you would actually <em>like</em> great blocks of floats at the end of each of your chapters, try the <i>morefloats</i> package; - this ‘simply’ increases the number of floating inserts that LaTeX - can handle at one time (from 18 to 36). + this allows you to increase the number of floating inserts that LaTeX + can handle at one time (from its original value of 18, in + LaTeX2e). Note that, even with e-TeX’s greater supply of + registers, there is still a modest limit on the total number of + floating inserts (e-TeX increases the total number of registers + available, but inserts don’t work if they are constructed from + registers in the extended range). +<p/> Caveat: if you are using <i>etex</i> to increase the number of + registers available, you need to “reserve” some inserts for + <i>morefloats</i>: something like: + <blockquote> +<pre> +\usepackage{etex} +\reserveinserts{18} +\usepackage{morefloats} +</pre> + </blockquote><p> <li> If you actually <em>wanted</em> all your figures to float to the end (<em>e.g</em>., for submitting a draft copy of a paper), don’t rely on LaTeX’s mechanism: get the <i>endfloat</i> package to do @@ -82,9 +97,10 @@ equally well to tables, or to “non-standard” floats defined by the <dl> <dt><tt><i>afterpage.sty</i></tt><dd>Distributed as part of <a href="http://mirror.ctan.org/macros/latex/required/tools.zip">macros/latex/required/tools</a> (or <a href="http://mirror.ctan.org/macros/latex/required/tools/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/afterpage.html">catalogue entry</a> <dt><tt><i>endfloat.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/endfloat.zip">macros/latex/contrib/endfloat</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/endfloat/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/endfloat.html">catalogue entry</a> +<dt><tt><i>etex.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/etex-pkg.zip">macros/latex/contrib/etex-pkg</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/etex-pkg/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/etex-pkg.html">catalogue entry</a> <dt><tt><i>flafter.sty</i></tt><dd>Part of the LaTeX distribution <dt><tt><i>float.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/float/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/float.html">catalogue entry</a> -<dt><tt><i>morefloats.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/misc/morefloats.sty">macros/latex/contrib/misc/morefloats.sty</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/morefloats.html">catalogue entry</a> +<dt><tt><i>morefloats.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/morefloats.zip">macros/latex/contrib/morefloats</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/morefloats/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/morefloats.html">catalogue entry</a> <dt><tt><i>placeins.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/placeins.zip">macros/latex/contrib/placeins</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/placeins/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/placeins.html">catalogue entry</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> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fmtconv.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fmtconv.html index d38ec5a0b3b..44127962215 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fmtconv.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-fmtconv.html @@ -34,11 +34,23 @@ TeX2RTF is supported on various Unix platforms and under Windows 3.1 <dt>Microsoft Word<dd> A rudimentary (free) program for converting - MS-Word to LaTeX is <i>wd2latex</i>, which runs on MSDOS. - <i>Word2</i><em>TeX</em> and <em>TeX</em><i>2Word</i> are + MS-Word to LaTeX is <i>wd2latex</i>, which runs on MSDOS; + it probably produces output destined for an archaic version of + MS-Word (the program itself was archived in 1991). +<p/> The current preferred free-software method is a two-stage process: + <ul> + <li> Convert LaTeX to <i>OpenOffice</i> format, using the + <i>tex4ht</i> command <i>oolatex</i>; + <li> open the result in <i>OpenOffice</i> and ‘save as’ a + MS-Word document. + </ul> + (Note that <i>OpenOffice</i> itself is <em>not</em> on + CTAN; see <a href="http://www.openoffice.org/">http://www.openoffice.org/</a>, though most + <i>linux</i> systems offer it as a ready-to-install bundle.) +<p/> <i>Word2</i><em>TeX</em> and <em>TeX</em><i>2Word</i> are shareware translators from - <a href="http://www.chikrii.com/">Chikrii Softlab</a>; users’ reports are - very positive. + <a href="http://www.chikrii.com/">Chikrii Softlab</a>; positive users’ + reports have been noted (but not recently). <p/> The excellent <i>tex4ht</i> will generate OpenOffice ODT format, which can be used as an intermediate to producing Word format files. @@ -86,6 +98,7 @@ translated to or from this one. <i>FrameMaker</i> provides <dt><tt><i>rtf2latex2e</i></tt><dd><a href="http://mirror.ctan.org/support/rtf2latex2e.zip">support/rtf2latex2e</a> (or <a href="http://mirror.ctan.org/support/rtf2latex2e/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/rtf2latex2e.html">catalogue entry</a> <dt><tt><i>rtf2tex</i></tt><dd><a href="http://mirror.ctan.org/support/rtf2tex.zip">support/rtf2tex</a> (or <a href="http://mirror.ctan.org/support/rtf2tex/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/rtf2tex.html">catalogue entry</a> <dt><tt><i>tex2rtf</i></tt><dd><a href="http://mirror.ctan.org/support/tex2rtf.zip">support/tex2rtf</a> (or <a href="http://mirror.ctan.org/support/tex2rtf/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/tex2rtf.html">catalogue entry</a> +<dt><tt><i>tex4ht</i></tt><dd><a href="http://mirror.ctan.org/obsolete/support/TeX4ht/tex4ht-all.zip">obsolete/support/TeX4ht/tex4ht-all.zip</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/tex4ht.html">catalogue entry</a> (but see <a href="http://tug.org/tex4ht/">http://tug.org/tex4ht/</a>) <dt><tt><i>tr2latex</i></tt><dd><a href="http://mirror.ctan.org/support/tr2latex.zip">support/tr2latex</a> (or <a href="http://mirror.ctan.org/support/tr2latex/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/tr2latex.html">catalogue entry</a> <dt><tt><i>wd2latex</i></tt><dd><a href="http://mirror.ctan.org/support/wd2latex.zip">support/wd2latex</a> (or <a href="http://mirror.ctan.org/support/wd2latex/">browse the directory</a>) <dt><tt><i>wp2latex</i></tt><dd><a href="http://mirror.ctan.org/support/wp2latex.zip">support/wp2latex</a> (or <a href="http://mirror.ctan.org/support/wp2latex/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/wp2latex.html">catalogue entry</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-getbitmap.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-getbitmap.html index 6cbea116594..90d8b8a93c6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-getbitmap.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-getbitmap.html @@ -34,18 +34,17 @@ for general public use by their originators Y&Y and Bluesky Research, in association with the AMS and other scientific publishers (they are nowadays available under the SIL’s Open Fonts Licence). The 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 - +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 +uncommon ever 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>), 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. +<a href="FAQ-uselmfonts.html">Latin Modern fonts</a> are both close relatives with +wider ranges of glyphs to offer. <dl> <dt><tt><i>BaKoMa fonts</i></tt><dd><a href="http://mirror.ctan.org/fonts/cm/ps-type1/bakoma.zip">fonts/cm/ps-type1/bakoma</a> (or <a href="http://mirror.ctan.org/fonts/cm/ps-type1/bakoma/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/bakoma-fonts.html">catalogue entry</a> <dt><tt><i>Bluesky fonts</i></tt><dd>Distributed as part of @@ -55,5 +54,6 @@ Computer Modern with wider ranges of glyphs to offer. <dt><tt><i>EC fonts (Type 1 format)</i></tt><dd><a href="http://mirror.ctan.org/fonts/ps-type1/cm-super.zip">fonts/ps-type1/cm-super</a> (or <a href="http://mirror.ctan.org/fonts/ps-type1/cm-super/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/cm-super.html">catalogue entry</a> <dt><tt><i>Latin Modern fonts</i></tt><dd><a href="http://mirror.ctan.org/fonts/lm.zip">fonts/lm</a> (or <a href="http://mirror.ctan.org/fonts/lm/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/lm.html">catalogue entry</a> </dl> + <p/><p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=getbitmap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=getbitmap</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gethelp.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gethelp.html index 3969414d67e..96f9eeffa3a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gethelp.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-gethelp.html @@ -18,7 +18,7 @@ Each catalogue entry has a brief description of the package, and links to any known documentation on the net. In fact, a large proportion of CTAN package directories now include documentation, so it’s often worth looking at the catalogue entry for a package you’re considering -using (where possible, each in package link in the main body of these +using (where possible, each package link in the main body of these FAQs has a link to the relevant catalogue entry). <p/>Failing all that, look to see if anyone else has had the problem @@ -27,7 +27,7 @@ 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>, or (as a long shot) -the archives of ancient posts on CTAN. +the archives of its ancient posts on CTAN. <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 @@ -36,6 +36,12 @@ 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/>Other alternative sources are the +<a href="http://www.latex-community.org/">“LaTeX community” site</a> or +<a href="http://tex.stackexchange.com/">TeX, LaTeX and friends Q&A site</a>. +Neither of these is particularly long-established (the “friends” +site is still in beta state at +the time of writing), but they’re already popular and helpful. <p/>Do <b>not</b> try mailing the <a href="FAQ-LaTeX3.html">LaTeX project team</a>, the maintainers of the TeX Live or MiKTeX distributions diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html index 7b2273759b1..ed6f705ccf3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-graphicspath.html @@ -29,26 +29,33 @@ inconvenient to use in Windows setups (at least). 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 sequence of paths (typically relative paths), each of which is -enclosed in braces. A slightly odd sample, given in the -<i>graphics</i> bundle documentation, is: +enclosed in braces. A slightly odd example (slightly modified from one +given in the <i>graphics</i> bundle documentation) is: <blockquote> <pre> -\graphicspath{{eps/}{tiff/}} +\graphicspath{{eps/}{png/}} </pre> </blockquote><p> -however, if the security checks on your (La)TeX system allow, the -path may be anything you choose (rather than strictly relative, like -those above); note that the trailing “<code>/</code>” <em>is</em> required. +which will search for graphics files in subdirectories <i>eps</i> and +<i>png</i> of the directory in which LaTeX is running. (Note that +the trailing “<code>/</code>” <em>is</em> required.) +<p/>(Note that some (La)TeX systems will only allow you to use files in +the current directory and its sub-directories, for security reasons. +However, <code>\</code><code>graphicspath</code> imposes no such restriction: as far as +<em>it</em> is concerned, you can access files anywhere.) <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 -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/>The slight disadvantage of the <code>\</code><code>graphicspath</code> method is +inefficiency. The package will call (La)TeX once for each entry in +the list to look for a file, which of course slows things. Further, +(La)TeX remembers the name of any file it’s asked to look up, thus +effectively losing memory, so that in the limit a document that uses a +huge number of graphical inputs could be embarrassed by lack of +memory. (Such “memory starvation” is pretty unlikely with any +ordinary document in a reasonably modern (La)TeX system, but it +should be borne in mind.) <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 diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst1cm.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst1cm.html index fc9f48f1cc8..b05ef0b9fff 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst1cm.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-inst1cm.html @@ -18,15 +18,15 @@ at a “command prompt” (<i>shell</i>, in a Unix-style system, “DOS box” in a Windows system). <p/>If the command works at all, the console output of the command will include a sequence of Type 1 font file names, listed as -<code><cmr10.pfb></code> and so on; this is <i>dvips</i> telling you -it’s copying information from the Type 1 font, and you need do no -more. +<code><<em>path</em>/cmr10.pfb></code> and so on; this is <i>dvips</i> +telling you it’s copying information from the Type 1 font, and you +need do no more. <p/>If the test has failed, you need to install your own set of the fonts; the distribution (including all the fonts the AMS designed and produced themselves) is now described as <i>amsfonts</i>. The bundle contains metric and map files — all you need to <a href="FAQ-instt1font.html">install the fonts</a>. -<p/><dl> +<dl> <dt><tt><i>AMS and CM fonts, in Type 1 format</i></tt><dd><a href="http://mirror.ctan.org/fonts/amsfonts.zip">fonts/amsfonts</a> (or <a href="http://mirror.ctan.org/fonts/amsfonts/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/amsfonts.html">catalogue entry</a> </dl> <p/><p/> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instt1font.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instt1font.html index 0417b7a5fe3..19b569be1df 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instt1font.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-instt1font.html @@ -23,7 +23,7 @@ much of what follows will be familiar: </pre> but if you are lucky, you will be starting from a distribution from CTAN and there is a corresponding <code>.tds.zip</code> file: - using the TDS-file saves the bother of deciding where to put + using this TDS-file saves the bother of deciding where to put your files in the TDS tree. <li> Regenerate the file indexes (as described in <a href="FAQ-inst-wlcf.html">package installation</a>). @@ -36,9 +36,11 @@ much of what follows will be familiar: updmap-sys --enable Map <fname>.map </pre> </blockquote><p> - as root. (Do <em>not</em> use plain <i>updmap</i>: it’s a - potent source of confusion, setting up different map sets - for different users.) + as root. (If you <em>can</em> use <i>updmap-sys</i> — do; if + not — presumably because your (La)TeX system was set up by + someone else — you have to fall back on plain <i>updmap</i>, + but be aware that it’s a potent source of confusion, setting up + map sets that might be changed behind your back.) <li> On a current MiKTeX system, update the system file <i>updmap.cfg</i>, using the shell command <blockquote> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelfig.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelfig.html index c92beebbda0..5d59b75b8e8 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelfig.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-labelfig.html @@ -48,7 +48,13 @@ another. 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/>The <i>lpic</i> package is somewhat similar to <i>overpic</i>; +it defines an environment <code>lpic</code> (which places your +graphic for you): within the environment you may use the command +<code>\</code><code>lbl</code> to position LaTeX material at appropriate places over the +graphic. <p/><i>Pstricks</i> can of course do everything that <i>overpic</i> +or <i>lpic</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> @@ -63,6 +69,7 @@ with the do-it-yourself approach. <dt><tt><i>auto-pst-pdf.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/auto-pst-pdf.zip">macros/latex/contrib/auto-pst-pdf</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/auto-pst-pdf/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/auto-pst-pdf.html">catalogue entry</a> <dt><tt><i>iTe</i></tt><dd><a href="http://mirror.ctan.org/support/ite.zip">support/ite</a> (or <a href="http://mirror.ctan.org/support/ite/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/ite.html">catalogue entry</a> <dt><tt><i>laprint</i></tt><dd>Distributed with <a href="http://mirror.ctan.org/macros/latex/contrib/psfragx.zip">macros/latex/contrib/psfragx</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/psfragx/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/psfragx.html">catalogue entry</a> +<dt><tt><i>lpic.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/lpic.zip">macros/latex/contrib/lpic</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/lpic/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/lpic.html">catalogue entry</a> <dt><tt><i>overpic.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/overpic.zip">macros/latex/contrib/overpic</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/overpic/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/overpic.html">catalogue entry</a> <dt><tt><i>psfrag.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/psfrag.zip">macros/latex/contrib/psfrag</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/psfrag/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/psfrag.html">catalogue entry</a> <dt><tt><i>psfragx.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/psfragx.zip">macros/latex/contrib/psfragx</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/psfragx/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/psfragx.html">catalogue entry</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lollipop.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lollipop.html deleted file mode 100644 index db28b1b0f65..00000000000 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-lollipop.html +++ /dev/null @@ -1,31 +0,0 @@ -<head> -<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 -the production of his book “<em>TeX by Topic</em>” (see -<a href="FAQ-ol-books.html">(La)TeX Tutorials</a>). The manual says of -it: -<blockquote> - Lollipop is ‘TeX made easy’. Lollipop is a macro package that - functions as a toolbox for writing TeX macros. It was my - intention to make macro writing so easy that implementing a fully - new layout in TeX would become a matter of less than an hour for - 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 - 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 -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="http://mirror.ctan.org/macros/lollipop.zip">macros/lollipop</a> (or <a href="http://mirror.ctan.org/macros/lollipop/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/lollipop.html">catalogue entry</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> -</body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-latex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-latex.html index 4830a53991e..2dcf2d965db 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-latex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-man-latex.html @@ -62,7 +62,7 @@ the source is also available). <dt><tt><i>Not so Short Introduction</i></tt><dd><a href="http://mirror.ctan.org/info/lshort/english.zip">info/lshort/english</a> (or <a href="http://mirror.ctan.org/info/lshort/english/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/lshort-english.html">catalogue entry</a> (in English, you may browse for sources and other language versions at <a href="http://mirror.ctan.org/info/lshort">info/lshort</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/lshort.html">catalogue entry</a>) -<dt><tt><i>Simplified LaTeX</i></tt><dd><a href="http://mirror.ctan.org/info/simplified-latex/simplified-intro.ps">info/simplified-latex/simplified-intro.ps</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/simplified-latex.html">catalogue entry</a> +<dt><tt><i>Simplified LaTeX</i></tt><dd><a href="http://mirror.ctan.org/info/simplified-latex/simplified-intro.pdf">info/simplified-latex/simplified-intro.pdf</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/simplified-latex.html">catalogue entry</a> <dt><tt><i>Short Course in LaTeX</i></tt><dd><a href="http://mirror.ctan.org/info/Math_into_LaTeX-4/Short_Course.pdf">info/Math_into_LaTeX-4/Short_Course.pdf</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/math-into-latex-4.html">catalogue entry</a> <dt><tt><i>The sins of LaTeX users</i></tt><dd><a href="http://mirror.ctan.org/info/l2tabu/english/l2tabuen.pdf">info/l2tabu/english/l2tabuen.pdf</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/l2tabu-english.html">catalogue entry</a>; diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathml.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathml.html index 81c7636a2f9..28e4f7ba8ed 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathml.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-mathml.html @@ -106,7 +106,7 @@ support for new Web standards. <dt><tt><i>GELLMU</i></tt><dd><a href="http://mirror.ctan.org/support/gellmu.zip">support/gellmu</a> (or <a href="http://mirror.ctan.org/support/gellmu/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/gellmu.html">catalogue entry</a> <dt><tt><i>MathTeX</i></tt><dd><a href="http://mirror.ctan.org/support/mathtex">support/mathtex</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/mathtex.html">catalogue entry</a> <dt><tt><i>MimeTeX</i></tt><dd><a href="http://mirror.ctan.org/support/mimetex">support/mimetex</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/mimetex.html">catalogue entry</a> -<dt><tt><i>TeX4HT</i></tt><dd><a href="http://mirror.ctan.org/support/TeX4ht/tex4ht-all.zip">support/TeX4ht/tex4ht-all.zip</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/tex4ht.html">catalogue entry</a> +<dt><tt><i>tex4ht</i></tt><dd><a href="http://mirror.ctan.org/obsolete/support/TeX4ht/tex4ht-all.zip">obsolete/support/TeX4ht/tex4ht-all.zip</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/tex4ht.html">catalogue entry</a> (but see <a href="http://tug.org/tex4ht/">http://tug.org/tex4ht/</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> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html index 4b4cd03e786..6c67cecfec9 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-metrics.html @@ -1,7 +1,7 @@ <head> <title>UK TeX FAQ -- question label metrics</title> </head><body> -<h3>TeX font metric files for PostScript fonts</h3> +<h3>TeX font metric files for Type 1 fonts</h3> <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 diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-music.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-music.html index ac13464522e..67627a7df4a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-music.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-music.html @@ -9,20 +9,27 @@ 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 -a three-pass system (with a processor program that computes values for -the element spacing in the music), and achieves finer control than is -possible in the unmodified TeX-based mechanism that MusicTeX -uses. Daniel Taupin’s is the only version of MusiXTeX currently -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’ -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/>MusicTeX has been superseded by a further development called +MusiXTeX, which is a three-pass system (with a processor program +that computes values for the element spacing in the music, and sorts +out spaces and ties (which MusicTeX does “woodenly” — playing +from a MusicTeX-typeset page is entirely possible, but the look of +the slurs is very unsatisfying). Thus MusixTeX achieves finer +control than is possible with the unmodified TeX-based mechanism +that MusicTeX uses. +<p/>The original author of MusixTeX, Andreas Egler, withdrew from +development of the package; he has a further package OpusTeX (not +on CTAN) which is focused on typesetting Gregorian chant and +the like. +<p/>Daniel Taupin forked his development of MusiXTeX, and his is the +only version currently maintained (by Daniel’s successors, since +Daniel died). +<p/>Input to MusiXTeX is 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; it operates “on top of” <i>pmx</i> <p/>Another simple notation is supported by <i>abc2mtex</i>; this is a @@ -37,13 +44,13 @@ extendable to many other types of music. MusicTeX source code. <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 +MusiXTeX and related systems. To subscribe, use <a href="http://icking-music-archive.org/mailman/listinfo/tex-music/">http://icking-music-archive.org/mailman/listinfo/tex-music/</a> <p/>An alternative (free) means of embedding music examples into (La)TeX documents is <a href="http://www.lilypond.org">Lilypond</a>. Lilypond is (at heart) a batch music typesetting system with plain text input that does most of its work without TeX. Lilypond’s input syntax is far -less cryptic than is MusixTeX’s, and it handles much more stuff +less cryptic than is MusiXTeX’s, and it handles much more stuff automatically, yielding the same or better quality with less effort. Lilypond can also produce basic MIDI output. <dl> @@ -52,8 +59,8 @@ Lilypond can also produce basic MIDI output. <dt><tt><i>midi2tex</i></tt><dd><a href="http://mirror.ctan.org/support/midi2tex.zip">support/midi2tex</a> (or <a href="http://mirror.ctan.org/support/midi2tex/">browse the directory</a>) <dt><tt><i>musictex</i></tt><dd><a href="http://mirror.ctan.org/macros/musictex.zip">macros/musictex</a> (or <a href="http://mirror.ctan.org/macros/musictex/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/musictex.html">catalogue entry</a> -<dt><tt><i>musixtex (Taupin’s version)</i></tt><dd><a href="http://mirror.ctan.org/macros/musixtex/taupin.zip">macros/musixtex/taupin</a> (or <a href="http://mirror.ctan.org/macros/musixtex/taupin/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/musixtex.html">catalogue entry</a> -<dt><tt><i>musixtex (Egler’s version)</i></tt><dd><a href="http://mirror.ctan.org/macros/musixtex/egler.zip">macros/musixtex/egler</a> (or <a href="http://mirror.ctan.org/macros/musixtex/egler/">browse the directory</a>) +<dt><tt><i>musixtex (Taupin’s version)</i></tt><dd><a href="http://mirror.ctan.org/macros/musixtex.zip">macros/musixtex</a> (or <a href="http://mirror.ctan.org/macros/musixtex/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/musixtex.html">catalogue entry</a> +<dt><tt><i>musixtex (Egler’s version)</i></tt><dd><a href="http://mirror.ctan.org/obsolete/macros/musixtex/egler.zip">obsolete/macros/musixtex/egler</a> (or <a href="http://mirror.ctan.org/obsolete/macros/musixtex/egler/">browse the directory</a>) <dt><tt><i>mutex</i></tt><dd><a href="http://mirror.ctan.org/macros/mtex.zip">macros/mtex</a> (or <a href="http://mirror.ctan.org/macros/mtex/">browse the directory</a>) <dt><tt><i>pmx</i></tt><dd><a href="http://mirror.ctan.org/support/pmx.zip">support/pmx</a> (or <a href="http://mirror.ctan.org/support/pmx/">browse the directory</a>) </dl> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopagebrk.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopagebrk.html index cfae4c4a482..949742d954f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopagebrk.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-nopagebrk.html @@ -17,13 +17,13 @@ list items’ attempts — they suggest page breaks between items — are subverted by <code>samepage</code>). Naturally, if <code>samepage</code> <em>does</em> work, it is capable of leaving stuff jutting out at the bottom of the page. -<p/>A convenient trick is to set all the relevant stuff in a <code>\</code><code>parbox</code> -(or a <code>minipage</code> if it contains things like verbatim text -that may not be in the argument of a <code>\</code><code>parbox</code>). The resulting box -certainly <em>won’t</em> break between pages, but that’s not to say that -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/>Another 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 used 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 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 @@ -97,13 +97,22 @@ 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 the rather few words he says on the subject in the TeXbook) one can decide, case by case, how to deal with problems at the last -proof-reading stage. The alternatives are to insert <code>\</code><code>clearpage</code> -commands as necessary, or to use <code>\</code><code>enlargethispage</code>. Supposing you -have a line or two that stray: issue the command -<code>\</code><code>enlargethispage{2<code>\</code><code>baselineskip</code>}</code> and two lines are -added to the page you’re typesetting. It depends on the document -whether this looks impossibly awful or entirely acceptable, but the -command remains a useful item in the armoury. +proof-reading stage. At this stage, you can manually alter page +breaking, using either <code>\</code><code>pagebreak</code> or <code>\</code><code>clearpage</code>, or you can +place a <code>\</code><code>nopagebreak</code> command to suppress unfortunate breaks. +Otherwise, you can make small adjustments to the page geometry, using +<code>\</code><code>enlargethispage</code>. Supposing you have a line or two that stray: +issue the command <code>\</code><code>enlargethispage{2<code>\</code><code>baselineskip</code>}</code> and +two lines are added to the page you’re typesetting. Whether this +looks impossibly awful or entirely acceptable depends on the document +context, but the command remains a useful item in the armoury. +<p/>Note that both <code>\</code><code>pagebreak</code> and <code>\</code><code>nopagebreak</code> take an optional +number argument to adjust how the command is to be interpreted. Thus +<code>\</code><code>pagebreak[0]</code>, the command ‘suggests’ that a page break +might be worth doing, whereas <code>\</code><code>pagebreak[4]</code> ‘demands’ a +page break. Similarly <code>\</code><code>nopagebreak[0]</code> makes a suggestion, +while <code>\</code><code>nopagebreak[4]</code> is a demand. In both commands, the +default value of the optional argument is 4. <dl> <dt><tt><i>memoir.cls</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/memoir/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/memoir.html">catalogue entry</a> <dt><tt><i>needspace.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/needspace.zip">macros/latex/contrib/needspace</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/needspace/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/needspace.html">catalogue entry</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-otherprinters.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-otherprinters.html index c06aa99d76a..7f861062c7e 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-otherprinters.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-otherprinters.html @@ -16,7 +16,7 @@ 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://mirror.ctan.org/support/ghostscript">support/ghostscript</a> +<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/ghostscript/GPL">support/ghostscript/GPL</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/ghostscript-GPL.html">catalogue entry</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> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papergeom.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papergeom.html index 3c69972e33f..7dafe756415 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papergeom.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-papergeom.html @@ -35,7 +35,8 @@ and PDFTeX has system variables <code>\</code><code>pdfpagewidth</code> and Unfortunately, most of the core software predates PDFTeX, so not even PDFLaTeX sets the correct values into those variables, to match the paper size specified in a <code>\</code><code>documentclass</code> option. -<p/>The DVI drivers <i>dvips</i> and <i>dvipdfm</i> define +<p/>The DVI drivers <i>dvips</i>, <i>dvipdfm</i> and its +extensions (<i>dvipdfmx</i> and <i>xdvipdfmx</i>) define <code>\</code><code>special</code> commands for the document to specify its own paper size; so in those cases, as when PDFTeX or VTeX is being used, the paper size can be programmed by the document. Users who wish to, may @@ -51,21 +52,25 @@ If the document is being processed by LaTeX on a TeX or e-TeX engine, there are package options which instruct <i>geometry</i> which <code>\</code><code>special</code> commands to use. (Note that the options are 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, when you are using LaTeX, is to add <blockquote> <pre> -\usepackage[dvixxx,...]{geometry} +\usepackage[processor-option,...]{geometry} </pre> </blockquote><p> -(where <code>dvixxx</code> is your current favourite DVI -driver — <i>geometry</i> knows about <code>dvips</code> and -<code>dvipdfm</code>), and the document will run correctly with -LaTeX. If you’re using PDFLaTeX, load with +Where <code>processor-option</code> tells the package what will produce +your (PostScript or PDF driver — <i>geometry</i> knows about +<code>dvips</code> and <code>dvipdfm</code> (<code>dvipdfm</code> also +serves for the extension <i>dvipdfmx</i> and +<i>xdvipdfmx</i>). +<p/>If you’re using PDFLaTeX, XeTeX or VTeX, load with <blockquote> <pre> -\usepackage[pdftex,...]{geometry} +\usepackage[program-option,...]{geometry} </pre> </blockquote><p> +where <code>program-option</code> is <code>pdftex</code>, +<code>xetex</code> or <code>vtex</code>. <p/>Needless to say, both the “big” classes (<i>koma-script</i> and <i>memoir</i>) provide their own ways to get the paper size “right”. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parskip.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parskip.html index 3ddaf3292ee..720812e1a3b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parskip.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-parskip.html @@ -30,7 +30,7 @@ equivalent (<i>rapport3</i>) whose design incorporates zero paragraph indent and non-zero paragraph skip. <dl> <dt><tt><i>NTG classes</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/ntgclass.zip">macros/latex/contrib/ntgclass</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/ntgclass/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/ntgclass.html">catalogue entry</a> -<dt><tt><i>parskip.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/misc/parskip.sty">macros/latex/contrib/misc/parskip.sty</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/parskip.html">catalogue entry</a> +<dt><tt><i>parskip.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/parskip.zip">macros/latex/contrib/parskip</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/parskip/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/parskip.html">catalogue entry</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> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdftexgraphics.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdftexgraphics.html index da3fb286e82..3d819f62a76 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdftexgraphics.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-pdftexgraphics.html @@ -41,7 +41,7 @@ secondary file.) “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 Voß’s <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 diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfchoice.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfchoice.html index ea841a8eb0a..38dff146738 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfchoice.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-psfchoice.html @@ -300,9 +300,9 @@ working on them, and several problems have been identified: <dt>pxfonts set version 1.0<dd>(26 fonts) by Young Ryu<br> The <i>pxfonts</i> set consists of <ul> - <li> virtual text fonts using <i>Adobe</i> <i>Palatino</i> (or the URW - replacement used by <i>ghostscript</i>) with modified plus, - equal and slash symbols; + <li> virtual text fonts using <i>Adobe</i> <i>Palatino</i> + (or the URW replacement used by <i>ghostscript</i>) + with modified plus, equal and slash symbols; <li> maths alphabets using <i>Palatino</i>; <li> maths fonts of all symbols in the computer modern maths fonts (<i>cmsy</i>, <i>cmmi</i>, <i>cmex</i> and the Greek @@ -318,9 +318,10 @@ working on them, and several problems have been identified: <i>txfonts</i> set should be installed whenever <i>pxfonts</i> are. LaTeX, <i>dvips</i> and PDFTeX support files are included. - - <a href="http://mirrors.ctan.org/fonts/pxfonts/doc/pxfontsdocA4.pdf">Documentation</a> - is readily available. +<p/> The fonts are not perfect; the widths assigned to the characters in + the <code>.tfm</code> file are wrong for some glyphs; this can cause + sequences of characters to “look wrong”, or in some cases even to + overlap. <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> @@ -340,9 +341,10 @@ working on them, and several problems have been identified: </ul> The text fonts are available in OT1, T1 and LY1 encodings, and TS encoded symbols are also available. - - <a href="http://mirrors.ctan.org/fonts/txfonts/doc/txfontsdocA4.pdf">Documentation</a> - is readily available. +<p/> The fonts are not perfect; the widths assigned to the characters in + the <code>.tfm</code> file are wrong for some glyphs; this can cause + sequences of characters to “look wrong”, or in some cases even to + overlap. <p/> The fonts are licensed under the GPL; use in published documents is permitted. <dt>txfontsb set version 1.00<dd> by Young Ryu and Antonis Tsolomitis<br> @@ -376,12 +378,14 @@ 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 was for a long time the “native” format for Windows, but +MicroSoft joined the development of the OpenType specification, and +‘modern’ windows will work happily with fonts in either format. 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.) +ATM. (When used on a system running Windows XP or later, +TrueTeX can also use Adobe Type 1 fonts.) <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 diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readML.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readML.html index 2300bf425b0..80a5e5bdec5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readML.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-readML.html @@ -4,12 +4,13 @@ <h3>Using TeX to read SGML or XML directly</h3> <p/>This can nowadays be done, with a certain amount of clever macro programming. David Carlisle’s <i>xmltex</i> is the prime example; -it offers a practical solution to typesetting -XML files. +it offers a solution (of sorts) for typesetting XML files. <p/>One use of a TeX that can typeset XML files is as a backend processor for XSL formatting objects, serialized as XML. Sebastian Rahtz’s PassiveTeX uses <i>xmltex</i> to achieve this end. +<p/>However, modern usage would proceed via XSL or XSLT2 to +produce a formattable version. <dl> <dt><tt><i>xmltex</i></tt><dd><a href="http://mirror.ctan.org/macros/xmltex/base.zip">macros/xmltex/base</a> (or <a href="http://mirror.ctan.org/macros/xmltex/base/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/xmltex.html">catalogue entry</a> <dt><tt><i>passivetex</i></tt><dd><a href="http://mirror.ctan.org/macros/xmltex/contrib/passivetex.zip">macros/xmltex/contrib/passivetex</a> (or <a href="http://mirror.ctan.org/macros/xmltex/contrib/passivetex/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/passivetex.html">catalogue entry</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-recovertex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-recovertex.html index 4b70b3b663a..91d907c44a3 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-recovertex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-recovertex.html @@ -42,10 +42,10 @@ 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="http://mirror.ctan.org/dviware/catdvi.zip">dviware/catdvi</a> (or <a href="http://mirror.ctan.org/dviware/catdvi/">browse the directory</a>) +<dt><tt><i>catdvi</i></tt><dd><a href="http://mirror.ctan.org/dviware/catdvi.zip">dviware/catdvi</a> (or <a href="http://mirror.ctan.org/dviware/catdvi/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/catdvi.html">catalogue entry</a> <dt><tt><i>crudetype</i></tt><dd><a href="http://mirror.ctan.org/dviware/crudetype.zip">dviware/crudetype</a> (or <a href="http://mirror.ctan.org/dviware/crudetype/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/crudetype.html">catalogue entry</a> <dt><tt><i>dvi2tty</i></tt><dd><a href="http://mirror.ctan.org/dviware/dvi2tty.zip">dviware/dvi2tty</a> (or <a href="http://mirror.ctan.org/dviware/dvi2tty/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/dvi2tty.html">catalogue entry</a> -<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/ghostscript">support/ghostscript</a> +<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/ghostscript/GPL">support/ghostscript/GPL</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/ghostscript-GPL.html">catalogue entry</a> <dt><tt><i>xpdf</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/xpdf">support/xpdf</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/xpdf.html">catalogue entry</a> </dl> <p><em>This answer last edited: 2009-05-29</em></p> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ref-doc.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ref-doc.html index 8ec1853d239..bc6180b14c1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ref-doc.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ref-doc.html @@ -17,18 +17,18 @@ it’s a list of (more or less) everything you ‘ought to’ rememb basic LaTeX use. (It’s laid out very compactly for printing on N.\ American ‘letter’; printed on ISO A4, using Adobe Acrobat’s “shrink to fit”, it strains aged eyes…) -<p/>Similarly, there’s no completely reliable command-organised reference -to LaTeX. The page (provided by NASA) -<a href="http://www.giss.nasa.gov/latex/">Hypertext Help with LaTeX</a> is -recently much improved. It still talks in LaTeX 2.09-isms in places, -but it’s been updated for current LaTeX. There are a number of -mirrors of the site, and it may be worth choosing a “local” one if -you’re going to use it a lot. -<p/>Another LaTeX2e reference (provided by the Emerson Center of Emory -University) is: +<p/>For command organised references to LaTeX, Karl Berry (et +al)’s +<a href="http://home.gna.org/latexrefman">LaTeX reference manual</a> is (to +an extent) work in progress, but is generally reliable. +<p/>The reference provided by the Emerson Center of Emory +University), <a href="http://www.emerson.emory.edu/services/latex/latex2e/latex2e_toc.html">LaTeXe help</a> +also looks good. <dl> <dt><tt><i>Cheat sheet</i></tt><dd><a href="http://mirror.ctan.org/info/latexcheat/latexcheat/latexsheet.pdf">info/latexcheat/latexcheat/latexsheet.pdf</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/latexcheat.html">catalogue entry</a> +<dt><tt><i>LaTeX reference manual</i></tt><dd><a href="http://mirror.ctan.org/info/latex2e-help-texinfo.zip">info/latex2e-help-texinfo</a> (or <a href="http://mirror.ctan.org/info/latex2e-help-texinfo/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/latex2e-help-texinfo.html">catalogue entry</a> </dl> +<p><em>This answer last edited: 2010-12-08</em></p> <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-dist/doc/generic/FAQ-en/html/FAQ-scriptfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-scriptfonts.html index 18c47790dcf..a58e850d3ce 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-scriptfonts.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-scriptfonts.html @@ -44,7 +44,7 @@ Examples of the available styles are available on CTAN. <dl> <dt><tt><i>eucal.sty</i></tt><dd>Distributed as part of <a href="http://mirror.ctan.org/fonts/amsfonts.zip">fonts/amsfonts</a> (or <a href="http://mirror.ctan.org/fonts/amsfonts/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/amsfonts.html">catalogue entry</a> <dt><tt><i>euler fonts</i></tt><dd>Distributed as part of <a href="http://mirror.ctan.org/fonts/amsfonts.zip">fonts/amsfonts</a> (or <a href="http://mirror.ctan.org/fonts/amsfonts/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/amsfonts.html">catalogue entry</a> -<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/ghostscript">support/ghostscript</a> +<dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://mirror.ctan.org/support/ghostscript/GPL">support/ghostscript/GPL</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/ghostscript-GPL.html">catalogue entry</a> <dt><tt><i>mathrsfs.sty</i></tt><dd>Distributed as part of <a href="http://mirror.ctan.org/macros/latex/contrib/jknappen.zip">macros/latex/contrib/jknappen</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/jknappen/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/mathrsfs.html">catalogue entry</a> <dt><tt><i>rsfs fonts</i></tt><dd><a href="http://mirror.ctan.org/fonts/rsfs.zip">fonts/rsfs</a> (or <a href="http://mirror.ctan.org/fonts/rsfs/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/rsfs.html">catalogue entry</a> <dt><tt><i>Script font examples</i></tt><dd><a href="http://mirror.ctan.org/info/symbols/math/scriptfonts.pdf">info/symbols/math/scriptfonts.pdf</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-setURL.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-setURL.html index 78c7b048cdd..e7a26b6939a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-setURL.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-setURL.html @@ -72,7 +72,7 @@ is in the package files. <dl> <dt><tt><i>hyperref.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/hyperref/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/hyperref.html">catalogue entry</a> <dt><tt><i>miniltx.tex</i></tt><dd>Distributed as part of <a href="http://mirror.ctan.org/macros/plain/graphics.zip">macros/plain/graphics</a> (or <a href="http://mirror.ctan.org/macros/plain/graphics/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/miniltx.html">catalogue entry</a> -<dt><tt><i>path.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/misc/path.sty">macros/latex/contrib/misc/path.sty</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/path.html">catalogue entry</a> +<dt><tt><i>path.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/generic/path.zip">macros/generic/path</a> (or <a href="http://mirror.ctan.org/macros/generic/path/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/path.html">catalogue entry</a> <dt><tt><i>url.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/url.zip">macros/latex/contrib/url</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/url/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/url.html">catalogue entry</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> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slashbox.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slashbox.html index 1ab953fcf4f..f67b8bc3c20 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slashbox.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-slashbox.html @@ -38,15 +38,17 @@ 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 LaTeX source file of rather startling starkness accompanies the -package file in the distribution. It does, however, process to a -DVI file that gives some idea of how the <code>\</code><code>slashbox</code> may be -expected to look. (The third example in the file shows the effect of +package file in the distribution, and the distribution includes that +file processed to a PDF file for reading over the net, if +necessary. (The third example in the file shows the effect of <code>picture</code> mode’s restrictions: the dividing line doesn’t go from corner to corner in the box: to correct this requires revision of <i>slashbox</i> — <i>pict2e</i> alone doesn’t help in this regard.) <dl> +<dt><tt><i>pict2e.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/pict2e.zip">macros/latex/contrib/pict2e</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/pict2e/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/pict2e.html">catalogue entry</a> <dt><tt><i>slashbox.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/slashbox.zip">macros/latex/contrib/slashbox</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/slashbox/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/slashbox.html">catalogue entry</a> </dl> +<p><em>This answer last edited: 2010-11-02</em></p> <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-dist/doc/generic/FAQ-en/html/FAQ-spawnprog.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spawnprog.html new file mode 100644 index 00000000000..0d0f1e1ae09 --- /dev/null +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-spawnprog.html @@ -0,0 +1,63 @@ +<head> +<title>UK TeX FAQ -- question label spawnprog</title> +</head><body> +<h3>Spawning programs from (La)TeX: <code>\</code><code>write18</code></h3> +<p/>The TeX <a href="FAQ-write.html"><code>\</code><code>write</code> primitive instruction</a> is used +to write to different file ‘streams’; TeX refers to each open file by +a number, not by a file name (although most of the time we hide this). +Originally, TeX would write to a file connected to a stream +numbered 0–15. More recently, a special “stream 18” has been +implemented: it is not writing to a file, but rather tells TeX to ask +the operating system to do something. To run a command, we put it as +the argument to <code>\</code><code>write18</code>. So to run the <i>epstopdf</i> +program on a file with name stored as <code>\</code><code>epsfilename</code>, we would +write: +<blockquote> +<pre> +\write18{epstopf \epsfilename} +</pre> +</blockquote><p> +When using something like the <i>epstopdf</i> package, the ‘stream’ +write operation is hidden away and you don’t need to worry about the +exact way it’s done. +<p/>However, there is a security issue. If you download some (La)TeX code from +the Internet, can you be sure that there is not some command in it +(perhaps in a hidden way) to do stuff that might be harmful to your +PC (let’s say: delete everything on the hard disk!)? In the +face of this problem, both MiKTeX and TeX Live have, for some +time, disabled <code>\</code><code>write18</code> by default. To turn the facility on, +both distributions support an additional argument when starting TeX +from the command shell: +<blockquote> +<pre> +(pdf)(la)tex --shell-escape <file> +</pre> +</blockquote><p> +The problem with this is that many people use (La)TeX via a graphical +editor, so to use <code>\</code><code>write18</code> for a file the editor’s settings must +be changed. Of course, the settings need restoring after the file is +processed: you defeat the point of the original protection, that way. +<p/>The latest MiKTeX (version 2.9), and TeX Live (2010 release) get +around this by having a special “limited” version of <code>\</code><code>write18</code> +enabled ‘out of the box’. The idea is to allow only a pre-set list of +commands (for example, BibTeX, <i>epstopdf</i>, TeX itself, +and so on). Those on the list are regarded as safe enough to allow, +whereas anything else (for example deleting files) still needs to be +authorised by the user. This seems to be a good balance: most people +most of the time will not need to worry about <code>\</code><code>write18</code> at all, +but it will be available for things like <i>epstopdf</i>. +<p/>Note that the TeX system may tell you that the mechanism is in use: +<blockquote> +<pre> +This is pdfTeX, Version 3.1415926-1.40.11 (TeX Live 2010) + restricted \write18 enabled. +</pre> +</blockquote><p> + +when it starts. +<dl> +<dt><tt><i>epstopdf.sty</i></tt><dd>Distributed with Heiko Oberdiek’s packages + <a href="http://mirror.ctan.org/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/oberdiek.html">catalogue entry</a> +</dl> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spawnprog">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=spawnprog</a> +</body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textflow.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textflow.html index 23ba2a7e108..6c750c2c146 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textflow.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-textflow.html @@ -63,7 +63,17 @@ LaTeX document). good), the documentation is in German. Piet van Oostrum has written a summary in English. </dl> -Plain TeX users only have one option: <i>figflow</i> (which +All of the above deal insertions at one or other margin; they are able +to take advantage of the TeX <code>\</code><code>parshape</code> primitive that allows +you to adjust the margins of the text of a paragraph, by line (Knuth +provides an example of such use, with text typeset in a circle, +half-overlapping the margin, in chapter 14 of the TeXbook). To +place insertions in the middle of a paragraph requires effort of an +entirely different sort; the <i>cutwin</i> package does this for +you. It requires a set of “part line widths” (two per line), and +typesets the “cutout” section of the paragraph line by line. The +examples in the package documentation look enticing. +<p/>Plain TeX users only have one option: <i>figflow</i> (which doesn’t work in LaTeX). <i>Figflow</i> only offers flowed figures at the start of the paragraph, but it seems perfectly functional. Syntax is @@ -73,6 +83,7 @@ functional. Syntax is (the user is responsible for having the dimensions correct, and for ensuring the figure fits on the page). <dl> +<dt><tt><i>cutwin.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/cutwin.zip">macros/latex/contrib/cutwin</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/cutwin/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/cutwin.html">catalogue entry</a> <dt><tt><i>figflow.tex</i></tt><dd><a href="http://mirror.ctan.org/macros/plain/contrib/figflow.zip">macros/plain/contrib/figflow</a> (or <a href="http://mirror.ctan.org/macros/plain/contrib/figflow/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/figflow.html">catalogue entry</a> <dt><tt><i>floatflt.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/floatflt.zip">macros/latex/contrib/floatflt</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/floatflt/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/floatflt.html">catalogue entry</a> <dt><tt><i>picins.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex209/contrib/picins.zip">macros/latex209/contrib/picins</a> (or <a href="http://mirror.ctan.org/macros/latex209/contrib/picins/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/picins.html">catalogue entry</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texthings.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texthings.html index b6fa7aa5b66..44a15b6a86b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texthings.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-texthings.html @@ -62,7 +62,7 @@ that you are likely to encounter: refers to the current version of LaTeX while LaTeX 2.09 is the long-since-obsolete (since 1994) version (cf. <a href="FAQ-latex2e.html">What is LaTeX2e?</a> for more information). -<p/> <dt>ConTeXt (executable: <i>texexec</i>)<dd> +<p/> <dt>ConTeXt (executable: <i>texmfstart</i>)<dd> See <a href="FAQ-context.html">What is ConTeXt?</a>. <p/> <dt>Texinfo (executables: <i>tex</i>, <i>makeinfo</i>)<dd> @@ -164,6 +164,8 @@ executable—probably <i>latex</i> or <i>pdflatex</i>—to produce an output file. The executable came bundled as part of a TeX distribution such as MiKTeX, which includes various other TeX-related components. -<p><em>This answer last edited: 2009-06-11</em></p> -<p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texthings">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texthings</a> +<p/>This question is also covered in a page on the TUG site, +“<a href="http://tug.org/levels.html">the Levels of TeX</a>”. +<p><em>This answer last edited: 2010-12-08</em></p> +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texthings">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=texthings</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tmupfl.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tmupfl.html index e989cb242ef..876390deccd 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tmupfl.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tmupfl.html @@ -4,47 +4,56 @@ <h3>“Too many unprocessed floats”</h3> <p/>If LaTeX responds to a <code>\</code><code>begin{figure}</code> or <code>\</code><code>begin{table}</code> command with the error message +<blockquote> <pre> ! LaTeX Error: Too many unprocessed floats. See the LaTeX manual or LaTeX Companion for explanation. </pre> -your figures (or tables) are failing to be placed properly. LaTeX +</blockquote><p> +your figures (or tables) are not being placed properly. LaTeX has a limited amount of storage for ‘floats’ (figures, tables, or floats you’ve defined yourself with the <i>float</i> package); if -you don’t let it ever actually typeset any floats, it will run out of -space. -<p/>This failure usually occurs in extreme cases of - - +something you have done has prevented LaTeX from typesetting +floats, it will run out of storage space. +<p/>This failure usually occurs in extreme cases of <a href="FAQ-floats.html">floats moving “wrongly”</a>; LaTeX has found it can’t place a float, and floats of the same type -have piled up behind it. LaTeX’s idea is to ensure that caption -numbers are sequential in the document: the caption number is -allocated when the figure (or whatever) is created, and can’t be -changed, so that placement out of order would mean figure numbers -appearing out of order in the document (and in the list of figures, or -whatever). So a simple failure to place a figure means that no -subsequent figure can be placed; and hence (eventually) the error. -<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 -long sequence of <code>figure</code> or <code>table</code> -environments, with no intervening -text. Unless the environments will fit “here” (and you’ve allowed -them to go “here”), there will never be a page break, and so there -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. +have piled up behind it. +<p/>How does this happen? — LaTeX guarantees that caption numbers are +sequential in the document, but the caption number is allocated when +the figure (or whatever) is created, and can’t be changed. Thus, if +floats are placed out of order, their caption numbers would also +appear out of order in the body of the document (and in the list of +figures, or whatever). As a result, enforcement of the guarantee +means that simple failure to place a float means that no subsequent +float can be placed; and hence (eventually) the error. +<p/>Techniques for solving the problem are discussed in the +<a href="FAQ-floats.html">floats question</a> already referenced. +<p/>An alternative <em>may</em> be to use the <i>morefloats</i> package. +The package will allocate more “float skeletons” than LaTeX +does by default; each such skeleton may then be used to store a +float. Beware that even with <i>morefloats</i>, the number you can +allocate is limited; even with the <i>etex</i> package (which makes +available many more registers, etc., than LaTeX does by default; +e-TeX can create lots more registers, but none of those “beyond +the original TeX default” may be used in float skeletons). Thus, +<i>etex</i> may offer some relief, but it can <em>not</em> be +regarded as a panacea +<p/>The error also occurs in a long sequence of float environments, with +no intervening text. Unless the environments will fit “here” (and +you’ve allowed them to go “here”), there will never be a page break, +and so there 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 <i>float</i> package’s <code>[H]</code> float qualifier, but you are unlikely to get away without using <code>\</code><code>clearpage</code> from time to time. <dl> <dt><tt><i>float.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/float.zip">macros/latex/contrib/float</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/float/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/float.html">catalogue entry</a> +<dt><tt><i>morefloats.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/morefloats.zip">macros/latex/contrib/morefloats</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/morefloats/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/morefloats.html">catalogue entry</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> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toascii.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toascii.html index 76d49847ef2..427f4297534 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toascii.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-toascii.html @@ -45,7 +45,7 @@ beings than the flat-style TeX code. and then to use a browser such as <i>lynx</i> to dump the resulting HTML as plain text. <dl> -<dt><tt><i>catdvi</i></tt><dd><a href="http://mirror.ctan.org/dviware/catdvi.zip">dviware/catdvi</a> (or <a href="http://mirror.ctan.org/dviware/catdvi/">browse the directory</a>) +<dt><tt><i>catdvi</i></tt><dd><a href="http://mirror.ctan.org/dviware/catdvi.zip">dviware/catdvi</a> (or <a href="http://mirror.ctan.org/dviware/catdvi/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/catdvi.html">catalogue entry</a> <dt><tt><i>crudetype</i></tt><dd><a href="http://mirror.ctan.org/dviware/crudetype.zip">dviware/crudetype</a> (or <a href="http://mirror.ctan.org/dviware/crudetype/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/crudetype.html">catalogue entry</a> <dt><tt><i>detex</i></tt><dd><a href="http://mirror.ctan.org/support/detex.zip">support/detex</a> (or <a href="http://mirror.ctan.org/support/detex/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/detex.html">catalogue entry</a> <dt><tt><i>dvi2tty</i></tt><dd><a href="http://mirror.ctan.org/dviware/dvi2tty.zip">dviware/dvi2tty</a> (or <a href="http://mirror.ctan.org/dviware/dvi2tty/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/dvi2tty.html">catalogue entry</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html index c57bf09c5cc..0c44154df64 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-triptrap.html @@ -11,18 +11,19 @@ systems. How, then, is a new version of TeX checked? 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 -(<code>trip</code>) and Metafont (<code>trap</code>). +(<i>trip</i>) and Metafont (<i>trap</i>). He characterises these as ‘torture tests’: they are designed not to check the obvious things that ordinary typeset documents, or font designs, will exercise, but rather to explore small alleyways off the main path through the code of TeX. They are, to the casual reader, pretty incomprehensible! -<p/>Once an implementation of TeX has passed its <code>trip</code> test, or an -implementation of Metafont has passed its <code>trap</code> test, then it may -in principle be distributed as a working version. (In practice, any -distributor would test new versions against “real” documents or -fonts, too; <code>trip</code> and <code>trap</code> don’t actually test any -for real world problems. +<p/>Once an implementation of TeX has passed its <i>trip</i> test, or +an implementation of Metafont has passed its <i>trap</i> test, then it +may in principle be distributed as a working version. (In practice, +any distributor would test new versions against “real” documents or +fonts, too; while <i>trip</i> and <i>trap</i> test bits of +pathways within the program, they don’t actually test for any real +world problem.) <p/><p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=triptrap">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=triptrap</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutbitslatex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutbitslatex.html index b0a53016999..2f4a9c1b80c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutbitslatex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-tutbitslatex.html @@ -6,7 +6,7 @@ available (in several formats) via <a href="http://www.ams.org/tex/amslatex.html">http://www.ams.org/tex/amslatex.html</a> (the “Additional Documentation” about half-way down the page. -<p/>Herbert Voss has written an extensive guide to mathematics in +<p/>Herbert Voß has written an extensive guide to mathematics in LaTeX (a German version of which is published as a book). The guide is part of his “<a href="FAQ-doc-dirs.html">tips and tricks</a>” and a copy is maintained on CTAN. @@ -86,7 +86,7 @@ deparment’s pages at <dl> <dt><tt><i>Graphics in LaTeX2e</i></tt><dd><a href="http://mirror.ctan.org/info/epslatex.zip">info/epslatex</a> (or <a href="http://mirror.ctan.org/info/epslatex/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/epslatex.html">catalogue entry</a> <dt><tt><i>testflow</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/IEEEtran/testflow">macros/latex/contrib/IEEEtran/testflow</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/testflow.html">catalogue entry</a> -<dt><tt><i>Herbert Voss’s Maths tutorial</i></tt><dd><a href="http://mirror.ctan.org/info/math/voss/mathmode/Mathmode.pdf">info/math/voss/mathmode/Mathmode.pdf</a> +<dt><tt><i>Herbert Voß’s Maths tutorial</i></tt><dd><a href="http://mirror.ctan.org/info/math/voss/mathmode/Mathmode.pdf">info/math/voss/mathmode/Mathmode.pdf</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutbitslatex">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=tutbitslatex</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typo-style.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typo-style.html index 7b28361379f..5f599e21997 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typo-style.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-typo-style.html @@ -2,10 +2,12 @@ <title>UK TeX FAQ -- question label typo-style</title> </head><body> <h3>Typography tutorials</h3> -<p/>Peter Wilson’s manual for his <i>memoir</i> class has a lengthy -introductory section on typographic considerations, which is a fine -tutorial, written by someone who is aware of the issues as they apply -to (La)TeX users. +<p/>Peter Wilson’s article <i>memdesign</i> 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. (<i>Memdesign</i> now distributed separately from +the manual for his <i>memoir</i> class, but was originally part of +that manual) <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>”. @@ -19,7 +21,7 @@ ambition to supplant such excellent books as contain its Rutgers-local matter) is a fine introduction to the issues of producing readable documents. <dl> -<dt><tt><i>memoir distribution</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/memoir/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/memoir.html">catalogue entry</a> +<dt><tt><i>memdesign</i></tt><dd><a href="http://mirror.ctan.org/info/memdesign.zip">info/memdesign</a> (or <a href="http://mirror.ctan.org/info/memdesign/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/memdesign.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typo-style">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=typo-style</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uselmfonts.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uselmfonts.html index df08e46d798..574b26563c5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uselmfonts.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-uselmfonts.html @@ -62,6 +62,5 @@ no support for using fonts according to the OT1 encoding. <dl> <dt><tt><i>Latin Modern fonts</i></tt><dd><a href="http://mirror.ctan.org/fonts/lm.zip">fonts/lm</a> (or <a href="http://mirror.ctan.org/fonts/lm/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/lm.html">catalogue entry</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> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepictex.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepictex.html index 007792e35c0..8995939275b 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepictex.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepictex.html @@ -49,6 +49,7 @@ part of the distribution). <i>MathsPic</i> is available either as a <i>Basic</i> program for DOS, or as a <i>Perl</i> program for other systems (including Windows, nowadays). <dl> +<dt><tt><i>etex.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/etex-pkg.zip">macros/latex/contrib/etex-pkg</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/etex-pkg/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/etex-pkg.html">catalogue entry</a> <dt><tt><i>m-pictex.sty</i></tt><dd>Distributed as part of <a href="http://mirror.ctan.org/macros/context/current/cont-tmf.zip">macros/context/current/cont-tmf.zip</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/context.html">catalogue entry</a> <dt><tt><i>m-pictex.tex</i></tt><dd>Distributed as part of <a href="http://mirror.ctan.org/macros/context/current/cont-tmf.zip">macros/context/current/cont-tmf.zip</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/context.html">catalogue entry</a> <dt><tt><i>MathsPic</i></tt><dd><a href="http://mirror.ctan.org/graphics/mathspic.zip">graphics/mathspic</a> (or <a href="http://mirror.ctan.org/graphics/mathspic/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/mathspic.html">catalogue entry</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepsfont.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepsfont.html index 804cc256cdc..91d16d74d68 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepsfont.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-usepsfont.html @@ -1,19 +1,20 @@ <head> <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 -<em>metric</em> (called TFM) files. Several sets of metrics are +<h3>Using Adobe Type 1 fonts with TeX</h3> +<p/>In order to use any font, TeX needs a +<em>metric</em> file (TFM file). Several sets of metrics for +common Adobe Type 1 fonts are available from the archives; for mechanisms for generating new ones, see <a href="FAQ-metrics.html">metrics for PostScript fonts</a>. You also need the fonts themselves; PostScript printers come with a set of -fonts built in, but to extend your repertoire you almost invariably +fonts built in, but to extend your repertoire you usually 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 -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 +<p/>If you use LaTeX2e, access to your printer’s fonts is offered by the +PSNFSS package; the LaTeX3 project team declare that +PSNFSS is a “required” part of a LaTeX distribution, and +bug reports may be submitted via the <a href="FAQ-latexbug.html">LaTeX bugs system</a>. PSNFSS gives you a set of packages for changing the default roman, sans-serif and typewriter fonts; <em>e.g</em>., the @@ -36,14 +37,10 @@ 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> -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 (see <a href="FAQ-psfontprob.html">problems with PS fonts</a>). <dl> <dt><tt><i>Metrics for the ‘Laserwriter’ set of 35 fonts</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/required/psnfss/lw35nfss.zip">macros/latex/required/psnfss/lw35nfss.zip</a>; <a href="http://mirror.ctan.org//help/Catalogue/entries/lw35nfss.html">catalogue entry</a> -<dt><tt><i>lollipop</i></tt><dd><a href="http://mirror.ctan.org/macros/lollipop.zip">macros/lollipop</a> (or <a href="http://mirror.ctan.org/macros/lollipop/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/lollipop.html">catalogue entry</a> <dt><tt><i>psnfss</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/required/psnfss.zip">macros/latex/required/psnfss</a> (or <a href="http://mirror.ctan.org/macros/latex/required/psnfss/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/psnfss.html">catalogue entry</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> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbwithin.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbwithin.html index 94731459f7a..e53d6391b0f 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbwithin.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-verbwithin.html @@ -45,7 +45,8 @@ provokes errors like ‘File ended while scanning use of matching <code>\</code><code>end{verbatim}</code>. <p/>This is why the LaTeX book insists that verbatim commands must not appear in the argument of any other command; they -aren’t just fragile, they’re quite unusable in any command parameter, +aren’t just fragile, they’re quite unusable in any “normal” 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 @@ -63,7 +64,7 @@ necessary?”. “<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: + environmen)t: <blockquote> <pre> \newsavebox{\mybox} @@ -75,7 +76,21 @@ necessary?”. </pre> </blockquote><p> </ul> -<p/>Otherwise, there are three partial solutions to the problem. +<p/>If you can’t avoid verbatim, the <code>\</code><code>cprotect</code> command (from the +package <i>cprotect</i>) might help. The package manages to make a +macro read a verbatim argument in a “sanitised” way by the simple +medium of prefixing the macro with <code>\</code><code>cprotect</code>: +<blockquote> +<pre> +\cprotect\section{Using \verb|verbatim|} +</pre> +</blockquote><p> +The package (at the time this author tested it) was still under +development (though it <em>does</em> work in this simple case) and +deserves consideration in most cases; the package documentation gives +more details. +<p/>Other than the <i>cprotect</i> package, 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, @@ -118,13 +133,12 @@ necessary?”. like percent signs for which (La)TeX already provides robust macros). </ul> -Documentation of both <i>url</i> and <i>verbdef</i> is in the -package files. <dl> +<dt><tt><i>cprotect.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/cprotect.zip">macros/latex/contrib/cprotect</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/cprotect/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/cprotect.html">catalogue entry</a> <dt><tt><i>fancyvrb.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/fancyvrb.zip">macros/latex/contrib/fancyvrb</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/fancyvrb/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/fancyvrb.html">catalogue entry</a> <dt><tt><i>memoir.cls</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/memoir.zip">macros/latex/contrib/memoir</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/memoir/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/memoir.html">catalogue entry</a> <dt><tt><i>url.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/url.zip">macros/latex/contrib/url</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/url/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/url.html">catalogue entry</a> -<dt><tt><i>verbdef.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/verbdef.zip">macros/latex/contrib/verbdef</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/verbdef/">browse the directory</a>) +<dt><tt><i>verbdef.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/latex/contrib/verbdef.zip">macros/latex/contrib/verbdef</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/verbdef/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/verbdef.html">catalogue entry</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbwithin">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=verbwithin</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-webpkgs.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-webpkgs.html index 7347e59f356..86fdd587dc5 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-webpkgs.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-webpkgs.html @@ -9,14 +9,15 @@ 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/><i>FWEB</i>, by John Krommes, is a version for Fortran, +Ratfor,C, C++, working with LaTeX; it was derived +from <i>CWEB</i>. <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, -Ratfor, and C. <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. @@ -29,8 +30,8 @@ is written in ANSI C). <dt><tt><i>aplweb</i></tt><dd><a href="http://mirror.ctan.org/web/apl/aplweb.zip">web/apl/aplweb</a> (or <a href="http://mirror.ctan.org/web/apl/aplweb/">browse the directory</a>) <dt><tt><i>cweb</i></tt><dd><a href="http://mirror.ctan.org/web/c_cpp/cweb.zip">web/c_cpp/cweb</a> (or <a href="http://mirror.ctan.org/web/c_cpp/cweb/">browse the directory</a>) <dt><tt><i>funnelweb</i></tt><dd><a href="http://mirror.ctan.org/web/funnelweb.zip">web/funnelweb</a> (or <a href="http://mirror.ctan.org/web/funnelweb/">browse the directory</a>) -<dt><tt><i>fweb</i></tt><dd><a href="http://mirror.ctan.org/web/fweb.zip">web/fweb</a> (or <a href="http://mirror.ctan.org/web/fweb/">browse the directory</a>) -<dt><tt><i>noweb</i></tt><dd><a href="http://mirror.ctan.org/web/noweb.zip">web/noweb</a> (or <a href="http://mirror.ctan.org/web/noweb/">browse the directory</a>) +<dt><tt><i>fweb</i></tt><dd><a href="http://mirror.ctan.org/web/fweb.zip">web/fweb</a> (or <a href="http://mirror.ctan.org/web/fweb/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/fweb.html">catalogue entry</a> +<dt><tt><i>noweb</i></tt><dd><a href="http://mirror.ctan.org/web/noweb.zip">web/noweb</a> (or <a href="http://mirror.ctan.org/web/noweb/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/noweb.html">catalogue entry</a> <dt><tt><i>nuweb</i></tt><dd><a href="http://mirror.ctan.org/web/nuweb.zip">web/nuweb</a> (or <a href="http://mirror.ctan.org/web/nuweb/">browse the directory</a>) <dt><tt><i>schemeweb</i></tt><dd><a href="http://mirror.ctan.org/web/schemeweb.zip">web/schemeweb</a> (or <a href="http://mirror.ctan.org/web/schemeweb/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/schemeweb.html">catalogue entry</a> <dt><tt><i>spiderweb</i></tt><dd><a href="http://mirror.ctan.org/web/spiderweb.zip">web/spiderweb</a> (or <a href="http://mirror.ctan.org/web/spiderweb/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/spiderweb.html">catalogue entry</a> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatbst.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatbst.html index 30987b96773..05d7c017b34 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatbst.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatbst.html @@ -49,7 +49,7 @@ 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…) <dl> -<dt><tt><i>xampl.bib</i></tt><dd><a href="http://mirror.ctan.org/biblio/bibtex/distribs/doc/xampl.bib">biblio/bibtex/distribs/doc/xampl.bib</a> +<dt><tt><i>xampl.bib</i></tt><dd><a href="http://mirror.ctan.org/biblio/bibtex/base/xampl.bib">biblio/bibtex/base/xampl.bib</a> </dl> <p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatbst">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatbst</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ifpdf.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatengine.html index b0a0121a1cc..47d47effccd 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-ifpdf.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whatengine.html @@ -1,10 +1,37 @@ <head> -<title>UK TeX FAQ -- question label ifpdf</title> +<title>UK TeX FAQ -- question label whatengine</title> </head><body> -<h3>Am I using PDFTeX?</h3> -<p/>It’s often useful to know whether your macros are operating within -PDFTeX or within (“normal”) TeX; getting the right answer is -surprisingly tricky. +<h3>Am I using PDFTeX, XeTeX or LuaTeX?</h3> +<p/><p/>You often need to know what “engine” your macros are running on (the +engine is the TeX-derivative or TeX-alike processor that +typesets your document). The reason that you need to know is that the +set of functions available in each engine is different. Thus, for +TeX macros to run on any engine, they need to “know” what they +can and cannot do, which depends on the engine in use. Getting the +right answer is surprisingly tricky (see below for an elaboration of +one apparently simple test). +<p/>There is now a comprehensive set of packages that answer the question +for you. They all create a TeX conditional command: +<ul> +<li> <i>ifpdf</i> creates a command <code>\</code><code>ifpdf</code>, +<li> <i>ifxetex</i> creates a command <code>\</code><code>ifxetex</code> and +<li> <i>ifluatex</i> creates a command <code>\</code><code>ifluatex</code>. +</ul> +These TeX commands may be used within the LaTeX conditional +framework, as (for example): +<blockquote> + <code>\</code><code>ifthenelse</code><code>\char‘{</code><code>\</code><code>boolean{pdf}</code><code>\char‘}\char‘{<<i>if pdf</i>>\char‘}\char‘{<<i>not pdf</i>>\char‘}</code> +</blockquote><p> +<p/>The <i>ifxetex</i> package also provides a command +<code>\</code><code>RequireXeTeX</code> which creates an error if the code is not running +under XeTeX; while the other packages don’t provide such a command, +it’s not really difficult to write one for yourself. +<p/> + +<p/>Now for those who want to do the job for themselves: here’s a +discussion of doing the job for PDFTeX and <code>\</code><code>ifpdf</code> — the +eager programmer can regenerate <code>\</code><code>ifxetex</code> or <code>\</code><code>ifluatex</code> in the +same fashion. It’s not recommended\dots <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 @@ -70,14 +97,6 @@ output, you also need to know about the value of <code>\</code><code>pdfoutput</ \fi </pre> </blockquote><p> -The above is, in essence, what Heiko Oberdiek’s <i>ifpdf</i> -package does; the reasoning is the FAQ’s interpretation of -Heiko’s explanation. -<p/>As an aside: there are now analogous packages <i>ifxetex</i> and -<i>ifluatex</i>, for the two up-and-coming TeX-like engines (see -the “TeX project” answers covering -<a href="FAQ-xetex.html">XeTeX</a>, and -<a href="FAQ-luatex.html">LuaTeX</a>). <dl> <dt><tt><i>ifpdf.sty</i></tt><dd>Distributed as part Heiko Oberdiek’s bundle <a href="http://mirror.ctan.org/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/ifpdf.html">catalogue entry</a> @@ -85,5 +104,5 @@ the “TeX project” answers covering <a href="http://mirror.ctan.org/macros/latex/contrib/oberdiek.zip">macros/latex/contrib/oberdiek</a> (or <a href="http://mirror.ctan.org/macros/latex/contrib/oberdiek/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/ifluatex.html">catalogue entry</a> <dt><tt><i>ifxetex.sty</i></tt><dd><a href="http://mirror.ctan.org/macros/generic/ifxetex.zip">macros/generic/ifxetex</a> (or <a href="http://mirror.ctan.org/macros/generic/ifxetex/">browse the directory</a>); <a href="http://mirror.ctan.org/help/Catalogue/entries/ifxetex.html">catalogue entry</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=whatengine">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=whatengine</a> </body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whereFAQ.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whereFAQ.html index 1ce359a0e30..1730f0d8afa 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whereFAQ.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-whereFAQ.html @@ -26,7 +26,7 @@ missing with other readers, or with earlier versions of Acrobat Reader <p/>Both the Francophone TeX user group Gutenberg and the Czech/Slovak user group CS-TUG have published translations of this FAQ, with extensions appropriate to their languages. -<p/>Herbert Voss’s excellent +<p/>Herbert Voß’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 diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wholerow.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wholerow.html index a318deb0419..9589906036a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wholerow.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-wholerow.html @@ -23,7 +23,7 @@ than columns. So, we set things up by: </pre> </blockquote><p> Now, we put ‘<code>$</code>’ before the first column specifier; and we -put ‘<code>textasciicircum</code>’ +put ‘<code>^</code>’ before the modifiers of subsequent ones. We then use <code>\</code><code>rowstyle</code> at the start of each row we want to modify: <blockquote> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-why-inp-font.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-why-inp-font.html index d52ec418c6a..1709822ef66 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-why-inp-font.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-why-inp-font.html @@ -14,7 +14,7 @@ despite its <a href="FAQ-t1enc.html">shortcomings</a>. <dl> <dt>Confusion<dd> You’ve been happily working in this mode, and for some reason find you’re to switch to writing in German: the effect - of using “<code>ß</code>” is somewhat startling, since T1 + of using “<code>ß{</code>}” is somewhat startling, since T1 and Latin-1 treat the codepoint differently. <dt>Compatibility<dd> You find yourself needing to work with a colleague in Eastern Europe: their keyboard is likely to be set to diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-write.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-write.html new file mode 100644 index 00000000000..68fc5cc9dd7 --- /dev/null +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-write.html @@ -0,0 +1,41 @@ +<head> +<title>UK TeX FAQ -- question label write</title> +</head><body> +<h3>Writing (text) files from TeX</h3> +<p/>TeX allows you to write to output files from within your document. +The facility is handy in many circumstances, but it is vital for +several of the things LaTeX (and indeed almost any higher-level +TeX-based macro package) does for you. +<p/>The basic uses of writing to an external file are “obvious” — +remembering titles of sections for a table of contents, remembering +label names and corresponding section or figure numbers, all for a +later run of your document. However, the “non-obvious” thing is +easy to forget: that page numbers, in TeX, are slippery beasts, and +have to be captured with some care. The trick is that <code>\</code><code>write</code> +operations are only executed as the page is sent to the DVI +or PDF file. Thus, if you arrange that your page-number macro +(<code>\</code><code>thepage</code>, in LaTeX) is not expanded until the page is +written, then the number written is correct, since that time is where +TeX guarantees the page number tallies with the page being sent +out. +<p/>Now, there are times when you want to write something straight away: +for example, to interact with the user. TeX captures that +requirement, too, with the primitive <code>\</code><code>immediate</code>: +<blockquote> +<pre> +\immediate\write\terminal{I'm waiting...} +</pre> +</blockquote><p> +writes a “computer-irritates-user” message, to the terminal. +<p/>Which brings us to the reason for that <code>\</code><code>terminal</code>. TeX can +“<code>\</code><code>write</code>” up to 16 streams simultaneously, and that argument to +<code>\</code><code>write</code> says which is to be used. Macro packages provide the +means of allocating streams for your use: Plain TeX provides a macro +<code>\</code><code>newwrite</code><code>\</code><code>streamname</code>, which sets <code>\</code><code>streamname</code> as +the stream number. In fact, <code>\</code><code>terminal</code> (or its equivalent) is the +first output stream ever set up (in most macro packages): it is never +attached to a file, and if TeX is asked to write to <em>any</em> +stream that isn’t attached to a file it will send the output to the +terminal (and the log). +<p/><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=write">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=write</a> +</body> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-zerochap.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-zerochap.html index e8516ea083f..5a0d3440ac4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-zerochap.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-zerochap.html @@ -7,10 +7,12 @@ before your first <code>\</code><code>chapter</code>. <p/>What happens is, that the class numbers sections as “<<i>chapter no</i>>.<<i>section no</i>>”, and until the first -chapter has appeared, the chapter number is 0. -<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>chapter</code> has appeared, the chapter number is 0. (If you +use<code>\</code><code>chapter*</code>, which doesn’t number the chapter it produces, the +problem still arises.) +<p/>If you’re doing this, it’s possible that the <i>article</i> class +is for you; try it and see. Otherwise, put a <code>\</code><code>chapter</code> before +your sections, 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>”. diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/index.html b/Master/texmf-dist/doc/generic/FAQ-en/html/index.html index 63dabf0e897..4998168d122 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/html/index.html +++ b/Master/texmf-dist/doc/generic/FAQ-en/html/index.html @@ -61,7 +61,6 @@ remains. <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> @@ -99,6 +98,8 @@ remains. <li><a href="FAQ-virtualfonts.html">Virtual fonts</a> <li><a href="FAQ-whatmacros.html">What are (TeX) macros</a> <li><a href="FAQ-specials.html"><code>\</code><code>special</code> commands</a> +<li><a href="FAQ-write.html">Writing (text) files from TeX</a> +<li><a href="FAQ-spawnprog.html">Spawning programs from (La)TeX: <code>\</code><code>write18</code></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> @@ -168,14 +169,10 @@ remains. <li><a href="FAQ-instt1font.html">Installing a Type 1 font</a> <li><a href="FAQ-inst1cm.html">Installing the Type 1 versions of the CM fonts</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> </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-usepsfont.html">Using Adobe Type 1 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-metrics.html">TeX font metric files for Type 1 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> @@ -184,6 +181,10 @@ remains. </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> +</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> </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> @@ -410,7 +411,7 @@ remains. <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-whatengine.html">Am I using PDFTeX, XeTeX or LuaTeX?</a> <li><a href="FAQ-subverttoks.html">Subverting a token register</a> <li><a href="FAQ-isdef.html">Is this command defined?</a> </ul><h4>LaTeX macro tools and techniques</h4><ul> @@ -548,6 +549,6 @@ remains. "<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.20, last modified on 2010-08-17. + This is FAQ version 3.21, last modified on 2011-02-18. </address> </body></html> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf b/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf Binary files differindex 8f891b0af2f..e0fe9e96da0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf +++ b/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf diff --git a/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf Binary files differindex 0b25684c830..6ceacf01a38 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf +++ b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf |