-
Notifications
You must be signed in to change notification settings - Fork 35
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.
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
UTF16-LE files can't be parsed #25
Comments
Bios-Marcel
added a commit
to Bios-Marcel/gotenv
that referenced
this issue
Aug 12, 2023
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
added a commit
to Bios-Marcel/gotenv
that referenced
this issue
Aug 14, 2023
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
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
I have written a
.env
file via PowerShell, usingecho "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.
The text was updated successfully, but these errors were encountered: