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

UTF16-LE files can't be parsed #25

Closed
Bios-Marcel opened this issue Aug 12, 2023 · 0 comments · Fixed by #26
Closed

UTF16-LE files can't be parsed #25

Bios-Marcel opened this issue Aug 12, 2023 · 0 comments · Fixed by #26

Comments

@Bios-Marcel
Copy link
Contributor

Bios-Marcel commented Aug 12, 2023 •
edited

I have written a .env file via PowerShell, using echo "X=Z" >> file.env. This produces a UTF16 file with a little endian BOM byte encoded in UTF-16.

I will try to fix this with a PR.
@Bios-Marcel Bios-Marcel changed the title Files with BOM bytes can't be parsed UTF16-LE files can't be parsed Aug 12, 2023
Bios-Marcel added a commit to Bios-Marcel/gotenv that referenced this issue Aug 12, 2023
@Bios-Marcel
Support reading UTF16 files
e829ad4 
To allow this, we need to use a different scanner that ignores the
respective BOM bytes possible to occur. This means \xFFEE and \xFEFF
since UTF16 can both be little endian or big endian.

By default, Windows uses UTF16 little endian.

Fixes subosito#25
@Bios-Marcel Bios-Marcel mentioned this issue Aug 12, 2023
Merged
Bios-Marcel added a commit to Bios-Marcel/gotenv that referenced this issue Aug 14, 2023
@Bios-Marcel
Support reading UTF16 files
2acf70a 
To allow this, we need to use a different scanner that ignores the
respective BOM bytes possible to occur. This means \xFFEE and \xFEFF
since UTF16 can both be little endian or big endian.

By default, Windows uses UTF16 little endian.

Fixes subosito#25
luisdavim pushed a commit that referenced this issue Aug 14, 2023
@Bios-Marcel
feat: support reading UTF16 files (#26)
0a22e48 
To allow this, we need to use a different scanner that ignores the
respective BOM bytes possible to occur. This means \xFFEE and \xFEFF
since UTF16 can both be little endian or big endian.

By default, Windows uses UTF16 little endian.

Fixes #25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support reading UTF16 files Bios-Marcel/gotenv
1 participant
@Bios-Marcel