i18n support. about node-sec-roadmap HOT 15 OPEN

@mikesamuel

If Gitlocalize helps extract human language text and track which commits have changes that need to be translated, that would probably help a lot.

Yes, we do those things. In addition, we return translated file via a pull request to your repository and each translation is associated with GitHub user so they can see what they have been contributed to GitHub. ✨

I can probably handle redirecting requests for / based on Accept-Language headers.

I got it. I will try to configure. Please wait. 🙇

cc:/ @yosuke-furukawa

from node-sec-roadmap.

CC: @sotayamashita @chikathreesix

from node-sec-roadmap.

Sounds good. What can I do to help?

from node-sec-roadmap.

@yosuke-furukawa I appreciate your suggestion. 💯

@mikesamuel Hi! I am an engineer for Gitlocalize. We should think how to translate docs first regardless of whether we use GitLocalize or not. Any idea?

from node-sec-roadmap.

@sotayamashita If Gitlocalize helps extract human language text and track which commits have changes that need to be translated, that would probably help a lot.

It's published via a gitbook which allow for publishing multiple versions.

"Multi-Languages" says

GitBook supports building books written in multiple languages. Each language should be a sub-directory following the normal GitBook format, and a file named LANGS.md should be present at the root of the repository with the following format:

* [English](en/)
* [French](fr/)
* [Español](es/)

You can see a complete example with the ...

I can probably handle redirecting requests for / based on Accept-Language headers.

from node-sec-roadmap.

@mikesamuel I would appreciate if you could tell me the reason why do you write this document under Google org. 🙇

from node-sec-roadmap.

@sotayamashita My employer required it.

Can we set up a fork that just tracks google/node-sec-roadmap and which uses your GH plugin?

from node-sec-roadmap.

@mikesamuel

My employer required it.

I got it.

Can we set up a fork that just tracks google/node-sec-roadmap and which uses your GH plugin?

Before forking the repo, I would appreciate if you could follow these conditions below, I can give you our free OSS plan. You do not need to fork if it could be accepted. 😄

• The OSS projects should be non-profitable
• Up to 5 repositories
• Put a note that GitLocalize is used for a localization and its project link on README.md
• If you have a website for a project, put a GitLocalize logo on the site.

By the way, google/WebFundamentals have been using GitLocalize already. 🎉

from node-sec-roadmap.

• The OSS projects should be non-profitable

Agreed

• Up to 5 repositories

Thanks

• Put a note that GitLocalize is used for a localization and its project link on README.md

Agreed

• If you have a website for a project, put a GitLocalize logo on the site.

Could it go in the sidebar above "Published with Gitbook"?

from node-sec-roadmap.

@mikesamuel

Could it go in the sidebar above "Published with Gitbook"?

Sound good. What about to add "Translated by GitLocalize"? if It is ok, I will create a PR for it.

• Have you created a GitLocalize account? If it has not done yet, please create.
• After creating account, please "add repository" on GitLocalize

from node-sec-roadmap.

@sotayamashita, Sounds good to me.

from node-sec-roadmap.

@mikesamuel Please let me know when you integrate this repository with GitLocalize.

from node-sec-roadmap.

In offline conversation

Sota from GitLocalize said

As I mentioned before, google/WebF are using our tool so I ask them to integrate the app
on GitLocalize. I let you know when it has done.

so I'll try to move this forward once github.com/google/WebFundamentals clicks the necessary checkboxes.

from node-sec-roadmap.

@sotayamashita Should I follow up with WebFundamentals?

from node-sec-roadmap.

@mikesamuel I will check the status

from node-sec-roadmap.