Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2007-08-13 10:43:30 →
Size: 577
Editor: TimoSirainen
Comment:
← Revision 4 as of 2007-08-13 10:44:56 → ⇥
Size: 690
Editor: TimoSirainen
Comment:
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:
When searching non-ASCII text, you'll have to specify CHARSET parameter. There is no way to list supported charsets, but you do get a {{{[BADCHARSET]}}} tag if the used charset isn't supported. So you can only guess. UTF-8 should be supported by all servers nowadays, and there probably isn't much point in trying to guess any others. Note that 8bit parameters must be sent only using literals. When searching non-ASCII text, you'll have to specify CHARSET parameter. There is no way to list supported charsets, but you do get a {{{[BADCHARSET]}}} tag if the used charset isn't supported. So you can only guess. UTF-8 should be supported by all servers nowadays, and there probably isn't much point in trying to guess any others.

8bit parameters must be sent only using literals:

{{{
1 SEARCH TEXT "pää"
1 BAD 8bit text in quoted string.
2 SEARCH TEXT {3}
+ OK
pää
* SEARCH 3
2 OK
}}}

Searching Messages

Make sure you're able to handle multiple SEARCH replies returning messages non-ordered: 

1 UID SEARCH ALL
* SEARCH 5 2
* SEARCH 1 6
1 OK

When searching non-ASCII text, you'll have to specify CHARSET parameter. There is no way to list supported charsets, but you do get a [BADCHARSET] tag if the used charset isn't supported. So you can only guess. UTF-8 should be supported by all servers nowadays, and there probably isn't much point in trying to guess any others.

8bit parameters must be sent only using literals: 

1 SEARCH TEXT "pää"
1 BAD 8bit text in quoted string.
2 SEARCH TEXT {3}
+ OK
pää
* SEARCH 3
2 OK

None: ClientImplementation/Search (last edited 2011-09-26 20:00:14 by TimoSirainen)