Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add i18n support and translate to Simplified Chinese #242

Open
wants to merge 7 commits into
base: docs
Choose a base branch
from

Conversation

CosmoLau
Copy link

Add i18n support and translate to Simplified Chinese.
Fixed broken links from blog.
Add i18n support for the home page.

If you want to add translations for a language, you need to run yarn run write-translations --locale [locale] first to generate the translation configuration. Then add the new locale to the i18n configuration in ducosaurus.config.ts. Then, copy the English documents and blogs to i18n/[locale]/docusaurus-plugin-content-docs/current/ and i18n/[locale]/docusaurus-plugin-content-blog/ directories respectively for translation.

To debug, you need to use yarn run start -- --locale [locale] to test the corresponding language, or use yarn run build and yarn run serve to see the effect of multi-language.

See https://docusaurus.io/docs/i18n/introduction for more information.

Copy link

Thanks for the contribution! Before we can merge this, we need @CosmoLau to sign the Salesforce Inc. Contributor License Agreement.

@mdonnalley
Copy link
Contributor

@CosmoLau Thanks for the PR 🏆

Sadly, we don't have the bandwidth (or literacy!) to support multiple translations of the documentation. I realize that we could rely on the community to keep the translations up to date but as far as I can tell there's not a lot of people who would be willing to update the translations as often as we update the english version.

I'm going to label this with waiting for interest to see if there's a strong interest in the community for this.

@mdonnalley mdonnalley added unlikely Feature we are unlikely to implement waiting for interest Waiting to see if there's strong community interest labels Apr 15, 2024
@CosmoLau
Copy link
Author

@CosmoLau Thanks for the PR 🏆

Sadly, we don't have the bandwidth (or literacy!) to support multiple translations of the documentation. I realize that we could rely on the community to keep the translations up to date but as far as I can tell there's not a lot of people who would be willing to update the translations as often as we update the english version.

I'm going to label this with waiting for interest to see if there's a strong interest in the community for this.

It's fine, I've deployed it to my github pages for myself or other Chinese developers to check out. I just have a question, can I use the APPID and APPKEY applied by oclif to provide algolia search service when I deploy it myself? I have disabled the search service for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla:signed unlikely Feature we are unlikely to implement waiting for interest Waiting to see if there's strong community interest
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants