In my mind, it would look like this:
--untra <TRA-able file> <TRA file>or like this:
--untra <TP2 file> <language>
And systematically parse the file, and replace all @x 's with the equivalent string from the TRA file.
Is this doable?
Feature Request --untra
Started by MagusWizardo, Apr 20 2004 11:55 PM
2 replies to this topic
#1
MagusWizardo
-
- Member
- 201 posts
Don't ask... please don't ask.
Posted 20 April 2004 - 11:55 PM
For me atleast, it is very difficult to read a TRAified TP2 , but we all know that they make translation easier... so, what I was doing was to keep a copy of my non-tra'd TP2... Then my computer crashed. Several times. So, I no longer have a copy of the non-tra'd TP2. Since I couldn't be bothered reconstructing the non-tra'd TP2 by hand (copy/paste, copy/paste, copy/paste...), and other people undoubtedly have/will find themselves in the same situation, I would like a --untra command line argument...
In my mind, it would look like this:
And systematically parse the file, and replace all @x 's with the equivalent string from the TRA file.
Is this doable?
In my mind, it would look like this:
And systematically parse the file, and replace all @x 's with the equivalent string from the TRA file.
Is this doable?
#2
-Guest-
-Guest-
-
- Guest
Posted 21 April 2004 - 01:10 AM
Ooh. I actually wanted this feature, too. With a large Tp2 and Tra combo, it's sometimes difficult to add new strings (because of the way I organize the Tra file, I have to spend some time searching for the last string before I can add a new one).For me atleast, it is very difficult to read a TRAified TP2 , but we all know that they make translation easier...
One of these days I'll learn to simply traify the Tp2 but continue using the original (un-traed) file.
#3
jcompton
-
- Modder
-
- 492 posts
Posted 21 April 2004 - 07:39 AM
--automate essentially does what you describe already.
Pocket Plane mods and modlist etc.
