Summary: | Font is rendered differently in kwrite and konsole | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Antonio Orefice <kokoko3k> |
Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | CC: | cfeck, kokoko3k |
Priority: | NOR | ||
Version: | 16.08 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | screenshot |
Description
Antonio Orefice
2016-10-07 11:20:54 UTC
Created attachment 101468 [details]
screenshot
Kwrite on top, konsole on bottom, very same font and size, rendered differently.
That's intentional. Konsole uses a character cell grid, forcing every character on a pixel boundary (QFont::ForceIntegerMetrics). KWrite is able to use non-monospaced fonts, and can therefore place characters on subpixel resolution. Thanks for the explaination, but wouldn't be more uniform/consistent to use the same setting (QFont::ForceIntegerMetrics) when kwrite is using monospaced fonts? As a side note, the same happens on the fonts kcm module when selecting the fixed width font (here, there is way to select a proportional font) Sorry, typo: As a side note, the same happens on the fonts kcm module when selecting the fixed width font (here, there is *NO* way to select a proportional font) No, ForceIntegerMetrics is a hack for applications that need to render glyphs at exact integer positions, and is actually not related to monospaced fonts. If you want consistency, ask Konsole developers to support fractional glyph positioning. Ok, thanks for the detailed explaination (again!) |