It's a fake encoding that we use to process text that's going into a
Tk widget. The font substitution mechanism allows for encoding
conversion, so Unicode CJK text, for instance, can be displayed
in an euc-cn or Big Five font. We abuse this mechanism a little
bit by putting in a dummy fallback font at the end of the search.
A character that has no representation in any font in the system
gets converted to a \xnn or \unnnn string by the X11ControlCharacters
encoding and displayed in an ISO8859-1 font.
Don't you feel better, knowing that? :)
--
73 de ke9tv/2, Kevin
Ah, thanks. Among other things, it is useful to know because there is
no point in presenting users with this choice of encoding. And I like
to think that I know every encoding, though that is no doubt a futile
task.