Bug 364488 - KCharSelect has (virtually) no Unicode support
Summary: KCharSelect has (virtually) no Unicode support
Status: RESOLVED DUPLICATE of bug 142625
Alias: None
Product: kcharselect
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Daniel Laidig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-06-19 09:49 UTC by Jeff Bai
Modified: 2016-06-20 03:15 UTC (History)
1 user (show)

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

Attachments
KCharSelect CJK support (72.49 KB, image/jpeg)
2016-06-19 09:50 UTC, Jeff Bai 		Details
KCharSel trying to find U+2A730 (54.04 KB, image/png)
2016-06-19 10:00 UTC, Star Brilliant 		Details
GuCharmap trying to find U+2A730 (96.05 KB, image/png)
2016-06-19 10:01 UTC, Star Brilliant 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Bai 2016-06-19 09:49:13 UTC 
KCharSelect does not seem to have support for Unicode > 3.0, which renders the issue like the application really just doesn't have support for Unicode anyways (with the newest Unicode revision reaching version 9.0).

This was discovered by one of my friends finding that there is no Unicode support for CJK Extension B/C/D/E.

I have attached a screenshot of his below.

Reproducible: Always
Comment 1 Jeff Bai 2016-06-19 09:50:37 UTC 
Created attachment 99595 [details]
KCharSelect CJK support
Comment 2 Star Brilliant 2016-06-19 10:00:01 UTC 
Created attachment 99596 [details]
KCharSel trying to find U+2A730

Trying to find U+2A730 in KCharSel, but the search returned nothing.
Comment 3 Star Brilliant 2016-06-19 10:01:03 UTC 
Created attachment 99597 [details]
GuCharmap trying to find U+2A730

Trying to find U+2A730 in GuCharmap, it successfully returned the result.
Comment 4 Star Brilliant 2016-06-19 15:11:58 UTC 
Seems duplicate in #142625 and #336360
Comment 5 Christoph Feck 2016-06-20 03:15:47 UTC 
Yes.

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