diff options
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/faq-bits+pieces.tex')
-rw-r--r-- | Master/texmf-dist/doc/generic/FAQ-en/faq-bits+pieces.tex | 99 |
1 files changed, 54 insertions, 45 deletions
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 fed5b685db2..d1f9571413f 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,19 +1,22 @@ -% $Id: faq-bits+pieces.tex,v 1.2 2009/08/25 20:58:46 rf10 Exp rf10 $ +% $Id: faq-bits+pieces.tex,v 1.5 2009/12/20 00:09:40 rf10 Exp $ \section{Bits and pieces of \AllTeX{}} \Question[Q-dvi]{What is a \acro{DVI} file?} A \acro{DVI} file (that is, a file with the type or extension -\extension{dvi}) is \TeX{}'s main output file, using \TeX{} in its -broadest sense to include \LaTeX{}, etc. `\acro{DVI}' is supposed to +\extension{dvi}) is \TeX{}'s main output file, when we use +``original'' \TeX{} (later \TeX{} systems, such as \PDFTeX{}~--- see +\Qref[question]{\PDFTeX{}}{Q-whatpdftex} may use other formats). + +`\acro{DVI}' is supposed to be an acronym for \acro{D}e\acro{V}ice-\acro{I}ndependent, meaning -that the file can be printed on most -kinds of typographic output device. The \acro{DVI} file is designed to be -read by a driver (\Qref{DVI drivers}{Q-driver}) to produce -further output designed specifically for a particular printer (e.g., a -LaserJet) or to be used as input to a previewer for display on a -computer screen. \acro{DVI} files use \TeX{}'s internal coding; a \TeX{} +that the file can be processed for printing or viewing on most +kinds of typographic output device or display. The \acro{DVI} file +may be processed by a \Qref*{DVI driver}{Q-driver} to produce +further output designed specifically for a particular printer, or it +may be used by a previewer for display on a computer screen. +\acro{DVI} files use an internal coding designed for \TeX{}; a \TeX{} input file should produce the same \acro{DVI} file regardless of which implementation of \TeX{} is used to produce it. @@ -243,10 +246,10 @@ commands in the em\TeX{} drivers (e.g., \ProgName{dvihplj}, \ProgName{dviscr}, commands in \ProgName{dvitoln03} that permit the page to be set in landscape orientation. -Note that \csx{special} provides rather different facilities in \PDFTeX{} -operation: since there is no device driver around, in this context. -In \PDFTeX{}, \csx{special} is only needed to generated \acro{PDF} for -which there is no existing defined \PDFTeX{} operation. +Note that \csx{special} behaves rather differently in \PDFTeX{}, since +there is no device driver around. There \emph{is} a concept of +\acro{PDF} specials, but in most cases \csx{special} will provoke a +warning when used in \PDFTeX{}. \Question[Q-hyphen]{How does hyphenation work in \TeX{}?} @@ -263,7 +266,7 @@ hyphenation rules from time to time. \TeX{} uses a pretty good system for hyphenation (originally designed by Frank Liang~--- you may view his % ! line break -\href{http://tug.org/docs/liang/}{Ph.D.\ thesis online}), and while +\href{http://tug.org/docs/liang/}{Ph.D.\ thesis} online), and while it's capable of missing ``sensible'' hyphenation points, it seldom selects grossly wrong ones. The algorithm matches candidates for hyphenation against a set of @@ -378,6 +381,7 @@ package to thus permitting documented distribution of bundles containing code for \MF{} and \MP{} together with related \LaTeX{} code. \begin{ctanrefs} +\item[AUC-TeX]\CTANref{auctex} \item[clsguide.pdf]\CTANref{clsguide} \item[docmfp.sty]\CTANref{docmfp} \item[docstrip.tex]Part of the \LaTeX{} distribution @@ -535,11 +539,9 @@ according to the \LaTeX{} \acro{TS}1 encoding, and are not viewed as `stable' in the same way as are the \acro{EC} fonts are. The Cork encoding is also implemented by virtual fonts provided in the -\Qref*{\acro{PSNFSS} system}{Q-usepsfont}, -for Adobe Type~1 fonts, and also by the \Package{txfonts} and -\Package{pxfonts} font packages -% beware line wrap -(see \Qref[question]{``choice of scalable fonts''}{Q-psfchoice}). +\Qref*{\acro{PSNFSS} system}{Q-usepsfont}, for Adobe Type~1 fonts, and +also by most other such fonts that have been developed (or otherwise +made available) for use with \AllTeX{}. \begin{ctanrefs} \item[CM-super fonts]\CTANref{cm-super} \item[CM-LGC fonts]\CTANref{cm-lgc} @@ -553,31 +555,30 @@ for Adobe Type~1 fonts, and also by the \Package{txfonts} and way of organising all the \TeX{}-related files on a computer system. Most modern distributions conform to the \acro{TDS}, which -provides for both a `standard' and a (set of) `local' hierarchies of -directories containing \TeX{}-related files. The -\acro{TDS} reserves the name \texttt{texmf} as the name of the root directory -(folder) of the hierarchies. Files supplied as part of the -distribution are put into the standard hierarchy. The location of the -standard hierarchy is system dependent, but on a Unix system it might -be at -\path{/usr/local/texmf}, or -\path{/usr/local/share/texmf}, or +provides for both a `distribution' and a (set of) `local' directory +trees containing \TeX{}-related files. The \acro{TDS} reserves the +name \texttt{texmf} as the name of the root directory (folder) of the +hierarchies, and most distributions use that name for their `own' +trees. Files supplied as part of the distribution are put into the +distribution's tree. The location of the distribution's hierarchy is +system dependent, but on a Unix system it might be at +\path{/usr/share/texmf} or \path{/opt/texmf}, or -a similar location, but in each case the \TeX{} files will be under the -\path{/texmf} subdirectory. - -There may be more than on `local' hierarchy in which additional files -can be stored. In the extreme an installation can have a local -hierarchy and each user can also have an individual local hierarchy. The -location of any local hierarchy is not only system dependent but also user -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 -\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}. +a similar location, but in each case the \TeX{} files will be in the +tree starting at the \path{/texmf} subdirectory. + +There may be more than one `local' hierarchy in which additional files +can be stored. In the extreme an installation can have a local +hierarchy and each user can also have an individual local hierarchy. +The location of any local hierarchy is not only system dependent but +also user dependent. Again, though, all files should be put under a +local \path{/texmf} directory. + +The \acro{TDS} itself is published as the output of a \acro{TUG} % ! line break +\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}. \begin{ctanrefs} \item[\nothtml{\rmfamily}\acro{TDS} specification]\CTANref{tds} \end{ctanrefs} @@ -626,8 +627,16 @@ Adobe has specified a number of formats for files to represent fonts in \PS{} files; this question doesn't attempt to be encyclopaedic, so we only discuss the two formats most commonly encountered in the \AllTeX{} context, types~1 and 3. In particular, we don't discuss the -OpenType format, whose has many advantages are somewhat ahead of the -\TeX{} world's mainstream (at time of writing). +OpenType format, whose has many advantages have only in the last year +or two been readily accessible to most \AllTeX{} users (by means of +\begin{wideversion} + the widely-used \Qref{\xetex{}}{Q-xetex} and the more experimental + \Qref{\LuaTeX{}}{Q-luatex}). +\end{wideversion} +\begin{narrowversion} + the widely-used \xetex{}~--- see \Qref[question]{}{Q-xetex}~--- and + the more experimental \LuaTeX{}~--- see \Qref[question]{}{Q-luatex}). +\end{narrowversion} Adobe Type~1 format specifies a means to represent outlines of the glyphs in a font. The `language' used is closely restricted, to ensure that |