Help translate PR HUD strings and messages
Posted: 2009-04-25 13:40
The objective is to get the PR localization files translated BEFORE the PR releases by volunteers from the community (DEVs, CONs, etc, are welcome as well).
These are the languages in the PR localization folder:
chinese (nozumu)
dutch ([R-DEV]AfterDune, Sluismaster1)
french (chargat, Guitouzid, [R-COM]Hauteclocque)
german (Priby, MadM!lo)
italian (ros)
japanese
korean
norwegian (HeXeY, Mathisen)
polish (PaulPL1, Aquiller, [R-COM]Ragni<RangersPL>)
portuguese (LosTLife, ___sangue-ruim___)
russian (DankE_SPB, [wow]titan, DiRaven)
spanish (elemanoel, Scar, FusionGames, sykrum)
swedish (manligheten)
thai
To accomplish that objective I've setup an open SVN repository on Google Code:
pr-localization - Google Code
If you want to collaborate, post bellow your Google Account username (the part before the @gmail.com) and the language you want to help with and I will add you as a Project Member.
You will then be able to Checkout the files to your computer using Subversion (TortoiseSVN is what we use) and translate away. Then you Commit the changes back to the repo for review.
After you started making changes, make sure to check for Updates to the english files to know what strings were modified/added using the Diff command. Also always run the Update command before doing new changes to make sure you have the latest version.
Follow this link to your Google Code password (different than your gmail one) for doing SVN commits.
You will need Notepad or any text editor and force it to open the utxt files. Make sure to not delete the 2 characters at the beginning and end of each string. These are special separators used by BF2. Also would be nice if you could test these files before committing, by at least putting them in your PR folder and seeing if you CTD when starting PR.
Also, the strings in prmessages.utxt that start with PYTHON_ should not have any accentuated characters as these are sent from Python and have issues with those characters. For latin based languages, stuff like "coração" should be translated to "coracao" to avoid problems. For the other languages we will have issues and probably can't be changed, but at least these messages are not used that much.
To check for any missing strings in comparison to the english files, open this file (updated every 30 min):
http://realitymodfiles.com/dbzao/pr_localization.txt
Well, that's it, post the info bellow if you would like to help.
These are the languages in the PR localization folder:
chinese (nozumu)
dutch ([R-DEV]AfterDune, Sluismaster1)
french (chargat, Guitouzid, [R-COM]Hauteclocque)
german (Priby, MadM!lo)
italian (ros)
japanese
korean
norwegian (HeXeY, Mathisen)
polish (PaulPL1, Aquiller, [R-COM]Ragni<RangersPL>)
portuguese (LosTLife, ___sangue-ruim___)
russian (DankE_SPB, [wow]titan, DiRaven)
spanish (elemanoel, Scar, FusionGames, sykrum)
swedish (manligheten)
thai
To accomplish that objective I've setup an open SVN repository on Google Code:
pr-localization - Google Code
If you want to collaborate, post bellow your Google Account username (the part before the @gmail.com) and the language you want to help with and I will add you as a Project Member.
You will then be able to Checkout the files to your computer using Subversion (TortoiseSVN is what we use) and translate away. Then you Commit the changes back to the repo for review.
After you started making changes, make sure to check for Updates to the english files to know what strings were modified/added using the Diff command. Also always run the Update command before doing new changes to make sure you have the latest version.
Follow this link to your Google Code password (different than your gmail one) for doing SVN commits.
You will need Notepad or any text editor and force it to open the utxt files. Make sure to not delete the 2 characters at the beginning and end of each string. These are special separators used by BF2. Also would be nice if you could test these files before committing, by at least putting them in your PR folder and seeing if you CTD when starting PR.
Also, the strings in prmessages.utxt that start with PYTHON_ should not have any accentuated characters as these are sent from Python and have issues with those characters. For latin based languages, stuff like "coração" should be translated to "coracao" to avoid problems. For the other languages we will have issues and probably can't be changed, but at least these messages are not used that much.
To check for any missing strings in comparison to the english files, open this file (updated every 30 min):
http://realitymodfiles.com/dbzao/pr_localization.txt
Well, that's it, post the info bellow if you would like to help.



