Dear,
Some time agao, I proposed to coordinate the translation of the documentation of Maxima that is written as texinfo files that are parsed to create the online info, the html info, the manuals ...
In order to store all versions in _one_ file in order to keep the translated documentation synchronized with the original English one, itself kept synchronized with the code, I consider that the usage of the gettext suite is a plus, and therefore I have waited for the proper tools to come up.
I knew that one was in developpement. It is called "PO4A" (see http://po4a.alioth.debian.org/). The support for the texinfo format has recently been added and the developper let me know, as I had asked him. This tools suite allows to parse the original texinfo formatted documents and thereafter use the po tools suite (gtranslate, kbabel or rosetta on launchpad.net or a combinaison of the 3)
I am therefore resuming the translation of Maxima help with the help of the people who will join the effort.
I also propose to use as much material as possible for the functions that have not changed from already translated older version of maxima, from http://michel.gosse.free.fr/documentation/index.html, a work of Michel Gosse.
As soon as possible, I'll proceed with these tools and distribute the tasks for the people who would like to help.
I also propose to coordinate the translation on the wiki of the TRADUC association on http://wiki.traduc.org/Maxima
I hoep with this that Maxima will have another language, French, available usable from within (through its help function) but also some printable documentation.
Thanks,
Nicolas
PS special thanks to Arnaud who pushed me recently to move on and proposed his help.
Afficher les réponses par date
Hi Nicolas,
I knew that one was in developpement. It is called "PO4A" (see http://po4a.alioth.debian.org/). The support for the texinfo format has recently been added and the developper let me know, as I had asked him. This tools suite allows to parse the original texinfo formatted documents and thereafter use the po tools suite (gtranslate, kbabel or rosetta on launchpad.net or a combinaison of the 3)
I took a quick look at po4a and it seems like it could be a useful tool for the Maxima project. However since I am not actually making the translations, I will let the translators on the Maxima team weigh in with their opinions of po4a. If there is general agreement that po4a is useful, we could start using it.
Maybe you can answer some general questions about po4a. How does po4a change the development process? At present: edit .texi files, commit to CVS, execute "make" (to run makeinfo and texi2html). How does that work with po4a in the picture?
Thanks very much for looking into this topic for us.
Robert Dodier
2006/11/9, Robert Dodier robert.dodier@gmail.com:
I took a quick look at po4a and it seems like it could be a useful tool for the Maxima project. However since I am not actually making the translations, I will let the translators on the Maxima team weigh in with their opinions of po4a. If there is general agreement that po4a is useful, we could start using it.
Maybe you can answer some general questions about po4a. How does po4a change the development process? At present: edit .texi files, commit to CVS, execute "make" (to run makeinfo and texi2html). How does that work with po4a in the picture?
Thanks very much for looking into this topic for us.
I will and let the maxima mailing list know about my results
THanks,
Nicolas