Rolling Shutter Type: "Top to Bottom" option using wrong string #47369

Closed
opened 2016-02-09 08:55:35 +01:00 by Gabriel Gazzán · 10 comments

Currently assigned to the same string used by Stereo 3D Display Mode "Top-Bottom".
Should be using Render Settings Tile Order "Top to Bottom" string instead.
That way it should get a more appropriate translation.

Thanks!

Currently assigned to the same string used by Stereo 3D Display Mode "Top-Bottom". Should be using Render Settings Tile Order "Top to Bottom" string instead. That way it should get a more appropriate translation. Thanks!
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @GabrielGazzan

Added subscriber: @GabrielGazzan

Added subscribers: @mont29, @Sergey

Added subscribers: @mont29, @Sergey
Bastien Montagne was assigned by Sergey Sharybin 2016-02-09 09:54:49 +01:00

While i'm fine with changing the label, it might cause other conflicts in translations. Afraid we have to define some sort of translation context here, @mont29 knows how.

Bastien, you're the translation boss, will leave it up to you to decide if we need extra con text here or not. And feel free to simply change the label. (be aware that more shutter types could be added in the future, like Bottom-Top or Left-Right).

While i'm fine with changing the label, it might cause other conflicts in translations. Afraid we have to define some sort of translation context here, @mont29 knows how. Bastien, you're the translation boss, will leave it up to you to decide if we need extra con text here or not. And feel free to simply change the label. (be aware that more shutter types could be added in the future, like Bottom-Top or Left-Right).

We can add BLT_I18NCONTEXT_ID_IMAGE context to the stereo3D stuff e.g.

But @GabrielGazzan I wonder, why can't you use same translation in both cases here? This is just a label name, imho can be translated literally and we are done (precise description of what it means is in tooltip anyway)? E.g. I just used 'Haut-bas' in french, can’t 'Alto-bajo' be enough in spanish?

We can add `BLT_I18NCONTEXT_ID_IMAGE` context to the stereo3D stuff e.g. But @GabrielGazzan I wonder, why can't you use same translation in both cases here? This is just a label name, imho can be translated literally and we are done (precise description of **what** it means is in tooltip anyway)? E.g. I just used 'Haut-bas' in french, can’t 'Alto-bajo' be enough in spanish?
Author
Member

Well, it's simple,
The string currently used is already used to describe a spacial disposition where one image sits atop of the other, whereas the other one represents an showing order, where things appear first from the top part and the progress down to the bottom part of the screen.

So, in the case of translations, one string is translated as "Superior - Inferior" (as in a "Top-Bottom" layout), whereas the other string is translated as "De arriba a abajo" (as in "From top to bottom").
It's really not the same, and being that strings with both meanings are already present, I think it'd be more appropriate to use de correct one.

Plus, there are already accompanying strings present for all the other possibilities (Bottom to top, Left to right, Right to left), so no need to worry about that either.

Thanks!

Well, it's simple, The string currently used is already used to describe a spacial disposition where one image sits atop of the other, whereas the other one represents an showing order, where things appear first from the top part and the progress down to the bottom part of the screen. So, in the case of translations, one string is translated as "Superior - Inferior" (as in a "Top-Bottom" layout), whereas the other string is translated as "De arriba a abajo" (as in "From top to bottom"). It's really not the same, and being that strings with both meanings are already present, I think it'd be more appropriate to use de correct one. Plus, there are already accompanying strings present for all the other possibilities (Bottom to top, Left to right, Right to left), so no need to worry about that either. Thanks!

Meh… I’m still not convinced here, often have the feeling translators are trying to be too smart for labels… Yes, superior-inferior is not exactly the same as arriba-abajo - but they totally convey the same “global meaning”. Otherwise, you could also argue that in english, we should also use 'upper - lower' for the layout, e.g.

What I’m trying to say here is that precision of labels is not really important, they are kind of codes/conventions anyway (aside from a few exceptions, you cannot describe what an operator does, or what a setting affects, in only one or two words), as long as they convey the correct general meaning it’s OK. Precise description of what it is about shall be kept for tooltips.

Otherwise, we can as well give each widget its own context! ;)

Meh… I’m still not convinced here, often have the feeling translators are trying to be too smart for **labels**… Yes, superior-inferior is not exactly the same as arriba-abajo - but they totally convey the same “global meaning”. Otherwise, you could also argue that in english, we should also use 'upper - lower' for the layout, e.g. What I’m trying to say here is that precision of labels is not really important, they are kind of codes/conventions anyway (aside from a few exceptions, you cannot describe what an operator does, or what a setting affects, in only one or two words), as long as they convey the correct general meaning it’s OK. Precise description of what it is about shall be kept for tooltips. Otherwise, we can as well give each widget its own context! ;)
Author
Member

Hi Bastien,
I you know a appreciate you and all the effort you a re putting into Blender.

But, honestly, here (and besides the technical issues that escapes me, in doing that change) you are not being clear at all.
We have the correct strings in place, but we are using others not as suitable as these ones.
This is just plain silly.
In English its also not the same, that's (I suppose) the very reason two different sets of strings exists?

I did my job reporting it, I will bother no more with this.
But please note you are discouraging those translators that "take their jobs too much seriously" by taking decisions that in the end make a poorer translation of the program.
I try to do my best to obtain a truly understandable translation of Blender, but with decisions like this one.... man... it makes me reconsider if anyone is taking translations as a valuable thing.
Perhaps I should stop using my sparse free time with this and use it in other things more rewarding... :-/

best regards

Hi Bastien, I you know a appreciate you and all the effort you a re putting into Blender. But, honestly, here (and besides the technical issues that escapes me, in doing that change) you are not being clear at all. We have the correct strings in place, but we are using others not as suitable as these ones. This is just plain silly. In English its also not the same, that's (I suppose) the very reason two different sets of strings exists? I did my job reporting it, I will bother no more with this. But please note you are discouraging those translators that "take their jobs too much seriously" by taking decisions that in the end make a poorer translation of the program. I try to do my best to obtain a truly understandable translation of Blender, but with decisions like this one.... man... it makes me reconsider if anyone is taking translations as a valuable thing. Perhaps I should stop using my sparse free time with this and use it in other things more rewarding... :-/ best regards

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

Don’t know why you take it like that, I never said anywhere that you were "taking your jobs too much seriously"… Your report is not invalid or wrong, it’s just too picky for our current goal in level of support of this feature - otherwise, as already said, we’ll end up adding contexts everywhere, which is not desired currently. Some fuzzyness in labels' translations is accepted (similar to fuzzyness of original english labels, not more nor less).

And I’m a bit tired of people’s susceptibility these days too, time to close this.

Don’t know why you take it like that, I never said anywhere that you were "taking your jobs too much seriously"… Your report is not invalid or wrong, it’s just too picky for our current goal in level of support of this feature - otherwise, as already said, we’ll end up adding contexts everywhere, which is not desired currently. Some fuzzyness in labels' translations is accepted (similar to fuzzyness of original english labels, not more nor less). And I’m a bit tired of people’s susceptibility these days too, time to close this.
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#47369
No description provided.