Fix UTF-8 encoding in gpgdata write callback #118
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
This change associates the buffer allocated in the gpgme_data write callback with the UTF-8 encoding. If there is a configured internal encoding (e.g. Encoding.default_internal), then the string is exported to that encoding.
|
This fixes this bug: #113 Probably would want to consider in the future unifying the encoding logic used in |
|
This fixes #113 |
|
Hi 👋 any news on getting this merged in? |
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.
This change associates the buffer allocated in the gpgme_data write
callback with the UTF-8 encoding. If there is a configured internal
encoding (e.g. Encoding.default_internal), then the string is exported
to that encoding.