diff options
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex')
-rw-r--r-- | Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex | 66 |
1 files changed, 38 insertions, 28 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex b/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex index 75c2064b556..9ca0d1863e2 100644 --- a/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex +++ b/Master/texmf-dist/doc/generic/FAQ-en/faq-adj-types.tex @@ -1,4 +1,4 @@ -% $Id: faq-adj-types.tex,v 1.28 2011/01/04 00:27:59 rf10 Exp rf10 $ +% $Id: faq-adj-types.tex,v 1.31 2011/04/13 09:45:46 rf10 Exp $ \section{Adjusting the typesetting} @@ -1403,7 +1403,7 @@ So, the resolution of the problem, when you are using \latex{}, is to add \end{verbatim} \end{quote} Where \pkgoption{processor-option} tells the package what will produce -your (\PS{} or \acro{PDF} driver~--- \Package{geometry} knows about +your (\PS{} or \acro{PDF} output~--- \Package{geometry} knows about \pkgoption{dvips} and \pkgoption{dvipdfm} (\pkgoption{dvipdfm} also serves for the extension \ProgName{dvipdfmx} and \ProgName{xdvipdfmx}). @@ -1439,6 +1439,7 @@ output that specifies the necessary paper size. \item[memoir.cls]\CTANref{memoir} \item[typearea.sty]Distributed as part of \CTANref{koma-script}[typearea] \end{ctanrefs} +\LastEdit{2011-03-07} \Question[Q-changemargin]{Changing the margins in \LaTeX{}} @@ -2517,19 +2518,19 @@ These very simple examples may be decorated in a huge variety of ways, and of course there are other languages in the package's vocabulary than just \ProgName{C}\dots{} -Most people, advising others on \AllTeX{} lists, seem to regard -\Package{listings} as the be-all and end-all on this topic. But there -\emph{are} alternatives, which may be worth considering, in some -situations. +For a long time, advice on \AllTeX{} lists seemed to regard +\Package{listings} as the be-all and end-all on this topic. In the +last few years, viable alternatives have appeared \ProgName{Highlight} is attractive if you need more than one output format for your program: as well as \AllTeX{} output, \ProgName{highlight} will produce (\acro{X})\acro{HTML}, \acro{RTF} -and \acro{XSL}-\acro{FO} representations of your program listing. -Documentation is available on the % ! line break -\href{http://www.andre-simon.de/}{\ProgName{highlight} project site}. +and \acro{XSL}-\acro{FO} representations of your program listing. The +manual leads you through the details of defining a parameter file for +a ``new'' language, as well as the presentation details of a language. -The \Package{minted} package is a relatively recent addition. It +The \Package{minted} package is another alternative that offers +the means of creating new language definitions. It requires that documents be pre-processed using an external (\ProgName{python}) script, \href{http://pygments.org/}{\ProgName{Pygments}}. @@ -2539,22 +2540,25 @@ more commonly-used languages, and there is advice on ``rolling your own'' on the % ! line break. <a href='http://pygments.org/docs/lexerdevelopment/'>\ProgName{Pygments} site</a> -The \ProgName{lgrind} system is another well-established pre-compiler, -with all the facilities one might need and a wide repertoire of -languages; it is derived from the very long-established -\ProgName{tgrind}, whose output is based on \plaintex{} - -The \ProgName{tiny_c2l} system is more recent: users are encouraged to -generate their own driver files for languages it doesn't already deal -with. - -The \ProgName{C++2LaTeX} system comes with strong recommendations for -use with \acro{C} and \acro{C}++. - -An extremely simple system is \ProgName{c2latex}, for which you write -\LaTeX{} source in your \acro{C} program comments. The program then -converts your program into a \LaTeX{} document for processing. The -program (implicitly) claims to be ``self-documenting''. +Longer-established, and variously less ``powerful'' systems include: +\begin{itemize} +\item The \ProgName{lgrind} system is a well-established + pre-compiler, with all the facilities one might need and a wide + repertoire of languages; it is derived from the even + longer-established \ProgName{tgrind}, whose output is based on + \plaintex{}. +\item The \ProgName{tiny_c2l} system is slightly more recent: users + are again encouraged to generate their own driver files for + languages it doesn't already deal with, but its ``tiny'' name + correctly hints that it's not a particularly elaborate system. +\item The \ProgName{C++2LaTeX} system comes with strong + recommendations for use with \acro{C} and \acro{C}++. +\item An extremely simple system is \ProgName{c2latex}, for which you + write \LaTeX{} source in your \acro{C} program comments. The + program then converts your program into a \LaTeX{} document for + processing. The program (implicitly) claims to be + ``self-documenting''. +\end{itemize} \begin{ctanrefs} \item[c2latex]\CTANref{c2latex} \item[C++2LaTeX]\CTANref{c++2latex} @@ -2565,6 +2569,7 @@ program (implicitly) claims to be ``self-documenting''. \item[tgrind]\CTANref{tgrind} \item[tiny\_c2l]\CTANref{tiny_c2l} \end{ctanrefs} +\LastEdit{2011-03-09} \Question[Q-algorithms]{Typesetting pseudocode in \LaTeX{}} @@ -2785,6 +2790,7 @@ There are three packages that help solve this problem: originally developed for using the \LaTeX{} graphics package in \plaintex{}). A small patch is also necessary: the required sequence is therefore: +\begin{quote} \begin{narrowversion} \begin{verbatim} \input miniltx @@ -2800,6 +2806,7 @@ There are three packages that help solve this problem: \input url.sty \end{verbatim} \end{wideversion} +\end{quote} \item The \Package{hyperref} package, which uses the typesetting code of \Package{url}, in a context where the typeset text forms the anchor of a link. @@ -2923,10 +2930,12 @@ space: otherwise it is sometimes going to be impossible to see the breaks between paragraphs. The simple-minded approach to zero paragraph indentation is thus: +\begin{quote} \begin{verbatim} - \setlength{\parindent}{0pt} - \setlength{\parskip}{\baselineskip} +\setlength{\parindent}{0pt} +\setlength{\parskip}{\baselineskip} \end{verbatim} +\end{quote} and in the very simplest text, it's a fine solution. However, the non-zero \csx{parskip} interferes with lists and the like, @@ -2942,6 +2951,7 @@ indent and non-zero paragraph skip. \item[\nothtml{\rmfamily}\acro{NTG} classes]\CTANref{ntgclass} \item[parskip.sty]\CTANref{parskip} \end{ctanrefs} +\LastEdit{2011-04-01} % yes, really \Question[Q-dropping]{Big letters at the start of a paragraph} |