Japanese translation | "Wrong" translation (Value) #105113

Open
opened 2023-02-23 07:52:52 +01:00 by hainarashi · 23 comments

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49

Blender Version
Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: rB55485cb379f7
Worked: (newest version of Blender that worked as expected)

The Japanese translations of "Value" are "値" and "明度" depending on the context.
The correct translation for "Value" in the Color Picker and Hue Saturation Value Node is "明度".
"値" and "輝度" are incorrect translations.

On the other hand, "値" is the correct translation for the Value Node, so there is no need to correct it as it is now.

Thank you!


  • Color Picker: Value input field
  • Separate and Combine nodes, HSL mode: Lightess input socket
  • Separate and Combine nodes, HSV mode: Value input socket
  • HSV node: Value in title
  • HSV node: Value input socket
**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49 **Blender Version** Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: `rB55485cb379f7` Worked: (newest version of Blender that worked as expected) The Japanese translations of "Value" are "値" and "明度" depending on the context. The correct translation for "Value" in the Color Picker and Hue Saturation Value Node is "明度". "値" and "輝度" are incorrect translations. On the other hand, "値" is the correct translation for the Value Node, so there is no need to correct it as it is now. Thank you! ----- - [x] Color Picker: Value input field - [x] Separate and Combine nodes, HSL mode: Lightess input socket - [ ] Separate and Combine nodes, HSV mode: Value input socket - [x] HSV node: Value in title - [x] HSV node: Value input socket
hainarashi added the
Priority
Normal
Status
Needs Triage
Type
Report
labels 2023-02-23 07:52:52 +01:00
Damien Picard added
Status
Confirmed
and removed
Status
Needs Triage
labels 2023-02-23 17:50:37 +01:00
Member

Hi, unfortunately this isn’t something that can be easily fixed right now, because there is no way to specify a different translation for node sockets (translation contexts).

I made a proposition a while ago to solve this, but it was not good enough.

I’m hoping we can solve it in the future!

Hi, unfortunately this isn’t something that can be easily fixed right now, because there is no way to specify a different translation for node sockets (translation contexts). I made [a proposition](https://archive.blender.org/developer/D15869) a while ago to solve this, but it was not good enough. I’m hoping we can solve it in the future!
Author

Thanks for your comment.

there is no way to specify a different translation for node sockets (translation contexts).

Understood.
On top of that, I have two suggestions.

Before Blender 3.3, Color Picker parameters were written as "H,S,V" in English.
In this case, there was no confusion because they are also written as "H,S,V" in Japanese.
In 3.4, the "H,S,V" was changed to "Hue Saturation Value", resulting in confusion in the translation of the "Value".
So is it possible to revert back to "H,S,V" in English?

The node names for the Hue Saturation Value Node in Japanese are incorrectly translated.

  • correct : 色相/彩度/明度
  • incorrect : 色相/彩度/輝度
    This is not node sockets, can it be fixed?
Thanks for your comment. > there is no way to specify a different translation for node sockets (translation contexts). Understood. On top of that, I have two suggestions. 1. Before Blender 3.3, Color Picker parameters were written as "H,S,V" in English. In this case, there was no confusion because they are also written as "H,S,V" in Japanese. In 3.4, the "H,S,V" was changed to "Hue Saturation Value", resulting in confusion in the translation of the "Value". So is it possible to revert back to "H,S,V" in English? 2. The node names for the Hue Saturation Value Node in Japanese are incorrectly translated. - correct : 色相/彩度/明度 - incorrect : 色相/彩度/輝度 This is not node sockets, can it be fixed?
Member

I’ll have a look about the color picker. The best solution would be to make it properly translatable, rather than revert.

For the HSV node, I don’t speak Japanese, so this should be handled by the Japanese translator, @SatoshiYamasaki.

I’ll have a look about the color picker. The best solution would be to make it properly translatable, rather than revert. For the HSV node, I don’t speak Japanese, so this should be handled by the Japanese translator, @SatoshiYamasaki.

@hainarashi Thank you for the report.
The word "Value" is used in many areas as 「値」(atai). so it should be separated by using msgctxt tag to solve the issue.

@pioverfour Thank you for telling.
Could you please add the msgctxt for it or do you have any idea?

@hainarashi Thank you for the report. The word "Value" is used in many areas as 「値」(atai). so it should be separated by using msgctxt tag to solve the issue. @pioverfour Thank you for telling. Could you please add the msgctxt for it or do you have any idea?
Member

@SatoshiYamasaki I’m just now adding it for the color picker, but for the nodes I can’t do it currently as the node system doesn’t allow it.

As far as I can see, @hainarashi is right and 色相/彩度/輝度 can be fixed without a new context.

@SatoshiYamasaki I’m just now adding it for the color picker, but for the nodes I can’t do it currently as the node system doesn’t allow it. As far as I can see, @hainarashi is right and 色相/彩度/輝度 can be fixed without a new context.

@hainarashi Other strings (E.g. "Hue Saturation Value" node that you uploaded above) will be fixed and committed soon.

@hainarashi Other strings (E.g. "Hue Saturation Value" node that you uploaded above) will be fixed and committed soon.

@pioverfour Thank you!
"色相/彩度/輝度(Hue Saturation Value)" and other strings which can be fixed by pot file are fixed now.

@pioverfour Thank you! "色相/彩度/輝度(Hue Saturation Value)" and other strings which can be fixed by pot file are fixed now.
Author

@pioverfour @SatoshiYamasaki Thank you for the support!
Just to confirm, does this mean that the following will be corrected?

  • Color Picker : Fix from "値" to "明度".
  • "Hue Saturation Value" node name : Fix from "色相/彩度/輝度" to "色相/彩度/明度".
  • "Hue Saturation Value" node parameters : Not allowed by node system, expect future resolution.
@pioverfour @SatoshiYamasaki Thank you for the support! Just to confirm, does this mean that the following will be corrected? - Color Picker : Fix from "値" to "明度". - "Hue Saturation Value" node name : Fix from "色相/彩度/輝度" to "色相/彩度/明度". - "Hue Saturation Value" node parameters : Not allowed by node system, expect future resolution.
Member

@hainarashi That is correct, the node name was fixed already, the color picker should be in time for 3.5, and the node sockets will hopefully be fixed for 3.6 depending on how fast #105195 is accepted.

@hainarashi That is correct, the node name was fixed already, the color picker should be in time for 3.5, and the node sockets will hopefully be fixed for 3.6 depending on how fast #105195 is accepted.
Author

@pioverfour I understand.
Thank you very much!

@pioverfour I understand. Thank you very much!

@hainarashi

"Hue Saturation Value" node name : Fix from "色相/彩度/輝度" to "色相/彩度/明度".

For now, if you want to see this fix, you can download the "ja.mo" file from the link below and rename it to "blender.mo" and copy it in the locale data folder of 3.5 beta build (installed dir\3.5\detafiles\locale\ja\LC_MESSAGES).

https://svn.blender.org/svnroot/bf-translations/branches/ja

Thanks,

@hainarashi > "Hue Saturation Value" node name : Fix from "色相/彩度/輝度" to "色相/彩度/明度". For now, if you want to see this fix, you can download the "ja.mo" file from the link below and rename it to "blender.mo" and copy it in the locale data folder of 3.5 beta build (installed dir\3.5\detafiles\locale\ja\LC_MESSAGES). https://svn.blender.org/svnroot/bf-translations/branches/ja Thanks,
Author

@SatoshiYamasaki
I am not in a hurry and will confirm this at the stable builde release.
Thanks for letting me know.

@SatoshiYamasaki I am not in a hurry and will confirm this at the stable builde release. Thanks for letting me know.
Damien Picard self-assigned this 2023-03-02 20:03:48 +01:00
Author

@pioverfour @SatoshiYamasaki Additional information.
Combine Color Node had a similar misinterpretation.

  • HSV "Value" / correct : 明度 , incorrect : 値
  • HSL "Lightness" / correct : 輝度 , incorrect : 明るさ
    When Node sockets are fixed, please correct these as well.

Combine Color.jpg

@pioverfour @SatoshiYamasaki Additional information. Combine Color Node had a similar misinterpretation. - HSV "Value" / correct : 明度 , incorrect : 値 - HSL "Lightness" / correct : 輝度 , incorrect : 明るさ When Node sockets are fixed, please correct these as well. ![Combine Color.jpg](/attachments/f90c50ee-a854-426e-80f3-bc62ca1fcb37)

@hainarashi Thank you for the report.
"Lightness" is just fixed with editing the ja.po file, but "Value" is needed more work.

@pioverfour Please check about it...

@hainarashi Thank you for the report. "Lightness" is just fixed with editing the ja.po file, but "Value" is needed more work. @pioverfour Please check about it...
Member

I can’t fix node sockets right now. The pull request to add contexts to sockets has been accepted, but it will not be usable until 3.6. So some translations will be available after 3.5 is out, in about one month.

However, I noticed another problem with some nodes which use yet another system to display their texts: the Separate and Combine nodes use a strange system of labels I’ll have to study to know how it can be fixed :/

@hainarashi Just to be sure, were you able to fix the color picker?

I can’t fix node sockets right now. The pull request to add contexts to sockets has been accepted, but it will not be usable until 3.6. So some translations will be available after 3.5 is out, in about one month. However, I noticed another problem with some nodes which use yet another system to display their texts: the Separate and Combine nodes use a strange system of labels I’ll have to study to know how it can be fixed :/ @hainarashi Just to be sure, were you able to fix the color picker?
Author

@pioverfour @SatoshiYamasaki
I have confirmed the following versions.
blender-3.5.0-beta+v35.89c3ead7c6d8-windows.amd64-release
(I downloaded it from the Daily Builds page just a few minutes ago.)

Looks like it is in the middle of a fix.
It shows "Value" instead of "明度".

Color Picker_3.5.0beta.png

@pioverfour @SatoshiYamasaki I have confirmed the following versions. blender-3.5.0-beta+v35.89c3ead7c6d8-windows.amd64-release (I downloaded it from the Daily Builds page just a few minutes ago.) Looks like it is in the middle of a fix. It shows "Value" instead of "明度". ![Color Picker_3.5.0beta.png](/attachments/3a08788e-634c-488e-980f-743cac0700a0)
Member

Ah yes of course! It should be available next week, when the translations are updated.

Ah yes of course! It should be available next week, when the translations are updated.

@pioverfour

I can’t fix node sockets right now

Oops, I remember you mentioned it before...Sorry.

@hainarashi
The color picker will be fixed next tuesday because language files of trunk are updated every monday.

@pioverfour > I can’t fix node sockets right now Oops, I remember you mentioned it before...Sorry. @hainarashi The color picker will be fixed next tuesday because language files of trunk are updated every monday.
Author

Okay, I will check back with you next Tuesday.

Okay, I will check back with you next Tuesday.
Author

I have confirmed that the following three items were fixed.

  • Color Picker : Fixed from "値" to "明度"
  • Combine Color node (HSL) "Lightness" : Fixed from "明るさ" to "輝度"
  • "Hue Saturation Value" node name : Fixed from "色相/彩度/輝度" to "色相/彩度/明度"

Thank you very much!

20230308.jpg

I have confirmed that the following three items were fixed. * Color Picker : Fixed from "値" to "明度" * Combine Color node (HSL) "Lightness" : Fixed from "明るさ" to "輝度" * "Hue Saturation Value" node name : Fixed from "色相/彩度/輝度" to "色相/彩度/明度" Thank you very much! ![20230308.jpg](/attachments/841c22a3-0805-4cf1-a672-4ed6e32a6d62)
Philipp Oeser added
Module
User Interface
and removed
Interest
User Interface
labels 2023-03-17 14:43:05 +01:00
Member

Hi, a fix was merged for the Value input socket of the HSV node.
The HSV mode of the Separate and Combine nodes will probably not be fixed soon.

Hi, a fix was merged for the Value input socket of the HSV node. The HSV mode of the Separate and Combine nodes will probably not be fixed soon.
Author

@Damien Picard Okay,I understand.
Thank you very much!

@Damien Picard Okay,I understand. Thank you very much!

@pioverfour Thank you for the fix!:)

@pioverfour Thank you for the fix!:)
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#105113
No description provided.