Encoding to UTF-8 #107
Closed
Encoding to UTF-8 #107
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 leaves #105 printing a |
|
This also solves #21. |
|
On review this is a dangerous change. It doesn't properly deal with all the possible R objects that could be passed in. It also copies everything in memory, which would make large yaml files horribly inefficient. Open questions 1) Does libyaml require UTF-8? 2) Examine how python deals with the encoding issue when using libyaml Possible solutions: Check for UTF-8 on input, if not UTF-8 halt and recommend pre conversion. |
|
Moved discussion into #113 |
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.
A modified version of 7256cba that preserves attributes and passes tests. This should solve #90 and #105.