Inquiring about i18n file structure changes in recent updates

[sharpdima]

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.

Content

"Hi Dify Team,

I am currently on version 1.13.0 and I'm trying to sync my local repository (which has extensive frontend and backend customizations for my project, Mora) with the latest upstream/main.

During the merge, I noticed that several translation files in web/i18n/fa-IR/ (such as common.ts, share.ts, and workflow.ts) are marked as deleted in the upstream, while I have modified them in my local branch.

Could you please clarify where these translation strings have been moved? I want to ensure my custom Persian translations are correctly migrated to the new structure without losing my branding and UI improvements.

[dosubot[bot]]

The translation files weren't deleted—they were migrated from TypeScript (.ts) to JSON (.json) format as part of a major i18n restructuring in late December 2025.

Where your files moved:

• common.ts → common.json
• share.ts → share.json + share-app.json
• workflow.ts → workflow.json

Key format changes (PR #30114):

Old TypeScript nested format:

fileUpload: { 
  title: "...", 
  description: "..." 
}

New JSON flattened format:

{
  "feature.fileUpload.title": "...",
  "feature.fileUpload.description": "..."
}

Translation function calls also changed from t('common.appMenus.promptEng') to t('appMenus.promptEng', { ns: 'common' }).

To migrate your Persian customizations:

1. Convert your modified .ts files to the new .json flat key format
2. The fa-IR directory now contains 30 JSON files—check if any of your custom strings need to go into new module-specific files (like app-debug.json, dataset-creation.json, etc.)
3. Review the i18n-config README for the complete structure and naming conventions (kebab-case filenames)

Related PRs: #30324 (namespace refactor), #30325 (translation sync), #30368 (kebab-case naming).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}