ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Giuseppe Bilotta <bourbaki@bigfoot.com>
Cc: ntg-context@ntg.nl
Subject: Re[3]: Broken catcodes
Date: Sun, 26 May 2002 22:38:19 +0200	[thread overview]
Message-ID: <190705343.20020526223819@bigfoot.com> (raw)
In-Reply-To: <5.1.0.14.1.20020526193620.02cd4058@remote-1>

Sunday, May 26, 2002 Hans Hagen wrote:

HH> The problem was introduced when adding support for french active : ; etc. 
HH> The reset code was generated under an unprotected regime, so the patch goes 
HH> into lang-spe.tex;

Thank you.

HH> For Oblomov's eyes only:

HH> I also took the opportunity to extend the protection report code a bit

HH> \def\reportunprotection   {\message{<unprotect \protectionstate>}}
HH> \def\reportprotection     {\message{<protect   \protectionstate>}}

HH> \def\protectionstate
HH>    {\the\protectionlevel
HH>     \ifcase\protectionthreshold=0\else
HH>       :\space
HH>       @=\the\catcode`@\space\space
HH>       !=\the\catcode`!\space\space
HH>       ?=\the\catcode`?%
HH>     \fi}

Yes, that's more or less the code I was using myself when
(unsuccessfully) trying to trace the thing ... :-)

-- 
Giuseppe "Oblomov" Bilotta


  reply	other threads:[~2002-05-26 20:38 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-25 18:14 Giuseppe Bilotta
2002-05-25 20:17 ` Hans Hagen
2002-05-25 21:46   ` Re[2]: " Giuseppe Bilotta
2002-05-26 17:39     ` Hans Hagen
2002-05-26 20:38       ` Giuseppe Bilotta [this message]
     [not found]       ` <pragma@wxs.nl>
2001-03-12 16:50         ` fonts fonts and fonts Hans Hagen
2001-03-12 17:07           ` Frans Goddijn
2001-03-12 23:11           ` Christoph Dreyer
2001-03-13  9:33             ` S2P development
2001-03-13 10:12               ` Han The Thanh
2001-03-13 10:35               ` Hans Hagen
2001-03-14 21:32               ` H. Ramm
2001-03-13  7:12           ` Steve Lumos
2001-03-13  9:13             ` Hans Hagen
2001-03-14  0:29             ` Uwe Koloska
2001-03-13 14:35           ` Ed L Cashin
2001-03-14  0:18           ` Uwe Koloska
2001-03-15 21:55           ` H. Ramm
2002-05-27 15:27         ` Re[2]: Broken catcodes Daniel Flipo
2002-05-27 15:32           ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2001-05-30 11:40 Environments, Projects, Products, Components Giuseppe Bilotta
2001-05-30 15:14 ` Taco Hoekwater
2001-05-30 18:01   ` Re[2]: " Giuseppe Bilotta
2001-05-31  7:51     ` Taco Hoekwater
2001-05-31  9:34       ` Hans Hagen
2001-08-30 17:54         ` Steve Lumos
2001-08-31  7:19           ` Hans Hagen
2001-05-31  8:11     ` Re[2]: " Hans Hagen
2001-02-22  7:24 Horizontal centering \startlines...\stoplines Steve Lumos
2001-02-22  8:47 ` Horizontal centering \startlines...\stoplines / poems Hans Hagen
2001-03-03  9:22   ` Steve Lumos
2001-03-04 21:09     ` Hans Hagen
2001-03-07  4:08       ` Steve Lumos
2001-03-07  8:14         ` Hans Hagen
2000-08-19 12:21 Setting up footnotes Joop Susan
2000-08-21 11:00 ` Hans Hagen
2000-08-21 18:19   ` Joop Susan
2000-08-22  6:59     ` 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=190705343.20020526223819@bigfoot.com \
    --to=bourbaki@bigfoot.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).