https://bugs.documentfoundation.org/show_bug.cgi?id=142940
--- Comment #18 from [email protected] --- I was reminded of this bug because another bug was just marked as a dupe of it. Wanted to comment that the dupe provides a good example of the point I was making: the user was reporting that kerning was bad on macOS, and that pair kerning seemed to make it much worse. It's not unlikely that this user went on to disable pair kerning (at least for certain fonts), ruining the quality of their published / printed documents. No doubt other users are doing the same, although they may never see this bug report. I think that's the situation we need to avoid. I think V Stuart Foote made a good point in https://bugs.documentfoundation.org/show_bug.cgi?id=142940#c15 > Addressing bug 10332 would allow effective sub-pixel rendering and more > appealing font kerning on displays. Fixing that bug would certainly fix this bug as well. However, the reason this bug exists is that there's seemingly been no movement whatsoever on that bug in *years* now. I think it is fair to say that there is virtually no interest in fixing it. This bug arises from that fact. Disabling pair kerning on the screen canvas would improve the quality of rendering in the interim, until that bug is fixed. Doing so is likely to be *much* easier than thoroughly replacing the glyph positioning code throughout LO to use floating point. Would a patch that disabled pair kerning *only* on the screen canvas without providing a corresponding toggle to enable it be acceptable, or is a setting a necessity? Trying to work out what I could conceivably contribute here, as someone unfamiliar with the LO codebase. -- You are receiving this mail because: You are the assignee for the bug.
