ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Cc: ntg-context@ntg.nl
Subject: Re: xml again
Date: Mon, 26 Nov 2001 10:12:16 +0100	[thread overview]
Message-ID: <20011126101216.73ad5e01.taco@elvenkind.com> (raw)
In-Reply-To: <01112417461400.00957@levana>

> it helps when I change things in xtags-ini.tex
> 
> [...] 
> .unexpanded.gdef.enableXML*
> [...]
>    .catcode`._=.@@other* 
> [...]
> *   .catcode`._=.@@active .def_B&tex-underscore;E*
> [...]

I head a similar problem with '#', under some circumstances. Hans, I believe the doubling is part of the log writing code, meaning that there is actually really just one hash mark in memory. That is quite important, because '#FFFFFF' (HTML color white) became '\getXMLentity{tex-hash}FFFFF' (I lost one F!). So I now have 

  .catcode`.#=.@@other

which it works flawlessly.

-- 
groeten,

Taco


  reply	other threads:[~2001-11-26  9:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-24 16:46 Patrick Gundlach
2001-11-26  9:12 ` Taco Hoekwater [this message]
2001-11-26 14:22 ` 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=20011126101216.73ad5e01.taco@elvenkind.com \
    --to=taco@elvenkind.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).