From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Hans Hagen <j.hagen@freedom.nl>
Subject: [NTG-context] Re: Very strange error:
Date: Tue, 15 Aug 2023 00:25:17 +0200 [thread overview]
Message-ID: <3c79e5c7-2153-fa7b-1978-f9732fb119a8@freedom.nl> (raw)
In-Reply-To: <20230814232423.774f0e811ad3275fd3b33801@posteo.net>
On 8/14/2023 11:24 PM, Xavier B. wrote:
> Thanks, Rik, for the comment. You're right.
> Note that I've never been aware of such requirement because always in MKIV I use \head without \par.
>
> @all, please comment it out this behaviour in somewhere. The weak point of context is documentation: wiki is too bit not updated and reference manual are outdated. As a simple user, it could cause nightmares, overall in transition to one major version to another.
the only things that really changed are
- input encodings, still supported but we assume utf8
- font encodings, font features etc that make for different specifications
- some fuzzy argument handling that made sense 25 years ago but not today
- some low level fatures that were never to be used at the user level
- improvements to mechanism that are now possible
- more was added than removed (and believe me: i'd like to remove some)
- if something fails also keep in mind that maybe it was never supossed
to work but tex is just rather tolerant
take for instance math: we adapt to possibilities, unicode developments
etc. but overall interfaces are kept (we eventually dropped $$ mkiv
because it is hard to get spacing right otherwise, een with some nasty
tricks)
\head is one of these "best use arguments" and les sknown is that we
also dropped par delimited \section and such (the head one currently can
be enabled with \autoparagraphmode4)
the main drive is 'better rendering' and 'less complicated coding'
you use for for instance \bigskip which is never going to guarantee good
spacing as it doesn't cooperate with \blank and friends (it is sort of
dangerous to mix what oen sees outside context with context commands
like like loading that lua module, which actually is in none of the
manuals)
if one wants to get an idea of coding context documents the 'source sof
manuals' can show some
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-08-14 22:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 15:41 [NTG-context] " Xavier B.
2023-08-14 15:49 ` [NTG-context] " Wolfgang Schuster
2023-08-14 21:26 ` Xavier B.
2023-08-15 14:45 ` Aditya Mahajan
2023-08-14 16:42 ` Rik Kabel
2023-08-14 16:49 ` Rik Kabel
2023-08-14 17:07 ` Wolfgang Schuster
2023-08-14 21:50 ` Xavier B.
2023-08-14 22:03 ` Xavier B.
2023-08-15 3:55 ` Wolfgang Schuster
2023-08-14 21:24 ` Xavier B.
2023-08-14 22:25 ` Hans Hagen via ntg-context [this message]
2023-08-15 18:58 ` Wolfgang Schuster
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=3c79e5c7-2153-fa7b-1978-f9732fb119a8@freedom.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@freedom.nl \
/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).