ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: SirColeman via ntg-context <ntg-context@ntg.nl>
To: Ntg Context <ntg-context@ntg.nl>
Cc: SirColeman <realsircoleman@tutanota.com>
Subject: [NTG-context] An announcement of my new book.
Date: Mon, 12 Feb 2024 08:49:46 +0100 (CET)	[thread overview]
Message-ID: <NqRHlpC--3-9@tutanota.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 3664 bytes --]

Greetings all. I have a passion for typesetting. I found that currently the best typesetting systems are those that are based on TeX. Of them, there are LaTeX, and ConTeXt.
LaTeX is very well documented and popular; ConTeXt, on the other hand, is apparently very powerful and capable, but is not as well documented.

There are things that are spectacularly well documented, others that only show hints, and leave it up to the user to figure things out on their own, and others still that won't even compile on a more recent version of ConTeXt (apparently the proper way to access a counter's value in ConTeXt is to use \getnumber or \convertednumber, and not \getcounter. That's just an example).

I thus thought, as an exercise in typesetting, in writing, and also to help the ConTeXt documentation, to write a new book, a large book, that teaches the details of how ConTeXt on a lower level works, allowing one to understand how to utilize low level typesetting features for anything more sophisticated than a simple book or article. By lower level, I mean how things like heads, items, references, alignment, tables, etc., work. Also, I would like a book that teaches things like how to program it using lua, how to understand and utilize the underlying engine itself (the low level LuaMetaTeX), how to even use DocBook with ConTeXt, etc.

(I do realize that there already are manuals for lua in ConTeXt and on LuaMetaTeX, etc., and manuals on various different parts of ConTeXt, and I'll certainly be learning from them whenever their particular topic comes, but I reserve the opportunity to rewrite parts of these manuals for this book, as is necessary for the book's purpose, perhaps referencing these manuals for further details.)

In particular, I want to go a step beyond the book "A not so short introduction to ConTeXt Mark IV", and teach the particularly advanced features, where there is sparse information. Particularly, it's meant to serve as one complete reference, instead of having to hunt for different manuals, which explain things differently, and with the consequence that it's hard to find a particular piece of information because its scattered around so many different places.

This book should serve as the one and only final documentation that you would need. It would contain everything in a highly cohesive format, in one place, and make particular pieces of information particularly easy to find. I realize that this is a very ambitious undertaking, but I find that a unified source of information is better than information with varying levels of quality scattered across more places than one can hold in his head.

I just have one question: What is all the necessary material to understand and utilize the low level TeX programming language itself? That is, what do I need to read to learn to be able to read the ConTeXt source code itself (which is written in TeX---and lua, but I can help myself in that regard)? Is the "Low Level TeX" set of manuals all that I'll need, or will I need other sources of information too? And also, is it worth learning Plain TeX, and reading The TeXbook, or is not necessary?

And, I'm grateful to have an alternative to LaTeX. It's certainly promising, but I would like to help make it appealing, by making it easy to learn and master it, and provide a single source of information. I'm grateful for having ConTeXt.

P.S. If I have bugs to file, should I file them on this mailing list, or on the dev-context@ntg.nl mailing list?

And, to all beginner ConTeXt users: What would you like to see covered in this book?

Thanks.

-- 
 Sent with Tuta; enjoy secure & ad-free emails: 
 https://tuta.com

[-- Attachment #1.2: Type: text/html, Size: 4782 bytes --]

[-- Attachment #2: Type: text/plain, Size: 511 bytes --]

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

maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage  : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive  : https://github.com/contextgarden/context
wiki     : https://wiki.contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2024-02-12  7:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12  7:49 SirColeman via ntg-context [this message]
2024-02-13 19:22 ` [NTG-context] " Wolfgang Schuster
     [not found] ` <a6a3392e-9370-00d6-a4e6-d607d080212c@gmail.com-NqYvC-q----9>
2024-02-13 19:44   ` SirColeman via ntg-context
2024-02-13 19:55     ` Wolfgang Schuster
2024-02-13 20:00       ` Sir Coleman via ntg-context
2024-02-13 21:44         ` Peter Hopcroft via ntg-context
2024-02-13 22:22           ` Sir Coleman via ntg-context
2024-02-14  5:03             ` Shiv Shankar Dayal
2024-02-14 18:07             ` Jim
2024-02-14 18:45               ` Sir Coleman via ntg-context
2024-02-15  7:23                 ` Jan Ulrich Hasecke via ntg-context
2024-02-15  8:26                   ` Mikael Sundqvist
2024-02-15 10:32                     ` Tommaso Gordini
2024-02-15 11:04                     ` Aditya Mahajan
2024-02-15 19:25                       ` Tommaso Gordini
2024-02-15 19:36                         ` Hans Hagen
2024-02-15 20:07                         ` Henning Hraban Ramm
2024-02-14 19:37 ` Joaquín Ataz López
2024-02-14 20:10   ` Hans Hagen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=NqRHlpC--3-9@tutanota.com \
    --to=ntg-context@ntg.nl \
    --cc=realsircoleman@tutanota.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).