2010/4/3 Idris Samawi Hamid ادريس سماوي حامد
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.
As the unique nature of typographical programming has lead it to under-documentation, I want to say that maintaining this as a central focus is a brilliant idea. Will Section II involve describing some detail important aspects of ConTeXt's internals?
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
As this is precisely my situation, perhaps I can offer you the benefit of a test-able target audience? Today I am already looking into the best route to learning TeX/mkiv in a holistic (ie not just looking for the 'recipe' I need to meet a given deadline). I have just entered full-time thesis mode, so the question begins Should I just sit down and read the TeXBook? (something that will be done regardless, it's just a question as what is most worthwhile to Getting Something Done Right Now) or would it be that the LuaTeX manual is more directly applicable? Or, perhaps, a chapter from your book? ;)
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!
I think the more you source it with the community, the stronger it will become. That is, our ignorance will most likely help you refine it in ways you wouldn't have expected to need to. But in other ways as well. For example, the appendix on workflows can gain a lot from community input I'd think.