Should we use i18n instead of recreating files?

[tony19]

I'm wondering if we can use an i18n lib to support translations instead of having to recreate every docs file from the main repo. Not sure which would be easier for contributors and maintainers. 🤔

For instance:

• @intlify/vite-plugin-vue-i18n
• VuePress i18n

cc @mrcego @ShenQingchuan

[mrcego]

I'm not sure about it, because according my knowledge, it drops forks from docs, right? I mean, contributors will keep up to date an unique repo with i18n tool into it.

[tony19]

Actually, I don't think those i18n libs will work in VitePress. Forking the Markdown files per language (as we're already doing) seems like the right way to go.