Comment # 11
on bug 10681
from Guy Harris
It might, perhaps, be nice to report *all* deviations from the presumed
character encoding in some fashion, although
1) to do it usefully might involve some way to mark those deviations in the
display form of the string (Unicode REPLACEMENT CHARACTER, perhaps - but what
if there's an actual REPLACEMENT CHARACTER in the string?) and have a pop-up
tooltip giving the raw byte sequence when you hover over one of those marked
deviations;
2) that might not work well for users with visual disabilities;
3) what about tshark?
For now, replacing invalid octet sequences with REPLACEMENT CHARACTER (or with
U+1F4A9, especially if the glyph has steam rising from it, or with U+1F595 in
many locales and U+1F594 in UK locales, or something along those lines) in the
display version of purportedly UTF-8 strings might make sense.
You are receiving this mail because:
- You are watching all bug changes.