Summary: | KCharSelect isn't clear if glyph/character is included in font/shows characters that are NOT in a given font/shows wrong character glyphs | ||
---|---|---|---|
Product: | [Applications] kcharselect | Reporter: | Kevin Coonan <kevin.coonan> |
Component: | general | Assignee: | Christoph Feck <cfeck> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | ||
Priority: | NOR | ||
Version First Reported In: | 25.04.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
screen shots
screen shot showing characters not in font Characters not in font More examples of wrong characters being shown |
Description
Kevin Coonan
2025-04-27 23:43:19 UTC
Created attachment 180720 [details]
screen shot showing characters not in font
Created attachment 180721 [details]
Characters not in font
Created attachment 180722 [details]
More examples of wrong characters being shown
*** This bug has been marked as a duplicate of bug 97420 *** (In reply to Antonio Rojas from comment #4) > > *** This bug has been marked as a duplicate of bug 97420 *** I am not clear on the resolution for that prior bug. It was acknowledged as a problem, but not fixed. The fact that the initial use case analysis was incomplete isn't a resolution! Just because I have font substitution set up on my computer that fills in a given gap in some other font is not a guarantee that others will be able to read a document sent to them. It totally depends on what other fonts someone has installed and how they have their font substitution set up. Most people assume that if I send them a document in a font they don't have, and they install that font it will fix any rendering problems. This usually easy enough as I only (very rarely) use the standard Windows fonts and open source fonts--which depends on their corporate computer security settings whether nor not they are even allowed to install a font. As with others, I have had to turn to software from GNOME, which is not ideal. Moreover, the problem with showing NO glyphs for a given font has not been addressed at all. So while others have noted the problem, it has not been resolved. I don't see any mention of the other issue with not showing anything in a font. (In reply to Kevin Coonan from comment #5) > (In reply to Antonio Rojas from comment #4) > > > > *** This bug has been marked as a duplicate of bug 97420 *** > > I am not clear on the resolution for that prior bug. It was acknowledged as > a problem, but not fixed. Which is why the bug is still open and not resolved. |