[PR #53] [MERGED] docs(ja): Translate "Conditioning" to "条件付け" (Conditioning) #64

New issue

Closed

opened 2026-10-26 22:08:38 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-26 22:08:38 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/Comfy-Org/embedded-docs/pull/53
Author: @kaitas
Created: 8/15/2025
Status: ✅ Merged
Merged: 8/15/2025
Merged by: @christian-byrne

Base: main ← Head: main

📝 Commits (1)

fe01141 docs(ja): 「コンディショニング」を「条件付け」に統一

📊 Changes

13 files changed (+57 additions, -59 deletions)

View changed files

📝 .gitignore (+1 -0)
📝 comfyui_embedded_docs/docs/ConditioningCombine/ja.md (+4 -4)
📝 comfyui_embedded_docs/docs/ConditioningConcat/ja.md (+4 -4)
📝 comfyui_embedded_docs/docs/ConditioningSetAreaStrength/ja.md (+4 -4)
📝 comfyui_embedded_docs/docs/ConditioningSetMask/ja.md (+5 -5)
📝 comfyui_embedded_docs/docs/ConditioningZeroOut/ja.md (+4 -4)
📝 comfyui_embedded_docs/docs/ControlnetApply/ja.md (+6 -6)
📝 comfyui_embedded_docs/docs/GligenTextBoxApply/ja.md (+5 -5)
📝 comfyui_embedded_docs/docs/KSampler/ja.md (+5 -6)
📝 comfyui_embedded_docs/docs/KSamplerAdvanced/ja.md (+4 -5)
📝 comfyui_embedded_docs/docs/Sd4xupscaleConditioning/ja.md (+6 -7)
📝 comfyui_embedded_docs/docs/StyleModelApply/ja.md (+5 -5)
📝 comfyui_embedded_docs/docs/SvdImg2vidConditioning/ja.md (+4 -4)

📄 Description

Reason for Translation Change

In both Japanese and English, "Conditioning" is commonly written phonetically as 「コンディショニング」. However, for users who are not familiar with machine learning or mathematics, translating it to 「条件付け」 (which directly means "conditioning" or "the act of
setting conditions") is more intuitive and easier to understand.

This change offers the following benefits:

Improved Clarity: Makes the node's function more accessible to users unfamiliar with the technical jargon.
Better UI/UX: Reduces the character count on the UI, resulting in a cleaner and less cluttered interface.

This approach is also consistent with the Chinese documentation, where "Conditioning" has been translated to the simpler term 「条件」 (condition).

翻訳の意図

日本語と英語において "Conditioning" は、一般的にカタカナで「コンディショニング」と表記されます。しかし、機械学習や数学の専門知識がない方にとっては、より直感的に意味を理解できる「条件付け」という言葉に翻訳する方が適切であると判断しました。

この変更により、以下のメリットが期待できます。

分かりやすさの向上: 専門用語に不慣れなユーザーでも、ノードの機能が理解しやすくなります。
UI/UXの改善: UI上で表示される文字数が少なくなり、よりスッキリとした見た目になります。

また、中国語版のドキュメントにおいても、同様に "Conditioning" が「条件」という、より平易な言葉で翻訳されていることを確認しています。

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/Comfy-Org/embedded-docs/pull/53 **Author:** [@kaitas](https://github.com/kaitas) **Created:** 8/15/2025 **Status:** ✅ Merged **Merged:** 8/15/2025 **Merged by:** [@christian-byrne](https://github.com/christian-byrne) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`fe01141`](https://github.com/Comfy-Org/embedded-docs/commit/fe01141f6ea2a0980a3ddcd5d19ec09d9339e22b) docs(ja): 「コンディショニング」を「条件付け」に統一 ### 📊 Changes **13 files changed** (+57 additions, -59 deletions) <details> <summary>View changed files</summary> 📝 `.gitignore` (+1 -0) 📝 `comfyui_embedded_docs/docs/ConditioningCombine/ja.md` (+4 -4) 📝 `comfyui_embedded_docs/docs/ConditioningConcat/ja.md` (+4 -4) 📝 `comfyui_embedded_docs/docs/ConditioningSetAreaStrength/ja.md` (+4 -4) 📝 `comfyui_embedded_docs/docs/ConditioningSetMask/ja.md` (+5 -5) 📝 `comfyui_embedded_docs/docs/ConditioningZeroOut/ja.md` (+4 -4) 📝 `comfyui_embedded_docs/docs/ControlnetApply/ja.md` (+6 -6) 📝 `comfyui_embedded_docs/docs/GligenTextBoxApply/ja.md` (+5 -5) 📝 `comfyui_embedded_docs/docs/KSampler/ja.md` (+5 -6) 📝 `comfyui_embedded_docs/docs/KSamplerAdvanced/ja.md` (+4 -5) 📝 `comfyui_embedded_docs/docs/Sd4xupscaleConditioning/ja.md` (+6 -7) 📝 `comfyui_embedded_docs/docs/StyleModelApply/ja.md` (+5 -5) 📝 `comfyui_embedded_docs/docs/SvdImg2vidConditioning/ja.md` (+4 -4) </details> ### 📄 Description Reason for Translation Change In both Japanese and English, "Conditioning" is commonly written phonetically as 「コンディショニング」. However, for users who are not familiar with machine learning or mathematics, translating it to 「条件付け」 (which directly means "conditioning" or "the act of setting conditions") is more intuitive and easier to understand. This change offers the following benefits: * Improved Clarity: Makes the node's function more accessible to users unfamiliar with the technical jargon. * Better UI/UX: Reduces the character count on the UI, resulting in a cleaner and less cluttered interface. This approach is also consistent with the Chinese documentation, where "Conditioning" has been translated to the simpler term 「条件」 (condition). # 翻訳の意図日本語と英語において "Conditioning" は、一般的にカタカナで「コンディショニング」と表記されます。しかし、機械学習や数学の専門知識がない方にとっては、より直感的に意味を理解できる「条件付け」という言葉に翻訳する方が適切であると判断しました。この変更により、以下のメリットが期待できます。 * 分かりやすさの向上: 専門用語に不慣れなユーザーでも、ノードの機能が理解しやすくなります。 * UI/UXの改善: UI上で表示される文字数が少なくなり、よりスッキリとした見た目になります。また、中国語版のドキュメントにおいても、同様に "Conditioning" が「条件」という、より平易な言葉で翻訳されていることを確認しています。 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-26 22:08:38 +00:00