TagStudioDev
Translations
Adds a translator that handles translation of objects via QCoreApplication.translate(context, key), and translations are stored as .ini files in the format:
*context*.*key*="*Translation*"
Currently has very few actually translated components, just the structure to add more.
Now that #332 has merged, this would be a great time to start separating out the strings to try using with Weblate
Strings separated in #507 I guess the best course of action would either be to:
- Merge this PR, then #507
- Add the json of strings to this PR.
Any thoughts?
@Tyrannicodin how much is left for this to be a proper PR and not a draft?
@Tyrannicodin how much is left for this to be a proper PR and not a draft?
The only missing thing is replacing all strings with translation functions, which I want to do in this pr or else it won't really add much.
Hmm, I'm not sure we need to translate logs right? They're not user-facing after all.
Definitely lower priority, but I'm in favor of translating everything.
Completely fine with just removing them as you see fit. I do not have enough knowledge of the code base (or code in general for that matter) to decide for myself what is user facing and what's not
Just wanted to bump this and check if this is still being worked on. Translations are being pulled from webplate, so the sooner we can implement those, the better. Thanks!
