Created attachment 108414 [details]
This may be limited to the windows version, but...
The font rendering looks terrible. In no way can I see any anti-aliasing on the fonts.
It might be a 3K thing, but the text looks bad.
Reproducible with LO 220.127.116.11 (Win 8.1):
With the font Liberation Serif and then zooming in it looks also for me quite pixelated.
Sorry, the system doesn't understand that png's are graphics, is downloadable, viewable and zoomable.
Because the issue involves anti-aliasing issues, I wanted a pixel-accurate format.
I fixed the attachment’s MIME type, that’s why it wasn’t displaying properly on browser.
Your attachment actually shows ClearType antialiasing, which is not the same as “no antialiasing”. I agree it,’s ugly and looks choppy, but that’s how Windows’ GDI+ library renders it.
We could eventually switch to the DirectWrite, but that would mean dropping XP support.
So what you are saying is, this might not be fixed for years?!
Thank you for fixing the mime-type,
Respectfully, I am asking your a second opinion further up on the decision chain.
ClearType is not developed by us. Its quirkinesses can only be fixed by Microsoft.
You can workaround it: either switch to Standard font smoothing or install a program called gdipp.
Please correctly, if I am wrong, but there is no "standard font smoothing" in windows.
This is the only windows application, I have this problem with.
I am asking for a look at by someone higher on the chain.
How could LibreOffice be a modern office application without font smoothing?
gdipp has not had a release in over 4 years, making it's security and current compatibility questionable. It is fine to offer a solution, but that solution should work, should it not.
Commentary: this is the kind of situation where open source for all its good intentions sometimes fails. Please don't let that happen here.
> Please correctly, if I am wrong, but there is no "standard font smoothing"
> in windows.
Under XP, there are three options: “None”, “Standard” and “ClearType”.
> gdipp has not had a release in over 4 years, making it's security and
> current compatibility questionable. It is fine to offer a solution, but that
> solution should work, should it not.
Well, it works, doesn’t it?
> Commentary: this is the kind of situation where open source for all its good
> intentions sometimes fails. Please don't let that happen here.
I’ve already told you what the solution would be under Windows: using DirectWrite. That is what Google Chrome developers did after receiving this kind of bug reports repeteadly. Unfortunately, DirectWrite is not available under Windows XP (it’s present in Vista SP2 with Platform Update and above).
Personally I look forward to this, but unless TDF decides to drop XP support, it won’t happen for a while. Please contact the ESC in the development list (libreoffice at lists.freedesktop.org) and let them know your concerns.
Another thing that I had forgotten to mention is that font hinting plays a big role in Windows’ rendering as well. Unfortunately, the Liberation fonts have hinting issues, but that’s NOTOURBUG as well (report that to Red Hat’s Bugzilla).
Believe me, this is one of the reasons why I prefer to use Linux over Windows. ;-)
I am using Windows 7, not XP. There is no such option. Respectfully, your solution is a non-solution. Does not work for me.
The fonts in question are not Liberation.
Windows XP is no longer supported. It's time to move on.
We now use DirectWrite (via Skia)!