diff options
| author | Karl Berry <karl@freefriends.org> | 2014-06-18 23:14:29 +0000 |
|---|---|---|
| committer | Karl Berry <karl@freefriends.org> | 2014-06-18 23:14:29 +0000 |
| commit | c5edd50aeb2c7508b5f1f856bdaa012239e86476 (patch) | |
| tree | b3ecc5d55ddf7f6f5099305f18c7ee1759b0e349 /Master/texmf-dist/doc/generic | |
| parent | c04fbad5aaa7648bdafba2e41f8390af5e0cb82b (diff) | |
FAQ-en (10jun14)
git-svn-id: svn://tug.org/texlive/trunk@34303 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/generic')
34 files changed, 1767 insertions, 541 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.28 b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.28 new file mode 100644 index 00000000000..29409bb0a08 --- /dev/null +++ b/Master/texmf-dist/doc/generic/FAQ-en/CHANGES-3.28 @@ -0,0 +1,66 @@ +Changes since version 3.27 + +New answers: + +Label centre-flt: deals with center environment around a float + +Label cpy-srchpdf: replaces label srchpdf, and covers copying text, too + +Label getnff: support for fonts "not allowed" in distributions + +Label lollipop: restored entry, given new maintainer + +Label ltx-csv: how to deal with CSV files in LaTeX + +Label otf-maths: typeset maths using OpenType fonts + +Label parmoderr: about the error "not in outer par mode" + +Relabelled answers: + <none> + +Revised answers: + +Label bibtexing: link to www.bibtex.org + +Label boldgreek: clarify some really old text + +Label catalogue: update in light of new www.ctan.org + +Label clsvpkg: clarify some distinctions + +Label cmdstar: \makeatletter was incorrectly placed in example + +Label commercial: remove entry for Micropress, Inc (once vTeX suppliers) + +Label conditional: discuss use of the tagging package + +Label context: editorial (for better relation to reality, one hopes ;-) + +Label custbib: discourage "beginners" from attempting biblatex styles + +Label dtx: add discussion of generating output from the files + +Label filesused: change reference from teTeX to TeX-live(!) + +Label findfont: tidy, add more reference details + +Label gethelp: add reference to TeX/StackExchange "starter" summary + +Label hyphexcept: deal, perfunctorily, with Unicode hyphenation + +Label hyphoff: editorial change only + +Label nohyph: {ditto} + +Label labelfig: discuss pdfrack + +Label latexandplain: re-write -- previous version seemed not to help, much + +Label latextoplain: re-dump my mental image of what goes on ... looks better + +Label ltxcmds: clarification (editorial changes only) + +Label makeindex: further work on xindy description + +Label mfptutorials: remove one dead link, refer to Voipio's TUGboat papers + +Label mp: MetaPost can also create SVG output + +Label music: update discussion of lilypond, and mention lilyglyphs pkg + +Label normalszmiss: rewritten (a simple answer is difficult to write "well"!) + +Label numbersets: add boondox, newpx and newtx fonts as a potential source + +Label oldfontnames: tidied up + +Label papergeom: remove special case for vTeX + +Label plninltx*: clarification (editorial changes only) + +Label psfchoice: provide link to +otf-maths + +Label readtex: add a bit about using on-line LaTeX servers + +Label slidecls: mention a beamer gallery linked from post in TeX/sx + +Label spell: suggest hunspell (which is even part of recent MacOS X) + +Label sysother: remove references to vTeX + +Label sysunix: remove mention of MikTeX/Unix, and references to vTeX + +Label tocloftwrong: add actual answer (as well as reference to answer...) + +Label usepictex: remove reference to vTeX + +Label verbwithin: suggest newverbs, verbatim box-writing (tcolorbox,verbatim) + +Label whereFAQ: remove link to texnik.de + +Label xspace: clarify, play down the value of the command + +Deleted answers: + +Label srchpdf: replaced by answer labelled cpy-srchpdf + +Web interface, etc.: + Links in the section at the end of each answer now go via the mirror + selector mirror.ctan.org (previously all links went via the Cambridge + CTAN node). + +Robin Fairbairns +Hapless FAQer of Cambridge diff --git a/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog b/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog index f3de019d90d..7eca576bcd4 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog +++ b/Master/texmf-dist/doc/generic/FAQ-en/ChangeLog @@ -1,7 +1,603 @@ +2014-06-10 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * texfaq2html: tidy blank lines + + * sanitize.pl: a few changes from -beta + + * gather-faqbody.tex: new version + + * faq-intro.tex: + * faq-mac-prog.tex + * faq-wdidt.tex: + * add-general.tex: \nothtml{\noindent}!!! + +2014-06-09 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-how-do-i.tex (q-conditional): mention the tagging package + +2014-06-03 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-bits+pieces.tex (q-dtx): first stab at description of "using" a + .dtx/.ins combination to produce packages and docs + +2014-05-30 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-fmt-conv.tex (q-latextoplain): clarification (i hope!) + + * faq-backgrnd.tex (q-context): attempting a better path for beginners + +2014-05-21 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-backgrnd.tex (q-readtex): dash off ref to online compilers + +2014-05-18 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-t-g-wr.tex (q-oldfontnames): historic stuff cleared away, + slight rewording + +2014-05-07 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-adj-types.tex (q-makeindex): work on description of using xindy + + * sanitize-beta.pl (sanitize_line): add \luatex and \lualatex + + * faq.sty: add \luatex and \lualatex + +2014-05-02 Robin Fairbairns <rf10@cl.cam.ac.uk> ron.cummins@gmail.com + + * faq-biblio.tex (q-custbib): discourage beginners from attempting + their own biblatex style; editorial + +2014-04-25 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * dirctan.tex: restore lollipop (w/cat link) + + * faq-backgrnd.tex (q-lollipop): renew, from add-general + +2014-04-23 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * dirctan.tex: drop fonts/armenian (fonts now part of armtex) + + * add-general.tex (q-lollipop): recreated entry for lollipop + +2014-04-04 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-mac-prog.tex (q-cmdstar): bug fix from javier mora + +2014-03-19 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-getit.tex (q-findfiles): editorial + +2014-03-18 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-backgrnd.tex (q-catalogue): yet another iteration + (q-context): typos + (q-latexandplain): rewrite. who knows if it's worth it... + +2014-03-17 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-backgrnd.tex (q-catalogue): 2 iterations towards + comprehensibility + +2014-03-14 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-docs.tex (q-latex-books): sort out html of more math into latex + (still not terribly good, but no more actual latex...) + +2014-03-05 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * add-general.tex (q-getnff,q-otf-maths): removed as already in main + (q-outer-err): removed, similarly + +2014-03-04 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-docs.tex: missing close brace + +2014-02-18 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-docs.tex (q-mfptutorials): add links to the voipio papers, + and remove the (dead) one to Heck's + +2014-02-16 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-hyp+pdf.tex (q-pdfpagelabels): add {} to a \dots call + (q-cpy-srchpdf): deal with broken parens + +2014-02-10 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * add-general.tex: remove q-ltx-csv (now in faq-mac-prog) + +2014-01-31 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-biblio.tex (q-custbib): typo + +2014-01-29 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * sanitize-beta.pl (sanitize_line): remove {} from pattern \\The{}\{\} ? + +2014-01-28 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-docs.tex (q-gethelp): warning of abrasiveness on tex/sx + +2014-01-26 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-how-do-i.tex (Q-filesused): convert tetex ref to texlive-unix(!) + +2014-01-22 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-adj-types.tex (q-dropping): remove ref to vtex + + * faq-graphics.tex (q-labelfig): remove refs to vtex + + * faq-hyp+pdf.tex (q-acrobat): remove ref to vtex + + * faq-t-g-wr.tex (q-usepictex): root out reference to vtex + + * faq-fonts.tex (q-otf-maths): new, from add-general + (q-psfchoice): editorial, incl reference to q-otf-maths + +2014-01-21 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-getit.tex (q-findfont): tidy, and fill in missing holes + +2013-12-10 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-backgrnd.tex (q-mp): mp output may be svg, too + +2013-12-04 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-symbols.tex (q-numbersets): add boondox as a source, mention + newpx, newtx as preferable to pxfonts/txfonts + +2013-11-28 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * add-general.tex (q-cap-out-flt): new error answer + +2013-11-27 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-backgrnd.tex (q-whattex): reworded for clarity + +2013-11-26 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-wdidt.tex (q-xspace): play the command down (after reading a post + on tex/sx by david carlisle, tidy the whole question. + +2013-11-20 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-jot-err.tex (q-normalszmiss): rewritten. not easy to do, without + sounding patronising + +2013-11-19 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-install.tex,faq-biblio.tex: editorial (% signs) + + * faq-wdidt.tex (q-center-flt): new, from add-general + + * sanitize-beta.pl (sanitize_line): move \textpercent{} to immediately + below "dump comments" code + + * faq-adj-types.tex (a-outszwrng): braces after \textpercent + +2013-11-05 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * add-general.tex (q-inputenc): show structure of multiple-encoding docs + +2013-10-28 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-adj-types.tex (q-linespace): editorial + +2013-10-22 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-fonts.tex (q-getnff): new, from add-general + + * add-general.tex (q-getnff): mention distinction between -sys and + user versions of the script + +2013-10-21 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-wdidt.tex (q-verbwithin): mention verbatim writing using + tcolorbox and moreverb (and mention the comments in the doc of + verbatim, for diy enthusiasts). + + * faq-intro.tex: add martin garrod to the list, mark drucbert deceased + + * faq-bits+pieces.tex (q-clsvpkg): remove duplicate "report" (!) + +2013-10-18 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * add-general.tex (q-catcodes): doodling with better explanation + (not got very far) + + * faq-docs.tex (q-latex-books): reference digital version of tlc2 + + * FAQ-wdidt.tex (q-verbwithin): typo (extra closing paren) + +2013-10-15 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-docs.tex (q-bibtexing): mention www.bibtex.org + +2013-10-10 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-backgrnd.tex (q-context): provide link to minimals (even though + it's not the neatest of web sites...) + +2013-10-09 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * dirctan.tex: add context-contrib + + * faq-backgrnd.tex (q-context): edited for more realism re. ctan + + * faq-getit.tex (q-findfiles): rsync is the only mirroring protocol + +2013-10-02 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-support.tex (q-spell): weave in hunspell (not on ctan...) + +2013-09-27 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-mac-prog.tex (q-plninltx*): editorial (hoping for clarification) + (q-ltxcmds): editorial (again aiming for clarification) + + * faq-adj-types.tex (q-music): typo for \progname + +2013-09-25 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-docs.tex (q-gethelp): change junk edit date to today + +2013-09-23 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * dirctan.tex: makeinfo's moved + + * faq-adj-types.tex (q-music): use of lilyglyphs as option + +2013-09-20 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-how-do-i.tex (q-nohyph): minor editorial + (q-hyphoff): ditto + (q-hyphexcept): editorial, add a bit of text discussing unicode + hyphenation + +2013-09-13 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * gather-faqbody.tex: comment out debugging stuff + + * faq-docs.tex (q-gethelp): mention tex/sx "getting started" page + +2013-09-11 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * dirctan.tex: pgf dir is actually the base above graphics/pgf + add cat link for picinpar + * faq-mac-prog.tex (q-ltx-csv): new, from add-general + +2013-09-09 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-jot-err.tex (q-parmoderr): new, from add-general + + * add-general.tex (q-parmoderr): tweaks for clarification + +2013-08-29 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-adj-types.tex (q-overstrike): suggest pdfcomment + + * dirctan.tex: add pdfcomment + +2013-08-21 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-how-do-i.tex (q-mathlips): sort out refs to yhmath (now in just + the one place on ctan + + * dirctan.tex: add belleek (from broken filectan entry) + + * faq-hyp+pdf.tex (q-cpy-srchpdf): extended replacement for q-srchpdf + + * dirctan.tex: add mmap, belleek; remove one of the verbdef entries + +2013-08-20 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-intro.tex: editorial + + * faq-wdidt.tex (q-tocloftwrong): missing brace + +2013-08-19 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * dirctan.tex: remove duplicate of verbdef + +2013-07-18 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * dirctan.tex: tidy up copies + + * faq-texsys.tex (throughout): remove vtex + (q-sysunix): purge mention of unix miktex + dirctan.tex: remove biolinum + +2013-07-17 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-adj-types.tex (q-slidecls): link to beamer theme gallery + +2013-07-15 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-adj-types.tex (q-papergeom): no more vtex + + * faq-texsys.tex (q-sysother): expunge reference to vtex + +2013-07-14 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-wdidt.tex (q-tocloftwrong): give answers as well as reference! + (needs some reference to koma-script) + +2013-07-12 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-graphics.tex (q-labelfig): add text discussing pdfrack + + * dirctan.tex: add pdfrack + +2013-07-09 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-bits+pieces.tex (q-clsvpkg): editorial + +2013-07-02 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-docs.tex (q-whereFAQ): remove voss's texnik.de (no longer there) + +2013-06-25 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-backgrnd.tex (q-eplain): editorial + (q-whyfree): editorial on licence issues + (q-tug*): tidy conditional sections + +2013-06-20 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * dirctan.tex: add verbatimbox + + * faq-wdidt.tex (q-verbwithin): add bullet item about verbatimbox + +2013-06-17 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-backgrnd.tex (q-context): flagged potential need for context + minimals; this file is wildly different to its supposed rcs copy... + needs review when i've learnt more about minimals + +2013-06-12 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faqbody.tex: version 3.28, today + + * faq-symbols.tex (q-boldgreek): largely rewritten, with more detail + about the reasons for the acrobatics needed (also remove incorrect + assertion about amsmath and \mathbf) + +2013-06-10 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-wdidt.tex (q-verbwithin): newverbs helps -- like verbdef, etc + + * dirctan.tex: add newverbs + +2013-06-07 *** Release 3.27 *** + +2013-06-06 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * add-general.tex (q-otf-maths): minor tweak + + * faq-install.tex (q-what-TDS): editorial + +2013-06-05 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-symbols.tex (q-scriptfonts): mention tgchorus + + * faq-wdidt.tex (q-dolldoll): editorial clarification (hopefully...) + +2013-06-04 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * dirctan.tex: add anyfontsize, remove ghostscript, gsview, + correct polyglossia + + * faq-mac-prog.tex (q-fontsize): editorial, incorporate + anyfontsize package + +2013-06-03 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-backgrnd.tex (q-notWYSIWYG): flesh out, note demise of textures, + editorial + + * texfaq2html-beta: ignore intro by scanning file for \end{introduction} + + * faq-jot-err.tex (q-buffovl): editorial + + * faq-graphics.tex (q-labelfig,q-repeatgrf,q-dvipdfmgraphics): gs + from web + +2013-05-31 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-hyp+pdf.tex (q-hyper, q-acrobat): tidies, gs from web + +2013-05-29 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-fonts.tex (q-psfchoice): add URW base35 in their own right + to discussion of txfonts + + * faq-graphics.tex (q-mpprologues): href for ghostscript + (q-labelfig): href for gsview + + * faq-fonts.tex (q-psfchoice): href for ghostscript + + * faq-dvi.tex (q-otherprinters): href for ghostscript + +2013-05-24 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * texfaq2html: minuscule changes from -beta + + * sanitize.pl (sanitize_line): minuscule changes from -beta + +2013-05-21 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-backgrnd.tex (q-texfuture): end date for luatex 2014 (i think) + + * sanitize-beta.pl (sanitize_line): add entity xlations for \beta, \pi + + * faq-projects.tex (q-luatex): update somewhat + + * faq-backgrnd.tex (q-ctan): editorial + (q-catalogue): editorial + (q-y2k): commented out (no longer relevant) + +2013-05-20 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-texsys.tex (q-editors): reword mention of texworks, add texstudio + +2013-05-14 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-symbols.tex (q-osf): \oldstylenums _does_ use bold style + +2013-05-13 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * dirctan.tex: add try + + * faq-how-do-i.tex (q-make): add try + + * faq-backgrnd.tex (q-catalogue): editorial + +2013-04-29 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-intro.tex: added subsection about licence + +2013-04-23 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-graphics.tex (q-mpprologues): untangle some prose. slightly. + +2013-04-22 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-fonts.tex (q-pspreview): ghostscript, gsview from web + (q-psfchoice): remove ghostscript mention in discussing urw fonts; + reference newpx from pxfonts, and newtx from txfonts, add urw-base35 + to ctanrefs as locations of palladio and NimbusRomanNo9 + +2013-04-19 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-dvi.tex (q-dvi-bmp): typo + +2013-04-18 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-jot-err.tex (q-buffovl): ghostscript and gsview from the net + +2013-04-17 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * dirctan.tex: add dtxgen + + * faq-bits+pieces.tex (q-dtx): mention dtxgen + + * faq-projects.tex (q-luatex): revise version statement, editorial + +2013-04-16 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> + + * faq-texsys.tex (q-commercial): remove bluesky :-( + +2013-04-16 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-fmt-conv.tex (q-recovertex): munge ghostscript refs, remove it + from ctanrefs + + * faq-dvi.tex (q-dvi-bmp): editorial + + * add-general.tex (q-tangle-weave): editorial, link to doc of web2c on + tug site + +2013-04-12 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-fmt-conv.tex (q-fmtconv): tidy, re-organise + +2013-04-11 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-fmt-conv.tex (q-readML): correct a \Qref call + + * faq-fonts.tex (q-psfchoice): add newpx to the list + + * faq-texsys.tex (q-syswin32): miktex 2.9 (in ctanrefs) + + * faq-dvi.tex (q-otherprinters): reword because gs no longer on ctan + (q-previewers): ditto + +2013-04-09 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-symbols.tex (q-scriptfonts): elide mention of ghostscript, + since (a) it doesn't add anything, and (b) it's no longer + available on ctan + + * dirctan.tex: add newpx + +2013-03-28 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * filectan.tex: remove <ispell> + + * dirctan.tex: add <showexpl>, <ispell>; correct <spelling>; remove + <makeinfo>, ghostscript-[gpl|ghostgum] + + * faq-adj-types.tex (q-codelist): add showexpl + +2013-03-26 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-docs.tex (q-man-latex): add link to nicola's phd and admin books + +2013-03-22 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * add-general.tex (q-tangle-weave): new: the basics of web + +2013-03-21 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-how-do-i.tex (q-make): add ctan link for vpp + +2013-03-15 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-bits+pieces.tex (q-dvi): editorial, hoping to clarify + +2013-03-11 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-how-do-i.tex (q-footintab): don't suggest putting a "table" in + minipage ... good sense from ulrike fischer + +2013-03-08 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * sanitize-beta.pl (sanitize_line): \arrowhyph translate to → + +2013-03-07 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * gather-faqbody.tex: v3.26b, today + + * faq-the-end.tex (q-latexbug): removed "upload bug by email"; editorial + +2013-03-05 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * add-general.tex (q-varitoc): start of an answer starting from the + ideas of the tableof package + + * faq-adj-types.tex (q-minitoc): editorial + +2013-03-04 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * texfaq2html, texfaq2html-beta, sanitize.pl, sanitize-beta.pl: + correct \ctanhref coding (never-used flexibility in early coding + had confused me summat rotten) + +2013-03-01 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-intro: remove a spurious "<p/>" (huh?) + + * faq-jot-err.tex (q-manymathalph): point out that the problem can also + be avoided by using xetex/luatex + + * gather-faqbody.tex: version 3.26a, today (released as beta) + + * faq-mac-prog.tex (q-repeat-num): tone down "tex.ne.prog language" + (q-repeat-set): consequential changes to match -repeat-num + +2013-02-28 Robin Fairbairns <rf10@cl.cam.ac.uk> + + * faq-mac-prog.tex (q-cmdstar): this was buggy; corrected + 2013-02-26 Robin Fairbairns <rf10@cl.cam.ac.uk> * faqbody.tex: update \faqfiledate + *** released 3.26 *** + 2013-02-21 Robin Fairbairns <rf10@cl.cam.ac.uk> * faq-support.tex (q-spell): editorial @@ -4338,7 +4934,7 @@ RELEASE 3.19a * faqbody.tex (subsection{"Generic" macros and techniques}): reword q-empty for clarity - + 2007-10-30 Robin Fairbairns <rf10@beret.cl.cam.ac.uk> * faqbody.tex (section{DVI Drivers and Previewers}): editorial diddles @@ -17152,7 +17748,6 @@ Thu Sep 22 09:18:38 1994 Robin Fairbairns (rf@dorceus.cl.cam.ac.uk) * newfaq.tex: (last night's work) new-style markup for question references, label for last question (so we can see how well we're doing), \makeshortverb of \| so as to get coherent log output - Tue Sep 20 13:54:51 1994 Robin Fairbairns (rf@dorceus.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 925cd1b08d1..1cf86379dc9 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/archive.cfg b/Master/texmf-dist/doc/generic/FAQ-en/archive.cfg index 8b64957f06f..0d998ea78c0 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/archive.cfg +++ b/Master/texmf-dist/doc/generic/FAQ-en/archive.cfg @@ -3,7 +3,7 @@ % % the archive itself -\def\LocalCTAN{ftp://ftp.tex.ac.uk/tex-archive/} % could be anything +\def\LocalCTAN{http://mirror.ctan.org/} % could be anything % out of CTAN.sites % % the format for use when retrieving directory hierarchies diff --git a/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex b/Master/texmf-dist/doc/generic/FAQ-en/dirctan.tex index 325040d7129..00f797453ad 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.301 2012/12/07 19:34:33 rf10 Exp rf10 $ +% $Id: dirctan.tex,v 1.302 2013/07/24 21:43:10 rf10 Exp rf10 $ % % protect ourself against being read twice \csname readCTANdirs\endcsname @@ -53,7 +53,6 @@ \CTANdirectory{appendix}{macros/latex/contrib/appendix}[appendix] \CTANdirectory{arabtex}{language/arabic/arabtex} \CTANdirectory{arara}{support/arara}[arara] -\CTANdirectory{armenian}{fonts/armenian} \CTANdirectory{aro-bend}{info/challenges/aro-bend}[aro-bend] \CTANdirectory{asana-math}{fonts/Asana-Math}[asana-math] \CTANdirectory{asc2tex}{systems/msdos/asc2tex} @@ -90,6 +89,7 @@ \CTANdirectory{beamer}{macros/latex/contrib/beamer}[beamer] \CTANdirectory{beamerposter}{macros/latex/contrib/beamerposter}[beamerposter] \CTANdirectory{beebe}{dviware/beebe} +\CTANdirectory{belleek}{fonts/belleek}[belleek] \CTANdirectory{beton}{macros/latex/contrib/beton}[beton] \CTANdirectory{bezos}{macros/latex/contrib/bezos}[bezos] \CTANdirectory{bib-fr}{biblio/bibtex/contrib/bib-fr} @@ -130,6 +130,7 @@ \CTANdirectory{bold-extra}{macros/latex/contrib/bold-extra}[bold-extra] \CTANdirectory{bonus}{systems/msdos/emtex-contrib/bonus} \CTANdirectory{booktabs}{macros/latex/contrib/booktabs}[booktabs] +\CTANdirectory{boondox}{fonts/boondox}[boondox] \CTANdirectory{borceux}{macros/generic/diagrams/borceux} \CTANdirectory{braket}{macros/latex/contrib/braket}[braket] \CTANdirectory{breakurl}{macros/latex/contrib/breakurl}[breakurl] @@ -220,7 +221,8 @@ \CTANdirectory{concmath}{macros/latex/contrib/concmath}[concmath] \CTANdirectory{concmath-f}{fonts/concmath}[concmath-fonts] \CTANdirectory{concrete}{fonts/concrete}[concrete] -\CTANdirectory{context}{macros/context}[context] +\CTANdirectory{context}{macros/context/current}[context] +\CTANdirectory{context-contrib}{macros/context/contrib} \CTANdirectory{cprotect}{macros/latex/contrib/cprotect}[cprotect] \CTANdirectory{cptex}{macros/generic/cptex} \CTANdirectory{crop}{macros/latex/contrib/crop}[crop] @@ -229,6 +231,7 @@ \CTANdirectory{crudetype}{dviware/crudetype}[crudetype] \CTANdirectory{crw}{macros/plain/contrib/crw} \CTANdirectory{cs-tex}{systems/atari/cs-tex} +\CTANdirectory{csvsimple}{macros/latex/contrib/csvsimple}[csvsimple] \CTANdirectory{ctable}{macros/latex/contrib/ctable}[ctable] \CTANdirectory{ctan}{help/ctan} \CTANdirectory{cun}{fonts/cun} @@ -562,12 +565,14 @@ \CTANdirectory{lgrind}{support/lgrind}[lgrind] \CTANdirectory{libertine}{fonts/libertine}[libertine] \CTANdirectory{libgreek}{macros/latex/contrib/libgreek}[libgreek] +\CTANdirectory{lilyglyphs}{macros/luatex/latex/lilyglyphs} \CTANdirectory{lineno}{macros/latex/contrib/lineno}[lineno] \CTANdirectory{lipsum}{macros/latex/contrib/lipsum}[lipsum] \CTANdirectory{listbib}{macros/latex/contrib/listbib}[listbib] \CTANdirectory{listings}{macros/latex/contrib/listings}[listings] \CTANdirectory{lm}{fonts/lm}[lm] \CTANdirectory{lm-math}{fonts/lm-math}[lm-math] +\CTANdirectory{lollipop}{macros/lollipop}[lollipop] \CTANdirectory{lookbibtex}{biblio/bibtex/utils/lookbibtex} \CTANdirectory{lpic}{macros/latex/contrib/lpic}[lpic] \CTANdirectory{lsedit}{support/lsedit} @@ -590,8 +595,8 @@ \CTANdirectory{makecell}{macros/latex/contrib/makecell}[makecell] \CTANdirectory{makedtx}{support/makedtx}[makedtx] \CTANdirectory{makeindex}{indexing/makeindex}[makeindex] -;\CTANdirectory{makeprog}{support/makeprog} -\CTANdirectory{maketexwork}{info/maketexwork} +\CTANdirectory{makeinfo}{macros/texinfo/contrib/texinfo-hu/texinfo/makeinfo} +\CTANdirectory{makeprog}{support/makeprog}\CTANdirectory{maketexwork}{info/maketexwork} \CTANdirectory{malayalam}{language/malayalam} \CTANdirectory{malvern}{fonts/malvern} \CTANdirectory{mapleweb}{web/maple/mapleweb} @@ -636,6 +641,7 @@ \CTANdirectory{minted}{macros/latex/contrib/minted}[minted] \CTANdirectory{mkjobtexmf}{support/mkjobtexmf}[mkjobtexmf] \CTANdirectory{mma2ltx}{graphics/mma2ltx} +\CTANdirectory{mmap}{macros/latex/contrib/mmap} \CTANdirectory{mnsymbol}{fonts/mnsymbol}[mnsymbol] \CTANdirectory{mnu}{support/mnu} \CTANdirectory{models}{macros/text1/models} @@ -677,6 +683,7 @@ \CTANdirectory{newsletr}{macros/plain/contrib/newsletr} \CTANdirectory{newpx}{fonts/newpx}[newpx] \CTANdirectory{newtx}{fonts/newtx}[newtx] +\CTANdirectory{newverbs}{macros/latex/contrib/newverbs}[newverbs] \CTANdirectory{nedit-latex}{support/NEdit-LaTeX-Extensions} \CTANdirectory{nonumonpart}{macros/latex/contrib/nonumonpart}[nonumonpart] \CTANdirectory{nopageno}{macros/latex/contrib/nopageno}[nopageno] @@ -718,18 +725,20 @@ \CTANdirectory{pbox}{macros/latex/contrib/pbox}[pbox] \CTANdirectory{pcwritex}{support/pcwritex} \CTANdirectory{pdcmac}{macros/plain/contrib/pdcmac}[pdcmac] +\CTANdirectory{pdfcomment}{macros/latex/contrib/pdfcomment}[pdfcomment] \CTANdirectory{pdfpages}{macros/latex/contrib/pdfpages}[pdfpages] +\CTANdirectory{pdfrack}{support/pdfrack}[pdfrack] \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}{graphics/pdftricks}[pdftricks] \CTANdirectory{pdftricks2}{graphics/pdftricks2}[pdftricks2] -\CTANdirectory{pgf}{graphics/pgf}[pgf] +\CTANdirectory{pgf}{graphics/pgf/base}[pgf] \CTANdirectory{phonetic}{fonts/phonetic} \CTANdirectory{phy-bstyles}{biblio/bibtex/contrib/phy-bstyles} \CTANdirectory{physe}{macros/physe} \CTANdirectory{phyzzx}{macros/phyzzx} -\CTANdirectory{picinpar}{macros/latex209/contrib/picinpar} +\CTANdirectory{picinpar}{macros/latex209/contrib/picinpar}[picinpar] \CTANdirectory{picins}{macros/latex209/contrib/picins}[picins] \CTANdirectory{pict2e}{macros/latex/contrib/pict2e}[pict2e] \CTANdirectory{pictex}{graphics/pictex}[pictex] @@ -855,7 +864,9 @@ \CTANdirectory{tablefootnote}{macros/latex/contrib/tablefootnote}[tablefootnote] \CTANdirectory{tabls}{macros/latex/contrib/tabls}[tabls] \CTANdirectory{tabulary}{macros/latex/contrib/tabulary}[tabulary] +\CTANdirectory{tagging}{macros/latex/contrib/tagging} \CTANdirectory{talk}{macros/latex/contrib/talk}[talk] +\CTANdirectory{tcolorbox}{macros/latex/contrib/tcolorbox}[tcolorbox] \CTANdirectory{tds}{tds}[tds] \CTANdirectory{ted}{macros/latex/contrib/ted}[ted] \CTANdirectory*{testflow}{macros/latex/contrib/IEEEtran/testflow}[testflow] @@ -933,9 +944,11 @@ \CTANdirectory{utopia}{fonts/utopia}[utopia] \CTANdirectory{varisize}{macros/plain/contrib/varisize}[varisize] \CTANdirectory{varwidth}{macros/latex/contrib/varwidth}[varwidth] -\CTANdirectory{version}{macros/latex/contrib/version}[version] \CTANdirectory{vc}{support/vc}[vc] +\CTANdirectory{verbatim}{macros/latex/required/tools}[verbatim] +\CTANdirectory{verbatimbox}{macros/latex/contrib/verbatimbox}[verbatimbox] \CTANdirectory{verbdef}{macros/latex/contrib/verbdef}[verbdef] +\CTANdirectory{version}{macros/latex/contrib/version}[version] \CTANdirectory{vertbars}{macros/latex/contrib/vertbars}[vertbars] \CTANdirectory{vita}{macros/latex/contrib/vita}[vita] \CTANdirectory{vmargin}{macros/latex/contrib/vmargin}[vmargin] @@ -969,8 +982,7 @@ \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{yhmath}{fonts/yhmath}[yhmath] \CTANdirectory{zefonts}{fonts/zefonts}[zefonts] \CTANdirectory{ziffer}{macros/latex/contrib/ziffer}[ziffer] \CTANdirectory{zoon-mp-eg}{info/metapost/examples}[metapost-examples] 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 8a483f1d06b..0906f918f46 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.7 2013/02/27 19:43:23 rf10 Exp rf10 $ +% $Id: faq-adj-types.tex,v 1.50 2014/01/22 17:29:03 rf10 Exp $ \section{Adjusting the typesetting} @@ -88,10 +88,11 @@ facilities for producing printed copies of slides. which claims to differ from the systems mentioned above, such as \Class{beamer}, in that it doesn't impose a slide style on you. You get to specify a bunch of slide styles, and you can switch from one to -the other between slides, as you need. (The class itself provides -just the one style, in the package \Package{greybars}: the author -hopes users will contribute their own styles, based on -\Package{greybars}.) +the other between slides, as you need. The class itself provides +just the one style, in the package \Package{greybars}: the author's +suggestion that users should contribute their own has been +enthusiastically accepted~--- see (for example) the % !line break +\href{http://deic.uab.es/~iblanes/beamer_gallery/}{Beamer Gallery}. \Package{Lecturer} is a \emph{generic} solution (it works with \plaintex{}, \latex{} and \context{}~mk~ii, but not~--- yet~--- with @@ -110,7 +111,7 @@ themselves be able to tune its macros. \acro{PDF}, to `animate' the file at places you've marked with commands from one of the \ProgName{pp4} packages. The commands don't work on \acro{PDF} that has come from \ProgName{dvips} output; they -work with \acro{PDF} generated by \PDFLaTeX{}, V\TeX{} \LaTeX{}, or +work with \acro{PDF} generated by \PDFLaTeX{}, \LaTeX{}, or \ProgName{dvipdfm} running on \LaTeX{} output. \Package{Pdfscreen} and \Package{texpower} are add-on packages that @@ -1370,7 +1371,7 @@ to the next: Page Scaling (default: ``Fit to printer margins'')~--- change to ``None'', and\\ Scale (default 95\textpercent{} of Normal size)~--- change to - ``100\textpercent''. + ``100\textpercent{}''. \item Adobe Reader 6:\\ in the print dialogue, on the ``copies \& pages'' pane, you'll find a popup menu/drop-down list titled ``Page Scaling''~--- change to ``None''. @@ -1423,7 +1424,7 @@ paper size specified in a \csx{documentclass} option. The \acro{DVI} drivers \ProgName{dvips}, \ProgName{dvipdfm} and its extensions (\ProgName{dvipdfmx} and \ProgName{xdvipdfmx}) define \csx{special} commands for the document to specify its own paper size; -so in those cases, as when \PDFTeX{} or V\TeX{} is being used, the +so in those cases, as when \PDFTeX{} is being used, the paper size can be programmed by the document. Users who wish to, may of course consult the manuals of the various programs to write the necessary code. @@ -1438,7 +1439,7 @@ necessary to ensure the correct size of paper is used. If If the document is being processed by \LaTeX{} on a \TeX{} or \eTeX{} 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{}.) +ignored if you are using \PDFLaTeX{}.) So, one resolution of the problem, when you are using \latex{}, is to add \begin{quote} @@ -1452,14 +1453,14 @@ your (\PS{} or \acro{PDF} output~--- \Package{geometry} knows about serves for the extension \ProgName{dvipdfmx} and \ProgName{xdvipdfmx}). -If you're using \PDFLaTeX{}, \xetex{} or V\TeX{}, load with +If you're using \PDFLaTeX{} or \xetex{}, load with \begin{quote} \begin{verbatim} \usepackage[program-option,...]{geometry} \end{verbatim} \end{quote} where \pkgoption{program-option} is \pkgoption{pdftex}, -\pkgoption{xetex} or \pkgoption{vtex}. +\pkgoption{xetex}. The alternative, \Package{zwpagelayout} requires a \pkgoption{driver} option: @@ -2300,13 +2301,14 @@ be inconsistent. For preference (and certainly for a production document, such as a dissertation or an article submission), use a line-spacing package. -The only one currently supported is \Package{setspace} (do \emph{not} -be tempted by \Package{doublespace}~--- its performance under current -\LaTeX{} is at best problematical). \Package{Setspace} switches off -double-spacing at places where even the most die-hard official would -doubt its utility (footnotes, figure captions, and so on); it's very -difficult to do this consistently if you're manipulating -\csx{baselinestretch} yourself. +The only one currently supported is \Package{setspace}. +\Package{Setspace} switches off double-spacing at places where even +the most die-hard official would doubt its utility (footnotes, figure +captions, and so on); it's very difficult to do this consistently if +you're manipulating \csx{baselinestretch} yourself. + +(Note: do \emph{not} be tempted by \Package{doublespace}~--- its +performance under current \LaTeX{} is at best problematical.) Of course, the real solution (other than for private copy editing) is \emph{not} to use double-spacing at all. Universities, in particular, @@ -2328,6 +2330,7 @@ package file itself. \begin{ctanrefs} \item[setspace.sty]\CTANref{setspace} \end{ctanrefs} +\LastEdit{2013-10-28} \Question[Q-letterspace]{Changing the space between letters} @@ -2835,7 +2838,12 @@ The following programs are available: then-current maintainer of \ProgName{makeindex}. It successfully addresses many of \ProgName{makeindex}'s shortcomings, including difficulties with collation order in different languages, and it is - highly flexible. Sadly, its take-up is proving rather slow. + highly flexible. + + \ProgName{Xindy} itself will work with Unicode (UTF-8) encoded + \latex{} input. A separate application (\ProgName{texindy}) deals + with `standard' \latex{} source, processes it and passes + `sanitised' text to \ProgName{Xindy}. \end{description} \begin{ctanrefs} \item[idxtex]\CTANref{glo+idxtex} @@ -2973,8 +2981,14 @@ with plain text input that does most of its work without \tex{}. \ProgName{Lilypond}'s input syntax is less cryptic than is MusiX\TeX{}'s, though similar quality is achieved. The \ProgName{lilypond} -\href{http://lilypond.org/web/about/faq}{\acro{FAQ}} mentions -development of graphical user interfaces. +\href{http://lilypond.org/web/about/faq}{\acro{FAQ}} mentions programs +with graphical user interfaces, that export lilypond output. + +For occasional music references (sharp and flat signs, notes, clefs +and so on, there is a (\latex{}) package (with associated font) called +\Package{lilyglyphs}. This uses \progname{lilypond}'s fonts (which +are included in the package), and also provides the means to add stuff +from other sources. Another alternative in the production of music is the \acro{ABC} notation, which was developed to notate the traditional music of @@ -3004,6 +3018,7 @@ Once Andreas Egler had withdrawn (his last version of the development, leading to the \Package{musixtex} used today. \begin{ctanrefs} \item[abc2mtex]\CTANref{abc2mtex} +\item[lilyglyphs]\CTANref{lilyglyphs} \item[M-Tx]\CTANref{m-tx} \item[midi2tex]\CTANref{midi2tex} \item[musictex]\CTANref{musictex} @@ -3014,7 +3029,7 @@ the development, leading to the \Package{musixtex} used today. \item[mutex]\CTANref{mutex} \item[pmx]\CTANref{pmx} \end{ctanrefs} -\LastEdit{2011-11-01} +\LastEdit{2013-09-27} \Question[Q-parskip]{Zero paragraph indent} @@ -3075,7 +3090,7 @@ you process the \extension{dtx}, the package itself must already be installed. Unfortunately, \Package{dropping} has an intimate relation to the set of device drivers available in an early version of the \LaTeX{} graphics package, and it cannot be trusted to work with -modern offerings such as \PDFTeX{}, V\TeX{} or \acro{DVI}pdfm, let +modern offerings such as \PDFTeX{} or \acro{DVI}pdfm, let alone such modernisms as \xetex{}. As a result, the package is widely deprecated, nowadays. @@ -3086,6 +3101,7 @@ examples adds to the package's document. \item[dropping]\CTANref{dropping} \item[lettrine]\CTANref{lettrine} \end{ctanrefs} +\LastEdit{2014-01-22} \Question[Q-dec_comma]{The comma as a decimal separator} @@ -3189,15 +3205,25 @@ This may be used, for example, to indicate text deleted in the course of editing. Both the \Package{ulem} and the \Package{soul} packages provide the necessary facilities. +Overstriking with an ``attached'' comment may be achieved using the +\Package{pdfcomment} package, to which you can give optional arguments +with all sorts of detail. The comment text is encoded using an Adobe +`annotation'; unfortunately, support for these annotations is not a +common feature of \acro{PDF} viewers, but if you can safely assume +that your audience will use \ProgName{Acrobat Reader}, the facility +provides that extra ``shine'' that business users so love. + Overstriking for % beware line break \Qref*{cancellation in maths expressions}{Q-cancellation} is achieved by a different mechanism. Documentation of \Package{ulem} is in the package file. \begin{ctanrefs} +\item[pdfcomment.sty]\CTANref{pdfcomment} \item[soul.sty]\CTANref{soul} \item[ulem.sty]\CTANref{ulem} \end{ctanrefs} +\LastEdit{2013-08-29} \Question[Q-upquot]{Realistic quotes for verbatim listings} 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 f5c334ee9fa..4b3ed751562 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-backgrnd.tex @@ -1,4 +1,4 @@ -% $Id: faq-backgrnd.tex,v 1.30 2012/10/10 20:37:43 rf10 Exp rf10 $ +% $Id: faq-backgrnd.tex,v 1.31 2014/01/28 18:17:36 rf10 Exp rf10 $ \section{The Background} @@ -80,16 +80,17 @@ systems~--- the sorts of attributes that much modern programming practice aims for. The processed `readable' source of \TeX{} the program may be found in the % ! line break \begin{hyperversion} - \Qref*{\acro{TDS} structured version}{Q-tds} of the distribution. + \Qref*{\acro{TDS} structured}{Q-tds} version of the distribution. \end{hyperversion} \begin{dviversion} - \Qref*{\acro{TDS} structured version of the distribution}{Q-tds}. + \acro{TDS} structured version of the distribution (see + \Qref*{\acro{TDS} structure}{Q-tds}). \end{dviversion} \begin{ctanrefs} \item[\nothtml{\rmfamily}Knuth's source distribution]\CTANref{knuth-dist} \item[\nothtml{\rmfamily}Knuth's sources in \acro{TDS} layout]\CTANref{knuth-tds} \end{ctanrefs} -\LastEdit{2011-06-01} +\LastEdit{2013-11-27} \Question[Q-plaintex]{What's ``writing in \TeX{}''?} @@ -158,7 +159,9 @@ other way than their conversion to an outline font format. The \MP{} system (by John Hobby) implements a picture-drawing language very much like that of \MF{}; the difference is that \MP{} outputs -Encapsulated \PS{} files instead of run-length-encoded bitmaps. \MP{} +vector graphic files instead of run-length-encoded bitmaps; output +formats available are \PS{} or \acro{SVG} +\MP{} is a powerful language for producing figures for documents to be printed on \PS{} printers, either directly or embedded in \AllTeX{} documents. \MP{} is able to integrate text and mathematics, marked up @@ -195,7 +198,7 @@ explanatory background material). \begin{ctanrefs} \item[tex-overview.pdf]\CTANref{tex-overview} \end{ctanrefs} -\LastEdit{2011-09-01} +\LastEdit{2013-12-10} \Question[Q-texthings]{Things with ``\TeX{}'' in the name} @@ -453,37 +456,40 @@ these \acro{FAQ}s, are set up to use the mirror selector. \Question[Q-catalogue]{The (\acro{CTAN}) catalogue} -Finding stuff on networks was always difficult, but in recent years, +Finding stuff on networks used always to be difficult, but in recent years, search engines have become amazingly good at digging out unconsidered trifles from the myriad items of information available on the net. -Confusion is added by the tendency to index the same file at several -mirror sites. - -Sadly, in the \tex{} context, search engines regularly locate -out-of-date material: their users need a means of finding the relevant -material on \acro{CTAN}~--- on the grounds that such material is most -likely to be up-to-date. The need to find up-to-date items, avoiding -out-of-date \alltex{} material, was the motivation for developing a -specialised information source: the \acro{CTAN} catalogue. The -catalogue contains enough information to support most users' needs; -the ideal is that the catalogue entries should appear early in search -engine results, but in practice this is not always achieved. +However, for the \alltex{} user, confusion is added by the tendency to +index the same file at several \acro{CTAN} mirror sites. + +Further, the \alltex{} user usually needs the most recent version of a +package; it's a rare search result that describes itself as obsolete! + +The \acro{CTAN} catalogue, several years after it was introduced, has +developed into a powerful tool for dealing with these difficulties. +It provides an entry for each package to be found on \acro{CTAN}; +users may search the catalogue for an entry, or they may browse its +contents, using the catalogue's lists of ``categories'' of item. The basis of the catalogue is a collection of small, stylised, articles; each shows basic information about a package on \acro{CTAN}, -and includes pointers to download address, documentation and home page -if any, and related -packages. Every \acro{CTAN} mirror holds a copy of the catalogue, -presented as a series of web pages; both alphabetic and category-based -indexes are provided. - -The core \acro{CTAN} sites also offer a simple text search of the -catalogue; the search could be improved, but manpower to do such -improvements is lacking. +and includes pointers to download address (on a \acro{CTAN} mirror), +documentation and home page if any, and related packages. + +The \href{http://www.ctan.org}{\acro{CTAN} central database machine} +offers a ``Browse \acro{CTAN}'' area, with links to the list of +packages, to a list of `topics' (with packages that match each topic), +and to a list of authors (with their packages). + +In addition, every \acro{CTAN} mirror holds a copy of the catalogue, +presented as a series of web pages; one may scan the files in +alphabetic order, or use a category-based index. Such access is not +as ``sophisticated'' as that on the central site, but it served for +years before the central site appeared. \begin{ctanrefs} -\item[\nothtml{\rmfamily}The CTAN catalogue]\CTANref{Catalogue} +\item[\nothtml{\rmfamily}The CTAN catalogue (on CTAN)]\CTANref{Catalogue} \end{ctanrefs} -\LastEdit*{2013-05-21} +\LastEdit{2014-03-17} \Question[Q-triptrap]{How can I be sure it's really \TeX{}?} @@ -750,37 +756,43 @@ closely to their markup. \Question[Q-LaTeXandPlain]{How does \LaTeX{} relate to \plaintex{}?} -\LaTeX{} is a program written in the programming language \TeX{}. (In -the same sense, any \LaTeX{} document is also a program, which is -designed to run `alongside', or `inside' \LaTeX{}, whichever metaphor -you prefer.) - -\plaintex{} is also a program written in the programming language -\TeX{}. - -Both exist because writing your documents in `raw' \TeX{} would -involve much reinventing of wheels for every document. They both -serve as convenient aids to make document writing more pleasant: -\LaTeX{} is a far more extensive aid. - -\LaTeX{} is close to being a superset of \plaintex{}. Many documents -designed for \plaintex{} will work with \LaTeX{} with no more than -minor modifications (though some will require substantial work). - -Interpretation of any \AllTeX{} program involves some data-driven -elements, and \LaTeX{} has a wider range of such elements than does -\plaintex{}. As a result, the mapping from \LaTeX{} to \plaintex{} -is far less clear than that in the other direction~--- see a later -answer about \Qref*{translating to \plaintex{}}{Q-LaTeXtoPlain}. - -\Question[Q-context]{What is \CONTeXT{}?} - -\href{http://www.pragma-ade.com/}{\CONTeXT{}} is a macro package -developed by Hans Hagen of Pragma-Ade; it started as a production tool +\tex{} provides a programming language (of sorts), and any document +more complex than the trivial ``hello world'' will need some +programming. + +\LaTeX{} and \plaintex{} are both libraries written for use with +\tex{}; the user commands \ProgName{tex} and \ProgName{latex} invoke +\tex{}-the-program with a library incorporated. Libraries that may be +loaded in this way are known as `\emph{formats}'; when a user ``runs'' +\plaintex{} or \latex{}, they are running \tex{} (the program) with an +appropriate format. The documents are then programmed in \plaintex{} +or \latex{} \emph{language}. + +\plaintex{} and \latex{} exist because writing your documents in `raw' +\TeX{} could involve much reinventing of wheels for every document. +Both languages serve as convenient aids to make document writing more +pleasant: \LaTeX{} provides many more items to support `common' +requirements of documents. + +As such, \LaTeX{} is close to being a superset of \plaintex{}, but +some \plaintex{} commands don't work as expected when used in a +\latex{} document. Using \plaintex{} commands in a \latex{} document +is an occasional source of bugs: the output is \emph{almost} right, +but some things are misplaced. + +So, \plaintex{} and \latex{} are related through a common parent, and +are designed for use in similar jobs; programming for one will often +not work correctly in the other. +\LastEdit{2014-03-18} + +\Question[Q-context]{What is \context{}?} + +\href{http://www.pragma-ade.com/}{\context{}} is a macro package +created by Hans Hagen of Pragma-Ade; it started as a production tool for Pragma (which is a publishing company). \CONTeXT{} is a document-production system based, like \LaTeX{}, on the \TeX{} typesetting system. Whereas \LaTeX{} insulates the writer from -typographical details, \CONTeXT{} takes a complementary approach by +typographical details, \context{} takes a complementary approach by providing structured interfaces for handling typography, including extensive support for colors, backgrounds, hyperlinks, presentations, figure-text integration, and conditional compilation. It gives the @@ -789,39 +801,49 @@ new layouts and styles without learning the \TeX{} macro language. \CONTeXT{}'s unified design avoids the package clashes that can happen with \LaTeX{}. -\CONTeXT{} also integrates MetaFun, a superset of \MP{} and a powerful +\context{} also integrates MetaFun, a superset of \MP{} and a powerful system for vector graphics. MetaFun can be used as a stand-alone system to produce figures, but its strength lies in enhancing -\CONTeXT{} documents with accurate graphic elements. +\context{} documents with accurate graphic elements. -\CONTeXT{} allows the users to specify formatting commands in English, +\context{} allows users to specify formatting commands in English, Dutch, German, French, or Italian, and to use different typesetting engines (\PDFTeX{}, Xe\TeX{}, Aleph and \LuaTeX{}) without -changing the user interface. \CONTeXT{} continues to develop, often in +changing the user interface. \context{} continues to develop, often in response to requests from the user community. -\CONTeXT{} has been bound to the development of -\Qref*{\luatex{}}{Q-luatex}, almost from the start of that project. -Nowadays, it is distributed in two versions~--- mark two (files with -extension \extension{mkii} (which runs on \pdftex{} but is not under -active development) and mark four files with extension -\extension{mkiv} (which runs on \luatex{} and is where development +The development of \Qref*{\luatex{}}{Q-luatex} was originally driven +by \context{}, almost from the start of its project. Nowadays, +\context{} it is distributed in two versions~--- mark two (files with +extension \extension{mkii}) which runs on \pdftex{} but is not under +active development, and mark four (files with extension +\extension{mkiv}) (which runs on \luatex{} and is where development happens). -\CONTeXT{} has a large developer community (though possibly not as +\context{} has a large developer community (though possibly not as large as that of latex{}), but those developers who are active seem to have prodigious energy. Support is available via a % ! line break -\href{http://contextgarden.net}{\acro{WIKI} site} and via the -\href{http://www.ntg.nl/mailman/listinfo/ntg-context}{mailing list}; -a ``standalone'' distribution (a \TeX{} distribution with no macros +\href{http://wiki.contextgarden.net/Main_Page}{\acro{WIKI} site} and via the +\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 +\url{http://minimals.contextgarden.net/} --- it provides a \context{} system on any of a number of platforms, executing either -mark~ii or mark~iv \context{}. +mark~ii or mark~iv \context{}. + +Note that \acro{CTAN} does \emph{not} hold the primary distribution of +\context{}~--- potential users should refer to +\href{http://contextgarden.net}{\context{} `garden' site} for details +of the +current distribution. \acro{CTAN} holds a copy of \CONTeXT{} but +makes no claim about its ``up-to-date''ness. Likewise, \acro{CTAN} +holds a few contributed \context{} packages, but many more are to be +found via the \href{http://contextgarden.net}{\CONTeXT{} garden}. \begin{ctanrefs} \item[\nothtml{\rmfamily}\CONTeXT{} distribution]\CTANref{context} +\item[\nothtml{\rmfamily}\CONTeXT{} packages selection]\CTANref{context-contrib} \end{ctanrefs} -\LastEdit{2011-11-02} +\LastEdit{2014-05-30} \Question[Q-AMSpkg]{What are the \acro{AMS} packages (\AMSTeX{}, \emph{etc}.)?} @@ -863,10 +885,10 @@ For example, \Eplain{} does not have a command \csx{section}, which would format section headings in an ``appropriate'' way, as \LaTeX{}'s \csx{section} does. The philosophy of \Eplain{} is that some people will always need or want to go beyond the macro designer's -idea of ``appropriate''. Such canned macros are fine~--- as long as you +idea of ``appropriate''. Canned sets of macros are fine~--- as long as you are willing to accept the resulting output. If you don't like the -results, or if you are trying to match a different format, you are out -of luck. +results, or if you are trying to match a different format, you may +find that \Eplain{} is for you. On the other hand, almost everyone would like capabilities such as cross-referencing by labels, so that you don't have to put actual page @@ -902,7 +924,7 @@ browse the list archives, via \begin{ctanrefs} \item[\nothtml{\rmfamily}\Eplain{} distribution]\CTANref{eplain} \end{ctanrefs} -\LastEdit{2011-07-13} +\LastEdit{2013-06-25} \Question[Q-texinfo]{What is Texinfo?} @@ -937,15 +959,35 @@ Finally, of course, you can also print the files, or convert them to \item[\nothtml{\rmfamily}Texinfo distribution]\CTANref{texinfo} \end{ctanrefs} +\Question[Q-lollipop]{Lollipop} + +A long time ago (in the early 1990s), the Lollipop \tex{} format was +developed (originally to typeset the excellent book % !line break +\Qref{\tex{} by topic}{Q-tex-books}). Several people admired the +format, but no ``critical mass'' of users appeared, that could have +prompted maintenance of the format. + +More than 20 years later, a new maintainer appeared: he hopes to build +Lollipop into an engine for rapid document style development. (In +addition, he intends to add support for right-to-left languages such +as his own~--- Persian.) + +We can only hope that, this time, Lollipop will ``catch on''! +\begin{ctanrefs} +\item[lollipop]\CTANref{lollipop} +\end{ctanrefs} + \Question[Q-whyfree]{If \TeX{} is so good, how come it's free?} It's free because Knuth chose to make it so (he makes money from -royalties on his \TeX{} books, which still sell well). He is nevertheless -apparently happy that others should earn money by selling \TeX{}-based -services and products. While several valuable \TeX{}-related tools and -packages are offered subject to restrictions imposed by the \acro{GNU} -General Public Licence (\acro{GPL}, sometimes referred to as -`Copyleft'), \TeX{} itself is not subject to \acro{GPL}. +royalties on his \TeX{} books, which still sell well). He is +nevertheless apparently happy that others should earn money by selling +\TeX{}-based services and products. While several valuable +\TeX{}-related tools and packages are offered subject to restrictions +imposed by the \acro{GNU} General Public Licence (\acro{GPL}, +sometimes referred to as `Copyleft'), which denies the right to +commercial exploitation. \TeX{} itself is offered under a pretty +permissive licence of Knuth's own. There are commercial versions of \TeX{} available; for some users, it's reassuring to have paid support. What is more, some of the @@ -956,7 +998,7 @@ not available commercially.) This \acro{FAQ} concentrates on `free' distributions of \TeX{}, but we do at least list the \Qref*{major vendors}{Q-commercial}. -\LastEdit{2011-07-06} +\LastEdit{2013-06-25} \Question[Q-TeXfuture]{What is the future of \TeX{}?} @@ -998,17 +1040,31 @@ accessible to ``ordinary users''. \Question[Q-readtex]{Reading \AllTeX{} files} -So you've been sent a \TeX{} file: what are you going to do with it? +So you've been sent an \AllTeX{} file: what are you going to do with +it? + +You can, of course, ``just read it'', since it's a plain text file; +the problem is that the markup tags in the document may prove +distracting. Most of the time, even \TeX{} \emph{experts} will +typeset a \AllTeX{} file before attempting to read it\nobreakspace{}\dots{} + +So you shouldn't be too concerned if you can't make head nor tail of +the file: it is designed to be read by a (sort of) compiler, and +compilers don't have much in common with human readers. + +A possible next step is to try an on-line \latex{} editor. There are +many of these~--- a compilation of links may be found in % line break +\href{http://texblog.net/latex-link-archive/online-compiler/}{this blog post} -You can, of course, ``just read it'', since it's a plain text file, -but the markup tags in the document may prove distracting. Most of -the time, even \TeX{} experts will typeset a \TeX{} file before -attempting to read it. +Of that long list, the present author has only dabbled with +\href{https://www.writelatex.com/}{Write\latex{}}; it seems well +suited to simple `one-shot' use in this way. -So, you need to typeset the document. The good news is that \TeX{} -systems are available, free, for most sorts of computer; the bad news -is that you need a pretty complete \TeX{} system even to read a single -file, and complete \TeX{} systems are pretty large. +If no online compiler helps, you need to typeset the document +``yourself''. The good news is that \TeX{} systems are available, +free, for most sorts of computer; the bad news is that you need a +pretty complete \TeX{} system even to read a single file, and complete +\TeX{} systems are pretty large. \TeX{} is a typesetting system that arose from a publishing project (see \wideonly{``}\Qref[question]{what is \TeX{}}{Q-whatTeX}\wideonly{''}), @@ -1041,7 +1097,7 @@ system to read a document ``as intended''. Are you ``put off'' by all this?~--- remember that \tex{} is good at producing \acro{PDF}: why not ask the person who sent the \tex{} file to send an \acro{PDF} copy? -\LastEdit{2012-10-10} +\LastEdit{2014-05-21} \Question[Q-notWYSIWYG]{Why is \TeX{} not a \WYSIWYG{} system?} @@ -1140,32 +1196,25 @@ Some time ago, \acro{TUG} established a ``technical council'', whose task was to oversee the development of \TeX{}nical projects. Most such projects nowadays go on their way without any support from \acro{TUG}, but \acro{TUG}'s web site lists its -\htmlignore -\ifpdf + +\begin{hyperversion} \href{http://www.tug.org/twg.html}{Technical Working Groups (\acro{TWG}s)}. -\else +\end{hyperversion} +\begin{flatversion} Technical Working Groups (\acro{TWG}s: see \URL{http://www.tug.org/twg.html}). -\fi -\endhtmlignore -\begin{htmlversion} -\href{http://www.tug.org/twg.html}{Technical Working Groups (\acro{TWG}s)}. -\end{htmlversion} +\end{flatversion} \acro{TUG} has a reasonable claim to be considered a world-wide organisation, but there are many national and regional user groups, too; \acro{TUG}'s web site maintains a list of -\htmlignore -\ifpdf -\href{http://www.tug.org/lugs.html}{``Local User Groups'' (\acro{LUG}s)}. -\else +\begin{hyperversion} +href{http://www.tug.org/lugs.html}{``Local User Groups'' (\acro{LUG}s)}. +\end{hyperversion} +\begin{flatversion} ``local user groups'' (\acro{LUG}s: see \URL{http://www.tug.org/lugs.html}). -\fi -\endhtmlignore -\begin{htmlversion} -\href{http://www.tug.org/lugs.html}{``local user groups'' (\acro{LUG}s)}. -\end{htmlversion} +\end{flatversion} Contact \acro{TUG} itself via \URL{http://tug.org/contact} -LastEdit{2011-09-19} +LastEdit{2013-06-25} 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 9bece3e6f2d..36419bb1bf0 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.14 2012/11/10 14:25:12 rf10 Exp rf10 $ +% $Id: faq-biblio.tex,v 1.15 2014/01/28 18:17:36 rf10 Exp rf10 $ \section{Bibliographies and citations} @@ -97,19 +97,24 @@ styles are written is pretty obscure, and one would not recommend anyone who's not a confident programmer to write their own, though minor changes to an existing style may be within the grasp of many. -If your style isn't too `far out', you can probably generate it by -using the facilities of the \Package{custom-bib} bundle. This +If your style isn't too `far out', you can probably avoid programming +it by using the facilities of the \Package{custom-bib} bundle. The bundle contains a file \File{makebst.tex}, which runs you through a text menu -to produce a file of instructions, with which you can generate your +to produce a file of instructions, which you can then use to generate your own \extension{bst} file. This technique doesn't offer entirely new styles -of document, but the system's ``master \BibTeX{} styles'' already -offer significantly more than the \BibTeX{} standard set. +of document, but the \Package{custom-bib}'s ``master \BibTeX{} +styles'' already offer significantly more than the \BibTeX{} standard set. -An alternative, which is increassingly often recommended, to use +An alternative, which is increasingly often recommended, to use \Qref*{\Package{biblatex}}{Q-biblatex}. \Package{Biblatex} offers many hooks for adjusting the format of the output of your `basic' \bibtex{} style, and a collection of `contributed' styles have also -started to appear. +started to appear. Note.bowever There are not as many of +\Package{biblatex}'s contributed styles as there are for \bibtex{}, +and there is no \Package{custom-biblatex}, both of which suggest that +beginners' r\"ole models are hard to come by. As a result, beginners +should probably resist the temptation to write their own contributed +\package{biblatex} style. \begin{ctanrefs} \item[biblatex.sty]\CTANref{biblatex} \item[biblatex \nothtml{\normalfont}contributed styles]\CTANref{biblatex-contrib} @@ -386,10 +391,10 @@ There is good reason to use the \Package{url} or \Package{hyperref} packages in this context: \BibTeX{} has a habit of splitting lines it considers excessively long, and if there are no space characters for it to use as `natural' breakpoints, \BibTeX{} will -insert a comment (`\texttt{\textpercent}') character~\dots{}\@ which -is an acceptable character in an \acro{URL}. Any current version of the -\Package{url} or \Package{hyperref} package detects this -``\texttt{\textpercent}--end-of-line'' structure in its argument, and +insert a comment (`\texttt{\textpercent{}}') character~\dots{}\@ which +is an acceptable character in an \acro{URL}. Any current version of +either of the \Package{url} or \Package{hyperref} packages detects this +``\texttt{\textpercent{}}--end-of-line'' structure in its argument, and removes it. \begin{ctanrefs} \item[babelbib \nothtml{\rmfamily}bundle]\CTANref{babelbib} 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 dc0d8788dd6..113d1139e4e 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.31 2012/12/07 19:34:33 rf10 Exp rf10 $ +% $Id: faq-bits+pieces.tex,v 1.32 2014/01/28 18:17:36 rf10 Exp rf10 $ \section{Bits and pieces of \AllTeX{}} @@ -476,13 +476,13 @@ it is very thoroughly managed by the \Package{babel} package; use of \latex{} aims to be a general-purpose document processor. Such an aim could be achieved by a selection of instructions which would enable users to use \tex{} primitives, but such a procedure is considered too -inflexible (and probably too daunting for ordinary users), and so the +inflexible (and probably too daunting for ordinary users). Thus the designers of \latex{} created a model which offered an \emph{abstraction} of the design of documents. Obviously, not all documents can look the same (even with the defocussed eye of abstraction), so the model uses \emph{classes} of document. Base \latex{} offers five classes of document: \Class{book}, -\Class{report}, \Class{report}, \Class{article} and \Class{letter}. +\Class{report}, \Class{article} and \Class{letter}. For each class, \latex{} provides a \emph{class file}; the user arranges to use it via a \csx{documentclass} command at the top of the document. So a document starting @@ -500,17 +500,17 @@ existing class, and then does its own thing with the document design. If the user finds such a refined class, all is well, but if not, the common way is to load a \emph{package} (or several). -\latex{} provides rather few package files, but there are lots of them -to be found on the archives by a wide variety of authors; several -packages are designed just to adjust the design of a document~--- -using such packages achieves what the programmer might have achieved -by refining the class. +The \latex{} distribution, itself, provides rather few package files, +but there are lots of them, by a wide variety of authors, to be found +on the archives. Several packages are designed just to adjust the +design of a document~--- using such packages achieves what the +programmer might have achieved by refining the class. Other packages provide new facilities: for example, the -\Package{graphics} package (actually provided by the \latex{} team) -allows the user to load externally-provided graphics into a document, -and the \Package{hyperref} package enables the user to construct -hyper-references within a document. +\Package{graphics} package (actually provided as part of any \latex{} +distribution) allows the user to load externally-provided graphics +into a document, and the \Package{hyperref} package enables the user +to construct hyper-references within a document. On disc, class and package files only appear different by virtue of their name ``extension''~--- class files are called \File{*.cls} while @@ -524,6 +524,7 @@ everything was called a style (``document style'' or ``document style option''). It doesn't really matter that the nomenclature has changed: the important requirement is to understand what other people are talking about. +\LastEdit{2013-10-21} \Question[Q-whatenv]{What are \latex{} ``environments''} @@ -645,23 +646,48 @@ have to wrap it in a macro of its own: \Question[Q-dtx]{Documented \LaTeX{} sources (\extension{dtx} files)} -\LaTeXe{}, and most contributed macro packages, are now written in a -\Qref*{literate programming style}{Q-lit}, with source and +\LaTeXe{}, and many contributed \latex{} macro packages, are written +in a \Qref*{literate programming style}{Q-lit}, with source and documentation in the -same file. This format, known as `doc', in fact originated before the +same file. This format in fact originated before the days of the \LaTeX{} project as one of the ``Mainz'' series of -packages. A documented source file conventionally has the suffix +packages. A documented source file conventionally has the suffix \extension{dtx}, and will normally be `stripped' before use with -\LaTeX{}; an installation file (\extension{ins}) is normally provided, +\LaTeX{}; an installation (\extension{ins}) file is normally provided, to automate this process of removing comments for speed of loading. -To read the comments, you can run \LaTeX{} on the +If the \extension{ins} file is available, you may process \emph{it} +with \latex{} to produce the package (and, often, auxiliary files). + +Output should look something like: +\begin{quote} +\begin{verbatim} +Generating file(s) ./foo.sty + +Processing file foo.dtx (package) -> foo.sty +File foo.dtx ended by \endinput. +Lines processed: 2336 +Comments removed: 1336 +Comments passed: 2 +Codelines passed: 972 +\end{verbatim} +\end{quote} +The lines ``\texttt{Processing \dots{}\ ended by \csx{endinput}}'' may +be repeated if the \extension{dtx} file provides more than one +`unpacked' file. + +To read the comments ``as a document'', you can run \LaTeX{} on the \extension{dtx} file to produce a nicely formatted version of the -documented code. Several -packages can be included in one \extension{dtx} file (they're sorted -out by the \extension{ins} file), with conditional -sections, and there are facilities for indexes of macros, etc. +documented code. (Most \latex{} packages on \ctan{}, nowadays, already +have \acro{PDF} of the result of processing the \extension{dtx} file, +as ``documentation''.) + +Several packages may be included in one \extension{dtx} file, with +conditional sections, and there are facilities for indexes of macros, +etc. All of this m\'elange is sorted out by directives in the +\extension{ins} file; conventional indexing utilities may be necessary +for ``full'' output. -Anyone can write \extension{dtx} files; the format is explained in +Anyone may write \extension{dtx} files; the format is explained in \Qref*{The \LaTeX{} Companion}{Q-latex-books}, and a tutorial is available from \acro{CTAN} (which comes with skeleton \extension{dtx} and \extension{ins} files). @@ -714,7 +740,7 @@ thus permitting documented distribution of bundles containing code for \item[makedtx]\CTANref{makedtx} \item[sty2dtx]\CTANref{sty2dtx} \end{ctanrefs} -\LastEdit{2011-06-01} +\LastEdit{2014-06-03} \Question[Q-whatenc]{What are encodings?} 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 c569b151804..dbbdeb37c53 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.44 2012/12/07 19:34:33 rf10 Exp rf10 $ +% $Id: faq-docs.tex,v 1.46 2014/03/04 15:42:45 rf10 Exp rf10 $ \section{Documentation and Help} @@ -98,7 +98,10 @@ A collection of Knuth's publications about typography is also available: 2011, \ISBN*{1847199860}{978-1847199867}) \item[The \LaTeX{} Companion]by Frank Mittelbach, Michel Goossens, Johannes Braams, David Carlisle and Chris Rowley (second edition, - Addison-Wesley, 2004, \ISBN*{0-201-36299-6}{978-0-201-36299-2}) + Addison-Wesley, 2004, \ISBN*{0-201-36299-6}{978-0-201-36299-2}); the + book as also available as a digital download (in \acro{EPUB}, + \acro{MOBI} and \acro{PDF} formats) from + \url{http://www.informit.com/store/latex-companion-9780133387667} \item[The \LaTeX{} Graphics Companion:]% \emph{Illustrating documents with \TeX{} and \PS{}} by Michel Goossens, Sebastian Rahtz, Frank Mittelbach, Denis Roegel and @@ -115,10 +118,9 @@ A collection of Knuth's publications about typography is also available: % by George Gr\"atzer (third edition Birkh\"auser and Springer Verlag, % 2000, \ISBN{0-8176-4431-9}, \ISBN{3-7643-4131-9}) % \checked{RF}{2001/01/16} -\item[More Math into \latex{}:]\emph{An Introduction to \LaTeX{} and - \AMSLaTeX{}}by George Gr\"atzer (fourth edition Springer Verlag, +\item[More Math into \latex{}:]\emph{An Introduction to} \LaTeX{} + \emph{and} \AMSLaTeX{} by George Gr\"atzer (fourth edition Springer Verlag, 2007, \ISBN{978-0-387-32289-6} -\checked{RF}{2011-07-06} %% gr\"atzer's home page %% http://www.maths.umanitoba.ca/homepages/gratzer.html/LaTeXBooks.html \item[Digital Typography Using \LaTeX{}]Incorporating some @@ -160,7 +162,7 @@ Gr\"atzer's ``First Steps in \LaTeX{}'', are all available on %\item[\nothtml{\rmfamily}Examples for \nothtml{\upshape}\TeX{} in Practice]\CTANref{tip} \item[\nothtml{\rmfamily}Sample of \nothtml{\upshape}Math into \LaTeX{}]\CTANref{mil} \end{ctanrefs} -\LastEdit*{2011-09-09} +\LastEdit{2014-03-14} \Question[Q-other-books]{Books on other \tex{}-related matters} @@ -277,11 +279,11 @@ Both the Francophone \TeX{} user group Gutenberg and the Czech/Slovak user group CS-TUG have published translations of this \acro{FAQ}, with extensions appropriate to their languages. -Herbert Vo\ss {}'s excellent % beware line break -\href{http://texnik.de/}{\LaTeX{} tips and tricks} -provides excellent advice on most topics one might imagine (though -it's not strictly a \acro{FAQ})~--- highly recommended for most -ordinary mortals' use. +% Herbert Vo\ss {}'s excellent % beware line break +% \href{http://texnik.de/}{\LaTeX{} tips and tricks} +% provides excellent advice on most topics one might imagine (though +% it's not strictly a \acro{FAQ})~--- highly recommended for most +% ordinary mortals' use. The Open Directory Project (\acro{ODP}) maintains a list of sources of \AllTeX{} help, including \acro{FAQ}s. View the \TeX{} area at @@ -312,6 +314,7 @@ Resources available on \acro{CTAN} are: \CTANref{TeX-FAQ} \item[\nothtml{\rmfamily}The visual \acro{FAQ}]\CTANref{visualFAQ} \end{ctanrefs} +\LastEdit{2013-07-02} \Question[Q-gethelp]{Getting help online} @@ -383,11 +386,21 @@ mechanisms are: which offers a variety of `categories' to place your query, and the % the next line will tend to break if you add _anything_ to it! \href{http://tex.stackexchange.com/}{\TeX{}, \LaTeX{} and friends Q\&A site} - (``Stack exchange''). + (``StackExchange''). - Stack exchange has a scheme for voting on the quality of answers (and + StackExchange has a scheme for voting on the quality of answers (and hence of those who offer support). This arrangement is supposed to enable you to rank any answers that are posted. + + StackExchange offers + \href{http://meta.tex.stackexchange.com/questions/1436/welcome-to-tex-sx}{hints about ``good behaviour''}, + which any user should at least scan before asking for help there. + (The hints' principal aim is to maximise the chance that you get useful + advice from the first answer; for example, it suggests that you supply a + \Qref*{minimal example of your problem}{Q-askquestion}, just as + these \acro{FAQ}s do. There are people on the site who can be abrasive + to those asking questions, who seem not to be following the + guidelines for good behaviour) \end{enumerate} Do \textbf{not} try mailing the \LaTeX{} project team, the maintainers of the \texlive{} or \miktex{} distributions or the maintainers of @@ -398,7 +411,7 @@ are a far better bet. \begin{ctanrefs} \item[texhax \nothtml{\rmfamily}`back copies']\CTANref{texhax} \end{ctanrefs} -\LastEdit{2011-05-27} +\LastEdit{2014-01-28} \Question[Q-maillists*]{Specialist mailing lists} @@ -1142,12 +1155,12 @@ Geoffrey Tobin's \textit{\MF{} for Beginners} % !! line break (see \Qref[question]{using \MF{}}{Q-useMF}) describes how the \MF{} system works and how to avoid some of the potential pitfalls. -There is also an article on how to run both \MF{} and \MP{} (the -programs). Peter Wilson's % !! line break -\textit{Some Experiences in Running \MF{} and \MP{}} -offers the benefit of Peter's experience (he has designed a number of -`historical' fonts using \MF{}). For \MF{} the article is geared -towards testing and installing new \MF{} fonts, while its \MP{} +Peter Wilson's experience of running both \MF{} and \MP{} (the +programs), \textit{Some Experiences in Running \MF{} and \MP{}} +(available on \ctan{}) offers the benefit of Peter's experience (he +has designed a +number of `historical' fonts using \MF{}). For \MF{} the article is +geared towards testing and installing new \MF{} fonts, while its \MP{} 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. @@ -1157,17 +1170,23 @@ 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} -and \href{http://www.tlhiv.org/MetaPost/tutorial/}{Urs Oswald}, -and one in French (listed here because it's clearly enough written -that even this author understands it), by -\href{http://pauillac.inria.fr/~cheno/metapost/metapost.pdf}{Laurent Ch\'eno}; -both have been recommended for inclusion in the \acro{FAQ} +Another \MP{} tutorial in English is: % ! line breaks +\url{http://www.tlhiv.org/MetaPost/tutorial/} by Urs Oswald. +One in French (listed here because it's clearly enough written +that even this author understands it), +\url{http://pauillac.inria.fr/~cheno/metapost/metapost.pdf} +by Laurent Ch\'eno. + +Urs Oswald's tutorial uses Troy Henderson's tool +(\URL{http://www.tlhiv.org/mppreview}) for testing little bits of +\MP{}; it is an invaluable aid to the learner: +\URL{http://www.tlhiv.org/mppreview} -Urs Oswald's tutorial is accompanied by a super tool (by Troy -Henderson) for testing little bits of \MP{}, which is an invaluable -aid to the learner: \URL{http://www.tlhiv.org/mppreview} +A three-part introduction, by Mari Voipio, was published in +\href{http://tug.org/TUGboat/intromp/tb106voipio-grid.pdf}{\TUGboat34(1) (Entry-level \MP{}: On the grid)}, +\TUGboat34(2) +\href{http://tug.org/TUGboat/intromp/tb107voipio-moveit.pdf}{(Entry-level \MP{}: Move it!\@)}, and +\href{http://tug.org/TUGboat/intromp/tb108voipio-color.pdf}{\TUGboat34(2) (Entry-level \MP{}: Color)}. Vincent Zoonekynd's massive set of example \MP{} files is available on \acro{CTAN}; the set includes a \ProgName{Perl} script to convert the @@ -1182,7 +1201,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} +\LastEdit{2014-02-18} \Question[Q-BibTeXing]{\bibtex{} Documentation} @@ -1196,6 +1215,9 @@ also has information on \bibtex{} and writing \bibtex{} style files. (See \Qref[question]{\latex{} books}{Q-latex-books} for details of both books.) +The web site ``\href{http://www.bibtex.org}{Your \bibtex{} resource}'' +offers a solid introduction, but doesn't go into very great detail. + The document ``Designing \bibtex{} Styles'', also in the \bibtex{} distribution (look for \File{btxhak}), explains the postfix stack-based language used to @@ -1205,15 +1227,16 @@ is the template for the four standard styles (\Package{plain}, \Package{abbrv}, \Package{alpha}, and \Package{unsrt}); it also contains their documentation. -A useful tutorial of the whole process of using \BibTeX{} is Nicolas -Markey's ``\emph{Tame the BeaST (The B to X of \BibTeX{})}'', which +A useful tutorial of the whole process of using \bibtex{} is Nicolas +Markey's ``\emph{Tame the BeaST (The B to X of \bibtex{})}'', which may also be found on \acro{CTAN}. A summary and \acro{FAQ} by Michael Shell and David Hoadley, is also to be recommended. \begin{ctanrefs} -\item[\nothtml{\rmfamily}\BibTeX{} distribution]\CTANref{bibtex} +\item[\nothtml{\rmfamily}\bibtex{} distribution]\CTANref{bibtex} \item[\nothtml{\rmfamily}Shell and Hoadley's FAQ]\CTANref{bibtex-faq} \item[\nothtml{\rmfamily}Tame the BeaST]\CTANref{ttb-pdf} \end{ctanrefs} +\LastEdit{2013-10-15} \Question[Q-symbols]{Where can I find the symbol for\,\dots{}} \keywords{assignment circular integral degrees diagonal dots Fourier transform} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex index 8df28bb2915..1b6ddf3cf4c 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-dvi.tex @@ -1,4 +1,4 @@ -% $Id: faq-dvi.tex,v 1.1 2009/06/13 20:56:38 rf10 Exp $ +% $Id: faq-dvi.tex,v 1.2 2014/01/28 18:17:36 rf10 Exp rf10 $ \section{\acro{DVI} Drivers and Previewers} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex index 90430598750..d555e6f1a66 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-fmt-conv.tex @@ -1,4 +1,4 @@ -% $Id: faq-fmt-conv.tex,v 1.8 2012/12/07 19:34:33 rf10 Exp rf10 $ +% $Id: faq-fmt-conv.tex,v 1.10 2014/05/29 11:24:34 rf10 Exp rf10 $ \section{Format conversions} @@ -437,12 +437,17 @@ succeed at this task. See % ! line break ``\Qref*{How does \LaTeX{} relate to \plaintex{}}{Q-LaTeXandPlain}'' for further details. +Obviously, trivial documents will translate in a trivial way. +Documents that use even relatively simple things, such as labels and +references, are likely to cause trouble (\plaintex{} doesn't support +labels). While graphics are in principle covered, by the \plaintex{} + Translating a document designed to work with \LaTeX{} into one -designed to work with \plaintex{} is likely to amount to carefully +that will work with \plaintex{} is likely to amount to carefully including (or otherwise re-implementing) all those parts of \LaTeX{}, beyond the provisions of \plaintex{}, which the document uses. -Some of this work is has (in a sense) been done, in the port of the +Some of this work has (in a sense) been done, in the port of the \LaTeX{} graphics package to \plaintex{}. However, while \Package{graphics} is available, other complicated packages (notably \Package{hyperref}) are not. The aspiring translator may find the @@ -454,7 +459,7 @@ offer.) \begin{ctanrefs} \item[\nothtml{\begingroup\rmfamily}The\nothtml{\endgroup} eplain \nothtml{\rmfamily}system]% \CTANref{eplain} -\item[\nothtml{\begingroup\rmfamily`}\plaintex{}\nothtml{'\endgroup} graphics]% +\item[\nothtml{\begingroup\rmfamily'}\plaintex{}\nothtml{'\endgroup} graphics]% \CTANref{graphics-plain} \end{ctanrefs} -\LastEdit{2011-05-04}
\ No newline at end of file +\LastEdit{2011-05-30} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex index 8a34b2066d9..c60bce4f54a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-fonts.tex @@ -1,4 +1,4 @@ -% $Id: faq-fonts.tex,v 1.20 2012/11/24 10:56:03 rf10 Exp $ +% $Id: faq-fonts.tex,v 1.21 2014/01/22 17:29:03 rf10 Exp $ \section{Fonts} @@ -195,7 +195,8 @@ formats. The constraint is, of course, that your previewer and printer driver should support such fonts (\TeX{} itself \emph{only} cares about metrics, not the actual character programs). -If you also need mathematics, then you are severely limited by the +If you also need mathematics, then your choice is more limited, in +particular by the demands that \TeX{} makes of maths fonts (for details, see the papers by \begin{wideversion} @@ -210,12 +211,15 @@ by \URL{http://tug.org/TUGboat/Articles/tb14-3/tb40horn.pdf} or \URL{http://tug.org/TUGboat/Articles/tb19-2/tb59bouc.pdf}, respectively). \end{narrowversion} -For mathematics, then, there are rather few choices (though the list is -at last growing). There are several font families available that are -based on Knuth's original designs, and some that complement other -commercial text font designs; one set (MicroPress's `informal math') -stands alone. ``Free'' font families that will support \TeX{} -mathematics include: +There are several options available, which are +based on Knuth's original designs. Others complement other +commercial and free text font designs; one set (MicroPress's `informal math') +stands alone. + +Users should also consider the possibilities of typesetting +\Qref*{maths using OpenType fonts}{Q-otf-maths}. + +``Free'' font families that will support \TeX{} mathematics include: \begin{booklist} \item[Computer Modern](75 fonts~--- optical scaling) Donald E. Knuth\\ The \acro{CM} fonts were originally designed in \MF{}, but are also @@ -711,7 +715,58 @@ print file (\PS{} or \acro{PDF}) for their output device. \item[\nothtml{\normalfont}URW ``35 fonts'' collection]\CTANref{urw-base35} \item[utopia \nothtml{\normalfont}fonts]\CTANref{utopia} \end{ctanrefs} -\LastEdit{2013-04-11} +\LastEdit{2014-01-22} + +\Question[Q-otf-maths]{Unicode Maths using OpenType fonts} + +The \acro{ISO} standard Universal Coding Scheme (UCS), which is +commonly known as Unicode, was adopted early by the designers of +TrueType (\acro{TTF}) and OpenType (\acro{OTF}) fonts. The +flexibility of the fonts offers hope, for the first time, of a uniform +method for typesetting essentially any language. + +\tex{} users have been eagerly adopting the fonts, for some time, +using \xetex{} (now a rather stable system) and \luatex{} (which is, +at the time of writing, still being developed). + +While \tex{} users were investigating the use of these text fonts, +\acro{ISO} was extending Unicode to provide a means of expressing +mathematics. As this work proceeded, MicroSoft and (separately) a +consortium of publishing companies were developing OpenType maths +fonts. (Microsoft contributed on the development of the concepts, +within the \acro{ISO} process.) MicroSoft's OpenType Maths font, +\FontName{Cambria Math} has been available for purchase for some time. + +The first free OpenType Maths font to appear was % !line break +\FontName{Asana Math}, which was eventually followed by +the publishers' consortium's offer of an interim version +of their font, \FontName{STIX}, which has been +redeveloped to provide a more usable whole, \FontName{XITS}, by a group +of \tex{} users. + +Other fonts are appearing, including % ! line break +\FontName{TeX Gyre Termes Math} (based on Times-like fonts) and +\FontName{Tex Gyre Pagella Math} (based on Palatino-like fonts), +and \FontName{LM Math} extending the OpenType version of the +\FontName{Latin Modern} font family. + +Actually using a unicode maths font is quite a complicated business, +but the \latex{} package \Package{unicode-math} (supported +by the \Package{fontspec} package) does the essential groundwork. +\begin{ctanrefs} +\item[Asana-Math \nothtml{\rmfamily}font]\CTANref{asana-math}[asana-math] +\item[fontspec.sty]\CTANref{fontspec} +\item[lm-math \nothtml{\rmfamily}fonts]\CTANref{lm-math} +\item[STIX \nothtml{\rmfamily}fonts]\CTANref{stix} +\item[unicode-math.sty]\CTANref{unicode-math} +\item[tex-gyre-math-pagella \nothtml{\rmfamily}font]distributed as + part of \CTANref{tex-gyre-math}[tex-gyre-math-pagella] +\item[tex-gyre-math-termes \nothtml{\rmfamily}font]distributed as part + of \CTANref{tex-gyre-math}[tex-gyre-math-termes] +\item[XITS \nothtml{\rmfamily}fonts]\CTANref{xits} +\end{ctanrefs} +\LastEdit*{2014-01-22} +% more to come... \Question[Q-charshift]{Weird characters in \ProgName{dvips} output} \keywords{fi ligature pound pounds sterling elephants} @@ -986,6 +1041,49 @@ no support for using fonts according to the \acro{OT}1 encoding. \item[\nothtml{\rmfamily}Latin Modern fonts]\CTANref{lm} \end{ctanrefs} +\Question[Q-getnff]{Getting `free' fonts not in your distribution} + +Some fonts are free to use, but may not be sold. This creates a +dilemma for distributions: users may want the fonts, but since the +distribution is also available on a \acro{DVD} for sale, the fonts may +not be in the distribtution. + +The \acro{CTAN} archives hold such fonts, together with all the +necessary support files, but even with the support files ready-made, +installing a font is a tedious business. + +For \texlive{} users, this dilemma is solved by the +\ProgName{getnonfreefonts} script. Download the script installer from +\url{http://tug.org/fonts/getnonfreefonts/}; the web page tells you +how to run the installer to get the script, and what fonts are +currently available + +Once the script is installed, you can ask it what it has available by +saying: +\begin{quote} +\begin{verbatim} +getnonfreefonts -l +\end{verbatim} +\end{quote} +and you can ask it to install a font (in your local texmf tree) by: +\begin{quote} +\begin{verbatim} +getnonfreefonts luximono +\end{verbatim} +\end{quote} +(for example; the printed version of the \acro{FAQ} uses luximono, so +that the example was to hand\dots{}). + +(System adminstrators may use \ProgName{getnonfreefonts-sys}, which +will install the font in the `public' \texttt{texmf} tree, so that all +users of the system may use the new font.) + +The script will download the relevant font files from \acro{CTAN}, +extract them from their \extension{zip} file, install them and update +the font maps. It even goes so far as to apologise for how long it's +taking! +\LastEdit*{2013-10-22} + \subsection{\MF{} fonts} \Question[Q-useMF]{Getting \MF{} to do what you want} 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 f07eef697a8..8cdd9ccc5ba 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-getit.tex @@ -1,4 +1,4 @@ -% $Id: faq-getit.tex,v 1.10 2012/03/31 09:22:17 rf10 Exp rf10 $ +% $Id: faq-getit.tex,v 1.11 2014/01/22 17:29:03 rf10 Exp $ \section{Acquiring the Software} @@ -197,8 +197,8 @@ But how to find the files? Modern distributions (\texlive{} and \miktex{}, at least) provide the means to update your system ``over the net''. This is the minimum effort route to getting a new file: `simply' find which of the -distributions `packages' holds the file in question, and ask the -distribution to update it. The mechanisms are different (the two +distribution's `packages' holds the file in question, and ask the +distribution to update itself. The mechanisms are different (the two distributions exhibit the signs of evolutionary divergence in their different niches), but neither is difficult~--- see % ! line break ``\Qref*{using \miktex{} for installing}{Q-inst-miktex*}'' and % ! line break @@ -212,30 +212,32 @@ Some sources, such as these \acro{FAQ} answers, provide links to files: so if you've learnt about a package here, you should be able to retrieve it without too much fuss. -Otherwise, the \acro{CTAN} sites provide searching facilities, via the -web: at Dante with \URL{http://dante.ctan.org/search.html}, at -Cambridge with \URL{http://www.tex.ac.uk/search.html}. +Otherwise, \acro{CTAN} provides a full-text search, at its +\href{http://www.ctan.org/}{`central database'} site, as well as +topic- and author-based indexes and a link to browse the archive +itself. -Two search mechanisms are offered: the simpler search, locating files -by name, simply scans a list of files (\File{FILES.byname}~--- see -below) and returns a list of matches, arranged neatly as a series of -links to directories and to individual files. +% Two search mechanisms are offered: the simpler search, locating files +% by name, simply scans a list of files (\File{FILES.byname}~--- see +% below) and returns a list of matches, arranged neatly as a series of +% links to directories and to individual files. -The more sophisticated search looks at the contents of each catalogue -entry, and returns a list of catalogue entries that mention the -keywords you ask for. +% The more sophisticated search looks at the contents of each catalogue +% entry, and returns a list of catalogue entries that mention the +% keywords you ask for. An alternative way to scan the catalogue is to use the catalogue's % ! line break \href{http://mirrors.ctan.org/help/Catalogue/bytopic.html}{``by topic'' index}; -this lists a series of topics, and \AllTeX{} projects that are worth -considering if you're working on matters related to the topic. +this is an older mechanism than the topic-based search (above), but is +well presented (even though its data has not been updated for some time). In fact, \ProgName{Google}, and other search engines, can be useful tools. Enter your search keywords, and you may pick up a package that -the author hasn't bothered to submit to \acro{CTAN}. If you're using -\ProgName{Google}, you can restrict your search to \acro{CTAN} by -entering +the author hasn't bothered to submit to \acro{CTAN}. + +A user of \ProgName{Google} can restrict the search to +\acro{CTAN} by entering \begin{quote} \texttt{site:ctan.org tex-archive \meta{search term(s)}} \end{quote} @@ -249,11 +251,12 @@ file searches use. This file, \File{FILES.byname}, presents a unified listing of the archive (omitting directory names and cross-links). Its companion \File{FILES.last07days} is also useful, to keep an eye on the changes on the archive. Since these files are -updated only once a day, a nightly automatic download (perhaps using +updated only once a day, a nightly automatic download (using \ProgName{rsync}) makes good sense. \begin{ctanrefs} \item[FILES.byname]\CTANref{f-byname} \item[FILES.last07days]\CTANref{f-last7} +\LastEdit{2014-03-19} \end{ctanrefs} \Question[Q-findfont]{Finding new fonts} @@ -262,14 +265,15 @@ 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. +as ``\mf{} font list''.) -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}. +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 will only 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 +(those you have to pay for) 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 @@ -278,13 +282,22 @@ you are using; roughly speaking: \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. + While a new font will need `generating' (by running \mf{}, etc.), + distributions are set up to do that ``on the fly'' and to save the + results (for next time). \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 + metric (\extension{afm}) files; \extension{map} files also need to + be created. Such fonts will work with \pdftex{}, and with the + (`vanilla')\alltex{} and \ProgName{dvips} combination. +\item TrueType fonts can be made to work with \pdftex{}~--- see +% ! line break +\href{http://www.radamir.com/tex/ttf-tex.htm}{Using TrueType fonts with \tex{}\dots{}} + (a rather dated document, dicsussing use with \miktex{}~1.11). \item TrueType and OpenType fonts are the usual sort used by \xetex{} - and \luatex{}; they ``just work'' with those engines. + and \luatex{}; while straightforward use is pretty easy, one is + well-advised to use a package such as \Package{fontspec} to gain + access to the full range of a font's capabilities. \end{itemize} The answer ``\Qref*{choice of scalable fonts}{Q-psfchoice}'' discusses @@ -292,9 +305,10 @@ 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. \begin{ctanrefs} +\item[fontspec.sty]\CTANref{fontspec} \item[\nothtml{\rmfamily}\MF{} font list]\CTANref{mf-list} \end{ctanrefs} -\LastEdit{2012-03-27} +\LastEdit{2014-01-21} \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 2509894cfbb..bd90cc183cf 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.26 2012/11/24 10:56:03 rf10 Exp $ +% $Id: faq-graphics.tex,v 1.27 2014/01/22 17:29:03 rf10 Exp $ \section{Graphics} @@ -748,8 +748,7 @@ of drawing, and setup, here are a few systems you may consider: contributed packages, ranging from world mapping to lens design diagrams, is available). \Package{Pstricks}' \csx{special}s are - by default specific to \ProgName{dvips}, but V\TeX{} (both in its - commercial and in its free versions) understands them, and there is + by default specific to \ProgName{dvips}, but there is a \Package{Pstricks} `driver' that allow \Package{Pstricks} to operate under \xetex{}. \PDFTeX{} users may use \Package{pst-pdf}, which (like \Package{epstopdf}~--- see % ! line break @@ -918,8 +917,11 @@ 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). -Placing labels on graphics produced by all those \emph{other} tools is -what we discuss here. +Placing `labels' on graphics produced by all those \emph{other} tools is +what we discuss here. (Note that the term ``label'' should be +liberally interpreted; many of the techniques \emph{were} designed for +use when applying labels to figures, but they may be used equally well +to draw funny faces on a figure \dots{} or anything. The time-honoured \Package{psfrag} package can help, if your image is included as an (encapsulated) \PS{} file. Place an unique @@ -933,15 +935,27 @@ 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 -\Qref*{\Package{pst-pdf} package}{Q-pdftexgraphics} can support such -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, % ! line break -\Qref*{V\TeX{}'s GeX processor}{Q-commercial} explicitly deals with -\Package{psfrag}, both in its free and commercial instances. +it needs extra work for use with \PDFLaTeX{}. Two techniques are +available, using \Qref*{\Package{pst-pdf} package}{Q-pdftexgraphics} +in a mode designed to do this work; and using \Package{pdfrack}. + +The \Qref*{\Package{Pst-pdf} package}{Q-pdftexgraphics} can support +this ``extra work'' usage. In fact, the \Package{pst-pdf} support +package \Package{auto-pst-pdf} offers a configuration setting +precisely for use with \Package{psfrag}. + +If you have the `right' environment (see below), you could try the +\Package{pdfrack} script bundle. The script aims to cut each figure +out of your source, using it to produce a small \latex{} file with +nothing but the figure inclusion commands. Each of these figure files +is then processed to \PS{}, compiled using the \csx{psfrag} commands, +and the resulting output converted to \acro{PDF} again. + +\Package{Pdfrack} is written to use the Unix Bourne shell (or +equivalent); thus your environment needs to be a Unix-based system, or +some equivalent such as \ProgName{cygwin} under windows. (What is +more, \Package{pdfrack}'s author is rather disparaging about his +package; the present author has never tried it.) The \Package{psfragx} package goes one step further than \Package{psfrag}: it provides a means whereby you can put the @@ -1009,6 +1023,7 @@ with the do-it-yourself approach. \item[laprint]Distributed with \CTANref{psfragx} \item[lpic.sty]\CTANref{lpic} \item[overpic.sty]\CTANref{overpic} +\item[pdfrack]\CTANref{pdfrack} \item[pinlabel.sty]\CTANref{pinlabel} \item[pgf.sty]\CTANref{pgf} \item[psfrag.sty]\CTANref{psfrag} 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 f2fbfb63e86..ac61e60ef24 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.45 2012/12/07 19:34:33 rf10 Exp rf10 $ +% $Id: faq-how-do-i.tex,v 1.47 2014/01/28 18:17:23 rf10 Exp $ \section{How do I do\dots{}?} @@ -279,10 +279,6 @@ The \Package{yhmath} package defines an \csx{adots} command, which is the analogue of \csx{ddots}, sloping forwards rather than backwards. The \Package{yhmath} package comes with a rather interesting font that extends the standard \Package{cmex}; details are in the documentation. -The disadvantage of this setup is, that although \csx{adots} is merely -a macro, the package tries to load its own font and produces a -``missing font'' substitution warning message if you haven't installed -the font. The \Package{mathdots} package (besides fixing up the behaviour of \AllTeX{} \csx{ddots} and \csx{vdots} when the font size changes) @@ -297,9 +293,9 @@ before being able to read the documentation). Documentation of \item[amslatex]\CTANref{amslatex} \item[graphics.sty]Part of the \CTANref{graphics} bundle \item[mathdots.sty]\CTANref{mathdots} -\item[yhmath \nothtml{\rmfamily}(fonts)]\CTANref{yhmath-fonts} -\item[yhmath \nothtml{\rmfamily}(macros)]\CTANref{yhmath-macros} +\item[yhmath]\CTANref{yhmath} \end{ctanrefs} +\LastEdit{2013-08-21} \Question[Q-limits]{Sub- and superscript positioning for operators} @@ -2184,12 +2180,13 @@ single float page is likely (at the least) to be rather tricky. This is of course a contradiction: \environment{figure} and \environment{table} are \emph{designed} to float, and will always have the potential to appear away from where you asked for them. Therefore -you have to find a means of getting the caption and other effects -without allowing the figure or table to float. +you need something that behaves like a \environment{figure} or +\environment{table} environment, except that it doesn't allow the +figure or table to float. -The most straightforward way is to use one of the \Package{float} or -\Package{here} packages; they give you a \texttt{[H]} float placement -option that prevents floating: +The most straightforward way is to use of the \Package{float} package; +it gives you a \texttt{[H]} float placement option that prevents +floating: \begin{quote} \begin{verbatim} \begin{figure}[H] @@ -2200,8 +2197,10 @@ option that prevents floating: \end{figure} \end{verbatim} \end{quote} -As the example shows, these \texttt{[H]} figures (and correspondingly, -tables) offer all you need to cross-reference as well as typeset. +As the example suggests, such a `\texttt{[H]}' figure (or +corresponding table) offers all you need to cross-reference as well +as typeset. (The package \Package{here} provides the same function, +but is no longer recommended.) However, you don't actually \emph{have} to use \Package{float} (or \Package{here}) since it is, in fact, doing rather little for you. @@ -2215,8 +2214,8 @@ You can place your figure as you please, with a sequence like \end{center} \end{verbatim} \end{quote} -which relies on the \csx{captionof} command to place a caption in -ordinary running text. That command may be had from the extremely +which relies on the \csx{captionof} command to place a caption without +benefit of an enclosing float. That command may be had from the extremely simple-minded package \Package{capt-of} or from the highly sophisticated \Package{caption} package. @@ -2251,7 +2250,7 @@ and the sequence of float numbers is all correct. \item[caption.sty]\CTANref{caption} \item[float.sty]\CTANref{float} \item[here.sty]\CTANref{here} -\item[perpage.sty]Distributed as part \CTANref{bigfoot}[perpage] +\item[perpage.sty]Distributed as part of \CTANref{bigfoot}[perpage] \end{ctanrefs} \subsection{Footnotes} @@ -2803,7 +2802,7 @@ has application in document exchange situations too. The \ProgName{bundledoc} system uses the \Package{snapshot} to produce an archive (e.g., \extension{tar.gz} or \extension{zip}) of the files needed by your document; it comes with configuration files for use with -\ProgName{teTeX} and \ProgName{\miktex{}}. It's plainly useful when +\texlive{}-\ProgName{Unix} 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', @@ -2816,6 +2815,7 @@ which may then be saved for transmission or archiving. \item[mkjobtexmf]\CTANref{mkjobtexmf} \item[snapshot.sty]\CTANref{snapshot} \end{ctanrefs} +\LastEdit{2014-01-26} \Question[Q-changebars]{Marking changed parts of your document} @@ -3013,10 +3013,10 @@ content will be excluded from the document. The package uses a method for exclusion that is pretty robust, and can cope with ill-formed bunches of text (e.g., with unbalanced braces or \csx{if} commands). -These FAQs employ the \Package{comment} package to alter layout +(These FAQs employ the \Package{comment} package to alter layout between the printed (two-column) version and the \acro{PDF} version for browsing; there are \environment{narrowversion} and -\environment{wideversion} for the two versions of the file. +\environment{wideversion} for the two versions of the file.) \Package{version} offers similar facilities to \File{comment.sty} (i.e., \csx{includeversion} and \csx{excludeversion} commands); @@ -3066,8 +3066,41 @@ environments named in its argument. So, for example: \end{verbatim} \end{quote} -A further valuable twist is offered by the \Package{extract} package. -This allows you to produce a ``partial copy'' of an existing document: +The \Package{tagging} package offers another neat set of syntax, which +allow the user to apply ``tags'' to chunks of text, and to include and +exclude tagged text, according to the tags. For example, the user may +`use' text marked with some tags, and to `drop' marked with others: +\begin{quote} +\begin{verbatim} +\usetag{<tag list>} +\droptag{<tag list>} +\end{verbatim} +\end{quote} +(the tag lists consist of comma-separated single words). + +There are then commands +\begin{quote} +\begin{verbatim} +\tagged{<tag list>}{<text>} +\end{verbatim} +\end{quote} +which reproduces the text only if the \meta{tag list} contains at +least one tag listed in the \csx{usetag} comand, and +\begin{quote} +\begin{verbatim} +\untagged{<tag list>}{<text>} +\end{verbatim} +\end{quote} +which only reproduces the text unless the \meta{tag list} contains +none of the tags mention in the \csx{droptag} command. + +Further commands offer an if-then-else setup, and specify +\environment{taggedblock} and \environment{untaggedblock} environments +that. + +Another valuable aspect of the problem is covered by the +\Package{extract} package. The package allows you to produce a +``partial copy'' of an existing document: the package was developed to permit production of a ``book of examples'' from a set of lecture notes. The package documentation shows the following usage: @@ -3101,12 +3134,13 @@ ready-to-run \LaTeX{} documents with stuff you've extracted. \item[pdfpages.sty]\CTANref{pdfpages} \item[selectp.sty]\CTANref{selectp} \item[stampinclude.sty]Distributed as part of \CTANref{oberdiek}[stampinclude] +\item[tagging.sty]\CTANref{tagging} \item[verbatim.sty]Distributed as part of \CTANref{2etools}[verbatim] \item[version.sty]\CTANref{version} \item[versions.sty]\CTANref{versions} \item[xcomment.sty]\CTANref{xcomment} \end{ctanrefs} -\LastEdit{2012-11-28} +\LastEdit{2014-06-09} \Question[Q-docotherdir]{Bits of document from other directories} @@ -3199,8 +3233,8 @@ following minimal solution: \begin{wideversion} \begin{verbatim} \def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}} -\RCS$Revision: 1.45 $ % or any RCS keyword -\RCS$Date: 2012/12/07 19:34:33 $ +\RCS$Revision: 1.47 $ % or any RCS keyword +\RCS$Date: 2014/01/28 18:17:23 $ ... \date{Revision \RCSRevision, \RCSDate} \end{verbatim} @@ -3210,8 +3244,8 @@ following minimal solution: \def\RCS$#1: #2 ${\expandafter \def\csname RCS#1\endcsname{#2}% } -\RCS$Revision: 1.45 $ % or any RCS keyword -\RCS$Date: 2012/12/07 19:34:33 $ +\RCS$Revision: 1.47 $ % or any RCS keyword +\RCS$Date: 2014/01/28 18:17:23 $ ... \date{Revision \RCSRevision, \RCSDate} \end{verbatim} @@ -3454,9 +3488,8 @@ So what else can go wrong? ordinarily recommend\dots{} The \Package{hyphenat} package defines a bundle of such commands (for introducing hyphenation points at various punctuation characters). -\item There may be accents in the word. The causes of and remedies - for this effect are discussed in - % beware line break +\item There may be accent commands in the word. The causes of and + remedies for this effect are discussed in % !line break \Qref[question]{accents and hyphens}{Q-hyphenaccents}. \item The hyphenation may simply not have been spotted; while \TeX{}'s algorithm is good, it's not infallible, and it does miss perfectly @@ -3476,6 +3509,7 @@ hyphenation; some feel the American hyphenation feels \begin{ctanrefs} \item[hyphenat.sty]\CTANref{hyphenat} \end{ctanrefs} +\LastEdit{2013-09-20} \Question[Q-weirdhyphen]{Weird hyphenation of words} @@ -3741,22 +3775,25 @@ the penalties instead. If you simply switch off hyphenation for a good bit of text, the output will have a jagged edge (with many lines seriously overfull), and your \AllTeX{} run will bombard you with warnings about overfull -and underfull lines. To avoid this you have two options. +and underfull boxes (that is, really, lines). To avoid this you have +two options. The simplest route is to use \csx{sloppy} (or its environment version \environment{sloppypar}), and have \TeX{} stretch what would otherwise be underfull lines to fill the space offered, while prematurely wrapping overfull lines and stretching the remainder. -Alternatively, you may set the text \Qref*{ragged right}{Q-ragright}, +The better bet is to set the text \Qref*{ragged right}{Q-ragright}, and at least get rid of the overfull lines; this technique is -`traditional' (in the sense that typists do it) and may be expected to +`traditional' (in the sense that typists have always done it) and may +be expected to appeal to the specifiers of eccentric document layouts (such as those for dissertations), but for once their sense conforms with typographic style. (Or at least, style constrained in this curious way.) \begin{ctanrefs} \item[hyphenat.sty]\CTANref{hyphenat} \end{ctanrefs} +\LastEdit{2013-09-20} \Question[Q-wdnohyph]{Preventing hyphenation of a particular word} @@ -3774,8 +3811,8 @@ If the word occurs in just one place, put it in a box: of paragraphs.) However, boxing the word is not really advisable unless you are sure it only occurs once. -If the word occurs commonly, the best choice is to assert a -non-hyphenation for it: +If the word occurs commonly, the best choice is to assert an +hyphenation exception for it: \begin{quote} \begin{verbatim} \hyphenation{oddword} @@ -3802,7 +3839,7 @@ A particular instance of this requirement is avoiding the hyphenation of acronyms; a general rule for those that concoct acronyms seems to be to make the capital-letter sequence read as near as is possible like a ``real'' word, but hyphenating an acronym often looks silly. -The \TeX{} flag \csx{uchyph} is designed for suppressing such +The \TeX{} control \csx{uchyph} is designed for suppressing such behaviour: \begin{quote} \begin{verbatim} @@ -3855,8 +3892,8 @@ select the appropriate language, and do the same as above: \end{quote} (nothing clever here: this is the ``correct'' hyphenation of the word, in the current tables). However, there's a problem here: just as -words with accents in them won't break, so \csx{hyphenation} commands -with accents in them produce an error: +words with accent macros in them won't break, so an \csx{hyphenation} +commands with accent macros in its argument will produce an error: \begin{quote} \begin{verbatim} \usepackage[french]{babel} @@ -3868,7 +3905,7 @@ tells us that the hyphenation is ``improper'', and that it will be ``flushed''. But, just as hyphenation of words is enabled by selecting an 8-bit font encoding, so \csx{hyphenation} commands are rendered proper again by selecting that same 8-bit font encoding. For the hyphenation -patterns provided in the usual distributions, the encoding is +patterns provided for `legacy', the encoding is \Qref*{Cork}{Q-ECfonts}, so the complete sequence is: \begin{quote} \begin{verbatim} @@ -3878,13 +3915,19 @@ patterns provided in the usual distributions, the encoding is \hyphenation{r\'e-f\'e-rence} \end{verbatim} \end{quote} - The same sort of performance goes for any language for which 8-bit fonts and corresponding hyphenation patterns are available. Since you have to select both the language and the font encoding to have your document typeset correctly, it should not be a great imposition to do the selections before setting up hyphenation exceptions. +Modern TeX variants (principally \xetex{} and \luatex{}) use unicode, +internally, and distributions that offer them also offer +\acro{UTF}-8-encoded patterns; since the hyphenation team do all the +work ``behind the scenes'', the use of Unicode hyphenation is +deceptively similar to what we are used to. +\LastEdit{2013-09-20} + \subsection{Odds and ends} \Question[Q-logos]{Typesetting all those \TeX{}-related logos} 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 6d1b36bea0f..aa670393d9b 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,4 +1,4 @@ -% $Id: faq-hyp+pdf.tex,v 1.1 2013/05/31 22:58:09 rf10 Exp rf10 $ +% $Id: faq-hyp+pdf.tex,v 1.8 2014/02/16 21:23:58 rf10 Exp $ \section{Hypertext and \acro{PDF}} @@ -20,11 +20,7 @@ For simple documents (with no hyper-references), you can either \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. + \Qref{\luatex{}}{Q-luatex}, or \Qref{\xetex{}}{Q-xetex}. \end{itemize} To translate all the \LaTeX{} cross-referencing into Acrobat @@ -82,7 +78,7 @@ doesn't make the same <mistake. \item[hyper.sty]\CTANref{hyper} \item[hyperref.sty]\CTANref{hyperref} \end{ctanrefs} -\LastEdit{2012-03-28} +\LastEdit{2014-01-22} \Question[Q-hyper]{Making hypertext documents from \TeX{}} @@ -527,7 +523,7 @@ The two options in question are: formatted form of the page number. With this option, \Package{hyperref} writes different anchors for pages `ii' and `2'. (This is the default value for the option, which is a % ! line break - \emph{good thing}\dots) + \emph{good thing}\dots{}) If the option is set `\texttt{true}' \Package{hyperref} writes page anchors as the arabic form of the page number, rather than the formatted form that gets printed; this is not usually appropriate. @@ -549,39 +545,64 @@ will happen in this case, regardless of the options. \item[hyperref.sty]\CTANref{hyperref} \end{ctanrefs} -\Question[Q-srchpdf]{Searching \acro{PDF} files} - -In principle, you can search a \acro{PDF} file: the text of the file -is available to the viewer, and at least some viewers provide a search -facility. (It's not the fastest thing in the world, but it does help -in some circumstances.) - -However, there is a problem: the viewer wants to look at Unicode text, -but no ordinary \TeX{}-based system deals in Unicode text. -Fortunately for us Anglophones, this is is hardly ever a problem for -our text, since even Knuth's ``\acro{OT}1'' encoding matches ASCII (and hence -the lowest 128 characters of Unicode) for most things printable. -However, using the inflected characters of Continental European -languages, or anything that doesn't use a Latin alphabet, there is -potential for problems, since \TeX{}'s view of what a font is doesn't -map \acro{PDF}'s and the reader won't understand\dots{} - -\dots{} Unless you use the \Package{cmap} package with \PDFLaTeX{}, -that is. The package will instruct \PDFTeX{} to load character -maps into your \acro{PDF} for output fonts encoded according to the \acro{T}1 -(Western European Languages), T2A, T2B, or T2C (Cyrillic Languages), -or T5 (Vietnamese) encodings. If your document uses such encodings, -viewers that can search will use the maps to interpret what they find -in the file. - -Unfortunately, the package only works with fonts that are directly -encoded, such as the \FontName{cm-super} distribution. Fonts like Adobe +\Question[Q-cpy-srchpdf]{Copy-paste-able/searchable \acro{PDF} files} + +\acro{PDF} files generated from \tex{} (and friends), will by default +hold their text in the encoding of the original \tex{} font used by +the document. + +When \acro{PDF} readers, etc., offer copy-paste or searching +functions, the operations take place on the glyph codes used for the +fonts selected by the document. This is fine, for the simplest +documents (in English, at least); the problem comes when you're using +an inflected language (with accented letters, or composite glyphs +such as `\ae{}')~--- \tex{} will typically use a non-standard +encoding, and there are likely be problems, since \acro{PDF} readers +assume the text is presented in Unicode. + +For \acro{PDF} generated from \latex{} (the \acro{DVI} being +converted, by whatever means), or from \pdflatex{}, the character +codes used in the \acro{PDF} file are in fact those of the document's +\Qref*{font encoding}{Q-whatenc}; if you're using \acro{OT}1 or +\acro{T}1, your document will be \acro{OK} for almost all \acro{ASCII} +characters, but it's likely that anything ``out of the ordinary'' will +not be represented properly. (Of course, \acro{PDF} generated from +\xetex{}- or \luatex{}-based formats is going to be \acro{OK}, since +those engines work in Unicode througout.) + +The solution comes from the character-mapping facilities in the +\acro{PDF} specification: the file may specify a table of translations +of characters present in the coding used in the file, to a Unicode +version of the characters. + +Packages \Package{cmap} and \Package{mmap} both offer means of +generating such tables (\Package{mmap} has wider coverage, including +the various maths encodings); both work with \pdftex{} and no other +engine. Thus your document becomes something like: +\begin{quote} +\begin{verbatim} +\documentclass{article} +\usepackage{mmap} % (or cmap) +\usepackage[T1]{fontenc} +... % your other packages +\begin{document} +... % your actual text +\end{verbatim} +\end{quote} + +Unfortunately, the packages only work with fonts that are directly +encoded, such as the default (Computer Modern, i.e., \FontName{cm} +fonts, and things such as \FontName{cm-super} or the \FontName{Latin} +\FontName{Modern} sets. Fonts like Adobe Times Roman (which are encoded for \AllTeX{} use via virtual fonts) are not amenable to this treatment. \begin{ctanrefs} \item[cmap.sty]\CTANref{cmap} \item[cm-super \nothtml{\rmfamily}fonts]\CTANref{cm-super} +\item[\nothtml{\rmfamily}Latin Modern fonts]\CTANref{lm} +\item[mmap.sty]\CTANref{mmap} \end{ctanrefs} +\LastEdit{2013-08-21} % \Question[Q-hypertex]{The Hyper\tex{} project} % 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 3e4eeab62c8..7c01b80fcf1 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.16 2012/02/08 21:59:32 rf10 Exp rf10 $ +% $Id: faq-install.tex,v 1.17 2014/01/28 18:17:36 rf10 Exp rf10 $ \section{Installing \AllTeX{} files} @@ -681,7 +681,7 @@ TEXMF = !!$TEXMFMAIN \end{verbatim} \end{quote} but, there are likely to be several alternative settings behind -comment markers (``\texttt{\textpercent}''), and the person who +comment markers (``\texttt{\textpercent{}}''), and the person who installed your system may have left them there. Whatever, you need to modify the line that's in effect: change the above to three lines: \begin{quote} 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 e69784d3fd6..6d82072690f 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.4 2013/05/31 22:58:09 rf10 Exp rf10 $ +% $Id: faq-intro.tex,v 1.31 2014/01/28 18:17:36 rf10 Exp rf10 $ % this environment is for the benefit of new-style file generation \begin{introduction} @@ -18,7 +18,7 @@ answered questions is therefore in a state of slow flux: new questions are answered, while old questions are deleted~\dots{}~but the whole process depends on the time available for \acro{FAQ} maintenance. -\noindent You may use the \acro{FAQ} +\nothtml{\noindent} You may use the \acro{FAQ} \begin{itemize} \item by reading a printed document, \item by viewing a \acro{PDF} file, with hyperlinks to assist @@ -106,9 +106,10 @@ Giuseppe Bilotta, Charles Cameron, Fran\c{c}ois Charette, % update of q-xetex Damian Cugley, +Martin Garrod, % two consecutive "report" in clsvpkg Michael Dewey, Michael Downes, % (RIP) on (ams)maths stuff -Jean-Pierre Drucbert, % corrected my interpretation of minitoc +Jean-Pierre Drucbert, % (RIP) corrected my interpretation of minitoc David Epstein, % comment on q-algorithms, suggestion of tex-sx Michael Ernst, % alert on confusing colloquialism Thomas Esser, @@ -152,6 +153,7 @@ Sanjoy Mahajan, Diego Andres Alvarez Marin, % suggestion of lacheck Andreas Matthias, % most recently q-isitanum Steve Mayer, % proof reading +Javier Mora, % bug in q-cmdstar Brooks Moses, % editorial suggestion Peter Moulder, % improvement of q-widows Iain Murray, % alternative solution in q-hyperdupdest @@ -192,9 +194,10 @@ and Reinhard Zierke. That list does \emph{not} cover the many people whose ideas were -encountered on various lists, newsgroups or (lately) web forums. Many +encountered on various mailing lists, in newsgroups, or (more +recently!) in web forums. Many such people have helped, even if simply to highlight an area in which \acro{FAQ} work would be useful. \endhtmlignore -% \LastEdit{2013-04-29} % not to be typeset or converted to html... +% \LastEdit{2013-08-20} % not to be typeset or converted to html... \end{introduction} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-jot-err.tex index 598b70649a9..3281e54a18e 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.24 2013/04/18 23:01:08 rf10 Exp rf10 $ +% $Id: faq-jot-err.tex,v 1.25 2014/01/28 18:17:36 rf10 Exp rf10 $ \section{The joy of \TeX{} errors} @@ -1850,10 +1850,12 @@ there is probably something wrong with the class file. \end{verbatim} \end{wideversion} \end{quote} -is reporting something pretty fundamental (document base font size not -set up). While this \emph{can}, as the message implies, be due to a -broken class file, the more common cause is that you have simply -forgotten to put a \csx{documentclass} command in your document. +reports something pretty fundamental (document base font size has not +been set, something the document class does for you). It \emph{can}, +in principle, be a problem with the document class, but is more often +caused by the user forgetting to start their document with a +\csx{documentclass} command. +\LastEdit{2013-11-20} \Question[Q-manymathalph]{Too many math alphabets} @@ -2178,6 +2180,49 @@ This author has also encountered the error when developing macros that used the \LaTeX{} internal float mechanisms. Most people doing that sort of thing are expected to be able to work out their own problems\dots{} +\Question[Q-parmoderr]{Not in outer par mode} + +For example: +\begin{quote} +\begin{verbatim} +*\mbox{\marginpar{foo}} + +! LaTeX Error: Not in outer par mode. +\end{verbatim} +\end{quote} +The error comes when you try to build something movable inside a box. +Movable things, in this context, are floating environments +(\environment{figure} and \environment{table}, for example), and +\csx{marginpar}s. \latex{} simply doesn't have the mechanisms for +floating out of boxes. In fact, floats and \csx{marginpar}s +themselves are built out of boxes, so that they can't be nested. + +If your error arises from \csx{marginpar}, you simply have to think of +an alternative way of placing the command; there is no slick solution. + +If a floating environment is the culprit, it may be possible to use +the ``\texttt{H}'' placement option, provided (for example) by the +\Package{float} package: +\begin{quote} +\begin{verbatim} +\parbox{25cm}{% + \begin{figure}[H] + ... + \caption{Apparently floating...} + \end{figure}% +} +\end{verbatim} +\end{quote} +This example makes little sense as it stands; however, it is +conceivable that sane uses could be found (for example, using a +package such as \Package{algorithm2e} to place two algorithms +side-by-side). +\begin{ctanrefs} +\item[algorithm2e.sty]\CTANref{algorithm2e} +\item[float.sty]\CTANref{float} +\end{ctanrefs} +\LastEdit{2013-09-09} + \Question[Q-texorpdf]{Token not allowed in PDFDocEncoded string} The package \Package{hyperref} produces this error when it doesn't 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 5bf2b098691..e9a881ba2a5 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.33 2012/12/07 19:34:33 rf10 Exp rf10 $ +% $Id: faq-mac-prog.tex,v 1.35 2014/01/28 18:17:36 rf10 Exp rf10 $ \section{Macro programming} @@ -984,7 +984,7 @@ appeared on \Newsgroup{comp.text.tex}: (the original appeared on a single line: it's wrapped here to fit in the printed \acro{FAQ}'s narrow columns). -\noindent +\nothtml{\noindent} \end{narrowversion} \begin{wideversion} \begin{quote} @@ -1020,8 +1020,8 @@ meaning of its various parts; unfortunately the meaning was rather lost in the problems the macro caused. The principal technique for suppressing spaces is the use of -\texttt{\textpercent} characters: everything after a -\texttt{\textpercent} is ignored, even the end of line itself (so +\texttt{\textpercent{}} characters: everything after a +\texttt{\textpercent{}} is ignored, even the end of line itself (so that not even the end of line can contribute an unwanted space). The secondary technique is to ensure that the end of line is preceded by a command name (since the end of line behaves like a space, it will be @@ -1048,18 +1048,18 @@ easier to blindly suppress spaces than to analyse at every point whether you actually need to. Three techniques were used to suppress spaces: \begin{itemize} -\item placing a \texttt{\textpercent} character at the end of a line +\item placing a \texttt{\textpercent{}} character at the end of a line (as in the 1st, 3rd and 5th lines), \item ending a line `naturally' with a control sequence, as in line 2, and \item ending a line with an `artificial' control sequence, as in line 4; the control sequence in this case (\csx{relax}) is a no-op in many circumstances (as here), but this usage is deprecated~--- a - \texttt{\textpercent} character would have been better. + \texttt{\textpercent{}} character would have been better. \end{itemize} Beware of the (common) temptation to place a space \emph{before} a -\texttt{\textpercent} character: if you do this you might as well omit -the \texttt{\textpercent} altogether. +\texttt{\textpercent{}} character: if you do this you might as well omit +the \texttt{\textpercent{}} altogether. In ``real life'', of course, the spaces that appear in macros are far more cryptic than those in the example above. The most common spaces @@ -2059,11 +2059,11 @@ whereas it's defined as ``\csx{hbox}\texttt{ to }\csx{hsize}'' in Maths setting shows a case where the \LaTeX{} version \emph{is} essentially equivalent to the \TeX{} primitive commands: the \LaTeX{} \csx{(}\texttt{\ ...\ }\csx{)} does essentially no different to the -\TeX{} \texttt{\$\ ...\ \$} -(except for checking that you're not attempting to open a maths -environment when you're already in one, or vice versa). % ! line break -However, \csx{[}\texttt{\ ...\ }\csx{]} \emph{isn't} the same as -\texttt{\$\$\ ...\ \$\$}: the \TeX{} version, used +primitive \texttt{\$\ ...\ \$}; except for checking that you're not +attempting to open a maths environment when you're already in one, or +attempting to close one when you're not. +However, \csx{[}\texttt{\ ...\ }\csx{]} has a more significant +difference from \texttt{\$\$\ ...\ \$\$}: the primitive version, used in \LaTeX{}, can miss the effect of the class option \pkgoption{fleqn}. Font handling is, of course, wildly different in \plaintex{} and @@ -2073,14 +2073,7 @@ Font handling is, of course, wildly different in \plaintex{} and safe in the most trivial contexts, and are potential sources of great confusion in many circumstances. Further discussion of this issue may be found in ``\Qref*{What's wrong with \csx{newfont}?}{Q-newfont*}''. -%% -%% Consider \csx{vskip} (or \plaintex{} users of it like \csx{medskip}) -%% \emph{vs}.\nothtml{\@} \csx{vspace} or \csx{vspace*}, but most -%% especially \csx{addvspace}. -%% \begin{ctanrefs} -%% \item[fntguide.pdf]\CTANref{fntguide.pdf} -%% \item[fntguide.tex]Distributed with \CTANref{latex} -%% \end{ctanrefs} +\LastEdit{2013-09-27} \Question[Q-atsigns]{\csx{@} and \texttt{@} in macro names} @@ -2414,7 +2407,7 @@ through \LaTeX{}, so you don't have to work with the whole of macro you're interested in: use your ``malleable text editor'' to find the definition in \File{latex.ltx}; then search backwards from that point for a line that starts % ! line break -\texttt{\textpercent\textpercent\textpercent\ From File:}~--- that line +\texttt{\textpercent{}\textpercent{}\textpercent{}\ From File:}~--- that line tells you which \extension{dtx} file contains the definition you are interested in. Doing this for \csx{protected@edef}, we find: \begin{quote} @@ -2450,9 +2443,9 @@ All these .dtx files are on \acro{CTAN} as part of the main \LaTeX{} distribution. \begin{ctanrefs} \item[\nothtml{\rmfamily}\LaTeX{} distribution]\CTANref{latex} -\item[texdef, \nothtml{{\rmfamily aka }}latexdef]\CTANref{texdef} +\item[texdef,\nothtml{\rmfamily aka} latexdef]\CTANref{texdef} \end{ctanrefs} -\LastEdit{2012-10-09} +\LastEdit{2013-09-27} \Question[Q-oarglikesect]{Optional arguments like \csx{section}} @@ -2624,8 +2617,8 @@ The \LaTeX{} kernel does a lot of this, and has its own command, \begin{quote} \begin{wideversion} \begin{verbatim} +\makeatletter \newcommand{\mycommand}{% - \makeatletter \@ifstar \mycommandStar% \mycommandNoStar% @@ -2720,7 +2713,7 @@ via the \Package{expl3} package. \item[xparse.sty]Distributed as part of \CTANref{l3packages}[xparse] \item[expl3.sty]Distributed as part of \CTANref{l3kernel}[expl3] \end{ctanrefs} -\LastEdit{2013-02-28} +\LastEdit{2014-04-04} \nothtml{\hrule height 0pt \nobreak\vskip0pt plus2.5in\vskip 0pt\relax} \Question[Q-ltxabbrv]{\LaTeX{} internal ``abbreviations'', etc.} @@ -3429,7 +3422,7 @@ text after \cmdinvoke{end}{env}. This doesn't happen with similar \LaTeX{}-supplied environments. You could impose the restriction that your users always put a -``\texttt{\textpercent}'' sign after the environment~\dots{}\nothtml{\@} but +``\texttt{\textpercent{}}'' sign after the environment~\dots{}\nothtml{\@} but \LaTeX{} environments don't require that, either. The \LaTeX{} environments' ``secret'' is an internal flag which causes @@ -3682,4 +3675,50 @@ draconian. \item[lacheck]\CTANref{lacheck} \item[nag.sty]\CTANref{nag} \end{ctanrefs} -\LastEdit{2012-10-09}
\ No newline at end of file +\LastEdit{2012-10-09} + +\Question[Q-ltx-csv]{Process a \acro{CSV} file in \latex{}} + +Comma-separated-variable (\acro{CSV}) files are a common means of +interchanging simple data between applications; for example, most +spreadsheet applications can provide files containing tables of +numbers with commas between them. One can envisage these tables as +``\latex{} tables'', and the packages to process them all provide +table generation, one way or another. + +For rather a long time, the canonical tools for dealing with such +files have been those provided in the \Package{datatool} bundle; +packages in the bundle allow the user to write procedures to process +numbers, currency amounts, names, etc., and to display them in tables +(including pie charts). + +The \Package{csvsimple} does similar tasks. Its processing is +controlled by keys established via the \Package{pgfkeys} package, +which define how each row of the \acro{CSV} file is to be processed. + +For usage ``nearer to the bone'', one might consider the commands +\csx{docsvlist} and \csx{forcsvlist} (from the \Package{etoolbox} +package). The first uses the time-honoured \latex{} technique of +changing the definition of a \csx{do} command; it runs through the +list, and processes every item of the list as the argument of the +\csx{do} command; so: +\begin{quote} +\begin{verbatim} +\begin{itemize} +\renewcommand*{\do}[1]{\item #1} +\docsvlist{item1, item2, {item3a, item3b}, item4} +\end{itemize} +\end{verbatim} +\end{quote} +will convert the elements of a \acro{CSV} list into an itemised list. + +The macro \csx{forcsvlist} applies a function to each element of a +\acro{CSV} list; this can of course be used to implement +\csx{docsvlist}, at the cost of a little clarity. +\begin{ctanrefs} +\item[csvsimple.sty]\CTANref{csvsimple} +\item[datatool \nothtml{\rmfamily}bundle]\CTANref{datatool} +\item[etoolbox.sty]\CTANref{etoolbox} +\item[pgfkeys.sty]Distributed as part of \CTANref{pgf} +\end{ctanrefs} +\LastEdit*{2013-09-10} 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 347ea2e17ab..e7a616ace80 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.28 2012/02/07 21:46:08 rf10 Exp $ +% $Id: faq-projects.tex,v 1.29 2014/01/28 18:17:36 rf10 Exp rf10 $ \section{Current \TeX{}-related projects} @@ -434,7 +434,7 @@ of \tex{}; the main changes include: Otherwise, the process of typesetting is essentially the same as \tex{}'s. (However some changes have also been made in the hyphenation stage that may give slightly different results if the same -document is compiled with \pdftex{} or \xetex{}. +document is compiled with \pdftex{} or \xetex{}.) \begin{ctanrefs} \item[polyglossia.sty]\CTANref{polyglossia} \item[xeCJK.sty]\CTANref{xecjk} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-support.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-support.tex index 7e4f88560f2..1a08d1865cf 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-support.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-support.tex @@ -1,4 +1,4 @@ -% $Id: faq-support.tex,v 1.8 2012/12/07 19:34:33 rf10 Exp rf10 $ +% $Id: faq-support.tex,v 1.9 2014/01/28 18:17:36 rf10 Exp rf10 $ \section{Support Packages for \TeX{}} @@ -56,28 +56,37 @@ A Unix port of the program (\ProgName{xtexcad}) has been made. \Question[Q-spell]{Spelling checkers for work with \TeX{}} -Most approaches to the problem (of checking your spelling) are -designed to work with a plain text file; in our case, this is \alltex{} +`Traditional' approaches to the problem (of checking your spelling) were +designed to work with a plain text file; in our case, we have an \alltex{} source. For the user, this is a simple-to-understand way to do the job; but for the spell-checker programmer, it requires heuristic (and hence fallible) analysis of \alltex{} macros and so on. The alternative, of viewing the text \emph{after} \alltex{} has processed the results, is covered below. +The user of an \Qref*{shell/editor}{Q-editors} will usually find it +embeds a spelling checker. For command-line use, there are several +choices, depending on the system you're using. + For Unix, \ProgName{ispell} was long the program of choice; it is well integrated with \ProgName{emacs}, and deals with some \TeX{} syntax. However, it has more-or-less been replaced everywhere, by \ProgName{aspell}, which was designed as a successor, and certainly performs better on most metrics; there remains some question as to its -performance with \AllTeX{} sources. - -For Windows, there is a good spell checker incorporated into many of -the \Qref*{shell/editor}{Q-editors} combinations that are available. -The spell checker from the (now defunct) 4All\TeX{} shell remains -available as a separate package, \ProgName{4spell}. +performance with \AllTeX{} sources. The most recent offering (which +is widely used in other open-source software projects) is +\begin{hyperversion} + \href{http://hunspell.sourceforge.net/}{\ProgName{Hunspell}}. +\end{hyperversion} +\begin{flatversion} + Hunspell~(see \URL{http://hunspell.sourceforge.net/}). +\end{flatversion} +\ProgName{Hunspell} is available for other architectures, too; a web +search shows versions available for Windows, at least. For the Macintosh, \ProgName{Excalibur} has long been used; its distribution comes with dictionaries for several languages. +\ProgName{Hunspell} (see above) is actually part of OS X from version 10.6. The \acro{VMS} Pascal program \ProgName{spell} makes special cases of some important features of \LaTeX{} syntax. @@ -115,7 +124,7 @@ duly highlighted.) \CTANref{vmspell} \item[winedt]\CTANref{winedt} \end{ctanrefs} -\LastEdit{2013-02-21} +\LastEdit{2013-10-02} \Question[Q-wordcount]{How many words have you written?} 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 e1c8caac05f..07050510f3d 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.14 2012/01/16 23:37:15 rf10 Exp rf10 $ +% $Id: faq-symbols.tex,v 1.15 2014/01/28 18:17:36 rf10 Exp rf10 $ \section{Symbols, etc.} @@ -53,7 +53,7 @@ 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. -In the ordinary course of events, mathematicians do not have +In the ordinary course of events, but 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 @@ -96,16 +96,23 @@ A document that shows the \FontName{bbm}, \FontName{bbold}, a feel for their appearance, is available (\acro{CTAN} package \Package{blackboard}). +The \Package{boondox} font set consists of Type~1 versions of the +\acro{STIX} mathematics set (the originals are distributed in +\acro{OTF} format). The set contains a font +`BOONDOXDoubleStruck-Regular' (blackboard bold) (as well as a `bold' +version of that. + An alternative source of Type~1 fonts with blackboard bold characters may be found in the steadily increasing set of complete families, both commercial and free, that have been prepared for use with \AllTeX{} (see % beware line break \htmlonly{``}\Qref[question]{choice of outline fonts}{Q-psfchoice}\htmlonly{''}). Of the free sets, the \FontName{txfonts} and \FontName{pxfonts} families -both come with replicas of \FontName{msam} and \FontName{msbm} -(though, as noted elsewhere, there are other reasons not to use these -fonts). The \FontName{mathpazo} family includes a ``mathematically -significant'' choice of blackboard bold characters, and the +both come with replicas of \FontName{msam} and \FontName{msbm}, but +(as noted elsewhere, there are other reasons not to use these fonts); +revised versions of the fonts, \FontName{newtx} and \FontName{newpx} +are better adjusted. The \FontName{mathpazo} family includes a +``mathematically significant'' choice of blackboard bold characters, and the \FontName{fourier} fonts contain blackboard bold upper-case letters, the digit `1', and lower-case `k'. @@ -140,9 +147,12 @@ the meaning of laziness (in this respect!). \item[doublestroke fonts]\CTANref{doublestroke} \item[fourier fonts]\CTANref{fourier} \item[mathpazo fonts]\CTANref{mathpazo} +\item[newpx]\CTANref{newpx} +\item[newtx]\CTANref{newtx} \item[pxfonts]\CTANref{pxfonts} \item[txfonts]\CTANref{txfonts} \end{ctanrefs} +\LastEdit{2013-12-04} \Question[Q-scriptfonts]{Better script fonts for maths} @@ -241,32 +251,41 @@ catalogue entries. \end{ctanrefs} \LastEdit{2011-08-17} -\Question[Q-boldgreek]{Setting bold Greek letters in \LaTeX{}} +\Question[Q-boldgreek]{Setting bold Greek letters in \LaTeX{} maths} The issue here is complicated by the fact that \csx{mathbf} (the command for setting bold \emph{text} in \TeX{} maths) affects a select -few mathematical symbols (the uppercase Greek letters). However -lower-case Greek letters behave differently from upper-case Greek -letters (due to Knuth's esoteric font encoding decisions). However, -\csx{mathbf} \emph{can't} be used even for upper-case Greek letters in -the \AMSLaTeX{} \Package{amsmath} package, which -disables this font-switching and you must use one of the techniques -outlined below. - -The \plaintex{} solution \emph{does} work, in a limited way: +few mathematical `symbols' (the uppercase Greek letters). + +In the default configuration, lower-case Greek letters behave +differently from upper-case Greek letters (the lower-case greek +letters are in the maths fonts, while the upper-case letters are in +the original (OT1-encoded) text fonts). + +The \plaintex{} solution \emph{does} work, in a limited way; you set a +maths \emph{style}, before you start an equation; thus \begin{quote} \begin{verbatim} {\boldmath$\theta$} \end{verbatim} \end{quote} -but \csx{boldmath} may not be used in maths mode, so this `solution' -requires arcana such as: +does the job, but \csx{boldmath} may not be used in maths mode. As a +result, this solution requires that you embed single bold characters +in a text box: \begin{quote} \begin{verbatim} $... \mbox{\boldmath$\theta$} ...$ \end{verbatim} \end{quote} -which then causes problems in superscripts, etc. +which then causes problems in superscripts, etc. With +\Package{amsmath} loaded, +\begin{quote} +\begin{verbatim} +$... \text{\boldmath$\theta$} ...$ +\end{verbatim} +\end{quote} +does the trick (and is less bad in regard to superscripts, etc), but +is an unsatisfactory solution, too. These problems may be addressed by using a bold mathematics package. \begin{itemize} @@ -278,14 +297,15 @@ These problems may be addressed by using a bold mathematics package. comprehensive than \csx{bm}) covers almost all common cases. \end{itemize} -All these solutions cover all mathematical symbols, not merely Greek -letters. +All these solutions apply to all mathematical symbols, not merely +Greek letters. \begin{ctanrefs} \item[bm.sty]Distributed as part of \CTANref{2etools}[bm] \item[amsbsy.sty]Distributed as part of \AMSLaTeX{} \CTANref{amslatex}[amsbsy] \item[amsmath.sty]Distributed as part of \AMSLaTeX{} \CTANref{amslatex}[amsmath] \end{ctanrefs} +\LastEdit{2013-06-12} \Question[Q-prinvalint]{The Principal Value Integral symbol} @@ -583,11 +603,11 @@ options available to the \AllTeX{} user, is already supported by package. Similar support is also in the works for \Qref*{\LuaTeX{}}{Q-luatex}. \begin{ctanrefs} +\item[boondox \nothtml{\rmfamily}fonts]\CTANref{boondox} \item[cmolddig \nothtml{\rmfamily}fonts]\CTANref{cmolddig} \item[eco \nothtml{\rmfamily}fonts]\CTANref{eco} \item[fontinst]\CTANref{fontinst} \item[fontspec.sty]\CTANref{fontspec} \item[mathpazo \nothtml{\rmfamily}fonts]\CTANref{mathpazo} \end{ctanrefs} -\LastEdit{2013-05-14} - +\LastEdit{2013-12-04} 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 2c8f88e7d93..48e5a1af7fa 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.14 2012/10/09 18:26:54 rf10 Exp rf10 $ +% $Id: faq-t-g-wr.tex,v 1.15 2014/01/22 17:27:56 rf10 Exp $ \section{Things are Going Wrong\dots{}} @@ -60,13 +60,12 @@ There is nothing that can directly be done about this error: you can't extend the number of available \csx{dimen} registers without extending \TeX{} itself. \begin{wideversion} % hyper - \Qref{\eTeX{}}{Q-etex} and \Qref{Omega}{Q-omegaleph} both do this, as - does \Qref{MicroPress Inc's V\TeX{}}{Q-commercial}. + \Qref{Omega}{Q-omegaleph} and \Qref{\eTeX{}}{Q-etex} both do this. \end{wideversion} \begin{narrowversion} - \eTeX{} and \ensuremath{\Omega}~--- \Qref[see questions]{}{Q-etex} - \Qref[and]{}{Q-omegaleph} respectively~--- both do this, as does - MicroPress Inc's V\TeX{}~--- \Qref{}{Q-commercial}. + \ensuremath{\Omega} and \eTeX{}~--- + \Qref[see questions]{}{Q-omegaleph} + \Qref[and]{}{Q-etex} respectively~--- both do this. \end{narrowversion} It's actually quite practical (with most modern distributions) to use @@ -105,6 +104,7 @@ program for other systems (including Windows, nowadays). \item[MathsPic]\CTANref{mathspic} \item[pictexwd.sty]Distributed as part of \CTANref{pictex-addon}[pictexwd] \end{ctanrefs} +\LastEdit{2014-01-22} \subsection{Making things stay where you want them} @@ -314,10 +314,11 @@ than the original widow. \Question[Q-oldfontnames]{Old \LaTeX{} font references such as \csx{tenrm}} \LaTeXo{} defined a large set of commands for access to the fonts -that it had built in to itself. For example, various flavours of -|cmr| could be found as \csx{fivrm}, \csx{sixrm}, \csx{sevrm}, +that it had built in to itself. For example, \FontName{cmr} might +appear as \csx{fivrm}, \csx{sixrm}, \csx{sevrm}, \csx{egtrm}, \csx{ninrm}, \csx{tenrm}, \csx{elvrm}, \csx{twlrm}, -\csx{frtnrm}, \csx{svtnrm}, \csx{twtyrm} and \csx{twfvrm}. +\csx{frtnrm}, \csx{svtnrm}, \csx{twtyrm} and \csx{twfvrm}, according +to the size it's being typeset at. These commands were never documented, but certain packages nevertheless used them to achieve effects they needed. 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 c7d14ed60cb..0fcc34bf659 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.16 2013/04/16 22:40:06 rf10 Exp rf10 $ +% $Id: faq-texsys.tex,v 1.17 2013/07/24 21:50:56 rf10 Exp $ \section{\TeX{} Systems} @@ -55,27 +55,12 @@ provided). It is distributed as source, and compiles with \acro{GNU} Pascal, thereby coming as close as you're likely to get to Knuth's original distribution. It is known to work well, but the omission of \etex{} and \pdftex{} will rule it out of many users' choices. - -A free version of the commercial % ! line break -\Qref*{V\TeX{} extended \TeX{} system}{Q-commercial} is available for -use under Linux. V\TeX{}, among other things, specialises in direct -production of \acro{PDF} from \AllTeX{} input. Sadly, it's no longer -supported, and the ready-built images are made for use with a rather -ancient Linux kernel. - -Finally, the developer of \miktex{} has released a port of the -\PDFTeX{} executable from of that excellent (Windows) system for use -on Linux; get it via % ! line break -\href{http://miktex.org/unx/}{the \miktex{} site}. The \miktex{} -package manager (\ProgName{mpm}), for Linux, is also available from -the same place. \begin{ctanrefs} \item[tex-gpc]\CTANref{tex-gpc} \item[texlive]Browse \CTANref{texlive} \item[texlive installer (Unix)]\CTANref{texlive-unix} -\item[vtex]\CTANref{vtex-linux} -\item[vtex \nothtml{\rmfamily}required common files]\CTANref{vtex-common} \end{ctanrefs} +\LastEdit{2013-07-18} \Question[Q-syswin32]{(Modern) Windows systems} @@ -247,12 +232,6 @@ Web2C~7.0 implementation, using the \acro{GNU} \ProgName{djgpp} compiler. While this package is more recent than em\TeX{}, it nevertheless also offers a rather old instance of \AllTeX{}. -For \acro{PC}s running \acro{OS/}2, users also have the option of the -free version of the commercial \Qref*{V\TeX{}}{Q-commercial}, which -specialises in direct production of \acro{PDF} from \AllTeX{} input. -(This version is, like the Linux version, unfortunately no longer -supported.) - For \acro{VAX} systems running Open\acro{VMS}, a \TeX{} distribution is available \acro{CTAN}, but is almost certainly not the latest (it is more than 10 years old). Whether a version is even available for @@ -270,7 +249,6 @@ machines, but since \TeX{} was originally written on a \acro{DEC}-10 under \acro{WAITS}, the \acro{TOPS}-20 port is another near approach to Knuth's original environment. Sources are available by anonymous \texttt{ftp} from \url{ftp://ftp.math.utah.edu/pub/tex/pub/web} - \checked{RF}{2010/04/19} \begin{ctanrefs} \item[\nothtml{\rmfamily}Atari TeX]\CTANref{atari-cstex} \item[djgpp]\CTANref{djgpp} @@ -278,10 +256,8 @@ to Knuth's original environment. Sources are available by anonymous \item[emtexTDS]\CTANref{emtextds} \item[OpenVMS]\CTANref{OpenVMSTeX} \item[PasTeX]\CTANref{amiga} -\item[vtex \nothtml{\rmfamily}for Linux]\CTANref{vtex-linux} -\item[vtex \nothtml{\rmfamily}for OS/2]\CTANref{vtex-os2} -\item[vtex \nothtml{\rmfamily}required common files]\CTANref{vtex-common} \end{ctanrefs} +\LastEdit{2013-07-18} \Question[Q-editors]{\TeX{}-friendly editors and shells} @@ -440,19 +416,6 @@ also have email, and normal telephone and fax support. Web: \URL{http://www.pctex.com/} \end{quote} Source: Personal \TeX{} Inc web site, December 2004 -\item[\acro{PC}; V\TeX{}] \acro{DVI}, \acro{PDF} and \acro{HTML} - backends, Visual Tools and Type 1 fonts - \begin{quote} - MicroPress Inc\\ - 68-30 Harrow Street\\ - Forest Hills, \acro{NY} 11375\\ - \acro{USA}\\[.25\baselineskip] - Tel: +1 718-575-1816\\ - Fax: +1 718-575-8038\\ - Email: \mailto{support@micropress-inc.com}\\ - Web: \URL{http://www.micropress-inc.com/} - \end{quote} - Source: Mail from MicroPress, Inc., July 1999 \item[\acro{PC}; Scientific Word] Scientific Word and Scientific Workplace offer a mechanism for near-\WYSIWYG{} input of \LaTeX{} documents; they ship with True\TeX{} from Kinch (see above). Queries within the \acro{UK} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-the-end.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-the-end.tex index 927ef675f15..9ace9b7919a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-the-end.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-the-end.tex @@ -1,4 +1,4 @@ -% $Id: faq-the-end.tex,v 1.2 2011/10/29 07:29:44 rf10 Exp rf10 $ +% $Id: faq-the-end.tex,v 1.3 2014/01/28 18:17:36 rf10 Exp rf10 $ \section{You're still stuck?} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-wdidt.tex index 97ab75e31a9..c6cdd8e95e8 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.23 2012/11/24 10:56:03 rf10 Exp $ +% $Id: faq-wdidt.tex,v 1.24 2014/01/22 17:29:03 rf10 Exp $ \section{Why does it \emph{do} that?} @@ -141,14 +141,21 @@ chance. For example: \verb+\error+ \end{verbatim} \end{quote} -will work (typesetting `\csx{error}'), but +will work (typesetting `\csx{error}'), but if we define no more than a +no-op macro, \begin{quote} \begin{verbatim} \newcommand{\unbrace}[1]{#1} +\end{verbatim} +\end{quote} +which simply regurgitates its argument, and use it as: +\begin{quote} +\begin{verbatim} \unbrace{\verb+\error+} \end{verbatim} \end{quote} -will not (it will attempt to execute \csx{error}). Other errors one +the combinartion will not (it will attempt to execute \csx{error}). +Other errors one may encounter are `\csx{verb} ended by end of line', or even the rather more helpful `\csx{verb} illegal in command argument'. The same sorts of thing happen with \cmdinvoke{begin}{verbatim} \dots{} @@ -192,7 +199,7 @@ necessary?''. ``\Qref*{typesetting \acro{URL}s}{Q-setURL}'' offers advice here. \item If you're putting \csx{verb} into the argument of a boxing command (such as \csx{fbox}), consider using the \environment{lrbox} - environmen)t: + environment: \begin{quote} \begin{verbatim} \newsavebox{\mybox} @@ -214,9 +221,8 @@ medium of prefixing the macro with \csx{cprotect}: \cprotect\section{Using \verb|verbatim|} \end{verbatim} \end{quote} -The package (at the time this author tested it) was still under -development (though it \emph{does} work in this simple case) and -deserves consideration in most cases; the package documentation gives +The package \emph{does} work in this simple case, and deserves +consideration in many others cases; the package documentation gives more details. Another way out is to use one of ``argument types'' of the @@ -240,7 +246,7 @@ argument sequence of an otherwise ``normal'' sort of command; that `\texttt{\char`\|}' \end{typesetversion} \begin{htmlversion} - `\texttt{|}' + `\texttt{|}' % | balance for emacs text-colouring \end{htmlversion} may be any old character that doesn't conflict with the content of the argument. @@ -250,7 +256,7 @@ own) but the downside is that \Package{xparse} pulls in the experimental \latex{}3 programming environment (\Package{l3kernel}) which is pretty big. -Other than the \Package{cprotect} package, there are three partial +Other than the \Package{cprotect} package, there are four partial solutions to the problem: \begin{itemize} \item Some packages have macros which are designed to be responsive @@ -273,7 +279,23 @@ solutions to the problem: Rather simpler is the \Package{verbdef} package, whose \csx{verbdef} command defines a (robust) command which expands to the verbatim - argument given. + argument given; the \Package{newverbs} package provides a similar + function as well as several related ones. +\item In a similar vein, the \Package{verbatimbox} package makes it + possible to put verbatim material in a box: + \begin{quote} +\begin{verbatim} +\begin{verbbox} +some exotic _&$ stuff +\end{verbbox} +\theverbbox +\end{verbatim} + \end{quote} + the operation typesets exotic stuff into an anonymous box, and its + contents may be retrieved using the command \csx{theverbbox}. It is + clear that it's in the same mould as the \csx{verbdef} command + mentioned above; the package defines other similar commands. +\item The \Package{tcolorbox} package provides a similar facility \item If you have a single character that is giving trouble (in its absence you could simply use \csx{texttt}), consider using \csx{string}. \cmdinvoke{texttt}{my\csx{string}\_name} @@ -296,17 +318,56 @@ solutions to the problem: troublesome character (though it's plainly not necessary for things like percent signs for which \AllTeX{} already provides robust macros). + +\item One may also consider putting verbatim material in an external + file; this is somewhat more tedious, but the file may be reused + several times within a single document. The \Package{tcolorbox} + permits this: +\begin{quote} +\begin{verbatim} +\begin{tcbverbatimwrite}{<file name>} +... +\end{tcbverbatimwrite} +\end{verbatim} +\end{quote} + which (as one might guess) writes to the named file; load the saved + contents using \cmdinvoke{input}{<file name>} + + A second environment puts your verbatim material in an (apparently) + anonymous temporary file: +\begin{quote} +\begin{verbatim} +\begin{tcbwritetemp}{<file name>} +... +\end{tcbverbatimwrite} +\end{verbatim} +\end{quote} + In this case, you use the anonymous file with the \csx{tcbusetemp} + macro. (You can change the name used for the `anonymous' file, if + its default proves troublesome.) + + The \Package{moreverb} package provides a \csx{verbatimwrite} + command, which doesn't provide an anonynous file. + + Macros, to achieve the same effect, are outlined in the + documentation of the \Package{verbatim} package; the macros use the + facilities of the package, but the user has to write a mini-package + actually to use them. \end{itemize} \begin{ctanrefs} \item[cprotect.sty]\CTANref{cprotect} \item[fancyvrb.sty]\CTANref{fancyvrb} \item[l3kernel \nothtml{\rmfamily}bundle]\CTANref{l3kernel} \item[memoir.cls]\CTANref{memoir} +\item[newverbs.sty]\CTANref{newverbs} +\item[tcolorbox.sty]\CTANref{tcolorbox} \item[url.sty]\CTANref{url} +\item[verbatim.sty]\CTANref{verbatim} +\item[verbatimbox.sty]\CTANref{verbatimbox} \item[verbdef.sty]\CTANref{verbdef} \item[xparse.sty]Distributed as part of \CTANref{l3packages}[xparse] \end{ctanrefs} -\LastEdit{2013-02-15} +\LastEdit{2013-10-21} \Question[Q-noline]{``No line here to end''} @@ -328,10 +389,11 @@ See the LaTeX manual or LaTeX Companion \end{verbatim} \end{narrowversion} \end{quote} -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): +appears when you give \LaTeX{} a \texttt{\bsbs } command at a time +when it's not expecting it; it is a \emph{line-breaking} command, and +is confused if \latex{} isn't building a paragraph when you give the +command. A common case is where you've decided you want the label of +a list item to be on a line of its own, and written (for example): \begin{quote} \begin{verbatim} \begin{description} @@ -341,14 +403,14 @@ so you've written (for example): \end{verbatim} \end{quote} % ridiculous coding for sanitize.pl -- careful! -\bsbs {} is actually a rather bad command to use in this case (even if -it worked), since it would force the `paragraph' that's made up of the -text of the item to terminate a line which has nothing on it but the -label. This would lead to an ``\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 -purpose. +% \bsbs {} is actually a rather bad command to use in this case (even if +% it worked), since it could 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 could 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 +% purpose. The proper solution to the problem is to write a new sort of \environment{description} environment, that does just what you're after. (The @@ -356,16 +418,16 @@ The proper solution to the problem is to write a new sort of \Qref[question]{\emph{\LaTeX{} Companion}}{Q-latex-books}\nothtml{~---} offers a rather wide selection of variants of these things.) -The quick-and-easy solution, which avoids the warning, is to write: +A straightforward solution, which avoids the warning, is to write: \begin{quote} \begin{verbatim} \begin{description} -\item[Very long label] \hspace*{\fill} \\ +\item[Very long label] \leavevmode \\ Text... \end{description} \end{verbatim} \end{quote} -which fills out the under-full line before forcing its closure. The +which starts a paragraph before forcing a break. The \Package{expdlist} package provides the same functionality with its \csx{breaklabel} command, and \Package{mdwlist} provides it via its \csx{desclabelstyle} command. @@ -396,11 +458,24 @@ be had by saying: \end{center} \end{verbatim} \end{quote} + +You \emph{can} use \csx{leavevmode}, as above: +\begin{quote} +\begin{verbatim} +\begin{center} + First (heading) line\\ + \leavevmode\\ + body of the centred text... +\end{center} +\end{verbatim} +\end{quote} +but that is just as tiresome to type as \texttt{\bsbs } with an optional +argument, and can not be recommended. \begin{ctanrefs} \item[expdlist.sty]\CTANref{expdlist} \item[mdwlist.sty]Distributed as part of \CTANref{mdwtools}[mdwlist] \end{ctanrefs} -\LastEdit{2011-06-01} +\LastEdit{2014-01-13} % other instances: \[no]linebreak in vertical mode @@ -462,6 +537,42 @@ not work with obsolete (pre-\LaTeXe{}) packages such as genesis of \csx{includegraphics}. \LastEdit{2012-11-16} +\Question[Q-centre-flt]{Why is my table/figure/\dots{} not centred?} + +You want a float whose contents are centred, but \latex{} ignores your +\environment{center} environment. Most likely, you have written: +\begin{quote} +\begin{verbatim} +\begin{center} + \begin{figure} + ... + \end{figure} +\end{center} +\end{verbatim} +\end{quote} +In this case, \latex{} has ``taken the \environment{figure} away'', +and will typeset it at some location it fancies (it does the same with +\environment{table}s) the only thing we can say (for sure) about the +location is that it \emph{won't} be inside that \environment{center} +environment. As a result, the \environment{center} environment is +left with nothing to do~\dots{} except to % !line break +\Qref*{make a mess of your vertical spacing}{Q-vertspacefloat}. + +The solution is the same as that outlined in % !line break +\Qref*{the same answer}{Q-vertspacefloat}, noting that all control of +an \environment{figure} or \environment{table} needs to be +inside the environment. So the example's code should be converted to +\begin{quote} +\begin{verbatim} +\begin{figure} + \centering + ... +\end{figure} +\end{verbatim} +\end{quote} +(or something similar for a \environment{table}). +\LastEdit*{2013-11-19} + \Question[Q-2colfltorder]{Two-column float numbers out of order} When \LaTeX{} can't place a float immediately, it places it on one of @@ -1197,21 +1308,27 @@ way \TeX{} works, and Lamport describes a solution (place a pair of braces after a command's invocation) in the description of \LaTeX{} syntax. Thus the requirement is in effect part of the definition of \LaTeX{}. -This \acro{FAQ}, -for example, is written with definitions that \emph{require} one to -type \cmdinvoke{fred}{\relax} % the \relax prevents {} being gobbled - % in html production (sigh) +These \acro{FAQ}s, +for example, is written in \latex{} for production of a web site. The +HTML code is generated by a script that \emph{requires} a pair of +braces, to make a null argument, as in: +\begin{quote} + \cmdinvoke{fred}{\relax} % the \relax prevents {} being gobbled + % in html production (sigh) + % (we needn't tell them about _that_ ;-) +\end{quote} for almost all macro invocations, regardless -of whether the following space is required: however, this \acro{FAQ} -is written by highly dedicated (and, some would say, eccentric) -people. Many users find all those braces become very tedious very +of whether the following space is required: however, these \acro{FAQ}s +should not itself be regarded as a model of \latex{} style. + +Many users find all those braces become very tedious very 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 \texttt{\bsbs }) and you don't need braces after -\emph{it}. Thus one can reduce to one the extra characters one needs -to type. +\emph{it}. Thus one can reduce to one the number of extra characters +one needs to type. If even that one character is too many, the package \Package{xspace} defines a command \csx{xspace} that guesses whether there should have @@ -1246,16 +1363,22 @@ The \csx{xspace} command must be the last thing in your macro definition (as in the example); it's not completely foolproof, but it copes with most obvious situations in running text. -The \Package{xspace} package doesn't save you anything if you only use -a modified macro once or twice within your document. In any case, be +The \Package{xspace} package doesn't save you anything if you use it in +a macro that appears only once or twice within your document, and it +is not totally foolproof. (The original author of the package wrote +it because he had been bitten by lost spaces. He no longer recommends +its use, simply because of the possibility of error.) + +In any case, be careful with usage of \csx{xspace}~--- it changes your input syntax, which can be confusing, notably to a collaborating author (particularly if you create some commands which use it and some which -don't). Of course, no command built into \LaTeX{} or into any +don't). No command built into \LaTeX{} or into any ``standard'' class or package will use \csx{xspace}. \begin{ctanrefs} \item[xspace.sty]Distributed as part of \CTANref{2etools}[xspace] \end{ctanrefs} +\LastEdit{2013-11-26} \Question[Q-overfull]{\AllTeX{} makes overfull lines} @@ -1541,7 +1664,7 @@ problem by ending the initial paragraph before starting the comment: \begin{verbatim} Paragraph text ... ... paragraph body ends. -\par\noindent +\par\nothtml{\noindent} {\footnotesize Comment on the paragraph.} Next paragraph starts... @@ -1571,6 +1694,7 @@ Main body of text... \Question[Q-tocloftwrong]{Numbers too large in table of contents, etc.} +\keywords{memoir table-of-contents spacing} \LaTeX{} constructs the table of contents, list of figures, tables, and similar tables, on the basis of a layout specified in the class. As a result, they do \emph{not} react to the sizes of things in them, @@ -1584,7 +1708,29 @@ fit in the space allowed for them in the class. A separate answer discusses % ! line break \nothtml{re-designing the tables ---} % ! line break \Qref{re-designing the tables}{Q-tocloft}\nothtml{ ---} -and those techniques can be employed to make the numbers fit. +and techniques from that answer may be employed to make the numbers +fit: +\begin{quote} +\begin{verbatim} +\setlength\cftsectionnumwidth{4em} +\end{verbatim} +\end{quote} + +The same command may be employed in documents typeset with the +\Class{memoir} package (by the same author as \Package{tocloft}). + +\Class{Memoir} has another mechanism for the job: +\cmdinvoke{cftsetindents}{\meta{kind}}{indent}{numwidth}. Here +\emph{kind} is \texttt{chapter}, \texttt{section}, or whatever; the +\emph{indent} specifies the `margin' before the entry starts; and the +\emph{width} is of the box into which the number is typeset (so needs +to be wide enough for the largest number, with the necessary spacing +to separate it from what comes after it in the line. +\begin{ctanrefs} +\item[memoir.cls]\CTANref{memoir} +\item[tocloft.sty]\CTANref{tocloft} +\end{ctanrefs} +\LastEdit{2013-08-20} \Question[Q-gutter]{Why is the inside margin so narrow?} @@ -1786,7 +1932,7 @@ The font-selection commands of \LaTeXo{} were \csx{rm}, \csx{sf}, commands, so you used them as: \begin{quote} \begin{verbatim} -{\bf Fred} was {\it here\/}}. +{\bf Fred} was {\it here\/}. \end{verbatim} \end{quote} with the font change enclosed in a group, so as to limit its effect; diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq.sty b/Master/texmf-dist/doc/generic/FAQ-en/faq.sty index cbe87012536..e057007ae83 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.139 2012/11/10 14:25:12 rf10 Exp rf10 $ +% $Id: faq.sty,v 1.140 2014/01/28 18:16:50 rf10 Exp rf10 $ % % This is the LaTeX package that deals with the eccentricities of mark % up of the UK TeX FAQ. @@ -257,8 +257,6 @@ \providecommand\miktex{MiKTeX} \providecommand\texshop{\ProgName{TeXshop}} \providecommand\texworks{\ProgName{TeXworks}} -\providecommand\xetex{XeTeX} -\providecommand\xelatex{XeLaTeX} % \newcommand\ctan{\acro{CTAN}} \newcommand\tex{\TeX{}} @@ -365,6 +363,9 @@ \newcommand\pdftex{PDF\TeX} \newcommand\LuaTeX{Lua\TeX} \newcommand\luatex{Lua\TeX} +\newcommand\lualatex{Lua\LaTeX} +\newcommand\xetex{XeTeX} +\newcommand\xelatex{XeLaTeX} %\newcommand\TeXXeT{TeX-{}-XeT} \newcommand\AllTeX{(La)\TeX} diff --git a/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex b/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex index eb7bd4b7681..326b455cbc6 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/filectan.tex @@ -20,10 +20,9 @@ \CTANfile{backgrnd}{macros/generic/misc/backgrnd.tex}[backgrnd] \CTANfile{bbl2html}{biblio/bibtex/utils/misc/bbl2html.awk}[bbl2html] \CTANfile{beginlatex-pdf}{info/beginlatex/beginlatex-3.6.pdf}[beginlatex] -\CTANfile{belleek}{fonts/belleek/belleek.zip}[belleek] \CTANfile{bibtex-faq}{biblio/bibtex/contrib/doc/btxFAQ.pdf} \CTANfile{bidstobibtex}{biblio/bibtex/utils/bids/bids.to.bibtex}[bidstobibtex] -\CTANfile{btxmactex}{macros/eplain/tex/eplain/btxmac.tex}[eplain] +\CTANfile{btxmactex}{macros/eplain/tex/btxmac.tex}[eplain] \CTANfile{catalogue}{help/Catalogue/catalogue.html} \CTANfile{cat-licences}{help/Catalogue/licenses.html} \CTANfile{clsguide}{macros/latex/doc/clsguide.pdf}[clsguide] 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 e535459068c..97f7b0cd69a 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.27} \def\faqfiledate{2013-06-07} +\def\faqfileversion{3.28} \def\faqfiledate{2014-06-10} % % The above line defines the file version and date, and must remain % the first line with any `assignment' in the file, or things will @@ -18,10 +18,11 @@ % facilitate auto-processing of this stuff; this line is clunkily % detected (and ignored) in the build-faqbody script -\let\faqinput\input -%\def\faqinput#1{\message{*** inputting #1; group level -% \the\currentgrouplevel}\input{#1}% -% \message{*** out of #1; group level \the\currentgrouplevel}} +%\let\faqinput\input +\def\faqinput#1{%\message{*** inputting #1; group level \the\currentgrouplevel} + \input{#1}% + %\message{*** out of #1; group level \the\currentgrouplevel} +} % the stuff to print \faqinput{faq-intro} % introduction @@ -54,5 +55,3 @@ \faqinput{faq-the-end} % wrapping it all up % \end{document} is in calling file (e.g., newfaq.tex) - - 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 0e07e29bb4b..5d9d7319743 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 606a5312aec..c758c0b5893 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf +++ b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.pdf diff --git a/Master/texmf-dist/doc/generic/FAQ-en/newfaq.tex b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.tex index 70286d5d135..be32724192a 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/newfaq.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/newfaq.tex @@ -51,14 +51,17 @@ \input{dirctan} \input{filectan} %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% - -\ifsinglecolumn - \input{gather-faqbody} -\else - \begin{multicols}{2} +%\showthe\currentgrouplevel +\begin{multicols}{2} +%\expandafter\show\csname @currenvir\endcsname +%\tracingnesting=2 \input{gather-faqbody} - \end{multicols} -\fi +\end{multicols} +%\showthe\currentgrouplevel +%% (should be 0) +% +%\expandafter\show\csname @currenvir\endcsname +%% (should be "document" \typeout{*** That makes \thequestion\space questions ***} \end{document} |