Re: issue with beta from 2019.11.29 21:47 in Windows

[Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>]

Pablo Rodriguez schrieb am 02.12.2019 um 16:18:
> Dear list,
>
> I have the following sample:
>
>      \def\ThisOption{ab}
>      \def\ThatOption{ábc}
>      \starttext
>      \executesystemcommand{contextjit --purgeall
> --arguments="OptionThis={\ThisOption},OptionThat={\ThatOption}" second.tex}

Limited alternative (no rerun when second.pdf exists and by default the 
resulting PDF is loaded as image).

\typesetfile[second.tex][--arguments="OptionThis={\ThisOption},OptionThat={\ThatOption}"][object=no]

>      \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?

I get the same results with MkIV but LMTX works.

> Is there any ConTeXt command (or Lua function) that translates non-ASCII
> chars to their ASCII values?

Lua: characters.shaped(...)

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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________