Spanish translations in WSL settings are inaccurate and differ from documentation

[crramirez]

Windows Version

Microsoft Windows [Version 10.0.26200.7623]

WSL Version

wsl --version

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

No response

Distro Version

No response

Other Software

No response

Repro Steps

1. Use the WSL settings interface in Spanish.
2. Review various settings sections, especially “Programador” and “Pulsación del sistema personalizada”.
3. Compare translations to the documentation for WSL and expect common PC Spanish words.
4. Note that terms such as “Pulsación del sistema personalizada” are uncommon or incorrect.
5. See attached screenshot for examples.

Expected Behavior

I was expecting the settings interface to use clear and accurate Spanish translations that are commonly used in PC contexts and match the WSL documentation. For example, terms like “Programador” and “Pulsación del sistema personalizada” should be consistent, accurate, and easily understood by Spanish-speaking users worldwide, without strong regionalisms.

Actual Behavior

Currently, several translations in the WSL settings UI are not accurate, do not reflect the Spanish typically used in the IT context, and sometimes use terms that are entirely different from the official documentation. This may cause confusion for users. A screenshot is attached, and there are other similar cases across the settings. I plan to create a PR proposing clearer and more standardized translations, and I kindly invite all Spanish-speaking community members to help validate these updates, as there is only one Spanish file for all regions, and I am striving to avoid very regional variations (like “computadora” vs “ordenador”).

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-wsl-logs.ps1 -LogProfile networking instead, 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'.

[crramirez]

/feature

[github-actions]

Diagnostic information

Found '/feature', adding tag 'feature'