[opensuse-translation] Re: translating the openSUSE manuals
Hi! For the translation of the opensuse manuals, there is any .po repository or the process is download the source, translate the .xml files (using xml2po) convert to .xml again (po2xml), create a build service account and package the opensuse manuals in your language to distribute it? If this is the process, is that hard to do something like KDE does? (using a svn repository for both the gui and doc strings) Another question: anyone knows where I find the openSUSE related man pages (for example, the zypper manual page) Regards, Luiz Fernando Ranghetti -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Hi Luiz, On Mittwoch 15 Oktober 2008, ¡ElCheVive! wrote:
For the translation of the opensuse manuals, there is any .po repository or the process is download the source, translate the .xml files (using xml2po) convert to .xml again (po2xml), create a build service account and package the opensuse manuals in your language to distribute it? If this is the process, is that hard to do something like KDE does? (using a svn repository for both the gui and doc strings)
We did it in the past too but have mixed feelings. It works -- somehow. If I recall it correctly, one of the problems was that the PO files are not really made for XML-based content. I think, it is a good method for translating GUI-based strings where you have a 1 to 1 translation. However, for books, this 1 to 1 relation is not always the case. Sometimes a paragraph fits only for an English text and it has to be removed in, say, a German translation. Or you have to insert an additional explanation in the translation. Either way, it is very troublesome to overcome this issue. I assume, the KDE documentation avoids more or less things that destroys this relation (maybe I'm wrong). The nature of our books did not allow this, so we had to change it as it was too cumbersome.
Another question: anyone knows where I find the openSUSE related man pages (for example, the zypper manual page)
Probably here: http://svn.opensuse.org/svn/zypp/trunk/zypper/doc/ http://en.opensuse.org/Zypper/Development Tom -- Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX GmbH >o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team http://developer.novell.com/wiki/index.php/Lessons_for_Lizards http://lizards.opensuse.org/author/thomas-schraitle/ --------------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wednesday, 2008-10-15 at 08:35 +0200, Thomas Schraitle wrote:
For the translation of the opensuse manuals, there is any .po repository or the process is download the source, translate the .xml files (using xml2po) convert to .xml again (po2xml), create a build service account and package the opensuse manuals in your language to distribute it? If this is the process, is that hard to do something like KDE does? (using a svn repository for both the gui and doc strings)
We did it in the past too but have mixed feelings. It works -- somehow. If I recall it correctly, one of the problems was that the PO files are not really made for XML-based content. I think, it is a good method for translating GUI-based strings where you have a 1 to 1 translation.
However, for books, this 1 to 1 relation is not always the case. Sometimes a paragraph fits only for an English text and it has to be removed in, say, a German translation. Or you have to insert an additional explanation in the translation. Either way, it is very troublesome to overcome this issue.
I had the feeling that would be so. What do you use to edit the documentation? Where can we find the docs, in source format, so that we can estimate the difficulty? I have attempted on occasion to translate xml docs, and found it too difficult because of the xml impedimenta. I don't like it, it feels like programesse. I much prefer a WYMIWYG, like lyX.
I assume, the KDE documentation avoids more or less things that destroys this relation (maybe I'm wrong). The nature of our books did not allow this, so we had to change it as it was too cumbersome.
Another question: anyone knows where I find the openSUSE related man pages (for example, the zypper manual page)
Probably here: http://svn.opensuse.org/svn/zypp/trunk/zypper/doc/ http://en.opensuse.org/Zypper/Development
You could consider creating a branch for us, under the translation "trunk", so that we can have a go at translating all mans. Not to mention that there is no GUI to editing man pages. Or no good, updated, one (plus the utf/latin issue). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkj1yTUACgkQtTMYHG2NR9UfJACfdNDD3GnzfCj86SR2OuyEEPh3 ESAAn2sPmpyBqV5fEXrCkxTEMcISFb/+ =dgHo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
"Carlos E. R."
Where can we find the docs, in source format, so that we can estimate the difficulty?
Source are part of the opensuse-manual_en package that exists in Factory of the OBS: https://build.opensuse.org/package/show?package=opensuse-manual_en&project=openSUSE%3AFactory I sync it approx. every two weeks or often during beta and RC releases.
I have attempted on occasion to translate xml docs, and found it too difficult because of the xml impedimenta. I don't like it, it feels like programesse. I much prefer a WYMIWYG, like lyX.
I'm not sure whether lyx supports DocBook XML, but there are wysiwyg-like XML editors. For what's worth, we can arrange a directory in the suse-i18n SVN where you can add those files for translation. If wanted you can also try to convert the XML files to the PO file format. Another option would be to try OmegaT. You are a little bit on your own for the moment, because I do not have that much time right now.
Probably here: http://svn.opensuse.org/svn/zypp/trunk/zypper/doc/ http://en.opensuse.org/Zypper/Development
You could consider creating a branch for us, under the translation "trunk", so that we can have a go at translating all mans.
That would be the easy part. Integrating into the package is the tough part, but Jan would probably help you.
Not to mention that there is no GUI to editing man pages. Or no good, updated, one (plus the utf/latin issue).
Translating man pages is rather tedious. Maybe, you better off translating the wiki pages: http://en.opensuse.org/Zypper/ and the sub-pages, of course. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Hi, On Mittwoch 15 Oktober 2008, Carlos E. R. wrote:
[...] What do you use to edit the documentation?
Depends. Sometimes Emacs, sometimes oXygen. For some time now, the last one, as it has some pretty nice features. However, oXygen is commercial.
Where can we find the docs, in source format, so that we can estimate the difficulty?
See Karl's answer.
I have attempted on occasion to translate xml docs, and found it too difficult because of the xml impedimenta. I don't like it, it feels like programesse. I much prefer a WYMIWYG, like lyX.
Well, there is an spec for these things, it is called XLIFF[1,2]. I think, I saw a respective editor somewhere but can't remember where it was.
[...]
Probably here: http://svn.opensuse.org/svn/zypp/trunk/zypper/doc/ http://en.opensuse.org/Zypper/Development
You could consider creating a branch for us, under the translation "trunk", so that we can have a go at translating all mans.
I don't have any admin permissions to do so. Maybe talk to Peter Poeml or Adrian.
Not to mention that there is no GUI to editing man pages. Or no good, updated, one (plus the utf/latin issue).
I usually prefer to edit manpages all together and write it in DocBook XML. This way, I can transform it to whatever format I like (including manpages). I did that for scout some month ago. Tom ---- References [1] http://docs.oasis-open.org/xliff/xliff-core/xliff-core.html [2]http://developers.sun.com/dev/gadc/technicalpublications/articles/xliff.html -- Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX GmbH >o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team http://developer.novell.com/wiki/index.php/Lessons_for_Lizards http://lizards.opensuse.org/author/thomas-schraitle/ --------------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Hi,
I usually prefer to edit manpages all together and write it in DocBook XML.
I meant to say: I usually prefer to avoid editing manpages all together. :) Tom -- Thomas Schraitle ---------------------------------------------------------------------- SUSE LINUX GmbH >o) Documentation Specialist Maxfeldstrasse 5 /\\ 90409 Nuernberg _\_v http://en.opensuse.org/Documentation_Team http://developer.novell.com/wiki/index.php/Lessons_for_Lizards http://lizards.opensuse.org/author/thomas-schraitle/ --------------------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
participants (4)
-
Carlos E. R. -
Karl Eichwalder -
Thomas Schraitle -
¡ElCheVive!