[Suggestion]: Please Support i18n for 18.react.dev
#7399
Comments
|
Hello, I'm maintainer for Serbian language together with @lxmarinkovic. For now I don't think there is much difference between latest version (v19) and v18, but I suppose docs will be updated only for v19 from now on. |
|
@rammba Thanks for sharing your thoughts! However, I believe it would be better to maintain the React v18 version separately. Combining the contents of v18 and v19 could lead to confusion for users. Many well-known open-source projects, such as facebook/docusaurus, manage their legacy versions separately. React also follows this approach with resources like Alternatively, we could use a previous Vercel production link, such as https://ko-react-exy5xcwjj-fbopensource.vercel.app/. This link provides the past Korean translation of React v18 (you can find this link in the Deployment section on GitHub).
The main reason I created this issue is to request official support for this i18n feature from React! Using links like https://ko-react-exy5xcwjj-fbopensource.vercel.app/ feels a bit messy and semantically improper. Anyway, happy new year, and I truly appreciate your passion for React! |
|
Yeah I totally agree with you. Even though there are vercel links provided by the bot, it would be great to have official domain for legacy versions. I hope maintainers will accept your proposal. I wish you a great and productive new year! 🚀 |
Summary
Hello,
I am currently the maintainer of
ko.react.dev.I noticed that the React Docs v18 was archived as
18.react.dev, but there is no support for i18n for translations of the v18 version of the React Docs.I would like to suggest adding i18n support for translations, such as
18.ko.react.devor something similar!If it's not possible, would it be okay if I host v18 version of
ko.react.devmyself for legacy users?Page
https://ko.react.dev
The text was updated successfully, but these errors were encountered: