ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: defineremapper as default (in style file)
Date: Mon, 25 May 2009 12:23:51 +0200	[thread overview]
Message-ID: <fe8d59da0905250323m1fea6e7ch102702d31982a914@mail.gmail.com> (raw)
In-Reply-To: <4A1A7022.8020909@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1678 bytes --]

On Mon, May 25, 2009 at 12:17 PM, Hans Hagen <pragma@wxs.nl> wrote:

> luigi scarso wrote:
>
>> On Fri, May 22, 2009 at 8:11 PM, Hans Hagen <pragma@wxs.nl> wrote:
>>
>>  Peter Münster wrote:
>>>
>>>  Hello,
>>>>
>>>> I would like to activate a remapper in a style or module file. How could
>>>> this be done?
>>>>
>>>> I tried this without success:
>>>>
>>>> \defineremapper[filterItem]
>>>> \remapcharacter[filterItem][`•]{\item}
>>>> \appendtoks \startfilterItem \to \everystarttext
>>>> \prependtoks \stopfilterItem  \to \everystoptext
>>>>
>>>>
>>  kep in mind that the remapper is just a hack and will not be extended etc
>>> etc; i'm not going to handle interferences with other mechanisms
>>>
>>>
>>  Hans
>>>
>>>
>>
>> I think the point is this :
>> in some situations one find useful to convert things like • in macros like
>> \item .
>> Of course, it can be done with  preprocessing , or with some ad-hoc macros
>> in lua code , etc
>> So, apart \remapcharacter, are there  any other safe ways to "remap
>> character" ?
>>
>
> one solution mentioned was making that character active and then do an
> unexpanded def which makes it roundtrip safe;  of course we should leave
> characters like : untouched
>

there was an article many years ago something like "Active characters -- No
thank you"


> the remapper works on all input and it might result in unwanted side
> effects .. imagine that someone defines symbol 1 as • and gets \item instead
>
this is true -- it's not a general solution it's a trick , it if you abuse
then....

>
>
> Hans
>

Maybe I'm not able to express what I mean .
-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 3208 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2009-05-25 10:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 17:47 Peter Münster
2009-05-22 18:05 ` Wolfgang Schuster
2009-05-22 18:11 ` Hans Hagen
2009-05-25 10:02   ` luigi scarso
2009-05-25 10:17     ` Hans Hagen
2009-05-25 10:23       ` luigi scarso [this message]
2009-05-25 10:18     ` Peter Münster
2009-05-25 10:24       ` luigi scarso

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=fe8d59da0905250323m1fea6e7ch102702d31982a914@mail.gmail.com \
    --to=luigi.scarso@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).