> Even though our default xterm(1) configuration is robust enough > that it usually doesn't break anything, I'm not convinced > indiscriminately printing UTF-8 is a good idea.
The first part of that sentence contains way too much optimism. xterm and robust probably do not belong in the same sentence. Sadly, xterm is unsafe software from 20 years ago which annually has doubled down on extending the featureset rather than taking moments to refactor for safety. I agree about the UTF-8 concerns. It is getting downright dangerous to use xterm in non UTF-8, and it feels like something eventually has to be done to resolve that.
