ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	SirColeman via ntg-context <ntg-context@ntg.nl>
Cc: SirColeman <realsircoleman@tutanota.com>
Subject: [NTG-context] Re: An announcement of my new book.
Date: Tue, 13 Feb 2024 20:22:00 +0100	[thread overview]
Message-ID: <a6a3392e-9370-00d6-a4e6-d607d080212c@gmail.com> (raw)
In-Reply-To: <NqRHlpC--3-9@tutanota.com>


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

SirColeman via ntg-context schrieb am 12.02.2024 um 08:49:
> 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).

This is wrong, the counter commands are official and the number variants 
are kept for backwards compatibility with old styles.

Wolfgang


[-- Attachment #1.2: Type: text/html, Size: 1561 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-13 19:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-12  7:49 [NTG-context] " SirColeman via ntg-context
2024-02-13 19:22 ` Wolfgang Schuster [this message]
     [not found] ` <a6a3392e-9370-00d6-a4e6-d607d080212c@gmail.com-NqYvC-q----9>
2024-02-13 19:44   ` [NTG-context] " 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=a6a3392e-9370-00d6-a4e6-d607d080212c@gmail.com \
    --to=wolfgang.schuster.lists@gmail.com \
    --cc=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).