I18n: disambiguate and extract a few messages #111146
No reviewers
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#111146
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "pioverfour/blender:dp_disambiguate"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This commit disambiguates the following messages:
places, as that is already extracted as part of the
sequencer_prop_effect_types
enum, and more specific.because this is all over the place)
It also extracts these messages:
Ref #43295
Damien Picard referenced this pull request2023-08-15 18:57:38 +02:00
Generally LGTM, some minor comments below.
@ -197,6 +198,7 @@ typedef struct {
BLT_I18NCONTEXTS_ITEM(BLT_I18NCONTEXT_ID_WORKSPACE, "id_workspace"), \
BLT_I18NCONTEXTS_ITEM(BLT_I18NCONTEXT_ID_WORLD, "id_world"), \
BLT_I18NCONTEXTS_ITEM(BLT_I18NCONTEXT_EDITOR_FILEBROWSER, "editor_filebrowser"), \
BLT_I18NCONTEXTS_ITEM(BLT_I18NCONTEXT_EDITOR_PREFERENCES, "editor_preferences"), \
See comment where it's used, think this is not needed.
@ -5135,6 +5135,7 @@ static void rna_def_userdef_view(BlenderRNA *brna)
prop, "rna_lang_enum_properties_get_no_international", nullptr, nullptr);
# endif
RNA_def_property_ui_text(prop, "Language", "Language used for translation");
RNA_def_property_translation_context(prop, BLT_I18NCONTEXT_EDITOR_PREFERENCES);
I really do not think a new context for this case is worth it... Could use instead e.g. some UI-related ID context, like
BLT_I18NCONTEXT_ID_WINDOWMANAGER
?Although I understand that that is not what the system is currently designed to solve, I still try finding contexts that will make sense to translators, and I don’t think "WindowManager" does that.
But I will change to that if you request it.
Thing is. 'user preferences' is not a really good context either... This is related to UI, so we could have a 'UI' context, but imho 'window manager' is a good 'synonym' to UI, since UI is the only role of that ID...
Actually, I just retested and this is not going to work anyway, because the language names are extracted in another way, and are used from different places.
It will be easier to actually leave them with the default context, and add a context to messages meaning “programming language”.
Ok so I went with adding a “Python console” context to refer to the programming instances. I hope that’s all right, I again couldn’t see an existing context that really made sense…
@ -122,3 +122,3 @@
return DATA_("Audio");
case SEQ_TYPE_CROSS:
return DATA_("Cross");
return CTX_DATA_(BLT_I18NCONTEXT_ID_SEQUENCE, "Cross");
Why do the above ones not need the
sequence
context too?@blender-bot build
8b40e2a396
tocabc4aa3a5
Eeh, still adding one more context in the end... But think this one makes sense then. thanks for all the fixes!
@blender-bot build