Re: Doc Translations



Kaixo!

On Wed, Sep 08, 2004 at 11:50:12PM +0200, Danilo Šegan wrote:

> xml2po is result of what I consider best practice for translations.
>   xml2po C/planner-manual.xml > planner-manual.pot
>   xml2po -p es.po -o es/planner-manual.xml C/planner-manual.xml

It seems much easier to use than XML mode of intltools.

A question however; how are handled the useless formating of XML
source?

That is one of the bad things I've seen so far on XML<->po converters;
when you add \n or spaces or tabs to the source XML, it changes
the msgid on the po files, breaking the translations; while addign
extra blank space to XML source has no change in meaning; imho the
XML->po converter should simply ignore linebreaks and extra space
(and then, when converting from po to XML, the text passed trough
something like "par" to nicely format it for people liking to read XML
directly...)
 
> Next time C/planner-manual.xml changes, you'd sync (gettextism is
> "merge") your es.po first:
> 
>   xml2po -u es.po C/planner-manual.xml

would there be a difference if merging with *.pot?

   xml2po C/planner-manual.xml > planner-manual.pot
   cp es.po es.po.old
   msgmerge es.po.old planner-manual.pot > es.po



-- 
Ki ça vos våye bén,
Pablo Saratxaga

http://chanae.walon.org/pablo/		PGP Key available, key ID: 0xD9B85466
[you can write me in Walloon, Spanish, French, English, Catalan or Esperanto]
[min povas skribi en valona, esperanta, angla aux latinidaj lingvoj]

Attachment: pgpBBlUtQQkWp.pgp
Description: PGP signature



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]