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
When running asciibinder build (v1.0.1) against content using UTF8 encoding, the build fails with the error
asciibinder build
Error: Could not generate docs: Encoding::InvalidByteSequenceError: /path/to/document_with_utf8.html.erb is not valid US-ASCII at [...]
When running it with LC_ALL=C.UTF-8 asciibinder build it builds correctly.
LC_ALL=C.UTF-8 asciibinder build
The system in question (a fresh RHEL8.7 install, but also happens on OSX12.6.1) has a locale of
LANG=en_US.UTF-8 LC_CTYPE=UTF-8 [...] LC_ALL=
When the override LC_ALL is empty (as is normal), the application should have fallen back to respect LC_CTYPE, then LANG.
LC_ALL
LC_CTYPE
LANG
It would be great to document this behaviour until the issue is fixed.
The text was updated successfully, but these errors were encountered:
Hi @fzdarsky - thanks for this. That is a good catch.
I don't maintain this repo actively anymore. Hoping someone else can take a look.
If you are able to, feel free to submit a PR against the docs repo to document this: https://github.com/redhataccess/ascii_binder-docs
Sorry, something went wrong.
No branches or pull requests
When running
asciibinder build
(v1.0.1) against content using UTF8 encoding, the build fails with the errorWhen running it with
LC_ALL=C.UTF-8 asciibinder build
it builds correctly.The system in question (a fresh RHEL8.7 install, but also happens on OSX12.6.1) has a locale of
When the override
LC_ALL
is empty (as is normal), the application should have fallen back to respectLC_CTYPE
, thenLANG
.It would be great to document this behaviour until the issue is fixed.
The text was updated successfully, but these errors were encountered: