Now that https://github.com/nodejs/nodejs.org/pull/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?
Fishrock123
All 18 comments
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:
To keep things clear, I'd like all upcoming design-related issues to be forwarded to the design repo so that I can consider them while designing.
leo
on 28 Jun 2016
Sure, I guess? But we kinda need it before then. Can't hold everything up for that.
Fishrock123
on 28 Jun 2016
one thing we could do if we're really getting translation efforts back up again is probe for the activeness of the i18n WGs
ghost
on 28 Jun 2016
Quoting myself here from https://github.com/nodejs/iojs.org/issues/235:
Flags != Languages.
We could add automatic redirection to the localized version based on the user's 'Accept-Language' header settings. There's an nginx module for that: http://wiki.nginx.org/AcceptLanguageModule
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.
fhemberger
on 28 Jun 2016
we should also probably assemble a separate team to control translation efforts. the iojs way wasn't the best
ghost
on 28 Jun 2016
@Fishrock123 Ahh, no problem! Didn't know that.
leo
on 28 Jun 2016
@fhemberger i wouldn't do it automatically though. maybe a hint from somewhere within the site asking if you want to switch to the version of the site in your language
ghost
on 28 Jun 2016
@ore https://github.com/nodejs/nodejs-ko is quite active.
Flags != Languages.
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.
We could add automatic redirection to the localized version based on the user's 'Accept-Language' header settings. There's an nginx module for that: http://wiki.nginx.org/AcceptLanguageModule
I think it's the most reliable way to determine a user's language without the need for user interaction.
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
Fishrock123
on 28 Jun 2016
@Fishrock123 yeah, but that's one of the only ones 😞
ghost
on 28 Jun 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
on 28 Jun 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.
fhemberger
on 28 Jun 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.
srl295
on 28 Jun 2016
i am going to open a separate issue regarding translation in general in this repo
ghost
on 28 Jun 2016
From The Korean Translation Group: https://github.com/nodejs/nodejs-ko/issues/381#issuecomment-229031422:
and I think there is a dropdown menu is needed to select languages.
Fishrock123
on 29 Jun 2016
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?
alexandrtovmach
on 24 Jun 2019
@alexandrtovmach just an example on my above discussion, instead of flags use українська | français | español | 日本語 etc
srl295
on 24 Jun 2019
@srl295 could you take a look on my PR?
alexandrtovmach
on 26 Jun 2019
This feature already merged, so I think is good idea to close this issue
alexandrtovmach
on 30 Jun 2019
Related issues
jitendra3109
·
6Comments
loriF
·
3Comments
julianduque
·
4Comments
JungMinu
·
8Comments
gbhrdt
·
4Comments
Most helpful comment
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.