Better way to promote translations

[fhemberger]

We should add a language switch/list of translations or something similar to the site to better promote the internationalization efforts. Also we need to discuss, if a translated home page alone qualifies as "site translation".

Tools like GitLocalize (discussed in #972 (comment)) would really help.

[sotayamashita]

We should add a language switch/list of translations or something similar to the site to better promote the internationalization efforts.

@fhemberger I appreciate you creating an issue. I can help to implement these features. We provide GitLocalize for free and would like to help Node.js let developers know more. 😄

cc:/ @bnb

[bnb]

Big +1 to GitLocalize from me - looks like a solid tool to really lower the barrier to participation in docs/site translation.

[kahwee]

Nice find. This looks fantastic.

[watilde]

Big +1 on this from me as well. It would be nice to keep having both of the workflows for a while to try the tool out quickly.

[sotayamashita]

We need to discuss it with a lot of people.
cc:/ @nodejs/website @nodejs/localization

[Lellansin]

It's great. I think we need a plan (how about Github Project?), and I've prepared to PR for it.

[fhemberger]

Again, before using GitLocalize, we need to discuss access rights to the organization (same as with Snyk or Greenkeeper):

Quoting @mikeal:

As a general rule we don't enable org wide access to external applications for security reasons. We have sensitive information in private repositories.

[Rukeith]

It's a great ideal. I would like to help to translate

[pierreneter]

You and me can do it with left and right panel in Sublime Text or whatever editor, granting a third party permission is a real risk. Why we need GitLocalize? Do not be lazy.

[sotayamashita]

@fhemberger
Do we use Snyk or Greenkeeper now? If it does, how to solve the issue?

@pierreneter

You and me can do it with left and right panel in Sublime Text or whatever editor,

We are not only offering the split view. Our focus is how to keep translated ones up-to-date when the original language is updated and provide the following necessary features for it below:

• Link each sentence between original and translated ones so we let you know which is updated or not.
• Check it out our video how we work: https://youtu.be/b09LDukIJiU

granting a third party permission is a real risk.

I would like to know the risk. You are talking about @fhemberger mentioned in #issuecomment-303936003

[laosb]

Agree with @sotayamashita, I've been doing translating with plain git & text editors, and it was a disaster.

[fhemberger]

@sotayamashita No, we don't use them because of the rights they require.

[pierreneter]

@sotayamashita

Here is why it's dangerous.

[sotayamashita]

@fhemberger I understood.

@pierreneter & @fhemberger
We will consider the permission again. I would like to know what permission setting is great so if there are great apps, please tell me! I will look into it.

[sotayamashita]

Please join the conversation. @JustinBeckwith, @mikeal, @phillipj, @rvagg

thanks in advance. 🙇

[zlatanvasovic]

The current system is too inefficient. You can't keep up with the English version easily. I'd suggest dropping out the usage of raw translating (translate whole file into new file). How about making an array of phrases to be translated one by one?

[preco21]

This might not be proper solution because it requires additional sync server, but anyway what about trying out https://crowdin.com/ with https://github.com/thejameskyle/crowdin-sync solution?

[sotayamashita]

@zdroid It might be backup plan 👍.

[sotayamashita]

@preco21 I have thought of crowdin but your translation will not be your commit in GitHub in crowdin.

[zeke]

[crowdin] requires additional sync server

Not any more.

Crowdin actually has a GitHub integration built in now, so a standalone server is not required. They can connect to your repo, sync content, generate pull requests, etc. I believe @thejameskyle created crowdin-sync before Crowdin supported GitHub syncing. See github/opensource.guide#295 (comment)

The Electron project is embarking on a localization effort, and we are using Crowdin. See https://github.com/electron/electron-i18n for details.

[sotayamashita]

@zake

It seems that Crowdin is getting better and electron/electron-i18n is the very great project 😄 We will use it as a reference to help Open Source Translation. By the way, I can help the project if you need a translator for Japanese 🇯🇵.

[sotayamashita]

@fhemberger

We are implementing the new way to get appropriate permission.
We will share it soon 😄

[fhemberger]

Okay, this issue went waaaaaaay of track from my original intention. 😉

We should add a language switch/list of translations or something similar to the site to better promote the internationalization efforts.

Can we please move translation workflow related discussions to #972?

[fhemberger]

Oh, noticed we already had a discussion about a language switching mechanism in #806, closing this for now.