langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-24 22:11:36 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[PR #26353] refactor: standardize dataset-pipeline i18n terminology consistency #31400

New Issue
Closed
opened 2026-02-21 20:49:23 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 20:49:23 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/langgenius/dify/pull/26353

State: closed
Merged: Yes

Summary

This PR addresses terminology inconsistencies across multiple language versions of the dataset-pipeline translation files to improve user experience and interface professionalism.

Changes Made:

  • Chinese Traditional (zh-Hant): Unified 'Knowledge Pipeline' terminology from mixed '管道'/'流水線' usage to consistent '知識流水線'
  • Chinese Simplified (zh-Hans): Removed English remnants by translating 'Process Documents' → '处理文档', 'delimiter' → '分隔符', 'Maximum Chunk Length' → '最大块长度'
  • Japanese (ja-JP): Standardized 'Knowledge' terminology from mixed '知識'/'ナレッジ' usage to consistent 'ナレッジ'
  • All languages: Improved sentence structure and readability while maintaining technical accuracy

Impact:

  • Enhanced localization quality without functional changes
  • Improved user interface consistency across languages
  • Reduced cognitive load through standardized terminology
  • Better adherence to internationalization best practices

Fixes #26352

Screenshots

N/A - Text-only changes in translation files

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/26353 **State:** closed **Merged:** Yes --- ## Summary This PR addresses terminology inconsistencies across multiple language versions of the dataset-pipeline translation files to improve user experience and interface professionalism. **Changes Made:** - **Chinese Traditional (zh-Hant)**: Unified 'Knowledge Pipeline' terminology from mixed '管道'/'流水線' usage to consistent '知識流水線' - **Chinese Simplified (zh-Hans)**: Removed English remnants by translating 'Process Documents' → '处理文档', 'delimiter' → '分隔符', 'Maximum Chunk Length' → '最大块长度' - **Japanese (ja-JP)**: Standardized 'Knowledge' terminology from mixed '知識'/'ナレッジ' usage to consistent 'ナレッジ' - **All languages**: Improved sentence structure and readability while maintaining technical accuracy **Impact:** - Enhanced localization quality without functional changes - Improved user interface consistency across languages - Reduced cognitive load through standardized terminology - Better adherence to internationalization best practices Fixes #26352 ## Screenshots N/A - Text-only changes in translation files ## Checklist - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:49:23 -05:00
yindo closed this issue 2026-02-21 20:49:23 -05:00
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 pull-request
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#31400
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?