Ideally we should rasterize glyphs on the GPU not the CPU. This would have several benefits including speedups, clear-type-ifying, and particularly sub-pixel glyph positioning giving better layout of tiny text.
Ideally we could get consistent sub-pixel glyph positions from harfbuzz as/when we move to that for shaping; and get something rather beautiful here.
Has this been implemented in the meantime? (E.g., bug 107090 talks of GPU rendering of text. Although I might be mixing things up.)
As for tiny text rendering issues, just for info: another, tangential, improvement is described in the bug 103322, with its other possible manifestations such as bug 88991 and its companions. Bug 71732 comment 14 summarizes the current state after the move to Harfbuzz.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
As Skia with Vulkan will replace OpenGL UI rendering on all platforms, it does not make sense to keep OpenGL UI reports open.
Details about Skia: https://www.collaboraoffice.com/success-story/implementing-vulkan-capable-libreoffice-user-interface-using-the-skia-library/
Perhaps no longer OpenGL related, but this remains a valid issue--including via Skia libs.
(In reply to V Stuart Foote from comment #4)
> Perhaps no longer OpenGL related, but this remains a valid issue--including
> via Skia libs.
I searched through the commit/patch history and it is clear that text rendering directly with Skia was implemented.
I asked Tomaž on IRC and he commented: "skia should solve this - IMHO at least this is not something we want to mess with anyway :)"
Stuart: what am I missing?
Closing the OpenGL issues for QA housekeeping is fine. But still work to be done here, @Michael?
Well, I guess the skia move is in large part an attempt to use a modern graphics library underneath our code, and leave these decisions to them so we can avoid having to try to boil the ocean =)
As such - assuming we can switch to Skia everywhere and deprecated OpenGL, I'd close this WONTFIX I think. I don't see any resource that we could apply here that wouldn't make more sense to do lower in the rendering stack =)
If that makes sense ?