Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Rewrite file encoding detection for efficiency and UTF-32 support #4

Open
DTW-DanWard opened this issue Jun 13, 2017 · 0 comments
Open

Rewrite file encoding detection for efficiency and UTF-32 support #4

DTW-DanWard opened this issue Jun 13, 2017 · 0 comments
Labels
enhancement

Comments

@DTW-DanWard
Copy link
Owner

DTW-DanWard commented Jun 13, 2017 •
edited
Loading

The function for determining the file encoding (Get-DTWFileEncoding) - specifically the code if no BOM is present - is not as efficient as it could be. Also, it might also have an subtle bug (if a 3 byte character exists at the beginning of a UTF-16 file). And it doesn't handle UTF-32 files. Update Get-DTWFileEncoding to fixed these issues.

Also, add UTF-32 files to test/FileEncoding tests.

Seriously, though, does anyone actually store their code in UTF-32?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@DTW-DanWard