diff options
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/faqbody.tex')
| -rw-r--r-- | Master/texmf-doc/doc/english/FAQ-en/faqbody.tex | 242 |
1 files changed, 98 insertions, 144 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex b/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex index f0d68addcb0..b0e724f163d 100644 --- a/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex +++ b/Master/texmf-doc/doc/english/FAQ-en/faqbody.tex @@ -1,8 +1,8 @@ -\def\faqfileversion{3.16c} \def\faqfiledate{2006-12-11} +\def\faqfileversion{3.16c-1} \def\faqfiledate{2006-12-18} % -% The above line defines the file version, and must remain the first -% line with any `assignment' in the file, or things will blow up -% nastily +% The above line defines the file version and date, and must remain +% the first line with any `assignment' in the file, or things will +% blow up in a stupid fashion % % get lists of CTAN labels % @@ -439,7 +439,7 @@ tricky. Lamport's last version of \LaTeX{} (\LaTeXo{}, last updated in 1992) was superseded in 1994 by a new version (\LaTeXe{}) provided by -\nothtml{the \LaTeX{} team (}\Qref{the \LaTeX{} team}{Q-LaTeX3}\nothtml{)}. +\Qref*{the \LaTeX{} team}{Q-LaTeX3}. \LaTeXe{} is now the only readily-available version of \LaTeX{}, and draws together several threads of \LaTeX{} development from the later days of \LaTeXo{}. @@ -548,8 +548,7 @@ prodigious energy. Some support is available via a % ! line break \AMSTeX{} is a \TeX{} macro package, originally written by Michael Spivak for the American Mathematical Society (\acro{AMS}) during 1983--1985 and -is described in the book \nothtml{``The Joy of \TeX{}'' (}% -\htmlonly{``}\Qref{The Joy of \TeX{}}{Q-books}\latexhtml{)}{''}. +is described in the book ``\Qref*{The Joy of \TeX{}}{Q-books}''. 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 @@ -736,14 +735,11 @@ to build substantial new macro packages based on \TeX{}. For the even longer term, there are various projects to build a \emph{successor} to \TeX{}; see, for example, the -\begin{wideversion} - \Qref{Omega/Aleph}{Q-omegaleph} and \Qref{\ExTeX{}}{Q-extex} - projects. -\end{wideversion} \begin{narrowversion} Omega/Aleph and \ExTeX{} projects (questions - \Qref[\nothtml]{}{Q-omegaleph} \Qref[and]{}{Q-extex}). \end{narrowversion} +\Qref[\nothtml]{Omega/Aleph}{Q-omegaleph} +\Qref[and]{\ExTeX{}}{Q-extex}\narrowonly{)}. \Question[Q-readtex]{Reading \AllTeX{} files} @@ -760,7 +756,7 @@ 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 -\htmlonly{``}\Qref[question]{what is \TeX{}}{Q-whatTeX}\htmlonly{''}), +\wideonly{``}\Qref[question]{what is \TeX{}}{Q-whatTeX}\wideonly{''}), and its basic source is available free from its author. However, at its root, it is \emph{just} a typesetting engine: even to view or to print the typeset output, you will need anciliary programs. In short, @@ -776,7 +772,7 @@ or But beware~--- \TeX{} makes no attempt to look like the sort of \WYSIWYG{} system you're probably used to (see % beware line wrap -\htmlonly{``}\Qref[question]{why is \TeX{} not \WYSIWYG{}}{Q-notWYSIWYG}\htmlonly{''}): +\wideonly{``}\Qref[question]{why is \TeX{} not \WYSIWYG{}}{Q-notWYSIWYG}\wideonly{''}): 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 \emph{markup}, which typically defines a logical @@ -823,13 +819,11 @@ last `great' \TeX{} version change, at the turn of the 1990s, to 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 \nothtml{commercially available (}% -\Qref{commercially available}{Q-commercial}\nothtml{)}. +these systems are \Qref*{commercially available}{Q-commercial}. The issue has of recent years started to attract attention from \TeX{} developers, and several interesting projects addressing the -\nothtml{``\TeX{} document preparation environment'' (}% beware line breaks -\htmlonly{``}\Qref{\TeX{} document preparation environment}{Q-WYGexpts}\latexhtml{)}{''} +``\Qref*{\TeX{} document preparation environment}{Q-WYGexpts}'' are in progress. Nevertheless, the \TeX{} world has taken a long time to latch onto the @@ -1926,15 +1920,9 @@ commands and packages needed to produce them. Other questions in this \acro{FAQ} offer specific help on kinds of symbols: \begin{itemize} -\item \nothtml{Script fonts for mathematics (}% - \Qref[question]{Script fonts for mathematics}{Q-scriptfonts}% - \nothtml{)} -\item \nothtml{Fonts for the number sets (}% - \Qref[question]{Fonts for the number sets}{Q-numbersets}% - \nothtml{)} -\item \nothtml{Typesetting the principal value integral (}% - \Qref[question]{Typesetting the principal value integral}{Q-prinvalint}% - \nothtml{)} +\item \Qref*{Script fonts for mathematics}{Q-scriptfonts} +\item \Qref*{Fonts for the number sets}{Q-numbersets} +\item \Qref*{Typesetting the principal value integral}{Q-prinvalint} \end{itemize} \begin{ctanrefs} \item[Symbol List]Browse \CTANref{symbols}; there are processed @@ -2211,10 +2199,9 @@ classes and packages may choose to load other packages.) \Question[Q-dtx]{Documented \LaTeX{} sources (\texttt{.dtx} files)} -\LaTeXe{}, and many support macro packages, are now written in a -\nothtml{literate programming style (}% beware line break -\Qref{literate programming}{Q-lit}\latexhtml{)}{ style}, -with source and documentation in the +\LaTeXe{}, and most contributed macro packages, are now written in a +\Qref*{literate programming style}{Q-lit}, with source and +documentation in the same file. This format, known as `doc', in fact originated before the days of the \LaTeX{} project as one of the ``Mainz'' series of packages. The documented sources conventionally have the suffix @@ -2458,8 +2445,7 @@ dependent. Again, though, all files should be put under a local \path{/texmf} directory. The \acro{TDS} is published as the output of a \acro{TUG} % beware line wrap -\nothtml{Technical Working Group (}% -\Qref{Technical Working Group}{Q-TUG*}\nothtml{)}. +\Qref*{Technical Working Group}{Q-TUG*}. You may browse an \href{http://tug.org/tds/}{on-line version} of the standard, and copies in several other formats (including source) are available on \acro{CTAN}. @@ -2705,14 +2691,8 @@ The Catalogue (one of the prime sources for finding \TeX{}-related material via \nothtml{web search~--- }% \Qref{web search}{Q-findfiles}) lists the licence details in each entry in its lists. -For details of the licence categories, see its -\begin{narrowversion} % really non-hyper version - list of licences~--- see - \URL{http://www.tex.ac.uk/tex-archive/help/Catalogue/licenses.html} -\end{narrowversion} -\begin{wideversion} +For details of the licence categories, see its % !line break \href{http://www.tex.ac.uk/tex-archive/help/Catalogue/licenses.html}{list of licences}. -\end{wideversion} \Question[Q-uploads]{Contributing a file to the archives} @@ -2947,11 +2927,10 @@ see \Qref{}{Q-commercial} for details of commercial packages. \end{ctanrefs} \item[Linux] Linux users may use te\TeX{} (see above). - The most recent offering is a free version of the - commercial \nothtml{V\TeX{} (see }% - \Qref[question]{V\TeX{}}{Q-commercial}\nothtml{)}, which among other + A free version of the commercial + \Qref*{V\TeX{}}{Q-commercial} is available, which among other things, specialises in direct production of \acro{PDF} from - \AllTeX{} input. + \AllTeX{} input. Unfortunately, it's no longer supported. \begin{ctanrefs} \item[tetex]Browse \CTANref{tetex} \item[vtex]\CTANref{vtex-linux} @@ -3048,9 +3027,9 @@ see \Qref{}{Q-commercial} for details of commercial packages. \item[djgpp]\CTANref{djgpp} \end{ctanrefs} \item[\acro{PC}: \acro{OS/}2] \acro{OS/}2 may also use a free version of the - commercial \nothtml{V\TeX{} (see }% - \Qref[question]{V\TeX{}}{Q-commercial}\nothtml{)}, which specialises - in direct production of \acro{PDF} from \AllTeX{} input. + commercial \Qref*{V\TeX{}}{Q-commercial}, which specialises + in direct production of \acro{PDF} from \AllTeX{} input. (This + version is, like the Linux version, unfortunately no longer supported.) \begin{ctanrefs} \item[vtex]\CTANref{vtex-os2} \item[vtex \nothtml{\rmfamily}required common files]\CTANref{vtex-common} @@ -3496,8 +3475,7 @@ 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-\ProgName{emacs} setup called -\nothtml{\ProgName{preview}-\ProgName{latex} (}% beware line breaks -\Qref{\ProgName{preview}-\ProgName{latex}}{Q-WYGexpts}\nothtml{)}. +\Qref*{\ProgName{preview}-\ProgName{latex}}{Q-WYGexpts}. In the past, the commonest way of generating bitmaps was to generate a \PS{} file of the \acro{DVI} and then use \ProgName{ghostscript} to @@ -3780,9 +3758,7 @@ multiple lines if necessary. The result is more readable to human beings than the flat-style \TeX{} code. Another significant possibility is to use one of the -\nothtml{\acro{HTML}-generation solutions (}% -% beware line wrap -\Qref{\acro{HTML}-generation solutions}{Q-LaTeX2HTML}\nothtml{)}, +\Qref*{\acro{HTML}-generation solutions}{Q-LaTeX2HTML}, and then to use a browser such as \ProgName{lynx} to dump the resulting \acro{HTML} as plain text. \begin{ctanrefs} @@ -3928,9 +3904,7 @@ For today, possible packages are: robust against the macros you include in your document, and it's also pretty fast. \item[\ProgName{TeXpider}] a commercial program from - % beware line breaks - \nothtml{MicroPress (see }% - \Qref[question]{Micropress}{Q-commercial}\latexhtml{),}{,} which is + \Qref*{Micropress}{Q-commercial}, which is described on \URL{http://www.micropress-inc.com/webb/wbstart.htm}; it uses bitmaps for equations. \item[\ProgName{Hevea}] a compiled program that supports \LaTeX{} @@ -4088,8 +4062,7 @@ creates the typographic effects of the document needs to be recreated by editing. If the file you have is in \acro{DVI} format, many of the techniques -for \nothtml{converting \AllTeX{} to \acro{ASCII} (}% -\Qref{converting \AllTeX{} to \acro{ASCII}}{Q-toascii}\nothtml{)} are +for \Qref*{converting \AllTeX{} to \acro{ASCII}}{Q-toascii} are applicable. Consider \ProgName{dvi2tty}, \ProgName{crudetype} and \ProgName{catdvi}. Remember that there are likely to be problems finding included material (such as included \PS{} figures, that @@ -4128,10 +4101,8 @@ to map to its standard Unicode representation. \Question[Q-LaTeXtoPlain]{Translating \LaTeX{} to Plain \TeX{}} Unfortunately, no ``general'', simple, automatic process is likely to -succeed at this task. See -% beware (lots of) line breaks -\nothtml{``How does \LaTeX{} relate to Plain \TeX{}'' (}% -\htmlonly{``}\Qref{How does \LaTeX{} relate to Plain \TeX{}}{Q-LaTeXandPlain}\latexhtml{)}{''} +succeed at this task. See % ! line break +``\Qref{How does \LaTeX{} relate to Plain \TeX{}}{Q-LaTeXandPlain}'' for further details. Translating a document designed to work with \LaTeX{} into one @@ -4381,9 +4352,7 @@ Modern \TeX{} implementations come with a bunch of search paths built in to them. In most circumstances these paths are adequate, but one sometimes needs to extend them to pick up files in strange places: for example, we may wish to try a new bundle of packages -before \nothtml{installing them `properly' (}% -% beware line break -\Qref{installing them `properly'}{Q-instpackages}\nothtml{)}. To do +before \Qref*{installing them `properly'}{Q-instpackages}. 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). @@ -4588,9 +4557,9 @@ stored in a directory its own sub-tree in the installation's follow the list through the ``next question'' links at the bottom of this answer to view them all. \end{htmlversion} -Other answers discuss specific font families~--- see, for example, +Other answers discuss specific font families~--- for example, % ! line break -\htmlonly{``}\Qref[\htmlonly]{using the concrete fonts}{Q-concrete}\htmlonly{''}. +``\Qref*{using the concrete fonts}{Q-concrete}''. \Question[Q-instmffont]{Installing a font provided as \MF{} source} @@ -4653,8 +4622,8 @@ Documentation of the \Package{psnfss} bundle is provided in \Question[Q-inst1cm]{Installing the Bluesky versions of the CM~fonts} -This is a specialised case of \nothtml{installing a font (}% -\Qref{installing a font}{Q-instfont}\nothtml{)}, but it comes easier +This is a specialised case of \Qref*{installing a font}{Q-instfont}, +but it comes easier than most, since the font metrics are installed in every \AllTeX{} system before you even start. Indeed, most recent systems will have the Type~1 fonts themselves already installed, so that the job is @@ -4669,8 +4638,8 @@ at a ``command prompt'' (\ProgName{shell}, in a Unix-style system, ``\acro{DOS} box'' in a Windows system). If the command works at all, the console output of the command will -include a sequence of Type~1 font file names, listed as |<cmr10.pfb>| -and so on; +include a sequence of Type~1 font file names, listed as +\texttt{<cmr10.pfb>} and so on; this is \ProgName{dvips} telling you it's including the Type~1 font, and you need do no more. @@ -4720,8 +4689,7 @@ loaded by the command \end{verbatim} Remember, after all such changes, the % beware line breaks -\nothtml{file-name database must be refreshed (}% -\Qref{file-name database must be refreshed}{Q-instpackages}\nothtml{)}. +\Qref*{file-name database must be refreshed}{Q-instpackages}. \begin{ctanrefs} \item[AMS fonts]Browse \CTANref{ams-AMStype1} \item[CM fonts]Browse \CTANref{bluesky} @@ -5111,8 +5079,7 @@ redefine various macros and accents, or you can use the font re-encoding mechanisms available in many drivers and in \ProgName{ps2pk} and \ProgName{afm2tfm}. -Victor Eijkhout's\nothtml{ Lollipop package (}% -\Qref{Lollipop package}{Q-lollipop}\nothtml{)} +Victor Eijkhout's \Qref*{Lollipop package}{Q-lollipop} supports declaration of font families and styles in a similar way to \LaTeX{}'s \acro{NFSS}, and so is easy to use with \PS{} fonts. @@ -5234,8 +5201,7 @@ software, and is available on \acro{CTAN}. \Question[Q-psfontprob]{Deploying Type 1 fonts} For the \LaTeX{} user trying to use the -\nothtml{\acro{PSNFSS} (}\Qref{\acro{PSNFSS}}{Q-usepsfont}\nothtml{)} -package, three questions may arise. +\Qref*{\acro{PSNFSS}}{Q-usepsfont} package, three questions may arise. First, you have to declare to the \acro{DVI} driver that you are using \PS{} fonts; in the case of \ProgName{dvips}, this means adding @@ -5302,8 +5268,8 @@ mathematics include: alphabets, in upright and italic shapes, medium and bold weights; the fifth font contains a small selection of ``blackboard bold'' characters (chosen for their mathematical significance). Support - under \LaTeXe{} is available in \nothtml{\acro{PSNFSS} (}% - \Qref{\acro{PSNFSS}}{Q-usepsfont}\nothtml{)}; the fonts are + under \LaTeXe{} is available in + \Qref*{\acro{PSNFSS}}{Q-usepsfont}; the fonts are licensed under the \acro{GPL}, with legalese permitting the use of the fonts in published documents. \item[Fourier/Utopia](15 fonts) Michel Bovani\\ @@ -5675,9 +5641,8 @@ print file (\PS{} or \acro{PDF}) for their output device. You've innocently generated output, using \ProgName{dvips}, and there are weird transpositions in it: for example, the \texttt{fi} ligature has appeared as a \textsterling{} symbol. -This is an unwanted side-effect of the -precautions\nothtml{ about generating \PS{} for \acro{PDF}} % beware line break -outlined in \Qref[question]{generating \PS{} for PDF}{Q-dvips-pdf}. +This is an unwanted side-effect of the precautions +outlined in \Qref*{generating \PS{} for PDF}{Q-dvips-pdf}. The \texttt{-G1} switch discussed in that question is appropriate for Knuth's text fonts, but doesn't work with text fonts that don't follow Knuth's patterns (such as fonts supplied by Adobe). @@ -5924,15 +5889,14 @@ no support for using fonts according to the \acro{OT}1 encoding. If you want on-line hypertext with a \AllTeX{} source, probably on the World Wide Web, there are four technologies to consider: \begin{itemize} -\item Direct \nothtml{\AllTeX{} conversion to \acro{HTML} (}% - \Qref{\AllTeX{} conversion to \acro{HTML}}{Q-LaTeX2HTML}\nothtml{)}; +\item Direct \Qref{\AllTeX{} conversion to \acro{HTML}}{Q-LaTeX2HTML}; % beware line break \item Use \Qref*{\Package{Texinfo}}{Q-texinfo}, and use the \ProgName{info} viewer, or convert the \Package{texinfo} to \acro{HTML}; \item Use Adobe Acrobat, which will preserve your typesetting - perfectly (see - \Qref[question]{Making Acrobat documents from \LaTeX{}}{Q-acrobat}); + perfectly + \Qref*{Making Acrobat \acro{PDF} documents from \LaTeX{}}{Q-acrobat}; \item The hyper\TeX{} conventions (standardised \csx{special} commands); there are supporting macro packages for Plain \TeX{} and \LaTeX{}). @@ -5967,13 +5931,13 @@ releases of \ProgName{ghostscript} or Acrobat Distiller. \Question[Q-acrobat]{Making Acrobat \acro{PDF} documents from \AllTeX{}} -There are three general routes to Acrobat output: Adobe's original +There are three general routes to \acro{PDF} output: Adobe's original `distillation' route (via \PS{} output), conversion of a \acro{DVI} file, and the use of a direct \acro{PDF} generator such as -\PDFTeX{} (see \Qref[question]{\PDFTeX{}}{Q-whatpdftex}) or +\Qref*{\PDFTeX{}}{Q-whatpdftex}) or MicroPress's V\TeX{} (which comes both as a % ! line break \Qref*{commercial version}{Q-commercial} for Windows PCs, and as a -\Qref*{`free' version)}{Q-TeXsystems} for Linux systems). +\Qref*{`free' version)}{Q-TeXsystems} for \acro{OS}/2 and Linux systems). For simple documents (with no hyper-references), you can either \begin{itemize} @@ -5984,71 +5948,69 @@ For simple documents (with no hyper-references), you can either \acro{PDF}writer in place of a printer driver (this route is a dead end: the \acro{PDF}writer cannot create hyperlinks); \item process the document in the normal way and generate \acro{PDF} - direct from the \acro{DVI} with \ProgName{dvipdfm}; or + direct from the \acro{DVI} using + \ProgName{dvipdfm}/\ProgName{dvipdfmx}; or \item process the document direct to \acro{PDF} with \PDFTeX{} or V\TeX{}. \PDFTeX{} has the advantage of availability for a wide range of platforms, V\TeX{} - (available commercially for Windows, or free of charge for Linux or - \acro{OS/}2) has wider graphics capability, dealing with - encapsulated \PS{} and some in-line \PS{}. + (available commercially for Windows, or free of charge, but + unsupported, for Linux or \acro{OS/}2) has wider graphics + capability, dealing with encapsulated \PS{} and some in-line \PS{}. \end{itemize} 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 Hyper\TeX{} specification -(see \Qref[question]{Making hypertext documents from \TeX{}}{Q-hyper}): +capable of conforming to the +\Qref{Hyper\TeX{} specification}{Q-hyper}: Heiko Oberdiek's \Package{hyperref}, and Michael Mehlich's -\Package{hyper}. -uses a configuration file to determine how it will generate hypertext; -it can operate using \PDFTeX{} primitives, the hyper\TeX{} +\Package{hyper}. (In practice, almost everyone uses +\Package{hyperref}; \Package{hyper} hasn't been updated since 2000.) +\Package{Hyperref} can often determine how it should generate +hypertext from its environment, but there is a wide set of +configuration options you can give via \csx{usepackage}. The package +can operate using \PDFTeX{} primitives, the hyper\TeX{} \csx{special}s, or \acro{DVI} driver-specific \csx{special} commands. -%% Both \ProgName{dvips} and \YandY{}'s \acro{\ProgName{DVIPSONE}} -\ProgName{Dvips} -translates the \acro{DVI} with these \csx{special} commands into +Both \ProgName{dvips} and \YandY{}'s \acro{\ProgName{DVIPSONE}} can +translate the \acro{DVI} with these \csx{special} commands into \PS{} acceptable to Distiller, and \ProgName{dvipdfm} has \csx{special} commands of its own. -(In practice, almost everyone uses \Package{hyperref}; \Package{hyper} -hasn't been updated since 2000.) - -If you use Plain \TeX{}, \Eplain{} macro package can help you create -Acrobat documents with hyper-references (see -\htmlonly{``}\Qref[question]{what is \Eplain{}}{Q-eplain}\htmlonly{''}). +If you use Plain \TeX{}, the \Qref*{\Eplain{} macros}{Q-eplain} can +help you create \acro{PDF} documents with hyper-references. It can operate using \PDFTeX{} primitives, or \csx{special} commands for the \ProgName{dvipdfm} \acro{DVI} driver. -There is no free implementation of all of \ProgName{Adobe} +While there is no free implementation of all of \ProgName{Adobe} \ProgName{Distiller}'s -functionality, any but the very oldest versions of \ProgName{ghostscript} -provide pretty reliable distillation (but beware of the problems -discussed in -% beware line break -\Qref[question]{\ProgName{dvips} output for distillation}{Q-dvips-pdf}). -In fact, \ProgName{Distiller} itself is now remarkably cheap (for -academics at least). +functionality, any but the very oldest versions of \ProgName{Ghostscript} +provide pretty reliable distillation (but beware of the problems with +\Qref*{\ProgName{dvips} output for distillation}{Q-dvips-pdf}). For viewing (and printing) the resulting files, Adobe's \ProgName{Acrobat} \ProgName{Reader} is available for a fair range of platforms; for those for which Adobe's reader is unavailable, remotely current versions of \ProgName{ghostscript} combined with -\ProgName{ghostview} or \ProgName{GSview} can display and print -\acro{PDF} files. +\ProgName{gv}, \ProgName{GSview} (or even the unsupported +\ProgName{ghostview}) can display and print \acro{PDF} files, as can +\ProgName{xpdf}. -In many circumstances, \ProgName{ghostscript} combined with a viewer +In many circumstances, \ProgName{Ghostscript} combined with a viewer application is actually preferable to Acrobat Reader. For example, on -Windows Acrobat Reader locks the |.pdf| file it's displaying: this +Windows Acrobat Reader locks the \texttt{.pdf} file it's displaying: this makes the traditional (and highly effective) \AllTeX{} development cycle of ``Edit\arrowhyph{}Process\arrowhyph{}Preview'' become -incredibly clumsy~--- \ProgName{GSview} doesn't make the same +rather clumsy~--- \ProgName{GSview} doesn't make the same mistake. \begin{ctanrefs} \item[\nothtml{\rmfamily}Acrobat Reader]browse \URL{ftp://ftp.adobe.com/pub/adobe/acrobatreader} \item[dvipdfm]\CTANref{dvipdfm} +\item[dvipdfmx]\CTANref{dvipdfmx} \item[ghostscript]Browse \CTANref{ghostscript} \item[ghostview]Browse \CTANref{ghostview} \item[GSview]Browse \CTANref{gsview} +\item[gv]\CTANref{gv} \item[hyper.sty]\CTANref{hyper} \item[hyperref.sty]\CTANref{hyperref} \end{ctanrefs} @@ -6068,16 +6030,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: \begin{itemize} -% beware line breaks (two lines) -\item \nothtml{Wrong type of fonts used (}% - \Qref{Wrong type of fonts used}{Q-fuzzy-type3}\nothtml{)}, which is +\item \Qref*{Wrong type of fonts used}{Q-fuzzy-type3}, which is the commonest cause of fuzzy text. -% beware line breaks (two lines) -\item \nothtml{\ProgName{ghostscript} too old (}% - \Qref{\ProgName{ghostscript} too old}{Q-fuzzy-gs}\nothtml{)}, +\item \Qref*{\ProgName{Ghostscript} too old}{Q-fuzzy-gs}, which can also result in fuzzy text. -\item \Qref*{Switching to font encoding \acro{T}1}{Q-fuzzy-T1}, which - is yet another possible cause of fuzzy text. +% beware line breaks +\item \Qref*{Switching to font encoding \acro{T}1 encoding}{Q-fuzzy-T1}, + which is yet another possible cause of fuzzy text. \item Another problem~--- missing characters~--- arises from an % beware line breaks \Qref*{aged version of \ProgName{Adobe}~\ProgName{Distiller}}{Q-distill-prob}. @@ -6118,14 +6077,12 @@ up in \ProgName{Reader}'s display as blurred blobs which are often not recognisable as the original letter, and are often not properly placed on the line. Nevertheless, even now, most \TeX{} systems have \ProgName{dvips} configured to use -\nothtml{\texttt{.pk} files (}% beware line breaks -\Qref{\texttt{.pk} files}{Q-pk}\nothtml{)} in its output. Even +\Qref*{\texttt{.pk} files}{Q-pk} in its output. Even \PDFTeX{} will use \texttt{.pk} files if it can see no alternative for a font in the document it is processing. Our remedy is to use -% perniciously dangerous line wraps await editors here ;-) -\latexhtml{``Adobe Type~1'' (}{``}\Qref{Adobe Type~1}{Q-adobetypen}\latexhtml{)}{''} +``\Qref*{Adobe Type~1}{Q-adobetypen}'' versions of the fonts we need. Since Adobe are in the business of selling Type~1 fonts, \ProgName{Reader} was of course made to deal with them really rather well, from the very beginning. @@ -6140,9 +6097,8 @@ with, and even those relative sophisticates who use something as exotic as \ProgName{Sabon} often find themselves using odd characters from \acro{CM} without really intending to do so. Fortunately, rather good versions of the \acro{CM} fonts are available from the \acro{AMS} -% beware line break -(who have them courtesy of \nothtml{Blue Sky Research~---} -\Qref{Blue Sky Research}{Q-commercial}\nothtml{ and \YandY{}}). +(who have them courtesy of % ! line break +\Qref{Blue Sky Research}{Q-commercial} and \YandY{}). Most modern systems have the fonts installed ready to use; and any system installed less than 3~years ago has a \ProgName{dvips} @@ -6174,8 +6130,7 @@ You may encounter the same warning messages as listed above. 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 -\nothtml{install the fonts (}% beware line breaks -\Qref{install the fonts}{Q-inst1cm}\nothtml{)}. +\Qref*{install the fonts}{Q-inst1cm}. \Question[Q-fuzzy-gs]{Fuzzy fonts because \ProgName{Ghostscript} too old} \keywords{crippled blurry} @@ -6213,12 +6168,11 @@ output and then distilling it, or you are using \PDFTeX{} for the whole job. In fact, this is the same problem as most others about the -\nothtml{quality of \acro{PDF} (}% beware line break -\Qref{quality of \acro{PDF}}{Q-dvips-pdf}\nothtml{)}: you've abandoned +\Qref*{quality of \acro{PDF}}{Q-dvips-pdf}: you've abandoned your previous setup using Type~1 versions of the \acro{CM} fonts, and \ProgName{dvips} has inserted Type~3 versions of the \acro{EC} fonts into your document output. (See % beware line break -\htmlonly{``}\Qref[question]{Adobe font types}{Q-adobetypen}\htmlonly{''} +``\Qref*{Adobe font types}{Q-adobetypen} for details of these font types; also, note that the font \emph{encoding}~\acro{T}1 has nothing directly to do with the font \emph{format}~Type~1). @@ -6266,7 +6220,7 @@ includes the switch. The switch is not without its problems; pre-2003 versions of \ProgName{dvips} will apply it to Adobe fonts as well, causing -\nothtml{havoc (}\Qref{havoc}{Q-charshift}\nothtml{)}, but fortunately +\Qref*{havoc}{Q-charshift}, but fortunately that problem is usually soluble. However, a document using both \acro{CM} and Adobe-specified fonts is stuck. The only real solution is either to upgrade \ProgName{dvips}, or to spend money to upgrade @@ -14631,8 +14585,8 @@ following minimal solution: \begin{wideversion} \begin{verbatim} \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} \end{verbatim} @@ -14642,8 +14596,8 @@ following minimal solution: \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} \end{verbatim} |