microsoft
Add Turkish translations for documentation files
Translated markdown documentation files into Turkish and organized them under a new 'tr/' directory. This makes it easier for Turkish developers to read, understand, and contribute to the WSL project. No changes were made to the original English documentation.
Summary of the Pull Request
This PR adds Turkish translations for 57 markdown documentation files. All translations are placed in a new tr/ folder, with no changes to the original English files.
PR Checklist
- [ ] Closes: Not applicable
- [ ] Communication: I have not discussed this with core contributors, but it is a documentation-only addition
- [ ] Tests: Not applicable
- [x] Localization: All added content is localized to Turkish
- [ ] Dev docs: Not applicable
- [x] Documentation updated: Turkish versions of all major documentation files have been added under
tr/
Detailed Description of the Pull Request / Additional comments
This PR introduces a Turkish translation of all key markdown documentation files in the repository. These translations are placed under a tr/ directory to avoid interfering with the original files. This structure also allows future translations in other languages to follow a similar format (e.g., fr/, de/, etc.).
Let me know if you'd prefer the translated files to be named differently (e.g., README.tr.md instead of placing them under a folder).
Validation Steps Performed
- Manually verified that all markdown files render properly in GitHub's markdown viewer.
- Confirmed that all links within the translated documents work correctly.
We need to figure out a story for how we do localization for our developer docs. This PR's intent is spot on, but I think we need to think about how we scale this to other languages as well. I'll ask about this internally!
Thank you for the feedback! I’d be happy to help if there’s a structured localization process in the future. Looking forward to hearing more.
Instead of <lang>/..., I'd personally put these into one of:
doc/<lang>/...(see https://github.com/microsoft/winget-cli/tree/master/doc)docs/<lang>/...(see https://github.com/microsoft/pyright/tree/main/docs)translations/<lang>/...(see https://github.com/microsoft/ML-For-Beginners/blob/09b03ccb52eb73842fd01a3f93a30f2905410bfa/translations/tr/README.mdLocalization/<lang>/...(see https://github.com/microsoft/winget-cli/tree/master/Localization)
@catuhana Thank you for your help. I'm going through and organizing each one.
@jsoref Thank you. it would be better to collect them in the translations folder. I will organize it this way.
I think it would make more sense to put documentations and its translations under docs/ folder. translations/ implies the strings in the code base being translated.
So there isn't a formalized localization process for the developer docs that are currently on this repo. The challenge here will be scaling to many different languages and maintaining those translations over changes. I don't think an approach of having all the languages in this repo will work well as it will be difficult to maintain (Any dev docs change would need updates across all languages from community members etc.). So I think there are two possible solutions: First you could fork this repo and maintain a translation of the dev docs in Turkish. Or the other possibility would be to use the dev docs at aka.ms/wsldocs which does have localization. The docs on this repo are intended to be lightweight, and tightly coupled to our code which is written and maintained only in English. We added a new docs page to our public docs which gives an overview of open sourcing, and if there is key information about open sourcing that is needed we can aim to put it there and it will be localized. So I will close this PR as I do not think there is action needed to be take on this specific code base, but happy to hear any feedback and continue the discussion, or review any other PRs on the docs repo etc.. Thank you!