Some terms in translation needs to be separated #61440

Closed
opened 2019-02-12 09:36:17 +01:00 by Michael Soluyanov · 7 comments

Some words in English may have several meanings, and this words can be translated differently. So I suggest to separate this terms, to give different translations of same word

This is a collection of this strings, that I found:

Flat

  • Projection method
  • Mesh plane (material preview)
  • Blur type
    Roughness
  • Material roughness
  • Particle's non-uniformness
    Project
  • Projection
  • Place to store proxy data
    Normal
  • Normal Direction
  • Usual / typical / default
  • Color blend mode
    New
  • Create new file (file-new)
  • Adjective for time remapping
  • Create new selection
    Keying
  • "Keyframing"
  • Keying node for compositing
    "Clip Start" and "Clip End"
  • Camera view
  • Light distance
    Translation
  • Old international fonts
  • Moving objects
    Back
  • Position (Background)
  • Interpolation type
    Emission
  • Emission of light
  • Emission of particles
Some words in English may have several meanings, and this words can be translated differently. So I suggest to separate this terms, to give different translations of same word This is a collection of this strings, that I found: Flat - Projection method - Mesh plane (material preview) - Blur type Roughness - Material roughness - Particle's non-uniformness Project - Projection - Place to store proxy data Normal - Normal Direction - Usual / typical / default - Color blend mode New - Create new file (file-new) - Adjective for time remapping - Create new selection Keying - "Keyframing" - Keying node for compositing "Clip Start" and "Clip End" - Camera view - Light distance Translation - Old international fonts - Moving objects Back - Position (Background) - Interpolation type Emission - Emission of light - Emission of particles
Author
Member

Added subscriber: @crantisz

Added subscriber: @crantisz
Bastien Montagne was assigned by Michael Soluyanov 2019-02-12 09:37:02 +01:00

Thanks for the report, but general assessments like that do not really help, we cannot separate everything in Blender. Please provide specific cases (with exact, complete message that has several meanings, and which meanings absolutely need to be separated).

Also please take in account that adding context to translations make things heavier for everybody (in the code, for the translators of every language…), so please do not be too picky here, i.e. if you can find a word/expression in your language that can convey all meanings, even if it is a bit imperfect/on the edge, use it. The less i18n contexts we use, the better it is. ;)

E.g., why 'Clip Start/End' actually has to be different for camera and light? They are basically the exact same thing - clipping a distance…

Thanks for the report, but general assessments like that do not really help, we cannot separate everything in Blender. Please provide specific cases (with exact, complete message that has several meanings, and which meanings absolutely need to be separated). Also please take in account that adding context to translations make things heavier for everybody (in the code, for the translators of every language…), so please do not be too picky here, i.e. if you can find a word/expression in your language that can convey all meanings, even if it is a bit imperfect/on the edge, use it. The less i18n contexts we use, the better it is. ;) E.g., why 'Clip Start/End' actually has to be different for camera and light? They are basically the exact same thing - clipping a distance…
Author
Member

Probably, I didn’t explain well - this is all specific cases (complete text strings) . The problem affects in general in one-word strings. So "Emission" - is problem string, "Emission color" - not. So this is exactly specific cases (complete text strings) (only "Clip Start" and "Clip End" combined in one item )

Probably, I didn’t explain well - this is all specific cases (complete text strings) . The problem affects in general in one-word strings. So "Emission" - is problem string, "Emission color" - not. So this is exactly specific cases (complete text strings) (only "Clip Start" and "Clip End" combined in one item )

Added subscriber: @GabrielGazzan

Added subscriber: @GabrielGazzan

@mont29
I know we should try to simplify things where possible, but currently there are some quite visible problems with strings being assigned in a too liberal way to different things.
At the very end of #43295 I've stated a lot of cases I've found while starting to translate 2.8 strings, some of the reports are the same as the ones in this issue.

I'll give just one example:
Light string is assigned to a "file compression method" (the opposite from 'heavy') and to "the lights" that illuminate the scene. So, currently, in Spanish when you want to add a new Light it reads Lightweight, and if I change the string to mean Lamp, when someone wants to choose between compression modes it gets Heavy and Lamp, as options. :-/
That kind of fail makes the translation look cheap (at least in Spanish) and I think we should make our best to iron them out.

If we (translators) need to specify where the issues are in a clearer way, I have absolutely no problem in dedicating time to do so.

Also, personally as a translator, I prefer having to translate 6 times the same string with different meanings, if necessary, than to see the product of all my efforts end up as a mediocre translation.

Thanks for considering it!

@mont29 I know we should try to simplify things where possible, but currently there are some quite visible problems with strings being assigned in a too liberal way to different things. At the very end of #43295 I've stated a lot of cases I've found while starting to translate 2.8 strings, some of the reports are the same as the ones in this issue. I'll give just one example: **Light** string is assigned to a "file compression method" (the opposite from 'heavy') and to "the lights" that illuminate the scene. So, currently, in Spanish when you want to add a new **Light** it reads **Lightweight**, and if I change the string to mean **Lamp**, when someone wants to choose between compression modes it gets **Heavy** and **Lamp**, as options. :-/ That kind of fail makes the translation look cheap (at least in Spanish) and I think we should make our best to iron them out. If we (translators) need to specify where the issues are in a clearer way, I have absolutely no problem in dedicating time to do so. Also, personally as a translator, I prefer having to translate 6 times the same string with different meanings, if necessary, than to see the product of all my efforts end up as a mediocre translation. Thanks for considering it!

Eeeh indeed missed your comment in #43295, best would be to merge this one there, and add additional requests from @crantisz.

Am not opposed to those changes (I also translate in French and occasionally hit that kind of issue), am just stressing that we should only fall back to context disambiguation when it is really needed, that’s all.

Eeeh indeed missed your comment in #43295, best would be to merge this one there, and add additional requests from @crantisz. Am not opposed to those changes (I also translate in French and occasionally hit that kind of issue), am just stressing that we should only fall back to context disambiguation when it is really needed, that’s all.

Closed as duplicate of #43295

Closed as duplicate of #43295
Sign in to join this conversation.
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
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#61440
No description provided.