The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Regardless of your nationality, when urine the bathroom, European…
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
I'm creating a new ASP.NET Core 3.1 Razor Pages application with individual user authentication using an in-app store (so SQL Server, as opposed to (Azure) AD).
The cool part is that Microsoft gives you a complete out-of-the-box register, login and profile solution, complete with 2FA and external authentication (OAuth 2.0).
It's all hidden inside some package so it doesn't clutter your solution either, although you have the option to scaffold each page individually if you like.
Really great, kudos to Microsoft, except...
IT'S ALL IN ELEPHANTING ENGLISH!
I've searched for a way to localize the default pages, but I can't find a proper solution.
When I scaffold the pages they have hard-coded strings in the HTML as well as the C# code.
Also, you really can't beat logic like this (if some string that the user is going to read starts with "Error"):
var statusMessageClass = Model.StartsWith("Error") ? "danger" : "success";
I've scaffolded all pages and I'm replacing all hard-coded strings with resource file references
It's quite a lot, so it keeps me off the streets and working for my money.
Still better than doing it all myself, but if you're going to offer this as one of the biggest companies on the planet, at least think about such stuff
We had many similar issues at my last firm which was a US (but 'international') company. On a number of occasions I tried to get changes made so things worked everywhere, not just in the USA. The response was always the same, "We'll take that under advisement". Which is a phrase that I have never really understood; but I am pretty sure it means, "screw you buster!".
They may look at their sales and decide that for the number of overseas sales that have in non-English speaking countries it's not worth the cost of creating/maintaining the application in alternate languages.
It may be that their sales would increase dramatically if they did add the additional language(s).
Were I to guess, I'd say that the answer may well depend upon the size of the company and how much they can afford to gamble on such a venture.