Localisation

[kyzh]

Most technicians speak and read English fluently. It is not entirely the case of the targeted audience.

The content could be brought to a broader public by localising it. Most of the content apart of the blog is probably meant to remain static, so that shouldn't be too difficult to integrate in the workflow.

I don't say now is the time to do it. That could wait for after the summit (#5), once the vision is strong enough to avoid being lost in translation.

I think it should be one of the requirement to go further with the OCI to realise its full potential.

[chadwhitacre]

Good call, @kyzh. I suppose we'd start with translations of the About page?

[kyzh]

I have started with 2 letter prefixes in the page name, in my case "fr", like so "fr_index.md" and "fr_pledge.md". I assume that the difference between french, Belgium french, Canadian french etc. is probably worth pursuing at a later stage if deemed necessary.

Now on the translation side of things there is few points that definitely need to be raised. I also translated open company initiative by Initiative d'entreprise libre.

• I kept the initiative word as it does the job rather well.
• I used entreprise instead of words like "société" as the former has a clearer meaning
• I used the word libre for open : 'The word "libre" has been recommended as a substitute for "free" when the "freedom" sense is intended (not the gratis sense), and for "open" when the essential freedoms apply' see wikipedia for more on the word libre.

It is likely that the draft has typo and contain sub-optimal translation. I would highly advise for someone to have a second look before using this version live

[chadwhitacre]

@kyzh Sweet! Can we get these in a pull request?

[kyzh]

Both the about and pledge are pull requests: https://github.com/opencompany/opencompany.github.io/pull/42 https://github.com/opencompany/opencompany.github.io/pull/43

[chadwhitacre]

Ah, missed that somehow. Thanks!

[kyzh]

I'm mainly using a web browser to contribute. That mean that i don't have a proper way to test the site behaviour on my modification.

I could do with a bit of help to understand how to rebuild a local version. I'll make it up by writing on the matter.

[chadwhitacre]

@kyzh Where will these show up on the site?

[kyzh]

The way i see it is on the main page, there could be a dropdown/button like so

Than would then redirect to the right index eg. fr_index or de_index etc. All of the prefixed page would link to each other.

The dropdown might not be the most elegant way to do it I'm sure that people found different ways

[chadwhitacre]

I could do with a bit of help to understand how to rebuild a local version.

We're using Jekyll, so if you have Ruby installed you should be able to do:

$ gem install jekyll
$ git clone https://github.com/opencompany/opencompany.github.io.git
$ cd opencompany.github.io
$ jekyll serve --watch

Then hit http://localhost:4000/ and go wild. :-)

[chadwhitacre]

Okay, so we localize with language code as the first path part? I wonder if Jekyll gives us any helpers for this ...

[chadwhitacre]

https://www.google.com/search?q=jekyll+i18n

[kyzh]

@whit537 i will give a go at the rebuild with the i18n

[chadwhitacre]

Sweet! :-)

Hey @timothyfcook, ask @kyzh if we can add him to https://www.gittip.com/opencompanybiz/members/ and this repo, eh?

[kyzh]

I think I making progress with https://github.com/screeninteraction/jekyll-multiple-languages-plugin

[kyzh]

I have the translation done in a separate branch i18n: https://github.com/kyzh/opencompany.github.io/tree/i18n

It works by adding fr to the URL. Then everything will be in French, both content and links.

What is left to do is a way to provide the translation.. I will try to make a dropdown at the right of the nav bar.

Let me know if you think that there is a better to provide the translated version.

[kyzh]

Added a dropdown that help switch from one language to another. I created a branch on top of i18n with the dropdown: https://github.com/kyzh/opencompany.github.io/tree/i18n_dropdown

Feedback appreciated :tada:

[kyzh]

kudos to @simonsarazin for the review of the french translation and for providing the required modification

[zbynekwinkler]

I'd like to do translation to czech.

[kyzh]

@zwn the framwork has been merged. You should now be able to start on the translation to czech..

Here is the few step involved:

1) Requirements installation

$ gem install jekyll
$ git clone https://github.com/opencompany/opencompany.github.io.git

2) Setup testing

$ cd opencompany.github.io
$ jekyll serve --watch

3) Branch creation Setup a new branch in git to track your changes. Also reference this issue in your commit if possible.

4) New language creation

• Add an item in the languages key in _config.yaml It should be a 2 letter string as in the ISO 639-1 2 letters code (list http://reference.sitepoint.com/html/lang-codes)
• Copy the set of translatable string

cp  _i18n/en.yml to _i18n/cs.yml 

• Copy the set of template

cp -R _i18n/en/ _i18n/cs/

5) Translation

• translate the strings in _i18n/cs.yml
• translate the template file in _i18n/cs/{about,home,join,_posts,summit}/*

6) Pull request (to merge your branch into master)

And if I'm not mistaken, that should be about it.

[kyzh]

I documented the process here https://github.com/opencompany/www.opencompany.org/wiki/How-to:-Setup-for-Translators

[chadwhitacre]

!m @kyzh