Patrik F�ltstr�m <[EMAIL PROTECTED]> writes: >> What you are proposing seem to >> require a cut'n'paste protocol to be implemented in both the MUA and >> the address book application. > > Not at all.
OK, then I misunderstood what you said. Disregard my mail.. >> (d) Email program understands IDNA but is running in a non-Unicode >> environment. The address is tagged and is transfered to address >> book application using e.g. ISO-8859-1. IDNA doesn't handle or >> care about this scenario, but it do exists in the real world >> (e.g. my machine). > > See above, if the address is to be transferred to other application, it > should either be negotiated that it is an IDN in a specific charset (like > 8859-1) or sent as ACE. Even tagging data as being an IDN encoded into a (legacy) coding system isn't sufficient to use IDNA interoperably, as no transcoding tables are specified. But I'm starting to repeat myself from another thread now.
