Skip to content
This repository has been archived by the owner on Nov 16, 2024. It is now read-only.

Specify using UTF-16 Little endian #61

Merged
merged 1 commit into from
Jan 30, 2023
Merged

Conversation

etra0
Copy link
Contributor

@etra0 etra0 commented Jan 30, 2023

Since we're writing bytes using the LittleEndian mode, we should rather specify we're using UTF-16LE rather than let the platform randomly decide which one is the correct one.

This also fixes #60

Since we're writing bytes using the LittleEndian mode, we should rather specify we're using UTF-16LE rather than let the platform randomly decide which one is the correct one.

This also fixes protoncr#60
@watzon
Copy link
Collaborator

watzon commented Jan 30, 2023

Ahh the M1 chips are big endian and by default set_encoding must be using the system endianness

@watzon watzon merged commit 194e3ee into protoncr:master Jan 30, 2023
@watzon
Copy link
Collaborator

watzon commented Jan 30, 2023

Thanks for this!

@etra0
Copy link
Contributor Author

etra0 commented Jan 30, 2023

Ahh the M1 chips are big endian and by default set_encoding must be using the system endianness

The M1s are little endian, but for some reason Crystal is choosing the wrong default for the UTF-16, I'll see where the discussion lands in the bug I opened in the compiler.

Thanks for merging!

@etra0 etra0 deleted the patch-1 branch January 30, 2023 16:36
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Command parsing are broken
2 participants