Bug 445398

Summary: kcharselect not displaying all Unicode areas (eg displaying characters in the U+E000 range)
Product: [Applications] kcharselect Reporter: referenciaguido
Component: generalAssignee: Christoph Feck <cfeck>
Status: RESOLVED DUPLICATE    
Severity: major    
Priority: NOR    
Version: 21.08.3   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: You can check how kcharselect totally skips from U+DFFF to U+F000, making seem like U+E000 doesn't exists.
Seeing a bit more, I noticed that it detects U+E000 as basic latin block, which shouldn't be the case.

Description referenciaguido 2021-11-12 21:39:36 UTC
Created attachment 143504 [details]
You can check how kcharselect totally skips from U+DFFF to U+F000, making seem like U+E000 doesn't exists.

SUMMARY
kcharselect is not displaying all the Unicode characters, it divides them by "blocks", but it skips some, particulary in the private area (U+E000 for example). The expected behavior was to display all the Unicode characters from a font, the font being used has special characters in the private area.

STEPS TO REPRODUCE
1. Use a font that has private characters in the U+E000 range for example.
2. Try to search for the character in the range.
3. You can search the character manually and add it to the bookmark, the character will appear and will be displayed, but after you bookmark it, the kcharselect will not redirect you to the character, in fact, it will do nothing.

OBSERVED RESULT
For step 2, You will see that the program totally skips the range, even if characters are available to be rendered in that range.

EXPECTED RESULT
The expected result was for the program to simply show all the ranges in the Unicode font, just like the Windows Char Map does (I had no problems with Windows Char map).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Clear Linux OS; Build ID: 35280
Comment 1 referenciaguido 2021-11-13 01:16:08 UTC
Created attachment 143505 [details]
Seeing a bit more, I noticed that it detects U+E000 as basic latin block, which shouldn't be the case.
Comment 2 Christoph Feck 2021-11-13 03:05:26 UTC

*** This bug has been marked as a duplicate of bug 142625 ***