Follow-up Comment #4, bug #50606 (project findutils): As an aside, when garbage characters show up where text is expected, and especially if ordinary ASCII characters seem to be coming through OK, it's often worth checking whether you're seeing non-ASCII characters encoded with UTF-8. I wind up doing this once or twice a year.
Of course, you can't memorize the Unicode table, but you can remember the way to translate: First, figure out what the actual bytes are. (The OP did an admirable job of this, showing which bytes had the high bit set.) Decode them into their bits. Now interpret those bits using the UTF-8 encoding (https://en.wikipedia.org/wiki/UTF-8) to find out what the character numbers ("code points") are. Then look them up in the Unicode roadmap (http://www.unicode.org/roadmaps/bmp/). _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?50606> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
