Localization - almost there

by **sturmy** » Sun Sep 03, 2006 2:29 pm

Hi,

the addon works like magic, however content.js is a JS file (doh) that is enUS localized only. This is the only drawback, as the queries in the DB return the (localized) talent names and talent tree names.

Instead of hard-coding (which will require an update of the addon at every class change of Blizz or event for BC), do you think you could build the combo boxes automatically? Maybe taking example on how the char.php formats the talent trees?

Otherwise we'll have to provide translated spell names for each and every locale.

For the moment, I translated to my locale the content.js for class names & talent trees. My guildmates being happy like that, but that would be a massive improvement IMHO!

Cheers!

by **Nenaisu** » Sun Sep 03, 2006 9:12 pm

If you need german talents I have already gone throu the work

look at workaround threat http://www.wowroster.net/Forums/viewtopic/t=1051.html and have changed the rouge talents to the new 1.12 talents I hope.

Nenaisu

by **DreadPickle** » Mon Sep 04, 2006 7:37 am

sturmy, that is my primary goal right now as I've just done a lot of small upgrades and fixes in th elatest release.

If anyone wants to help with localization of anything, I'd greatly appreciate it.

by **sturmy** » Mon Sep 04, 2006 7:42 am

Glad to help with frFR!

by **DreadPickle** » Tue Sep 05, 2006 4:10 am

Thanks a bunch! I've added all the rest of the content items to the latest.

by **sturmy** » Tue Sep 05, 2006 10:54 am

Beware! the accentuated characters (at least in the frFR) in the updated zip for talented seem not to be stored in UTF-8. I had to do a search and replace to get this up & running.

Symptoms: all combo boxes empty in Talented.

*Edit* in case this is useful, the result of the search & replace I did ;-)

*Edit2* upon testing it seems I've picked the wrong utf8 match table. Disregard the attachment & wait for the auto-generated lists (see post below ;-) )

by **DreadPickle** » Tue Sep 05, 2006 5:16 pm

sturmy wrote:... seem not to be stored in UTF-8.

Oops Since the accents were showing up fine in my editor I didn't chack how it was saved. :oops:

I'll update them again and then I hope to be done with localizing this part. I think I've figured out how to generate the content.js from database queries in a php file! I'll have an update in a day or so.

In other localization news, I've localized a bit more of the display. This is a bit smaller so it will be easier to maintain.

by **sturmy** » Tue Sep 05, 2006 9:33 pm

That would be GRAND! Looking forward to the update!

by **DreadPickle** » Wed Sep 06, 2006 5:21 am

Try it now. The latest version populates the lists from the database. this will provide 3 major benefits:

1) List automatically pulls shaman/paladin depending which is there. After BC expansion it will pull both with no extra code.

2) Talent reviews are automatically updated on th enext upload after the patch. No need to recode contents.js; e.g. Rogues @ 1.1.2

3) Localization should be automatic as it pulls stored DB values.

Monir benefit: no more misspellings or odd translations - everything will be Blizzard's fault! :grin:

by **sturmy** » Wed Sep 06, 2006 10:29 am

Works like a charm! Good job Dread!