Current status: v238 traify-ing chokes on %tutu_var% (used in combination with dlg or item names, for example) and also %(UN)SOLVED_JOURNAL% (used instead of (UN)SOLVED_JOURNAL, obciously).
It produces d/tra pairs for any kind of OUTER_SPRINTs used for triggers or transactions (with error messages, but they have no influence), like %ERASEJOURNALENTRY_xx%, Class(Player1,MAGE%_ALL%), ActionOverride("Ragefast",%STARTDIALOGNOSET%([PC])), %ISGABBERPLAYER1%, CreateCreature("c#lcba02",[3452.3736]%FACE_9%)
I guess there is nothing you can do to make traify not stopping for %tutu_var%? I can live with replacing the journal commands before and after traify-ing, but removing and adding the %tutu_var% has a high risk of introducing errors into the d by forgetting some instances (mass replace would be even worse. Maybe it's my way of naming my dialogue states and variables.)