Greetings, I have checked out the release-notes of FC-4 from cvs. Some one suggests me to use xml2po to simplify the translation process. I tried it but it doesn't work. Some xml files are blank, without a root element. Only one of them contains DOCTYPE and xml2po just ignores all the tags in the other files. If I specify *.xml in the command line, xml2po prompts me
Traceback (most recent call last): File "/usr/bin/xml2po", line 716, in ? CurrentXmlMode.preProcessXml(doc,msg) File "/usr/share/xml2po/docbook.py", line 142, in preProcessXml root = doc.getRootElement() File "/usr/lib/python2.4/site-packages/libxml2.py", line 4064, in getRootElement if ret is None:raise treeError('xmlDocGetRootElement() failed') libxml2.treeError: xmlDocGetRootElement() failed
What should I do to generate a proper pot file?
BTW, are there any chinese speakers on this list?
On Thu, 2005-05-26 at 17:49 +0800, Yuan Yijun wrote:
Greetings, I have checked out the release-notes of FC-4 from cvs. Some one suggests me to use xml2po to simplify the translation process. I tried it but it doesn't work. Some xml files are blank, without a root element. Only one of them contains DOCTYPE and xml2po just ignores all the tags in the other files. If I specify *.xml in the command line, xml2po prompts me
Some of the files in CVS are skeleton files, meaning they are there to support content but do not contain content.
They are pulled in to the parent XML file RELEASE-NOTES-en.xml, which has the DOCTYPE header
Traceback (most recent call last): File "/usr/bin/xml2po", line 716, in ? CurrentXmlMode.preProcessXml(doc,msg) File "/usr/share/xml2po/docbook.py", line 142, in preProcessXml root = doc.getRootElement() File "/usr/lib/python2.4/site-packages/libxml2.py", line 4064, in getRootElement if ret is None:raise treeError('xmlDocGetRootElement() failed') libxml2.treeError: xmlDocGetRootElement() failed
What should I do to generate a proper pot file?
I'm not sure. The Makefile.old may help, since it was used previously for i18n.
I don't recommend translating any of the release notes at this stage. They are extremely raw and full of outdated information. They will be completed by 30 May.
In the future, there will be a more direct line from test notes to final notes, all in XML.
You may want to try fedora-i18n-list for help on generating PO files.
- Karsten
On Thu, 2005-05-26 at 17:49 +0800, Yuan Yijun wrote: <snip>
BTW, are there any chinese speakers on this list?
Yeah, I am one :-)
You can find more on fedora-trans-zh_cn@redhat.com
For all translation related matters, fedora-trans-list@redhat.com is a better place to discuss. Currently documentation translation is not in Fedora Translation Project yet, but it will be included once the proper file structures and work procedures are defined.
We'd love to have your suggestions and contributions on how the documentation translation can be effectively handled.
Cheers, Sarah
2005/5/31, Sarah Wang sarahs@redhat.com:
We'd love to have your suggestions and contributions on how the documentation translation can be effectively handled.
Cheers, Sarah
Nice to see you Sarah! I heard of you from Funda Wang[1] who is in charge of Mandriva document translation, then I found your name in almost all documents. :) He suggests to use his scripts in Mandriva cvs[2] in translation process. I will try that later. He always helps us on the fedora forum[3]. The idea of using xml2po is from him, too. The problem in the first post is because there are un-quoted &'s in every xml, making the xml2po confused. His scripts would help.
[1] Funda Wang: fundawang#gmail.com [2] http://cvs.mandriva.com/cgi-bin/cvsweb.cgi/doc/po/ [3] http://www.linuxsir.org/bbs/forumdisplay.php?f=40
-
Karsten Wade -
Sarah Wang -
Yuan Yijun