True xml:lang isn't a perfect solution but it does provide a fairly easy way to support designating which language you are speaking without changing the protocol. We handle multiple langs in a single message buy using mutiple <message> stanzas each with their own xml:lang attribute. In our client we provide a drop down that let's the user select the lang for each message sent. You can try it out by downloading our client from https://xmpp.je.jfcom.mil
If you are using multiple langs within the same stanza then you're out of luck. We have been using this approach for 2 years in production environments with a high degree of success. Boyd -----Original Message----- From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> To: XMPP Extension Discussion List <[email protected]> Sent: Mon Feb 18 04:10:00 2008 Subject: Re: [Standards] UPDATED: XEP-0171 (Language Translation) Boyd Fletcher pisze: > BTW, the language a user is speaking is identified by the XML:Lang attribute > to the presence or message packet which unfortunately major clients to not > send. It's not easy to send xml:lang that always provides accurate information. Yes, we can guess the language by looking at system locale, client's translation pack selected by user, active keyboard layout, etc, etc, but it still won't work automatically in all cases. If I talk with one person in English and with other in Russian, a client could detect that different keyboard layouts and send different xml:lang attribute automatically. But if I talk in English and Polish, and all English characters are included in Polish layout, then the only way to detect this (without using AI, etc), would be asking the user to manually specify the language. And now think how many users will always set conversation language in every chat window.. -- Maciek xmpp:[EMAIL PROTECTED]
