Translations for Asset Browser are incorrect #107895
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#107895
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
Blender Version
Broken: (blender-3.6.0-alpha+main.225d111357b3)
Hi, they are not bugs, but I noticed following things about the Asset Browser:
In pot file, there are some names and describes for procedual hair curves assets such as "Attach Hair Curves to Surface" or "Attaches hair curves to a surface mesh", but they don't be shown in tooltips...Where are they shown in blender?
Now, asset tags are translated in Asset Browser, but I think they shouldn't be translated like other data type such as material names.
Thanks,
I see no issue with translating bundled assets (and their descriptions). In any case as you said, this is not a bug and this tracker is only for bugs and errors, so will close this issue.
Translations are provided and managed by community, whether some text is translatable is different issue, but still not a bug. I would treat it as feature request
Hi @iss, I do some i18n on Blender.
The tracker is a very convenient way to communicate about this sort of i18n issue. Text which is not translatable but should, or the other way around, can in many cases be considered a bug actually. It often happens because most developers are not even aware that there is something wrong with the translation, because they don’t use it themselves.
Satoshi is a translator for Japanese so they know how the translation and i18n work. Having people do i18n checks is important for non-English speakers, please don’t discourage that.
Now I don’t think there is an official stance on whether i18n issues are bugs or feature requests, but they can be usually reported in #43295, which Satoshi did after this issue was closed.
@pioverfour Thanks for clarification, next time I will check with you on these issues, or will deffer to #43295
My reasoning was, that since there is no module for translations I could assign this report to, it would be lost between another 700 reports (UI module).
@iss I regularly check the Translations label, but unfortunately I couldn’t find a way to subscribe to it to get notified. But yeah, I will usually end up noticing these issues.
Thanks :)
@pioverfour
Thank you for explanation. I should'nt post this report here...I thought this problem was not suitable for the "Translation disambiguation requests" page.
@SatoshiYamasaki Well, at first that issue was only for disambiguation, but it was since repurposed for all translation issues, so that they can all be tracked in the same place. But creating new translation issues is all right as well in my opinion.
@pioverfour Thank you for the suggestion. For now, it's best place for both translators and developers. :-)