Skip to content

Language picker #806

Description

@Fishrock123

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

  1. leo commented on Jun 28, 2016

    @leo

    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.

  2. Fishrock123 commented on Jun 28, 2016

    @Fishrock123
    ContributorAuthor

    Sure, I guess? But we kinda need it before then. Can't hold everything up for that.

  3. fhemberger commented on Jun 28, 2016

    @fhemberger
    Contributor

    Quoting myself here from nodejs/iojs.org#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.

  4. leo commented on Jun 28, 2016

    @leo

    @Fishrock123 Ahh, no problem! Didn't know that.

  5. Fishrock123 commented on Jun 28, 2016

    @Fishrock123
    ContributorAuthor

    @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

  6. fhemberger commented on Jun 28, 2016

    @fhemberger
    Contributor

    @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.

  7. fhemberger commented on Jun 28, 2016

    @fhemberger
    Contributor

    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.

  8. srl295 commented on Jun 28, 2016

    @srl295
    Member

    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.

  9. Fishrock123 commented on Jun 29, 2016

    @Fishrock123
    ContributorAuthor

    From The Korean Translation Group: nodejs/nodejs-ko#381 (comment):

    and I think there is a dropdown menu is needed to select languages.

  10. added
    i18nIssues/PRs related to the Website Internationalisation
    and removed
    contentIssues/pr concerning content
    on Jun 15, 2017
  11. alexandrtovmach commented on Jun 24, 2019

    @alexandrtovmach
    Contributor

    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?

  12. srl295 commented on Jun 24, 2019

    @srl295
    Member

    @alexandrtovmach just an example on my above discussion, instead of flags use українська | français | español | 日本語 etc

  13. alexandrtovmach commented on Jun 26, 2019

    @alexandrtovmach
    Contributor

    @srl295 could you take a look on my PR?

  14. ghost added a commit that references this issue on Jun 29, 2019
  15. alexandrtovmach commented on Jun 30, 2019

    @alexandrtovmach
    Contributor

    This feature already merged, so I think is good idea to close this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    i18nIssues/PRs related to the Website Internationalisation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions