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.
Adding support for Quoted Printable fields
Related to Issue #448
GetContentLines
string parsers to support line continuation when Encoding is quoted printable AND line ends with =I am far from convinced that this is a good solution. There are a number of places where this pull seems inelegant.
GetContentLines
that tests for the encoding by a string match is ugly. I would prefer to, get the field name, read the properties, and then use that information while parsing the value but that is structural change.DataTypes/QuotedPrintableString.cs
I think I should be wrapping the value in a strongly typed object. The way I am using it as something like a Type flag feels more like a hack.GetEncoderFor
isn't pretty.