Re: How use Launchpad translations for translate debian-installer upstreams?

[Marcos Alvarez Costales <marcos.alvarez.costales@gmail.com>]

Ops...
For run :$...

In the same folder:
template.po (Download from upstream)
translated_file.po (Download from Launchpad)

In terminal:
Go to the directory.
python poupdate.py template.pot translated_file.po new_translate_file.po

This will create the new_translate_file.po translated with the strings
found.

Example:
python poupdate.py template.pot installer-po_debian-installer-ast.po
ast.po

It this can be an useful program, maybe I can improve it for more
stable :)


On Wed, 2009-01-07 at 07:30 +0100, Christian Perrier wrote:
> Quoting Arne Goetje (arne@linux.org.tw):
> 
> > Of course you can export those .po files from Rosetta and copy/paste
> > those message strings which are the same in debian. Then you have only
> 
> 
> I'd recommend a more automatic approach:
> 
> - export the PO files from Rosetta --> /tmp/ast-rosetta.po
> - resync them with Debian's POT file in each sublevel:
>   cd <your SVN root>/packages/po
>   cd sublevel1
>   cp /tmp/ast-rosetta.po ast.po
>   msgmerge -U ast.po template.pot
>   msgattrib --no-obsolete ast.po >ast-new.po && mv ast-new.po ast.po
>   
>   <and the same for other sublevels>
> 
> If there's already a translation you can do things slightly
> differently:
> 
>   cd sublevel1
>   msgcat --use-first ast.po /tmp/ast-rosetta.po | \
>     msgattrib --no-obsolete >ast-new.po && mv ast-new.po ast.po
> 
> This will pick strings that are translated in ast-rosetta.po and add
> them in ast.po...only when ast.po didn't have them (or had them fuzzy).
>