Comment 23 for bug 10822

(In reply to comment #22)
> I can reproduce this on a Hoary preview install, oddly enough.
>
> Perhaps the issue is that we ship en_GB .mo files, but no en_US ones?

Exactly. language-pack-en-base contains heaps of en_GB translations, but only
one (gcalctool) for en_US. I assume that the vast majority of C strings are
already in en_US, so that upstreams generally don't ship en_US po files.

So actually you exactly get what you asked for with

  LANGUAGE="en_US:en_GB:en"

So if this is really annoying for English users, maybe GB should not be a
fallback for US (and vice versa), but rather C should be the general fallback?