nodejs
Internationalization Wishlist
Living list of items to consider when designing and building out the new site for internationalization (i18n), localization (l11n), translation (t9n), etc.
- [ ] Redirect to the closest available localized version of a page based on
Accept-Languageheaders or user settings. This should be done when there's no locale specified in the URL, instead of always redirecting to English (although English can be the fallback when the preferred locale version doesn't exist). Also need to address/downloadwhich I think cannot be redirected to a localized download content page (e.g./en/download). - [x] A language picker
- [ ]
hreflangmeta tags
I propose we include a related goal of verifying the content is accessible to screen-readers and/or printable as I've heard this may offer secondary benefit of being easily ingested by a translation toolkit. On that note, any QA work on the adaptive layout should include a test of the content post-translation by Chrome's embedded Google Translate utility, as things post-GT can look very-very ugly if styles mistakenly assumed character count & font size would be the same across cultures. And finally, there's got to be a tool that would force Left-to-Right appearance, so we could test our assumptions as to where the content will be for Arabic, Hebrew, etc.
Hello, I would like to help with internationalization/localization. Do you guys already have the implementation to support the internationalization of the new website?
We have some questions about how this is currently being done on the current website. Would be nice to have i18n parity but the learn docs in particular (on the new site) don't have translations.
Hello there, I really need some learning content in my classes. since this project content is amazing I want to use it, but there is no translation, there is any plan to add i18n to the project? I can help with a translation in persian. Google translation is really bad with persian!
Going to check regarding the Accept Language header and see if we can do something about this on React level. But not 100% sure about it.
