Help translate PR server messages
Posted: 2007-09-03 04:32
In the upcoming patch, servers will be able to define in what language the server messages will be displayed to the players.
Those are the messages for kit request, rally point, commander assets, etc.
The following languages are available in PR's default localization folder:
dutch - EagleSquadron - download
french - Saobh - download
german - MAINERROR and SpearHead - download
italian - TroyMcClure - download
polish - Veres - download
portuguese_br - [R-PUB]Hfett - download
portuguese_pt - cctoide - download
spanish - 77SiCaRiO77 - download
swedish - NickO and Zrix - download
thai - download
If your server wants to run any other language, there's no problem. New languages:
hebrew - ZZEZ - download
russian - Sergi0[B2K]
norwegian - norhawk
Languages that won't work because of non-ascii characters:
chinese - wujj123456 - download
japanese - Jackass_miu - download
The server python code uses the new prpython.utxt localization file to get all the messages and uses special variables to replace specific content in the message.
The special variables are between #, for example #KIT#, #ASSET#, #TICKET#. These should NOT be translated, only the rest of the message around them.
Also notice the special code §C1001 is used to give another color to the words between them. For example: "this is green text but §C1001 this is orange text §C1001 and now green again". We recommend that you keep the color on these specific parts of the message in your translation.
Just a notice, most messages usually start with the player name in-game, for example:
"dbzao, you can't build a BUNKER too far from a friendly CP"
But in the language file I don't put the player name variable, I just start like this:
"you can't build a BUNKER too far from a friendly CP"
So, make sure you keep the feeling of somebody telling the player what he needs or what he's doing wrong.
Also make sure you don't use uppercase letters at the start of some strings unless the original string is also uppercase, since most strings have the player name and a comma before it.
Also a suggestion from wujj123456 is that you put the assets and kits names in english and in your language if adequate, something like this:
BUNKER (bunker in your language)
SUPPORT (support in your language)
So for portuguese, would be something like this:
ANTI AIR (ANTI AEREO)
SANDBAGS (SACOS DE AREIA)
Currently the file contains 115 messages that can be easily translated in a few minutes.
If you are interested in helping out, post the language you wish to translate bellow and I will send you the file via PM.
Don't post if you are not going to help translating.
EDIT: Looks like BF2 can't handle accentuation and different characters than english ones (ascii).
Those are the messages for kit request, rally point, commander assets, etc.
The following languages are available in PR's default localization folder:
dutch - EagleSquadron - download
french - Saobh - download
german - MAINERROR and SpearHead - download
italian - TroyMcClure - download
polish - Veres - download
portuguese_br - [R-PUB]Hfett - download
portuguese_pt - cctoide - download
spanish - 77SiCaRiO77 - download
swedish - NickO and Zrix - download
thai - download
If your server wants to run any other language, there's no problem. New languages:
hebrew - ZZEZ - download
russian - Sergi0[B2K]
norwegian - norhawk
Languages that won't work because of non-ascii characters:
chinese - wujj123456 - download
japanese - Jackass_miu - download
The server python code uses the new prpython.utxt localization file to get all the messages and uses special variables to replace specific content in the message.
The special variables are between #, for example #KIT#, #ASSET#, #TICKET#. These should NOT be translated, only the rest of the message around them.
Also notice the special code §C1001 is used to give another color to the words between them. For example: "this is green text but §C1001 this is orange text §C1001 and now green again". We recommend that you keep the color on these specific parts of the message in your translation.
Just a notice, most messages usually start with the player name in-game, for example:
"dbzao, you can't build a BUNKER too far from a friendly CP"
But in the language file I don't put the player name variable, I just start like this:
"you can't build a BUNKER too far from a friendly CP"
So, make sure you keep the feeling of somebody telling the player what he needs or what he's doing wrong.
Also make sure you don't use uppercase letters at the start of some strings unless the original string is also uppercase, since most strings have the player name and a comma before it.
Also a suggestion from wujj123456 is that you put the assets and kits names in english and in your language if adequate, something like this:
BUNKER (bunker in your language)
SUPPORT (support in your language)
So for portuguese, would be something like this:
ANTI AIR (ANTI AEREO)
SANDBAGS (SACOS DE AREIA)
Currently the file contains 115 messages that can be easily translated in a few minutes.
If you are interested in helping out, post the language you wish to translate bellow and I will send you the file via PM.
Don't post if you are not going to help translating.
EDIT: Looks like BF2 can't handle accentuation and different characters than english ones (ascii).