Turkish localization strings does not make sense

[saydemr]

Windows Version

Microsoft Windows [Version 10.0.26200.7171]

WSL Version

2.6.2.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.87.2-1

Distro Version

Ubuntu 24.04.3 LTS

Other Software

No response

Repro Steps

There are apparent translation mistakes in the Turkish localization file. I caught one that used the file format "tar" with the words meaning translated to Turkish i.e. tar: a dark, thick, flammable liquid, in Turkish: Katran.

see:

WSL/localization/strings/tr-TR/Resources.resw

Line 1060 in f4b67e3

<value>Bu bir VHD dosyası gibi görünüyor. Katran --vhd VHD içeri aktarın.</value>

Expected Behavior

Proper Turkish translation. For example, words that have meaning in software domain by itseld should not be translated.

Actual Behavior

Poor translation for several prompts.

Diagnostic Logs

No response

[github-actions]

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise, please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions in Collect WSL logs for networking issues

Once completed please upload the output files to this GitHub issue.

See Collect WSL logs (recommended method).

If you choose to email these logs instead of attaching them to the bug, please send them to wsl-gh-logs@microsoft.com with the GitHub issue number in the subject, and include a link to your GitHub issue comment in the message body, and reply with '/emailed-logs'.

[saydemr]

/question

[github-actions]

Diagnostic information

Found '/question', adding tag 'question'