--traify glitches

[Miloch]

Spent a couple hours traifying Infinity Animations manually, because WeiDU turned it into a train wreck. For some reason, it increments the string count for blank strings (but ones with sounds without text such as SAY offset ~~ [MYSOUND], which don't need to be translated). On top of that, it puts a load of blank lines in the resulting .tra file where those strings would otherwise be (but shouldn't be anyhow). Also, it seems to want to translate one-letter variables and even WeiDU variables such as SOURCE_FILE, at least when they're enclosed in quotes (which they need to be for STRING_EQUAL* if I'm not wrong).

And while I'm on a rant (), is there a reason there's no documentation for stuff like *ASSOCIATIVE_ARRAY yet? I gave some examples a while back, and I assume GeN1e failed to follow through with more complete documentation, but at least give the syntax in the list of commands, for Gruumsh's sake.

[Leomar]

WeiDU traifies the VERSION command in the TP2, too, and I think that should be excluded. It is easier to handle the version number only in the TP2 instead of changing it in each TRA.

Greetings Leomar

[Miloch]

WeiDU traifies the VERSION command in the TP2, too, and I think that should be excluded.

Agreed; I only mentioned the more annoying glitches . But one thing I didn't mention that *is* rather annoying is that WeiDU doesn't parse the .tp2 for strings in external functions (.tpa/.tpp/.tph files). So you have to traify all those by hand separately, then sequence the @ numbers correctly, then paste them in your setup.tra. I did a lot of copy-pasting from my pseudo-generated-tra files to Excel and back to a text editor to get all that right. But the most annoying thing of course was updating all the .tp* files by hand with those string references.

[the bigg]

--traify is much more stupid than you're assuming (and a full algorithm rewrite is not likely to happen).
Some of your woes could be related to SPRINT - replace all instances of SPRINT with TEXT_SPRINT.
I can't follow INCLUDE references because some mods (widescreen for one) use %variables% in the file name; otherwise it'd be a decent idea. Write a couple of shell scripts to iterate through `find mymod -iname '*.tp*'` and look into --traify-old-tra (there should be a couple of old threads by cmorgan and jastey on PPG providing code examples and whatnot).
AFAICR Wisp provided code samples for *ARRAY, I'm looking for a descriptive tutorial like the rest of the tutorials are, rather than a simple code dump.

[Wisp]

AFAICR Wisp provided code samples for *ARRAY, I'm looking for a descriptive tutorial like the rest of the tutorials are, rather than a simple code dump.

I did? I don't remember that (doesn't mean it didn't happen, though).
Regardless, I did start on an attempt to provide some documentation for the undocumented features (I think) I understand. I'll see if I can't finish at least some of it.

[Miloch]

AFAICR Wisp provided code samples for *ARRAY, I'm looking for a descriptive tutorial like the rest of the tutorials are, rather than a simple code dump.

I did?

I did, actually, for all the good it did .

Tutorials are for wusses. Seriously. Half the existing ones aren't very intelligible anyway, and why do you need your hand held to figure out something like defining an array? It. Defines. An. Array. Ditto for compressing a BAM etc. Commented code serves the same purpose without taking up pages of unnecessary space. Anyway, I just want to see the syntax parameters in the documentation, so I don't need to dig up one of my tp2s (and figure out which one I used it in) every time I forget.

Some of your woes could be related to SPRINT - replace all instances of SPRINT with TEXT_SPRINT.

Another undocumented command?

I can't follow INCLUDE references because some mods (widescreen for one) use %variables% in the file name; otherwise it'd be a decent idea.

So either look up the variable value or skip such aberrations?

Write a couple of shell scripts to iterate through `find mymod -iname '*.tp*'` and look into --traify-old-tra (there should be a couple of old threads by cmorgan and jastey on PPG providing code examples and whatnot).

Must be ancient or in German or something, because I can't find anything like that on the net.

[the bigg]

Tutorials are for wusses. Seriously

Meh, I'll add your code dump sometimes this life.

Another undocumented command?

I think it's mentioned in the docs. Either way, it's one of those gotcha moments that everybody knows about and nobody talks about.

So either look up the variable value or skip such aberrations?

"It won't work on my mod" is reason enough to say "it might cause problems with mods from other people".

Must be ancient or in German or something, because I can't find anything like that on the net.

Searching ppg for traify-old-tra turns up a number of threads. this should be somewhat relevant.