Comment 3 for bug 421441

У нед, 30. 08 2009. у 21:23 +0000, Bruno Patri пише:
> I guess that 95% of Ubuntu packages doesn't have Ubuntu specific
> strings.

And that's exactly the problem: you have to *guess* which packages do
and which don't have Ubuntu specific translations. There's no point
trying to fix this problem before we fix that first.

To prove a case in point: metacity, which is brought up as an example,
has the following patch in Ubuntu package:

- workspace_names[i] = g_strdup_printf (_("Workspace %d"), i + 1);
+ workspace_names[i] = g_strdup_printf (_("Desk %d"), i + 1);

(and a bunch of other string changes doing s/workspace/desk/)

Practically, anyone's guess is useless until we come up with a mechanism
to figure these out automatically.

> What is on Launchpad translations is mostly a fork pf upstream
> translations.

Let's get some facts straight first: Ubuntu includes *forks* of upstream
packages (like all distributions do). Launchpad enables translation of
such forks and uses the upstream translation as the base. If you
dislike how Ubuntu ships forks of upstream packages, you should bring
that up elsewhere.

We *are* interested in figuring out more details about Ubuntu packages
and how they are modified from their upstream sources, but it's simply
the data packages are not providing *yet* to Launchpad.

> Like many other teams we already have a good list of Ubuntu specific
> apps and docs, and our team members usually know what they can do or
> not.

Apparently, everyone can miss a few. Was metacity with its changes on
your list?

> The problem is that everybody can make suggestions everywhere...

Why is that a problem? Do you repeatedly see people making new
suggestions on already translated messages? Or did you see that in the
past?

Also, note that Ubuntu rolls out language pack updates even long time
after upstream has continued supporting a certain version (i.e. we might
get a hardy language pack update, even if GNOME 2.22 is not getting any
translation updates anymore). Locking translations would be counter
productive in that case as well, especially since we are going to enable
translations sharing between all active Ubuntu releases.

> There's also a potential issue with the Cannonical copyright at the
> bottom of Launcpad translations pages, but it's another problem..

I am not sure what do you mean by this? The only mention of (c)Canonical
I see there is for the web page, and I can't see how's that a problem.