Good feedback -- thanks. We've long struggled to find the right balance between "convenient/automatically correct" and "non-confusing" in site localization.
Born and raised in California, have lived abroad the past 10 years in various locations. The language I always want a website displayed in is the language my browser says I want it displayed in. Sure, make the content local, e.g. assume Chilean pesos if I'm in Chile, but please simply follow Accept-Language for language selection.
Same, but I’m in South Africa now. I was impressed by how cool the banking is. But then, many countries were ahead of the US in that. My fave feature is being able to send cash by SMSing a one time pin.
Why not just use the Accept-Language header? stripe.com already does this – At least I get redirected to "https://stripe.com/en-de", seemingly based on the combination of header and geolocation
Show a pop-up or pop-up like asking if they want to switch to an Indian language.
I never switch to another language other than English.
It is highly advisable that companies translate to eight most common Indian languages. Or even the top five [0].
People speaking all major languages of India are huge potential markets for companies. Google offers search in nine Indian languages. Amazon provides customer services in five languages.
For some services, you should not even want to translate to languages other than English. India has one of the largest English speaking populace of the world- 2nd only after the US [1].
Especially where people willfully get arrested to wipe down Hindi marks from metro stations [0] and people who have fasted to death to not have Hindi as the national language [1].
