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

[Heikki Toivonen]

Philippe Bossut wrote:
> I'm not proposing to change Chandler code at all. I'm proposing that,
> when running in locale en-US, Chandler loads the relevant localization
> file if present as with any other locale. Actually, it is entirely
> possible that this works already (I'll check and log a bug if it
> doesn't). What I'm proposing is that we *do have* such a po file
> somewhere in our (TBD) localization svn repository, that we (coders and
> PPD) remember that we have one and that we ship it along with the en-US
> version.

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 wonder what kind of a performance hit en_US locale would be. (Of
course, all other locales are already suffering a perf hit.)

There is also the footprint issue, although again the other locales are
already suffering from this.

-- 
  Heikki Toivonen


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 251 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/design/attachments/20060925/2ab526dc/signature.pgp