Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The "开发商" category translation in WSL settings seems inaccurate #12428

Open
DuckDuckStudio opened this issue Jan 4, 2025 · 10 comments
Open
Labels

Comments

@DuckDuckStudio
Copy link

DuckDuckStudio commented Jan 4, 2025

I am unsure about the original English wording, but based on the settings under this category, I believe the Simplified Chinese translation should be "开发(Developer)" or "开发选项(Developer Options)" rather than the current term "开发商". The term "开发商" typically refers to a "developer" in the context of real estate or business (such as a property developer), which could lead to confusion in this context. In WSL settings, the intended meaning is likely related to "development" or "developer tools," so a more fitting translation would be "开发" or "开发选项" to reflect the context of software development. Revisiting the translation would provide better clarity for users and align with the expected meaning in the WSL environment.

I'm not sure if it's correct to submit translation issue to this repository, but I see the localization and i18n internationalization label in the repository labels.

Image

Copy link

github-actions bot commented Jan 4, 2025

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 here

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

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

@DuckDuckStudio
Copy link
Author

/question
Localization issues should not require associated logs.

Copy link

github-actions bot commented Jan 4, 2025

Diagnostic information
Found '/question', adding tag 'question'

@DuckDuckStudio DuckDuckStudio changed the title The "开发商" option translation in WSL settings seems inaccurate The "开发商" category translation in WSL settings seems inaccurate Jan 4, 2025
Copy link

github-actions bot commented Jan 4, 2025

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 here

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

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

@DuckDuckStudio
Copy link
Author

DuckDuckStudio commented Jan 4, 2025

/question
It's been explained earlier. (I just fixed an incorrect word in the title of the issue...)

Copy link

github-actions bot commented Jan 4, 2025

Diagnostic information
Found '/question', adding tag 'question'

@DuckDuckStudio DuckDuckStudio changed the title The "开发商" category translation in WSL settings seems inaccurate The "开发商" category translation in WSL settings seems inaccurate (test) Jan 4, 2025
Copy link

github-actions bot commented Jan 4, 2025

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 here

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

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

@DuckDuckStudio DuckDuckStudio changed the title The "开发商" category translation in WSL settings seems inaccurate (test) The "开发商" category translation in WSL settings seems inaccurate Jan 4, 2025
Copy link

github-actions bot commented Jan 4, 2025

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 here

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

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

@DuckDuckStudio
Copy link
Author

/question

Copy link

github-actions bot commented Jan 4, 2025

Diagnostic information
Found '/question', adding tag 'question'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants