Roster 2.0 added a bunch of new strings to the localization files

With this new version, it is even more important we get the correct translations for Roster

The addon system is revamped for Roster 2.0, meaning most of the functionality is now provided by addons.
Make sure you check the locale files in the addon folders as well


When editing these files, do NOT use notepad, use a real text editor.
Wordpad works but I suggest Notepad++

Character encoding needs to be utf-8 encoded.
The files need to be saved in ansi, or UTF-8 without the BOM

With all that said, please make a new post with the following subject

Localization [LOCALE] svn[####]

Replace LOCALE with the locale being translated to, such as deDE
Replace #### with the svn revision of your beta build, such as 1202

Here is a good website for english to German translations

www.leo.org

Is there any coordination for the French localization ?

I've finished the first localization file and will begin to translate the add-ons local.

What's the best way to proceed with that ?

Best regards.

Just a note for french translators :

Before each : there is an unicode "non breakable space", different from a normal space.

Code: Select all

$utf8nbsp = chr(194).chr(160); 

So for example, typics regulars expressions can be written as :

Code: Select all

$lang['tooltip_equip']='Équipé'.$utf8nbsp;
$lang['tooltip_preg_madeby']='/\<Artisan'.$utf8nbsp.': (.+)\>/';
$lang['tooltip_preg_block']='/Bloquer'.$utf8nbsp.': (\d+)/'; 

Is there a way to insert this character without using php variables?
We are trying to stay away form using them in locale files

Yeah no problem Zanix. Better ways of handling it.. Great to know why my matches failed though!

for translation of addons use addons because in French greffons is medical world.

in attachement a new version for localisation fr

zanix wrote:Is there a way to insert this character without using php variables?
We are trying to stay away form using them in locale files

Code: Select all

$lang['tooltip_equip']='Équipé'.chr(194).chr(160);
$lang['tooltip_preg_madeby']='/\<Artisan'.chr(194).chr(160).': (.+)\>/';
$lang['tooltip_preg_block']='/Bloquer'.chr(194).chr(160).': (\d+)/'; 

If you try to copy paste character n°160, some softwares convert it in character n°32 (a simple space). So if you want to be sure that any copy/paste won't alter your file, you have to type explicitly in localization file :

Code: Select all

chr(194).chr(160) 

And you have to type the character before with the same way, if you want the file readable by an utf8 editor...

(Yes I know, utf-8 french characters are very disappointing...)

The reason we don't want php in the locale files is because we eventually want to put these files up so users can submit corrections to these files via our site

I understand, so you have to warn these users about this "little" problem.

It's possible to make locale files without chr(194).chr(160) by replacing with ascii values, but when you merge files, you have to be very careful (for example, if a user opens a locale file with an editor that replaces automatically #160 by #32).

Or, as you do, you can use a regular expression with wildcard character ".", but users have to know regular expressions.

Nothing really difficult, just be meticulous

titan99 wrote:for translation of addons use addons because in French greffons is medical world.

Not only !

According to this link and other dictionnaries it's also used as a botanic term ; and in the computer science area for "plugin" and this is quite the same as we call here "add-on".

Add-on is not a french word at all. According to this site, the word "compagnon" should be used.

Best regards.

As we used to say in France : "if ne faut pas être plus royaliste que le roi" a language evolves, and enriches itself with others tongues. In France, we used without complex words "plug-in" and "add-on", because there's no translation. For some expressions, imho, I think it's better to let english terms that will be understood by more people.

Some current examples :
Parking is used in France
C'est le fun (it's funny) or appuier sur les brake (to brake) is used in Québec
Rendez-vous is used in US and GB

Every language borrows expressions from others, that's why our languages are living languages, in opposition to lost languages

I know, I know Exerladan

This was an academic answer to the "only a medical word" comment which is not correct.

The goal here is , I think, that everybody knows what we are talking about when refering to it.

I am working on german translation right now. Just to check: german special character have to be coded in UTF-8 and not html, right???

Yes, the locale files (all files really) are encoded utf-8 now.

Make sure your text editor saves them in UTF-8.