langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-23 04:55:28 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Missing ‘read’ meaning in Japanese translation #6895

New Issue
Closed
opened 2026-02-21 18:17:52 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:17:52 -05:00
Owner
Copy Link
Copy Source

Originally created by @nomi3 on GitHub (Nov 22, 2024).

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.11.2

Utility with translation issue

http://localhost/install

🌐 Language affected

Japanese

❌ Actual phrase(s)

'Dify Community Editionを開始する前に、GitHubの'

✔️ Expected phrase(s)

'GitHubのオープンソースライセンスを確認してから、Dify Community Editionを開始してください。'

スクリーンショット 2024-11-23 0 37 21

ℹ Why is the current translation wrong

The current translation “Dify Community Editionを開始する前に、GitHubの” is incomplete and misses the meaning of “read.” It does not instruct users to review or read the open-source license on GitHub, which is an important step. The expected translation explicitly includes this meaning, ensuring that users understand they need to read the license before starting with Dify Community Edition. Without this, users might skip an essential action.

Originally created by @nomi3 on GitHub (Nov 22, 2024). ### Self Checks - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.11.2 ### Utility with translation issue http://localhost/install ### 🌐 Language affected Japanese ### ❌ Actual phrase(s) 'Dify Community Editionを開始する前に、GitHubの' ### ✔️ Expected phrase(s) 'GitHubのオープンソースライセンスを確認してから、Dify Community Editionを開始してください。' ![スクリーンショット 2024-11-23 0 37 21](https://github.com/user-attachments/assets/ec48bd95-6a8a-487c-afda-e72b8e49feaa) ### ℹ Why is the current translation wrong The current translation “Dify Community Editionを開始する前に、GitHubの” is incomplete and misses the meaning of “read.” It does not instruct users to review or read the open-source license on GitHub, which is an important step. The expected translation explicitly includes this meaning, ensuring that users understand they need to read the license before starting with Dify Community Edition. Without this, users might skip an essential action.
yindo added the 📚 documentation label 2026-02-21 18:17:52 -05:00
yindo closed this issue 2026-02-21 18:17:52 -05:00
yindo commented 2026-02-21 18:17:52 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 22, 2024):

Hello, @nomi3! I'm here to help you with any bugs, questions, or contributions you have. Let's work together to solve this issue!

The expected Japanese translation you provided is correct. It clearly instructs users to read the open-source license on GitHub before starting with Dify Community Edition:

「GitHubのオープンソースライセンスを確認してから、Dify Community Editionを開始してください。」

This translation ensures that users understand the importance of reviewing the license, which is a crucial step before proceeding.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Nov 22, 2024): <!-- Greeting --> Hello, @nomi3! I'm here to help you with any bugs, questions, or contributions you have. Let's work together to solve this issue! <!-- Answer --> The expected Japanese translation you provided is correct. It clearly instructs users to read the open-source license on GitHub before starting with Dify Community Edition: 「GitHubのオープンソースライセンスを確認してから、Dify Community Editionを開始してください。」 This translation ensures that users understand the importance of reviewing the license, which is a crucial step before proceeding. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 📚 documentation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#6895
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?