It's late and I really don't know what I'm doing

[clav]

I have no idea, I keep meaning to try in case I need to make an extension with an en-UK locale, you could try it and see.

en-GB is the language code.

i keep meaning to test if just 'en' works, because all my extensions use real English, but register the package as en-US at the moment

[Pike]

i keep meaning to test if just 'en' works, because all my extensions use real English, but register the package as en-US at the moment

hehe, if you do get round to it please let me know if it works, registering as en-US just seems wrong

[c∂n]

i keep meaning to test if just 'en' works, because all my extensions use real English, but register the package as en-US at the moment

hehe, if you do get round to it please let me know if it works, registering as en-US just seems wrong

en-UK would probably be english for Ukranians : )

we should definitely use en-GB more : )

[clav]

here's my latest install script.

- uses an array of locales as seen above
- incorporates Jed's checking-if-it's-already-installed stuff
- can set kSkinFolder to "" if the package doesn't have one, rather than editing the rest of the script
- doesn't have a success message, because i've decided i don't want them in my extensions.

[diesel_travis]

here's my latest install script.

looks good. I wonder how difficult it would be to localize strings used: kMsg, error messages. I'm also trying to think of a pleasant way to give the user the option to install the additional locales. It may be excessive, but I'm just trying to think globally.