search

ryanmcdermott / clean-code-javascript

:bathtub: Clean Code concepts adapted for JavaScript
MIT License
91.21k stars 12.23k forks source link

Adding translations #445

Open fparedlo opened 9 months ago

fparedlo commented 9 months ago

What is the best way to do this ? Would it be better to send the URL to the translation via Issue or Pull request?

Should we consider opening a folder in this repository to host all translations in one repo instead of linking into others? This will also allow pull request that overwrite the original text

cksharma2468 commented 8 months ago

Hi, I think it would be better if all the translations are hosted in a separate folder as it would be easy to access for new comers.

ppYoung commented 8 months ago

亲，你的邮件东阳已经收到了

kavyamehra20 commented 8 months ago

Handling translations in a JavaScript codebase involves leveraging internationalization (i18n) libraries like i18next, react-i18next, or vue-i18n. The project structure typically includes a designated directory for locales, housing translation files such as en.json, fr.json, etc. Initialization of the i18n library involves setting up the default language and loading translations into the project. Components then implement translation using i18n functions, with popular frameworks like React utilizing hooks such as useTranslation. Dynamic language switching can be facilitated through a language switcher component. Regularly update translations by extracting new translatable strings from the codebase and using provided tools or scripts. Additionally, consider factors like pluralization and variables in translations, recognizing that different languages may have distinct rules for these elements.