Possibly use GitLocalize to simplify translation work

As discussed here, translation might be made substantially simpler with the GitLocalize service that @sotayamashita has generously made available to us! 😍 This looks like a great workflow, but I have a few questions/concerns for vuejs.org specifically:

• I notice only .md files are supported. Since we also have other files with localized content (e.g. .ejs), do you think it would soon be possible to support those as well? I’m not sure if it’s a deal breaker - it just means some translation work would have to be done outside the service.
• Since we update these docs very frequently and translate to many languages, we currently maintain a separate repository for each language. GitLocalize only seems to support subfolders within the same directory, but I worry that this would create a barrage of pull requests that most people would have to ignore. Are there any plans for multi-repo support?

@kazupon @ChangJoo-Park @gbezyuk @ErickPetru @Jinjiang @ludo237 @Haeresis What are your thoughts?

[sotayamashita]

@chrisvfritz

I am sorry not to reply fast.

I notice only .md files are supported. Since we also have other files with localized content (e.g. .ejs), do you think it would soon be possible to support those as well?

We will not support .ejs but we think we can extract localized content into config file such as.en.yaml. What do you think?

Since we update these docs very frequently and translate to many languages, we currently maintain a separate repository for each language. GitLocalize only seems to support subfolders within the same directory, but I worry that this would create a barrage of pull requests that most people would have to ignore. Are there any plans for multi-repo support?

We are considering and understand your concern. If we merge other locales into one repository, PR will be getting increasing. However, I think it will not be the problem if there is translation flow. For example, what about to create locale team like Node.js. There are localization teams such as nodejs-ja or node-ko and they will review before merging PRs.

[kazupon]

@ludo237 sorry, the above example was bad … 🙇 I don’t forget Italian vue users 😺

@chrisvfritz sorry, my poor english … 🙇

Yes! I think so. Hexo can localize with current language (language: en in _config.yml) from src / languages / current.yml. In that way, translators can manage all work in their own repos with not using GitLozalize.