Document translation plan

[baboon-king]

Any plans for translation?
I would like to be involved in translation if possible

[cyberalien]

I'm not sure about that.

Ideally it would be nice to have a translation.

However, there is issue of maintenance. Documentation is never finished, there is always something that needs to be updated. That means translators will have to dedicate a lot of time keeping translation up to date. Sometimes there is nothing new to add for long time, sometimes there are huge chunks of new or updated documentation. I've seen it many times in various projects when translation was outdated because person translating has lost interest.

Then need to consider target audience. This project is for developers, not typical users, most developers do understand English. Those who do not, have various automated ways of translating documentation, which usually leads to bad translation, but at least it have correct code samples, not out of date.

[baboon-king]

First of all, thank you for your reply

Your concern is necessary. When a project has multiple translations, there will be certain translations that are out of date

But I love this project. If the documentation of this project has Chinese translations, he will have more Chinese users.

Although some users can use the translation tool, the bad translation result is really hard to accept

Maybe I can maintain a community version of the Chinese translation repository first, if I actively update it and keep the good quality. Then consider becoming part of "iconify", or keep the community version all the time.