-
-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Localization (translations) #307
Conversation
Add some basic translations for settings modal as proof-of-concept
* Add French translation * Fix typo * Remove \ symbol
Fr-CA will fall back to just fr now.
Restructure locale json files, Remove keys from en-US that are same as en
* Update French translation Co-authored-by: Rom <skav@gmx.fr> Co-authored-by: Nam Anh <phamnamanh25@gmail.com>
I think I've got all the strings translated and this is ready to go. Please give it a test and see if I missed anything. I'd also like to note that I left the French "dark" and "light" theme tags in English because I wasn't sure which word referred to a colour theme as opposed to somber/gloomy/etc. @xerta555 What would you use for those? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Works fine as well.
Not having any programming skills (except shell), all the projects I'm involved in for translations use i18n with sites like Crowdin, GetLocalization, OneSky, Transifex and others. |
I added i18next as the library, and added some basic translations for settings modal as a proof of concept. It can detect the language set in Spotify, so we shouldn't need to add an option for it. The translations are stored in different files, so we can have people make PRs and add/update their native language.
Working on the settings modal so far:
