Localized Strings

Post by **dlh** » Mon Jun 06, 2005 7:13 am

This is just a reminder that there are a few strings that need to be localized.

1. /msg error codes from return on num_matches
2. /players (logged in)/(logged out) text
3. /radmin /login and /logout
4. bookmarks_menu, bookmarks_menu_edit, bookmarks_menu_edit_slot, bookmarks_menu_address, bookmarks_menu_address_help, bookmarks_menu_name, bookmarks_menu_name_help, bookmarks_menu_connect
5. Headlights
6. teamkill messages
7. pref_time24hour_text and _help
8. pref_explosion_text and pref_explosion_help
9. Added "b" key to network_master_browserhelp
10. hud_menu, hud_menu_help

Post by **Tank Program** » Mon Jun 06, 2005 9:55 am

Also the teamkill string...

Post by **Lucifer** » Mon Jun 06, 2005 10:17 am

Aha, finally a forum split that might make a whole lot of sense.

Can we have a forum for translation? A thread there would be basically a list of strings that need to be translated in one post, discussion of those strings, and ending with hopefully a series of posts saying the translation is complete for each locale supported.

Post by **Lucifer** » Tue Jun 07, 2005 7:33 am

$pref_time24hour_text and _help as well (new strings for the clock, the 24 hour clock was bothering me)

k · Post by k » Tue Jun 07, 2005 8:57 am

pref_explosion_text and pref_explosion_help.

Post by **dlh** » Tue Jun 07, 2005 7:30 pm

added English strings for bookmarks, need German translation. (It has been rebranded the Bookmarks Menu)

Post by **Lucifer** » Wed Jun 08, 2005 12:23 am

Any word on these? Should we Google Translate them?

Luke-Jr · Post by **Luke-Jr** » Wed Jun 08, 2005 12:32 am

nemostultae wrote:(It has been rebranded the Bookmarks Menu)

Good; that avoids my debate about favoUrite...

Post by **dlh** » Wed Jun 08, 2005 3:28 am

Added info about adding a server your bookmarks. Please translate network_master_browserhelp.

Also, who thinks a there should be a different language selection menu on your first run. I think it should list all the options for you to see, the only showing one option and use left/right is a little non-intuitive.

Post by **dlh** » Wed Jun 08, 2005 4:31 am

I moved the HUD options to its own menu, because there were so many of them. And as a result, hud_menu and hud_menu_help

Website · Post by **Z-Man** » Wed Jun 08, 2005 6:44 am

Nooo, no google translation. I'll do them when I have time.

Post by **dlh** » Sat Jul 09, 2005 9:48 pm

Lucifer made a config item for the position of the center_message text location, so thats needs translation too.

Post by **Lucifer** » Sat Jul 09, 2005 10:01 pm

nemostultae wrote:Lucifer made a config item for the position of the center_message text location, so thats needs translation too.

Not really? I don't know, there's no menu item for it so it doesn't appear in the GUI. I don't remember if I had to add a new translated string, though. I've slept since then.

Post by **dlh** » Sat Jul 09, 2005 10:04 pm

Lucifer wrote:
nemostultae wrote:Lucifer made a config item for the position of the center_message text location, so thats needs translation too.
Not really? I don't know, there's no menu item for it so it doesn't appear in the GUI. I don't remember if I had to add a new translated string, though. I've slept since then.

It is a config item, though, correct? They still need to be translated.

Website · Post by **Z-Man** » Thu Jul 21, 2005 10:51 pm

Just to fetch some feedback:
I added language/update.py to CVS. It's a small python script I hacked together that is supposed to keep the translation files in sync with english_base.txt (some hardcoding there....); a sample form a synced deutsch.txt looks like this:

Code: Select all

#                             Start position of the smart camera
camera_smart_start_y_help     Startposition der SmartCam

#                             use custom camera settings when glancing with the smart camera
#camera_smart_glance_custom_help UNTRANSLATED

A complete version is attached.

The general file structure is taken from english_base.txt, the original text of the items are added as comments, eventual introductory comments of the translated file are also kept. Untranslated strings are marked.

In another mode (call it with --dist), the script can strip all comments from the translation files so they don't take that much space in the distribution; the operation is fully reversible.

The question I want to ask is this:
How should the translated files be kept in CVS? There are two competing principles here:
a) Files should be in CVS as the user edits them
b) no automatically generated files should be in CVS
Well, of course it's most convenient to edit the translated file WITH the English original texts, but these original texts are copied over from another file that already is in CVS. So a) says the original text should be in the CVS version of the translated files, and b) says it shouldn't. Quite a dilemma.

I'd tend to giving a) the higher priority, but wanted to get some feedback before I pollute the CVS database first with a huge addition of lines, only to remove half of them later after you convinced me b) is more important

Another thing is a more up to date version of a french translation I received by mail (there is one for 0.2.6.0 floating around). It's attached, too. Can anyone with a bit better feeling for french check whether it's allright? Canadians or Canadians-in-Exile would do.