Internationalization

Menu system translated.
On to context information / tooltips for buttons and such.
Then forward with the descriptions that show up in the status bar.
Screenshots available if someone has some hosting.(Menus only at the moment).
Current code also available if requested. Otherwise, I'm not going to release until, A) people come together on it and need the code changes. OR first version is ready for testing.

Only one known problem at the moment...the \"recent files\" feature under the main File menu was disabled to get the gettext feature to function properly with the way the menu system was written. This isn't a key issue, as such this will be resolved last. Getting translations done is far more important.

Is anyone working on the documentation?


-Jason

Still working on this, it hasn't been forgotten. However, you know how it is when things come up that involve making money and sadly we must have this money to survive. Due to this, the effort is ongoing but at a slower pace than I originally intended. After the current contract work is over things should pick up a bit.

Is anyone truly interested in this being done though? I don't expect the community for this type of software to be as large as... say the Linux Kernel community. Though I was expecting some actual input from members of this site.

Till next time...

-Jason

Hi,

Thanks a lot for all your efforts!

I will be happy to contribute some of my time for the work, but I dont' know french. Could you please let me know if there is something I can help with?

Can I get a patch for all the work done so far please? My email address is This email address is being protected from spambots. You need JavaScript enabled to view it..


Regards,

Venkat

Hello,

I am willing to work on some translations of the Code-Aster User Manuals if somebody can give me the MS-Word or OpenOffice format documents.

I have been in touch with Mathieu at the Code-Aster team and I translated one document into english & sent it back to him. I hope to translate some more as I use them. My knowledge of French is rudimentary, but I hope to get better at it as time goes by. Hopefully these will be posted at \"www.code-aster.org/utilisation/non-french.php\";. I am waiting for \"U4.21.01-H1 LIRE_MAILLAGE operator\" to get posted on the website as soon as somebody at Code-Aster team has reviewed it. Yes, I translated it (aka ks3597). If somebody is willing to help, please speak up!

JMB

Hello,

I am willing to work on some translations of the Code-Aster User Manuals if somebody can give me the MS-Word or OpenOffice format documents.

I have been in touch with Mathieu at the Code-Aster team and I translated one document into english & sent it back to him. I hope to translate some more as I use them. My knowledge of French is rudimentary, but I hope to get better at it as time goes by. Hopefully these will be posted at \"www.code-aster.org/utilisation/non-french.php\";. I am waiting for \"U4.21.01-H1 LIRE_MAILLAGE operator\" to get posted on the website as soon as somebody at Code-Aster team has reviewed it. Yes, I translated it (aka ks3597). If somebody is willing to help, please speak up!

JMB

@Venkat - Let me cobble together a few more basic things and I'll see what I can send you. If you've used gettext before with a programming language, you'll know what needs to be done. If not, it is simply a matter of finding the strings to be translated in the code, and wrapping them with the _() function.

For example -
[code:1]
self.but_val = Button(self.frame_valeur, text =\"Valider\", command= self.Choisir)
[/code:1]

would become
[code:1]
self.but_val = Button(self.frame_valeur, text=_(\"Valider\"«»), command= self.Choisir)
[/code:1]
*The above is lifted straight from Eficas, file \"uniqueassdpanel.py\" line 114

Obviously there are a LOT of strings that need to be wrapped.

@ JMB - I saw the translation on the site, in the pending status I do believe.
I don't have the docs in either format, though I am curious about something. Exactly how many doc's are left that need translations. ( Please no one bite my head off for not knowing, I haven't gone through every little thing about CA yet)

@Everyone - Noticed something interesting today ( yes, I actually worked on it a bit today). As we know in prefs.py there is the lang=\"fr\". This specifies the language for certain tools. If no one knew this, you can change it to lang=\"ang\" and have some things regarding homard in english.
Now, how is this interesting you ask? Allow me to explain.

Using you favorite python editor open the file \"cata.py\" under \"RootAster/outils/eficas-1.9.2/Aster/Cata/cataSTA8/\" and scroll down to line 1,851. You should now be looking at \"AFFE_CARA_ELEM=OPER.....\", inside this you'll see the 'fr' in reference to the lang=\"fr\" found in prefs.py. If you add

[code:1]ang=\"this is my text\", [/code:1]

between the 'fr=' and the 'reentrant=' you'll get the english text inside the status bar when you mouseover the phrase 'AFFE_CARA_ELEM' inside of Eficas as opposed to the french one. (assuming you changed lang='fr' to lang='ang' in prefs)

The only languages currently supported (from what I can find in the code) are 'fr','ang', and 'ou'.
So the question is... which would be better? For this \"segment\" of the application should we extend and use the lang=\"whatever\" ability and maintain two translations for each language (internal using lang=\"\" and other GUI using gettext), OR, should we just use gettext?
Obviously, using gettext would make it easier and much quicker to add yet other languages. There would be templates, and someone would only have to touch the *.po file. Using the \"hybrid\" method, the code would have to be constantly updated and merged, becoming an issue. Obviously, I support wrapping the \"fr=' ' \" with gettext.
What do you guys think?

For those wanting to contact me directly, write me at [ depthcharge _at_ cox.net ]. Please include \"CAELinux\",\"Code_Aster\", or \"Eficas Suggestions\" somewhere in the subject line so you will not be auto-trashed.

Later-

-Jason