Bug 290420 - Spelling window shows bold markup when less than sign is in context area.
Summary: Spelling window shows bold markup when less than sign is in context area.
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kspell (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-02 17:01 UTC by Chris Fritz
Modified: 2023-01-20 05:09 UTC (History)
2 users (show)

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


Attachments
"Check Spelling" window showing the unexpecte result. (38.48 KB, image/png)
2012-01-02 17:01 UTC, Chris Fritz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Fritz 2012-01-02 17:01:52 UTC
Created attachment 67346 [details]
"Check Spelling" window showing the unexpecte result.

Version:           unspecified (using Devel) 
OS:                Linux

When running "Spelling", the "Check Spelling" window includes a line at the top showing the context of the misspelled word.  If there is a less than sign before the misspelled word, then misspelled word appears not bolded, and instead shows bold markup.

Reproducible: Always

Steps to Reproduce:
1) Key in a less than sign followed by a misspelled word.  For example:

  one < tuo

2) From the "Tools" menu, select "Spelling".  This will open the "Check Spelling" window due to the misspelled word.

Actual Results:  
Using the example above, the context area shows:

one < <b>tuo</b>...

(Nothing is in bold.)

Expected Results:  
The expected result in the context area is:

one < tuo...

(The word "tuo" should be in bold.)

OS: Linux (x86_64) release 3.1.6-1-ARCH
Compiler: gcc

I couldn't find the exact versions in the version drop-down menu, but this is using:

KDE 4.7.4
Kate 3.7.4
Kate Part 3.7
Comment 1 Christoph Cullmann 2012-10-27 09:17:42 UTC
Seems for me to be issue inside the sonnet spellcheck dialog.
Comment 2 Andrew Crouthamel 2018-11-09 00:55:46 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 3 Andrew Crouthamel 2018-11-18 03:32:27 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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2022-12-21 23:58:23 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2023-01-05 05:25:49 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 6 Bug Janitor Service 2023-01-20 05:09:03 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!