Repository navigation
ja-JP: Inconsistent translation of "Image" in wslc CLI help / messages #41738
Description
Windows Version
Microsoft Windows [Version 10.0.26200.9457]
WSL Version
3.0.1.0
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
- Set Windows display language / WSL locale to Japanese (ja-JP).
- Run
wslc image list --helpandwslc image import --help. - Compare the Japanese wording used for "image" across the different help/output strings.
Expected Behavior
The term "Image" (container image) should be translated consistently as「イメージ」throughout the ja-JP UI, matching the vast majority of existing strings (e.g. イメージを管理します。, Dockerfile からイメージをビルドします。).
Actual Behavior
A handful of strings in localization/strings/ja-JP/Resources.resw translate "Image" as「画像」instead, which reads as "picture/photo" in Japanese rather than "container image", and is inconsistent with the rest of the file:
| Resource name | Current | Should be |
|---|---|---|
MessageWslcInvalidImage |
無効な画像: '{}' | 無効なイメージ: '{}' |
WSLCCLI_ImageImportDesc |
tarball から画像をインポートします。 | tarball からイメージをインポートします。 |
WSLCCLI_ImageListAllArgDescription |
すべての画像を表示します (既定では中間画像は非表示です)。 | すべてのイメージを表示します (既定では中間イメージは非表示です)。 |
WSLCCLI_ImagePruneDeletedHeader |
削除された画像: | 削除されたイメージ: |
WSLCCLI_ImageLoaded |
読み込まれた画像: {} | 読み込まれたイメージ: {} |
WSLCCLI_ImageLoadedId |
読み込まれた画像 ID: {} | 読み込まれたイメージ ID: {} |
WSLCCLI_PullAllTagsArgDescription |
リポジトリ内のすべてのタグ付き画像をダウンロードします。 | リポジトリ内のすべてのタグ付きイメージをダウンロードします。 |
WSLCCLI_TableHeaderImage |
画像 | イメージ |
MessageWslcImportProgressParseFailed |
画像のインポート進行状況の解析に失敗しました | イメージのインポート進行状況の解析に失敗しました |
Diagnostic Logs
No response
Activity
github-actions commentedon Sep 30, 2026
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:
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 networkinginstead, following the instructions in Collect WSL logs for networking issuesOnce 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'.
[-]ja-JP: Inconsistent translation of "Image" (画像 vs イメージ) in `wslc` CLI help / messages[/-][+]ja-JP: Inconsistent translation of "Image" in `wslc` CLI help / messages[/+]github-actions commentedon Sep 30, 2026
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:
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 networkinginstead, following the instructions in Collect WSL logs for networking issuesOnce 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'.
microsoft-github-policy-service commentedon Oct 7, 2026
This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.
Thank you!