869
edits
Changes
Jump to navigation
Jump to search
m
Revision and translations of “ConTeXt, an excursion” (view source)
Revision as of 05:36, 9 May 2007
, 05:36, 9 May 2007→How to create a document: Removed an old comment
At EuroTeX 2005 http://www.gutenberg.eu.org/eurotex2005/ several persons approached Hans Hagen to translate the manual ''ConTeXt, an excursion''. This page lists the contents of the manual version 990527.
The purpose it of this page is to comment which sections need to be updated, which ones need to be deleted, etc., before to begin beginning the translation.
== How to create a document ==
* In the source, <code>\type{filename}</code> should be changed to <code>\filename{filename}</code>.
* The manual says that ConTeXt excepts plain ASCII input. This is not true (anymore) since you can input other encodings also. AFAIU, ASCII is just the first 128 characters, right?
* Page 4, change ''This can be done yet some other context command...'' to ''....done by '''another''' context ....''
* Change ''One can use texexec...'' to '' '''You''' can use ....'' (The previous sentence refers to the reader as you...)
* ''This perl script'' to ... ''this '''ruby''' script''
== How to process a file / Run CONTEXT ==
* Remove ''context filename''. AFAIK, the script '''context''' is not distributed by any tex distribution.
* At tex prompt ? S to scroll future error messages,
R to run without stopping, Q to run quietly, 1 or ... or 9 to ignore the next 1 to 9 tokens of input.
* Futher more -> Furthermore
* Explain that the log file is called myfile.log
* The document does not explain how to get the dvi. Something must be said about the backend drivers for dvi also.
== Special characters ==
* Table 3.2 is a bit confusing. These characters can be used in text mode also. The output of textmode looks different from the output of math mode
* Table 3.1 should also mention _ (underscore) and ^ (cadet).
* For all practical purposes in ConTeXt | (pipe) is also a special character.
== Defining a document ==
* In the source change <code>\type{command}</code> to <code>\tex{command}</code>
* $\cdots$ -> \unknown
== Headers ==
* \setupsectionblock[...][..,..=..,..]
== Itemize ==
* \startitemize[..,...,..][..,..=..,..] ... \stopitemize
* \setupitemize[.1.][..,.2.,..][..,..=..,..]
== Formulae ==
* \placeformula[ref,..]{.1.}$$.2.$$
* \footnote[ref]{...}
* \note[ref]
* \setupfootnotes[..,..=..,..] : It would be interesting to talk about columnsets (even if not detailing them) for users looking for powerful column features.
== Definitions ==
* \definedescription[...][..,..=..,..]
== Using modules ==
* \usemodule[..,...,..]
* \loadmapfile[gbk] \usemodule[chinese]
== Appendix A User specifications ==
* \setupoutput[pdftex]
