Bug 215270 - squared brackets in chat
Summary: squared brackets in chat
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 0.80.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-19 13:02 UTC by tedmosby
Modified: 2023-01-12 05:17 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tedmosby 2009-11-19 13:02:01 UTC
Version:           0.80.2 (using KDE 4.3.2)
OS:                Linux
Installed from:    Ubuntu Packages

if i get a message with a squared bracket, e.g. like "-->" or ">>" all characters behind it, inklusive the brackets aren't shown
even in the log-files (.kde/.../kopete/logs/...) the don't appear

excuse me for my bad english, greets from germany
Comment 1 Rémy Greinhofer 2009-12-20 17:24:06 UTC
I tried to reproduce the bug you described using the debian package of kopete (4:4.3.4-1) and I did not experience the problem.

If I input a message with square brackets in a chat window, in the log file (located in ~/.kde/share/apps/kopete/logs/_protocol_/_account_) I get:
<msg nick=".." in="0" from=".." time="20 17:10:19" >test square brakets</msg>
<msg nick=".." in="0" from=".." time="20 17:10:25" >before >> after</msg>
<msg nick=".." in="0" from=".." time="20 17:16:47" >another style --></msg>
<msg nick=".." in="0" from=".." time="20 17:16:55" >again another &lt;--</msg>
<msg nick=".." in="0" from=".." time="20 17:17:7" >and a last one &lt;&lt; for fun</msg>

As you can see, the square brakets do appear in the log file.

Do you still encounter the problem? If yes, could you be a bit more specific about a it? Thanks.
Comment 2 Dario Andres 2009-12-20 17:28:17 UTC
Marking as NEEDSINFO
Comment 3 tedmosby 2010-03-14 22:17:03 UTC
http://yfrog.com/jpsnapshotmp

 <msg nick="QQQQQ" in="1" from="QQQQQ" time="14 21:53:56">und jo, genau</msg>
 <msg nick="RRRRR" in="0" from="RRRRR" time="14 21:53:59">seh ich nich^^</msg>
 <msg nick="CQQQQQ" in="1" from="QQQQQ" time="14 21:54:13">haha xD</msg>
 <msg nick="QQQQQ" in="1" from="QQQQQ" time="14 21:54:21">htmltags mag er wohl nich</msg>
 <msg nick="RRRRR" in="0" from="RRRRR" time="14 21:54:24">haste mit leerzeichen geschickt?</msg>
 <msg nick="QQQQQ" in="1" from="QQQQQ" time="14 21:54:27">ja</msg>
 <msg nick="QQQQQ" in="1" from="QQQQQ" time="14 21:54:31">3 </msg>

-----------

the first was a "< 3"
and the second "3<"
we also tried "<3", but the same


-----------

kde 4.4.00
kopete 1.0.0
kubuntu
Comment 4 tedmosby 2010-08-01 15:48:19 UTC
nothing happens?
bug is already active.
Comment 5 Andrew Crouthamel 2018-11-05 03:10:07 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-11-16 05:34:28 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 7 Justin Zobel 2022-12-13 02:54:19 UTC
Thank you for reporting this issue in KDE software. As it was reported on an older version, can we please ask you to see if you cazn reproduce the issue with a more recent software version?  
  
If you can confirm this issue still exists in a recent version, please change the version field and the status to "REPORTED" when replying. Thank you!
Comment 8 Bug Janitor Service 2022-12-28 05:24:26 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2023-01-12 05:17:24 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!