Spanish translation | Some other issues with the preferences area #102071

Closed
opened 2022-10-26 06:59:27 +02:00 by Carlos · 13 comments

System Information
Operating system: Linux-6.0.2-2-MANJARO-x86_64-with-glibc2.36 64 Bits
Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06

Blender Version
Broken: version: 3.4.0 Alpha and 3.3.1, branch: makepkg (modified), commit date: 2022-10-04 18:35, hash: b292cfe5a9
Worked: (?)

Short description of error
Screen is translated as "Trama" (there is no relation it means plot, weave, weft ) the right one is "Pantalla".
The left is the 3.3 in English for comparison but also the text in magenta in the 3.4 is not translated to Spanish.
image.png
I don't know if this options could be translated or not, but only a few are translated image.png
I know the translation is not an easy job, I just want to help you and the community.
Thank you!

**System Information** Operating system: Linux-6.0.2-2-MANJARO-x86_64-with-glibc2.36 64 Bits Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 520.56.06 **Blender Version** Broken: version: 3.4.0 Alpha and 3.3.1, branch: makepkg (modified), commit date: 2022-10-04 18:35, hash: `b292cfe5a9` Worked: (?) **Short description of error** Screen is translated as "Trama" (there is no relation it means plot, weave, weft ) the right one is "Pantalla". The left is the 3.3 in English for comparison but also the text in magenta in the 3.4 is not translated to Spanish. ![image.png](https://archive.blender.org/developer/F13770793/image.png) I don't know if this options could be translated or not, but only a few are translated ![image.png](https://archive.blender.org/developer/F13770838/image.png) I know the translation is not an easy job, I just want to help you and the community. **Thank you!**
Author

Added subscriber: @Confabulatori

Added subscriber: @Confabulatori
Member

Added subscriber: @GabrielGazzan

Added subscriber: @GabrielGazzan

Added subscriber: @pioverfour

Added subscriber: @pioverfour

Trama vs Pantalla is one of the known problems, caused by the same text string used for the meanings of:

  • Computer Screen = Pantalla
    and
  • Screen Blending Mode = Trama

I recall recent work on sorting out other occurrences of this problem by @pioverfour
but there still seems to be one or two misplaced messages left:

These are the functions currently translated by that string:

  • . :src: bpy.types.ColorMapping.blend_type:'SCREEN'
  • . :src: bpy.types.GPencilStroke.display_mode:'SCREEN'
  • . :src: bpy.types.Brush.blend:'SCREEN'
  • . :src: bpy.types.LineStyleColorModifier_AlongStroke.blend:'SCREEN'
  • . :src: bpy.types.LineStyleColorModifier_CreaseAngle.blend:'SCREEN'
  • . :src: bpy.types.LineStyleColorModifier_Curvature_3D.blend:'SCREEN'
  • . :src: bpy.types.LineStyleColorModifier_DistanceFromCamera.blend:'SCREEN'
  • . :src: bpy.types.LineStyleColorModifier_DistanceFromObject.blend:'SCREEN'
  • . :src: bpy.types.LineStyleColorModifier_Material.blend:'SCREEN'
  • . :src: bpy.types.LineStyleColorModifier_Noise.blend:'SCREEN'
  • . :src: bpy.types.LineStyleColorModifier_Tangent.blend:'SCREEN'
  • . :src: bpy.types.CompositorNodeMixRGB.blend_type:'SCREEN'
  • . :src: bpy.types.ShaderNodeMix.blend_type:'SCREEN'
  • . :src: bpy.types.ShaderNodeMixRGB.blend_type:'SCREEN'
  • . :src: bpy.types.ShaderNodeOutputLineStyle.blend_type:'SCREEN'
  • . :src: bpy.types.TextureNodeMixRGB.blend_type:'SCREEN'
  • . :src: bpy.types.Sequence.blend_type:'SCREEN'
  • . :src: bpy.types.ColorMixSequence.blend_effect:'SCREEN'
  • . :src: bpy.types.TextureSlot.blend_type:'SCREEN'
  • : source/blender/nodes/composite/nodes/node_composite_keyingscreen.cc:33
    msgid "Screen"
    msgstr "Trama"

I see

: source/blender/nodes/composite/nodes/node_composite_keyingscreen.cc:33

that's causing a problem in the Keying Screen node "Screen" output connector label.
But I can't manage to see, where's the link from this string to the "Screen" label in Preferences > Keymap, as shown in the first image above.

Thanks for pointing it out!

Trama vs Pantalla is one of the known problems, caused by the same text string used for the meanings of: - Computer Screen = Pantalla and - Screen Blending Mode = Trama I recall recent work on sorting out other occurrences of this problem by @pioverfour but there still seems to be one or two misplaced messages left: These are the functions currently translated by that string: - . :src: bpy.types.ColorMapping.blend_type:'SCREEN' - . :src: bpy.types.GPencilStroke.display_mode:'SCREEN' - . :src: bpy.types.Brush.blend:'SCREEN' - . :src: bpy.types.LineStyleColorModifier_AlongStroke.blend:'SCREEN' - . :src: bpy.types.LineStyleColorModifier_CreaseAngle.blend:'SCREEN' - . :src: bpy.types.LineStyleColorModifier_Curvature_3D.blend:'SCREEN' - . :src: bpy.types.LineStyleColorModifier_DistanceFromCamera.blend:'SCREEN' - . :src: bpy.types.LineStyleColorModifier_DistanceFromObject.blend:'SCREEN' - . :src: bpy.types.LineStyleColorModifier_Material.blend:'SCREEN' - . :src: bpy.types.LineStyleColorModifier_Noise.blend:'SCREEN' - . :src: bpy.types.LineStyleColorModifier_Tangent.blend:'SCREEN' - . :src: bpy.types.CompositorNodeMixRGB.blend_type:'SCREEN' - . :src: bpy.types.ShaderNodeMix.blend_type:'SCREEN' - . :src: bpy.types.ShaderNodeMixRGB.blend_type:'SCREEN' - . :src: bpy.types.ShaderNodeOutputLineStyle.blend_type:'SCREEN' - . :src: bpy.types.TextureNodeMixRGB.blend_type:'SCREEN' - . :src: bpy.types.Sequence.blend_type:'SCREEN' - . :src: bpy.types.ColorMixSequence.blend_effect:'SCREEN' - . :src: bpy.types.TextureSlot.blend_type:'SCREEN' - : source/blender/nodes/composite/nodes/node_composite_keyingscreen.cc:33 msgid "Screen" msgstr "Trama" I see # : source/blender/nodes/composite/nodes/node_composite_keyingscreen.cc:33 that's causing a problem in the Keying Screen node "Screen" output connector label. But I can't manage to see, where's the link from this string to the "Screen" label in Preferences > Keymap, as shown in the first image above. Thanks for pointing it out!
Author

Screen Blending Mode = Trama

Yes thank you, this is also wrong, is "Pantalla" as well. I didn't remember where I had seen it, is in the rgb mix node, this need to be changed. Just like screen in English, Pantalla in Spanish there is no difference, neither for the fusion/mix mode nor for the area in the interface. Is this way in Inkscape, Krita, Gimp and others.

It appears when you search for the "z" key binding.

> Screen Blending Mode = Trama Yes thank you, this is also wrong, is "Pantalla" as well. I didn't remember where I had seen it, is in the rgb mix node, this need to be changed. Just like screen in English, Pantalla in Spanish there is no difference, neither for the fusion/mix mode nor for the area in the interface. Is this way in Inkscape, Krita, Gimp and others. It appears when you search for the "z" key binding.

Well, I wholeheartedly disagree on that one.
"Trama" is the standard translation for "Screen" blending mode in any image editor software, starting with Photoshop.
And so, is what every user would expect to find among the usual image blending modes available.

Here's an excerpt of Photoshop documentation:
imagen.png imagen.png

Well, I wholeheartedly disagree on that one. "Trama" is the standard translation for "Screen" blending mode in any image editor software, starting with Photoshop. And so, is what every user would expect to find among the usual image blending modes available. Here's an excerpt of Photoshop documentation: ![imagen.png](https://archive.blender.org/developer/F13778611/imagen.png) ![imagen.png](https://archive.blender.org/developer/F13778685/imagen.png)
Member

I know the translation is not an easy job, I just want to help you and the community.

It’s much apprieciated!

In #102071#1437730, @GabrielGazzan wrote:
I see
#: source/blender/nodes/composite/nodes/node_composite_keyingscreen.cc:33
that's causing a problem in the Keying Screen node "Screen" output connector label.

This is impossible to disambiguate for now, because individual node sockets can’t have a specific context. I tried to fix it but the fix was bad and it was rejected. I’m hoping to revisit it once the general node system has progressed.

But I can't manage to see, where's the link from this string to the "Screen" label in Preferences > Keymap, as shown in the first image above.

My impression is that keymap names are not extracted at all, so only those which are already extracted elsewhere can be translated, and context collisions can happen, as in the case of Trama.
This needs to be fixed, adding to the list.

>I know the translation is not an easy job, I just want to help you and the community. It’s much apprieciated! > In #102071#1437730, @GabrielGazzan wrote: > I see > #: source/blender/nodes/composite/nodes/node_composite_keyingscreen.cc:33 > that's causing a problem in the Keying Screen node "Screen" output connector label. This is impossible to disambiguate for now, because individual node sockets can’t have a specific context. I tried to fix it but the fix was bad and it was rejected. I’m hoping to revisit it once the general node system has progressed. > But I can't manage to see, where's the link from this string to the "Screen" label in Preferences > Keymap, as shown in the first image above. My impression is that keymap names are not extracted *at all*, so only those which are already extracted elsewhere can be translated, and context collisions can happen, as in the case of *Trama*. This needs to be fixed, adding to the list.
Author

"Trama" is the standard translation for "Screen" blending mode in any image editor software, starting with Photoshop.

Yes this is the standard but only for Photoshop.

Da Vinci Resolve
image.png

Inkscape
image.png

Krita
image.png

Gimp
image.png

Anyway naming the mix as "Pantalla" will make it easy in case you agree (no more trama interference)

> "Trama" is the standard translation for "Screen" blending mode in any image editor software, starting with Photoshop. > Yes this is the standard but only for Photoshop. Da Vinci Resolve ![image.png](https://archive.blender.org/developer/F13781904/image.png) Inkscape ![image.png](https://archive.blender.org/developer/F13781931/image.png) Krita ![image.png](https://archive.blender.org/developer/F13781951/image.png) Gimp ![image.png](https://archive.blender.org/developer/F13781963/image.png) Anyway naming the mix as "Pantalla" will make it easy in case you agree (no more trama interference)

I have two things to say about that:

  1. DaVinci Resolve doesn't have a Spanish UI. The capture you posted here is from a Guide document that is translated into Spanish, but not from an official part of the software.
  2. I don't know the persons that translate the other open source software you mention here, and although I must respect their effort as much as mine, I must assume they are volunteers like me, I must also asume they could be wrong as me, and I must asume that if they don't know much about what part of the software they were translating (sometimes it happens) or if there are technical disambiguation restrictions in their softare like in Blender, then the most direct word that comes to mind when you see Screen is of course Pantalla, so they could have done it wrong and even don't know about it or can't do anything to disambiguate both cases.

On the other hand, Adobe has a tremendous impact on the user base (i.e. a vast majority of professional users use their products on a daily basis), so if they are working with that term, I think that's the word I will choose too, so they find comfortable in Blender as well.

I have two things to say about that: 1. DaVinci Resolve doesn't have a Spanish UI. The capture you posted here is from a Guide document that is translated into Spanish, but not from an official part of the software. 2. I don't know the persons that translate the other open source software you mention here, and although I must respect their effort as much as mine, I must assume they are volunteers like me, I must also asume they could be wrong as me, and I must asume that if they don't know much about what part of the software they were translating (sometimes it happens) or if there are technical disambiguation restrictions in their softare like in Blender, then the most direct word that comes to mind when you see Screen is of course Pantalla, so they could have done it wrong and even don't know about it or can't do anything to disambiguate both cases. On the other hand, Adobe has a tremendous impact on the user base (i.e. a vast majority of professional users use their products on a daily basis), so if they are working with that term, I think that's the word I will choose too, so they find comfortable in Blender as well.

This issue was referenced by 83c21e01dd

This issue was referenced by 83c21e01dd9a8a14ce157285e3060d15d89904c7
Member

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
Member

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'
Damien Picard self-assigned this 2022-12-06 17:43:28 +01:00
Member

Mostly fixed in 83c21e01dd. The remaining issue is the “Trama” or “Pantalla” blending mode in Spanish, but I don’t think this task will help settle it.

Mostly fixed in 83c21e01dd. The remaining issue is the “Trama” or “Pantalla” blending mode in Spanish, but I don’t think this task will help settle it.
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
5 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#102071
No description provided.