Mallis
Professional Jet Addict
Hey there,
I'm currently translating the game + Restoration Project to Portuguese, and I realized it was a pain in the ass to manually translate the .msg files in Fallout 2 in a revision-friendly manner, so I created this lil console app in C++. It should improve translation time by about 50% to 60% (Yes, I'm pulling these numbers out of my ass).
Basically, it gives you the strings one by one, and you just need to type in the translation and press Enter. It automatically comments the untranslated line from the file (by removing the brackets and adding a # to the beginning) and inserts the translated line right below it, all formatted with the number code, brackets and everything. The reason for commenting out the untranslated lines is purely for revision, in case you are collaborating with other translators and need to make sure everything is ok with the translation, etc.
It's real easy to use, just select the msg file, the line you wanna begin translating from, and start typing out. Then, when you're happy, just type in "save" and it will overwrite the untranslated file (yeah, don't forget to save). Further instructions are displayed in the app.
I've never fiddled with the files in Fallout 1, I don't know if the resource files are in the same format, but if they are, hey, you can use this to translate Fallout 1 too!
Suggestions and feedback are welcome, I will definitely improve the tool. Make sure to tell me if everything is alright with the encoding and other annoying technical shit.
Have fun and happy translating!
EDIT:
*Reaching end of file no longer crashes the program. What a stupid oversight.
*Typing in an invalid number code displays a message telling the user to try another number.
*Increased font and console size.
EDIT 2:
*Fixed a bug where the tool would screw up while trying to translate very similar words. EX: Desert to Deserto, or Guard to Guarda.
*Added an option to open another file for translation without having to close and reopen the app.
*Added a filter to the File Select so that you can only open .MSG files.
EDIT 3:
*The tool now correctly displays characters according to your region and locale preferences.
EDIT 4:
*GNU/Linux support is out! Just make sure to download the correct file, the main difference is that in the Windows version you can select a file from a GUI dialog, and in Linux you'll have to specify the path to the file (ex.: /home/fallout2/MAP.MSG).
Note: In Linux, the file output encoding defaults to UTF-8. If I'm not mistaken, Fallout 2 uses ANSI encoding with code pages (1252 for Latin, 1253 for Cyrillic, etc.). So make sure to convert the file to ANSI if it happens to be in UTF-8, at least until I can figure out how to output it to ANSI in Linux. One can do that easily with Notepad++: just go to Format > Convert to ANSI.
I'm currently translating the game + Restoration Project to Portuguese, and I realized it was a pain in the ass to manually translate the .msg files in Fallout 2 in a revision-friendly manner, so I created this lil console app in C++. It should improve translation time by about 50% to 60% (Yes, I'm pulling these numbers out of my ass).
Basically, it gives you the strings one by one, and you just need to type in the translation and press Enter. It automatically comments the untranslated line from the file (by removing the brackets and adding a # to the beginning) and inserts the translated line right below it, all formatted with the number code, brackets and everything. The reason for commenting out the untranslated lines is purely for revision, in case you are collaborating with other translators and need to make sure everything is ok with the translation, etc.
It's real easy to use, just select the msg file, the line you wanna begin translating from, and start typing out. Then, when you're happy, just type in "save" and it will overwrite the untranslated file (yeah, don't forget to save). Further instructions are displayed in the app.
I've never fiddled with the files in Fallout 1, I don't know if the resource files are in the same format, but if they are, hey, you can use this to translate Fallout 1 too!
Suggestions and feedback are welcome, I will definitely improve the tool. Make sure to tell me if everything is alright with the encoding and other annoying technical shit.
Have fun and happy translating!
EDIT:
*Reaching end of file no longer crashes the program. What a stupid oversight.
*Typing in an invalid number code displays a message telling the user to try another number.
*Increased font and console size.
EDIT 2:
*Fixed a bug where the tool would screw up while trying to translate very similar words. EX: Desert to Deserto, or Guard to Guarda.
*Added an option to open another file for translation without having to close and reopen the app.
*Added a filter to the File Select so that you can only open .MSG files.
EDIT 3:
*The tool now correctly displays characters according to your region and locale preferences.
EDIT 4:
*GNU/Linux support is out! Just make sure to download the correct file, the main difference is that in the Windows version you can select a file from a GUI dialog, and in Linux you'll have to specify the path to the file (ex.: /home/fallout2/MAP.MSG).
Note: In Linux, the file output encoding defaults to UTF-8. If I'm not mistaken, Fallout 2 uses ANSI encoding with code pages (1252 for Latin, 1253 for Cyrillic, etc.). So make sure to convert the file to ANSI if it happens to be in UTF-8, at least until I can figure out how to output it to ANSI in Linux. One can do that easily with Notepad++: just go to Format > Convert to ANSI.
Attachments
Last edited: