RE: Internationalization of IMAP servers/clients

RANDY@mpa15ab.mv.unisys.com Fri, 24 May 1996 22:16 UTC

Errors-To: owner-imap@cac.washington.edu
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: RANDY@mpa15ab.mv.unisys.com
Date: Fri, 24 May 1996 14:40:00 -0000
To: imap%CAC.WASHINGTON.EDU@mvdns1.mv.unisys.com, treister%BEADLE.STANFORD.EDU@mvdns1.mv.unisys.com, larryo%EXCHANGE.MICROSOFT.COM@mvdns1.mv.unisys.com
MMDF-Warning: Parse error in original version of preceding line at CNRI.Reston.VA.US
Subject: RE: Internationalization of IMAP servers/clients
In-Reply-To: Your message of "24 May 1996 13:25:54 -0700"
References: <c=US%a=_%p=Microsoft%l=TAPEWORM-960524202554Z-2447@feyuri.m icrosoft
Message-Id: <EG1Q3816160607@MPA15AB>

On 24 May 1996 13:25:54 -0700, "Larry Osterman (Exchange)" <larryo@
exchange.MICROSOFT.com> wrote:

> If we do LANGUAGE NUMERIC, we should also have a CAPABILITY
> ERRORSTRING, which would enable the new ERRORSTRING command....
>
> I sort of see this as two extensions:  The first is the basic LANGUAGE
> extension, the second is the ERRORSTRING extension, which relies on
> the LANGUAGE extension.

I like this idea.  One minor point:  what if (for whatever reason) the
server is unable to produce a specific error text in a requested
language?  I'd say the server should be permitted to return it in a
different language, of the server's (or admin's) choice.

--
|Randall Gellens             |                    randy@mv.unisys.com|
|(714) 380-6350              | fax (714)597-8053 can add ,,,,,,,,6350|
|Mail Stop MV 237            |                        Net**2 656-6350|
|Opinions are personal;  facts are suspect;   I speak only for myself|

                  Randomly selected tag:

Television has raised writing to a new low.      -- Sam Goldwyn

RE: Internationalization of IMAP servers/clients RANDY