ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug in latest beta?
Date: Mon, 10 Nov 2008 12:59:54 +0100	[thread overview]
Message-ID: <273B0BA8-8F86-4DE4-A9E9-50DA310B33ED@gmail.com> (raw)
In-Reply-To: <48af9a710811100155t1fc072e4m18c7cdd25efb8408@mail.gmail.com>


Am 10.11.2008 um 10:55 schrieb Chen Shen:

> Hi all,
>
> the following code used to work, but broke in the latest beta. \at
> works well, but \in appears as a math "member of set" symbol ( ∈ ).

You could use the last stable for the moment.

> ========================
> \starttext
> \placefigure[here][abc]{xyz}{123}
>
> abc \at[abc].
> abc \in[abc].
>
> \stoptext
> ========================


If you still want to use the last beta use the following patch,
Hans removed a few lines of code from enco-ini.mkiv and this
breaks the \in command because it is redefined later in the core
from the math commands.

\def\definecommand#1 #2 %
   {\setvalue{\string#1}{\dohandlecommand{#1}}%
    \setvalue{\characterencoding\string#1}{#2}}

\def\dohandlecommand#1%
    {\csname
       \ifcsname\characterencoding#1\endcsname
         \characterencoding
       \else
         \nocharacterencoding
       \fi
     #1\endcsname}

\definecommand in    {\doinatreference\currenttextreference}

Wolfgang

___________________________________________________________________________________
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:[~2008-11-10 11:59 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-10  9:55 Chen Shen
2008-11-10 11:59 ` Wolfgang Schuster [this message]
2008-11-10 12:37   ` Chen Shen
2008-11-10 15:25 ` Hans Hagen
2014-03-18 17:30 Pablo Rodriguez
2014-03-18 17:39 ` Wolfgang Schuster
2014-03-18 17:52   ` Pablo Rodriguez
2014-05-26  5:47 Pablo Rodriguez
2014-05-26  8:24 ` Hans Hagen
2014-05-26 15:44   ` Pablo Rodriguez
2014-12-10 18:51 Pablo Rodriguez
2014-12-10 19:14 ` Hans Hagen
2014-12-10 19:59   ` Pablo Rodriguez
2015-05-14 20:46 Pablo Rodriguez
2015-05-15  5:07 ` Pablo Rodriguez
2015-05-27 20:38 Pablo Rodriguez
2015-05-28 14:59 ` Otared Kavian
2015-05-31 11:34   ` Pablo Rodriguez
2015-05-28 17:10 ` Hans Hagen
2015-05-31 11:56   ` Pablo Rodriguez
2015-05-31 22:16     ` Hans Hagen
2015-06-01  6:45       ` Otared Kavian
2015-06-01  7:28         ` Pablo Rodriguez
2015-06-01  7:41           ` Otared Kavian
2016-09-05  5:59 Pablo Rodriguez
2016-09-05  6:36 ` josephcanedo
2016-09-05 15:10   ` Pablo Rodriguez
2016-09-06  4:43     ` Pablo Rodriguez
2016-09-05  8:39 Akira Kakuto
2016-09-05 14:33 ` Pablo Rodriguez
2016-09-05 14:44   ` luigi scarso
2016-09-05 15:32     ` Pablo Rodriguez
2017-11-01 13:18 Pablo Rodriguez
2017-11-01 15:50 ` Pablo Rodriguez

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=273B0BA8-8F86-4DE4-A9E9-50DA310B33ED@gmail.com \
    --to=schuster.wolfgang@googlemail.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).