Font rendering problems with Qt WebKit

[arash9900]

Hi,
I have problem with the font of zeal.as you can see in below picture, the texts(specially in Overview and Example Section) are not showing well.

[bdeshi]

File > Options > Appearance tab > Minimum font size: set a value that works. In my case 13 was good enough.

[arash9900]

As you can see the problem exist with the font size:14

[bdeshi]

make a few more increments?

[arash9900]

that's better now.Thanks

[trollixx]

Hm, it really a font rendering issue. I bet something wrong in Qt WebKit which is not officially supported any longer. Zeal needs a new web view engine, but there's no drop-in replacement we could use.

I'll leave this open to run some tests once I have access to Windows machine, but most likely there's nothing I could do for now :(

[bdeshi]

maybe you could meanwhile add zoom in/out shortcuts CTRL+,CTRL-

[artursapek]

Agreed with @smsrkr - a zoom function would be very welcome. Ideally it would default to OS scale settings, because I think the webkit view is rendering at a 100% scale despite OS settings (Ubuntu 16.04 here). For example I am using Ubuntu at 150% UI scale because I have a high DPI screen, but in zeal the docs are rendered disproportionately smaller than the rest of the UI.

Min font size kind of addresses it, but then you lose the benefit of larger headings etc.

Awesome app by the way. Thanks for developing it.

[damianpeterson]

Just adding my own screenshot at 2x scaling on a 3200x1800px laptop in Ubuntu 17.04

[trollixx]

CI builds for Windows are now based on the new Qt WebKit (qtwebkit-ng), which should resolve the most of the issues with rendering. Please give it a try.

Linux users need to install qtwebkit-ng themselves, although some distros do provide binaries.

[trollixx]

The majority of font rendering issues can be fixed by upgrading the the new Qt WebKit. If an issue persists even with qtwebkit-ng (like #658), please create a new ticket.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.