Bug 123208 - Do not interpret emoticons as quote characters when using Fancy Formatting
Summary: Do not interpret emoticons as quote characters when using Fancy Formatting
Status: RESOLVED UNMAINTAINED
Alias: None
Product: knode
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-07 05:26 UTC by Tristan Miller
Modified: 2018-09-04 18:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot showing described behaviour (17.37 KB, image/png)
2006-03-07 05:27 UTC, Tristan Miller
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tristan Miller 2006-03-07 05:26:22 UTC
Version:            (using KDE KDE 3.5.1)
Installed from:    SuSE RPMs

There is a conflict between KNode's recognition of quote characters and emoticons (a.k.a. smileys).  Namely, if the first character on a line is part of an emoticon, it will also be interpreted as a quote character.

To reproduce:

1. In Settings->Configure Knode->Reading news->Viewer->Recognized quote characters, make sure the colon (:) is in the list.
2. Make sure Fancy Formatting is enabled (View->Fancy Formatting)
3. View a message that contains the smiley :) at the beginning of the line.

Observed results:

4. The line beginning with :) is rendered in the colour used for quoted text.

Expected results:

4. The line beginning with :) should be rendered in the style of normal text.

I haven't tested this extensively, so the bug may or may not occur with nested quoted text.
Comment 1 Tristan Miller 2006-03-07 05:27:18 UTC
Created attachment 14992 [details]
Screenshot showing described behaviour

The following line is rendered incorrectly as quoted text:

:-) Not with Windows, unless you install a proper MTA.
Comment 2 Andrew Crouthamel 2018-09-04 18:33:40 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.