From: Hans Hagen <j.hagen@xs4all.nl>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>,
"Marcel Fabian Krüger" <tex@2krueger.de>
Subject: Re: Changed behavior of ^^ in csname
Date: Thu, 11 Jun 2020 10:07:34 +0200 [thread overview]
Message-ID: <f055a776-ec10-e968-5dbc-4ff4e49a3315@xs4all.nl> (raw)
In-Reply-To: <20200611020640.ygusnhrznns6vgoi@yoga>
On 6/11/2020 4:06 AM, Marcel Fabian Krüger wrote:
> Hi,
>
> I noticed that in the latest LMTX version, ^^ (with ^ of catcode 7)
> is no longer interpreted inside csnames. Is this intentional?
>
> (Example:
>
> \starttext
> \catcode\circumflexasciicode=\superscriptcatcode% Ensure correct catcodes
>
> \show ^^41 % This still works and shows "> the letter A"
>
> \show^^41 % This used to be an error "Undefined control sequence \showA",
> % now show "> The letter A"
>
> \show\^^41 % Used to show "> \A=undefined", now shows "> \^=macro:->\enco_handle_accent {^}"
> % and "! Missing $ inserted"
> \stoptext
>
> )
Indeed that is intentional because in lmtx we disable them (partially).
You have to say:
\normalsupmarkmode\zerocount % we use 1 as default in lmtx
This is because in lmtx we have native prescript support, as in:
$ x^{rt}_{rb}^^{lt}__{lb} $
so, double _ ^ can have a different meaning there.
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 / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-06-11 8:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 2:06 Marcel Fabian Krüger
2020-06-11 8:07 ` Hans Hagen [this message]
2020-06-11 10:24 ` Marcel Fabian Krüger
2020-06-11 17:51 ` Hans Hagen
2020-06-11 20:47 ` Marcel Fabian Krüger
2020-06-12 6:04 ` Hans Hagen
2020-06-12 18:05 ` Marcel Fabian Krüger
[not found] ` <20200615121737.ytepj47mtvmcujy4@yoga>
[not found] ` <98372899-4f2e-447b-c9f1-29c80fcec13d@xs4all.nl>
[not found] ` <20200617101059.3zvwgt5qltufl64v@yoga>
2020-06-17 13:43 ` Yet another cornercase of ^^ handling in LuaMetaTeX Hans Hagen
2020-06-17 14:24 ` Marcel Fabian Krüger
2020-06-17 16:12 ` 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=f055a776-ec10-e968-5dbc-4ff4e49a3315@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=tex@2krueger.de \
/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).