Added encoding argument to TextReuseCorpus and TextReuseTextDocument #89
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.
When using Windows
readLines
will expect text files to be encoded in Windows-1252.This would add an optional encoding argument to
TextReuseCorpus
as well asTextReuseTextDocument
which can be used to explicitly specify the encoding of the input files (mostly UTF-8).As it defaults to "unknown" which is the default for
readLines
this should maintain backward compatability.Edit: I forgot to mention that this specific issue can be worked around by setting
options(encoding = "UTF-8")
before creating the corpus however this has some side effects so I still think having an encoding argument is the better way to deal with this.