Tokio Kikuchi firstname.lastname@example.org writes:
iso-2022-jp contains " and \ in the second byte. Big5 also.
That should not be a problem: the MBCS routines of the C library (or, rather, iconv) should be able to take care of that (if the encoding is known); so the problem can be solved. I know it isn't, but anybody interested in solving it could either report a bug or maybe even design a patch.