Add i18n support to components

[caixingyue]

I hope that the components can add support for localization, such as [Request], [Responses], etc.

[sserrata]

Hi @caixingyue, I'm not very familiar with how docusaurus implements i18n - can you describe what, in your opinion/expertise, need to be added to support translations for Request, Response, etc? Is it a matter of wrapping the text of those components in <Translate>?

[caixingyue]

Hi @caixingyue, I'm not very familiar with how docusaurus implements i18n - can you describe what, in your opinion/expertise, need to be added to support translations for Request, Response, etc? Is it a matter of wrapping the text of those components in <Translate>?

Hello, the red circles in my screenshots need to be translated. There are some parts of the page that I did not take screenshots of, but you should be able to understand which ones need to be translated or have translations added (such asbody, which can be annotated with translations).

According to the instructions of docusaurus, you can use translation APIs.

Reference address: https://docusaurus.io/docs/i18n/tutorial#translate-your-react-code

[kenny-not-dead]

I have the same problem. cli command "write-translations" does not generate this part described above @caixingyue.
Please let me know how this part can be translated in another way.

[arloktev]

Is there anything currently being worked on regarding this issue? Or can it be considered for revision?

[sserrata]

Hi @arloktev and everyone on this thread - just opened a PR intended to add initial i18n support to the theme. Would appreciate any help testing to see how well it handles translations. At least, so far, the deploy preview looks good. Let me know if you need help with setting up the dev/test environment. Thanks!

[sserrata]

Here's a link to the PR and related branch you should check out: #1210