From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: catcode change in macros
Date: Sat, 15 Nov 2008 21:41:36 +0100 [thread overview]
Message-ID: <491F3400.4020302@wxs.nl> (raw)
In-Reply-To: <alpine.LNX.2.00.0811151427440.22240@nqv-yncgbc>
Aditya Mahajan wrote:
> On Sat, 15 Nov 2008, Wolfgang Schuster wrote:
>
>> Am 14.11.2008 um 19:37 schrieb Aditya Mahajan:
>>
>>> On Fri, 14 Nov 2008, Aditya Mahajan wrote:
>>>
>>>> On Fri, 14 Nov 2008, Wolfgang Schuster wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I make in a module the comment sign a simple letter to pass
>>>>> number formats to a lua function and want to know if should
>>>>> use another (better) way to change the catodes.
>>>> I think it will be cleaner to use catcode tables. See syst-cat.mkiv.
>>> and syst-cat.tex
>> I keep now my low level solution but with fewer lines.
>
> Even though you are still using the mailling list, I will reply :-)
>
>> To help other users with the same question I present
>> here my solution:
>>
>> \def\????ax{@@@@ax}
>>
>> \def\setupaxis
>> {\catcode`\%\@@letter
>> \dodoubleargument\dosetupaxis}
>>
>> \def\dosetupaxis[#1][#2]%
>> {\def\docommand##1{\getparameters[\????ax##1][#2]}%
>> \catcode`\%\@@comment
>> \processcommalist[#1]\docommand}
>>
>> \setupaxis
>> [\c!x,\c!y]
>> [\c!format=%d]
>
> Here you are assuming that whenever \setupaxis will be used, the catcode
> of % is comment. This may not be the case. You can of course, store the
> inital catcode of % and then restore it later, as done by many LaTeX
> packages.
>
> The main advantage of catcode tables is that you can do
> \pushcatcodetable, and \popcatcodetable, and not do the book keeping
> yourself. Here is a solution using catcodetables:
>
> \unprotect
>
> % A mixture of \startcatcodetable and \extendcatcodetable
> \long\def\startchangecatcodetable#1#2#3\stopchangecatcodetable
> {\bgroup
> \catcodetable\scratchcatcodetable
> \catcodetable#1\relax
> #3%
> \savecatcodetable#2\relax
> \egroup}
>
>
> \newcatcodetable \LUAstringcatcodes
>
> \startchangecatcodetable \ctxcatcodes \LUAstringcatcodes
> \catcode`\%\@@letter
> \stopchangecatcodetable
>
> \protect
>
> \starttext
>
> \pushcatcodetable
> \catcodetable\LUAstringcatcodes
> % Does this print
> Hello world
> \popcatcodetable
>
> \stoptext
>
> So, you code now becomes
>
> \unprotect
> \def\????ax{@@@@ax}
>
> \def\setupaxis
> {\pushcatcodetable
> \catcodetable\LUAstringcatcodes
> \dodoubleargument\dosetupaxis}
>
> \def\dosetupaxis[#1][#2]%
> {\def\docommand##1{\getparameters[\????ax##1][#2]}%
> \popcatcodetable
> \processcommalist[#1]\docommand}
>
> \setupaxis
> [\c!x,\c!y]
> [\c!format=%d]
>
> Hans, do you think that something like \startchangecatcodetable should be
> added to the core. An old definition of \extendcatcodetable almost does
> that, but does not provide a name to the resulatant catcodetable.
i wonder if change is the right name, isn't it more cloning?
anyhow, keep in mind that in mkiv we print back to tex every now and
then and then we use one of the predefined catcode tables.
Another option is:
[\c!format=\letterpercent d]
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-11-15 20:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 18:22 Wolfgang Schuster
2008-11-14 18:36 ` Aditya Mahajan
2008-11-14 18:37 ` Aditya Mahajan
2008-11-14 18:51 ` Wolfgang Schuster
2008-11-15 13:13 ` Wolfgang Schuster
2008-11-15 20:06 ` Aditya Mahajan
2008-11-15 20:41 ` Hans Hagen [this message]
2008-11-15 20:59 ` 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=491F3400.4020302@wxs.nl \
--to=pragma@wxs.nl \
--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).