summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/faq-hyp+pdf.tex
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2012-03-30 22:59:00 +0000
committerKarl Berry <karl@freefriends.org>2012-03-30 22:59:00 +0000
commitd82e1c23973fd0271f93686f487bd1cee8dcd947 (patch)
treeaa2b560201147b7fa4c9a307309855ed5c7ef6a6 /Master/texmf-dist/doc/generic/FAQ-en/faq-hyp+pdf.tex
parent0c2a4b76e6f5683bb95ad5a176f157745fd78dc7 (diff)
FAQ-en (30mar12)
git-svn-id: svn://tug.org/texlive/trunk@25791 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/faq-hyp+pdf.tex')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/faq-hyp+pdf.tex179
1 files changed, 107 insertions, 72 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-hyp+pdf.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-hyp+pdf.tex
index 3c54be82162..546ed139c74 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/faq-hyp+pdf.tex
+++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-hyp+pdf.tex
@@ -1,83 +1,34 @@
-% $Id: faq-hyp+pdf.tex,v 1.3 2011/03/08 20:08:01 rf10 Exp rf10 $
+% $Id: faq-hyp+pdf.tex,v 1.5 2011/12/24 23:13:57 rf10 Exp rf10 $
\section{Hypertext and \acro{PDF}}
-\Question[Q-hyper]{Making hypertext documents from \TeX{}}
-
-If you want on-line hypertext with a \AllTeX{} source, probably on the
-World Wide Web, there are four technologies to consider:
-\begin{itemize}
-\item Direct \Qref{\AllTeX{} conversion to \acro{HTML}}{Q-LaTeX2HTML};
-% beware line break
-\item Use \Qref*{\Package{Texinfo}}{Q-texinfo},
- and use the \ProgName{info} viewer, or convert the \Package{texinfo}
- to \acro{HTML};
-\item Use Adobe Acrobat, which will preserve your typesetting
- perfectly
- \Qref*{Making Acrobat \acro{PDF} documents from \LaTeX{}}{Q-acrobat};
-\item The hyper\TeX{} conventions (standardised \csx{special}
- commands); there are supporting macro packages for \plaintex{} and
- \LaTeX{}).
-\end{itemize}
-
-The Hyper\TeX{} project extended the functionality of all the
-\LaTeX{} cross-referencing commands (including the table of contents)
-to produce \csx{special} commands which are parsed by \acro{DVI} processors
-conforming to the Hyper\TeX{} guidelines;
-it provides general hypertext links, including those
-to external documents.
-
-The Hyper\TeX{} specification says that conformant viewers/translators
-must recognize the following set of \csx{special} commands:
-\begin{description}
-\item[href:] |html:<a href = "href_string">|
-\item[name:] |html:<a name = "name_string">|
-\item[end:] |html:</a>|
-\item[image:] |html:<img src = "href_string">|
-\item[base\_name:] |html:<base href = "href_string">|
-\end{description}
-
-The \emph{href}, \emph{name} and \emph{end} commands are used to do
-the basic hypertext operations of establishing links between sections
-of documents.
-
-Further details are available on \URL{http://arXiv.org/hypertex/}; there
-are two commonly-used implementations of the specification, a
-modified \ProgName{xdvi} and (recent releases of)
-\ProgName{dvips}. Output from the latter may be used in recent
-releases of \ProgName{ghostscript} or Acrobat Distiller.
-
-\Question[Q-acrobat]{Making Acrobat \acro{PDF} documents from \AllTeX{}}
+\Question[Q-acrobat]{Making \acro{PDF} documents from \AllTeX{}}
There are three general routes to \acro{PDF} output: Adobe's original
-`distillation' route (via \PS{} output), conversion of a
-\acro{DVI} file, and the use of a direct \acro{PDF} generator such as
-\Qref*{\PDFTeX{}}{Q-whatpdftex}) or
-MicroPress's V\TeX{} (which comes both as a % ! line break
-\Qref*{commercial version}{Q-commercial} for Windows PCs, and as a
-\Qref*{`free' version)}{Q-TeXsystems} for \acro{OS}/2 and Linux systems).
+`distillation' route (via \PS{} output), direct conversion of a
+\acro{DVI} file, and the use of a direct \tex{}-like \acro{PDF}
+generator such as \Qref*{\PDFTeX{}}{Q-whatpdftex}.
For simple documents (with no hyper-references), you can either
\begin{itemize}
\item process the document in the normal way, produce \PS{}
output and distill it;
-\item (on a Windows or Macintosh machine with the appropriate Adobe
- tools installed) pass the output through the
- \acro{PDF}writer in place of a printer driver (this route is a dead
- end: the \acro{PDF}writer cannot create hyperlinks);
-\item process the document in the normal way and generate \acro{PDF}
- direct from the \acro{DVI} using
- \ProgName{dvipdfm}/\ProgName{dvipdfmx}; or
-\item process the document direct to \acro{PDF} with \PDFTeX{} or
- V\TeX{}. \PDFTeX{} has
- the advantage of availability for a wide range of platforms, V\TeX{}
- (available commercially for Windows, or free of charge, but
- unsupported, for Linux or \acro{OS/}2) has wider graphics
- capability, dealing with encapsulated \PS{} and some in-line \PS{}.
+\item (on a Windows or Macintosh machine with appropriate
+ tools installed) pass the output through a \acro{PDF}writer in place
+ of a printer driver. This route is only appropriate for simple
+ documents: \acro{PDF} writers cannot create hyperlinks;
+\item process the document with ``vanilla'' \latex{} and generate \acro{PDF}
+ direct from the \acro{DVI} using \ProgName{dvipdfm}/\ProgName{dvipdfmx}; or
+\item process the document direct to \acro{PDF} with \PDFTeX{},
+ \Qref{\luatex{}}{Q-luatex}, \Qref{\xetex{}}{Q-xetex} or V\TeX{}.
+ \PDFTeX{}, \luatex{} and \xetex{} have the advantage of availability
+ for a wide range of platforms, but V\TeX{} is available only for
+ Windows (as a commercial product), or free of charge, but
+ unsupported, for Linux or \acro{OS/}2.
\end{itemize}
To translate all the \LaTeX{} cross-referencing into Acrobat
-links, you need a \LaTeX{} package to suitably redefine
+links, you need a \LaTeX{} package to redefine
the internal commands. There are two of these for \LaTeX{}, both
capable of conforming to the
\Qref{Hyper\TeX{} specification}{Q-hyper}:
@@ -93,7 +44,7 @@ Both \ProgName{dvips} and \YandY{}'s \acro{\ProgName{DVIPSONE}} can
translate the \acro{DVI} with these \csx{special} commands into
\PS{} acceptable to Distiller, and
\ProgName{dvipdfm} and \ProgName{dvipdfmx} have \csx{special} commands of
-its own.
+their own.
If you use \plaintex{}, the \Qref*{\Eplain{} macros}{Q-eplain} can
help you create \acro{PDF} documents with hyper-references.
@@ -121,8 +72,7 @@ cycle of ``Edit\arrowhyph{}Process\arrowhyph{}Preview'' become
rather clumsy~--- \ProgName{GSview} doesn't make the same
mistake.
\begin{ctanrefs}
-\item[\nothtml{\rmfamily}Acrobat Reader]browse
- \URL{ftp://ftp.adobe.com/pub/adobe/acrobatreader}
+\item[\nothtml{\rmfamily}Acrobat Reader]download from \URL{http://get.adobe.com/reader}
\item[dvipdfm]\CTANref{dvipdfm}
\item[dvipdfmx]\CTANref{dvipdfmx}
\item[ghostscript]Browse \CTANref{ghostscript}
@@ -131,6 +81,58 @@ mistake.
\item[hyper.sty]\CTANref{hyper}
\item[hyperref.sty]\CTANref{hyperref}
\end{ctanrefs}
+\LastEdit{2012-03-28}
+
+\Question[Q-hyper]{Making hypertext documents from \TeX{}}
+
+If you want on-line hypertext with a \AllTeX{} source, probably on the
+World Wide Web, there are four technologies to consider:
+\begin{itemize}
+\item start from \alltex{}, and use one of a number of techniques to
+ translate (more or less) directly to
+ \Qref{\acro{HTML}}{Q-LaTeX2HTML};
+% beware line break
+\item Start from \Qref*{\Package{texinfo}}{Q-texinfo} source,
+ and use the \ProgName{info} viewer, or convert the \Package{texinfo}
+ source to \acro{HTML} using \ProgName{texi2html};
+\item Start from \alltex{}; use \pdftex{}, \xetex{} or \luatex{} to
+ produce \acro{PDF}, using \Package{hyperref} to construct
+ hyperlinks.
+\item Start from (unconventional) \alltex{} which use the % ! line break
+ \Qref*{hyper\TeX{} conventions}{Q-hypertex}.
+\end{itemize}
+\begin{ctanrefs}
+\item[texinfo]\CTANref{texinfo}
+\end{ctanrefs}
+
+\Question[Q-hypertex]{The \emph{hyper\tex{}} project}
+
+The \emph{hyper\tex{}} project extended the functionality of all the
+\LaTeX{} cross-referencing commands (including the table of contents)
+to produce \csx{special} commands which are parsed by \acro{DVI} processors
+conforming to the Hyper\TeX{} guidelines;
+it provides general hypertext links, including those
+to external documents.
+
+The Hyper\TeX{} specification says that conformant viewers/translators
+must recognize the following set of \csx{special} commands:
+\begin{description}
+\item[href:] |html:<a href = "href_string">|
+\item[name:] |html:<a name = "name_string">|
+\item[end:] |html:</a>|
+\item[image:] |html:<img src = "href_string">|
+\item[base\_name:] |html:<base href = "href_string">|
+\end{description}
+
+The \emph{href}, \emph{name} and \emph{end} commands are used to do
+the basic hypertext operations of establishing links between sections
+of documents.
+
+Further details are available on \URL{http://arXiv.org/hypertex/}; there
+are two commonly-used implementations of the specification, a
+modified \ProgName{xdvi} and (recent releases of)
+\ProgName{dvips}. Output from the latter may be used in recent
+releases of \ProgName{ghostscript} or Acrobat Distiller.
\Question[Q-dvips-pdf]{Quality of \acro{PDF} from \PS{}}
\keywords{blurry fuzzy crippled}
@@ -177,6 +179,7 @@ Shell's \Package{testflow} package, which these FAQs recommend as a
\item[testflow]\CTANref{testflow}
\end{ctanrefs}
+
\Question[Q-fuzzy-type3]{The wrong type of fonts in \acro{PDF}}
\keywords{crippled blurry}
@@ -187,11 +190,12 @@ Most people use \ProgName{Adobe} \ProgName{Acrobat} \ProgName{Reader}
to view their \acro{PDF}: \ProgName{Reader} is distributed free of
charge, and is widely available, for all its faults. One of those
faults is its failure to deal with bitmap fonts (at least, in all
-versions earlier than the recently released version~6).
+versions earlier than version~6, all of which copies are pretty old,
+now~\dots{} but some are occasionally found).
So we don't want bitmap fonts in our \PS{}: with them, characters show
up in \ProgName{Reader}'s display as blurred blobs which are often not
-recognisable as the original letter, and are often not properly placed
+even recognisable as the original letter, and are often not properly placed
on the line. Nevertheless, even now, most \TeX{} systems have
\ProgName{dvips} configured to use
\Qref*{\extension{pk} files}{Q-pk} in its output. Even
@@ -257,6 +261,7 @@ configuration file either; however, it might have the configuration
file without the fonts. In either case, you need to
\Qref*{install the fonts}{Q-inst1cm}.
+
\Question[Q-fuzzy-gs]{Fuzzy fonts because \ProgName{Ghostscript} too old}
\keywords{crippled blurry}
@@ -573,3 +578,33 @@ are not amenable to this treatment.
\item[cm-super \nothtml{\rmfamily}fonts]\CTANref{cm-super}
\end{ctanrefs}
+% \Question[Q-hypertex]{The Hyper\tex{} project}
+%
+% The Hyper\TeX{} project extended the functionality of all the
+% \LaTeX{} cross-referencing commands (including the table of contents)
+% to produce \csx{special} commands which are parsed by \acro{DVI} processors
+% conforming to the Hyper\TeX{} guidelines;
+% it provides general hypertext links, including those
+% to external documents.
+%
+% The Hyper\TeX{} specification says that conformant viewers/translators
+% must recognize the following set of \csx{special} commands:
+% \begin{description}
+% \item[href:] |html:<a href = "href_string">|
+% \item[name:] |html:<a name = "name_string">|
+% \item[end:] |html:</a>|
+% \item[image:] |html:<img src = "href_string">|
+% \item[base\_name:] |html:<base href = "href_string">|
+% \end{description}
+%
+% The \emph{href}, \emph{name} and \emph{end} commands are used to do
+% the basic hypertext operations of establishing links between sections
+% of documents.
+%
+% Further details are available on \URL{http://arXiv.org/hypertex/}; there
+% are two commonly-used implementations of the specification, a
+% modified \ProgName{xdvi} and (recent releases of)
+% \ProgName{dvips}. Output from the latter may be used in recent
+% releases of \ProgName{ghostscript} or Acrobat Distiller.
+
+