El mar., 7 de jul. de 2020 a = la(s) 13:54, Phelype Oleinik (phe.h.o= 1@gmail.com) escribi=C3=B3:

Hi Jairo,

ConTeXt's \unexpanded is e-TeX's \protected, so the error boils dow= n to
something like: \edef\x{\unexpanded{#}}, which works in Plain but not in ConTeXt.

Usually packages that claim to be generic have to cope with that.
xstring would need to do (in a ConTeXt-specific loader):
=C2=A0 =C2=A0 \let\xstring@unexpanded\normalunexpanded
and
=C2=A0 =C2=A0 \let\xstring@unexpanded\unexpanded
in Plain and LaTeX loaders, then then use \xstring@unexpanded in the
code.=C2=A0 But `xstring` doesn't claim (that I found, at least) to be<= br> compatible with ConTeXt, so it's understandable: though if it is
compatible with Plain, it wouldn't be hard to adapt to ConTeXt.

That said, you can load `xstring` if you do:
=C2=A0 =C2=A0 =C2=A0\let\unexpanded\normalunexpanded
=C2=A0 =C2=A0 =C2=A0\input xstring.tex
=C2=A0 =C2=A0 =C2=A0\let\unexpanded\protected
but the internals of the package will probably be comprimised by the
misuse of (ConTeXt) \unexpanded.

Phelype

On Tue, Jul 7, 2020 at 3:40 PM Jairo A. del Rio <jairoadelrio6@gmail.com> wrote= :
>
> Reading about macro bundles meant to be generic (format agnostic), som= e of them work in plain/LaTeX, but crash when loaded on ConTeXt. The follow= ing happens with xstring.tex
>
> tex error > tex error on line 372 in file xstring.tex: ! Illegal pa= rameter number in definition of \xs_reserved_C
>
>
> <to be read again>
>
> 1
>
> \xs_newlines ->\unexpanded {}\xs_def \xs_arg_i {##1
>
> }
>
> \xs_newmacro_ ...name \xs_myarg }\edef \xs_reserved_C {\unexpanded \ex= pandafter {\xs_newlines
>
> }\edef \noexpand \xs_call }\edef \xs_reserved_D {...
>
> l.372 \xs_newmacro\StrRemoveBraces{}{1}{1}
>
> {%
>
>
> <empty file>
>
>
> You meant to type ## instead of #, right? Or maybe a } was forgotten s= omewhere
>
> earlier, and things are all screwed up? I'm going to assume that y= ou meant ##.
>
> I've tried changing the catcode regime, but with no effect.
>
> Don't misunderstand me. I'm aware of ConTeXt capabilities and = string manipulation via Lua. My question is more like: "Why doesn'= t xstring.tex?"
>
> Sorry if my question is outside the scope of ConTeXt developers/mainta= iners. Thank you very much.
>
> Jairo :)
>
> ______________________________________________________________________= _____________
> 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/listin= fo/ntg-context
> webpage=C2=A0 : http://www.pragma-ade.nl / http://context.aanhet.ne= t
> archive=C2=A0 : https://bitbucket.org/phg/cont= ext-mirror/commits/
> wiki=C2=A0 =C2=A0 =C2=A0: http://contextgarden.net
> ______________________________________________________________________= _____________
___________________________________________________________________________= ________
If your question is of interest to others as well, please add an entry to t= he Wiki!

maillist : ntg-cont= ext@ntg.nl / http://www.ntg.nl/mailman/listinfo/nt= g-context
webpage=C2=A0 : http://www.pragma-ade.nl / http://context.aanhet.net=
archive=C2=A0 : https://bitbucket.org/phg/context-m= irror/commits/
wiki=C2=A0 =C2=A0 =C2=A0: http://contextgarden.net
___________________________________________________________________________= ________