[Disclaimer: NOT a joke!]

Dear gang, cabal, and knights of the context table,

FYI: I am presently working on a book:

Typographical Ontology and Engineering:
Structured and Automated Authoring in Context

It is a book on ConTeXt, but NOT a ConTeXtBook, ConTeXt Companion, or other clone. Rather, it aims to introduce Context as a general tool for typographical and typesetting engineering. Some of the philosophy of book design and layout will be discussed, and it will contain a strong reference to commands etc.

NB: MKIV ONLY!

The basic outline is


I. Ontology and Theory
II. Typographical Engineering in Context [including special topics, advanced techniques of luatex, opentype etc] III. A Typographical Engineer's Reference [organization of options and commands, glossary]
IV. Appendix: Authoring in Notepad++ [or some other tool]
V. Indices


So no knowledge or familiarity with TeX is assumed at all. We will cover some advanced topics as well, including introductions to luatex scripting etc

I was not planning to announce this for some time yet, but given the buzz around the topic on ConTeXt documentation Hans thought it would be a good moment to introduce this project and to get your feedback.

So please use this thread to make suggestions:

What would you all like to see covered in the planned book project:

Typographical Ontology and Engineering: Structured and Automated Authoring in Context

I look forward to your feedback and suggestions!

Best wishes
Idris

--
Professor Idris Samawi Hamid, Editor-in-Chief
International Journal of Shi`i Studies
Department of Philosophy
Colorado State University
Fort Collins, CO 80523

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to