We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, we refer to UTF-32LE as UTF-32. We need to add support UTF-32BE which is relatively easy.
Related: #3
The text was updated successfully, but these errors were encountered:
It is probably more urgent to address #3
There is probably little need for UTF-32BE since UTF-32 is mostly used internally, and processors are invariably LE these days.
cc @NicolasJiaxin
Sorry, something went wrong.
No branches or pull requests
Currently, we refer to UTF-32LE as UTF-32. We need to add support UTF-32BE which is relatively easy.
Related: #3
The text was updated successfully, but these errors were encountered: