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

[Chore/Refactor] Standardize i18n terminology consistency in dataset-pipeline translations #18427

New Issue
Closed
opened 2026-02-21 19:47:34 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 19:47:34 -05:00
Owner
Copy Link
Copy Source

Originally created by @lyzno1 on GitHub (Sep 28, 2025).

Description

This refactoring addresses terminology inconsistencies across multiple language versions of the dataset-pipeline translation files. The current translations contain mixed usage of technical terms, English remnants in Chinese translations, and inconsistent terminology that affects user experience.

Motivation

  1. Terminology Inconsistency: Chinese Traditional uses both '管道' and '流水線' for 'Pipeline', causing user confusion
  2. English Remnants: Chinese Simplified contains untranslated English terms like 'Process Documents', 'delimiter', 'Maximum Chunk Length'
  3. Mixed Term Usage: Japanese uses both '知識' and 'ナレッジ' for 'Knowledge' inconsistently
  4. User Experience: Inconsistent terminology reduces interface professionalism and increases cognitive load

Proposed Changes

  • Standardize 'Knowledge Pipeline' terminology across all languages
  • Remove English remnants from Chinese translations
  • Unify Japanese knowledge-related terminology
  • Ensure consistent technical term translations

Additional Context

This affects user-facing strings in the dataset pipeline feature, improving localization quality without functional changes. The refactoring follows established translation standards and maintains technical accuracy while improving consistency.

Originally created by @lyzno1 on GitHub (Sep 28, 2025). **Description** This refactoring addresses terminology inconsistencies across multiple language versions of the dataset-pipeline translation files. The current translations contain mixed usage of technical terms, English remnants in Chinese translations, and inconsistent terminology that affects user experience. **Motivation** 1. **Terminology Inconsistency**: Chinese Traditional uses both '管道' and '流水線' for 'Pipeline', causing user confusion 2. **English Remnants**: Chinese Simplified contains untranslated English terms like 'Process Documents', 'delimiter', 'Maximum Chunk Length' 3. **Mixed Term Usage**: Japanese uses both '知識' and 'ナレッジ' for 'Knowledge' inconsistently 4. **User Experience**: Inconsistent terminology reduces interface professionalism and increases cognitive load **Proposed Changes** - Standardize 'Knowledge Pipeline' terminology across all languages - Remove English remnants from Chinese translations - Unify Japanese knowledge-related terminology - Ensure consistent technical term translations **Additional Context** This affects user-facing strings in the dataset pipeline feature, improving localization quality without functional changes. The refactoring follows established translation standards and maintains technical accuracy while improving consistency.
yindo closed this issue 2026-02-21 19:47:34 -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
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#18427
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?