[JDEV] no text after quotes in conference - solved

John Reinke John.M.Reinke at mail.sprint.com
Fri Jan 18 16:27:32 CST 2002


David,

Thank you very, very much. I hadn't found that in the archives and it
has so far (knock on wood) solved all the problems.

There was one typo in the solution, the code was in the function
xmlnode_insert_node, not xmlnode_insert_data.

Can this change be made in the next version of the server?

John

On Fri, 2002-01-18 at 14:05, mass at akuma.org wrote:
> Perhaps it has something to do with this issue?
> http://mailman.jabber.org/pipermail/jdev/2001-September/008589.html
> 
> Odds go up if you are using a compiler besides GCC.
> 
> -David Waite
> 
> ----- Original Message -----
> From: "John Reinke" <John.M.Reinke at mail.sprint.com>
> To: <jdev at jabber.org>
> Sent: Thursday, January 17, 2002 10:33 AM
> Subject: [JDEV] no text after quotes in conference
> 
> 
> > No one has responded to this on the jadmin list, and the only occurance
> > I've found in the archives has no resolution. I'm not sure where to start
> > in resolving this, but I definitely need a solution.
> >
> > I have a problem where almost all my users have all the text on a line
> > disappear following a quote (single or double) or a handfull of other
> > characters. Other clients without the problem can still see all of the
> > message.
> >
> > This wasn't a problem as each person started using Jabber, but once it
> > happens, we can't seem to fix it. We've tried restarting the client,
> > rebooting the machines (Win2k), and even uninstalling and reinstalling
> > the clients. It seems to be a problem on the server end.
> >
> > This happens mainly with the JIM client, and support at jabber.com suggests
> > upgrading the OSS server. I'm currently running 1.4.1, with conference
> > 0.4.1, on Solaris 8.
> >
> > This is rather frustrating, since it really prevents serious usage of
> > conferencing for any technical conversations. We even have to restrict
> > the use of contractions (it's, that's, etc) in sentences.
> >
> > Any suggestions would be greatly appreciated.






More information about the JDev mailing list