@guyonroche how do we deal with translating this to Chinese? Do we keep this PR open until someone adds a Chine translation or do we merge the PR and create a ticket for its Chinese translation?

@alubbe I could translate to Spanish too if you want that

Why don't we discuss how exceljs makes docs and how we translates it?

• If every time we discuss docs and translation at the same time, documenting cost will go high
• If documenting cost goes high, everyone stops documenting

I think documenting in English first is a good idea in order to supply a minimum and essential information fast. At the moment we can put // TODO in corresponding position in README_zh.md not to forget the later work.

@alubbe, @ABenassi87, @piglovesyou - translations (for Chinese so far) have come from volunteer submissions.
I (and quite a few contributors) try to keep the main English README up to date so it does tend to change with some frequency. This does mean the translations risk getting stale. I did mention this to the original Chinese contributor and he said he was happy to keep it up to date.
I expect the best option is to add a little caveat above the translations explaining this.

@ABenassi87 - by all means, if you want to add a Spanish version then it will be most welcome.