this post was submitted on 06 Mar 2025
125 points (94.3% liked)
Programming
18656 readers
129 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It would be a useful way to predict it possibly, but presumably the author meant if you have support for localization, you also provide an obvious and easy means of changing the language.
More importantly, you should be using the language an existing user has already used in the past.
Edit: come to think of it, this is less a programmer problem, and more of a UX problem. Obviously as programmers we need to take UX into consideration, but in all my products I've worked on, UX is specified already by a UX designer.
It's not even that, there are multiple languages spoken in the same region. Webpages should just use the language the browser tells it to use.
I had assumed the author didn't limit his statements to web browsers. If it's an application on a user's box, they should be using the language the OS provides.
In the case of less complex hardware, IoT or embedded devices with localization support, you would likely have another strategy if it doesn't have a setup process. For something without internet or GPS, you can't do this obviously. For something without a GUI, it's unlikely to have localization support without direct design consideration for it's destination.