As I tried to use Hexyl on content using characters from the extended ASCII table (8-bits table, as opposed to the original 7-bits one), I was shown with xx representations.
After some reading of the --help, I stumbled on this:
- default: Show printable ASCII characters as-is, '⋄' for NULL bytes, ' '
for space, '_' for other ASCII whitespace, '•' for other ASCII characters, and
'×' for non-ASCII bytes
However I'd tend to say many people around Europe reading this expect it to cover the clearly not recent (https://en.wikipedia.org/wiki/Extended_ASCII) extended ASCII table, using 8 bits and covering many of the most used latin characters in Europe and with usually a wide support.
If for any reason it's preferred to stick to the original 7-bits table, I'd suggest to clarify it, unless it's considered ASCII is clear enough for most people and I'm wrong on that one. I can open a PR if needs be (although I'm not sure of how to word this yet).
I'd be interested though as to why chose to not show any UTF character provided the font allows for it, and if you prefer to stick to 7-bits ASCII, why so? (While I can still see situations where Unicode would still not be well supported, I don't think that'd be the case for extended ASCII?)
As I tried to use Hexyl on content using characters from the extended ASCII table (8-bits table, as opposed to the original 7-bits one), I was shown with
xxrepresentations.After some reading of the
--help, I stumbled on this:However I'd tend to say many people around Europe reading this expect it to cover the clearly not recent (https://en.wikipedia.org/wiki/Extended_ASCII) extended ASCII table, using 8 bits and covering many of the most used latin characters in Europe and with usually a wide support.
If for any reason it's preferred to stick to the original 7-bits table, I'd suggest to clarify it, unless it's considered ASCII is clear enough for most people and I'm wrong on that one. I can open a PR if needs be (although I'm not sure of how to word this yet).
I'd be interested though as to why chose to not show any UTF character provided the font allows for it, and if you prefer to stick to 7-bits ASCII, why so? (While I can still see situations where Unicode would still not be well supported, I don't think that'd be the case for extended ASCII?)