Adds i18n footer links (for all known active languages)

[snostorm]

Adds i18n footer links, merges against #257 not master

Notes:

• This list was originally a side bar, until I remembered this would look funny on the homepage, so it is a footer (for now.) I'd like to revisit having it in a sidebar again once we evolve the design more.
• The footer links are to the SAME article in the selected language. I'll cover the more advanced case of missing articles at a later time.
• I'll need to confirm with the i18n groups I got all of the names right (message sent)
• There's probably a better place to maintain this list of languages
• There is an "i18n" dictionary variable for the word "Languages" itself, which we fall back to English for when this isn't defined. See 中文 for this in action. (Shows 其他语言 instead of Languages.)

[snostorm]

Can the i18n teams please check the following:

• Your language name is correct, https://github.com/iojs/website/blob/template-build-refactor_i18n-footer/source/project.json
• If you want to translate "Languages", https://github.com/iojs/website/blob/template-build-refactor_i18n-footer/content/en/template.json#L4

@iojs/iojs-bg
@iojs/iojs-bn
@iojs/iojs-cn
@iojs/iojs-cs
@iojs/iojs-da
@iojs/iojs-de
@iojs/iojs-el
@iojs/iojs-es
@iojs/iojs-fa
@iojs/iojs-fi
@iojs/iojs-fr
@iojs/iojs-he
@iojs/iojs-hi
@iojs/iojs-hu
@iojs/iojs-id
@iojs/iojs-it
@iojs/iojs-ja
@iojs/iojs-ka
@iojs/iojs-ko
@iojs/iojs-mk
@iojs/iojs-nl
@iojs/iojs-no
@iojs/iojs-pl
@iojs/iojs-pt
@iojs/iojs-ro
@iojs/iojs-ru
@iojs/iojs-sv
@iojs/iojs-ta
@iojs/iojs-tr
@iojs/iojs-tw
@iojs/iojs-uk
@iojs/iojs-vi

I used Wikipedia's list of language names as inspiration.

[AdriVanHoudt]

Any plans on adding something for missing languages with a capture page to see the interest in the language?

[parroit]

Italian it's OK

[snostorm]

@AdriVanHoudt good timing! I just semi-addressed this in an update to the PR description.

Short term answer: no

Long term answer: yes

Currently we have 99% coverage of articles, so this is a non-issue. Soon, we'll be adding new pages and it will be very important to fall back to English but consider cases like:

• Although the fallback content is shown english, show a message (in the original language) at the top to help recruit translation assistance -- and link to the GitHub repo.
• Don't get a negative search engine hit / mis-indexing for these duplicate pages
• etc.

For now we're not doing any sort of magical language detection. Nobody will be redirected/forced to use a language they didn't plan to see :)

[marocchino]

ko looks okey.
The word "Languages" is "언어" in Korean. but It's too small to send PR.

[AdriVanHoudt]

@snostorm I like the fallback + native language notification. This is just something for us (@iojs/iojs-nl) because we feel that dutch speaking people in general do all dev in english so translating only seems needed if there is really demand for it.

[YurySolovyov]

Russian / Русский LGTM

[snostorm]

@marocchino noted. I'll take any incoming small responses like this and bundle them in to a patch before merging.

[marocchino]

Oh, Thank you. :3

[stringparser]

Spanish its OK. Regarding to translate the Language I think so but I'll ask around :) on iojs-es and come back here ;)

[snostorm]

Note to translators who might PR/post translations here, there's also a new string "contribute-message" which was requested in #225

Lets you localize the following however you like (a joke, url to your local group, both projects, etc.)
<!-- See something you like? Want to help? Visit https://github.com/iojs/website to contribute -->

[stringparser]

Right, I'll take care of that as well @snostorm

[Starefossen]

When #256 is merged you can add a link to the Norwegian translation as Norsk.

[fhemberger]

German is ok.

[diagramatics]

id looks okay.

[behcet]

Turkish is ok.

[JCMais]

👍 Portuguese

[margaritis]

👍 Greek

[nikcorg]

Finnish 👍

[kosamari]

Japanese 👍

[mingtsay]

Myabe 正體中文 for tw will be better

On 2015年3月4日週三 12:12 Haoliang Gao [email protected] wrote:

Is it good to change in this way 中文 -> 简体中文 臺灣 -> 繁體中文

cc @iojs/iojs-cn https://github.com/orgs/iojs/teams/iojs-cn
@iojs/iojs-tw https://github.com/orgs/iojs/teams/iojs-tw

—
Reply to this email directly or view it on GitHub
#258 (comment).

[therebelrobot]

@snostorm I just ran both gulp and gulp build on iojs 1.0.3, and it built super fast. Kudos bro. No errors, seems G2G once you have all the language +1's

[haoxins]

Is it good to change in this way 中文 -> 简体中文 臺灣 -> 繁體中文

+1

[parroit]

regarding "current_version": "1.4.3" and "current_v8": "4.1.0.21",
are they meaning to be used to dynamically change release numbers in markdown?
If so, how can we use them?

[snostorm]

FYI I'll probably merge this soon. I think I factored in everyone's comments although there was a lot of inline brainstorming / discussion around cn and zh_TW that I may have got it wrong.

If there are any additional tweaks feel free to fix with additional PRs to the master branch once this lands.

@parroit, take a look at line 3 of https://raw.githubusercontent.com/iojs/website/template-build-refactor_i18n-footer/content/en/es6.md (or almost any other index.md or es6.md in the repo), we've already introduced some variables in to the build process to simplify things.

Under the {{i18n.VARIABLE}} namespace you can access your own dictionary as specified in the template.json. If you want some more information or to discuss this further please open a new Issue, and we'll continue there 👍

[diagramatics]

Something seems off on line 90 of gulp/tasks/templates.js.

url: `/${lang.code}/${fileName}.html`

It's a backtick instead of a quote. Gives me an Unexpected Token ILLEGAL while trying to locally develop.

[snostorm]

@diagramatics this will only run against io.js which supports ES6 style strings. You may be running a Node.js 0.10-12?

[diagramatics]

@snostorm Ah, thanks. I just updated node to the new version because of another error. I'll rollback that commit on my PR.

[AntouanK]

@snostorm Are you aware that on translated pages, the FAQ link still leads to the English version?
It has an href of /faq.html

<a href="/faq.html">Συχνές ερωτήσεις</a>

[yoannmoinet]

@AntouanK I've just created an issue for this #267.

[AntouanK]

Oh, ok. 👍

[yoannmoinet]

@snostorm here's a PR #268 for #267 to set faq's links to relative.

[snostorm]

Since many localizations are following this thread I'll direct you to #276 which contains the ongoing build process work which was a followup to some of the effort which was started here.

At this point we're looking for feedback / suggestions on the patterns used in the sample home.html within that pull request. Some files (like the homepage) would move to sharing a single template like this with i18n hooks where articles (like FAQ, ES6) would remain markdown.