Bug 132120 - Cursor is not shown at the correct position if there is an unknown character on a line
Summary: Cursor is not shown at the correct position if there is an unknown character ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2006-08-09 09:59 UTC by S. Burmeister
Modified: 2018-10-21 04:26 UTC (History)
2 users (show)

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


Attachments
funny filename (137 bytes, application/x-tgz)
2006-08-09 10:08 UTC, S. Burmeister
Details

Note You need to log in before you can comment on or make changes to this bug.
Description S. Burmeister 2006-08-09 09:59:26 UTC
Version:            (using KDE KDE 3.5.4)
Installed from:    SuSE RPMs
OS:                Linux

I see this in kwrite, quanta but also in koqnueror's text-fields while typing this bug-report, which is why I did not know which application I should assign this to.

If there are characters that cannot be displayed correctly, be it a small space (which is not displayed at all but shows the symptoms) or a malformed Umlaut, the cursor is shown one position to the left of its actual writing position, i.e. where a letter typed appears.

I am not sure if this example gets through, but if I paste the following into konqueror's text-field I am typing in, the cursor is shown before the "r" yet typing results in letters being added after the "r".

F
Comment 1 S. Burmeister 2006-08-09 10:06:53 UTC
Ok, it does not get through. I'll attach an archive which has a filename in it. For me that filename shows two squares in between the f and the r. Copy the f..r into a textfield, e.g. the one when adding comments to bugs and watch the cursor. I hope this works. :)
Comment 2 S. Burmeister 2006-08-09 10:08:16 UTC
Created attachment 17304 [details]
funny filename
Comment 3 Médéric Boquien 2008-11-09 01:59:12 UTC
Hello,

Can you still reproduce the bug with the latest KDE 4 release?

Thanks.
Comment 4 FiNeX 2009-08-04 14:16:24 UTC
If someone can reproduce the bug, a screenshot could be useful too :)
Comment 5 Andrew Crouthamel 2018-09-20 03:20:07 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 set the bug status 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 Andrew Crouthamel 2018-10-21 04:26:59 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!