Skip to content

Fix escape string translation when generating a resx file from the PowerShell ETW manifest#5892

Merged
daxian-dbw merged 1 commit intoPowerShell:masterfrom
dantraMSFT:dantra/issue5890
Jan 19, 2018
Merged

Fix escape string translation when generating a resx file from the PowerShell ETW manifest#5892
daxian-dbw merged 1 commit intoPowerShell:masterfrom
dantraMSFT:dantra/issue5890

Conversation

@dantraMSFT
Copy link
Copy Markdown
Contributor

PR Summary

Fixes #5890

The original resx generator misconfigured the translation table for translating message resource escape characters to string escape characters. The change fixes the escapeStrings table and includes the regenerated resx file.

The resx file is used on Linux and MacOS for writing the equivalent of ETW events to the system log files.

PR Checklist

Note: Please mark anything not applicable to this PR NA.

@lzybkr
Copy link
Copy Markdown
Contributor

lzybkr commented Jan 13, 2018

How about just using my original suggestion: #5144 (comment)

@dantraMSFT
Copy link
Copy Markdown
Contributor Author

@daxian-dbw, @TravisEz13, @adityapatwardhan: Do you guys have any feedback on this?

Copy link
Copy Markdown
Member

@daxian-dbw daxian-dbw left a comment

Choose a reason for hiding this comment

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

The updated resource strings look good to me.

@daxian-dbw daxian-dbw self-assigned this Jan 18, 2018
@daxian-dbw daxian-dbw merged commit 65a4002 into PowerShell:master Jan 19, 2018
@dantraMSFT dantraMSFT deleted the dantra/issue5890 branch January 19, 2018 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Resxgen.psm1 is not translating manifest escape characters.

4 participants