ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: textbackground > bug
Date: Sun, 18 Dec 2005 11:40:49 +0100	[thread overview]
Message-ID: <43A53CB1.30001@elvenkind.com> (raw)
In-Reply-To: <B3CDDC4A-98C3-44A9-B36C-FADD27972A23@science.uva.nl>

Hans van der Meer wrote:
> Therefore I suspect it has something to do with the output routine  
> where \s is taken as the next macro.
> A simpe experiment (\def\s{something}) shows that indeed a macro \s  is 
> executed.
> Is someone here messing up the catcode's of the letters?

Yes, the \startJAVA command :-)

The problem is that context is loading the pdfr-ec resource
file (Glyph -> Unicode mapping) while the prettytype catcodes
are in effect, and it does not properly switch back to
"non-verbatim" catcodes.

I am not quite sure what the best way is to fix this, but
I've redefined that loading macro in my preamble, like so,
and it seems to work as a temporary workaround:

\def\dododoincludepdffontresource#1% encoding
   {\bgroup
    \def\currentencoding{#1}%
    \doifvaluesomething\pdffontfileresource
      {\uncatcodeallcharacters % new
       \catcode`\[=12          % new*
       \catcode`\]=12          % new*
       \setnaturalcatcodes     % new
       \startreadingfile
         \readsysfile{pdfr-\getvalue\pdffontfileresource}
            \donothing\donothing
       \stopreadingfile
       \letgvalue\pdffontfileresource\empty}%
    \egroup}

  reply	other threads:[~2005-12-18 10:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-17 20:29 Hans van der Meer
2005-12-18 10:40 ` Taco Hoekwater [this message]
2005-12-18 19:11   ` Hans van der Meer
2005-12-18 21:10 ` 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=43A53CB1.30001@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).