From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Enumeration: chapter in counter, problem next to placefigure, and documentation issues
Date: Sun, 04 Sep 2016 22:22:20 +0200 [thread overview]
Message-ID: <57CC827C.4040302@gmail.com> (raw)
In-Reply-To: <753E37B0-7521-4DF5-8FAB-5DA799DCE9C6@posteo.net>
[-- Attachment #1.1: Type: text/plain, Size: 1417 bytes --]
> Florian Leupold <mailto:fleupold@posteo.net>
> 4. September 2016 um 19:37
> Issues with the documentation:
> - In “ConTeXt Commands”, it says on page 224 that \setupenumeration
> inherits from \setupcounter; but in “ConTEXt reference manual", it
> says on page 246 that \setupenumerations inherits from \setupdescriptions.
> - In “ConTEXt reference manual”, the key “location” for
> \defineenumeration should probably replaced by “alternative”. Right
> now, all examples on page 247 are unaffected by this setting and hence
> look the same.
ConTeXt contains two different interface files, a) a old one
(cont-en.xml) which was written for MkII and extended of the time with a
few new command introduced by MkIV (e.g. \definefontfeature) and b) a
new one (i-context.xml) which was rewritten with MkIV as its base.
Most of the existing documents use the old file which contains either
wrong keys (e.g. location vs. alternative) or document no longer
existing functions (compare counter related settings in both files).
The new file takes also into account internal changes for commands, e.g.
in MkII note descriptions are based on enumerations which are itself a
extension to the description commands. In MkIV notations (new name for
note descriptions), enumerations and descriptions all use a internal
mechanism called constructions with extra functions for each instance.
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 2416 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2016-09-04 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 17:37 Florian Leupold
2016-09-04 19:54 ` Otared Kavian
2016-09-05 9:06 ` Florian Leupold
2016-09-06 0:55 ` Aditya Mahajan
2016-09-06 7:18 ` Florian Leupold
2016-09-04 20:22 ` Wolfgang Schuster [this message]
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=57CC827C.4040302@gmail.com \
--to=schuster.wolfgang@gmail.com \
--cc=ntg-context@ntg.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).