I also plan to make a jabberclient support Chinese, but I think jabbercom may support Chinese, if you convert Chinese into utf-8, default xml encoding is 'utf-8', if not ,you should convert into utf-8, most xml parser(include jabbercom buildin xml parser) not support Chinese native encoding (gb2312,gbk...),exept xml4c/xml4j(about that you should visit ibm alphaworks). now ,I want to use libunicode,and you should try it. �� 2002-01-24 �� �� 09:19�� qhzhao ��� > I make a jabberclient based on jabbercom,But jabbercom cann't support chinese .Have >any version of jabbercom to support chinese?if no,how can I support chinese? > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, January 24, 2002 2:01 AM > Subject: jdev digest, Vol 1 #1218 - 3 msgs > > > > Send jdev mailing list submissions to > > [EMAIL PROTECTED] > > > > To subscribe or unsubscribe via the World Wide Web, visit > > http://mailman.jabber.org/listinfo/jdev > > or, via email, send a message with subject or body 'help' to > > [EMAIL PROTECTED] > > > > You can reach the person managing the list at > > [EMAIL PROTECTED] > > > > When replying, please edit your Subject line so it is more specific > > than "Re: Contents of jdev digest..." > > > > > > Today's Topics: > > > > 1. Re: Jabber behind a firewall (Kevin Smathers) > > 2. [ANN] Jabberpy 0.3 Released (mallum) > > 3. getting iqs to remote servers (Mark Cheverton) > > > > --__--__-- > > > > Message: 1 > > Date: Tue, 22 Jan 2002 10:06:46 -0800 > > From: Kevin Smathers <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: Re: [JDEV] Jabber behind a firewall > > Reply-To: [EMAIL PROTECTED] > > > > Getting Jabber to work from behind a firewall at all takes quite a bit > > of help from your firewall administrator; the usual recommendation is > > to simply unblock the ports required for Jabber at the firewall. > > > > Of course you can run your own separate Jabber network using your own > > servers for employees to connect to, but they won't be able to message > > external users unless the s2s link can be started, and s2s uses a TCP > > dial-back to ensure that the link can be opened in both directions. > > > > The other option is to rely on public servers, and proxy just the c2s > > link. That link is only opened from the client to the server, so it > > can go through firewalls or proxies without trouble. The easiest > > approach then would be to get your firewall administrator to unblock > > the Jabber port in your socks proxy and use a socksified Jabber client > > (which most of them are.) > > > > Running socks libraries over an HTTP transport is possible if I > > recall correctly. Try looking up the Dante project: > > > > http://www.inet.no/dante/ > > > > Cheers, > > -kls > > > > > > On Sat, Jan 19, 2002 at 01:40:34AM +0100, MadCoder wrote: > > > So. I wants to install a Jabber server with ICQ/MSN/Y! transport support. > > > > > > but my server is behind a HTTP proxy and a SOCKS5 proxy. > > > in the SOCKS5 proxy, only the ICQ port is open. > > > > > > is there something I can do to socksify the jabber daemon threw the HTTP > > > proxy ? > > > > > > I saw on www.jabber.org that there was a project called "jabber web" that > > > wanted to enable jabberd socksification. but there's nothing to download > > > :(( > > > > > > PS : the server is under Debian-woody > > > > > > PPS : sorry for my poor english. I'm french. > > > _______________________________________________ > > > jdev mailing list > > > jdevOjabber.org > > > http://mailman.jabber.org/listinfo/jdev > > > > -- > > // .--=, > > .....::://::::::::::::::::::::::::::::.. (o O & [EMAIL PROTECTED] > > :::::::://:::://://://:/:://::||_// / V K > > :::::://:::://:/:|//'/' // _,|' r , 'qk > > :'''/____ // / // |_// // || .'~. .~`, > > kls \_/-=\_/ > > > > --__--__-- > > > > Message: 2 > > Date: Tue, 22 Jan 2002 23:39:13 +0000 > > From: mallum <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED], [EMAIL PROTECTED], > > [EMAIL PROTECTED] > > Subject: [JDEV] [ANN] Jabberpy 0.3 Released > > Reply-To: [EMAIL PROTECTED] > > > > Im pleased to announce the 0.3 release of Jabberpy. > > > > Get it while its hot from; > > > > http://jabberpy.sf.net > > > > This new release includes; > > > > o Many bug fixes, including encoding problems. > > o License change to LGPL. > > o Server Component support. > > o Improved Roster / JID / X 'payload' support. > > o New 'Stackable' handlers. > > o SSL support. > > o A maturing pygtk client. > > o A pyQt client. > > o New and improved examples. > > > > > > What is it? > > ----------- > > Jabberpy is a Python module for the Jabber [1] instant messaging > > protocol. > > > > The eventual aim is to produce a fully featured easy to use library > > for creating jabber clients, components and servers. > > > > Jabberpy requires at least python 2.0 and the XML expat parser module > > ( included in the standard Python distribution ). > > > > It is developed on Linux but should run happily on other Unix's > > and win32 . > > > > Jabber.py is released under the LGPL license. > > > > > > Please download, try and enjoy. > > > > All constructive feedback is appreciated. > > > > Thanks to all that have helped out with this release. > > > > -- mallum > > [EMAIL PROTECTED] > > > > > > [1] http://jabber.org > > > > --__--__-- > > > > Message: 3 > > From: Mark Cheverton <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Date: 23 Jan 2002 17:04:35 +0000 > > Subject: [JDEV] getting iqs to remote servers > > Reply-To: [EMAIL PROTECTED] > > > > Hi guys, > > > > I'm currently trying to get it so that a user on one server can register > > for a group on another server (I've fixed a bug or two in mod_groups and > > realised my Gabber version doesn't support browsing, so alls wel getting > > it working now). > > > > Currently when a user tries to send the packet it seems to get delivered > > to the wrong instance (the servers are all CNAMEd to the same process > > atm, but setup as totally seperate vhosts with their own service > > sections): > > > > Wed Jan 23 16:38:16 2002 mio.c:698 MIO read from socket 12: <iq > > type="set" id="JCOM_46" to="im.lon.sports.com/groups/london"><query > > >xmlns="jabber:iq:register"><name>madr</name><key>aca71f39fd338d5cb2a550eba434caa9aff4ede1</key></query></iq> > > Wed Jan 23 16:38:16 2002 client.c:243 pthsock_client_read called with: > > m:8292910 flag:3 arg:82930F0 > > Wed Jan 23 16:38:16 2002 deliver.c:460 DELIVER 4:im.mad.sports.com > > <route to='[EMAIL PROTECTED]/82B2000' from='12@c2s/8292910'><iq > > type='set' id='JCOM_46' to='im.lon.sports.com/groups/london'><query > > >xmlns='jabber:iq:register'><name>madr</name><key>aca71f39fd338d5cb2a550eba434caa9aff4ede1</key></query></iq></route> > > Wed Jan 23 16:38:16 2002 deliver.c:649 delivering to instance > > 'im.mad.sports.com' > > Wed Jan 23 16:38:16 2002 deliver.c:83 (81BC4D0)incoming packet <route > > to='[EMAIL PROTECTED]/82B2000' from='12@c2s/8292910'><iq > > type='set' id='JCOM_46' to='im.lon.sports.com/groups/london'><query > > >xmlns='jabber:iq:register'><name>madr</name><key>aca71f39fd338d5cb2a550eba434caa9aff4ede1</key></query></iq></route> > > Wed Jan 23 16:38:16 2002 users.c:137 > > js_user([EMAIL PROTECTED],82B3C68) > > Wed Jan 23 16:38:16 2002 mtq 81EE808 entering from pth > > Wed Jan 23 16:38:16 2002 mtq 81EE808 queue call 8294078 > > Wed Jan 23 16:38:16 2002 sessions.c:234 THREAD:SESSION:FROM received a > > packet! > > Wed Jan 23 16:38:16 2002 modules.c:124 mapi_call 1 > > Wed Jan 23 16:38:16 2002 modules.c:147 MAPI 82B22A8 > > Wed Jan 23 16:38:16 2002 mod_groups Register request > > Wed Jan 23 16:38:16 2002 mod_groups Getting info london > > > > although I may be confusing things and it may be the responsibility of > > the module to send this on rather than the server itself, though it > > seems to me that if something is addressed to > > im.lon.sports.com/groups/london then it should be sent there by the > > server without ever touching the local module. > > > > Can someone give me a few pointers here to understand why Im having this > > delivery issue, or will jabber not deliver these formats of remote JIDs > > at all? > > > > -Mark > > > > > > > > --__--__-- > > > > _______________________________________________ > > jdev mailing list > > [EMAIL PROTECTED] > > http://mailman.jabber.org/listinfo/jdev > > > > > > End of jdev Digest > > _______________________________________________ > jdev mailing list > [EMAIL PROTECTED] > http://mailman.jabber.org/listinfo/jdev > >
_______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
