fix(plugin-import-export): adds UTF-8 BOM support to csv exports #14044
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
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖 |
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.
What?
Adds UTF-8 Byte Order Mark (BOM) to CSV exports in both streaming and buffered export paths.
Why?
CSV exports containing non-Latin scripts (e.g., Hebrew, Arabic, Chinese) display as mojibake in Microsoft Excel on Windows because Excel defaults to ANSI encoding and fails to auto-detect UTF-8 without a BOM.
The BOM (
EF BB BF) signals UTF-8 encoding to Excel without breaking compatibility with other tools (Google Sheets, LibreOffice, modern CSV parsers all handle it correctly).How?
0xEF 0xBB 0xBF) to the first chunk in streaming CSV exports\uFEFF) to buffered CSV exportscharset=utf-8for CSV filesFixes #13929