jabberapplet-release — JabberApplet new release mailing list

[Jabberapplet-release] Still active?

[Barry H. <ba...@tr...>]

Is this still active?  I was planning on adding an applet param for port,
since I need to have a test server and a public server on one of my
machines.




--
Barry Hoggard
Tristan Media LLC
e: ba...@tr...
p: 212-627-1596
aim: hoggardb

[Jabberapplet-release] Anyone maintaining JabberApplet?

[<ke...@an...>]

Hi David,

Is anyone on the Sourceforge site still maintaining JabberApplet?  The
mailing list has been dead for ages, and I have some patches I may want
to submit in the next couple of weeks.

Here are the usability problems I'm likely to work on.

* Send message without a person selected silently ignores the request
* Show online users without anyone in your subscription list just shows
  an empty list.  Should show 'no one is in your list'.
* Add user requires JID.  Should be able to browse online users
* File transfer support
* Video IM support (via JMS)
* Optionally package and run as an application rather than applet
* Fix errors in the MiniXML parser
* Bring up error messages for commonly encountered problems

Cheers,
-kls


-- 
          //                               .--=,
 .....::://::::::::::::::::::::::::::::.. (o O &           ke...@an...
:::::::://:::://://://:/:://::||_//       / V  K   
 :::::://:::://:/:|//'/' // _,|'         r ,  'qk   
  :'''/____ // /  //  |_// // ||        .'~.  .~`, 
                                   kls   \_/-=\_/

[Jabberapplet-release] Problems with encoding

[<jn...@li...>]

 I've sent this problem before to you, to the mailing lists and to the bug 
submition form.

 I'm Portuguese and, because of that, I usually write accents. The real 
problem is:

 * When I send messages or similar data, JabberApplet sends the message body 
"as is", i. e., if I write accents they're sent with no conversion;

 * The Jabber server is expecting UTF-8, as the XML spec assumes by default. 
When I send some message with accents, it classifies the message XML as 
invalid and shuts down the connection.

 Let's see the problem on the other side now:

 * Other clients send me their data in UTF-8, as it's supposed to happen. The 
problem is that JabberApplet doesn't translate the message body to ISO 
8859-1, and all I get is the message body in UTF-8, i. e., with lots of weird 
characters.

 Can you fix that problem? It would be great if you do. I find the 
JabberApplet very interesting, but that bug keeps me from using it. But don't 
worry, JabberApplet isn't the only client with that bug. I found lots of 
clients with it.

 I would appreciate if you reply to this message, meaning that you received 
it and acknowledged it. If there's a next release to go out, could that be 
corrected in it, so I and the people on the enterprise I'm working on could 
start using it?

 By the way, the last binary release doesn't match the CVS code. It seems the 
code in the CVS is for JabberApplet 1.0, not 1.1.

 Thanks

 Jose Nuno Pires