Testing the translation and locating the bug source

Redmar redmar at ubuntu-nl.org
Wed Mar 21 20:30:35 UTC 2012


Eagle Burkut schreef op di 20-03-2012 om 18:20 [-0500]:
> Dear All,
> 
> 
> I am an Ubuntu translator. For most of the translatable templates, I
> can test my translation locally, just converting the PO files into MO
> files and copying the files onto a running Ubuntu system.
> Unfortunately, for other couple of templates such as "bootloader",
> "debian-installer", and "ubiquity-???", I can not find an easy way to
> test it locally. The only way I can test them now is I have to
> download the daily build release ISO CD file and install it on a
> virtual environment. When I find a translation bug on screen, I still
> have difficulty locating the bug source (the exact string) in the
> original PO template files.
> 
> 
> Now I have 2 questions:
> 
> 
> (1) Is there any easier way to test the "bootloader",
> "debian-installer", and "ubiquity-???" templates, without downloading
> the daily live CD release?
> 
> 
> (2) When testing the translation, is there any way to locate the
> translation bug in the source template PO files? I mean, for a given
> screen element already translated, how can I know which PO files it
> originally come from and from which lines?

I alway's use 

grep -r "Searchterm" /usr/share/locale*

which returns all .mo files in which 'searchterm' shows up. The name of
the .mo file is usually the same as the template.

Greetings,
Redmar
--
Ubuntu Dutch Translators

> 
> 
> Thanks.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/ubuntu-translators/attachments/20120321/9a99c379/attachment.sig>


More information about the ubuntu-translators mailing list