microsoft / vscode-loc

VS Code Localization Extension
Other
535 stars 294 forks source link

Bring back British English language pack #443

Open ZanderBrown opened 2 years ago

ZanderBrown commented 2 years ago

Please publish an en-GB language pack again.

Note on implementation: we could generate an English language pack from the English strings we have and then string replace things like trash -> bin.

rswift commented 2 years ago

I've been pondering the same thing... it seems to have vanished? VSCode throws a wobbler on load, and the language pack is no longer in the market place?

The 1 extension(s) below, in workspace recommendations have issues: ms-ceintl.vscode-language-pack-en-gb (not found in marketplace)

danyeh commented 2 years ago

@TylerLeonhardt, no longer in microsoft publish scope?

TylerLeonhardt commented 2 years ago

👋 hi there. The English (UK) language pack is causing more harm than good now because it hadn’t been updated in a very long time… because of this, old strings are being used when new ones should so you run into situations where:

Because of this, and because another dialect of English is already supported by the product, we unlisted it for now until we have cycles to set up the right automation to make it happen. Sorry for unpublishing it out of the blue but the usage was also incredibly low which made us feel like not may folks would be impacted by this.

ZanderBrown commented 2 years ago

I'd be interesting in helping out with updating it, but really if your ending up with old strings used when the source has been updated it sounds like a flaw in the localisation system — Though I can't say I ever noticed any placeholders

trash -> bin

In GNOME we actually call it the Wastebasket, but arguably things like colour are more important (I first noticed the pack was gone when I got no results for "colour" in the palette), there is also more to it than simply find/replace a load of -ize — There are grammatical differences as well. But of course, USian strings are a useful starting point.

(also it feels a bit odd you've entirely replaced the initial post, I'll agree the original wasn't entirely helpful but now I sorta read like an entitled idiot)

rswift commented 2 years ago

@ZanderBrown don't worry old bean, us entitled idiots can stick together and grumble about the lack of ColourfulBinLocalisations ;)

I'd also be willing to help out. The lack of usage does make me wonder if non-en-US speakers have become used to the US English content that people no longer bother seeking out localisation?

thany commented 2 years ago

I'm not even British myself and I want it back! I just like the UK variety of English more than the US one. It feels closer to home (and geographically speaking, it is).

As a Dutch boy, I'm very used to typing colour, metre (or meter if it refers to a device like a multimeter), customise and maybe Dockerise, and (less relevant) chips and crisps, and the boot and bonnet.

So go ahead, mates, do feel a bit proud of your language 😎

SergiusMath commented 2 years ago

I agree with Zander, please try to return it.

hickford commented 2 years ago

Dates written in the American style are confusing to many people. Consider using a unambiguous date format such as yyyy-mm-dd (ISO 8601)

Example from Extension page

Last updated 12/3/2021

image

https://code.visualstudio.com/docs/getstarted/locales

I tried changing the locale to Spanish, but the dates in the Extensions page are still in American:

image

ZanderBrown commented 2 years ago

Indeed, arguably even if en_GB is restored (one can dream) it would be more appropriate to use 8601 as it avoids confusion, and it is likely already familiar for programmers.

nithin-mk commented 2 weeks ago

As an Indian boy, I want the en-GB pack back too :-)