From: Rik Kabel <context@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: (MkVI) Regression in named parameters, TL2013 to current
Date: Fri, 28 Feb 2014 18:45:17 -0500 [thread overview]
Message-ID: <53111F8D.7090705@rik.users.panix.com> (raw)
% macros=mkvi
\setupwhitespace[small]
\def\ä<^>?z{Ä<^>?}
\def\Named[#PARAMETERNAME]{¦#PARAMETERNAME¦}
\def\Numbered[#1]{¦#1¦}
\starttext
\subject{Regression between TL2013 and current beta}
There does appear to have been some change or regression in the
definition of allowed characters in parameter names between the
versions of TL2013 ({\tt ConTeXt ver: 2013.05.28 00:36 MKIV current
fmt: 2013.12.11}) and the current standalone beta ({\tt ConTeXt ver:
2014.02.14 17:07 MKIV beta fmt:2014.2.14})
The definition
\type{\def\Named[#PARAMETERNAME]{¦#PARAMETERNAME¦}} (using BROKEN
BAR, U00A6) is processed without error and gives an acceptable
result under TL2013. Under the current beta it fails.
When warnings are skipped in the current beta, the generated PDF
shows that the trailing BROKEN BAR appears to be treated as a part
of the parameter name: \Named[value].
With numbered parameters (\type{\def\Numbered[#1]{¦#1¦}}), all is
well in both versions: \Numbered[value].
This issue makes it difficult to convert macros that use delimiters
(for example, \type{\def\ABC#1×#2¦{#1\ #2}}) to Mark VI syntax, and
difficult to create such macros under Mark VI.
\subject{What is allowed \ä<^>?z}
What characters are acceptable in Mark VI parameter names?
What characters are acceptable in Mark IV and Mark VI macro names?
The wiki states: \quotation{Mark VI is identical to Mark IV in
every respect, except that when you define a new macro you can give
parameters names instead of numbers.} Other than that, there is no
guidance.
Experimentation shows that many more characters are allowed in
\CONTEXT{} identifiers than are generally allowed with other \TeX{}
engines. The definition providing the last part of the subject of
this section, \type{\def\ä<^>?z{Ä<^>?}}, presents no problems.
(That definition fails in Lua\TeX, \pdfTeX, and \XeTeX. I have never
used Mark II, and do not have Ruby installed to enable a test.)
-\hbox{}-~\crlf
Rik Kabel
\stoptext
___________________________________________________________________________________
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
___________________________________________________________________________________
next reply other threads:[~2014-02-28 23:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 23:45 Rik Kabel [this message]
2014-03-01 1:32 ` Hans Hagen
2014-03-01 3:39 ` Rik Kabel
2014-03-01 9:59 ` Wolfgang Schuster
2014-03-01 14:40 ` Rik Kabel
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=53111F8D.7090705@rik.users.panix.com \
--to=context@rik.users.panix.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).