support i18n

[youngxhui]

please support i18n

[cortinico]

Can you clarify what exactly in i18n is not already supported?

[Ucekay]

I'm also interested in i18n support. To add context to this discussion:

I can see that react-native-web supports i18n, but I'd like to understand if the React Native documentation project is ready to accept community translations.

I'm particularly eager to contribute to Japanese localization of the documentation, as I believe this would greatly benefit the Japanese developer community.

Are there any established processes or guidelines for contributing translations?

[cortinico]

I can see that react-native-web supports i18n, but I'd like to understand if the React Native documentation project is ready to accept community translations.

We're happy to see community interests in translating the React Native docs, but we don't feel we're currently ready to accept translations at this stage

[Ucekay]

In #4367 , I suggested utilizing Docusaurus i18n support, referencing React docs' approach. What are the main concerns about translations at this stage? Is it the challenge of keeping up with frequent documentation updates, maintaining translation quality, or team bandwidth?

Also, would it be acceptable to host translations independently outside the react-native-website repository?

[cortinico]

Is it the challenge of keeping up with frequent documentation updates, maintaining translation quality, or team bandwidth?

A combination of both. For example, we just released the New Architecture as default, and that required significant work on the website. If we would have allowed for translations, we would have needed to update all of them.
Similarly we're aware that the API docs need a refresh as some props are not 100% correctly documented.