Version: 0.7.93 (using KDE 3.1.93 (3.2 beta 1), compiled sources) Compiler: gcc version 3.3.2 (Debian) OS: Linux (i686) release 2.6.0-test11 I have set message windows to display the the last 10 messages from history. Today, when I logged in, I had some offline messages from Yahoo. The message window just showed the line given in the subject a few times. I guess this is because of the history-storing format. Today being the 1st of Dec., that is, a new month, the history files aren't read properly. On selecting the contact and clicking on view history, the messages are visible properly.
Subject: I wonder if it's a yahoo problem or a history problem. I'll play with the date on my computer for a bit and see what I can reproduce.
Subject: Re: "An internal Kopete error occurred while parsing a message:XSL document could not be parsed!" On Monday 01 Dec 2003 12:27, Matt Rogers wrote: > I wonder if it's a yahoo problem or a history problem. I'll play with the > date on my computer for a bit and see what I can reproduce. It's not a yahoo problem since even messages from the MSN protocol aren't displayed. Also, just checked: new messages sent aren't displayed as well. Any messages I send or I receive are not displayed; the error is displayed in the messages window. I unset the 'show old messages' from the history plugin and tried; same result. So it may not also be the history. I checked the logs, they're fine, not corrupted. Also, the 'view history' window shows them properly, so there probably wasn't a problem there anyways. But still.
Subject: Re: [Kopete-devel] New: "An internal Kopete error occurred while parsing a message:XSL document could not be parsed!" On December 01, 2003 2:28 am, Amit Shah wrote: > I have set message windows to display the the last 10 messages from > history. Today, when I logged in, I had some offline messages from Yahoo. > The message window just showed the line given in the subject a few times. I > guess this is because of the history-storing format. Actually, this error is usually because the message contained color codes and whatnot that weren't stripped off properly. Do you know if this offline message had color information in it?
Subject: Re: "An internal Kopete error occurred while parsing a message:XSL document could not be parsed!" On Monday 01 Dec 2003 18:06, Jason Keirstead wrote: > Actually, this error is usually because the message contained color codes > and whatnot that weren't stripped off properly. > > Do you know if this offline message had color information in it? They didn't have any color information in them. Also, the older messages, which I could see a couple of days back are now not shown. This err message is shown in their place. Even messages sent by me aren't seen. I frequently take backups of the .kde directory, had taken a backup just before I started kde today. There weren't (nearly) any changes in the kopeterc file. I wonder what would've gone wrong. Hence, I guessed it could be a date issue. But since even messages sent by me aren't shown, I guess it could be something else.
Subject: Re: [Kopete-devel] "An internal Kopete error occurred while parsing a message:XSL document could not be parsed!" On December 01, 2003 8:42 am, Amit Shah wrote: > I frequently take backups of the .kde directory, had taken a backup just > before I started kde today. There weren't (nearly) any changes in the > kopeterc file. I wonder what would've gone wrong. Hence, I guessed it could > be a date issue. But since even messages sent by me aren't shown, I guess > it could be something else. The files you need to check for changes are the $KDEDIR/share/apps/kopete/ styles/*.xsl files, which are your Kopete XSLT themes. If you have added or modified any of those styles, there would also be some in your $KDEHOME under that prefix.
Subject: Re: "An internal Kopete error occurred while parsing a message:XSL document could not be parsed!" On Monday 01 Dec 2003 18:23, Jason Keirstead wrote: > The files you need to check for changes are the $KDEDIR/share/apps/kopete/ > styles/*.xsl files, which are your Kopete XSLT themes. If you have added or > modified any of those styles, there would also be some in your $KDEHOME > under that prefix. Oh well, those files were okay, but it turns out that no style was selected in the appearances window. I haven't tweaked my settings in quite some while. Why would this setting be affected, then? I selected my custom style and then all was fine. I remember one of my friends too had this problem, and he couldn't see any of his messages in the message window. I had suggested him to change his style then... and we found out that none of the styles was selected in his case too. I had forgotten about this incident... and since in my case, I got err messages in the window, I didn't think about the same problem. Now, is this a bug while saving the config file at close time, or is this a problem somewhere else? Note: I have my own custom style config; but my friend (who's using 0.7.3) doesn't have a custom one.
It's certenly because you used CVS, something may have change in the style or something like that.
Subject: Re: "An internal Kopete error occurred while parsing a message:XSL document could not be parsed!" On Friday 05 Dec 2003 02:30, Olivier Goffart wrote: > ------- It's certenly because you used CVS, something may have change in > the style or something like that. Well, I've also reported that my friend, who was using 0.7.3 got this problem. He hadn't upgraded recently, or anything. He came to office, started kopete and it behaved strangely. Similar experience with me: I'm using Kopete that shipped with kde3.2beta1. No upgrades, no changing config, nothing. Just started kopete (have to do this, since kdewallet isn't used while reconnecting), and got this behavior. It's got to be something else.
I've had this strange behaviour. Go to Kopete's settings, appearence and select your theme again. This will solve the problem.
Subject: Re: "An internal Kopete error occurred while parsing a message:XSL document could not be parsed!" On Friday 05 Dec 2003 19:43, Thiago Macieira wrote: > I've had this strange behaviour. Go to Kopete's settings, appearence and > select your theme again. This will solve the problem. One more case of the bug being reported...
An internal Kopete error occurred while parsing a message: XML document could not be parsed! I get this error when few of my buddies message me. I am not sure why I get this error. Atleast a suggestion or better error should be given to the end user
Subject: Re: "An internal Kopete error occurred while parsing a message:XSL document could not be parsed!" On Wednesday 17 Dec 2003 19:56, rahul sundaram wrote: > 15:26 ------- An internal Kopete error occurred while parsing a message: > XML document could not be parsed! > > I get this error when few of my buddies message me. I am not sure why I get > this error. Atleast a suggestion or better error should be given to the end > user probably setting some style sheet in the 'appearance' setting in 'configure kopete' would help.
If not, it's an encoding problem, as in bug #67727
KDE-3.2 (release), kopete-0.8.0 (release), ICQ plugin: Got the same error: -- An internal Kopete error occurred while parsing a message:XSL document could not be parsed -- Didn't change any settings after upgrade from 0.7.x ...
I forgot: * I can't see my messages, but the receiver can. * I can't read any messages sent to me to an open chat window, but I _can_ read them in the "notification-bubble" when no chat window is open?! BTW, on konsole I get: -- MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0 -- Is this related?
Subject: Re: "An internal Kopete error occurred while parsing a message:XSL document could not be parsed!" On Wednesday 04 Feb 2004 02:51, Daniel Franke wrote: > Got the same error: > -- > An internal Kopete error occurred while parsing a message:XSL document > could not be parsed -- Select some style from configure->appearances..
I get this error when I recive a message where a word contains 2(!) german umlaute like "Frühstück" (german: breakfast).
@ Frank: Select "Windows Codepage 1252" for contacts where that happens. See contacts userinfo-dialog, "Encoding" on first tab.
I get this same error when my Friend send 'Prööt' message. (it's Finnish, and dont mean anything, just Prööt) In notification buble it show up like 'Pr t' but in message window it get that error, sometimes i get that error in message window too. I have tryed that style thing but it wont help for me.