Firefox translations status in Natty

[David Planella]

El dt 18 de 01 de 2011 a les 16:53 +0100, en/na Ask Hjorth Larsen va
escriure:
> Hi David
> 
> On Tue, Jan 18, 2011 at 4:00 PM, David Planella
> <david.planella at ubuntu.com> wrote:
> > Hi translators,
> >
> > I thought I'd give you a quick update on the Firefox translations in
> > Natty:
> >
> > Due to a change in the way upstream packages translations, those of you
> > who are testing Natty will have noticed that Firefox is in English only.
> >
> > During the Canonical Platform Rally last week we worked on fixing this
> > to import translations into Launchpad and put them in the language
> > packs. Special thanks go to Danilo on his great work on modifying po2xpi
> > for the new format [1], Chris Coulson for getting the Firefox en-US
> > template to build automatically and Martin Pitt to integrate the po2xpi
> > changes into langpack-o-matic [2], which will allow to build the Firefox
> > translations and put them into the language packs.
> >
> > If all goes well, most of the translations should be available after
> > Alpha-2 on February the 3rd.
> >
> >      * Once they are available, please make sure to test them well and
> >        report any bugs you might find.
> >
> > In addition to that, while importing some upstream translations we
> > noticed a couple of bugs. These need to be fixed upstream, so I'd like
> > to ask the teams affected to coordinate with upstream to fix them.
> >
> > Here are the bugs in Launchpad with upstream links:
> >
> > Brazilian Portuguese:
> > https://bugs.launchpad.net/firefox/+bug/704210
> >
> > Norwegian Nynorsk:
> > https://bugs.launchpad.net/firefox/+bug/704202
> >
> > Oriya:
> > https://bugs.launchpad.net/firefox/+bug/704205
> >
> > Telugu:
> > https://bugs.launchpad.net/firefox/+bug/704208
> >
> > Tamil:
> > https://bugs.launchpad.net/firefox/+bug/704211
> >
> >
> >      * Please work with the upstream teams to get these fixed. In the
> >        meantime, you can fix them in the xpi files for Ubuntu [3] and
> >        upload them.
> >
> > Finally, just a note to say that we imported the translations from [4].
> > I know some teams haven't got their translations in there yet, only on
> > Mercurial. We've only imported the official ones for now. If you need
> > your non-official translation to get imported, let us know and we'll see
> > if we can figure something out.
> >
> > Regards,
> > David.
> >
> > [1] https://code.launchpad.net/~mozillateam/po2xpi/trunk
> > [2] https://launchpad.net/langpack-o-matic
> > [3] https://translations.launchpad.net/ubuntu/natty/+source/firefox/+imports?field.filter_status=FAILED&field.filter_extension=all
> > [4] http://releases.mozilla.org/pub/mozilla.org/firefox/releases/4.0b9/linux-i686/
> >
> > --
> > David Planella
> > Ubuntu Translations Coordinator
> > www.ubuntu.com / www.davidplanella.wordpress.com
> > www.identi.ca/dplanella / www.twitter.com/dplanella
> 
> Are there any ubuntu-specific changes to the firefox templates?  I
> notice that we have a few untranslated strings, and this is unusual
> because the Danish upstream Mozilla translators tend to keep it at
> 100%.
> 
> Regards
> Ask

Hi Ask,

I don't think we do any changes to Firefox upstream strings in Ubuntu.

I too noticed that there were 8 untranslated strings in the Catalan
translation in Launchpad, whereas upstream was 100% translated.

From investigation, it simply seems that some of the strings present in
the original template (in the case of Firefox, this is the en-US.xpi
file) are often left out in the translations. Thus they are then
(correctly) shown as untranslated in Launchpad.

An example:

https://translations.launchpad.net/ubuntu/natty/+source/firefox/+pots/firefox/ca/4/+translate

Here you see that the string comes from the
"browser.search.order.3=Bing" string in the original template, in the
browser-region/region.properties file.

However, in upstream the "browser.search.order.3" string was left out
(only "browser.search.order.1" and "browser.search.order.2" were
specified):

http://hg.mozilla.org/l10n-central/ca/file/9308e2d49a41/browser/chrome/browser-region/region.properties#l10

Since the original template has a "browser.search.order.3" string,
Launchpad expects the translation to have it (as it is in the case of PO
files), and fills it with the default value.

I'm not sure what the best solution is here, in case we want to leave
them unspecified. I guess we could use an empty string as a translation,
but I'm not sure if .properties files are valid with empty strings.

Does anyone with experience in Firefox translations know more?

Regards,
David.

-- 
David Planella
Ubuntu Translations Coordinator
www.ubuntu.com / www.davidplanella.wordpress.com
www.identi.ca/dplanella / www.twitter.com/dplanella
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/ubuntu-translators/attachments/20110120/6325363c/attachment.sig>