zf8848 / libjingle

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

libjingle doesnt use utf-8 in xmpp messages #130

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. use libjingle in any non-english windows system
-
What is the expected output? What do you see instead?

After libjingle makes session it start data exchange about preffered connection 
points looks like
SEND >>>>>>>>>>>>>>>> : Fri Jan 28 04:01:29 2011
   <iq to="server@ingerdev.com/19139412091296180044668002" type="set" id="9">
     <jingle xmlns="urn:xmpp:jingle:1" action="transport-info" id="1247312448" initiator="client@ingerdev.com/544483627129618008159002">
       <content name="tunnel" creator="initiator">
         <transport xmlns="http://www.google.com/transport/p2p">
           <candidate name="tcp" address="10.0.0.1" port="56002" preference="1" username="OWux6xHg2RNJYD9g" protocol="udp" generation="0" password="bMNnR0oi9rfSqD6/" type="local" network="Atheros AR8121/AR8113/AR8114 PCI-E Ethernet Controller(NDIS6.20)"/>
         </transport>
       </content>
     </jingle>
   </iq>

But on non-english system network adapters can be named in system-default 
locale style using cyrillic or deutch symbols. And xmpp server (ejabberd 2.1.6) 
when  received non-utf8 characters immediatelly stop 
connection and session failed.

-
What version of the product are you using? On what operating system?

libjingle 0.5.1, windows 7 x64/windows xp x32
-

Any suggestions?

Original issue reported on code.google.com by inger...@gmail.com on 28 Jan 2011 at 4:13

GoogleCodeExporter commented 9 years ago
you should convert any other encodes to utf-8 string to xmpp engine.

Original comment by greatfoolbear on 28 Jan 2011 at 4:38

GoogleCodeExporter commented 9 years ago
As i see in source, network adapter names used only in debug mode. I tested 
release libjingle version - all is ok, no problem with it.

Original comment by inger...@gmail.com on 31 Jan 2011 at 12:27

GoogleCodeExporter commented 9 years ago
This seems not an issue.

Original comment by jun...@google.com on 3 Feb 2011 at 12:11