Problems translating faqguide [Fwd: Re: xml2po]

[Matthew East]

On Wed, 2005-09-14 at 16:48 +0200, Sean Wheller wrote:
> 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

This is a bit cryptic, but if I understand correctly, you have made
important changes to the faqguide code which makes it valid xml. If so,
please merge your changes to the faqguide to branches/breezy so that any
changes will be included in Breezy and the pot file that I'll upload.

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

As I said, identical strings only show up once in Rosetta. If I am
misunderstanding the issue, please tell me.

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

Ok I did "msgmerge -o test pt.po faqguide_new.pot". pt.po was the
portugese translation downloaded from rosetta, and faqguide_new.pot was
the pot I made in branches/breezy using xml2po -e.

"test" reveals that a lot of translations have been kept, although there
are a lot more still to do. So if I did it right, the old translations
should be merging correctly. Tell me if I did something wrong.

M
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/ubuntu-doc/attachments/20050914/79c67645/attachment.pgp>