a) you think we're all crazy (for some definition of 'all')
Yes.
b) you think we should simply convert the message at read time to UTF-8
No. The message must remain in its original format. But as we process it
internally, we do so as utf8. So I guess my answer really was yes.
and ONLY output UTF-8.
Yes.
Let's call this the 'Plan 9' approach.
If you like. Plan 9 is so 1980s in this regard. I would rather call it 21st
century :-)
The
user's locale setting is simply ignored, at least in terms of supported
character set.
Yes.
We would be telling everyone if they're not using UTF-8, then we don't
support you.
In the sense that we don't support your character set encodings, yes. In the
sense that we won't design interfaces to at least try to make it palatable for
you to provide your own character set conversion glue? No.
But the bottom line is utf8 is here to stay, and the other character sets will
become historical artifacts. It's absurd to spend thousands of lines of (new)
code supporting them.
That problem space lives well outside of nmh. The people to rightly fix it are
the xterm authors, and people writing keyboard drivers. These conversion layers
belong inside the terminal I/O drivers, where they can fix the problem for
everything.
--lyndon
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers