Bug 379506 - Code coloring shifted with some characters
Summary: Code coloring shifted with some characters
Status: CONFIRMED
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (Clang-based) (other bugs)
Version First Reported In: 5.1.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-04 13:04 UTC by Maverick Chardet
Modified: 2021-11-24 16:48 UTC (History)
2 users (show)

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

Attachments
Screenshot (14.04 KB, image/png)
2017-05-04 13:04 UTC, Maverick Chardet 		Details
Color shift due to ãáç (9.39 KB, image/png)
2021-11-24 14:12 UTC, Gianni 		Details
Color shift due to ã (8.85 KB, image/png)
2021-11-24 14:12 UTC, Gianni 		Details
Color shift now gone if remove ã (6.81 KB, image/png)
2021-11-24 14:14 UTC, Gianni 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Maverick Chardet 2017-05-04 13:04:28 UTC 
Created attachment 105338 [details]
Screenshot

I noticed a shift of the text coloring when using some characters (see attached file). I suspect UTF-8 support to be the cause. It might not be valid C++ but I suppose that it is not the way this error should be highlighted.

Code:

#include <iostream>

void print(std::ostream& os) {
  os << "δ" << std::endl;
}
Comment 1 Gianni 2021-11-24 14:12:30 UTC 
Created attachment 143903 [details]
Color shift due to ãáç
Comment 2 Gianni 2021-11-24 14:12:59 UTC 
Created attachment 143904 [details]
Color shift due to ã
Comment 3 Gianni 2021-11-24 14:14:08 UTC 
Created attachment 143905 [details]
Color shift now gone if remove ã
Comment 4 Gianni 2021-11-24 14:15:28 UTC 
I've had the same issue with accents (portuguese strings).  As shown in the attachments I've added, any time I have a string with ãçá I get the shift.  If I substitute the ã for a the bug is gone.
Comment 5 Sven Brauch 2021-11-24 16:48:39 UTC 
Setting this to confirmed, it has definitely been a problem basically forever.