Re: [EAI] Body parts

["Frank Ellermann" <hmdmhdfmhdjmzdtjmzdtzktdkztdjz at gmail.com>]

Shawn Steele wrote:

>> a "you SHOULD do the obvious" norm does not really help, or does it ?
 
> I think it does.  EAI requires that the client software understand
> UTF-8 (otherwise From: and To: look stupid), so any application
> must therefore be able to handle UTF-8 in the body as well.

That's what I doubted:  An EAI-aware MUA can of course handle UTF-8,
and hopefully the user of this MUA finds an e-mail service provider
with EAI-aware MSA / IMAP / POP3.  But this user might still have
friends with less capable MUAs and service providers, or use mailing
lists and newsgroups where UTF-8 is not yet the norm.

A technical SHOULD trying to modify netiquette would make me nervous.
Limited to "SHOULD be the default" it is acceptable, this could be
added to the eai-scenarios and/or eai-email-clients draft.

> This would help ensure that new implementations support UTF-8.

As you said, when they can do EAI at all they must support UTF-8.
And anybody implementing a MUA today without supporting UTF-8 is
a hopeless case.  The email-arch draft could note that as fact, it
has no I18N considerations so far:  A point for the Last Call, the
last time when I wanted a mere informative EAI reference in this
draft a bunch of IETF mail reactionists tried to lynch me... :-)

> Many modern devices, particularly phones, don't bother leading
> to the aforementioned compatibility issues

The LEMONADE folks don't belong to the old mail guard, I think.

> right now there's no *guaranteed* code page that'll work across
> all environments

There's RFC 2277 and 5198, anybody who still hasn't heard the shot
is deaf.  But UTF-8 is IMHO no *guaranteed* code page.  On my box
characters in code page 437, 819, 850, 858, 878, 923, 1252, and
others are *guaranteed* to work, encoded as UTF-8 or in various
"legacy" charsets.  Actually I never tested if my MUA can do 437,
850, 858, or 923, but the used fonts offer all glyphs for these
and many other code pages.  When I want a *guarantee* I use 1252,
and that is my default, replacing <http://purl.net/net/cp/819>.

 Frank

P.S.: Just for fun using http://purl.net/net/cp/878 in reply to your 819 ;-)

_______________________________________________
IMA mailing list
IMA at ietf.org
https://www.ietf.org/mailman/listinfo/ima