headers
Alexey Melnikov | 1 Dec 2007 23:35
Favicon

Ad-hoc meeting to discuss IMAP Internationalization


With permissions of IMAPEXT and Lemonade chairs, I've put IMAP I18N 
document on the Lemonade WG agenda on Thursday, December 6th.
But I was thinking it might be better to spend some time before that, in 
order to make some progress on the document and save some time during 
the Lemonade WG meeting. I would also like to discuss future potential 
work on IMAP internationalization, because I would prefer to get 
draft-ietf-imapext-i18n done pretty much as is soon (within 2 months) 
and defer any further work till another document.

So, is there any interest to meet up during one of the following slots 
in Vancouver:

Wednesday, December 5th, 15:10-16:10
Thursday, December 6th, 09:00-11:30

?
Permalink | Reply | 1 comment |
headers
Peter Coates | 2 Dec 2007 00:02
Picon

RE: Ad-hoc meeting to discuss IMAP Internationalization


I'm only going to be there the Wednesday and Thursday.  Either of those
times work for me.

-----Original Message-----
From: owner-ietf-imapext <at> mail.imc.org
[mailto:owner-ietf-imapext <at> mail.imc.org] On Behalf Of Alexey Melnikov
Sent: December 1, 2007 14:36
To: IMAP Extensions WG
Subject: Ad-hoc meeting to discuss IMAP Internationalization

With permissions of IMAPEXT and Lemonade chairs, I've put IMAP I18N 
document on the Lemonade WG agenda on Thursday, December 6th.
But I was thinking it might be better to spend some time before that, in 
order to make some progress on the document and save some time during 
the Lemonade WG meeting. I would also like to discuss future potential 
work on IMAP internationalization, because I would prefer to get 
draft-ietf-imapext-i18n done pretty much as is soon (within 2 months) 
and defer any further work till another document.

So, is there any interest to meet up during one of the following slots 
in Vancouver:

Wednesday, December 5th, 15:10-16:10
Thursday, December 6th, 09:00-11:30

?
Permalink | Reply | 0 comments |
headers
Ken Murchison | 3 Dec 2007 16:55
Picon

draft-daboo-imap-annotatemore-11


I'm in the process of migrating my older ANNOTATEMORE implementation to 
the new METADATA syntax and I noticed that draft -11 doesn't contain 
ABNF for the LIST-EXTENDED METADATA return option or the METADATA 
extended list data item (response).

--

-- 
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University
Permalink | Reply | 0 comments |
headers
Alexey Melnikov | 3 Dec 2007 15:20
Favicon

Discussion of IMAP I18N in Vancouver


We will meet on Thursday, 10am near the IETF message board.
Permalink | Reply | 0 comments |
headers
Alexey Melnikov | 3 Dec 2007 18:32
Favicon

Friends of IMAP dinner meeting time

Let's meet at 8pm today near the IETF message board.

_______________________________________________
lemonade mailing list
lemonade <at> ietf.org
https://www1.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade
Permalink | Reply | 0 comments |
headers
Alexey Melnikov | 8 Dec 2007 23:17
Favicon

Re: Updated IMAP I18N document


Mark Crispin wrote:

> I am uneasy about having COMPARATOR and UNICASEMAP as separate 
> capabilities, especially since COMPARATOR implies but does not require 
> UNICASEMAP.  This means that a client that only cares about UNICASEMAP 
> capability must test for both requirements.
>
> As an alternative, how about I18NLEVEL=<version #>, where version 1 
> means UNICASEMAP capability and version 2 means COMPARATOR?  This 
> implies that any subsequent additions will be additive with all 
> previous ones being mandatory-to-implement; but I think that is the 
> right thing in this case.

Based on various discussions in Vancouver it seems that people are Ok 
with this change.
If you object, please speak up now.
Permalink | Reply | 0 comments |
headers
Internet-Drafts | 8 Dec 2007 23:40
Picon
Favicon

I-D Action:draft-ietf-imapext-i18n-14.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Internet Message Access Protocol Extension Working Group of the IETF.

	Title           : Internet Message Access Protocol Internationalization
	Author(s)       : C. Newman, et al.
	Filename        : draft-ietf-imapext-i18n-14.txt
	Pages           : 18
	Date            : 2007-12-08

Internet Message Access Protocol (IMAP) version 4rev1 has basic
 support for non-ASCII characters in mailbox names and search
 substrings.  It also supports non-ASCII message headers and content
 encoded as specified by Multipurpose Internet Mail Extensions
 (MIME).  This specification defines a collection of IMAP extensions
 which improve international support including comparator negotiation
 for search, sort and thread, language negotiation for international
 error text, and translations for namespace prefixes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-imapext-i18n-14.txt

To remove yourself from the I-D Announcement list, send a message to
i-d-announce-request <at> ietf.org with the word unsubscribe in the body of 
the message.
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then
(Continue reading)

Permalink | Reply | 0 comments |
headers
Pete Resnick | 10 Dec 2007 02:25

QUICK WG Last Call: draft-ietf-imapext-i18n-14.txt


It is currently the belief of the chair and the editor that this 
document reasonably addresses all outstanding issues. Consider this a 
1 week last call for the WG. I'll be out of town until Monday, Dec. 
17. If you are not heard of by then, this document will be written up 
for IETF Last Call.

pr
--

-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102
Permalink | Reply | 15 comments |
headers
Timo Sirainen | 10 Dec 2007 12:33
Picon
Picon
Favicon

Re: QUICK WG Last Call: draft-ietf-imapext-i18n-14.txt

On Sun, 2007-12-09 at 19:25 -0600, Pete Resnick wrote:
> It is currently the belief of the chair and the editor that this 
> document reasonably addresses all outstanding issues. Consider this a 
> 1 week last call for the WG. I'll be out of town until Monday, Dec. 
> 17. If you are not heard of by then, this document will be written up 
> for IETF Last Call.

Looks pretty good, although I'm not sure if it's such a good idea to
have it specify how to handle invalid input / unknown charsets.
Especially for SORT:

    The ordering operation (e.g., IMAP SORT and THREAD) SHOULD collate
    the following together: strings encoded using unknown or invalid
    character encodings, strings in unrecognized charsets, and invalid
    input (as defined by the active collation).

Does that mean if I have messages sorted by subject:

abc
bcd =?unknown-charset?q?1234?=
cde

These should instead be sorted by:

abc
cde
bcd =?unknown-charset?q?1234?=

Would be better if this rule applied only at the position where the
unknown data was found.
(Continue reading)

Permalink | Reply | 14 comments |
headers
Arnt Gulbrandsen | 10 Dec 2007 13:14
Favicon

Re: QUICK WG Last Call: draft-ietf-imapext-i18n-14.txt


Timo Sirainen writes:
> Would be better if this rule applied only at the position where the 
> unknown data was found.

I think that's in scope for RFC 4790, not this document. And I don't 
remember what 4790 says, and I haven't the time to look it up now.

Arnt
Permalink | Reply | 0 comments |

Gmane