From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: issue with beta from 2019.11.29 21:47 in Windows
Date: Mon, 2 Dec 2019 16:18:29 +0100 [thread overview]
Message-ID: <f1e09514-2465-60ca-5f9a-87ec355ee4af@gmx.es> (raw)
Dear list,
I have the following sample:
\def\ThisOption{ab}
\def\ThatOption{ábc}
\starttext
\executesystemcommand{contextjit --purgeall
--arguments="OptionThis={\ThisOption},OptionThat={\ThatOption}" second.tex}
\contextversion
\stoptext
The contents of second.tex read:
\starttext
\enablemode[\env{OptionThis}]
\enablemode[\env{OptionThat}]
This: \doifmodeelse{ab}{enabled}{disabled}.\par
That: \doifmodeelse{ábc}{enabled}{disabled}.
\stoptext
I use --arguments to pass modes to documents compiled via
\executesystemcommand.
Everything worked fine. This morning I updated ConTeXt at work (with
Win7) and modes with non-ASCII chars aren’t recognized.
Could anyone confirm the issue I’m describing in Windows?
Is there any ConTeXt command (or Lua function) that translates non-ASCII
chars to their ASCII values?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2019-12-02 15:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 15:18 Pablo Rodriguez [this message]
2019-12-02 17:01 ` Wolfgang Schuster
2019-12-02 17:46 ` Pablo Rodriguez
2019-12-02 20:45 ` Wolfgang Schuster
2019-12-03 19:37 ` Pablo Rodriguez
2019-12-03 21:14 ` Hans Hagen
2019-12-04 21:19 ` Pablo Rodriguez
2019-12-05 8:23 ` Hans Hagen
2019-12-05 19:31 ` Pablo Rodriguez
2019-12-06 9:01 ` Arthur Reutenauer
2019-12-07 13:40 ` Pablo Rodriguez
2019-12-07 15:32 ` Hans Hagen
2019-12-07 22:49 ` Pablo Rodriguez
2019-12-07 23:33 ` Hans Hagen
2019-12-04 21:27 ` Pablo Rodriguez
2019-12-02 17:05 ` Hans Hagen
2019-12-02 17:51 ` Pablo Rodriguez
2019-12-02 22:22 ` Hans Hagen
[not found] <7992CF71224042639D33FC342999C075@CJ3001517A>
2019-12-03 8:17 ` Hans Hagen
2019-12-03 19:45 ` Pablo Rodriguez
2019-12-03 21:11 ` 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=f1e09514-2465-60ca-5f9a-87ec355ee4af@gmx.es \
--to=oinos@gmx.es \
--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).