[Design] Proposal: have an en-US localization egg

[Philippe Bossut]

Heikki Toivonen wrote:
> Are you proposing that this en_US locale would not be complete, only
> containing last minute wording fixes? Or full localization even though
> most strings would be identical to the strings in the code?
>   
I didn't elaborate but, indeed, having only the modified strings seems 
to be a perfectly good solution. No need to dupe the strings that are 
identical to the python code since the message factory default to those 
if the translation is missing.
> I wonder what kind of a performance hit en_US locale would be. (Of
> course, all other locales are already suffering a perf hit.)
>   
As you said, it can't be worse than what other languages go through. If 
it's that bad, we better fix it...
> There is also the footprint issue, although again the other locales are
> already suffering from this.
>
>   
FWIW, the current French egg is around 200K once decompressed and 
dropped in place in Chandler. Not that significant when compared to the 
rest of Chandler.

Cheers,
- Philippe