Alex,

it might be a bit confusing, but localization has some nuts and bolds.

As Vincenç stated, Language Packs are outsourced to the community, some members provide them for free (like I myself the German ones at DeutschNetNuke), others sell them at Snow. These language packs contains translated versions of the default resource files, that has to be provided by the core, module and provider developers.

Duplicate keys do currently not lead to a misfunction of the module, but make translators' lifes harder.

For an en-US language pack, you do not need to copy every item, if you edit /App_GlobalResources/Locales.xml, so your English item looks like

  <language name="English (United Kingdom)" key="en-GB" fallback="en-US" />

OK then, but the situation remains that the language packs do remain out of date with no version control regardless.
A better mechanism to deploy the language packs with version control I suspect will be needed in the (distant) future (XML logging perhaps). Centralising the deployment could help a lot here and having a good way of submitting new (user created) language packs to the community. Could mean I radical change to the core I guess. That won't happen for a while.

I do understand the resouces argument so sorry to rake it,  I also understand the non English issue.
But be nice to your English friends in the UK over the pond please and give us some nice files to play with (if you can)  :)
I wish I had some better ideas!

Thanks for your suggestions, taken on board...

Cheers

Alex

¡No soñaría con hacer tal cosa mi amigo!

Alex