starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

German translation for FOR /F command description is incorrect #16419

New Issue
Open
opened 2026-01-31 05:08:50 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 05:08:50 +00:00
Owner
Copy Link

Originally created by @german-one on GitHub (Jan 17, 2022).

Originally assigned to: @lhecker on GitHub.

Windows Terminal version

No response

Windows build number

No response

Other Software

No response

Steps to reproduce

for_bug

Run FOR /?

  1. The description of how to use a FOR /F loop for commands and without using option USEBACKQ shows no quotes around the command. However, single quotes would have been correct here.
  2. The description of how to use a FOR /F loop for strings and using option USEBACKQ shows double quotes around the string. However, single quotes would have been correct here.

Expected Behavior

  1. FOR /F ["Optionen"] %variable IN ('Befehl') DO Befehl [Parameter]
  2. FOR /F ["Optionen"] %variable IN ('Zeichenfolge') DO Befehl [Parameter]

Actual Behavior

  1. FOR /F ["Optionen"] %variable IN (Befehl) DO Befehl [Parameter]
  2. FOR /F ["Optionen"] %variable IN ("Zeichenfolge") DO Befehl [Parameter]
Originally created by @german-one on GitHub (Jan 17, 2022). Originally assigned to: @lhecker on GitHub. ### Windows Terminal version _No response_ ### Windows build number _No response_ ### Other Software _No response_ ### Steps to reproduce <img width="476" alt="for_bug" src="https://user-images.githubusercontent.com/46659645/152648897-98534ea2-f4c4-4d46-964e-e7920b41033f.png"> Run `FOR /?` 1. The description of how to use a FOR /F loop for commands and _without_ using option USEBACKQ shows no quotes around the command. However, single quotes would have been correct here. 2. The description of how to use a FOR /F loop for strings _and_ using option USEBACKQ shows double quotes around the string. However, single quotes would have been correct here. ### Expected Behavior 1. `FOR /F ["Optionen"] %variable IN ('Befehl') DO Befehl [Parameter]` 2. `FOR /F ["Optionen"] %variable IN ('Zeichenfolge') DO Befehl [Parameter]` ### Actual Behavior 1. `FOR /F ["Optionen"] %variable IN (Befehl) DO Befehl [Parameter]` 2. `FOR /F ["Optionen"] %variable IN ("Zeichenfolge") DO Befehl [Parameter]`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Localization Issue-Bug Needs-Tag-Fix Priority-2 Product-Cmd.exe Tracking-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#16419
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?