Domi Posted February 7, 2006 Share Posted February 7, 2006 Good even, everyone. Basically, I have a wagonload of D-coded files, and I need to TRA'fy them. Now, I have not TRA'fied ever in my life, so I am looking for a simple solution. Below is JC's tutorial included in WeiDU Documentation, that leads me to believe that I need to fire up WeiDU and load in file after file, recording the last string number and then starting the next file with the next one etc. It sounds very cumbersome. So, firends and modders, is that the latest in TRA' technology, or is there anywhere a smart program that converts the contents by the folder? Or can WeiDU do that on its own if I ask it to TRA the folder? However, some WeiDU users, for reasons of convenience or simply never anticipating the opportunity to translate, may have originally chosen the "hard-coded" approach but now regret that decision. --traify will break out all the text in SAY, REPLY, and JOURNAL entries into translation-ready format. --traify may also be used on TP2 files. To turn the hard-coded D file FWKI.d into a new D/TRA combo, use --traify and --out to specify the input and output filenames, respectively: C:\Program Files\Black Isle\BGII - SoA\> weidu --traify fwki.d --out fwki-new.d After a brief pause, fwki-new.d and fwki-new.tra will be created. The --traify process turns fwki.d's APPEND J#KLSYJ IF ~~ THEN BEGIN KelseySAHPR4 SAY ~Urk. Who was the lucky donor?~ IF ~~ THEN EXTERN SAHPR2 10 END END into fwki-new.d's APPEND J#KLSYJ IF ~~ THEN BEGIN KelseySAHPR4 SAY @0 IF ~~ THEN EXTERN SAHPR2 10 END END and in the newly created fwki-new.tra, you will find @0 = ~Urk. Who was the lucky donor?~and this dialogue file is now ready for translation. --traify works from the top of the D down, starting at @0. It will NOT skip over any existing @x translation references it finds, so if your D contains any translation support at all, it is best to use --traify# as well. Because standard --traify starts at @0 and is unaware of any any existing @x entries in the D, if you have begun to convert a D to a D/TRA pair by hand, you may have @x entries that clash with --traify's results. In other words, if you already have a state that says IF ~~ THEN BEGIN blah SAY @0 IF ~~ THEN EXIT END--traify will not skip @0 automatically, you will have two locations where @0 is used but you intended to use two different strings, and this will be bad. To avoid this problem, add the --traify# argument to specify the starting number (rather than 0) for new @x entries. C:\Program Files\Black Isle\BGII - SoA\> weidu --traify fwki.d --traify# 1000 --out fwki-1000.d will create new @x references in fwki-1000.tra that begin at @1000, instead of @0. --traify# may also be used on TP2 files. Finally, note that --traify works for BAF files as well. Link to comment
This topic is now archived and is closed to further replies.