Internationalization

Hello Jason or others,

In the interest of making Code-Aster's command file editor EFICAS more usable by English speaking users and following up on the excellent initiative taken up by Jason, I have translated his messages.po file into English. Yes all 5700 lines of it. It may still contain errors from my limited knowledge of French, but it is a start. It is ready for anybody who knows more than I do about the gettext tools for internationalization (i18n).

In doing so I am hoping that somebody will come forward quickly to help in the i18n process for EFICAS & ASTK ... hint, HINT!

Jason: I hope you can use this file in your project at \"codeaster-intl.sourceforge.net/\";. Please see my emails to you at \"cox.net\"

Admin: I have sent this messages.po file to you via ftp transfer.

Regards,
JMB

Work is progressing.......albeit slowly.

I have received your messages_en.po Admin, and am waiting on a response from JMB about his.
As those that follow the threads may know...I've recently moved...and have finally settled in. The @cox.net addresses will not be up much longer... instead use @nc.rr.com
The username is still the same.. 'depthcharge'

As soon as the files are merged in, there will be a new version posted and the sourceforge site updated. The new version will have the french documentation PDF's stripped out of the \"docs\" directory. This should cause the bzipped archive to be around 2.2MB vs 35MB when ready. For now it is still based on Eficas 1.9.2, soon I shall be looking into the latest Eficas/ASTK release.

Later all.
Jason.

Hello \"The Never\",

I have sent the hand translated version of messages.po to you file in a private email. It should have the original French strings intact and therefore useable by gettext. The only things I may have removed are some of the \"# fuzzy\" lines, since I felt confident of the translation in those instances.

Let me know asap how the efforts of Eficas 1.10 are coming along and I can assist with the translation of strings there too. Is there an automated way in the gettext tools to merge an older messages.po file (the one I have sent you from Eficas 1.9.2) with a newer one that will be generated from Eficas 1.10? I am hoping that there is, so I do not have to hand cut & paste all the 2800 or so strings already completed. Hopefully, subsequent releases of Eficas will mean lesser string translations.

Please let me know if you have received my file, because I am not entirely sure that my private emails are reaching you. I had sent a couple of private emails to let you know that the messages.po file was ready for you, but I did not get any replies. You might want to delve into your email system or ISP's restrictions.

Thanks
JMB

Hello \"The Never\",

I have sent the hand translated version of messages.po to you file in a private email. It should have the original French strings intact and therefore useable by gettext. The only things I may have removed are some of the \"# fuzzy\" lines, since I felt confident of the translation in those instances.

Let me know asap how the efforts of Eficas 1.10 are coming along and I can assist with the translation of strings there too. Is there an automated way in the gettext tools to merge an older messages.po file (the one I have sent you from Eficas 1.9.2) with a newer one that will be generated from Eficas 1.10? I am hoping that there is, so I do not have to hand cut & paste all the 2800 or so strings already completed. Hopefully, subsequent releases of Eficas will mean lesser string translations.

Please let me know if you have received my file, because I am not entirely sure that my private emails are reaching you. I had sent a couple of private emails to let you know that the messages.po file was ready for you, but I did not get any replies. You might want to delve into your email system or ISP's restrictions.

Thanks
JMB

Hey all,

The files that Admin and JMB have provided have been dumped into another small release. Those two did a lot of translating! Still more to go though Got some more work to do in various sections of the application, still lacking some strings here and there, but its coming along.

@ JMB

Yeah, I seem to be getting all of your mails as we discussed...via email As for merging...yes, there are merge utilities...so don't worry about that. Each release should include less and less work to be done. With it very soon going into a maintenance mode with very minor updates needed (assuming CA team doesn't create massive changes one day).


Later all
Jason.

Hello everybody who is involved in Code-Aster- Internationalisation. (JMB. TheNever, admin,...)

Summary: I see two fields of activity to improve the support for translation of code-aster.

• A} The information exchange btw. the codeaster-intl. project and potential translators must be improved.
• B} There must be reached higher awareness among relevant groups of potential helpers.

I have a few questions/suggestions:

1. JMB wrote on 5. Sept. 2006 that the admin is waiting for a green light of the Code-Aster-Team to finish the translation of 900 manuals. Has this green light been given in the meantime? If not: Why not? Why do you need it anyway?
2. Did I get it right that the admin has 900 automatically translated manuals in html with broken formulas etc.that need to be cleaned? Do you still need help on this?
3. Where can potential helpers download these files? In what format would you like to have the result? What are the priorities among the 900 docs?
4. Are you aware that people with language skills have not necessarily evenly high computer skills? They might not want to deal with SVN/CVS etc. and just would like check in an overview list (possibly with priorities) which document is not yet under work and then download it. After cleaning up language and formatting they would like to have an easy way to upload it and see the the overview list updated shortly thereafter to avoid redundant work. There must be a one-stop-shop for helpers where they can find all relevant information.
5. I suggest that something like that is implemented in one of the web sites ( CAElinux , codeaster-intl.sourceforge.net ).The Code-Aster-Website itself seems not practical for this due to the reported slowliness of their response.
6. I have 2-3 friends with FEM-background and French language skills that I might be able to motivate to do some translation. But they are not computer geeks. So I must be able to tell them how to get the necessary files in a easy way and to do their work with well known tools without complicated conversion and sending emails forth and back and waiting for replies etc. I am sure you will get much more response of other helpers as well when the helper's \"interface\" is made much more easy.
7. To start with I made a spreadsheet (OpenOffice) with all documents listed on the Code-Aster-Website with the few translations also available there. I counted 856 French docs of which 9 are translated into English and one to German. This list could be the basis of the above mentioned overview list available on a website for all helpers. If you are interested to get it tell me where to send it.
8. Can I help in another way to improve organisation, to raise support or to translate?

Are my suggestions exaggerated? The handful of supporters you are right now don't need more organisation. However, without better organisation you will remain that handful!

I am looking forward to your answers and your opinions.
With best wishes for your project
roleic