The info provided by add-ons is very valuable to users, yet it wasn’t translatable yet.
Details
Details
Diff Detail
Diff Detail
- Repository
- rB Blender
Event Timeline
Comment Actions
Generally looks fine.
Would think non-official add-ons can simply add their own description etc. to their own translation file?
| release/scripts/startup/bl_ui/space_userpref.py | ||
|---|---|---|
| 1959 | not sure there is much point in translating that one? | |
| release/scripts/modules/bl_i18n_utils/bl_extract_messages.py | ||
|---|---|---|
| 928 | Would be a bit more specific here, something like this maybe? Add-on " + module.bl_info['name'] + "info: " + prop | |
Comment Actions
It works fine but I still need to update the add-on part of the I18n add-on to extract the bl_info, for convenience. But this can wait another day!
| release/scripts/startup/bl_ui/space_userpref.py | ||
|---|---|---|
| 1959 | Are you talking about the whole line, or just the "%s: %s" bit? If the whole line, then I believe most add-ons need to have their name translated, except if they have an original / fancy / brand name. And the category is already translated in the Enum, so it makes sense to translate it here as well. But maybe as a tip_, though, not sure… If the %s bit, it’s not strictly needed but it was already extracted here and in several other places anyway. It allows changing the punctuation, which is more correct (and pleasing) in French and possibly other languages (well, that’s dubious but who knows!). | |
| release/scripts/startup/bl_ui/space_userpref.py | ||
|---|---|---|
| 1959 | Was talking about the "%s: %s" part yes, but fair enough. | |
Comment Actions
Note: Will commit this to master, think it's too risky/too late for 3.3 at that point.
Comment Actions
While I was at it, I refactored slightly so that non-official add-ons could get their bl_info extracted to their translation_tuple.