Due to the *Jože Klepec *email back in April I started making the documentation translation to Portuguese. This requires indeed a great effort but I believe it to be very useful.
I started by using OmegaT which seems easy enough to understand and the translation memory helps a little... I also like the google translator integration.
However I'm writing not only to share this facts but more to share problems and solutions.
1) I felt the need to change the segmentation settings of OmegaT, more precisely I unset the "Text files segmentation" rule so it became an exception. This rule breaks sentences and paragraphs each time a newline is detected. And geany.txt has newlines in the middle of phrases which was making the translation impossible. Are these newlines in geany.txt required for some kind of text formatting? They seem to limit the width of the text but I doubt this has to be made manually.
2) So far, the setting change in 1) had one negative side effect. I'm unable to have the first table right. The images attached show the 2 types that come out after a series of tries. If I edit the html file to include <br> after each authors name, the table gets equal to the original one. Any thoughts on how to solve this?
3) I've been generating the html by explicitly writing *rst2html -stg --stylesheet=geany.css ./geany.txt geany.html* this is because running *make doc* inside the geany's doc directory gives me the *make: *** No rule to make target `doc'. Stop.* error. I'm not sure but I see that in the doc folder there is only the Makefile.am and Makefile.in, in "my days" the make tool looked for a Makefile file, without any extension. Times change and I probably didn't get the memo :p. (I don't write a makefile in quite some time...) Where's the problem?
4) I noticed 1 typo in geany.txt and made a little change (added a period to a sentence) to have the correct behaviour out of OmegaT. I'm thinking, in the end, of sending a patch with the changes I make. It's the most practical thing right? Or I shouldn't touch geany.txt at all?
Kind Regards, André Glória
Na 20. 06. 2010 15:02, André Glória je pisal:
Due to the /Jože Klepec /email back in April I started making the documentation translation to Portuguese. This requires indeed a great effort but I believe it to be very useful.
I started by using OmegaT which seems easy enough to understand and the translation memory helps a little... I also like the google translator integration.
However I'm writing not only to share this facts but more to share problems and solutions.
- I felt the need to change the segmentation settings of OmegaT, more
precisely I unset the "Text files segmentation" rule so it became an exception. This rule breaks sentences and paragraphs each time a newline is detected. And geany.txt has newlines in the middle of phrases which was making the translation impossible. Are these newlines in geany.txt required for some kind of text formatting? They seem to limit the width of the text but I doubt this has to be made manually.
- So far, the setting change in 1) had one negative side effect. I'm
unable to have the first table right. The images attached show the 2 types that come out after a series of tries. If I edit the html file to include <br> after each authors name, the table gets equal to the original one. Any thoughts on how to solve this?
- I've been generating the html by explicitly writing /rst2html -stg
--stylesheet=geany.css ./geany.txt geany.html/ this is because running /make doc/ inside the geany's doc directory gives me the /make: *** No rule to make target `doc'. Stop./ error. I'm not sure but I see that in the doc folder there is only the Makefile.am and Makefile.in, in "my days" the make tool looked for a Makefile file, without any extension. Times change and I probably didn't get the memo :p. (I don't write a makefile in quite some time...) Where's the problem?
- I noticed 1 typo in geany.txt and made a little change (added a
period to a sentence) to have the correct behaviour out of OmegaT. I'm thinking, in the end, of sending a patch with the changes I make. It's the most practical thing right? Or I shouldn't touch geany.txt at all?
Kind Regards, André Glória
Geany-i18n mailing list Geany-i18n@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-i18n
Hello all!
I'm very happy that someone else started translating this awkward text file. As the matter of fact, I stopped working on this file for now (since Thunderbird 3.0.5 project was finally done with my friends as the date, if you look for one). I even threw away all my work - as I thought it's worthless. Finally, I think that everyone should take into account that we have on Earth around 6700 natural languages (not to count esperanto and all alike). So, we need to agree that essential part or survival guide in help must be left UNTRANSLATED (=in English?). Behind that Survival part/Quick guide (containing quick and very brief guide around menus, plugins and so forth), the it comes all about in your mothers, fathers or another spoken/written language. That's what I think about the help and what it should be like. :)
Cheers, Jože
Hi,
Sorry for the brief answer. Currently to be honest its not my main topic :( Will become better soon I hope.
On Sun, 20 Jun 2010 14:02:12 +0100 André Glória gloria.andre@gmail.com wrote:
- I've been generating the html by explicitly writing *rst2html -stg
--stylesheet=geany.css ./geany.txt geany.html* this is because running *make doc* inside the geany's doc directory gives me the *make: *** No rule to make target `doc'. Stop.* error. I'm not sure but I see that in the doc folder there is only the Makefile.am and Makefile.in, in "my days" the make tool looked for a Makefile file, without any extension. Times change and I probably didn't get the memo :p. (I don't write a makefile in quite some time...) Where's the problem?
IIRc Makefile will be generated but autotools stuff is still some big miracle to me.
- I noticed 1 typo in geany.txt and made a little change (added a
period to a sentence) to have the correct behaviour out of OmegaT. I'm thinking, in the end, of sending a patch with the changes I make. It's the most practical thing right? Or I shouldn't touch geany.txt at all?
Nope. geany.txt can be updated in case of a misspelling, wrong info or just extension by some useful fact. Just send a patch to geany-devel mailing list at best so one of the committers can have a look onto patch and submit it to subversion in case of its a good suggestion.
Cheers, Frank
