-
Notifications
You must be signed in to change notification settings - Fork 13.1k
Windows PowerShell Output Encoding Bug #20968
Copy link
Copy link
Open
Labels
area/coreIssues related to User Interface, OS Support, Core FunctionalityIssues related to User Interface, OS Support, Core Functionalityhelp wantedWe will accept PRs from all issues marked as "help wanted". Thanks for your support!We will accept PRs from all issues marked as "help wanted". Thanks for your support!priority/p2Important but can be addressed in a future release.Important but can be addressed in a future release.type/bug
Metadata
Metadata
Assignees
Labels
area/coreIssues related to User Interface, OS Support, Core FunctionalityIssues related to User Interface, OS Support, Core Functionalityhelp wantedWe will accept PRs from all issues marked as "help wanted". Thanks for your support!We will accept PRs from all issues marked as "help wanted". Thanks for your support!priority/p2Important but can be addressed in a future release.Important but can be addressed in a future release.type/bug
Type
Fields
Give feedbackNo fields configured for issues without a type.
What happened?
Resolve terminal encoding bugs in the Windows ecosystem by explicitly configuring PowerShell child processes to output stdout and stderr in UTF-8 format.
What did you expect to happen?
By standardizing PowerShell's output to UTF-8, we can ensure reliable and consistent handling of text, particularly for non-ASCII characters, improving the overall stability and internationalization support of the application. This prevents Node.js from misinterpreting characters due to PowerShell's default output encoding.
Client information
on Windows
Login information
No response
Anything else we need to know?
No response