hard coding of UTF-8 as export format for plain text #14
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.
Problem: The native encoding of treeline seems to be utf-8. If the OS encoding is set differently (for what ever reason this is common in Windows) plain text export is not possible as there exists no transcoding function instead the export will fail.
So as long as no transcoding is done, hard coding the plain text export to utf-8 seems like a sensible solution, which is also used for treeline, xml, html exports.