diff options
27 files changed, 1267 insertions, 500 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.25 b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.25 new file mode 100644 index 00000000000..766f3062f34 --- /dev/null +++ b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.25 @@ -0,0 +1,47 @@ +Changes since version 3.24 + +New answers: + +Label includeother:LaTeX refuses to \include from (some) other directories + +Relabelled answers: + <none> + +Revised answers: + +Label acrobat: Rearranged and extended somewhat (dropped V-TeX details) + +Label bibinline: Outline use of the new usebib package + +Label citesort: Show how to do the job with biblatex + +Label cmdstar: Suggest use of xparse for *-commands + +Label crossref: Clarified wording, and removed incorrect "effect" of error + +Label eqnarray: Added link to Stefan Kottwitz blog entry on the problem + +Label euro: Updated note about using marvosym font + +Label extrabrace: Some clarification (and a new solution) + +Label filesused: Discuss mkjobtexmf + +Label findfont: Rewritten, downplaying Metafont and covering TTF and OTF + +Label footintab: Discuss tablefootnote package + +Label i18nbib: BibLaTeX is another candidate + +Label inlgrphapp: Add picture environment to list, mention picture package + +Label isitanum: Improve \testnum definition + +Label labelfig: Describe pinlabel package + +Label man-latex: Correct link to Chris Harrison's (now) tutorial; + Mention van Dongen's, Wilkins' and Buxbaum's offerings + +Label marginpkgs: Discuss zwpagelayout + +Label mfptutorials:Restore (lost) link to MetaFun manual + +Label noroom: Mention morewrites for lots of (pretend) output streams + +Label papergeom: Outline use of zwpagelayout package + +Label ref-doc: Added reference to macros2e document + +Label slashbox: Recommend diagbox package in preference to slashbox + +Label syswin32: Miktex 2.9 no longer beta ... so catch up! + +Label tutbitslatex:Rearrange stuff on pgf/tikz, after new management of site + +Label tutorials*: Changed question title to "... TeX-based systems" + +Label usesymb: Add fdsymbol, mdsymbol + +Label verbwithin: Suggest "v" argument type of xparse + +Label watermark: Discuss xwatermark and use of pdftk + +Label whatengine: Sort out erroneous wording, correct HTML of example code + +Deleted answers: + <none removed> + +Web interface, etc.: + <no changes> + +Robin Fairbairns diff --git a/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog b/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog index c3dd610d1b6..8817b98318a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog +++ b/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog @@ -1,3 +1,299 @@ +2012-03-29 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * gather-faqbody.tex: v 3.25, today + + * faq-wdidt.tex (q-eqnarray): link to kottwitz's tex blog entry + +2012-03-28 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-hyp+pdf.tex (q-acrobat): tidying, dragging into 21st century... + + * faq-texsys.tex (q-syswin32): miktex 2.9 no longer beta, and so luatex + available on miktex too + +2012-03-27 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * sanitize-beta.pl (sanitize_line): accept \mf, \mp as well as uc vrsn + + * faq.sty: new \mf, \mp, existing uc vrsn each only use initial capital + + * faq-getit.tex (q-findfont): rewritten in rather different style, + noting the decline of mf and the appearance of alternate engines + +2012-03-26 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-texsys.tex (q-sysunix): editorial -- clarify that tlmgr works + however you install tl + +2012-03-23 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: add usebib + + * faq-biblio.tex (q-i18nbib): biblatex does this too + (q-bibinline): suggest usebib + +2012-03-16 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-graphics.tex (q-inlgrphapp): add picture environment to list, and + mention picture package with it + + * faq-mac-prog.tex (q-printvar): \verb in verbatim sections is silly, + and in typeset sections doesn't get translated by process.pl ... + +2012-03-14 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-parmoderr): not in outer par mode + +2012-03-09 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-t-g-wr.tex (q-msxy): mention berthold horn's partial msym + +2012-03-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-inputenc,q-fontenc): proof-reading corrections + (probably meaning that other questions aren't any longer useful; these + questions marked...) + +2012-03-07 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-ltx-csv): \LastEdit tag + (q-archives-rev): editorial + + * faq-bits+pieces.tex (q-unicode): editorial clarification + +2012-02-20 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: add datatool + + * add-general.tex (q-ltx-csv): new answer on csv lists + +2012-02-17 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-graphics.tex (q-labelfig): editorial work + +2012-02-16 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: add macros2e + + * faq-docs.tex (q-ref-doc): add macros2e + +2012-02-14 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: add mdframed + remove metafont(actually mac-),mctex,mewltx + + * faq-adj-types.tex (q-subsubsub): editorial + (q-breakbox): add mdframed as another solution + +2012-02-13 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-wdidt.tex (q-verbwithin): xparse arguments for verbatim use + + * sanitize-beta.pl (sanitize_line): get \{, \}, and \[oc]bracesymbol + working with numeric entities + + * faq-jot-err.tex (q-includeother): it's \File not \FileName!!! + + * faq-mac-prog.tex (q-whatengine): correct wording, and coding of + \ifthenelse example to make it do correct html + +2012-02-11 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-wdidt.tex (q-verbwithin): verbatim arg in \NewDocumentCommand etc + +2012-02-10 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-jot-err.tex (q-includeother): more editorial expansion + + * faq-biblio.tex (q-citesort): mention biblatex number-comp style + +2012-02-09 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-jot-err.tex (q-extrabrace): more rationalisation + +2012-02-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-jot-err.tex (q-extrabrace): slip in a \Qref + +2012-02-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-install.tex (q-inst-tds-zip): in "that are that's" remove "that's" + +2012-02-07 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-jot-err.tex (q-includeother): came from add-general + + * CHANGES-3.25: tags for cmdstar and crossref + + * faq-projects.tex (q-latex3): explain the concept of "harness", tidy + + * faq-mac-prog.tex (q-cmdstar): outline use of xparse to define *-macros + + * faq-wdidt.tex (q-crossref): dang! -- it could never have had a + "previous figure number" + other editing + + * faq-how-do-i.tex (q-footintab): move tablefootnotes "further up" + +2012-02-06 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-install.tex (q-install-find): tidying and clarification + (q-instmffont): more clarification + +2012-02-01 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq.sty, sanitize-beta.pl: add \LeadFrom + + * faq-adj-types.tex (q-runheadtoobig): include an actual example of + using titlesec pkg + +2012-01-27 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: add morewrites + + * faq-jot-err.tex: move q-optionclash and q-optclash together, for + easier editing + (q-noroom): tidies, mention morewrites package + +2012-01-19 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-docs.tex (q-tutbitslatex): stefan kottwitz runs texample.net, + editorial + + * faq-wdidt.tex: odd bits of editorial + +2012-01-16 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-docs.tex (q-bibtexing): correct parentheses + + * dirctan.tex: add fdsymbol, mdsymbol + + * faq-symbols.tex (q-usesymb): add fdsymbol and mdsymbol with mnsymbol + +2012-01-10 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-intro.tex: comment on matthias' latest contribution + + * faq-mac-prog.tex (q-isitanum): correct def of \testnum, per matthias + +2012-01-08 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-jot-err.tex (q-noroom): circumspection around the numbers of + floats that may be reserved + +2012-01-04 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-adj-types.tex (q-poster): correct (old) typo + +2012-01-03 Robin Fairbairns + + * faq-docs.tex (q-man-latex): add van dongen's, wilkins' and buxbaum's + oeuvres + + * dirctan.tex: add latex-course + +2011-12-29 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-docs.tex (q-pkgdoc): editorial (awful english) + +2011-12-21 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-fontenc): editorial + +2011-12-19 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-symbols.tex (q-numbersets): editorial reducing verbosity + +2011-12-15 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-intro.tex: credit william adams + + * faq-docs.tex (q-man-latex): new link for chris harrison's tutorial + +2011-12-12 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: add pinlabel + + * faq-graphics.tex (q-labelfig): mention pinlabel + + * dirctan.tex: add zwpagelayout + + * faq-adj-types.tex (q-papergeom): zwpagelayout usage outline + (q-marginpkgs): mention that zwpagelayout is also available + +2011-12-01 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-hyp+pdf.tex (q-acrobat): trying to drag into c.21 + + * add-general.tex (q-pdf-encr): re-arrange to make clear that pdftk is + worth considering + +2011-11-30 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: add xwatermark + + * faq-adj-types.tex (q-watermark): add xwatermark, discuss pdftk + +2011-11-29 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: add mkjobtexmf + + * faq-how-do-i.tex (q-filesused): discuss mkjobtexmf + +2011-11-28 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: add tablefootnote + + * faq-how-do-i.tex (q-footintab): mention tablefootnote + +2011-11-22 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * add-general.tex (q-position): editorial stuff (seems ok, so far) + +2011-11-22 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * dirctan.tex: add diagbox + + * faq-how-do-i.tex (q-slashbox): convert to use diagbox, with slashbox + as an also-ran + +2011-11-21 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-position): first more or less complete version + + * faq-docs.tex (q-mfptutorials): restore link to metafun manual + + * faq-symbols.tex (q-euro): update (incl. usage of marvosym) + +2011-11-16 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-repetition): memo about csv commands + +2011-11-08 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-docs.tex (q-tutorials*): change question title to avoid clash + with q-tutbitslatex + (q-tutbitslatex): remove pTeX tutorial link (seems to have gone) + + * faq-adj-types.tex (q-slidecls): add ctanref for pdfscreen + + * dirctan.tex: add pdfscreen + +2011-11-07 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * add-general.tex (q-detknize): correct link for q-filename + +2011-11-04 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-wdidt.tex (q-t1enc): tidy-up: \'e + (throughout): remove | except in a \verb command in verbatim env + +2011-11-02 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> + + * faq-backgrnd.tex (q-context): add link to context standalone site + + * faq-projects.tex (q-luatex): diddle with version numbers, add web doc + link + *** release 3.24 *** 2011-11-01 Robin Fairbairns <rf10@warp.cl.cam.ac.uk> diff --git a/Master/texmf-dist/doc/generic/FAQ-en/FAQ-html.tar.gz b/Master/texmf-dist/doc/generic/FAQ-en/FAQ-html.tar.gz Binary files differindex 7977e2f5142..925cd1b08d1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/FAQ-html.tar.gz +++ b/Master/texmf-dist/doc/generic/FAQ-en/FAQ-html.tar.gz diff --git a/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex b/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex index 74f02064f3c..dd5155a9c70 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.282 2011/10/25 18:22:56 rf10 Exp rf10 $ +% $Id: dirctan.tex,v 1.291 2012/02/26 16:56:42 rf10 Exp rf10 $ % % protect ourself against being read twice \csname readCTANdirs\endcsname @@ -242,6 +242,7 @@ \CTANdirectory{dante}{usergrps/dante} \CTANdirectory{dante-faq}{help/de-tex-faq} \CTANdirectory{databases}{biblio/bibtex/databases} +\CTANdirectory{datatool}{macros/latex/contrib/datatool}[datatool] \CTANdirectory{datetime}{macros/latex/contrib/datetime} \CTANdirectory{db2tex}{support/db2tex} \CTANdirectory{dblfloatfix}{macros/latex/contrib/dblfloatfix}[dblfloatfix] @@ -250,6 +251,7 @@ \CTANdirectory{dc-nfss}{language/hyphen-accent/dc-nfss} \CTANdirectory{detex}{support/detex}[detex] \CTANdirectory{devanagari}{language/devanagari} +\CTANdirectory{diagbox}{macros/latex/contrib/diagbox}[diagbox] \CTANdirectory{diagrams}{macros/generic/diagrams} \CTANdirectory{dijkstra}{web/spiderweb/src/dijkstra} \CTANdirectory{dinbrief}{macros/latex/contrib/dinbrief} @@ -371,6 +373,7 @@ \CTANdirectory{fancyvrb}{macros/latex/contrib/fancyvrb}[fancyvrb] \CTANdirectory{faq}{help/uk-tex-faq}[uk-tex-faq] \CTANdirectory{fc}{fonts/jknappen/fc} +\CTANdirectory{fdsymbol}{fonts/fdsymbol}[fdsymbol] \CTANdirectory{feyn}{fonts/feyn} \CTANdirectory{feynman}{macros/latex209/contrib/feynman} \CTANdirectory{feynmf}{macros/latex/contrib/feynmf}[feynmf] @@ -526,6 +529,7 @@ \CTANdirectory{lamstex}{macros/lamstex} \CTANdirectory{lastpage}{macros/latex/contrib/lastpage}[lastpage] \CTANdirectory{latex}{macros/latex/base} +\CTANdirectory{latex-course}{info/latex-course}[latex-course] \CTANdirectory{latex-essential}{info/latex-essential} \CTANdirectory{latex2e-help-texinfo}{info/latex2e-help-texinfo}[latex2e-help-texinfo] \CTANdirectory{latex4jed}{support/jed}[latex4jed] @@ -566,6 +570,7 @@ \CTANdirectory{lwc}{info/examples/lwc} \CTANdirectory{ly1}{fonts/psfonts/ly1}[ly1] \CTANdirectory*{mactex}{systems/mac/mactex}[mactex] +\CTANdirectory{macros2e}{info/macros2e}[macros2e] \CTANdirectory{mactotex}{graphics/mactotex} \CTANdirectory{mailing}{macros/latex/contrib/mailing} \CTANdirectory{make_latex}{support/make_latex}[make-latex] @@ -591,17 +596,15 @@ \CTANdirectory{mathspic}{graphics/mathspic}[mathspic] \CTANdirectory{mcite}{macros/latex/contrib/mcite}[mcite] \CTANdirectory{mciteplus}{macros/latex/contrib/mciteplus}[mciteplus] -\CTANdirectory{mctex}{support/mctex} +\CTANdirectory{mdframed}{macros/latex/contrib/mdframed}[mdframed] +\CTANdirectory{mdsymbol}{fonts/mdsymbol}[mdsymbol] \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} \CTANdirectory{metalogo}{macros/latex/contrib/metalogo}[metalogo] \CTANdirectory{metapost}{graphics/metapost} \CTANdirectory{metatype1}{fonts/utilities/metatype1}[metatype1] -\CTANdirectory{mewltx}{support/mewltx} -\CTANdirectory{mf-extra}{fonts/cm/mf-extra} \CTANdirectory{mf2ps}{fonts/utilities/mf2ps} \CTANdirectory{mf2pt1}{support/mf2pt1}[mf2pt1] \CTANdirectory{mf_optimized_kerning}{fonts/cm/mf_optimized_kerning} @@ -620,6 +623,7 @@ \CTANdirectory{minionpro}{fonts/minionpro}[minionpro] \CTANdirectory{minitoc}{macros/latex/contrib/minitoc}[minitoc] \CTANdirectory{minted}{macros/latex/contrib/minted}[minted] +\CTANdirectory{mkjobtexmf}{support/mkjobtexmf}[mkjobtexmf] \CTANdirectory{mma2ltx}{graphics/mma2ltx} \CTANdirectory{mnsymbol}{fonts/mnsymbol}[mnsymbol] \CTANdirectory{mnu}{support/mnu} @@ -628,6 +632,7 @@ \CTANdirectory{modes}{fonts/modes} \CTANdirectory{morefloats}{macros/latex/contrib/morefloats}[morefloats] \CTANdirectory{moreverb}{macros/latex/contrib/moreverb}[moreverb] +\CTANdirectory{morewrites}{macros/latex/contrib/morewrites}[morewrites] \CTANdirectory{mparhack}{macros/latex/contrib/mparhack}[mparhack] \CTANdirectory{mpgraphics}{macros/latex/contrib/mpgraphics}[mpgraphics] \CTANdirectory{mps2eps}{support/mps2eps} @@ -700,6 +705,7 @@ \CTANdirectory{pcwritex}{support/pcwritex} \CTANdirectory{pdcmac}{macros/plain/contrib/pdcmac}[pdcmac] \CTANdirectory{pdfpages}{macros/latex/contrib/pdfpages}[pdfpages] +\CTANdirectory{pdfscreen}{macros/latex/contrib/pdfscreen}[pdfscreen] \CTANdirectory{pdftex}{systems/pdftex}[pdftex] \CTANdirectory{pdftex-graphics}{graphics/metapost/contrib/tools/mptopdf}[pdf-mps-supp] \CTANdirectory{pdftricks}{macros/latex/contrib/pdftricks}[pdftricks] @@ -715,6 +721,7 @@ \CTANdirectory{pictex-addon}{graphics/pictex/addon}[pictexwd] \CTANdirectory{pictex-converter}{support/pictex-converter} \CTANdirectory{pictex-summary}{info/pictex/summary}[pictexsum] +\CTANdirectory{pinlabel}{macros/latex/contrib/pinlabel}[pinlabel] \CTANdirectory{pkbbox}{fonts/utilities/pkbbox} \CTANdirectory{pkfix}{support/pkfix}[pkfix] \CTANdirectory{pkfix-helper}{support/pkfix-helper}[pkfix-helper] @@ -826,6 +833,7 @@ \CTANdirectory{svninfo}{macros/latex/contrib/svninfo}[svninfo] \CTANdirectory{swebib}{biblio/bibtex/contrib/swebib} \CTANdirectory*{symbols}{info/symbols/comprehensive}[comprehensive] +\CTANdirectory{tablefootnote}{macros/latex/contrib/tablefootnote}[tablefootnote] \CTANdirectory{tabls}{macros/latex/contrib/tabls}[tabls] \CTANdirectory{tabulary}{macros/latex/contrib/tabulary}[tabulary] \CTANdirectory{talk}{macros/latex/contrib/talk}[talk] @@ -898,6 +906,7 @@ \CTANdirectory{urlbst}{biblio/bibtex/contrib/urlbst}[urlbst] \CTANdirectory{urw-base35}{fonts/urw/base35}[urw-base35] \CTANdirectory{urwchancal}{fonts/urwchancal}[urwchancal] +\CTANdirectory{usebib}{macros/latex/contrib/usebib}[usebib] \CTANdirectory{utopia}{fonts/utopia}[utopia] \CTANdirectory{varisize}{macros/plain/contrib/varisize}[varisize] \CTANdirectory{varwidth}{macros/latex/contrib/varwidth}[varwidth] @@ -934,10 +943,12 @@ \CTANdirectory{xmltex}{macros/xmltex/base}[xmltex] \CTANdirectory*{xpdf}{support/xpdf}[xpdf] \CTANdirectory{xtab}{macros/latex/contrib/xtab}[xtab] +\CTANdirectory{xwatermark}{macros/latex/contrib/xwatermark}[xwatermark] \CTANdirectory{yagusylo}{macros/latex/contrib/yagusylo}[yagusylo] \CTANdirectory{yhmath-fonts}{fonts/yhmath}[yhmath] \CTANdirectory{yhmath-macros}{macros/latex/contrib/yhmath} \CTANdirectory{zefonts}{fonts/zefonts}[zefonts] \CTANdirectory{ziffer}{macros/latex/contrib/ziffer}[ziffer] \CTANdirectory{zoon-mp-eg}{info/metapost/examples}[metapost-examples] +\CTANdirectory{zwpagelayout}{macros/latex/contrib/zwpagelayout}[zwpagelayout] \endinput 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 b03de85315d..63a9dc49fd3 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.35 2011/10/12 21:58:46 rf10 Exp rf10 $ +% $Id: faq-adj-types.tex,v 1.41 2012/02/18 19:28:56 rf10 Exp rf10 $ \section{Adjusting the typesetting} @@ -138,6 +138,7 @@ available, with examples, in %\item[ifmslide.sty]\CTANref{ifmslide} \item[lecturer.sty]\CTANref{lecturer} \item[seminar.cls]\CTANref{seminar} +\item[pdfscreen.sty]\CTANref{pdfscreen} \item[pgf.sty]\CTANref{pgf} \item[powerdot.cls]\CTANref{powerdot} \item[pp4]\CTANref{ppower4} @@ -215,7 +216,7 @@ route): \begin{ctanrefs} \item[a0poster.cls]\CTANref{a0poster} \item[beamer.cls]\CTANref{beamer} -\item[beamberposter.sty]\CTANref{beamerposter} +\item[beamerposter.sty]\CTANref{beamerposter} \item[flowfram.sty]\CTANref{flowfram} \item[multicol.sty]Distributed as part of \CTANref{2etools}[multicol] \item[sciposter.cls]\CTANref{sciposter} @@ -815,10 +816,10 @@ and \csx{subparagraph}; you can (if you \emph{must}) arrange that these two commands produce numbered headings, so that you can use them as \csx{subsubsubsection}s and lower. -The \Package{titlesec} allows you to adjust the definitions of the -sectioning macros, and it may be used to -transform a \csx{paragraph}'s typesetting so that it looks like that -of a \csx{section}. +The \Package{titlesec} package provides a sensible set of macros for +you to adjust the definitions of the sectioning macros, and it may be +used to transform a \csx{paragraph}'s typesetting so that it looks +like that of a \csx{section}. If you want to program the change yourself, you'll find that the commands (\csx{section} all the way down to \csx{subparagraph}) are @@ -826,13 +827,21 @@ defined in terms of the internal \csx{@startsection} command, which takes 6~arguments. Before attempting this sort of work, you are well advised to read the \LaTeX{} sources (\File{ltsect.dtx} in the \LaTeX{} distribution) and the source of the standard packages -(\File{classes.dtx}). The \Qref*{\LaTeX{} Companion}{Q-latex-books} -discusses use of \csx{@startsection} for this sort of thing. +(\File{classes.dtx}), or to make use of the % ! line break +\Qref*{\LaTeX{} Companion}{Q-latex-books}, which +discusses the use of \csx{@startsection} for this sort of thing. + +You will note that Lamport didn't go on adding ``\texttt{sub}'' to the +names of sectioning commands, when creating commands for the lowest +levels of a document. This would seem sensible to any but the most +rigorous stickler for symmetry~--- it would surely challenge pretty +much anyone's reading of the source of a document, if there was a need +to distinguish \csx{subsubsubsection} and \csx{subsubsubsubsection} \begin{ctanrefs} \item[\nothtml{\rmfamily}\LaTeX{} source]\CTANref{latex} \item[titlesec.sty]\CTANref{titlesec} \end{ctanrefs} -\LastEdit{2011-06-01} +\LastEdit{2012-02-14} \Question[Q-captsty]{The style of captions} @@ -1203,8 +1212,16 @@ you're using is odd enough that it puts a page header on a chapter's opening page. Note that the \Package{titlesec} package manages the running heads in -a completely different fashion; users of that package should refer to -the documentation. +a completely different fashion; for example, you can use the optional +argument of sectioning commands for page headers, only, by loading the +package as: +\begin{quote} +\begin{verbatim} +\usepackage[toctitles]{titlesec} +\end{verbatim} +\end{quote} +The package documentation offers other useful techniques in this area. +\LeadFrom{Tobi}{sx}{2012-02-01} The \Class{memoir} class avoids all the silliness by providing an extra optional argument for chapter and sectioning commands, for @@ -1230,6 +1247,7 @@ tailor the header text to fit, with very little trouble. \item[memoir.cls]\CTANref{memoir} \item[titlesec.sty]\CTANref{titlesec} \end{ctanrefs} +\LastEdit{2012-02-01} \nothtml{\begingroup\boldmath} \Question[Q-nofm]{Page numbering ``\meta{n} of \meta{m}''} @@ -1387,7 +1405,8 @@ paper size can be programmed by the document. Users who wish to, may of course consult the manuals of the various programs to write the necessary code. -The \Package{geometry} package (whose main business is defining +The \Package{geometry} and \Package{zwpagelayout} packages (whose main +business includes defining typeset page areas), also takes notice the size of the paper that the document is going to be printed on, and can issue the commands necessary to ensure the correct size of paper is used. If @@ -1398,7 +1417,7 @@ 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, when you are using \latex{}, is to add +So, one resolution of the problem, when you are using \latex{}, is to add \begin{quote} \begin{verbatim} \usepackage[processor-option,...]{geometry} @@ -1419,6 +1438,16 @@ If you're using \PDFLaTeX{}, \xetex{} or V\TeX{}, load with where \pkgoption{program-option} is \pkgoption{pdftex}, \pkgoption{xetex} or \pkgoption{vtex}. +The alternative, \Package{zwpagelayout} requires a \pkgoption{driver} +option: +\begin{quote} +\begin{verbatim} +\usepackage[driver=value,...]{zwpagelayout} +\end{verbatim} +\end{quote} +(permissible \meta{values} are \pkgoption{pdftex}, \pkgoption{xetex} +and \pkgoption{dvips}; the default value is \pkgoption{unknown}). + Needless to say, both the ``big'' classes (\Class{koma-script} and \Class{memoir}) provide their own ways to get the paper size ``right''. @@ -1440,8 +1469,9 @@ output that specifies the necessary paper size. \item[geometry.sty]\CTANref{geometry} \item[memoir.cls]\CTANref{memoir} \item[typearea.sty]Distributed as part of \CTANref{koma-script}[typearea] +\item[zwpagelayout.sty]\CTANref{zwpagelayout} \end{ctanrefs} -\LastEdit{2011-03-07} +\LastEdit{2011-12-12} \Question[Q-changemargin]{Changing the margins in \LaTeX{}} @@ -1485,10 +1515,11 @@ temporarily~--- and there's an answer that covers that, too: \Question[Q-marginpkgs]{Packages to set up page designs} -The `ultimate' tool for adjusting the dimensions and position of the -printed material on the page is the \Package{geometry} package; a very +There are two trustworthy tools for adjusting the dimensions and position of the +printed material on the page are \Package{geometry} and the +\Package{zwpagelayout} packages; a very wide range of adjustments of the layout may be relatively -straightforwardly programmed, and package documentation is good and +straightforwardly programmed with either, and package documentation is good and comprehensive. As is usual, users of the \Class{memoir} class have built-in @@ -1497,9 +1528,11 @@ are recommended to use an alternative package, \Package{typearea}. In either case it is difficult to argue that users should go for \Package{geometry}: both alternatives are good. -The documentation of \Package{geometry} is a bit overwhelming, and -learning all its capabilities may be more than you ever need. -Somewhat simpler to use is the \Package{vmargin} package, which has a +The documentation both of \Package{geometry} and of +\Package{zwpagelayout} is rather overwhelming, and +learning all of of either package's capabilities is likely to be more +than you ever need. +The \Package{vmargin} package is somewhat simpler to use: it has a canned set of paper sizes (a superset of that provided in \LaTeXe{}), provision for custom paper, margin adjustments and provision for two-sided printing. @@ -1510,17 +1543,19 @@ two-sided printing. \item[memoir.cls]\CTANref{memoir} \item[typearea.sty]Distributed as part of \CTANref{koma-script}[typearea] \item[vmargin.sty]\CTANref{vmargin} +\item[zwpagelayout.sty]\CTANref{zwpagelayout} \end{ctanrefs} +\LastEdit{2011-12-12} \Question[Q-marginmanual]{How to set up page layout ``by hand''} So you're eager to do it yourself, notwithstanding the cautions -\begin{narrowversion} +\begin{flatversion} outlined above (\Qref{}{Q-changemargin}). -\end{narrowversion} -\begin{wideversion} +\end{flatversion} +\begin{hyperversion} outlined in ``\Qref{changing margins}{Q-changemargin}''. -\end{wideversion} +\end{hyperversion} It's important that you first start by familiarising yourself with LaTeX's page layout parameters. For example, see section C.5.3 of the @@ -1768,6 +1803,9 @@ The \Package{draftwatermark} package uses the same author's \Package{everypage} package to provide a simple interface for adding textual (`DRAFT'-like) watermarks. +The \Package{xwatermark} package provides very flexible watermarking, +with a ``modern'' (key-value) interface. + More elaborate watermarks may be achieved using the \Package{eso-pic} package, which in turn uses the package \Package{everyshi}, or by using \Package{everypage}. \Package{Eso-pic} attaches a @@ -1790,6 +1828,23 @@ the content of the page. \Package{Everypage} allows you to add ``something'' to every page, or to a particular page; you therefore need to construct your own apparatus for anything complicated. + +Finally, one can use the \ProgName{pdftk} untility; with it, the +command: +\begin{quote} +\begin{verbatim} +pdftk a.pdf background b.pdf output c.pdf +\end{verbatim} +\end{quote} +will recreate \File{a.pdf} as \File{c.pdf}, having used the first page +of \File{b.pdf} as background on every page. If you have a standard +background (``DRAFT'' or ``SECRET'', or whatever) used in several +files, \ProgName{pdftk} might well be attractive. + +\ProgName{Pdftk} is available as a command line tool; it is available +in most linux distritbutions, but may be downloaded from its +% ! line break +\href{http://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/}{home site} \begin{ctanrefs} \item[atbegshi.sty]Distributed as part of \CTANref{oberdiek}[atbegshi] \item[draftcopy.sty]\CTANref{draftcopy} @@ -3041,7 +3096,7 @@ out beyond the side or the bottom of the page if it doesn't fit in the typeset area. If you want a substantial portion of your text to be framed (or -coloured), the restriction starts to seem a real imposition. +coloured), the restriction imposes a serious restriction. Fortunately, there are ways around the problem. The \Package{framed} package provides \environment{framed} and @@ -3053,6 +3108,14 @@ marginpars and head-line entries, and will not work with \Class{memoir} class includes the functionality of the \Package{framed} package. +The \Package{mdframed} package does the same job, using a different +algorithm. The package also provides means of defining +`private' framed environments, whose parameters are set at definition +time, thus saving considerable effort in documents with many framed +boxes. Its restrictions seem much the same as those of +\Package{framed}; this is as one would expect, but the list is +noticeably different in the two packages' documentation. + The \Package{boites} package provides a \environment{breakbox} environment; examples of its use may be found in the distribution, and the package's \File{README} file contains terse documentation. The @@ -3073,9 +3136,11 @@ current \LaTeX{}. \item[backgrnd.tex]\CTANref{backgrnd} \item[boites.sty]\CTANref{boites} \item[framed.sty]\CTANref{framed} +\item[mdframed.sty]\CTANref{mdframed} \item[memoir.cls]\CTANref{memoir} \item[shade.tex]\CTANref{shade} \end{ctanrefs} +\LastEdit{2012-02-14} \Question[Q-overstrike]{Overstriking characters} 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 60219017103..ec62131e433 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex @@ -803,11 +803,16 @@ happens). large as that of latex{}), but those developers who are active seem to have prodigious energy. Support is available via a % ! line break \href{http://contextgarden.net}{\acro{WIKI} site} and via the -\href{http://www.ntg.nl/mailman/listinfo/ntg-context}{mailing list}. +\href{http://www.ntg.nl/mailman/listinfo/ntg-context}{mailing list}; +a ``standalone'' distribution (a \TeX{} distribution with no macros +other than \context{}-based ones) is available from +\url{http://wiki.contextgarden.net/ConTeXt_Standalone}~--- it provides +a \context{} system on any of a number of platforms, executing either +mark~ii or mark~iv \context{}. \begin{ctanrefs} \item[\nothtml{\rmfamily}\CONTeXT{} distribution]\CTANref{context} \end{ctanrefs} -\LastEdit{2011-06-12} +\LastEdit{2011-11-02} \Question[Q-AMSpkg]{What are the \acro{AMS} packages (\AMSTeX{}, \emph{etc}.)?} 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 c1851a5ccd9..e23a5a512fd 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.11 2011/03/08 20:08:01 rf10 Exp $ +% $Id: faq-biblio.tex,v 1.12 2012/02/11 10:14:41 rf10 Exp rf10 $ \section{Bibliographies and citations} @@ -1049,13 +1049,25 @@ Note that \Package{jurabib} does the job using \LaTeX{}'s standard footnotes, whereas \Package{footbib} creates its own sequence of footnotes. Therefore, in a document which has other footnotes, it may be advisable to use \Package{jurabib} (or of course -\Package{inlinebib}), to avoid confusion of footnotes and foot-citations. +\Package{inlinebib}), to avoid confusion of footnotes and +foot-citations. + +The \Package{usebib} package offers a `toolbox', which allows the user +to place exactly what is needed, in the text (that is, rather than a +full citation). The package's command, that does the actual +typesetting, is \cmdinvoke{usebibdata}{\meta{key}}{\meta{field}}; it +typesets the \emph{field} item from the entry \emph{key} in the +bibliography; the user then formats the entry as desired~--- obviously +one could construct one's own bibliography, altogether, from this +command, but it would quickly become tedious. \begin{ctanrefs} \item[bibentry.sty]\emph{Distributed with} \CTANref{natbib} \item[footbib.sty]\CTANref{footbib} \item[inlinebib.sty]\CTANref{inlinebib} \item[jurabib.sty]\CTANref{jurabib} +\item[usebib.sty]\CTANref{usebib} \end{ctanrefs} +\LastEdit{2012-03-23} \Question[Q-citesort]{Sorting and compressing citations} @@ -1072,15 +1084,17 @@ with the \pkgoption{numbers} and \pkgoption{sort\&compress} options, will do the same when working with its own numeric bibliography styles (\File{plainnat.bst} and \File{unsrtnat.bst}). -Both \Package{cite} and \Package{natbib} will interwork with -\Package{hyperref}, thus making links to the bibliography for +The package \Package{biblatex} has a built-in style +\Package{numeric-comp} for its bibliographies. \begin{ctanrefs} +\item[biblatex.sty]\CTANref{biblatex} \item[cite.sty]\CTANref{cite} \item[hypernat.sty]\CTANref{hypernat} \item[hyperref.sty]\CTANref{hyperref} \item[plainnat.bst]Distributed with \CTANref{natbib} \item[unsrtnat.bst]Distributed with \CTANref{natbib} \end{ctanrefs} +\LastEdit{2012-02-10} \Question[Q-mcite]{Multiple citations} @@ -1283,14 +1297,20 @@ writes in another language (or who deal with citations in the style of other disciplines than maths) to strike out into contributed software. For the user whose language is not English, there are several -alternatives. The simplest is to provide translations of \BibTeX{} -styles into the required language: the solitary \Package{finplain.bst} -does that for Finnish; others one can find are for Danish -(\Package{dk-bib}), French (\Package{bib-fr}), German -(\Package{bibgerm}), Norwegian (\Package{norbib}) and Swedish -(\Package{swebib}) bundles (of which the \Package{bib-fr} set is the -most extensive). The \Package{spain} style implements a traditional -Spanish citation style. +alternatives. Possibly most straightforward is to switch to using +\Package{biblatex}, which can produce a bibliography appropriate to +several languages. However, \Package{biblatex} is large and has +correspondingly large documentation (though it is well-written and +pleasingly typeset), so its adoption takes time. + +Otherwise, the simplest procedure is to provide translations of +\BibTeX{} styles into the +required language: the solitary \Package{finplain.bst} does that for +Finnish; others one can find are for Danish (\Package{dk-bib}), French +(\Package{bib-fr}), German (\Package{bibgerm}), Norwegian +(\Package{norbib}) and Swedish (\Package{swebib}) bundles (of which +the \Package{bib-fr} set is the most extensive). The \Package{spain} +style implements a traditional Spanish citation style. These static approaches solve the problem, for the languages that have been covered by them. Unfortunately, with such an approach, a lot of @@ -1320,12 +1340,14 @@ freedom via the extensibility of \Package{babelbib} \item[babelbib.sty]\CTANref{babelbib} \item[bib-fr \nothtml{\rmfamily\upshape}bundle]\CTANref{bib-fr} \item[bibgerm \nothtml{\rmfamily\upshape}bundle]\CTANref{bibgerm} +\item[biblatex.sty]\CTANref{biblatex} \item[custom-bib \nothtml{\rmfamily\upshape}bundle]\CTANref{custom-bib} \item[finplain.bst]\CTANref{finplain} \item[norbib \nothtml{\rmfamily\upshape}bundle]\CTANref{norbib} \item[spain]\CTANref{spain} \item[swebib \nothtml{\rmfamily\upshape}bundle]\CTANref{swebib} \end{ctanrefs} +\LastEdit{2012-03-23} \Question[Q-formbiblabel]{Format of numbers in the bibliography} 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 a6ed86b6617..be1a21ba66b 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.23 2011/10/25 21:30:42 rf10 Exp rf10 $ +% $Id: faq-bits+pieces.tex,v 1.24 2012/03/10 13:56:18 rf10 Exp rf10 $ \section{Bits and pieces of \AllTeX{}} @@ -765,18 +765,22 @@ option \pkgoption{utf8x}. Broadly, the difference is that \pkgoption{utf8} deals with ``standard \latex{} fonts'' (those for which \latex{} has a defined encoding), while \pkgoption{utf8x} deals with pretty much anything for which it knows a mapping of a Unicode -range to a font. - -The up-and-coming \tex{}-alike applications, \Qref*{\xetex{}}{Q-xetex} -and \Qref*{\luatex{}}{Q-luatex} read \acro{UTF}-8 representations of -Unicode as standard. They also use TrueType or OpenType fonts for -output; each such font ``declares'' which part(s) of the Unicode space -it covers, so that the \tex{}-alike engines can decide which font to -use for which character. +range to a font. As a general rule, you should never use +\Package{ucs}/\pkgoption{utf8x} until you have convinced yourself that +\Package{inputenc}/\pkgoption{utf8} can not do the job for you. + +`Modern' \tex{}-alike applications, \Qref*{\xetex{}}{Q-xetex} and +\Qref*{\luatex{}}{Q-luatex} read their input using \acro{UTF}-8 +representations of Unicode as standard. They also use TrueType or +OpenType fonts for output; each such font has tables that tell the +application which part(s) of the Unicode space it covers; the tables +enable the engines to decide which font to use for which character +(assuming there is any choice at all). \begin{ctanrefs} \item[inputenc.sty]Part of the \CTANref{latex} distribution \item[ucs.sty]\CTANref{unicode} \end{ctanrefs} +\LastEdit{2011-03-07} \Question[Q-tds]{What is the \acro{TDS}?} 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 33a819732c5..43c948b6dec 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: faq-docs.tex,v 1.29 2011/10/25 18:22:56 rf10 Exp rf10 $ +% $Id: faq-docs.tex,v 1.37 2012/02/18 19:28:56 rf10 Exp rf10 $ \section{Documentation and Help} @@ -585,7 +585,7 @@ The above advice, differently phrased, may also be read on the web at article may be found at \URL{http://www.minimalbeispiel.de/}, in both German and English. -\Question[Q-tutorials*]{\AllTeX{} Tutorials, etc.} +\Question[Q-tutorials*]{Tutorials, etc., for \tex{}-based systems} From a situation where every \AllTeX{} user \emph{had} to buy a book if she was not to find herself groping blindly along, we now have what @@ -599,10 +599,10 @@ Next comes a selection of \Qref*{``specialised'' \AllTeX{} tutorials}{Q-tutbitslatex}, each of which concentrates on a single \LaTeX{} topic. -A couple of reference documents (it would be good to have more) are -listed in an \Qref*{answer of their own}{Q-ref-doc}. +A small selection of reference documents (it would be good to have +more) are listed in an \Qref*{answer of their own}{Q-ref-doc}. -Next comes the (rather new) field of % ! line break +Next comes the (somewhat newer) field of % ! line break \Qref*{\TeX{}-related WIKIs}{Q-doc-wiki}. A rather short list gives us a % ! line break @@ -614,7 +614,7 @@ A rather short list gives us a % ! line break Michael Doob's splendid `Gentle Introduction' to \plaintex{} (available on \acro{CTAN}) has been stable for a very long time. -Another recommendable document is D. R.~Wilkins `Getting started with \TeX{}', +Another recommendable document is D. R.~Wilkins' `Getting started with \TeX{}', available on the web at \URL{http://www.ntg.nl/doc/wilkins/pllong.pdf} \begin{ctanrefs} \item[\nothtml{\rmfamily}Gentle Introduction]\CTANref{gentle} @@ -665,20 +665,33 @@ is a pleasing short introduction to the use of \AllTeX{}; some of the slides for \emph{actual} tutorials are to be found on the page, as well. +D. R.~Wilkins' % ! line break +\href{http://www.maths.tcd.ie/~dwilkins/LaTeXPrimer/}{`Getting started with \latex{}'} +also looks good (it appears shorter~--- more of a primer~--- than some +of the other offerings). + Chris Harrison's % ! line break -\href{http://www.chrisharrison.co.uk/xophbook/mybooks/tex/index.html}{TeX book} -presents basic \LaTeX{} with useful hints for extensions +\href{http://xoph.co/20111024/latex-tutorial/}{LaTeX tutorial} +presents basic \LaTeX{} in a rather pleasing and straightforward way. Nicola Talbot's % ! line break \href{http://theoval.cmp.uea.ac.uk/~nlct/latex/novices/}{\LaTeX{} for complete novices} does what it claims: the author teaches \LaTeX{} at the University of -East Anglia. That is one of several of Nicola's % ! line break +East Anglia. That is one of several % ! line break \href{http://theoval.cmp.uea.ac.uk/~nlct/latex/}{introductory tutorials}, which include exercises (with solutions). Other tutorials include those for writing theses/dissertations with \LaTeX{}, and for using \LaTeX{} in administrative work. (The page seems to be an adjunct to her \LaTeX{} courses~--- fortunate people, the people of \acro{UEA}!). +Engelbert Buxbaum provides the `slides' for his \latex{} course `The +\latex{} document preparation system'; this seems to be a departmental +course at his university. + +Mark van Dongen's % line break +\href{"http://csweb.ucc.ie/~dongen/LaTeX-and-Friends.pdf}{`\latex and friends'} +appeared as he was writing his book on the subject (soon to be published). + An interesting (and practical) tutorial about what \emph{not} to do is \Package{l2tabu}, or ``A list of sins of \LaTeXe{} users'' by Mark Trettin, translated into English by J\"urgen Fenn. The @@ -690,6 +703,7 @@ the source is also available). \item[\nothtml{\rmfamily}Getting something out of \latex{}]\CTANref{first-latex-doc} % ! line break \item[\nothtml{\rmfamily}Getting up and running with \AMSLaTeX{}]\CTANref{amslatex-primer} +\item[\nothtml{\rmfamily}Slides for \latex{} course]\CTANref{latex-course} \item[\nothtml{\rmfamily}Not so Short Introduction]\CTANref{lshort} (in English, you may browse for sources and other language versions at \CTANref{lshort-parent}) @@ -745,14 +759,19 @@ excellent introduction to graphics use. It's available on \acro{CTAN}, but not in the \texlive{} or miktex{} distributions, for lack of sources. -Kjell Magne Fauske offers a set of examples of the use of the drawing +Stefan Kottwitz manages a web site devoted to the use of the drawing packages % ! line break -\Qref*{\acro{PGF} and \acro{T}ik\acro{Z}}{Q-drawing}; the % ! line break -\href{http://www.texample.net/tikz/examples/}{examples catalogue} +\Qref*{\acro{PGF} and \acro{T}ik\acro{Z}}{Q-drawing}, % ! line break +\url{http://www.texample.net/} + +Included is % ! line break + \href{http://www.texample.net/tikz/examples/}{examples catalogue} includes examples (with output) from the package documentation as well -as code written by the author himself. The compendious -\acro{PGF}/\acro{T}ik\acro{Z} manual is clear, but is bewildering for -some beginners. The ! line break +as code written by the original site maintainer (Kjell Magne Fauske) +and others. + +The compendious \acro{PGF}/\acro{T}ik\acro{Z} manual is clear, but is +bewildering for some beginners. The % ! line break \href{http://cremeronline.com/LaTeX/minimaltikz.pdf}{`minimal' introduction} has helped at least the present author. @@ -777,23 +796,12 @@ author's macros for papers submitted for \acro{IEEE} publications). The issues are also covered in a later % ! line break \Qref{\acro{FAQ} answer}{Q-dvips-pdf}. -Documentation of Japanese \TeX{} use appears at least twice on the web: -Haruhiko Okumura's page on +Documentation of Japanese \ensuremath{\Omega{}} use appears in +Haruhiko Okumura's page % ! line break \href{http://oku.edu.mie-u.ac.jp/~okumura/texfaq/japanese/}{typesetting Japanese with Omega} (the parent page is in Japanese, so out of the scope of this -\acro{FAQ}). - -One ``Tim'' documents p\TeX{} (a \TeX{} system widely used in Japan) -in his -\begin{narrowversion} - ``English notes on p\TeX{}'' (see - \url{http://www.users.waitrose.com/~nihilist/English_Notes_on_pTex.pdf}). -\end{narrowversion} -\begin{wideversion} - % ! line break - ``\href{http://www.users.waitrose.com/~nihilist/English_Notes_on_pTex.pdf}{English notes on p\TeX{}}''. -\end{wideversion} +\acro{FAQ} list). Some university departments make their local documentation available on the web. Most straightforwardly, there's the simple translation of @@ -806,7 +814,7 @@ More ambitiously, some university departments have enthusiastic documenters who make public record of their \AllTeX{} support. For example, Tim Love (of Cambridge University Engineering Department) maintains his -deparment's pages at +department's pages at \URL{http://www-h.eng.cam.ac.uk/help/tpl/textprocessing/} %% and Mimi %% Burbank (of the School of Computer Science \& Information Technology @@ -846,6 +854,9 @@ al)'s % !line break an extent) work in progress, but is generally reliable (source is available on the.archive as well). +Martin Scharrer's ``List of internal \latex{} macros'' is a help to +those aiming to write a class or package. + 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} @@ -853,8 +864,9 @@ also looks good. \begin{ctanrefs} \item[\nothtml{\rmfamily}Cheat sheet]\CTANref{latexcheat} \item[\nothtml{\rmfamily}LaTeX reference manual]\CTANref{latex2e-help-texinfo} +\item[\nothtml{\rmfamily}LaTeX internal macros]\CTANref{macros2e} \end{ctanrefs} -\LastEdit{2010-12-08} +\LastEdit{2012-02-16} \Question[Q-doc-wiki]{\acro{WIKI} books for \TeX{} and friends} @@ -963,9 +975,9 @@ seems useful), you will more often than not find documentation that way. If your luck (as defined above) doesn't hold out, you've got to find -documentation by other means. This is where you need to exercise your -intelligence: you have to find the documentation for yourself. What -follows offers a range of possible techniques. +documentation by other means. That is, you have to find the +documentation for yourself. The rest of this answer offers a range of +possible techniques. The commonest form of documentation of \LaTeX{} add-ons is within the \extension{dtx} file in which the code is distributed (see @@ -1009,7 +1021,7 @@ to write, it should be hard to use'' philosophy). Most ordinary mortals will seek support from some more experienced user at this stage, though it \emph{is} possible to proceed in the way that the original author apparently expected\dots{}by reading his code. -\LastEdit{2011-07-19} +\LastEdit{2011-12-29} \Question[Q-writecls]{Learning to write \LaTeX{} classes and packages} @@ -1078,10 +1090,10 @@ section describes how to use \MP{} illustrations in \LaTeX{} and \PDFLaTeX{} documents, with an emphasis on how to use appropriate fonts for any text or mathematics. -% Hans Hagen (of \CONTeXT{} fame) offers a \MP{} tutorial called -% MetaFun (which admittedly concentrates on the use of \MP{} within -% \CONTeXT{}). It may be found on his company's % ! line break -% \href{http://www.pragma-ade.com/metapost.htm}{\MP{} page}. +Hans Hagen (of \CONTeXT{} fame) offers a \MP{} tutorial called +MetaFun (which admittedly concentrates on the use of \MP{} within +\CONTeXT{}). It may be found on his company's % ! line break +\href{http://www.pragma-ade.com/general/manuals/metafun-p.pdf}{`manuals' page}. Other \MP{} tutorials that have appeared are two in English by % ! line breaks \href{http://remote.science.uva.nl/~heck/Courses/mptut.pdf}{Andr\'e Heck} @@ -1108,6 +1120,7 @@ written more as a document, and presented in \acro{PDF}. \item[\nothtml{\rmfamily}Peter Wilson's ``experiences'']\CTANref{metafp-pdf} \item[\nothtml{\rmfamily}Vincent Zoonekynd's examples]\CTANref{zoon-mp-eg} \end{ctanrefs} +\LastEdit{2011-11-21} \Question[Q-BibTeXing]{\bibtex{} Documentation} @@ -1123,7 +1136,7 @@ books.) The document ``Designing \bibtex{} Styles'', also in the \bibtex{} distribution (look for -\File{btxhak}, explains the postfix stack-based language used to +\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}, diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex index 7b7af0a55bc..cc349bdcb11 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex @@ -286,29 +286,43 @@ updated only once a day, a nightly automatic download (perhaps using \Question[Q-findfont]{Finding new fonts} -A comprehensive list of \MF{} fonts used to be posted to -\Newsgroup{comp.fonts} and to \Newsgroup{comp.text.tex}, roughly -every six weeks, by Lee Quin. -Nowadays, authors of new material in \MF{} are few and far between -(and mostly designing highly specialised things with limited appeal to -ordinary users); as a result, no-one has taken over maintenance of the -list of fonts. If you need a font for some esoteric purpose, it may -be worth \Qref*{searching \acro{CTAN}}{Q-findfiles} using your purpose -as a search keyword. - -Most new fonts that appear are prepared in some scalable outline form -or other, and a large proportion is distributed under commercial -terms. However, once you have acquired such a font, converting it to -a form usable by your \AllTeX{} distribution is not (in principle) a -serious problem. +Nowadays, new fonts are seldom developed by industrious people using +\mf{}, but if such do appear, they will nowadays be distributed in +the same way as any other part of \alltex{} collections. (An +historical review of Metafont fonts available is held on \acro{CTAN} +as ``\mf{} font list''.) Nowadays, most new fonts that appear are +only available in some scalable outline form, and a large proportion +is distributed under commercial terms. + +Such fonts often make their way to the free distributions (at least +\texlive{} and \miktex{}) if their licensing is such that the +distributions can accept them. Commercial fonts do not get to +distributions, though support for some of them is held by \acro{CTAN}. + +Arranging for a new font to be usable by \alltex{} is very different, +depending on which type of font it is, and which \tex{}-alike engine +you are using; roughly speaking: +\begin{itemize} +\item MetaFont fonts will work without much fuss (provided their + sources are in the correct place in the installation's tree); + \tex{}-with-\ProgName{dvips}, and \pdftex{} are ``happy'' with them. +\item Adobe Type 1 fonts can be made to work, after \extension{tfm} + and (usually) \extension{vf} files have been created from their + metric (\extension{afm}) files. +\item TrueType fonts can be made to work with \pdftex{}, using the + techniques discussed in ANSWER TO BE WRITTEN +\item TrueType and OpenType fonts are the usual sort used by \xetex{} + and \luatex{}; they ``just work'' with those engines. +\end{itemize} The answer ``\Qref*{choice of scalable fonts}{Q-psfchoice}'' discusses fonts that are configured for general (both textual and mathematical) use with \AllTeX{}. The list of such fonts is sufficiently short that -they \emph{can} all be discussed in one answer here. +they \emph{can} all be discussed in one answer. \begin{ctanrefs} \item[\nothtml{\rmfamily}\MF{} font list]\CTANref{mf-list} \end{ctanrefs} +\LastEdit{2012-03-27} \Question[Q-CD]{The \TeX{} collection} 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 9e063a72408..363d9e6ec3e 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.20 2011/06/03 18:01:31 rf10 Exp rf10 $ +% $Id: faq-graphics.tex,v 1.23 2012/03/16 23:01:22 rf10 Exp rf10 $ \section{Graphics} @@ -702,11 +702,13 @@ importing graphics created externally), ranging from simple use of sophisticated (but slow) drawing with \PiCTeX{}. Depending on your type of drawing, and setup, here are a few systems you may consider: \begin{itemize} -\item \PiCTeX{} is a venerable, and very powerful, system, that draws - by placing dots on the page to give the effect of a line or curve. While - this has the potential of great power, it is (of course) much slower - than any of the other established packages. What's more, there - are problems with its \Qref*{documentation}{Q-docpictex}. +\item The \environment{picture} environment provides rather primitive + drawing capabilities (anything requiring more than linear + calculations is excluded, unless a font can come to your help). The + environment's tedious insistence on its own \csx{unitlength}, as the + basic measurement in a diagram, may be avoided by use of the + \Package{picture} package, which detects whether a length is quoted + as a number or as a length, and acts accordingly. \item \Package{epic} was designed to make use of the \LaTeX{} \environment{picture} environment somewhat less agonising; \Package{eepic} extends it, and is capable of using \ProgName{tpic} @@ -722,6 +724,11 @@ of drawing, and setup, here are a few systems you may consider: useful tool than the original environment has ever been. (Note that \Package{pict2e} supersedes David Carlisle's stop-gap \Package{pspicture}.) +\item \PiCTeX{} is a venerable, and very powerful, system, that draws + by placing dots on the page to give the effect of a line or curve. While + this has the potential of great power, it is (of course) much slower + than any of the other established packages. What's more, there + are problems with its \Qref*{documentation}{Q-docpictex}. \item \Package{PSTricks}; this gives you access to all the power of \PS{} from \TeX{} itself, by sophisticated use of \Qref*{\csx{special} commands}{Q-specials}. Since \PS{} is itself a @@ -797,6 +804,7 @@ see \Qref{question}{Q-inlgrphapp}. \item[pgf.sty]\CTANref{pgf} \item[pict2e.sty]\CTANref{pict2e} \item[pictex.sty]\CTANref{pictex} +\item[picture.sty]Distributed as part of \CTANref{oberdiek}[picture] \item[pstricks]\CTANref{pstricks} \item[tikz.sty]Distributed as part of \CTANref{pgf} \end{ctanrefs} @@ -896,16 +904,19 @@ drawing or graphing tools that can do such things (the honourable exception being \MP{}, which allows you to program the labels, in \AllTeX{}, in the middle of specifying your graphic). -Labels on graphics produced by all those \emph{other} tools is where -the \Package{psfrag} package can help. Place an unique +Placing labels on graphics produced by all those \emph{other} tools is +what we discuss here. + +The time-honoured \Package{psfrag} package can help, if your image is +included as an (encapsulated) \PS{} file. Place an unique text in your graphic, using the normal text features of your tool, and you can ask \Package{psfrag} to replace the text with arbitrary \AllTeX{} material. \Package{Psfrag}'s ``operative'' command is -\cmdinvoke{psfrag}{\emph{PS text}}{\emph{Repl text}}, which instructs -the system to replace the original (``\texttt{PS}'') text with the -\TeX{}-typeset replacement text. Optional -arguments permit adjustment of position, scale and rotation; full -details may be found in \File{pfgguide} in the distribution. +\cmdinvoke{psfrag}{\emph{Orig text}}{\emph{Repl text}}, which +instructs the system to replace the original (``unique'') text with +the \TeX{}-typeset replacement text. Optional arguments permit +adjustment of position, scale and rotation; full details may be found +in \File{pfgguide} in the distribution. Since \Package{psfrag} works in terms of (encapsulated) \PS{} files, it needs extra work for use with \PDFLaTeX{}. The % ! line break @@ -914,15 +925,9 @@ usage. In fact, the \Package{pst-pdf} support package \Package{auto-pst-pdf} offers a configuration setting precisely for use with \Package{psfrag}. -On the other hand, -\begin{narrowversion} - V\TeX{}'s GeX processor (\Qref{}{Q-commercial}) -\end{narrowversion} -\begin{wideversion} - \Qref*{V\TeX{}}{Q-commercial}'s GeX processor -\end{wideversion} -explicitly deals with \Package{psfrag}, both in its free and -commercial instances. +On the other hand, % ! line break +\Qref*{V\TeX{}'s GeX processor}{Q-commercial} explicitly deals with +\Package{psfrag}, both in its free and commercial instances. The \Package{psfragx} package goes one step further than \Package{psfrag}: it provides a means whereby you can put the @@ -953,8 +958,15 @@ graphic for you): within the environment you may use the command \csx{lbl} to position \latex{} material at appropriate places over the graphic. +\Package{Pinlabel} is another package whose author thought in the same +sort of way as that of \Package{overpic}; the documentation explains +in detail how to plan your `labelling attack'~--- in this case by +loading your figure into a viewer and taking measurements from it. +(The package discusses direct use of \ProgName{ghostscript} as well as +customised viewers such as \ProgName{gsview} or \ProgName{gv}.) + \Package{Pstricks} can of course do everything -that \Package{overpic} or \Package{lpic} +that \Package{overpic}, \Package{lpic} or \Package{pinlabel} can, with all the flexibility of \PS{} programming that it offers. This capability is exemplified by the \Package{pst-layout} package, which seems to be a superset of both \Package{overpic} and @@ -975,15 +987,19 @@ are plainly little more than a convenience over what is achievable with the do-it-yourself approach. \begin{ctanrefs} \item[auto-pst-pdf.sty]\CTANref{auto-pst-pdf} -\item[pgf.sty]\CTANref{pgf} +\item[ghostscript]\CTANref{ghostscript} +\item[gsview]\CTANref{gsview} +\item[gv]\CTANref{gv} \item[iTe]\CTANref{ite} \item[laprint]Distributed with \CTANref{psfragx} \item[lpic.sty]\CTANref{lpic} \item[overpic.sty]\CTANref{overpic} +\item[pinlabel.sty]\CTANref{pinlabel} +\item[pgf.sty]\CTANref{pgf} \item[psfrag.sty]\CTANref{psfrag} \item[psfragx.sty]\CTANref{psfragx} \item[pstricks.sty]\CTANref{pstricks} \item[pst-layout.sty]\CTANref{pst-layout} \item[pst-pdf.sty]\CTANref{pst-pdf} \end{ctanrefs} -\LastEdit{2011-06-02} +\LastEdit{2012-03-16} 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 bcac3f260d8..a10e82d6899 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.34 2011/09/03 18:56:20 rf10 Exp rf10 $ +% $Id: faq-how-do-i.tex,v 1.37 2012/02/07 21:46:08 rf10 Exp $ \section{How do I do\dots{}?} @@ -1610,8 +1610,9 @@ in the neighbourhood of list environments (unless you change your \end{narrowversion} The syntax of the \environment{wraptable} environment is similar. - Height can be omitted, in which case it will be calculated by the - package; the package will use the greater of the specified and the + The \emph{\texttt{height}} may be omitted, in which case it will + be calculated from the size of the figure; the package will use + the greater of the specified and the actual width. The \texttt{\{l,r,\emph{etc}.\}} parameter may also be specified as \texttt{i}\emph{(nside)} or \texttt{o}\emph{(utside)} for two-sided documents, and uppercase @@ -1706,32 +1707,21 @@ x y However, this doesn't satisfy everyone: many want the labelling in a single cell at the top left of the table. It sounds a simple enough requirement, yet it calls for some slightly tricky \LaTeX{} coding. -The \Package{slashbox} package does the job for you: it defines -commands \csx{slashbox} and \csx{backslashbox}, each taking the two -labels as arguments. It draws a picture with the two labels on either -side of a slanting line; the command (and hence the picture) may be -placed in the corner cell, where the labelled row and column meet. - -The package isn't the world's neatest: it uses \LaTeX{} -\environment{picture} mode to draw its line, and picture mode has many -tedious restrictions (and doesn't, in all honesty, produce -particularly good pictures). Load slashbox with the \Package{pict2e} -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, 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.) +The \Package{diagbox} package does this job for you: it defines a +command \csx{diagbox} whose two arguments provide the texts to be +used; an optional argument may be used for fine tuning of the result. +It draws a picture with the two labels on either side of a slanting +line; the command (and hence the picture) may be placed in the corner +cell, where the labelled row and column meet. + +The \Package{diagbox} package supersedes \Package{slashbox}; the older +package's commands \csx{slashbox} and \csx{backslashbox} are provided +in a compatible way in the newer package, to ease transition. \begin{ctanrefs} -\item[pict2e.sty]\CTANref{pict2e} +\item[diagbox.sty]\CTANref{diagbox} \item[slashbox.sty]\CTANref{slashbox} \end{ctanrefs} -\LastEdit{2010-11-02} +\LastEdit{2010-11-22} \Question[Q-wholerow]{How to change a whole row of a table} @@ -2335,6 +2325,8 @@ advice, you can: tools distribution; they're noticeably less efficient than the standard \environment{tabular} environment, but they do allow footnotes. +\item Use \Package{tablefootnote}; it provides a \csx{tablefootnote}, + which does the job without fuss. \item Use \Package{footnote}, which provides an \environment{savenotes} which collects all footnotes and emits them at the end of the environment; thus if you put your @@ -2357,10 +2349,12 @@ recommend any of them, believing that table notes are the way to go\dots{} \item[footnote.sty]Distributed as part of \CTANref{mdwtools}[footnote] \item[longtable.sty]Distributed as part of \CTANref{2etools}[longtable] \item[mdwtab.sty]Distributed as part of \CTANref{mdwtools}[mdwtab] +\item[tablefootnote.sty]\CTANref{tablefootnote} \item[threeparttable.sty]\CTANref{threeparttable} \item[threeparttablex.sty]\CTANref{threeparttablex} \item[tabularx.sty]Distributed as part of \CTANref{2etools}[tabularx] \end{ctanrefs} +\LastEdit{2012-02-07} \Question[Q-ftnsect]{Footnotes in \LaTeX{} section headings} @@ -2821,8 +2815,15 @@ archive (e.g., \extension{tar.gz} or \extension{zip}) of the files needed by you document; it comes with configuration files for use with \ProgName{teTeX} and \ProgName{\miktex{}}. It's plainly useful when you're sending the first copy of a document. + +The \ProgName{mkjobtexmf} finds which files are used in a `job', +either via the \texttt{-recorder} option of \tex{}, or by using the +(Unix) command \ProgName{strace} to keep an eye on what \tex{} is +doing. The files thus found are copied (or linked) to a directory +which may then be saved for transmission or archiving. \begin{ctanrefs} \item[bundledoc]\CTANref{bundledoc} +\item[mkjobtexmf]\CTANref{mkjobtexmf} \item[snapshot.sty]\CTANref{snapshot} \end{ctanrefs} @@ -3188,8 +3189,8 @@ following minimal solution: \begin{wideversion} \begin{verbatim} \def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}} -\RCS$Revision: 1.34 $ % or any RCS keyword -\RCS$Date: 2011/09/03 18:56:20 $ +\RCS$Revision: 1.37 $ % or any RCS keyword +\RCS$Date: 2012/02/07 21:46:08 $ ... \date{Revision \RCSRevision, \RCSDate} \end{verbatim} @@ -3199,8 +3200,8 @@ following minimal solution: \def\RCS$#1: #2 ${\expandafter \def\csname RCS#1\endcsname{#2}% } -\RCS$Revision: 1.34 $ % or any RCS keyword -\RCS$Date: 2011/09/03 18:56:20 $ +\RCS$Revision: 1.37 $ % or any RCS keyword +\RCS$Date: 2012/02/07 21:46:08 $ ... \date{Revision \RCSRevision, \RCSDate} \end{verbatim} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-hyp+pdf.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-hyp+pdf.tex index 3c54be82162..546ed139c74 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-hyp+pdf.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-hyp+pdf.tex @@ -1,83 +1,34 @@ -% $Id: faq-hyp+pdf.tex,v 1.3 2011/03/08 20:08:01 rf10 Exp rf10 $ +% $Id: faq-hyp+pdf.tex,v 1.5 2011/12/24 23:13:57 rf10 Exp rf10 $ \section{Hypertext and \acro{PDF}} -\Question[Q-hyper]{Making hypertext documents from \TeX{}} - -If you want on-line hypertext with a \AllTeX{} source, probably on the -World Wide Web, there are four technologies to consider: -\begin{itemize} -\item Direct \Qref{\AllTeX{} conversion to \acro{HTML}}{Q-LaTeX2HTML}; -% beware line break -\item Use \Qref*{\Package{Texinfo}}{Q-texinfo}, - and use the \ProgName{info} viewer, or convert the \Package{texinfo} - to \acro{HTML}; -\item Use Adobe Acrobat, which will preserve your typesetting - perfectly - \Qref*{Making Acrobat \acro{PDF} documents from \LaTeX{}}{Q-acrobat}; -\item The hyper\TeX{} conventions (standardised \csx{special} - commands); there are supporting macro packages for \plaintex{} and - \LaTeX{}). -\end{itemize} - -The Hyper\TeX{} project extended the functionality of all the -\LaTeX{} cross-referencing commands (including the table of contents) -to produce \csx{special} commands which are parsed by \acro{DVI} processors -conforming to the Hyper\TeX{} guidelines; -it provides general hypertext links, including those -to external documents. - -The Hyper\TeX{} specification says that conformant viewers/translators -must recognize the following set of \csx{special} commands: -\begin{description} -\item[href:] |html:<a href = "href_string">| -\item[name:] |html:<a name = "name_string">| -\item[end:] |html:</a>| -\item[image:] |html:<img src = "href_string">| -\item[base\_name:] |html:<base href = "href_string">| -\end{description} - -The \emph{href}, \emph{name} and \emph{end} commands are used to do -the basic hypertext operations of establishing links between sections -of documents. - -Further details are available on \URL{http://arXiv.org/hypertex/}; there -are two commonly-used implementations of the specification, a -modified \ProgName{xdvi} and (recent releases of) -\ProgName{dvips}. Output from the latter may be used in recent -releases of \ProgName{ghostscript} or Acrobat Distiller. - -\Question[Q-acrobat]{Making Acrobat \acro{PDF} documents from \AllTeX{}} +\Question[Q-acrobat]{Making \acro{PDF} documents from \AllTeX{}} There are three general routes to \acro{PDF} output: Adobe's original -`distillation' route (via \PS{} output), conversion of a -\acro{DVI} file, and the use of a direct \acro{PDF} generator such as -\Qref*{\PDFTeX{}}{Q-whatpdftex}) or -MicroPress's V\TeX{} (which comes both as a % ! line break -\Qref*{commercial version}{Q-commercial} for Windows PCs, and as a -\Qref*{`free' version)}{Q-TeXsystems} for \acro{OS}/2 and Linux systems). +`distillation' route (via \PS{} output), direct conversion of a +\acro{DVI} file, and the use of a direct \tex{}-like \acro{PDF} +generator such as \Qref*{\PDFTeX{}}{Q-whatpdftex}. For simple documents (with no hyper-references), you can either \begin{itemize} \item process the document in the normal way, produce \PS{} output and distill it; -\item (on a Windows or Macintosh machine with the appropriate Adobe - tools installed) pass the output through the - \acro{PDF}writer in place of a printer driver (this route is a dead - end: the \acro{PDF}writer cannot create hyperlinks); -\item process the document in the normal way and generate \acro{PDF} - direct from the \acro{DVI} using - \ProgName{dvipdfm}/\ProgName{dvipdfmx}; or -\item process the document direct to \acro{PDF} with \PDFTeX{} or - V\TeX{}. \PDFTeX{} has - the advantage of availability for a wide range of platforms, V\TeX{} - (available commercially for Windows, or free of charge, but - unsupported, for Linux or \acro{OS/}2) has wider graphics - capability, dealing with encapsulated \PS{} and some in-line \PS{}. +\item (on a Windows or Macintosh machine with appropriate + tools installed) pass the output through a \acro{PDF}writer in place + of a printer driver. This route is only appropriate for simple + documents: \acro{PDF} writers cannot create hyperlinks; +\item process the document with ``vanilla'' \latex{} and generate \acro{PDF} + direct from the \acro{DVI} using \ProgName{dvipdfm}/\ProgName{dvipdfmx}; or +\item process the document direct to \acro{PDF} with \PDFTeX{}, + \Qref{\luatex{}}{Q-luatex}, \Qref{\xetex{}}{Q-xetex} or V\TeX{}. + \PDFTeX{}, \luatex{} and \xetex{} have the advantage of availability + for a wide range of platforms, but V\TeX{} is available only for + Windows (as a commercial product), or free of charge, but + unsupported, for Linux or \acro{OS/}2. \end{itemize} To translate all the \LaTeX{} cross-referencing into Acrobat -links, you need a \LaTeX{} package to suitably redefine +links, you need a \LaTeX{} package to redefine the internal commands. There are two of these for \LaTeX{}, both capable of conforming to the \Qref{Hyper\TeX{} specification}{Q-hyper}: @@ -93,7 +44,7 @@ Both \ProgName{dvips} and \YandY{}'s \acro{\ProgName{DVIPSONE}} can translate the \acro{DVI} with these \csx{special} commands into \PS{} acceptable to Distiller, and \ProgName{dvipdfm} and \ProgName{dvipdfmx} have \csx{special} commands of -its own. +their own. If you use \plaintex{}, the \Qref*{\Eplain{} macros}{Q-eplain} can help you create \acro{PDF} documents with hyper-references. @@ -121,8 +72,7 @@ cycle of ``Edit\arrowhyph{}Process\arrowhyph{}Preview'' become rather clumsy~--- \ProgName{GSview} doesn't make the same mistake. \begin{ctanrefs} -\item[\nothtml{\rmfamily}Acrobat Reader]browse - \URL{ftp://ftp.adobe.com/pub/adobe/acrobatreader} +\item[\nothtml{\rmfamily}Acrobat Reader]download from \URL{http://get.adobe.com/reader} \item[dvipdfm]\CTANref{dvipdfm} \item[dvipdfmx]\CTANref{dvipdfmx} \item[ghostscript]Browse \CTANref{ghostscript} @@ -131,6 +81,58 @@ mistake. \item[hyper.sty]\CTANref{hyper} \item[hyperref.sty]\CTANref{hyperref} \end{ctanrefs} +\LastEdit{2012-03-28} + +\Question[Q-hyper]{Making hypertext documents from \TeX{}} + +If you want on-line hypertext with a \AllTeX{} source, probably on the +World Wide Web, there are four technologies to consider: +\begin{itemize} +\item start from \alltex{}, and use one of a number of techniques to + translate (more or less) directly to + \Qref{\acro{HTML}}{Q-LaTeX2HTML}; +% beware line break +\item Start from \Qref*{\Package{texinfo}}{Q-texinfo} source, + and use the \ProgName{info} viewer, or convert the \Package{texinfo} + source to \acro{HTML} using \ProgName{texi2html}; +\item Start from \alltex{}; use \pdftex{}, \xetex{} or \luatex{} to + produce \acro{PDF}, using \Package{hyperref} to construct + hyperlinks. +\item Start from (unconventional) \alltex{} which use the % ! line break + \Qref*{hyper\TeX{} conventions}{Q-hypertex}. +\end{itemize} +\begin{ctanrefs} +\item[texinfo]\CTANref{texinfo} +\end{ctanrefs} + +\Question[Q-hypertex]{The \emph{hyper\tex{}} project} + +The \emph{hyper\tex{}} project extended the functionality of all the +\LaTeX{} cross-referencing commands (including the table of contents) +to produce \csx{special} commands which are parsed by \acro{DVI} processors +conforming to the Hyper\TeX{} guidelines; +it provides general hypertext links, including those +to external documents. + +The Hyper\TeX{} specification says that conformant viewers/translators +must recognize the following set of \csx{special} commands: +\begin{description} +\item[href:] |html:<a href = "href_string">| +\item[name:] |html:<a name = "name_string">| +\item[end:] |html:</a>| +\item[image:] |html:<img src = "href_string">| +\item[base\_name:] |html:<base href = "href_string">| +\end{description} + +The \emph{href}, \emph{name} and \emph{end} commands are used to do +the basic hypertext operations of establishing links between sections +of documents. + +Further details are available on \URL{http://arXiv.org/hypertex/}; there +are two commonly-used implementations of the specification, a +modified \ProgName{xdvi} and (recent releases of) +\ProgName{dvips}. Output from the latter may be used in recent +releases of \ProgName{ghostscript} or Acrobat Distiller. \Question[Q-dvips-pdf]{Quality of \acro{PDF} from \PS{}} \keywords{blurry fuzzy crippled} @@ -177,6 +179,7 @@ Shell's \Package{testflow} package, which these FAQs recommend as a \item[testflow]\CTANref{testflow} \end{ctanrefs} + \Question[Q-fuzzy-type3]{The wrong type of fonts in \acro{PDF}} \keywords{crippled blurry} @@ -187,11 +190,12 @@ Most people use \ProgName{Adobe} \ProgName{Acrobat} \ProgName{Reader} to view their \acro{PDF}: \ProgName{Reader} is distributed free of charge, and is widely available, for all its faults. One of those faults is its failure to deal with bitmap fonts (at least, in all -versions earlier than the recently released version~6). +versions earlier than version~6, all of which copies are pretty old, +now~\dots{} but some are occasionally found). So we don't want bitmap fonts in our \PS{}: with them, characters show up in \ProgName{Reader}'s display as blurred blobs which are often not -recognisable as the original letter, and are often not properly placed +even recognisable as the original letter, and are often not properly placed on the line. Nevertheless, even now, most \TeX{} systems have \ProgName{dvips} configured to use \Qref*{\extension{pk} files}{Q-pk} in its output. Even @@ -257,6 +261,7 @@ configuration file either; however, it might have the configuration file without the fonts. In either case, you need to \Qref*{install the fonts}{Q-inst1cm}. + \Question[Q-fuzzy-gs]{Fuzzy fonts because \ProgName{Ghostscript} too old} \keywords{crippled blurry} @@ -573,3 +578,33 @@ are not amenable to this treatment. \item[cm-super \nothtml{\rmfamily}fonts]\CTANref{cm-super} \end{ctanrefs} +% \Question[Q-hypertex]{The Hyper\tex{} project} +% +% The Hyper\TeX{} project extended the functionality of all the +% \LaTeX{} cross-referencing commands (including the table of contents) +% to produce \csx{special} commands which are parsed by \acro{DVI} processors +% conforming to the Hyper\TeX{} guidelines; +% it provides general hypertext links, including those +% to external documents. +% +% The Hyper\TeX{} specification says that conformant viewers/translators +% must recognize the following set of \csx{special} commands: +% \begin{description} +% \item[href:] |html:<a href = "href_string">| +% \item[name:] |html:<a name = "name_string">| +% \item[end:] |html:</a>| +% \item[image:] |html:<img src = "href_string">| +% \item[base\_name:] |html:<base href = "href_string">| +% \end{description} +% +% The \emph{href}, \emph{name} and \emph{end} commands are used to do +% the basic hypertext operations of establishing links between sections +% of documents. +% +% Further details are available on \URL{http://arXiv.org/hypertex/}; there +% are two commonly-used implementations of the specification, a +% modified \ProgName{xdvi} and (recent releases of) +% \ProgName{dvips}. Output from the latter may be used in recent +% releases of \ProgName{ghostscript} or Acrobat Distiller. + + diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-images.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-images.tex new file mode 100644 index 00000000000..714c628f0af --- /dev/null +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-images.tex @@ -0,0 +1,25 @@ +\documentclass[a4paper,12pt]{article} +\usepackage[active,tightpage]{preview} +\begin{document} +\large + +% image 1: wobbly subscript +\begin{preview} + $ X^{1}_{2} X_{2} $ +\end{preview} + +% image 2: even subscript pushed down by null superscript +\begin{preview} + $ X^{1}_{2} X^{}_{2} $ +\end{preview} + +% image 3: simple use of maths: +\begin{preview} + \texttt{fi}\ensuremath\Rightarrow``fi'' +\end{preview} +\end{document} + +%%% Local Variables: +%%% mode: latex +%%% TeX-master: t +%%% End: 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 e16460a7cb3..b65ecb06130 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.14 2011/04/13 09:45:46 rf10 Exp $ +% $Id: faq-install.tex,v 1.16 2012/02/08 21:59:32 rf10 Exp rf10 $ \section{Installing \AllTeX{} files} @@ -27,17 +27,20 @@ decided what it is that you want to install: How did you learn about the package? If the information came from these \acro{FAQ}s, you should already -have a link to the file (there are lists at the end of each answer): +have a link to the file (there are lists of packages at the end of +each answer). \begin{narrowversion} - make a browser link from \URL{http://mirror.ctan.org/} and the text - in the list; if the link returns a directory listing, you can + Make a browser link from \URL{http://mirror.ctan.org/} and the text + in the package list; if the link returns a directory listing, you can generally retrieve the whole directory by appending the link with - \extension{zip} + \extension{zip}~--- so, for example + \URL{http://mirror.ctan.org/macros/latex/doc.zip} for the \latex{} + documentation directory. \end{narrowversion} \begin{wideversion} - click on one of the links associated with the package, and you can + Click on one of the links associated with the package, and you can get the package (which may be one file or several). -% need searate wording for pdfversion and htmlversion, here +% need separate wording for pdfversion and htmlversion, here \end{wideversion} If you heard about the file somewhere else, it's possible that the @@ -52,10 +55,10 @@ very simplest will actually offer just \File{package.sty}~--- in this case, just download the file and % ! line break \Qref*{get on with installation}{Q-inst-wlcf}. -Normally, though, you will want \File{foo.sty} but that file is distributed -in a \LaTeX{} documented source file \File{foo.dtx}; thus you should -search just for \emph{foo}~--- \File{foo.sty} won't be visible -anywhere on the archive or in the catalogue. +You will regularly find that the file you want (e.g., \File{foo.sty}) +is distributed in a \LaTeX{} documented source file \File{foo.dtx}; +thus you should search just for \emph{foo}~--- \File{foo.sty} won't be +visible anywhere on the archive or in the catalogue. Since most packages are distributed in this \extension{dtx}/\extension{ins} way, they usually occupy their own @@ -197,7 +200,8 @@ On a Unix(-alike) system, using te\TeX{} or \texlive{}, the root directory will be named something like \path{/usr/share/texmf-local/} or \path{/usr/local/share/texmf/} You can ask such a system where it believes a local tree should be: -\begin{quote} +\begin{quote} + \begin{verbatim} kpsewhich -var-value TEXMFLOCAL \end{verbatim} @@ -500,7 +504,7 @@ last being easy (unless it is forgotten!). Ready-built \acro{ZIP} files~--- also known as % ! line break \Qref*{\acro{TDS}-\acro{ZIP} files}{Q-tds-zip}~--- are designed to lighten the load of performing the first two steps of installation: they -contain all the files that are that's to be installed for a given +contain all the files that are to be installed for a given package, in their ``correct'' locations in a % ! line break \Qref*{\acro{TDS} tree}{Q-tds}. @@ -525,6 +529,7 @@ remaining chore is to update the file indexes~--- as in % ! line break the package provides a font, you also need to enable the font's map, which is discussed in % ! line break ``\Qref*{Installing a Type~1 font}{Q-instt1font}'' +\LastEdit{2012-02-08} \Question[Q-tempinst]{``Temporary'' installation of \AllTeX{} files} @@ -770,7 +775,7 @@ Other answers discuss specific font families~--- for example, \Question[Q-instmffont]{Installing a font provided as \MF{} source} -Metafont fonts are (by comparison with other sorts of font) rather +Installing Metafont fonts is (by comparison with other sorts of font) rather pleasingly simple. Nowadays, they are mostly distributed just as the \MF{} source, since modern \TeX{} distributions are able to produce everything the user needs ``on the fly''; however, if the distribution @@ -787,9 +792,10 @@ specifies where the files should go. Further confusion is introduced by font families whose authors devise rules for automatic generation of \MF{} sources for generating fonts at particular sizes; the installation has to know about the rules, as -otherwise it cannot generate font files. +otherwise it cannot generate font files. No general advice is +available, but most such font families are now obsolescent. -\Question[Q-instprinterfont]{Installing a \PS{} printer built-in font} +\Question[Q-instprinterfont]{`Installing' a \PS{} printer built-in font} There is a ``standard'' set of fonts that has appeared in every \PS{} printer since the second generation of the type. These fonts 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 fdf37f9f92f..cf710945e00 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.25 2011/10/12 21:58:46 rf10 Exp rf10 $ +% $Id: faq-intro.tex,v 1.29 2012/02/07 21:46:08 rf10 Exp $ % this environment is for the benefit of new-style file generation \begin{introduction} @@ -86,7 +86,9 @@ remains. \htmlignore The following people (at least~--- there are almost certainly others whose names weren't correctly recorded) have contributed help or -advice on the development of the \acro{FAQ}: Donald Arseneau, +advice on the development of the \acro{FAQ}: +William Adams, % spotting dead url +Donald Arseneau, % indefatigable Rosemary Bailey, % lots of initial set of maths answers Barbara Beeton, % one of first reviewers outside cttee Karl Berry, % often provides comments & suggestions @@ -97,7 +99,7 @@ Damian Cugley, Michael Dewey, Michael Downes, % (RIP) on (ams)maths stuff Jean-Pierre Drucbert, % corrected my interpretation of minitoc -David Epstein, % comment on q-algorithms +David Epstein, % comment on q-algorithms, suggestion of tex-sx Michael Ernst, % alert on confusing colloquialism Thomas Esser, Ulrike Fischer, % spotted boondoggle in q-tabcellalign @@ -106,6 +108,7 @@ Bruno Le Floch, % alert to mess in q-latex3 Anthony Goreham, Norman Gray, Enrico Gregorio, % new definition for q-seccntfmt +Werner Grundlingh, % xparse for *-commands Eitan Gurari, % (RIP) comparative html translators William Hammond, % lots of work on xml-related answers John Hammond, % corrections to q-protect @@ -137,7 +140,7 @@ Daniel Luecking, % typos Aditya Mahajan, % rewrite of q-context Sanjoy Mahajan, Diego Andres Alvarez Marin, % suggestion of lacheck -Andreas Matthias, +Andreas Matthias, % most recently q-isitanum Steve Mayer, % proof reading Brooks Moses, % editorial suggestion Peter Moulder, % improvement of q-widows 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 dad92238703..e7a0a794610 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.12 2011/10/29 07:43:12 rf10 Exp rf10 $ +% $Id: faq-jot-err.tex,v 1.19 2012/02/18 19:28:56 rf10 Exp rf10 $ \section{The joy of \TeX{} errors} @@ -196,6 +196,22 @@ giving us the error message ! Argument of \@caption has an extra }. \end{verbatim} \end{quote} +The similar (but more sensible): +\begin{quote} +\begin{verbatim} +\caption{Energy: \(e=mc^2\)} +\end{verbatim} +\end{quote} +is more tiresome, still: there's no error when you first run the +job~\dots{} but there is on the second pass, when the list of figures +(or tables) is generated, giving: +\begin{quote} +\begin{verbatim} +! LaTeX Error: Bad math environment delimiter. +\end{verbatim} +\end{quote} +in the \csx{listoffigures} processing. + The solution is usually to use a robust command in place of the one you are using, or to force your command to be robust by prefixing it with \csx{protect}, which in the \csx{section} case would show as @@ -212,8 +228,8 @@ with \csx{protect}, which in the \csx{section} case would show as \end{verbatim} \end{wideversion} \end{quote} -In both the \csx{section} case and the \csx{caption} case, you can -separate the moving argument, as in +However, in both the \csx{section} case and the \csx{caption} case, +you can separate the moving argument, as in \cmdinvoke*{section}[moving]{static}; this gives us another standard route~--- simply to omit (or otherwise sanitise) the fragile command in the moving argument. So, one might rewrite the \csx{caption} @@ -221,22 +237,29 @@ example as: \begin{quote} \begin{narrowversion} \begin{verbatim} -\caption[Energy: $E=mc^2$]% - {Energy: \[E=mc^2\]} +\caption[Energy: (Einstein's equation)]% + {Energy: \(E=mc^2\)} \end{verbatim} \end{narrowversion} \begin{wideversion} \begin{verbatim} -\caption[Energy: $E=mc^2$]{Energy: \[E=mc^2\]} +\caption[Energy: (Einstein's equation)]{Energy: \(E=mc^2\)} \end{verbatim} \end{wideversion} \end{quote} -for, after all, even if you want display maths in a caption, you -surely don't want it in the list of figures. +In practice, inserting mathematics in a moving argument has already +been addressed in \latexe{} by the robust command \csx{ensuremath}: +\begin{quote} +\begin{verbatim} +\caption{Energy: \ensuremath{E=mc^2}} +\end{verbatim} +\end{quote} +So: always look for alternatives to the \csx{protect} route. -The case of footnotes is somewhat more complex; -``\Qref[question]{footnotes in \LaTeX{} section headings}{Q-ftnsect}'' +Footnotes can be even more complex; % ! line break +``\Qref*[question]{footnotes in \LaTeX{} section headings}{Q-ftnsect}'' deals specifically with that issue. +\LastEdit{2012-02-09} \Question[Q-semanticnest]{Capacity exceeded [semantic nest\,\dots{}]} @@ -347,7 +370,7 @@ itself. \endhtmlignore all do this, as does \Qref*{MicroPress Inc's V\TeX{}}{Q-commercial}. -One common way to encounter one of these error messages is to have +The commonest way to encounter one of these error messages is to have broken macros of some sort, or incorrect usage of macros (an example is discussed in \Qref[question]{epsf problems}{Q-epsf}). @@ -356,7 +379,7 @@ and when this happens, you've just got to work out a different way of doing things. An example is the % beware line wrap \Qref*{difficulty of loading \PiCTeX{} with \LaTeX{}}{Q-usepictex}. The more modern drawing package, \Package{pgf} with its higher-level -interface \Package{TikZ} is a common problem. +interface \Package{TikZ} is also a common source of such problems. In such cases, it is usually possible to use the \Qref*{\eTeX{}}{Q-etex} extensions (all modern distributions provide @@ -368,18 +391,21 @@ used in building the \eTeX{} Plain format; both files are part of the \eTeX{} distribution and are available in current distributions. It is possible that, even with \Package{etex} loaded, you still find -yourself running out of things. Problems could be caused by packages -that use large numbers of ``inserts'' (combinations of counter, box, -dimension and skip registers, used for storing floats and footnotes). -\Package{Morefloats} does this, of course (naturally enough, +yourself running out of things. Problems can be caused by packages +that use large numbers of ``inserts'' (inserts are combinations of +counter, box, dimension and skip registers, used for storing floats +and footnotes). \Package{Morefloats} does this, of course (naturally enough, allocating new floats), and footnote packages such as -\Package{manyfoot} and \Package{bigfoot} (which uses \Package{manyfoot} -can also give problems. The \Package{etex} allows you to deal with +\Package{manyfoot} and \Package{bigfoot} (which uses \Package{manyfoot}) +can also give problems. The \Package{etex} extensions allow you to deal with these things: the command \cmdinvoke*{reserveinserts}{n} ensures there -is room for \meta{n} more inserts. (Hint: \Package{morefloats} needs -18 inserts, and \Package{manyfoot} seems to be happy with 10 -reserved.) Load \Package{etex} before any others, and reserve the -inserts immediately: +is room for \meta{n} more inserts. Hint: by default +\Package{morefloats} adds 18 inserts (though it can be instructed to +use more), and \Package{manyfoot} seems to be happy with 10 reserved, +but there are `hard' limits that we cannot program around~--- the +discussion of \Qref*{running out of floats}{Q-tmupfl} has more about this. +It is essential that you load \Package{etex} before any other +packages, and reserve any extra inserts immediately: \begin{quote} \begin{verbatim} \documentclass[...]{...} @@ -388,13 +414,18 @@ inserts immediately: \end{verbatim} \end{quote} -Unfortunately, \eTeX{} doesn't help with \csx{read} or \csx{write} -objects (and neither will the \Package{etex} package). +The \eTeX{} extensions don't help with \csx{read} or \csx{write} +objects (and neither will the \Package{etex} package), but the +\Package{morewrites} package can provide the \emph{illusion} of large +numbers of \csx{write} objects. +\begin{ctanrefs} +\item[morewrites.sty]\CTANref{morewrites} +\end{ctanrefs} \Question[Q-epsf]{\texttt{epsf} gives up after a bit} -Some copies of the documentation of \File{epsf.tex} seem to suggest -that the command +Some copies of the documentation of \File{epsf.tex} seemed once to +suggest that the command \begin{verbatim} \input epsf \end{verbatim} @@ -460,6 +491,123 @@ accented-letter commands such as the |\'||e| in |\hyphenation{Ji-m\'||e-nez}| automatically become the single accented character by the time the hyphenation gets to look at it. +\Question[Q-optionclash]{Option clash for package} + +So you've innocently added: +\begin{quote} +\cmdinvoke{usepackage}[draft]{graphics} +\end{quote} +to your document, and \LaTeX{} responds with +\begin{wideversion} +\begin{quote} +\begin{verbatim} +! LaTeX Error: Option clash for package graphics. +\end{verbatim} +\end{quote} +\end{wideversion} +\begin{narrowversion} +\begin{quote} +\begin{verbatim} +! LaTeX Error: Option clash for package + graphics. +\end{verbatim} +\end{quote} +\end{narrowversion} + +The error is a complaint about loading a package % ! line break +\emph{with options}, more than once (\LaTeX{} doesn't actually examine +what options there are: it complains because it can't do anything with +the multiple sets of options). You can load a package +any number of times, with no options, and \LaTeX{} will be happy, but +you may only supply options when you first load the package. + +So perhaps you weren't entirely innocent~--- the error would have +occurred on the second line of: +\begin{quote} +\cmdinvoke{usepackage}[dvips]{graphics}\\ +\cmdinvoke{usepackage}[draft]{graphics} +\end{quote} +which could quite reasonably (and indeed correctly) have been typed: +\begin{quote} +\cmdinvoke{usepackage}[dvips,draft]{graphics} +\end{quote} + +But if you've not made that mistake (even with several lines +separating the \csx{usepackage} commands, it's pretty easy to spot), +the problem could arise from something else loading the package for +you. How do you find the culprit? The "\texttt{h}" response to the +error message tells you which options were loaded each time. +Otherwise, it's down to the log analysis games discussed in % ! line break +``\Qref*{How to approach errors}{Q-erroradvice}''; the trick to remember +is that that the process of loading each file is parenthesised in the +log; so if package \Package{foo} loads \Package{graphics}, the log +will contain something like: +\begin{quote} +\begin{verbatim} +(<path>/foo.sty ... +... +(<path>/graphics.sty ... +...) +... +) +\end{verbatim} +\end{quote} +(the parentheses for \Package{graphics} are completely enclosed in +those for \Package{foo}; the same is of course true if your class +\Class{bar} is the culprit, except that the line will start with the +path to \texttt{bar.cls}). + +If we're dealing with a package that loads the package you are +interested in, you need to ask \LaTeX{} to slip in options when +\Package{foo} loads it. Instead of: +\begin{quote} +\cmdinvoke{usepackage}{foo}\\ +\cmdinvoke{usepackage}[draft]{graphics} +\end{quote} +you would write: +\begin{quote} +\cmdinvoke{PassOptionsToPackage}{draft}{graphics}\\ +\cmdinvoke{usepackage}{foo} +\end{quote} +The command \csx{PassOptionsToPackage} tells \LaTeX{} to behave as if +its options were passed, when it finally loads a package. As you would +expect from its name, \csx{PassOptionsToPackage} can deal with a list +of options, just as you would have in the the options brackets of +\csx{usepackage}. + +More trickily, instead of: +\begin{quote} +\cmdinvoke{documentclass}[...]{bar}\\ +\cmdinvoke{usepackage}[draft]{graphics} +\end{quote} +you would write: +\begin{quote} +\cmdinvoke{PassOptionsToPackage}{draft}{graphics}\\ +\cmdinvoke{documentclass}[...]{bar} +\end{quote} +with \csx{PassOptionsToPackage} \emph{before} the \csx{documentclass} +command. + +However, if the \Package{foo} package or the \Class{bar} class loads +\Package{graphics} with an option of its own that clashes with +what you need in some way, you're stymied. For example: +\begin{quote} +\cmdinvoke{PassOptionsToPackage}{draft}{graphics} +\end{quote} +where the package or class does: +\begin{quote} +\cmdinvoke{usepackage}[final]{graphics} +\end{quote} +sets \pkgoption{final} \emph{after} it's dealt with option you passed to +it, so your \pkgoption{draft} will get forgotten. In extreme cases, +the package might generate an error here (\Package{graphics} doesn't +go in for that kind of thing, and there's no indication that +\pkgoption{draft} has been forgotten). + +In such a case, you have to modify the package or class itself +(subject to the terms of its licence). It may prove useful to contact +the author: she may have a useful alternative to suggest. + \Question[Q-optclash]{Option clash for package} The error message @@ -1897,7 +2045,7 @@ seemingly innocent: produces the error (the same happens with \csx{mbox} in place of \csx{fbox}, or with either of their ``big brothers'', \csx{framebox} and \csx{makebox}). This is because the \environment{alltt} environment -uses a ``trivial'' list, hidden inside their definition. (The +uses a ``trivial'' list, hidden inside its definition. (The \environment{itemize} environment also has this construct inside itself, in fact, so \cmdinvoke{begin}{itemize} won't work inside an \csx{fbox}, either.) The list construct wants to happen between @@ -2057,123 +2205,6 @@ and with that definition, the example will compile succesfully (\Package{hyperref} knows about the macro \csx{space}). \LastEdit*{2009-05-29} -\Question[Q-optionclash]{Option clash for package} - -So you've innocently added: -\begin{quote} -\cmdinvoke{usepackage}[draft]{graphics} -\end{quote} -to your document, and \LaTeX{} responds with -\begin{wideversion} -\begin{quote} -\begin{verbatim} -! LaTeX Error: Option clash for package graphics. -\end{verbatim} -\end{quote} -\end{wideversion} -\begin{narrowversion} -\begin{quote} -\begin{verbatim} -! LaTeX Error: Option clash for package - graphics. -\end{verbatim} -\end{quote} -\end{narrowversion} - -The error is a complaint about loading a package % ! line break -\emph{with options}, more than once (\LaTeX{} doesn't actually examine -what options there are: it complains because it can't do anything with -the multiple sets of options). You can load a package -any number of times, with no options, and \LaTeX{} will be happy, but -you may only supply options when you first load the package. - -So perhaps you weren't entirely innocent~--- the error would have -occurred on the second line of: -\begin{quote} -\cmdinvoke{usepackage}[dvips]{graphics}\\ -\cmdinvoke{usepackage}[draft]{graphics} -\end{quote} -which could quite reasonably (and indeed correctly) have been typed: -\begin{quote} -\cmdinvoke{usepackage}[dvips,draft]{graphics} -\end{quote} - -But if you've not made that mistake (even with several lines -separating the \csx{usepackage} commands, it's pretty easy to spot), -the problem could arise from something else loading the package for -you. How do you find the culprit? The "\texttt{h}" response to the -error message tells you which options were loaded each time. -Otherwise, it's down to the log analysis games discussed in % ! line break -``\Qref*{How to approach errors}{Q-erroradvice}''; the trick to remember -is that that the process of loading each file is parenthesised in the -log; so if package \Package{foo} loads \Package{graphics}, the log -will contain something like: -\begin{quote} -\begin{verbatim} -(<path>/foo.sty ... -... -(<path>/graphics.sty ... -...) -... -) -\end{verbatim} -\end{quote} -(the parentheses for \Package{graphics} are completely enclosed in -those for \Package{foo}; the same is of course true if your class -\Class{bar} is the culprit, except that the line will start with the -path to \texttt{bar.cls}). - -If we're dealing with a package that loads the package you are -interested in, you need to ask \LaTeX{} to slip in options when -\Package{foo} loads it. Instead of: -\begin{quote} -\cmdinvoke{usepackage}{foo}\\ -\cmdinvoke{usepackage}[draft]{graphics} -\end{quote} -you would write: -\begin{quote} -\cmdinvoke{PassOptionsToPackage}{draft}{graphics}\\ -\cmdinvoke{usepackage}{foo} -\end{quote} -The command \csx{PassOptionsToPackage} tells \LaTeX{} to behave as if -its options were passed, when it finally loads a package. As you would -expect from its name, \csx{PassOptionsToPackage} can deal with a list -of options, just as you would have in the the options brackets of -\csx{usepackage}. - -More trickily, instead of: -\begin{quote} -\cmdinvoke{documentclass}[...]{bar}\\ -\cmdinvoke{usepackage}[draft]{graphics} -\end{quote} -you would write: -\begin{quote} -\cmdinvoke{PassOptionsToPackage}{draft}{graphics}\\ -\cmdinvoke{documentclass}[...]{bar} -\end{quote} -with \csx{PassOptionsToPackage} \emph{before} the \csx{documentclass} -command. - -However, if the \Package{foo} package or the \Class{bar} class loads -\Package{graphics} with an option of its own that clashes with -what you need in some way, you're stymied. For example: -\begin{quote} -\cmdinvoke{PassOptionsToPackage}{draft}{graphics} -\end{quote} -where the package or class does: -\begin{quote} -\cmdinvoke{usepackage}[final]{graphics} -\end{quote} -sets \pkgoption{final} \emph{after} it's dealt with option you passed to -it, so your \pkgoption{draft} will get forgotten. In extreme cases, -the package might generate an error here (\Package{graphics} doesn't -go in for that kind of thing, and there's no indication that -\pkgoption{draft} has been forgotten). - -In such a case, you have to modify the package or class itself -(subject to the terms of its licence). It may prove useful to contact -the author: she may have a useful alternative to suggest. - \Question[Q-checksum]{Checksum mismatch in font} When \MF{} generates a font it includes a checksum in the font bitmap @@ -2270,3 +2301,74 @@ documentation on how to do it~--- there are lots of % ! line break \Qref*{free tutorials}{Q-tutorials*} to help you on your way, if you don't have access to a \LaTeX{} manual of any sort. +\Question[Q-includeother]{\latex{} won't include from other directories} + +You wanted to \cmdinvoke{include}{../bar/xyz.tex}, but \latex{} says: +\begin{quote} +\begin{wideversion} +\begin{verbatim} +latex: Not writing to ../bar/xyz.aux (openout_any = p). +! I can't write on file `../bar/xyz.aux'. +\end{verbatim} +\end{wideversion} +\begin{narrowversion} +\begin{verbatim} +LaTeX: Not writing to ../bar/xyz.aux + (openout_any = p). +! I can't write on file `../bar/xyz.aux'. +\end{verbatim} +(The first line of that message is wrapped, here.) +\end{narrowversion} +\end{quote} +The error comes from \tex{}'s protection against writing to +directories that aren't descendents of the one where your document +resides. (The restriction protects against problems arising from +\latex{}ing someone else's malicious, or merely broken, document. If +such a document overwrites something you wanted kept, there is obvious +potential for havoc.) + +Document directory structures that can lead to this problem will look +like the fictional \File{mybook}: +\begin{quote} +\begin{verbatim} +./base/mybook.tex +./preface/Preface.tex +./preface/*** +./chapter1/Intro.tex +... +\end{verbatim} +\end{quote} +With such a structure, any document directory (other than the one +where \File{mybook.tex} lives), seems ``up'' the tree from the +base directory. (References to such files will look like +\cmdinvoke{include}{../preface/Preface}: the ``\texttt{..}'' is the +hint.) + +But why did it want to write at all?~--- % ! line break +``\Qref*{what's going in in my \csx{include}}{Q-include}'' explains +how \csx{include} works, among other things by writing an +\extension{aux} file for every \csx{includ}ed file. + +Solutions to the problem tend to be drastic: +\begin{enumerate} +\item Restructure the directories that hold your document so that the + master file is at the root of the tree: + \begin{quote} +\begin{verbatim} +./mybook.tex +./mybook/preface/Preface.tex +./mybook/preface/*** +./mybook/chapter1/Intro.tex +... +\end{verbatim} + \end{quote} + and so on. +\item Did you actually \emph{need} \csx{include}?~--- if not, you can + replace \csx{include} by \csx{input} throughout. (This only works + if you don't need \csx{includeonly}.) +\item You \emph{could} patch your system's \File{texmf.cnf}~--- if you + know what you're doing, the error message should be enough of a + hint; this action is definitely not recommended, and is left to + those who can ``help themselves'' in this respect. +\end{enumerate} +\LastEdit*{2012-02-13} 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 b71fbaece6d..b6b706555aa 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.25 2011/09/09 19:35:14 rf10 Exp rf10 $ +% $Id: faq-mac-prog.tex,v 1.28 2012/02/18 19:28:56 rf10 Exp rf10 $ \section{Macro programming} @@ -503,19 +503,20 @@ what's left: \begin{narrowversion} \begin{verbatim} \def\testnum#1{\afterassignment\testresult - \count255=#1 \end} + \count255=0#1 \end} \def\testresult#1\end{\ifx\end#1\end} -\def\IsInteger#1{TT\fi \testnum{#1}} \end{verbatim} \end{narrowversion} \begin{wideversion} \begin{verbatim} -\def\testnum#1{\afterassignment\testresult\count255=#1 \end} +\def\testnum#1{\afterassignment\testresult\count255=0#1 \end} \def\testresult#1\end{\ifx\end#1\end\isanumtrue\else\isanumfalse\fi} \end{verbatim} \end{wideversion} \end{quote} -(which technique is due to David Kastrup); this can provoke errors. +(which technique is due to David Kastrup; the trick for avoiding the +errors, noted in an earlier version of this answer, was suggested by +Andreas Matthias). In a later thread on the same topic, Michael Downes offered: \begin{quote} \begin{wideversion} @@ -863,7 +864,7 @@ accurately. \item[keyval.sty]Distributed as part of \CTANref{graphics}[keyval] \end{ctanrefs} - * faq-mac-prog.tex (q-keyval): tweak words about getoptk + * faq-mac-prog.tex (q-keyval): tweak words about getoptk \Question[Q-keyval]{Key-value input for macros and package options} @@ -1508,7 +1509,7 @@ for you. They all create a \tex{} conditional command: 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`\}} + \csx{ifthenelse}\texttt{\obracesymbol{}}\cmdinvoke{boolean}{pdf}\texttt{\cbracesymbol{}}\texttt{\obracesymbol{}}\meta{if pdf}\texttt{\cbracesymbol{}}\texttt{\obracesymbol{}}\meta{if not pdf}\texttt{\cbracesymbol{}} \end{quote} The \Package{ifxetex} package also provides a command @@ -1598,6 +1599,7 @@ output, you also need to know about the value of \csx{pdfoutput}: \CTANref{oberdiek}[ifluatex] \item[ifxetex.sty]\CTANref{ifxetex} \end{ctanrefs} +\LastEdit{2012-02-13} \Question[Q-subverttoks]{Subverting a token register} @@ -2359,10 +2361,49 @@ definition like: \WithSuffix\gdef\mycommand*{starred version} \end{verbatim} \end{quote} + +For those of an adventurous disposition, a further option is to use +the \Package{xparse} package from the \Package{l3packages} +distribution. The package defines a bunch of commands (such as +\csx{NewDocumentCommand}) which are somewhat analagous to +\csx{newcommand} and the like, in \latexe{}. The big difference is +the specification of command arguments; for each argument, you have a +set of choices in the command specification. So, to create a +*-command (in \latexe{} style), one might write: +\begin{quote} +\begin{verbatim} +\NewDocumentCommand \foo { s m } {% + % #1 is the star indicator + % #2 is a mandatory argument + ... +} +\end{verbatim} +\end{quote} +The ``star indicator'' (\texttt{s}) argument appears as \texttt{\#1} +and will take values \csx{BooleanTrue} (if there was a star) or +\csx{BooleanFalse} (otherwise); the other (\texttt{m}) argument is a +normal \tex{}-style mandatory argument, and appears as \texttt{\#2}. + +While \Package{xparse} provides pleasing command argument +specifications, it \emph{is} part of the % ! line break +\Qref*{\latex{}~3 experimental harness}{Q-LaTeX3}, and +simply loading the package ``pulls in'' a large bunch of other package +files via the \Package{expl3} package: these packages provide the rest +of the harness. +% original suggestion was to offer: +% \NewDocumentCommand{\mycommand}{s}{% +% % macro contents where #1 refers to *-variant (true) or not (false) +% \IfBooleanTF{#1}% Condition on * +% {}% TRUE: \mycommand* +% {}% FALSE: \mycommand +% } \begin{ctanrefs} \item[ifthen.sty]Part of the \LaTeX{} distribution \item[suffix.sty]Distributed as part of \CTANref{bigfoot}[suffix] +\item[xparse.sty]Distributed as part of \CTANref{l3packages}[xparse] +\item[expl3.sty]Distributed as part of \CTANref{l3kernel}[expl3] \end{ctanrefs} +\LastEdit{2012-02-07} \nothtml{\hrule height 0pt \nobreak\vskip0pt plus2.5in\vskip 0pt\relax} \Question[Q-ltxabbrv]{\LaTeX{} internal ``abbreviations'', etc.} @@ -2517,7 +2558,7 @@ So, using \Package{printlen}, we could say: \end{quote} and get: \begin{quote} -\verb|\foo| is 12pt +\csx{foo} is 12pt \end{quote} while, if we say: \begin{quote} @@ -2525,17 +2566,17 @@ while, if we say: \newlength{\foo} \setlength{\foo}{12pt} \uselengthunit{mm} -\verb|\foo| is \printlength{\foo} +\verb|foo| is \printlength{\foo} \end{verbatim} \end{quote} we get: \begin{quote} -\verb|\foo| is 4.21747mm +\csx{foo} is 4.21747mm \end{quote} \begin{ctanrefs} \item[printlen.sty]\CTANref{printlen} \end{ctanrefs} -\LastEdit*{2011-09-08} +\LastEdit{2012-03-16} \Question[Q-labelcount]{Using labels as counter values} 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 8cee087f490..d427436dbf7 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.27 2011/10/17 23:24:32 rf10 Exp rf10 $ +% $Id: faq-projects.tex,v 1.28 2012/02/07 21:46:08 rf10 Exp $ \section{Current \TeX{}-related projects} @@ -33,17 +33,18 @@ Some of the project's experimental code is visible on the net: \item from \acro{CTAN}: snapshots of two major collections from the code, \Package{l3kernel} (supporting \LaTeX{}3 coding conventions in a \LaTeXe{} environment), \Package{l3packages} (a first cut of a - ``document designer's interface'') and \Package{l3experimental} (new - stuff that's still under development). + ``document designer's interface'') as well as + \Package{l3experimental} (new stuff that's still under + development). \end{itemize} -Note that \Package{L3kernel} introduces a coding structure quite -different from earlier \latex{} code, but a few authors, who are not -members of the project, are nevertheless using it in their development +The packages \Package{l3kernel} and \Package{l3packages} provide an +``experimental harness'' that may be used as a testbed for \latex{}3 work. -While it is possible to build an experimental \latex{}3 format, it's -not (yet) a usable object; the team use it for debugging purposes, and -any other brave soul may also try it. +Note that \Package{l3kernel} introduces a coding structure quite +different from earlier \latex{} code; a few hardy authors, who are not +members of the project, are nevertheless using it in their development +work. Anyone may participate in discussions of the future of \LaTeX{} through the mailing list \texttt{latex-l}; some development work @@ -56,7 +57,7 @@ to \mailto{listserv@urz.Uni-Heidelberg.de} \item[\nothtml{\rmfamily}\LaTeX{} project publications]\CTANref{ltx3pub} \item[l3packages \nothtml{\rmfamily}bundle]\CTANref{l3packages} \end{ctanrefs} -\LastEdit{2011-10-04} +\LastEdit{2012-02-07} \Question[Q-mathml]{Future \acro{WWW} technologies and \AllTeX{}} @@ -452,18 +453,21 @@ support from various sources) pursuing avenues that many of the other current projects have in their sights, notably Unicode character representations and support for OpenType fonts. The intention is to integrate the extensions pioneered by \Qref*{Aleph}{Q-omegaleph}. +Users may also care to view the % ! line break +\href{http://www.luatex.org/documentation.html}{\luatex{} documentation page} -The current released version (Beta 0.70.1, in June 2011) of \LuaTeX{} +The current released version (0.70.1, in June 2011) of \LuaTeX{} is supposed at least to demonstrate the final functionality. This stability was declared with version 0.50.0, released near the end of December 2009. Much work remains to be done, and this remains a -beta-release. \texlive{} 2010 incorporates (at the time of writing) -\LuaTeX{} version 0.60.2, and current \miktex{} (version 2.9) +beta-release. \texlive{} 2011 incorporates (at the time of writing) +\LuaTeX{} version 0.70.1, and current \miktex{} (version 2.9) offers version 0.70.0. \CONTeXT{} `Mark 4' can already make use of \LuaTeX{}; much of its code already appears in two forms~--- a \TeX{}-based version -(\extension{mkii}) and a `\extension{mkiv}' version, which uses +(\extension{mkii}) and a `\extension{mkiv}' version (new functionality +typically \emph{only} appears in `\extension{mkiv}' form), which uses \luatex{} extensions (including \ProgName{lua} scripting). \LaTeX{} packages that support its use are appearing (some of them providing re-implementations of existing \context{} code). @@ -471,7 +475,7 @@ re-implementations of existing \context{} code). \item[\nothtml{\rmfamily}\luatex{} snapshot]\CTANref{luatex} \item[\nothtml{\rmfamily}\pdftex{} distribution]\CTANref{pdftex} \end{ctanrefs} -\LastEdit{2011-07-10} +\LastEdit{2011-11-02} \Question[Q-ant]{The \textsf{ANT} typesetting system} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex index f12b9a0c254..34f7e5e4be1 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-symbols.tex @@ -1,4 +1,4 @@ -% $Id: faq-symbols.tex,v 1.11 2011/08/28 10:13:19 rf10 Exp rf10 $ +% $Id: faq-symbols.tex,v 1.14 2012/01/16 23:37:15 rf10 Exp rf10 $ \section{Symbols, etc.} @@ -15,7 +15,8 @@ discussed in \begin{wideversion} ``\Qref{symbol already defined}{Q-alreadydef}''. \end{wideversion} -Some font sets (for example, \FontName{MnSymbol}) are huge, and the +Some font sets (for example the related set: \FontName{FdSymbol}, +\FontName{MdSymbol} and \FontName{MnSymbol}) are huge, and the accompanying macros cover so many symbols that name clashes are surely a serious problem. @@ -41,7 +42,9 @@ font family and colour specified in the arguments of clear; it is probably the best tool to use for picking and choosing symbols from a variety of font families. \begin{ctanrefs} -\item[mnsymbol \nothtml{\rmfamily}fonts]\CTANref{mnsymbol} +\item[FdSymbol \nothtml{\rmfamily}fonts]\CTANref{fdsymbol} +\item[MdSymbol \nothtml{\rmfamily}fonts]\CTANref{mdsymbol} +\item[MnSymbol \nothtml{\rmfamily}fonts]\CTANref{mnsymbol} \item[pifont.sty]Distributed as part of \CTANref{psnfss} \item[yagusylo.sty]\CTANref{yagusylo} \end{ctanrefs} @@ -50,10 +53,10 @@ symbols from a variety of font families. Mathematicians commonly use special lettering for the real numbers and other standard number sets. Traditionally these were typeset in bold. -Because, in the ordinary course of events, mathematicians do not have -access to bold chalk, they invented special symbols that are now -often used for the number sets; these symbols are known as -``blackboard bold'' (or double-stroked fonts); in place of the heavier +In the ordinary course of events, mathematicians do not have +access to bold chalk, so they invented special symbols that are now +often used for the number sets. Such symbols are known as +``blackboard bold'' (or double-stroked) letters; in place of the heavier strokes of a bold font, (some) strokes of the letters are doubled. The minimum useful set is upper-case letters `I', `N', `R', `Q' and `Z'; some fonts offer a figure `1' (for a unit matrix~--- not a number @@ -61,13 +64,14 @@ set at all). A set of blackboard bold capitals is available in the \acro{AMS} \FontName{msbm} fonts (\FontName{msbm} is available at a range of -design sizes, with names such as \FontName{msbm10}). The pair of font -families (the other is called \FontName{msam}) have a large number of -mathematical symbols to supplement those provided in the Knuth's -original \TeX{} distribution, and are available in Type~1 format in -modern distributions. Support files for using the fonts, both under -\plaintex{} and \LaTeX{} (packages \Package{amssymb} and -\Package{amsfonts}), are available. The font shape is a rather +design sizes, with names such as \FontName{msbm10}). The \acro{AMS} +actually provides a pair of font +families (the other is called \FontName{msam}), which offer a large number of +mathematical symbols to supplement those provided in Knuth's fonts. +The fonts are available in Type~1 format in +modern distributions. Support for using the fonts under +\LaTeX{} is available in packages \Package{amssymb} and +\Package{amsfonts}. The font shape is a rather austere sans, which many people don't like (though it captures the essence of quickly-chalked writing rather well). @@ -395,7 +399,10 @@ Ordinary people (such as the author of this \acro{FAQ}) need only type The European currency ``Euro'' (\texteuro {}) is represented by a symbol of somewhat dubious design, but it's an important currency and -\AllTeX{} users need to typeset it. +\AllTeX{} users need to typeset it. When the currency first appeared, +typesetting it was a serious problem for \AllTeX{} users; things are +easier now (most fonts have some way of providing a Euro sign), but +this answer provides a summary of methods ``just in case''. Note that the Commission of the European Community at first deemed that the Euro symbol should always be set in a sans-serif font; @@ -470,13 +477,9 @@ providing Euro symbols in a number of shapes. The file Euro symbols are found in several other places, which we list here for completeness. -The \Package{marvosym} fonts contain a Euro symbol among many other -good things. -%% ; the font on \acro{CTAN} is not Adobe \ProgName{ATM} -%% compatible, but a compatible version is available free from -%% \href{http://www.YandY.com/download/marvosym.zip}{\YandY{}}. The font -%% on \acro{CTAN} comes with a set of macros to typeset all the symbols -%% it contains. +The \Package{marvosym} font contains a Euro symbol (in a number of +typographic styles), among many other good things; the font is +available in both Adobe Type 1 and TrueType formats. Other \MF{}-based bundles containing Euro symbols are to be found in \Package{china2e} (whose primary aim is Chinese dates and suchlike @@ -491,6 +494,7 @@ matters) and the \Package{eurosym} fonts. \item[marvosym fonts]\CTANref{marvosym-fonts} \item[textcomp.sty]Part of the \LaTeX{} distribution. \end{ctanrefs} +\LastEdit{2011-11-21} \Question[Q-tradesyms]{How to get copyright, trademark, etc.} 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 ab839983542..ede1f338519 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.12 2011/10/16 22:59:45 rf10 Exp rf10 $ +% $Id: faq-t-g-wr.tex,v 1.13 2012/03/10 13:56:18 rf10 Exp $ \section{Things are Going Wrong\dots{}} @@ -351,9 +351,9 @@ now redesigned the fonts, using the current version of \MF{}, and the new versions are called the \FontName{msa} and \FontName{msb} families. -Nevertheless, \FontName{msx} and \FontName{msy} continue to turn up to -plague us. There are, of course, still sites that haven't got around -to upgrading; but, even if everyone upgraded, there would still be the +Nevertheless, \FontName{msx} and \FontName{msy} continue to turn up. +There may, of course, still be sites that haven't got around to +upgrading; but, even if everyone upgraded, there would still be the problem of old documents that specify them. If you have a \extension{tex} source that requests \FontName{msx} and @@ -361,12 +361,19 @@ If you have a \extension{tex} source that requests \FontName{msx} and \FontName{msa} and \FontName{msb} (you only need to change the single letter in the font names). +A partial re-implementation of the blackboard-bold part of the +\FontName{msy} font (covering C, N, R, S and Z, only) is available in +Type~1 format; if your mathematical needs only extend that far, the +font could be a good choice. + If you have a \acro{DVI} file that requests the fonts, there is a package of \Qref*{virtual fonts}{Q-virtualfonts} to map the old to the new series. \begin{ctanrefs} -\item[msa and msb fonts]Distributed as part of \CTANref{amsfonts} -\item[virtual font set]\CTANref{msx2msa} +\item[msam \& msbm \nothtml{\rmfamily}fonts]Distributed as part of \CTANref{amsfonts} +\item[msym \nothtml{\rmfamily}fonts]\CTANref{msym} +\item[\nothtml{\rmfamily}virtual font set]\CTANref{msx2msa} \end{ctanrefs} +\LastEdit{2012-03-09} %%%???%%% spell-checked to here....zzzyx 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 1922410d2d7..84ebca739df 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.13 2011/10/05 21:46:53 rf10 Exp rf10 $ +% $Id: faq-texsys.tex,v 1.13 2012/03/26 20:15:53 rf10 Exp $ \section{\TeX{} Systems} @@ -38,9 +38,10 @@ The \TeX{} distribution of choice, for Unix systems (including which is distributed as part of the \Qref*{\TeX{} collection}{Q-CD}. \texlive{} may also be installed ``over the network''; a network -installer is provided, and once you have a system (whether network- or -offline-installed) a manager (\ProgName{tlmgr}) can both keep your -installation up-to-date and add packages you didn't install at first. +installer is provided, and once you have a system (whether installed +from the network or installed off-line from a disc) a manager +(\ProgName{tlmgr}) can both keep your installation up-to-date and add +packages you didn't install at first. \texlive{} may be run with no installation at all; the web page % ! line break \href{http://www.tug.org/texlive/portable.html}{\texlive{} portable usage} @@ -81,13 +82,11 @@ the same place. Windows users nowadays have a real choice, between two excellent distributions, \miktex{} and \texlive{}. \texlive{} on windows has only in recent years been a real challenger to the long-established -\miktex{}, and even now \miktex{} has features that \texlive{} lacks, -while \texlive{} offers a \Qref*{\luatex{}}{Q-luatex} implementation, -which \miktex{} lacks (though it is present in \miktex{} 2.9, in -beta-release at the time of writing). Both are comprehensive +\miktex{}, and even now \miktex{} has features that \texlive{} lacks. +Both are comprehensive distributions, offering all the established \tex{} variants (\tex{}, -\pdftex{}~--- both with \etex{} variants~--- and \xetex{}), together -with a wide range of support tools. +\pdftex{}~--- both with \etex{} variants~--- as well as \xetex{} and +\luatex{}), together with a wide range of support tools. Both \miktex{} and \texlive{} offer management tools, including the means of keeping an installation ``up-to-date'', by reinstalling @@ -100,8 +99,8 @@ and has a large audience of satisfied users; \texlive{} is the dominant distribution in use in the world of Unix-like systems, and so its Windows version may be expected to appeal to those who use both Unix-like and Windows systems. The latest release of \miktex{}~--- -version 2.9, still in beta release at the time of writing~--- requires -Windows~XP, or later; it does not work on Windows~2000 or earlier. +version 2.9~--- requires Windows~XP, or later (so it does not work on +Windows~2000 or earlier). Both distributions may be used in a configuration which involves no installation at all. \miktex{}'s ``portable'' distribution may be @@ -172,6 +171,7 @@ comes with a bunch of Type~1 fonts packaged to work with BaKoMa \item[texlive]Browse \CTANref{texlive} \item[texlive installer (Windows)]\CTANref{texlive-windows} \end{ctanrefs} +\LastEdit{2012-03-28} \Question[Q-sysmac]{Macintosh systems} 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 040767dec37..f4a9c08f3e2 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.12 2011/06/01 19:57:21 rf10 Exp rf10 $ +% $Id: faq-wdidt.tex,v 1.17 2012/02/18 19:28:56 rf10 Exp rf10 $ \section{Why does it \emph{do} that?} @@ -40,7 +40,8 @@ whereas, in \end{figure} \end{verbatim} \end{quote} -the label will report the \emph{previous} figure's number, etc. +the label will report the number of the section (or whatever) in which +the surrounding text resides, or the like. You can, with the same malign effect, shield the \csx{caption} command from its associated \csx{label} command, by enclosing the caption in an @@ -55,13 +56,13 @@ environment of its own. This effect will be seen with: \end{verbatim} \end{quote} where the \csx{label} definitely \emph{is} after the \csx{caption}, -but because the \environment{figure} environment closed early, the -\csx{label} can't `see' the \csx{caption}. +but because the \environment{figure} environment closed before the +\csx{label} command, the \csx{caption} is no longer ``visible''. In summary, the \csx{label} must be \emph{after} the command that defines it (e.g., \csx{caption}), and if the \csx{caption} is inside an environment, the \csx{label} must be in there too. -\LastEdit{2011-03-09} +\LastEdit{2012-02-07} \Question[Q-newlineargs]{Start of line goes awry} \keywords{asterisk square bracket start line} @@ -78,13 +79,13 @@ This answer concerns two sorts of problems: errors of the form and those where a single asterisk at the start of a line mysteriously fails to appear in the output. -Both problems arise because |\|{}|\| takes optional arguments. The -command |\|{}|\*| means ``break the line here, and inhibit page break -following the line break''; the command |\|{}|\[|\meta{dimen}|]| +Both problems arise because \texttt{\bsbs } takes optional arguments. The +command \texttt{\bsbs *} means ``break the line here, and inhibit page break +following the line break''; the command \texttt{\bsbs [}\meta{dimen}\texttt{]} means ``break the line here and add \meta{dimen} extra vertical space afterwards''. -So why does |\|{}|\| get confused by these things at the start of a +So why does \texttt{\bsbs } get confused by these things at the start of a line? It's looking for the first non-blank thing, and in the test it uses ignores the end of the line in your input text. @@ -216,6 +217,37 @@ development (though it \emph{does} work in this simple case) and deserves consideration in most cases; the package documentation gives more details. +Another way out is to use one of ``argument types'' of the +\csx{NewDocumentCommand} command in the experimental \latex{}3 package +\Package{xparse}: +\begin{quote} +\begin{verbatim} +\NewDocumentCommand\cmd{ m v m }{#1 `#2' #3} +\cmd{Command }|\furble|{ isn't defined} +\end{verbatim} +\end{quote} +Which gives us: +\begin{quote} + Command \csx{furble} isn't defined +\end{quote} +The ``\texttt{m}'' tag argument specifies a normal mandatory argument, +and the ``\texttt{v}'' specifies one of these verbatim arguments. +As you see, it's implanting a \csx{verb}-style command argument in the +argument sequence of an otherwise ``normal'' sort of command; that +\begin{typesetversion} + `\texttt{\char`\|}' +\end{typesetversion} +\begin{htmlversion} + `\texttt{|}' +\end{htmlversion} +may be any old character that doesn't +conflict with the content of the argument. + +This is pretty neat (even if the verbatim is in an argument of its +own) but the downside is that \Package{xparse} pulls in +\Package{expl3} (the experimental \latex{}3 programming environment) +which is painfully large. + Other than the \Package{cprotect} package, there are three partial solutions to the problem: \begin{itemize} @@ -244,7 +276,7 @@ solutions to the problem: its absence you could simply use \csx{texttt}), consider using \csx{string}. \cmdinvoke{texttt}{my\csx{string}\_name} typesets the same as - |\verb+my_name+|, and will work in the argument of a command. It + \csx{verb+my\_name+}, and will work in the argument of a command. It won't, however, work in a moving argument, and no amount of \Qref*{\csx{protect}ion}{Q-protect} will make it work in such a case. @@ -265,10 +297,14 @@ solutions to the problem: \end{itemize} \begin{ctanrefs} \item[cprotect.sty]\CTANref{cprotect} +\item[expl3.sty]Distributed as part of \CTANref{l3kernel}[expl3] \item[fancyvrb.sty]\CTANref{fancyvrb} \item[memoir.cls]\CTANref{memoir} \item[url.sty]\CTANref{url} \item[verbdef.sty]\CTANref{verbdef} +\item[xparse.sty]Distributed as part of \CTANref{l3packages}[xparse] +\LastEdit{2012-02-13} + \end{ctanrefs} \Question[Q-noline]{No line here to end} @@ -291,7 +327,7 @@ See the LaTeX manual or LaTeX Companion \end{verbatim} \end{narrowversion} \end{quote} -comes in reaction to you giving \LaTeX{} a |\|{}|\| command at a time +comes in reaction to you giving \LaTeX{} a \texttt{\bsbs } command at a time when it's not expecting it. The commonest case is where you've decided you want the label of a list item to be on a line of its own, so you've written (for example): @@ -307,7 +343,7 @@ so you've written (for example): \bsbs {} is actually a rather bad command to use in this case (even if it worked), since it would force the `paragraph' that's made up of the text of the item to terminate a line which has nothing on it but the -label. This would lead to an ``|Underfull \hbox|'' warning message +label. This would lead to an ``\texttt{Underfull }\csx{hbox}'' warning message (usually with `infinite' badness of 10000); while this message doesn't do any actual harm other than slowing down your \LaTeX{} run, any message that doesn't convey any information distracts for no useful @@ -1019,7 +1055,7 @@ reason is that the font you selected just doesn't have a representation for the character in question. For example, if I type ``that will be \pounds{}44.00'' into an ordinary -\AllTeX{} document, or if I select the font |rsfs10| (which contains +\AllTeX{} document, or if I select the font \texttt{rsfs10} (which contains uppercase letters only) and type pretty much anything, the \pounds{} sign, or any lowercase letters or digits will not appear in the output. There's no actual error message, either: you have to read the @@ -1074,7 +1110,7 @@ from the previous run when it started; it does this comparison at Sometimes, the message won't go away: however often you reprocess your document, \LaTeX{} still tells you that ``Label(s) may have changed''. This can sometimes be caused by a broken package: both -\Package{footmisc} (with the |perpage| option) and \Package{hyperref} +\Package{footmisc} (with the \pkgoption{perpage} option) and \Package{hyperref} have been known to give trouble, in the past: if you are using either, check you have the latest version, and upgrade if possible. @@ -1114,7 +1150,7 @@ quickly, and would really rather not type them all. An alternative structure, that doesn't violate the design of \LaTeX{}, is to say \csx{fred}\csx{ }~--- the \csx{ } command is ``self -terminating'' (like |\|{}|\|) and you don't need braces after +terminating'' (like \texttt{\bsbs }) and you don't need braces after \emph{it}. Thus one can reduce to one the extra characters one needs to type. @@ -1217,7 +1253,7 @@ assignment~--- for example \end{verbatim} \end{quote} For both, an ``infinite'' tolerance is represented by the value -|10|\nothtml{\,}|000|, but infinite tolerance is rarely +\texttt{10}\nothtml{\,}\texttt{000}, but infinite tolerance is rarely appropriate, since it can lead to very bad line breaks indeed. \csx{emergencystretch} is a \TeX{}-internal `dimen' register, and can @@ -1238,12 +1274,12 @@ troublesome. In practice, \csx{pretolerance} is rarely used other than to manipulate the use of hyphenation; \plaintex{} and \LaTeX{} both set its value -to |100|. To suppress the first scan of paragraphs, set -\csx{pretolerance} to |-1|. +to \texttt{100}. To suppress the first scan of paragraphs, set +\csx{pretolerance} to \texttt{-1}. \csx{tolerance} is often a good method for adjusting spacing; -\plaintex{} and \LaTeX{} both set its value to |200|. \LaTeX{}'s -\csx{sloppy} command sets it to |9999|, as does the +\plaintex{} and \LaTeX{} both set its value to \texttt{200}. \LaTeX{}'s +\csx{sloppy} command sets it to \texttt{9999}, as does the \environment{sloppypar} environment. This value is the largest available, this side of infinity, and can allow pretty poor-looking breaks (this author rarely uses \csx{sloppy} ``bare'', though he does @@ -1566,9 +1602,9 @@ keyboards have been (or ever will be) manufactured. By contrast, the \Package{fontenc} package generates the \acro{T}1 code points from ordinary \LaTeX{} commands (e.g., it generates the -\texttt{\'e} character codepoint from the command |\'|{}|e|). So, unless you -have program-generated \acro{T}1 input, use -\cmdinvoke{usepackage}[T1]{fontenc} rather than +\texttt{\'e} character codepoint from the command \csx{'}\texttt{e}). +So, unless you have program-generated \acro{T}1 input (which is almost +inconceivable), use \cmdinvoke{usepackage}[T1]{fontenc} rather than \cmdinvoke{usepackage}{t1enc}. \Question[Q-why-inp-font]{Why bother with \Package{inputenc} and \Package{fontenc}?} @@ -1587,13 +1623,13 @@ 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 produce Latin-2, so that the simple mapping doesn't work. \item[Traditional \LaTeX{}] You lapse and write something like - |\'|{}|e| rather than typing \texttt{\'e}; only \Package{fontenc} + \cmdinvoke{'}{e} rather than typing \texttt{\'e}; only \Package{fontenc} has the means to convert this \LaTeX{} sequence into the \acro{T}1 character, so an \csx{accent} primitive slips through into the output, and hyphenation is in danger. @@ -1623,8 +1659,9 @@ associated with real arrays elsewhere in the document. The user is far better served by the \AMSLaTeX{} bundle, which provides an \environment{align} environment, which is designed with the needs of mathematicians in mind (as opposed to the convenience of -\LaTeX{} programmers). For this simple case (align is capable of far -greater things), code as: +\LaTeX{} programmers). For this simple case (\environment{align} and +other \AMSLaTeX{} alignment environments are capable of far greater +things), code as: \begin{quote} \begin{verbatim} \begin{align} @@ -1635,7 +1672,10 @@ greater things), code as: \end{quote} The matter is discussed in more detail in a % ! line break \href{http://tug.org/pracjourn/2006-4/madsen/madsen.pdf}{Prac\TeX{} journal paper} -by Lars Madsen. +by Lars Madsen; Stefan Kottwitz offers a % ! line break +\href{http://texblog.net/latex-archive/maths/eqnarray-align-environment/}{\tex{} blog entry} +which includes screen shots of the output, convincingly demonstrating +the problem. \begin{ctanrefs} \item[AMSLaTeX]\CTANref{amslatex} \end{ctanrefs} @@ -1691,7 +1731,7 @@ At the release of \LaTeXe{} in summer 1994, these simple commands were deprecated, but recognising that their use is deeply embedded in the brains of \LaTeX{} users, the commands themselves remain in \LaTeX{}, \emph{with their \LaTeXo{} semantics}. Those semantics were part of -the reason they were deprecated: each |\|\emph{\texttt{xx}} overrides +the reason they were deprecated: each \csx{\emph{xx}} overrides any other font settings, keeping only the size. So, for example, \begin{quote} \begin{verbatim} @@ -1705,7 +1745,7 @@ italic correction has a real effect), whereas {\it\bf happy as can be\/} \end{verbatim} \end{quote} -ignore \csx{it} and produces upright text at bold weight (and the +ignores \csx{it} and produces upright text at bold weight (and the italic correction has nothing to do). The same holds if you mix \LaTeXe{} font selections with the old style commands: \begin{quote} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq.sty b/Master/texmf-dist/doc/generic/FAQ-en/faq.sty index 5dcf6455821..225cffb242a 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.132 2011/10/25 18:22:56 rf10 Exp rf10 $ +% $Id: faq.sty,v 1.134 2012/03/10 13:56:18 rf10 Exp rf10 $ % % This is the LaTeX package that deals with the eccentricities of mark % up of the UK TeX FAQ. @@ -142,6 +142,7 @@ % % general support %\RequirePackage{calc} +\RequirePackage{microtype} % % code for handling logo font %% \RequirePackage{mflogo} @@ -157,8 +158,10 @@ %% }% %% } %% \fi -\DeclareRobustCommand\MF{Meta\-Font} -\DeclareRobustCommand\MP{Meta\-Post} +\DeclareRobustCommand\MF{Meta\-font} +\let\mf\MF +\DeclareRobustCommand\MP{Meta\-post} +\let\mp\MP \newcommand\ttype{TrueType} \newcommand\otype{OpenType} \let\textlogo\textmd @@ -1073,6 +1076,9 @@ % date question last edited \def\LastEdit{\@ifstar\@gobble\@gobble} % +% where the info came from +\newcommand\LeadFrom[3]{} +% % \Qlabel and \Qref: define and refer to labels \ifpdf % hyperref version of \label doesn't get set until begin document 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 78a705368ad..92bb688aafa 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.24} \def\faqfiledate{2011-11-01} +\def\faqfileversion{3.25} \def\faqfiledate{2012-03-29} % % The above line defines the file version and date, and must remain % the first line with any `assignment' in the file, or things will diff --git a/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf b/Master/texmf-dist/doc/generic/FAQ-en/letterfaq.pdf Binary files differindex a225aaaa38b..c7036d0f3e8 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 a6285a73b65..3b095b7fa51 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf +++ b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf |