Document reading gzipped text in other encodings - #1209
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1209 +/- ##
=======================================
Coverage 95.75% 95.75%
=======================================
Files 9 9
Lines 5489 5489
=======================================
Hits 5256 5256
Misses 233 233 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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.
The reading guide explains gzip and UTF-8 input but does not show how to combine decompression with character conversion. Add a runnable ISO-8859-1 gzip example using CodecZlib and StringEncodings, with both dependencies limited to the docs environment.
The example decompresses first and passes a UTF-8 decoder to
CSV.File. It closes the decoder infinally, which also checks for an incomplete final character. It states the source-encoding and in-memory parsing constraints.Addresses #1091.
Validation: full Documenter build passed, including the example's value assertions; rendered output checked. Independent checks passed for ISO-8859-1, UTF-16LE, UTF-16BE and Windows-1252, plus truncated-character rejection (17 checks). No parser/API changes.
Co-authored by Codex