Just add new content in English version

[Xuanwo]

When I update the document of zh-cn, I have a idea that we can just add new content in english version, and other languages just keep pace with english version. In this way, it will make the translation work easier.

[leesei]

I second. There should be a single source of truth.

We could add info in the README suggesting

• new contents SHOULD be added to en version
• language maintainers SHOULD sync the en version to other languages intermittently
• if the content contributor is not familiar with English, merge the PR first and create issue or PR to add to en version.

[jasonren0403]

As for my experiences in other repos, it may be better to put Crowdin into practice. Strings may be updated there for approval.

[andrii-bodnar]

Hi @Xuanwo, @jasonren0403!

it's Andrii from Crowdin. I’m big fan of Hexo. Crowdin is free for opensource, I can do a pull request with the integration setup. I would only need a green light from you and the minimal setup of this repo (create a Crowdin project and add some Actions secrets).

The integration can be completely automatic and can be done via Crowdin GH Action.

Also, I'd like to participate in the Ukrainian language translations if you'll add this language.

[stevenjoezhang]

CC @hexojs/core

[yoshinorin]

@andrii-bodnar

Thank you for your advice :)
So, what should we do if we want to proceed this?

I assume...

1. Create hexo org in Crowdin
2. Register maintainers to Crowdin
3. Migrate translated files to Crowdin (I don't know how to...)
4. Delete translated contents from this repo

Is it correct?

[andrii-bodnar]

Hi @yoshinorin, thanks for your response!

I will prepare a fork with the integration setup and a demo Crowdin project.

The translated files will be migrated to Crowdin automatically and then Crowdin GH Action will start creating pull requests with new translations. Translated content shouldn't be deleted from this repo.

The translations migration process might be a bit difficult since translations upload to the HTML-based file formats (MD, HTML, txt, and others) is based on some ML algorithm that sometimes can't handle all the translations correctly.

[yoshinorin]

@andrii-bodnar

I will prepare a fork with the integration setup and a demo Crowdin project.

Is this means we can try to use Crowdin demo with current hexo.io data?

[andrii-bodnar]

@yoshinorin demo project just to show how it will look like

If you will decide to move forward, it'll be better to create a project under your own Crowdin account

[yoshinorin]

@hexojs/core
May we proceed this?