[Refactor/Chore] Complete missing Turkish Agent Skills translations
- Dominant language
- TypeScript
- Stars
- 156k
- Forks
- 24.6k
- Avg merge
- 22h 9m
- Merged PRs (30d)
- 610
Description
### Self Checks
- [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542).
- [x] This is only for refactors or chores; if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general).
- [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, otherwise it will be closed.
- [x] 【中文用户 & Non English User】请使用英语提交,否则会被关闭 :)
- [x] Please do not modify this template :) and fill in all the required fields.
### Description
## Problem
The Turkish Agent Skills locale is missing translations for the Agent Skills management and Skill Builder UI. Users see English fallback text in the Turkish interface.
## Proposed change
Add the missing Turkish translations in `web/i18n/tr-TR/agent-v-2.json`, keeping the locale keys and interpolation placeholders synchronized with `en-US`.
## Scope
This issue tracks the localization-only change proposed in #41532.
### Motivation
Completing these translations provides a consistent Turkish experience for Agent Skills management and Skill Builder without changing application behavior.
### Additional Context
Validation should include JSON parsing, key parity, and interpolation placeholder parity between the English and Turkish locale files.
Contributor guide
Research direction
Start by comparing web/i18n/tr-TR/agent-v-2.json with the English locale file, focusing on the Agent Skills management and Skill Builder entries. Add the missing Turkish translations while preserving locale keys and interpolation placeholders. Validate JSON parsing, key parity, and placeholder parity between both files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- localization
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100