[Jabber-IETF] internationalization/localization

Marshall Rose mrose+internet.ietf.jabber at dbc.mtview.ca.us
Tue Oct 15 16:52:44 CDT 2002

> The problem is when we have s2s situations, including using a GroupChat
> service on a remote server.  (Example: I access jdev at conference.jabber.org
> from my jabber.com account).
> It is likely that the remote service would want to know my locale, so that
> the configuration information for rooms could be localized for me.  How
> should it determine that?
> Yes, you could argue that this should be the responsibility of the groupchat
> protocol (which is not currently in scope for the IETF work), but I think
> there is a generic problem here.
> Let me try to boil a suggestion down to an algorithm that a server could
> use:
> 1) The client SHOULD include xml:lang on stream:stream.
> 2) If server sees xml:lang on the stream:stream, it SHOULD remember that
> value.
> 3) If the server does not receive an xml:lang from the client, it SHOULD
> have a configurable default locale that it remembers instead.
> 4) For all packets, if the client does not send an xml:lang attribute on the
> root tag of the packet, the server SHOULD apply its remembered value.
> 5) If the client does send an xml:lang attribute on a packet, the server
> MUST NOT modify or delete it.

well, this sounds like a reasonable way to proceed.


More information about the xmppwg mailing list