mafintosh / mafintosh/csv-parser
Encoded characters when reading utf16
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.5k
- Forks
- 143
- PR merge metrics
- No merged PRs in 30d
Description
* Operating System: macOs Mojave 10.4.6
* Node Version: 12.10.0
* NPM Version: 6.11.3
* csv-parser Version: 2.3.3
### Expected Behavior
Output decoded text when reading utf16
### Actual Behavior
Outputs encoded characters when reading utf16
### How Do We Reproduce?
Referencing test/fixtures/bench/utf16.csv
If you attempt to process this file, the result is an object containing encoded characters, while test/fixtures/bench/utf8.csv returns decoded characters.
Is it intentional for data to be returned in different forms like this?
My ideal solution would be to identify and decode utf16. But a blurb in the readme to explain this or how to handle it would work.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with test/fixtures/bench/utf16.csv and compare its output with test/fixtures/bench/utf8.csv. Read the issue's expected and actual behavior, then determine whether the intended result is UTF-16 decoding or documented handling; done means the behavior is resolved or clearly explained in the README.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100