diff options
author | Karl Berry <karl@freefriends.org> | 2010-01-30 00:23:18 +0000 |
---|---|---|
committer | Karl Berry <karl@freefriends.org> | 2010-01-30 00:23:18 +0000 |
commit | a6eeaf899a64dcd37c685f4d6225be65e5577f79 (patch) | |
tree | 10d2e849f7c5f3e58cc50f528b55b1c6f63af375 /Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex | |
parent | 5cf448717d5bd535646efd1290abb0237b239f41 (diff) |
FAQ_en 3.19c (29jan10)
git-svn-id: svn://tug.org/texlive/trunk@16865 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex')
-rw-r--r-- | Master/texmf-dist/doc/generic/FAQ-en/faq-t-g-wr.tex | 56 |
1 files changed, 47 insertions, 9 deletions
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 935869ad543..b89d2a25b94 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.2 2009/06/30 18:44:15 rf10 Exp $ +% $Id: faq-t-g-wr.tex,v 1.4 2010/01/21 21:01:42 rf10 Exp rf10 $ \section{Things are Going Wrong\dots{}} @@ -84,7 +84,7 @@ variants) or the corresponding \LaTeX{} \Package{m-pictex} package provide an ingenious solution to the problem based on hacking the code of \csx{newdimen} itself. -Alternatively, Andreas Schell's \Package{pictexwd} and related +Alternatively, Andreas Schrell's \Package{pictexwd} and related packages replace \PiCTeX{} with a version that uses 33 fewer \csx{dimen} registers; so use \Package{pictexwd} in place of \Package{pictex} (either as a \LaTeX{} package, or as a file to read @@ -357,11 +357,49 @@ all know and love (or hate)% There's not a lot one can do with these fonts; they are (as their name implies) almost (but not quite) the same as the \FontName{cm} series; if you're faced with a document that requests -them, all you can reasonably do is to edit the document. The -appearance of \acro{DVI} files that request them is sufficiently rare that -no-one has undertaken the mammoth task of creating a translation of -them by means of virtual fonts; however, most drivers let you have a -configuration file in which you can specify font substitutions. If you -specify that every \FontName{am} font should be replaced by its corresponding -\FontName{cm} font, the output should be almost correct. +them, the only reasonable approach is to edit the document to replace +\FontName{am*} font names with \FontName{cm*}. + +The appearance of \acro{DVI} files that request them is sufficiently +rare that no-one has undertaken the mammoth task of creating a +translation of them by means of virtual fonts. + +You therefore have to fool the system into using \FontName{cm*} fonts +where the original author specified \FontName{am*}. + +One option is the font substitutions that many +\acro{DVI} drivers provide via their configuration file~--- +specify that every \FontName{am} font should be replaced by its +corresponding \FontName{cm} font. + +Alternatively, one may try \acro{DVI} editing~--- packages +\Package{dtl} (\acro{DVI} Text Language) and \Package{dviasm} +(\acro{DVI} assembler) can both provide round trips from \acro{DVI} to +text and back to \acro{DVI}. One therefore edits font names +(throughout the text representation of the file) in the middle of that +round trip. + +The \acro{DTL} text is pretty straightforward, for this purpose: +fontnames are in single quotes at the end of lines, so: +\begin{quote} + \texttt{dv2dt -o} \meta{doc.txt} \meta{doc.dvi}\\ + (\emph{edit the \extension{txt} file})\\ + \texttt{dt2dv -o} \meta{edited.dvi} \meta{edited.txt} +\end{quote} +(you have to compile the \acro{C} programs for this). +\ProgName{Dviasm} is a \ProgName{Python} script; its output has font +names in a section near the start of the document, and then dotted +about through the body, so: +\begin{quote} + \texttt{python dviasm.py -o} \meta{doc.txt} \meta{doc.dvi}\\ + (\emph{edit the \extension{txt} file})\\ + \texttt{python dviasm.py -o} \meta{edited.dvi} \meta{edited.txt} +\end{quote} +Both routes seem acceptable ways forward; it is a matter of taste +which any particular user may choose (it's not likely that it will be +necessary very often...). +\begin{ctanrefs} +\item[dviasm.py]\CTANref{dviasm} +\item[dtl]\CTANref{dtl} +\end{ctanrefs}
\ No newline at end of file |