This gets very icky, very quickly :-P My feeling is that if you don't recognize the source character set, you cannot possibly convert it to a display format in any secure manner. By default I think we should not display the content, but instead spit out a diagnostic, with the option to re-run the show (or whatever) with a command-line option that passes the content through unconverted. I'm of mixed feelings about converting unknown characters to a proxy (e.g. '?'). This could be exploited to inject terminal escape sequences into xterm (or your VT220 – I know people who still use them!). Yet another argument for declaring nmh a utf8-only zone, and convert everything to that on the way in. We could bundle our own internal iconv and just call it a day. --lyndon
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Nmh-workers mailing list Nmh-workers(_at_)nongnu(_dot_)org https://lists.nongnu.org/mailman/listinfo/nmh-workers
Previous by Date: | Re: [Nmh-workers] General question - unsupported charset conversion, Ken Hornstein |
---|---|
Next by Date: | Re: [Nmh-workers] General question - unsupported charset conversion, Ken Hornstein |
Previous by Thread: | Re: [Nmh-workers] General question - unsupported charset conversion, Ken Hornstein |
Next by Thread: | Re: [Nmh-workers] General question - unsupported charset conversion, Ken Hornstein |
Indexes: | [Date] [Thread] [Top] [All Lists] |