Skip to content

Conversation

@Gimly
Copy link
Contributor

@Gimly Gimly commented Oct 1, 2020

PR Summary

The System.Management.Automation.Utils.GetEncoding method should return UTF8 without BOM as a default but was returning ASCII.

This is fixed by returning an instance of the Utf8Encoding with the BOM set to false as a default fallback encoding.

PR Context

This should fix #13678 and fix partially #13677

PR Checklist

The System.Management.Automation.Utils.GetEncoding method
should return UTF8 without BOM as a default but was returning ASCII.

This is fixed by returning an instance of the Utf8Encoding with the BOM
set to false.
@ghost ghost assigned rjmholt Oct 1, 2020
@rjmholt rjmholt requested review from JamesWTruher and daxian-dbw and removed request for daxian-dbw October 1, 2020 21:02
@rjmholt rjmholt added Breaking-Change breaking change that may affect users Review - Committee The PR/Issue needs a review from the PowerShell Committee labels Oct 1, 2020
@rjmholt
Copy link
Collaborator

rjmholt commented Oct 1, 2020

@PowerShell/powershell-committee please review this potentially breaking change, noting the linked issues

Add the label for the boolean argument

Co-authored-by: Ilya <darpa@yandex.ru>
@iSazonov
Copy link
Collaborator

iSazonov commented Oct 2, 2020

For PowerShell-Committee:

  • it affects only transcribe output files.
  • we already changed defaults to Uft8NoBOM in other code paths
  • I think it is a bug and we shouldn't consider this as a breaking change - it is unexpected behavior if we change encoding of existent file.

@SteveL-MSFT SteveL-MSFT changed the title Change default fallback encoding for GetEncoding in Start-Transcribe Change default fallback encoding for GetEncoding in Start-Transcript Oct 7, 2020
@SteveL-MSFT
Copy link
Member

ASCII being a subset of UTF8 makes this an unlikely impactful breaking change (bucket 3) for me. Seems like the right thing to do.

@SteveL-MSFT
Copy link
Member

@PowerShell/powershell-committee reviewed this, we agree that this is a bucket 3 breaking change that is unlikely to have negative impact on anyone. This should have been changed along with the other encoding changes to UTF-8 by default and is a bug fix.

@SteveL-MSFT SteveL-MSFT added Committee-Reviewed PS-Committee has reviewed this and made a decision and removed Review - Committee The PR/Issue needs a review from the PowerShell Committee labels Oct 7, 2020
@rjmholt rjmholt added the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label Oct 7, 2020
@ghost ghost removed the Waiting on Author The PR was reviewed and requires changes or comments from the author before being accept label Oct 8, 2020
@rjmholt
Copy link
Collaborator

rjmholt commented Oct 8, 2020

@daxian-dbw please re-review if you can

@Gimly
Copy link
Contributor Author

Gimly commented Oct 9, 2020

@rjmholt I'm not sure about those CI fails, do I need to do something about them?

@iSazonov
Copy link
Collaborator

iSazonov commented Oct 9, 2020

I restarted CI Windows.

@rjmholt rjmholt merged commit cf251a9 into PowerShell:master Oct 9, 2020
@rjmholt rjmholt added the CL-Engine Indicates that a PR should be marked as an engine change in the Change Log label Oct 9, 2020
@iSazonov
Copy link
Collaborator

iSazonov commented Oct 9, 2020

@Gimly Thanks for your contribution!

@Gimly Gimly deleted the default_utf8_in_starttranscript branch October 28, 2020 11:48
@ghost
Copy link

ghost commented Nov 17, 2020

🎉v7.2.0-preview.1 has been released which incorporates this pull request.:tada:

Handy links:

Copy link

@Steg17 Steg17 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Breaking-Change breaking change that may affect users CL-Engine Indicates that a PR should be marked as an engine change in the Change Log Committee-Reviewed PS-Committee has reviewed this and made a decision

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Start-Transcript -Append uses lossy ASCII character encoding when appending to a BOM-less target file

6 participants