Translation and language parameter

[Bizzz]

After days on translation in french, I think I have discovered a bug with the language parameter into editor.

I wanted to translate "Toggle HTML source" button value in french and when searching this text I found a /var/www/wiki.../editor/lang directory containing 27 language files, including a french one (fr.js)!

But when editing a page, the button displays "Toggle HTML source" and not the correct french value contained into fr.js, "Afficher / Masquer code source".
The value displayed come from editor/htmlarea.js file!!! Is it normal?

I have tried to modify this line $wgLanguageCode= 'fr'; contained into includes/DefaultSettings.php, but no visible change occurs.

How to configure a language for correctly use the existing language strings?

May be your answer will also correct the bad display of french date actually displayed in 2 different forms, depending on screen displayed...

[Bizzz]

Another problem with date displayed in a foreign language.
When you invite a guest for a page, you can choose the ending date for this.
The javascript Wigdit used for select this date is Datepicker.
I never had french labels displayed into this popup : always US labels!!!

I tried many corrections, without success :
force french language into includes/DefaultSettings.php
force french langage into skins/common/datepicker/datepicker.js with the following line
(after existing "datePicker.languageinfo = ..." lines)
datePicker.languageinfo = 'fr';

Datepicker use the browser language, and this is french on my PC.
To confirm the problem is on Dekiwiki side, I've tried the inline Datepicker demo (http://www.frequency-decoder.com/demo/date-picker-v2/), and all is fine, the french labels for monthes and days are correct (all in french).

What's wrong?

[Bizzz]

Did somebody already translate this software completely or am I the only one to encounter these problems?

[royk]

Hey, sorry for the late reply.

The editor is actually a modification of Xinha, and it has its own localization. The localization will depend on which plugin you're using.

As for the datepicker, what is the exact problem you're having? Is the whole localization not working or just parts?

I know that our datepicker was integrated with our product, so we might not have kept up with the localization integration, but I can take a look at this tomorrow and let you know more in detail.

[Bizzz]

OK for the editor with its own localization. But I've not anderstood the plugin solution. What is the best solution to have the french text expected :
- configuration of 'fr' language somewhere (but where exactly?)
- translation of US texts with french texts, if language parameter is too hard to configure.

For Datepicker, the problem is only into the Datepicker window. All my wiki is now in french, except monthes and days displayed into Datepicker selection window. I have not still translated these US days and monthes because I have seen Datepicker should normally use the browser language (mine is french of course). But as previously written, this parameter is not correctly proceeded with Dekiwiki. Even if I try to force 'fr' into datepicker.js, I continue to have US monthes and days displayed.

[tamax]

Hi Bizzz,
Did you solve the localization issue you encountered in the editor ? Because I'm translating the Wiki into Spanish and I'm facing the same problem :(
Regards,
Maxime.

[royk]

For Datepicker, the problem is only into the Datepicker window. All my wiki is now in french, except monthes and days displayed into Datepicker selection window. I have not still translated these US days and monthes because I have seen Datepicker should normally use the browser language (mine is french of course). But as previously written, this parameter is not correctly proceeded with Dekiwiki. Even if I try to force 'fr' into datepicker.js, I continue to have US monthes and days displayed.

Have you tried simply overwriting /skins/common/datepicker/datepicker.js around lines 58 - 83 to do a manual overwrite of the values?

[Bizzz]

Thank you, Royk!
I wanted to use a more elegant solution (with use of language parameter), but this simple one also works very well ;)