It is recommended to use the token syntax (:Cxxx)

Even if the text always uses English-US, it is recommended to use the
token syntax (:Cxxx) for command and constant names to protect
against potential problems due to commands or constants being renamed
from one version of 4D to another.

Did someone already write a code to insert the http://doc.4d.com/4Dv17/4D/17/4D-Transformation-Tags.300-3730734.en.htmltoken >beside an English 4D command?

You can try to save the method code (export) with token and then to read back the text and copy paste it in you code (not tested)

: Bertrand SOUBEYRAND

Even if the text always uses English-US
That does not “protect” against the use of a french 4D. In C/S, you can have a guy working in french and another in english. I use tokens sometimes, in formulas as text (calculated listbox column, for example - when I’m not lazy.)

BTW, http://forums.4d.com/Post/FR/15522046/2/15532109#15532112tokens for constants> (K:xxx) are missing in the doc, I wonder why.

<code 4D>
Parse formula($Txt;Formula out with tokens)
</code 4D>

Available soon via the macro “Special past” into 4DPop Macros :

[]27579718;“Your comment here…”[/]

<code 4D>
Parse formula($Txt;Formula out with tokens)
</code 4D>

Available soon via the macro “Special past” into 4DPop Macros :

[]27579750;“Your comment here…”[/]

<code 4D>
Parse formula($Txt;Formula out with tokens)
</code 4D>