jpass- Adds user-selected language feature#32
jpass- Adds user-selected language feature#32octavo-dev wants to merge 36 commits intogaborbata:masterfrom
Conversation
src/main/resources/resources/languages/languages_hu_HU.properties
Outdated
Show resolved
Hide resolved
src/main/resources/resources/languages/languages_it_IT.properties
Outdated
Show resolved
Hide resolved
|
Thanks for your changes, I'll review them in the following weeks (depending on job activities). |
src/main/resources/resources/languages/languages_it_IT.properties
Outdated
Show resolved
Hide resolved
src/main/resources/resources/languages/languages_it_IT.properties
Outdated
Show resolved
Hide resolved
| if (instance == null) { | ||
| String languageTag = Configuration.getInstance().get("language.languageSetting", "en-US"); | ||
| instance = new JPassFrame(fileName, Locale.forLanguageTag(languageTag)); | ||
| String languageTag = Configuration.getInstance().get(LANGUAGE_LANGUAGE_SETTING, null); |
There was a problem hiding this comment.
Why don't you simply use Configuration.getInstance().get(LANGUAGE_LANGUAGE_SETTING, "en-US") here?
| panel.unencryptedDataWarningMessage=Please note that all data will be stored unencrypted.\nMake sure you keep the exported file in a secure location. | ||
|
|
||
| language.languageChanged=Language has changed successfully. | ||
| language.en.us=English |
There was a problem hiding this comment.
I don't think it is a good idea to store language names in language resources. Every time a new translation in introduced, then all the resources need to be updated. Maybe it would be better to hard-code them in the supported languages map.
There was a problem hiding this comment.
I added them on the language resource because language names change on each language so they have to be actually translated. It's true that with every new language all the current languages resources needs to add this new language name but I believe it's expected.
Let me know if you want it to change it anyway.
…o user_selected
This PR introduces: