Re: [NTG-context] Typographical Engineering in Context

On Sat, 03 Apr 2010 08:41:31 -0600, John Haltiwanger wrote:

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?

Let's distinguish typographical engineering from typographical programming. This will not be a book on the latter per se. Typographical engineering can be done by a non-programmer -- structured and automated processing using the high-level commands of Context. Typographic programming is an advanced topic, for which this book can serve as an introduction. So there may be some introduction to the ConTeXt internals, but nothing too indepth. Hopefully there will be successors to this first book which build on the foundation in different ways, or which or written fro a programmer-audience from the start.

...

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?

For typographic programming, of course the TeXBook is, if no indispensable, then extremely useful. OTOH, we need a luaTeXBook that describes the eTeX extensions, the omega-aleph extensions, and luatex's own extensions, not to mention using the lua scripting language itself.

(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 want to have one chapter on advanced techniques that includes an introduction to typographic programming in TeX -- including the primitive extensions -- and lua. But that will have to be expanded to a full book later on by real programmers like Wolfgang or Luigi.

...

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.

Can you explain what you mean by "appendix on workflows"? A community model for feedback on the book would be useful. I don't want it too open at the moment -- can slow down development and I want to get this DONE. But maybe a select audience of test-able volunteers will be the way to go... thnx for that suggestion! 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