[Fix #133] StringReader fails to normalize Windows line endings #145
Conversation
This file contains hidden or 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
Contributor
Author
|
Wanted to follow up and see if there was anything this was missing. |
1 similar comment
Contributor
Author
|
Wanted to follow up and see if there was anything this was missing. |
nschonni
added a commit
that referenced
this pull request
Apr 15, 2015
[Fix #133] StringReader fails to normalize Windows line endings
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
[Fix #133] StringReader fails to normalize Windows line endings
\rmatches a carriage return\nmatches a newline character.{1, 2}matches between either 1 or 2 of the preceding tokensThis way you can start with either and should cover both linux or windows to fix #133
cc: @nschonni