ValentijnNK / miranda

Automatically exported from code.google.com/p/miranda
0 stars 0 forks source link

Default roster:delimiter XEP-0083 Nested Roster Groups #1652

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Miranda Version                  : 0.10.8.0
Unicode Build                    : Yes

What steps will reproduce the problem?

Miranda is one clients what support XEP-0083. But I think it not full support. 
Because I can't to change roster:delimiter by self.
And Miranda ignore result that get from server (just reset it).

What is the expected result?

Set this delimiter by user or use delimiter got from server.

From XEP-0083
>A compliant client SHOULD ask for the nested delimiter before requesting the 
user's roster, in order to know whether or not to parse the roster >'group' 
fields accordingly. If there is no delimiter stored, a client MAY set a 
delimiter but MUST either prompt the user for a delimiter, or use >a 
user-configurable default.

What happens instead?

<iq type="get" id="mir_3">
<query xmlns="jabber:iq:private">
<roster xmlns="roster:delimiter" />
</query>
</iq>
­
<iq type="result" id="mir_3" to="user@example.com/Miranda">
<query xmlns="jabber:iq:private">
<roster xmlns="roster:delimiter">::</roster>
</query>
</iq>
­
<iq type="set" id="mir_8">
<query xmlns="jabber:iq:private">
<roster xmlns="roster:delimiter">\</roster>
</query>
</iq>

Original issue reported on code.google.com by Tem...@gmail.com on 25 Oct 2012 at 12:12