Add Byte Order Mark (BOM) output support #1424
Merged
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
setting it to 1 will add a BOM sequence at the beginning of the output. This is to generate Excel on Windows friendly CSV files.
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.
if
QSV_BOM_OUTPUTis set to 1, it will add a BOM sequence to the beginning of qsv's output.This is primarily to generate "Excel for Windows"-friendly CSV files, as it forces Excel to recognize the CSV as UTF8-encoded.
Note that Excel on macOS does not need BOM, as the default encoding on macOS is UTF-8.