Thanks!
I've been playing around with xml2po and the pot file to see how it works. It will be really great to get to the point that we can use it in a sensible way.
I think the things that need to happen first, though, are getting a sensible TOC worked out and then populating an xml file with the new TOC, then copying over the existing contents into the correct places.
Elisa and I have been working on the Wiki page for the TOC. Can we work on getting a somewhat final TOC together? As soon as it's done, I'll be happy to put together the new xml skeleton so we can start adding the text. Then we can work on the content a lot more easily. (By the way, I've just checked out Gtranslator and Kbabel, both of which are very nice for doing the translations. I can't wait to get to put them to good use!)
However, if there is opposition do doing all this right now, please just tell me and I'll work on something different.
JF
Colin Marquardt wrote:
Hi,
I just changed inkscapeUTFfr.xml so that xml2po is happy with it. I had to change a lot of <para></para> or <para /> to <para>some text</para> (I used FIXME instead of "some text"), since xml2po doesn't seem to like such empty tags. (Not just paras, also terms and titles etc.)
Doing xmllint --valid --noout inkscapeUTFfr.xml still complains about some issues though.
Oh, and I also changed "<para >" to "<para>" for cosmetic reasons.
If you want to try creating a pot file youself, do:
xml2po --output=inkscape_user_manual_orig_fr.pot inkscapeUTFfr.xml
Cheers Colin
This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Inkscape-docs mailing list Inkscape-docs@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-docs