dovecot - Jan 2010 - IMAP client dependence on dovecot mail storage fromat?

Hi,

After setting up a maildir tree with :LAYOUT=fs and accessing it with KMail 
and Thunderbird, various mail client-specific problems appeared, but, as I 
didn't try with maildir++, I would like to confirm here: does that matter
for
an IMAP client much if I store mail on server as ":LAYOUT=fs" or
maildir++?
Can it see differences? 
I would like to think, that IMAP protocol should provide for all transactions 
in a standard way and its dovecot's/server's sole business how it stores
mail
locally. 
However... These results seem not very good:
KMail: try creating a folder "sub" in "parrent" and
you'll get "parrent.sub"
along with "parrent" on server side. There, however, are no problems
with
Latvian unicode chars.
Thunderbird: it can create a new folder in "parrent" as desired, but
it can't
display Latvian unicode chars (being such at server side) on client, while, if 
I try creating a new folder with Thunderbird with these chars, on server it 
will look somewhat like base64!

So I'm really confused. All together these things are pretty frustrating, 
sure, but I'd like to understand whats the real problem here!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20100108/9534f710/attachment-0002.bin>

It might be useful to add this conversation here:

On Friday 08 January 2010 22:43:27 Ingo Kl?cker wrote:
> On Friday 08 January 2010, K?rlis Repsons wrote:
> >  On top of that, its impossible
> >  to create and access a new folder with KMail on my dovecot: it
> >  doesn't happen, that a new folder would be created with name
> >  "newfolder" into "parrentfolder", but along with
the latter
> >  "parrentfolder.newfolder" is created!
> 
> Hmm. "parentfolder.newfolder" sounds like maildir++. All KMail
(and also
> Thunderbird) does is tell the IMAP server to create a folder
"newfolder"
> below the folder "parentfolder". It's up to dovecot to
actually create
> the folder in its storage as needed. I cannot imagine why a folder
> created by Thunderbird results in parentfolder/newfolder while a folder
> created by KMail results in parentfolder.newfolder unless you switched
> dovecot's storage format.
Well, that is weird to me as I didn't! No joke, I did again:
Thunderbird 3.0;
KMail 1.12.1 Using KDE 4.3.1 (KDE 4.3.1);
dovecot-1.2.6;
So:
1) create folder TOP with KMail, then create a subfolder sub, which results 
in: "TOP" and "TOP.sub" (both prepared as maildirs with
cur,new,tmp and
maildirfolder file);
2) create folder "TOP2" on the same fs level with Thunderbird, then
create a
subfolder "sub2" into it, which results in: "TOP2" prepared
and containing
"sub2" also prepared (prepared just like with KMail).

So... Its reality!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20100109/73728a36/attachment-0002.bin>