Repository navigation
Language picker #806
Description
Now that #490 has landed and the related build/deployment work seems to be completed, we should be able to get the language groups once again more involved with the website.
We should also start thinking of a way to choose the language.
I'm not sure io.js's way was really that great. I know we discussed the flag thing before, but to me that is the most easily recognizable way.
We don't have to have that open a country list, but we can use it as a prompt for language nonetheless.
cc @nodejs/website
cc also @leo who may have some ideas?
Activity
leo commentedon Jun 28, 2016
That seems like something that should be implemented with the next redesign. So it would be great if you could add it to this repo. More details here:
Fishrock123 commentedon Jun 28, 2016
Sure, I guess? But we kinda need it before then. Can't hold everything up for that.
fhemberger commentedon Jun 28, 2016
Quoting myself here from nodejs/iojs.org#235:
EDIT New link: https://www.nginx.com/resources/wiki/modules/accept_language/
I think it's the most reliable way to determine a user's language without the need for user interaction.
leo commentedon Jun 28, 2016
@Fishrock123 Ahh, no problem! Didn't know that.
Fishrock123 commentedon Jun 28, 2016
@ore https://github.com/nodejs/nodejs-ko is quite active.
My point also, but we shouldn't have the selection be flags, only the initial, along with the Language indicator.
I.e.
[🇩🇪 DE] is a little more visible than [DE] for such a thing.
perhaps but idk if I'm comfortable not having an easy way to adjust it?
I'm willing to look into the nginx thing though
fhemberger commentedon Jun 28, 2016
@ore You still could add a cookie for example: "Nah, I want to browse the site in Klingon". In case we're adding a manual selection dropdown, this should be done anyway.
fhemberger commentedon Jun 28, 2016
Link to the nginx module is now https://www.nginx.com/resources/wiki/modules/accept_language/
… and meh, it's a 3rd party module. Thought it was a core feature.
srl295 commentedon Jun 28, 2016
I'd recommend (1) content negotiation and then (2) a simple popup with a textual list of languages.
I would NOT recommend flags. You could put a little stylized globe for an icon to represent the language choice perhaps. English 🇦🇺 is spoken in a lot of places, as is French🇧🇱, etc. for that matter. Would be a lot of flags.
You could add a cookie and not change the URL. That means if you're browsing in French and you send the link to someone who prefers Spanish, they will see the same content in Spanish.
It might be better to redirect to a specific URL ( like /fr/ or /en/ ) so that links go to the right thing, with a popup offering to take you to your "preferred" language (content / cookie negotiated) if different.
Fishrock123 commentedon Jun 29, 2016
From The Korean Translation Group: nodejs/nodejs-ko#381 (comment):
alexandrtovmach commentedon Jun 24, 2019
Hello, I'm not sure what is the current status with language picker implementation. Can I propose something? I'm ready to implement and create PR with language picker on my own. Does it's have a reason?
srl295 commentedon Jun 24, 2019
@alexandrtovmach just an example on my above discussion, instead of flags use
українська | français | español | 日本語etcalexandrtovmach commentedon Jun 26, 2019
@srl295 could you take a look on my PR?
Language picker implemented (#2294)
alexandrtovmach commentedon Jun 30, 2019
This feature already merged, so I think is good idea to close this issue