> to solve my problem I need to find why my function ParseCSVdata
> incorrectly parses strings stored in a macro.
You can work around the problem by defining a Lua function that calls
the macro:
\def\parse#1{\directlua{pars("#1")}}
You can then either call it directly:
\parse{\printaction}
or from Lua with tex.print:
\startluacode
tex.print("\\parse{\\printaction}")
\stopluacode
and the macros are expanded in the order you want.
It's admittedly a bit silly, but it works.
As a side note, the infinitive of the verb related to “parser” is “to
parse” in English, with an ‘e’ at the end.
Arthur
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
