Okay, we're sorry
The installer for Roster states there is a frFR localization of Roster

Truth is, there is none...
The story goes like this

• We were planning to include it
• It was almost done
• The site got hacked
• We lost the translation file

So, we are asking for help on this

Eventually, we'll be asking for permenant french translators, but that's for another day...

The WoWRoster Dev Team requests that all submissions be posted here

Attatched is the latest version of enUS.php and frFR.php for Roster 1.7.1
Warning: Do NOT use these files in WoWRoster 1.7.0

Most of the text in these files must be UTF-8 encoded
This means all the facy text (Well, fancy to us English speakers) must be converted

Here is an example from the frFR.php file

Code: Select all

'BRDp' => array('Key-Only','BRDp' => 'Clé de la prison|15545'),
'BRDs' => array('Parts','BRDs' => 'Clé de Shadowforge|2966','Ironfel|9673'),
'HT' => array('Key-Only','HT' => 'Clé en croissant|35607'), 

I think this file : http://www.wowroster.net/Forums/viewtopic/t=161.html was a good start for translation in french. But it's not complete

There are some areas that are not encoded correctly

Most of that file uses html encoded characters while very little of it uses utf-8 encoded characters

This would need to be fixed

i'm try to working on it

i have succesfuly translate all instance key (with Eternal Quintessence as working)

But i have a problem for warlock and i don't know why ...

Hi, I've just made a correction of the french localization in http://www.wowroster.net/Forums/viewtopic/t=161.html

I will tranlsate the v1.7.1 (if you agree with) when I return from holidays in 10 days

I suggest some improvements too (may be there are already in v1.7.1, I've not installed yet 1.7.1) in http://www.wowroster.net/Forums/viewtopic/t=161.html

Many many many thanks to Exerladan (and wowodo too)
Just upload the file and check the two thinks or three that doesn't work and it's rocks!!!
instance Key are correct
Reput addon works with accent
Resolved problems on displayed abilities of certain caracter (warlock)
Great improvement on general performance
Great job

/kiss : )

Hello

Found a bug/problem ? with the bonus item on character stats

Every item create a line with is own bonus, and there is no
summary for bonuses.

Sorry i'm too dummy on php code

Here an example:
http://guilde.le.sablier.free.fr/roster ... =character

Hi

I don't understand why you ask us to have everything in UTF-8... UTF-8 encoded is good for all db-related names but for display information why do we have to use UTF-8?

You are right, but do you know for sure what is for db matching/use and whats for display only?
I don't, and I spend hours looking at roster code

It's just "safer" this way

That's a better information...

Just for your informatio, I translated everything and had a look at my installed roster after each block translation. Just to be sure that nothing was altered.

Hello.

Bump for a bug/problem ? with the bonus item on character stats

Every item create a line with is own bonus, and there is no
summary for bonuses.

Sorry i'm too dummy on php code...

Is anybody got a French Roster that character stats works ????


Here an example:
http://guilde.le.sablier.free.fr/roster ... =character

Regards.

Hello.

My 2 cts to a french installation of the super wow roster..

http://www.wowroster.net/Forums/viewtop ... .html#3991

Ansgar wrote:Hi

I don't understand why you ask us to have everything in UTF-8... UTF-8 encoded is good for all db-related names but for display information why do we have to use UTF-8?

Simply because, in english, you don't have any accent, so any encoding equals to another, but in german or in french you have special characters. Let me show by an example :
Spallières (the french word for spauldrons) contains the "é" character (an "e acute"). In you don't use UTF8 as DB encoding, the user has to type é and can't type e character instead when he searches (the accentued characters can be typed generally with a key combination, that's not really simple).
It would'nt be really a problem if the translations were all the sames, but sometimes names have the special charcters and sometimes haven't, like Wildheart's set translations : you found Coeur-sauvage and Cœur-sauvage (note the oe and the œ).

Another problem is the characters that are not in latin1 or ascii (such as € character for example) : the database can simply fault the SQL request, because it didn't recognize the character as valid.

I have modified the sources files of my own version for the DB encoding, and I can share it, it reprensents really 10 lines. I have to write a script for upgrading latin1 to utf8 db, I will do it today.

Well, we could make the database use utf-8 encoding, but then all users with mysql lower than 4.1 couldn't use roster since it isn't supported below that version

zanix wrote:Well, we could make the database use utf-8 encoding, but then all users with mysql lower than 4.1 couldn't use roster since it isn't supported below that version

Well, even in debian sarge (I pick this example because it's well known that debian releases very lately its packages), you find packages for mysql 4.1

The official roster requirements are :

Wiki wrote:MySQL 4.1.x or higher

3.x may be possible but is unsupported

and the backward compatibility isn't supported

I can't test modifications for utf8 on 4.0 or lower (my distro are too new), but imho, it may work, only queries about character encoding will fail, and database will respond in default character encoding.