Bug 472376

Summary: KCharSelect Missing entire "Mathematical Alphanumeric Symbols" block
Product: [Applications] kcharselect Reporter: Michael <kde>
Component: generalAssignee: Christoph Feck <cfeck>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: 23.04.3   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Michael 2023-07-19 01:42:30 UTC
SUMMARY

KCharSelect is missing an entire grouping/block of symbols called "Mathematical Alphanumeric Symbols". The symbols can be looked up one at a time in its database if you happen to know exactly what you're looking for, but we cannot see the entire block and browse them, like we can for "Supplemental Arrows-A" group, for example.

This missing block is defined here: https://www.unicode.org/charts/PDF/U1D400.pdf


STEPS TO REPRODUCE

1. In KCharSelect, paste the 𝒀 symbol into the search bar at the top and ensure that Noto Sans is selected as the font.
2. The character is found and the code point is shown as U+1D480, as it should be. 
3. From the unicode.org site, doing a search on this character tells us that it is the "Mathematical Alphanumeric Symbols" range. 
4. Attempt to find the "Mathematical Alphanumeric Symbols" block in KCharSelect. 
4a. Select "Mathematical Symbols" from the first drop-down list and examine the secondary drop-down list.
4b. Go through all the sub-blocks one at a time, to verify that code point U+1D480 is not there. Even look in the first drop-down's "Symbol" category, it's not there either.

EXPECTED RESULT

Should be able to find the entire group/block called "Mathematical Alphanumeric Symbols" as shown in https://www.unicode.org/charts/PDF/U1D400.pdf

SOFTWARE/OS VERSIONS

Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Comment 1 Christoph Feck 2023-07-19 03:20:06 UTC

*** This bug has been marked as a duplicate of bug 142625 ***
Comment 2 Michael 2023-07-20 05:11:24 UTC
Thank you, I tried searching but I didn't realize the technical reason behind it and couldn't get a match. Looks like it's an old bug, 16 years old.