-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Prepare translatable strings #455
Conversation
translation facilities. Changed translatable messages with arguments to use string.format for one complete string versus snippets. Removed gen_i18n_mo since we will be using darktable's translation facilities and there's no need to generate lua specific mo files.
contrib/LabelsToTags.lua
Outdated
["*****4"] = { "Four stars", "Not rejected" }, | ||
["*****5"] = { "Five stars", "Not rejected" }, | ||
["*****R"] = { "Rejected" } } | ||
[_("Colors")] = { ["+*****"] = { _("Red") }, |
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.
Just a quick look, I think all strings should be lower-case.
- Ensure that identical string on dt side will be used to translation
- Ensure consistent UI for standard dt
- The English capitalized UI is now handled as a separate translation and maintained by @victoryforce.
There is many strings like this on this PR.
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.
I lower cased all strings except for things such as status (ERROR/SUCCESS), file types (HTML, KML, KMZ), script names, darktable variables in strings (i.e. $(FILE_NAME))
handle the translations yet. In 5.0 this will be removed and darktable will handle translating the strings.
Prepare the lua scripts for inclusion in the darktable translation workflow.
Partially fixes #451