The mixed-up use of the word 'Lines' with a hidden meaning 'number of', and the original meaning #54993
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
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
EEVEE & Viewport
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
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
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
EEVEE & Viewport
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
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
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#54993
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
I'm hitting another wall with this word at the moment, negotiating the pathways to resolve these multiple meaning problems.
As listed, this world is being used in multiple places:
: scripts/startup/bl_ui/space_view3d.py:3509 # hidden 'number of'
msgid "Lines"
msgstr "(Số) Đường/Dòng"
Following are images supporting these findings:
Number of grid lines
Number of halo lines
Import of waterfront OBJ format
Calculate motion path for poses
Use this test file if you do not want to recreate
20180507_bones_motion_path_calc_0001.blend
I honestly still think the job of separating the meanings are down to the translators but there must be a mechanism allowing them to do so. This task might vary between languages.
Added subscriber: @hoanguk
Added subscriber: @lichtwerk
Why not stick to the plural? Sorry, absolutely no native speaker, but
những Dòng
wouldnt work?Otherwise, changes in a couple of places need to happen (not to speak of external documentation...)
No, if this was OK I'd have come up a solution myself already. If you've noticed my translation, I already use brackets, slashes to add possible meanings to the translation, at least allowing users to 'GUESS'. But this is, to me, a not very clean and clearcut as it should be. I've already grepped the list of all possible contexts I could use and tried
for the 'Halo' instance, but it didn't make any difference.
I do not yet know the inside working of the translation code, so this idea is just a gabbled thought in my head. Maybe all the definitions of CONTEXT strings should be placed outside, in a text file, and allowing translators to add their own definitions to it. The coding will just follow the context to insert the appropriate translation beneath it. Would this make life much easier for the translation portion of the code? I personally think I could live with this - of course, this is relating to homophones (words with multiple meanings).
There should be a tool which expose (visually) those contexts, say in translation editing mode, which allows translators to visualise the context a field (English text) is being used and be able to match their translations to that appropriately.
Changed status from 'Open' to: 'Archived'
Am sorry, but this looks much more like feature request than actual bug report, we do not handle that here. Further more, dev time for i18n aspect of the project is pretty much NULL currently, so… we’ll have to live with what we have for now.