Problems translating faqguide [Fwd: Re: xml2po]

[Sean Wheller]

On Wednesday 14 September 2005 16:22, Matthew East wrote:
> Yes I think so, although I have no way to tell really. As far as I can
> see, making the pot using the gnome-doc-utils package with the -e switch
> also solves the problem nicely. 

Yes, now that you have valid and well-formed xml you will be able to use gnome 
tools in the same way that you used the kde sdk.

> However, I still think that we should 
> proceed with turning the faqguide into one single .xml file, because the
> translated xml files will be single files, so we might as well have the
> original in a single file too. It will also allow us to check that the
> whole document is valid xml.

No need. The XInclude already makes it a single xml-instance. If you feel more 
comfortable then just use xmllint and output stdout to a file.

With pwd faqguide/

xmllint --xinclude --noent --postvalid faqguide.xml > faqguide.xml.new

That will output an xml instance where all xincludes and entities are expanded 
and resolved.

Personally I don't think you want to send that for translation as your 
translators will be translating more strings than is required.

>
> > If my contribution solves the problem, then your objective has been
> > achieved and people can go on translating.
>
> I'm not sure at the moment whether uploading a pot made with a
> completely different tool will allow the translators to go on
> translating. I am concerned to minimise any risk of lost translations,
> and if using the same utility (gnome-doc-utils) can help with this, then
> I am keen to do it. Even if we upload a new pot, made with xml2po -e, I
> am not yet sure how many translations will be lost. Probably, a lot. :(

Perhaps, perhaps not. test it first. Use msgmerge.

Hint: I documented the the old process in shell. See trunk/i18n.sh

Hope this helps,


-- 
Sean Wheller
Technical Author
sean at inwords.co.za
084-854-9408
http://www.inwords.co.za
Registered Linux User #375355