Problems translating faqguide [Fwd: Re: xml2po]

[Sean Wheller]

On Wednesday 14 September 2005 16:42, Matthew East wrote:
> On Wed, 2005-09-14 at 16:31 +0200, Sean Wheller wrote:
> > 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.
>
> Actually, I had tested xml2po -e on the old xml to be found in
> branches/breezy, which looked like it worked ok. So have you done
> something to the faqguide in trunk? It would be really nice if you let
> us know what has been done.

The answer is in patches 1786:1787
1786 = mk valid and well-formed  for xml2pot
1787 = xml2pot *.xml

> I don't totally follow this: surely all strings will need to be
> translated under both solutions? If there are identical strings, then
> these show up only once in Rosetta.

The single file would be created by expanding XInclude and External Entity 
refs  to their value. This would mean, for example, that External Entities 
such as &feedback; will be expand in full value and therefore translators 
will translate the text. Now if the xml-instance that is the value of 
&feedback; is used elsewhere, they translation will be done all over again 
for the same strings. Better would be to translate feedback.xml and keep the 
External Entity refs in the POT files. That way when you reassemble to XML 
you will still have &feedback; in your language specific xml instances.

Naturally, you will want to have i18n for the feedback.xml

>
> > > > 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.

See trunk/i18n.sh for example of msgmerge usage

Then diff old pot and new pot to see what's 'appening and decide what should 
be done.

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