Add UTF8 #32
Open
Add UTF8 #32
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Requirements
Description of the Change
Added the ability to specify the Encoding parameter to choose between ASCII or UTF8 encoding. If the parameter is not specified, ASCII will be used by default. Specifying this parameter is important when the message text contains non-ASCII characters. Without it, the received message may be displayed incorrectly. For example, the text might be displayed as "?" characters.
Usage example:
Send-SyslogMessage -Server hostname -Message "Test" -Severity Alert -Facility local0 -Encoding UTF8
This command will send a message using UTF8 encoding.
Testing
The tests verify the correct encoding of non-ASCII characters after converting back to text.
Associated/Resolved Issues
Wrong non-ASCII chars in messages.