Document new variable PSApplicationOutputEncoding

[jborean93]

PR Summary

Documents the new variable $PSApplicationOutputEncoding which is used to control the encoding PowerShell uses when reading output from an external application.

This also removes the example for $OutputEncoding as it is wrong. The $OutputEncoding variable is only used as the encoding that PowerShell writes data through the external application's stdin pipe. The command line is always a string on Windows/Linux/macOS so is unaffected by this option.

• See https://github.com/PowerShell/PowerShell/pull/21219 for the PR that is attempting to add this feature.

PR Checklist

• [x] Descriptive Title: This PR's title is a synopsis of the changes it proposes.
• [x] Summary: This PR's summary describes the scope and intent of the change.
• [x] Contributor's Guide: I have read the contributors guide.
• [x] Style: This PR adheres to the style guide.

[learn-build-service-prod[bot]]

Learn Build status updates of commit b55f4ce:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
reference/7.5/Microsoft.PowerShell.Core/About/about_Character_Encoding.md	:white_check_mark:Succeeded	View (powershell-7.5)
reference/7.5/Microsoft.PowerShell.Core/About/about_Preference_Variables.md	:white_check_mark:Succeeded	View (powershell-7.5)

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[github-actions[bot]]

Expectations

Thanks for your submission! Here's a quick note to provide you with some context for what to expect from the docs team and the process now that you've submitted a PR. Even if you've contributed to this repo before, we strongly suggest reading this information; it might have changed since you last read it.

To see our process for reviewing PRs, please read our editor's checklist and process for managing pull requests in particular. Below is a brief, high-level summary of what to expect, but our contributor guide has expanded details.

The docs team begins to review your PR if you request them to or if your PR meets these conditions:

• It is not a draft PR.
• It does not have a WIP prefix in the title.
• It passes validation and build steps.
• It does not have any merge conflicts.
• You have checked every box in the PR Checklist, indicating you have completed all required steps and marked your PR as Ready to Merge.

You can always request a review at any stage in your authoring process, the docs team is here to help! You do not need to submit a fully polished and finished draft; the docs team can help you get content ready for merge.

While reviewing your PR, the docs team may make suggestions, write comments, and ask questions. When all requirements are satisfied, the docs team marks your PR as Approved and merges it. Once your PR is merged, it is included the next time the documentation is published. For this project, the documentation is published daily at 3 p.m. Pacific Standard Time (PST).

[jborean93]

~~Depending on what happens with https://github.com/MicrosoftDocs/PowerShell-Docs/pull/10877, I might just revert the changes to $OutputEncoding here in favour of that PR and keep this focused on the new proposed variable.~~

Edit: PR has been merged so I've rebased the changes here.

[learn-build-service-prod[bot]]

Learn Build status updates of commit c1a3390:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
reference/7.5/Microsoft.PowerShell.Core/About/about_Character_Encoding.md	:white_check_mark:Succeeded	View (powershell-7.5)
reference/7.5/Microsoft.PowerShell.Core/About/about_Preference_Variables.md	:white_check_mark:Succeeded	View (powershell-7.5)

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[learn-build-service-prod[bot]]

Learn Build status updates of commit bfb0a36:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
reference/7.5/Microsoft.PowerShell.Core/About/about_Character_Encoding.md	:white_check_mark:Succeeded	View (powershell-7.5)
reference/7.5/Microsoft.PowerShell.Core/About/about_Preference_Variables.md	:white_check_mark:Succeeded	View (powershell-7.5)

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[learn-build-service-prod[bot]]

Learn Build status updates of commit 49de1d1:

:white_check_mark: Validation status: passed

File	Status	Preview URL	Details
reference/7.5/Microsoft.PowerShell.Core/About/about_Character_Encoding.md	:white_check_mark:Succeeded	View (powershell-7.5)
reference/7.5/Microsoft.PowerShell.Core/About/about_Preference_Variables.md	:white_check_mark:Succeeded	View (powershell-7.5)

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[github-actions[bot]]

Expectations

Thanks for your submission! Here's a quick note to provide you with some context for what to expect from the docs team and the process now that you've submitted a PR. Even if you've contributed to this repo before, we strongly suggest reading this information; it might have changed since you last read it.

To see our process for reviewing PRs, please read our editor's checklist and process for managing pull requests in particular. Below is a brief, high-level summary of what to expect, but our contributor guide has expanded details.

The docs team begins to review your PR if you request them to or if your PR meets these conditions:

• It is not a draft PR.
• It does not have a WIP prefix in the title.
• It passes validation and build steps.
• It does not have any merge conflicts.
• You have checked every box in the PR Checklist, indicating you have completed all required steps and marked your PR as Ready to Merge.

You can always request a review at any stage in your authoring process, the docs team is here to help! You do not need to submit a fully polished and finished draft; the docs team can help you get content ready for merge.

While reviewing your PR, the docs team may make suggestions, write comments, and ask questions. When all requirements are satisfied, the docs team marks your PR as Approved and merges it. Once your PR is merged, it is included the next time the documentation is published. For this project, the documentation is published daily at 3 p.m. Pacific Standard Time (PST).