>>>> Glynn Clements <glynn(a)sensei.co.uk> writes:
> but it smells as if eterm is assuming that the coding system is
> appropriate rather than making it so.
Define "appropriate." For example, today trying to figure out what
was going on in my undergraduate college's Web site, I saw English,
German, EUC, Shift-JIS, ISO-2022-JP, and Big5 (which is Chinese, for
those who tuned in late). I just verified that there is a sequence of
4 links which hits all of those last four in turn. DEC OSF/1's less
in a kterm got the English and the three flavors of Japanese right,
but didn't get the German or Chinese. At least with file input, you
can assume that the character coding will be consistent throughout,
and the buffer is all safely Mule internal encoding.
You can't make that assumption here. This is going to require user
intervention, even if LANG is set properly. Even if you can be pretty
sure of the OS messages, who knows what cat is going to spew?
It would be nice if you could screw up the coding system first time
through and go back and fix what's in the buffer, too. I've never
figured out how to do that in Mule, though. It should be possible, I
think, although you may have to use some of the "private" functions.
> Is this MULE-related?
Or the recent surgical separation of file-encoding from Mule may have
exposed the underlying problem.