diff options
| author | Karl Berry <karl@freefriends.org> | 2006-12-19 00:53:35 +0000 |
|---|---|---|
| committer | Karl Berry <karl@freefriends.org> | 2006-12-19 00:53:35 +0000 |
| commit | 38f0f73a43e0f28ff67323cdea32ff5bd3754c27 (patch) | |
| tree | c8ba84bb803e526d35cc23dba462f35f993209aa /Master | |
| parent | a48b9b71cee12257ba796c9aa1f1cef6f6a86eeb (diff) | |
faq update (18dec06)
git-svn-id: svn://tug.org/texlive/trunk@2797 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master')
27 files changed, 72 insertions, 109 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-AMSpkg.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-AMSpkg.html index 361430da52c..db71fffdda8 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-AMSpkg.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-AMSpkg.html @@ -5,8 +5,7 @@ <p>AMSTeX is a TeX macro package, originally written by Michael Spivak for the American Mathematical Society (AMS) during 1983–1985 and -is described in the book -“<a href="FAQ-books.html">The Joy of TeX</a>”. +is described in the book “<a href="FAQ-books.html">The Joy of TeX</a>”. It is based on Plain TeX, and provides many features for producing more professional-looking maths formulas with less burden on authors. It pays attention to the finer details of diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX2HTML.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX2HTML.html index ed9708daa31..08c0410d8f2 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX2HTML.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeX2HTML.html @@ -52,8 +52,6 @@ browsing may be brighter — see robust against the macros you include in your document, and it’s also pretty fast. <dt><i>TeXpider</i><dd> a commercial program from - - <a href="FAQ-commercial.html">Micropress</a>, which is described on <a href="http://www.micropress-inc.com/webb/wbstart.htm">http://www.micropress-inc.com/webb/wbstart.htm</a>; it uses bitmaps for equations. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXtoPlain.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXtoPlain.html index 7becdda3f9a..64df243538f 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXtoPlain.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-LaTeXtoPlain.html @@ -4,8 +4,6 @@ <h3>Translating LaTeX to Plain TeX</h3> <p>Unfortunately, no “general”, simple, automatic process is likely to succeed at this task. See - - “<a href="FAQ-LaTeXandPlain.html">How does LaTeX relate to Plain TeX</a>” for further details. <p>Translating a document designed to work with LaTeX into one diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-RCS.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-RCS.html index 730fe6cc140..d706c796646 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-RCS.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-RCS.html @@ -19,8 +19,8 @@ following minimal solution: <blockquote> <pre> \def\RCS$#1: #2 ${\expandafter\def\csname RCS#1\endcsname{#2}} -\RCS$Revision: 1.423 $ % or any RCS keyword -\RCS$Date: 2006/12/11 23:23:07 $ +\RCS$Revision: 1.426 $ % or any RCS keyword +\RCS$Date: 2006/12/18 09:59:16 $ ... \date{Revision \RCSRevision, \RCSDate} </pre> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXfuture.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXfuture.html index 5be869e5ac5..a50645e52e4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXfuture.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXfuture.html @@ -24,8 +24,8 @@ to build substantial new macro packages based on TeX. For the even longer term, there are various projects to build a <em>successor</em> to TeX; see, for example, the - <a href="FAQ-omegaleph.html">Omega/Aleph</a> and <a href="FAQ-extex.html">ExTeX</a> - projects. +<a href="FAQ-omegaleph.html">Omega/Aleph</a> +<a href="FAQ-extex.html">ExTeX</a>. <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXfuture">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=TeXfuture</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html index 00914bccb4b..06cb5c301a0 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-TeXsystems.html @@ -44,11 +44,10 @@ <dt><tt><i>web2c</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/web2c.zip">systems/web2c</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/web2c.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/web2c/">browse</a>) </dl> <dt>Linux<dd> Linux users may use teTeX (see above). -<p> The most recent offering is a free version of the - commercial - <a href="FAQ-commercial.html">VTeX</a>, which among other +<p> A free version of the commercial + <a href="FAQ-commercial.html">VTeX</a> is available, which among other things, specialises in direct production of PDF from - (La)TeX input. + (La)TeX input. Unfortunately, it’s no longer supported. <dl> <dt><tt><i>tetex</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/systems/unix/teTeX/current/distrib/">systems/unix/teTeX/current/distrib/</a> <dt><tt><i>vtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/linux.zip">systems/vtex/linux</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/linux.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/linux/">browse</a>) @@ -139,9 +138,9 @@ <dt><tt><i>djgpp</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/msdos/djgpp.zip">systems/msdos/djgpp</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/msdos/djgpp.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/msdos/djgpp/">browse</a>) </dl> <dt>PC: OS/2<dd> OS/2 may also use a free version of the - commercial - <a href="FAQ-commercial.html">VTeX</a>, which specialises - in direct production of PDF from (La)TeX input. + commercial <a href="FAQ-commercial.html">VTeX</a>, which specialises + in direct production of PDF from (La)TeX input. (This + version is, like the Linux version, unfortunately no longer supported.) <dl> <dt><tt><i>vtex</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/os2.zip">systems/vtex/os2</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/os2.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/os2/">browse</a>) <dt><tt><i>vtex required common files</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.zip">systems/vtex/common</a> (<a href="ftp://cam.ctan.org/tex-archive/systems/vtex/common.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/systems/vtex/common/">browse</a>) diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-acrobat.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-acrobat.html index 3f783f9ac40..0f2afca46bc 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-acrobat.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-acrobat.html @@ -2,13 +2,13 @@ <title>UK TeX FAQ -- question label acrobat</title> </head><body> <h3>Making Acrobat PDF documents from (La)TeX</h3> -<p>There are three general routes to Acrobat output: Adobe’s original +<p>There are three general routes to PDF output: Adobe’s original ‘distillation’ route (via PostScript output), conversion of a DVI file, and the use of a direct PDF generator such as -PDFTeX (see <a href="FAQ-whatpdftex.html">PDFTeX</a>) or +<a href="FAQ-whatpdftex.html">PDFTeX</a>) or MicroPress’s VTeX (which comes both as a <a href="FAQ-commercial.html">commercial version</a> for Windows PCs, and as a -<a href="FAQ-TeXsystems.html">‘free’ version)</a> for Linux systems). +<a href="FAQ-TeXsystems.html">‘free’ version)</a> for OS/2 and Linux systems). <p>For simple documents (with no hyper-references), you can either <ul> <li> process the document in the normal way, produce PostScript @@ -18,65 +18,64 @@ MicroPress’s VTeX (which comes both as a PDFwriter in place of a printer driver (this route is a dead end: the PDFwriter cannot create hyperlinks); <li> process the document in the normal way and generate PDF - direct from the DVI with <i>dvipdfm</i>; or + direct from the DVI using + <i>dvipdfm</i>/<i>dvipdfmx</i>; or <li> process the document direct to PDF with PDFTeX or VTeX. PDFTeX has the advantage of availability for a wide range of platforms, VTeX - (available commercially for Windows, or free of charge for Linux or - OS/2) has wider graphics capability, dealing with - encapsulated PostScript and some in-line PostScript. + (available commercially for Windows, or free of charge, but + unsupported, for Linux or OS/2) has wider graphics + capability, dealing with encapsulated PostScript and some in-line PostScript. </ul> <p>To translate all the LaTeX cross-referencing into Acrobat links, you need a LaTeX package to suitably redefine the internal commands. There are two of these for LaTeX, both -capable of conforming to the HyperTeX specification -(see <a href="FAQ-hyper.html">Making hypertext documents from TeX</a>): +capable of conforming to the +<a href="FAQ-hyper.html">HyperTeX specification</a>: Heiko Oberdiek’s <i>hyperref</i>, and Michael Mehlich’s -<i>hyper</i>. -uses a configuration file to determine how it will generate hypertext; -it can operate using PDFTeX primitives, the hyperTeX +<i>hyper</i>. (In practice, almost everyone uses +<i>hyperref</i>; <i>hyper</i> hasn’t been updated since 2000.) +<i>Hyperref</i> can often determine how it should generate +hypertext from its environment, but there is a wide set of +configuration options you can give via <code>\</code><code>usepackage</code>. The package +can operate using PDFTeX primitives, the hyperTeX <code>\</code><code>special</code>s, or DVI driver-specific <code>\</code><code>special</code> commands. - -<i>Dvips</i> -translates the DVI with these <code>\</code><code>special</code> commands into +Both <i>dvips</i> and Y&Y’s <i>DVIPSONE</i> can +translate the DVI with these <code>\</code><code>special</code> commands into PostScript acceptable to Distiller, and <i>dvipdfm</i> has <code>\</code><code>special</code> commands of its own. -<p>(In practice, almost everyone uses <i>hyperref</i>; <i>hyper</i> -hasn’t been updated since 2000.) -<p>If you use Plain TeX, Eplain macro package can help you create -Acrobat documents with hyper-references (see -“<a href="FAQ-eplain.html">what is Eplain</a>”). +<p>If you use Plain TeX, the <a href="FAQ-eplain.html">Eplain macros</a> can +help you create PDF documents with hyper-references. It can operate using PDFTeX primitives, or <code>\</code><code>special</code> commands for the <i>dvipdfm</i> DVI driver. -<p>There is no free implementation of all of <i>Adobe</i> +<p>While there is no free implementation of all of <i>Adobe</i> <i>Distiller</i>’s -functionality, any but the very oldest versions of <i>ghostscript</i> -provide pretty reliable distillation (but beware of the problems -discussed in - +functionality, any but the very oldest versions of <i>Ghostscript</i> +provide pretty reliable distillation (but beware of the problems with <a href="FAQ-dvips-pdf.html"><i>dvips</i> output for distillation</a>). -In fact, <i>Distiller</i> itself is now remarkably cheap (for -academics at least). <p>For viewing (and printing) the resulting files, Adobe’s <i>Acrobat</i> <i>Reader</i> is available for a fair range of platforms; for those for which Adobe’s reader is unavailable, remotely current versions of <i>ghostscript</i> combined with -<i>ghostview</i> or <i>GSview</i> can display and print -PDF files. -<p>In many circumstances, <i>ghostscript</i> combined with a viewer +<i>gv</i>, <i>GSview</i> (or even the unsupported +<i>ghostview</i>) can display and print PDF files, as can +<i>xpdf</i>. +<p>In many circumstances, <i>Ghostscript</i> combined with a viewer application is actually preferable to Acrobat Reader. For example, on Windows Acrobat Reader locks the <code>.pdf</code> file it’s displaying: this makes the traditional (and highly effective) (La)TeX development cycle of “Edit-> Process-> Preview” become -incredibly clumsy — <i>GSview</i> doesn’t make the same +rather clumsy — <i>GSview</i> doesn’t make the same mistake. <dl> <dt><tt><i>Acrobat Reader</i></tt><dd>browse <a href="ftp://ftp.adobe.com/pub/adobe/acrobatreader">ftp://ftp.adobe.com/pub/adobe/acrobatreader</a> <dt><tt><i>dvipdfm</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.zip">dviware/dvipdfm</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfm.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfm/">browse</a>) +<dt><tt><i>dvipdfmx</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfmx.zip">dviware/dvipdfmx</a> (<a href="ftp://cam.ctan.org/tex-archive/dviware/dvipdfmx.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/dviware/dvipdfmx/">browse</a>) <dt><tt><i>ghostscript</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/ghostscript/">nonfree/support/ghostscript/</a> <dt><tt><i>ghostview</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/support/ghostscript/gnu/ghostview/">support/ghostscript/gnu/ghostview/</a> <dt><tt><i>GSview</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/nonfree/support/ghostscript/ghostgum/">nonfree/support/ghostscript/ghostgum/</a> +<dt><tt><i>gv</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/support/gv.zip">support/gv</a> (<a href="ftp://cam.ctan.org/tex-archive/support/gv.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/support/gv/">browse</a>) <dt><tt><i>hyper.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyper.zip">macros/latex/contrib/hyper</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyper.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyper/">browse</a>) <dt><tt><i>hyperref.sty</i></tt><dd><a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.zip">macros/latex/contrib/hyperref</a> (<a href="ftp://cam.ctan.org/tex-archive/macros/latex/contrib/hyperref.tar.gz">gzipped tar</a>, <a href="http://www.tex.ac.uk/tex-archive/macros/latex/contrib/hyperref/">browse</a>) </dl> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-charshift.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-charshift.html index 12d73558d35..cc8cce1c5e3 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-charshift.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-charshift.html @@ -6,8 +6,7 @@ <p>You’ve innocently generated output, using <i>dvips</i>, and there are weird transpositions in it: for example, the <code>fi</code> ligature has appeared as a textsterling symbol. -This is an unwanted side-effect of the -precautions +This is an unwanted side-effect of the precautions outlined in <a href="FAQ-dvips-pdf.html">generating PostScript for PDF</a>. The <code>-G1</code> switch discussed in that question is appropriate for Knuth’s text fonts, but doesn’t work with text fonts that don’t follow diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html index bb6f760af39..35bea68fcd6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html @@ -2,10 +2,9 @@ <title>UK TeX FAQ -- question label dtx</title> </head><body> <h3>Documented LaTeX sources (<code>.dtx</code> files)</h3> -<p>LaTeX2e, and many support macro packages, are now written in a - -<a href="FAQ-lit.html">literate programming</a> style, -with source and documentation in the +<p>LaTeX2e, and most contributed macro packages, are now written in a +<a href="FAQ-lit.html">literate programming style</a>, with source and +documentation in the same file. This format, known as ‘doc’, in fact originated before the days of the LaTeX project as one of the “Mainz” series of packages. The documented sources conventionally have the suffix diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi-bmp.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi-bmp.html index 215ab5e047b..b552f590db1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi-bmp.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvi-bmp.html @@ -20,7 +20,6 @@ readers will have available). Other common examples are generation of sample bitmaps, and generation for insertion into some other application’s display — to insert equations into Microsoft PowerPoint, or to support the enhanced-<i>emacs</i> setup called - <a href="FAQ-WYGexpts.html"><i>preview</i>-<i>latex</i></a>. <p>In the past, the commonest way of generating bitmaps was to generate a PostScript file of the DVI and then use <i>ghostscript</i> to diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips-pdf.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips-pdf.html index 45e166d4278..8639e3fab52 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips-pdf.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dvips-pdf.html @@ -14,16 +14,13 @@ the character glyphs that make up the document. The following answers offer solutions to this (and other) problems of bad presentation. Issues covered are: <ul> - -<li> - <a href="FAQ-fuzzy-type3.html">Wrong type of fonts used</a>, which is +<li> <a href="FAQ-fuzzy-type3.html">Wrong type of fonts used</a>, which is the commonest cause of fuzzy text. - -<li> - <a href="FAQ-fuzzy-gs.html"><i>ghostscript</i> too old</a>, +<li> <a href="FAQ-fuzzy-gs.html"><i>Ghostscript</i> too old</a>, which can also result in fuzzy text. -<li> <a href="FAQ-fuzzy-T1.html">Switching to font encoding T1</a>, which - is yet another possible cause of fuzzy text. + +<li> <a href="FAQ-fuzzy-T1.html">Switching to font encoding T1 encoding</a>, + which is yet another possible cause of fuzzy text. <li> Another problem — missing characters — arises from an <a href="FAQ-distill-prob.html">aged version of <i>Adobe</i> <i>Distiller</i></a>. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-T1.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-T1.html index cdab3a7167c..1e665e46980 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-T1.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-T1.html @@ -10,12 +10,11 @@ has become fuzzy. The problem may arise whether you are using PostScript output and then distilling it, or you are using PDFTeX for the whole job. <p>In fact, this is the same problem as most others about the - <a href="FAQ-dvips-pdf.html">quality of PDF</a>: you’ve abandoned your previous setup using Type 1 versions of the CM fonts, and <i>dvips</i> has inserted Type 3 versions of the EC fonts into your document output. (See -“<a href="FAQ-adobetypen.html">Adobe font types</a>” +“<a href="FAQ-adobetypen.html">Adobe font types</a> for details of these font types; also, note that the font <em>encoding</em> T1 has nothing directly to do with the font <em>format</em> Type 1). diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-type3.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-type3.html index 9c02f418cdc..d4c8472b683 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-type3.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-fuzzy-type3.html @@ -15,12 +15,10 @@ up in <i>Reader</i>’s display as blurred blobs which are often not recognisable as the original letter, and are often not properly placed on the line. Nevertheless, even now, most TeX systems have <i>dvips</i> configured to use - <a href="FAQ-pk.html"><code>.pk</code> files</a> in its output. Even PDFTeX will use <code>.pk</code> files if it can see no alternative for a font in the document it is processing. <p>Our remedy is to use - “<a href="FAQ-adobetypen.html">Adobe Type 1</a>” versions of the fonts we need. Since Adobe are in the business of selling Type 1 fonts, <i>Reader</i> was of course made @@ -34,9 +32,8 @@ with, and even those relative sophisticates who use something as exotic as <i>Sabon</i> often find themselves using odd characters from CM without really intending to do so. Fortunately, rather good versions of the CM fonts are available from the AMS - (who have them courtesy of -<a href="FAQ-commercial.html">Blue Sky Research</a>). +<a href="FAQ-commercial.html">Blue Sky Research</a> and Y&Y). <p>Most modern systems have the fonts installed ready to use; and any system installed less than 3 years ago has a <i>dvips</i> configuration file ‘<code>pdf</code>’ that signals the use of the @@ -65,7 +62,6 @@ You may encounter the same warning messages as listed above. <p>If your system does not have the fonts, it won’t have the configuration file either; however, it might have the configuration file without the fonts. In either case, you need to - <a href="FAQ-inst1cm.html">install the fonts</a>. <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-type3">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=fuzzy-type3</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyper.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyper.html index cee095108bc..060a4c1b4a6 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyper.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-hyper.html @@ -5,15 +5,14 @@ <p>If you want on-line hypertext with a (La)TeX source, probably on the World Wide Web, there are four technologies to consider: <ul> -<li> Direct - <a href="FAQ-LaTeX2HTML.html">(La)TeX conversion to HTML</a>; +<li> Direct <a href="FAQ-LaTeX2HTML.html">(La)TeX conversion to HTML</a>; <li> Use <a href="FAQ-texinfo.html"><i>Texinfo</i></a>, and use the <i>info</i> viewer, or convert the <i>texinfo</i> to HTML; <li> Use Adobe Acrobat, which will preserve your typesetting - perfectly (see - <a href="FAQ-acrobat.html">Making Acrobat documents from LaTeX</a>); + perfectly + <a href="FAQ-acrobat.html">Making Acrobat PDF documents from LaTeX</a>; <li> The hyperTeX conventions (standardised <code>\</code><code>special</code> commands); there are supporting macro packages for Plain TeX and LaTeX). diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html index 2ce7546241e..08835e07d90 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-inst1cm.html @@ -2,8 +2,8 @@ <title>UK TeX FAQ -- question label inst1cm</title> </head><body> <h3>Installing the Bluesky versions of the CM fonts</h3> -<p>This is a specialised case of -<a href="FAQ-instfont.html">installing a font</a>, but it comes easier +<p>This is a specialised case of <a href="FAQ-instfont.html">installing a font</a>, +but it comes easier than most, since the font metrics are installed in every (La)TeX system before you even start. Indeed, most recent systems will have the Type 1 fonts themselves already installed, so that the job is @@ -17,8 +17,8 @@ so the first thing to do is to just try it. On a system that uses at a “command prompt” (<i>shell</i>, in a Unix-style system, “DOS box” in a Windows system). <p>If the command works at all, the console output of the command will -include a sequence of Type 1 font file names, listed as <code><cmr10.pfb></code> -and so on; +include a sequence of Type 1 font file names, listed as +<code><cmr10.pfb></code> and so on; this is <i>dvips</i> telling you it’s including the Type 1 font, and you need do no more. <p>If the test has failed, you need to install your own set of the fonts. @@ -62,7 +62,6 @@ loaded by the command dvips -Pbluesky myfile </pre> <p>Remember, after all such changes, the - <a href="FAQ-instpackages.html">file-name database must be refreshed</a>. <dl> <dt><tt><i>AMS fonts</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/fonts/amsfonts/ps-type1/">fonts/amsfonts/ps-type1/</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instfont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instfont.html index b3caf4a1a81..fe8d33b74fa 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instfont.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-instfont.html @@ -14,7 +14,7 @@ TDS tree; all these sub-trees have the directory describes the installation of fonts: follow the list through the “next question” links at the bottom of this answer to view them all. -Other answers discuss specific font families — see, for example, +Other answers discuss specific font families — for example, “<a href="FAQ-concrete.html">using the concrete fonts</a>”. <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instfont">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=instfont</a> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonfree.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonfree.html index 0fe3dfb236e..425df5a775d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonfree.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-nonfree.html @@ -18,8 +18,7 @@ use material they have retrieved from the <code>nonfree</code> tree. material via <a href="FAQ-findfiles.html">web search</a>) lists the licence details in each entry in its lists. -For details of the licence categories, see its - +For details of the licence categories, see its <a href="http://www.tex.ac.uk/tex-archive/help/Catalogue/licenses.html">list of licences</a>. <p><p>This question on the Web: <a href="http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonfree">http://www.tex.ac.uk/cgi-bin/texfaq2html?label=nonfree</a> </body> diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-notWYSIWYG.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-notWYSIWYG.html index 723bd5f81ba..069f6c96eb1 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-notWYSIWYG.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-notWYSIWYG.html @@ -31,11 +31,9 @@ TeX version 3). Modern systems that are similar in their approach are Lightning Textures (an extension of Blue Sky’s original TeX system for the Macintosh), and Scientific Word (which can also cooperate with a computer algebra system); both -these systems are -<a href="FAQ-commercial.html">commercially available</a>. +these systems are <a href="FAQ-commercial.html">commercially available</a>. <p>The issue has of recent years started to attract attention from TeX developers, and several interesting projects addressing the - “<a href="FAQ-WYGexpts.html">TeX document preparation environment</a>” are in progress. <p>Nevertheless, the TeX world has taken a long time to latch onto the diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html index fc609fc2173..d52bbafee1d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-psfontprob.html @@ -3,8 +3,7 @@ </head><body> <h3>Deploying Type 1 fonts</h3> <p>For the LaTeX user trying to use the -<a href="FAQ-usepsfont.html">PSNFSS</a> -package, three questions may arise. +<a href="FAQ-usepsfont.html">PSNFSS</a> package, three questions may arise. <p>First, you have to declare to the DVI driver that you are using PostScript fonts; in the case of <i>dvips</i>, this means adding lines to the <code>psfonts.map</code> file, so that <i>dvips</i> will know diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html index efc37e800b2..d1a4c3b0832 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-readtex.html @@ -12,7 +12,7 @@ systems are available, free, for most sorts of computer; the bad news is that you need a pretty complete TeX system even to read a single file, and complete TeX systems are pretty large. <p>TeX is a typesetting system that arose from a publishing project (see -“<a href="FAQ-whatTeX.html">what is TeX</a>”), +<a href="FAQ-whatTeX.html">what is TeX</a>), and its basic source is available free from its author. However, at its root, it is <em>just</em> a typesetting engine: even to view or to print the typeset output, you will need anciliary programs. In short, @@ -27,7 +27,7 @@ or <p>But beware — TeX makes no attempt to look like the sort of WYSIWYG system you’re probably used to (see -“<a href="FAQ-notWYSIWYG.html">why is TeX not WYSIWYG</a>”): +<a href="FAQ-notWYSIWYG.html">why is TeX not WYSIWYG</a>): while many modern versions of TeX have a compile–view cycle that rivals the best commercial word processors in its responsiveness, what you type is usually <em>markup</em>, which typically defines a logical diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-recovertex.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-recovertex.html index 67dab6387fd..f8111cdc156 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-recovertex.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-recovertex.html @@ -16,8 +16,7 @@ text retrieval is going to be possible; the (La)TeX markup that creates the typographic effects of the document needs to be recreated by editing. <p>If the file you have is in DVI format, many of the techniques -for -<a href="FAQ-toascii.html">converting (La)TeX to ASCII</a> are +for <a href="FAQ-toascii.html">converting (La)TeX to ASCII</a> are applicable. Consider <i>dvi2tty</i>, <i>crudetype</i> and <i>catdvi</i>. Remember that there are likely to be problems finding included material (such as included PostScript figures, that diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-symbols.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-symbols.html index 45bc5947a1d..fb854467f81 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-symbols.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-symbols.html @@ -14,15 +14,9 @@ commands and packages needed to produce them. <p>Other questions in this FAQ offer specific help on kinds of symbols: <ul> -<li> - <a href="FAQ-scriptfonts.html">Script fonts for mathematics</a> - -<li> - <a href="FAQ-numbersets.html">Fonts for the number sets</a> - -<li> - <a href="FAQ-prinvalint.html">Typesetting the principal value integral</a> - +<li> <a href="FAQ-scriptfonts.html">Script fonts for mathematics</a> +<li> <a href="FAQ-numbersets.html">Fonts for the number sets</a> +<li> <a href="FAQ-prinvalint.html">Typesetting the principal value integral</a> </ul> <dl> <dt><tt><i>Symbol List</i></tt><dd>Browse <a href="http://www.tex.ac.uk/tex-archive/info/symbols/comprehensive/">info/symbols/comprehensive/</a>; there are processed diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tds.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tds.html index e7734d8ef2d..8bae9c1f84a 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tds.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tds.html @@ -24,7 +24,6 @@ location of any local hierarchy is not only system dependent but also user dependent. Again, though, all files should be put under a local <i>/texmf</i> directory. <p>The TDS is published as the output of a TUG - <a href="FAQ-TUGstar.html">Technical Working Group</a>. You may browse an <a href="http://tug.org/tds/">on-line version</a> of the standard, and copies in several other formats (including source) are diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tempinst.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tempinst.html index 7f4a4f83fad..c91246a3eb9 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tempinst.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-tempinst.html @@ -13,9 +13,7 @@ file, and the <code>PATH</code> variable tells the shell where to find those fil built in to them. In most circumstances these paths are adequate, but one sometimes needs to extend them to pick up files in strange places: for example, we may wish to try a new bundle of packages -before - -<a href="FAQ-instpackages.html">installing them ‘properly’</a>. To do +before <a href="FAQ-instpackages.html">installing them ‘properly’</a>. To do this, we need to change the relevant path as TeX perceives it. However, we don’t want to throw away TeX’s built-in path (all of a sudden, TeX won’t know how to deal with all sorts of things). diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toascii.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toascii.html index c42cb70514b..bc378c856d4 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toascii.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-toascii.html @@ -41,8 +41,6 @@ roots, ...) into “ASCII art” that spreads over multiple lines if necessary. The result is more readable to human beings than the flat-style TeX code. <p>Another significant possibility is to use one of the - - <a href="FAQ-LaTeX2HTML.html">HTML-generation solutions</a>, and then to use a browser such as <i>lynx</i> to dump the resulting HTML as plain text. diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepsfont.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepsfont.html index 4314ad333d2..512f60c3142 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepsfont.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-usepsfont.html @@ -36,8 +36,7 @@ the fonts is not the same as Computer Modern it will be up to you to redefine various macros and accents, or you can use the font re-encoding mechanisms available in many drivers and in <i>ps2pk</i> and <i>afm2tfm</i>. -<p>Victor Eijkhout’s -<a href="FAQ-lollipop.html">Lollipop package</a> +<p>Victor Eijkhout’s <a href="FAQ-lollipop.html">Lollipop package</a> supports declaration of font families and styles in a similar way to LaTeX’s NFSS, and so is easy to use with PostScript fonts. <p>Some common problems encountered are discussed elsewhere diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/index.html b/Master/texmf-doc/doc/english/FAQ-en/html/index.html index 5af2930d83c..da4e7e2732b 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/html/index.html +++ b/Master/texmf-doc/doc/english/FAQ-en/html/index.html @@ -575,5 +575,5 @@ Reinhard Zierke. "<a href="FAQ-noans.html">Improving the FAQ</a>" or "<a href="FAQ-newans.html">Extending the FAQ</a>". <p> - This is FAQ version 3.16c, last modified on 2006-12-11. + This is FAQ version 3.16c-1, last modified on 2006-12-18. </address> |