I18n: write messages of the vertex group lock operator explicitly #104484
Closed
Damien Picard
wants to merge 1 commits from
When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.
pioverfour:dp_improve_lock_vertex_group into blender-v3.5-release
pull from: pioverfour:dp_improve_lock_vertex_group
merge into: blender:blender-v3.5-release
blender:main
blender:blender-v4.3-release
blender:npr-prototype
blender:blender-v3.6-release
blender:blender-v4.2-release
blender:cmbasnett/use_pass_z_name
blender:color-node-drag-and-drop
blender:temp-sculpt-dyntopo
blender:icons-cleanup
blender:blender-v3.3-release
blender:brush-assets-project
blender:pr-extensions-tidy-space
blender:blender-v4.0-release
blender:universal-scene-description
blender:blender-v4.1-release
blender:blender-v3.6-temp_wmoss_animrig_public
blender:gpencil-next
blender:blender-projects-basics
blender:bridge-curves
blender:sculpt-blender
blender:asset-browser-frontend-split
blender:asset-shelf
blender:blender-v3.5-release
blender:blender-v2.93-release
blender:sculpt-dev
blender:bevelv2
blender:xr-dev
When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.
1 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
| 40d12296cb |
I18n: write messages of the vertex group lock operator explicitly
The operator's description used a format string like:
```
BLI_sprintfN(TIP_("%s %s vertex groups of the active object"),
action_str, target_str)
```
which is almost guaranteed to be impossible to properly localize to
some languages -- I know there are a couple of issues for French
already.
So instead of hoping formatting works, write all possible strings
explicitly, even if it looks stupidly verbose.
|
