Some languages not showing up in Launchpad translations

Bug #1278065 reported by Bernhard Reiter on 2014-02-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Undecided
Unassigned

Bug Description

We're using Launchpad translations for translating Gourmet Recipe Manager (https://translations.launchpad.net/gourmet/). I've only recently noticed that some language variations like Austrian German (de_AT) or Flemish (nl_BE) don't show up there. They must however have been imported at some earlier time, as I can access e.g. Austrian German translations by manually entering the URL https://translations.launchpad.net/gourmet/main/+pots/gourmet/de_AT/+translate -- its translation details reveal that it hasn't just been newly created, but has been present before. Also, if I download the current *.po files, de_AT.po and nl_BE.po are present. I can't expect translators to find out about those "hidden" translations by themselves, which is why there is a report about Flemish idiosyncracies in the standard Dutch translations as apparently a Flemish translator just edited the Dutch translations as obviously he or she wasn't able to find the Flemish translations.

BTW, where does the funky directory structure of the downloaded tarball come from -- is that from the original import (which wasn't done by myself)? Everything is in po/gourmet-xx.po or po/gourmet-xx_YY.po except for mainland Chinese which is in gourmet/zh_CN.po. Trying to upload a new tarball last night failed with a timeout, BTW (maybe because of a slightly different layout with everything in po/xx.po and po/xx_YY.po ?)

Revision history for this message
William Grant (wgrant) wrote :

Many locales aren't hugely different from their parent language, so we recommend that they just inherit the base language's translations. These languages aren't shown by default in Launchpad's web UI. So de_AT should just fall back to de, nl_BE to nl, etc., to avoid having to duplicate translation work for almost indistinguishable locales.

As for the tarball structure, paths are indeed taken from the tarball from which they were originally imported.

Changed in launchpad:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers