Created attachment 102297 [details] Font rendering glitch in Qt Assistant I don't really know where to report this so please bear with me. The Qt Assistant v5.6.2 has problems rendering documentation generated with KApiDocs, in particular viewing entries from the "File List" See the attached screenshot. I'm only seeing this with documentation generated with KApiDox (even git/master/head), it seems to be independent of the font used, and it happens on Linux/X11 and Mac/Cocoa (i.e. with the Freetype and CoreText font engines). Is this a known issue in Qt Assistant or an issue in one of KApiDox's css sheets?
Hi, Could you try again against the current master? I cannot reproduce your issue
Current master of what? Are you by any chance running the Assistant built with QtWebKit support? I have learnt since submitting this ticket that doing that prevents the issue. That's no more than a workaround though because sooner or later WebKit support will be removed from the sources.
Is the output of kapidox in HTML format also for usage in Assistant?
Yes it is used for QtAssistant.
Indirectly, yes. It's that output which is compiled into a single .qch file. In the meantime, WebKit support is still present in the Assistant (even in the dev branch), and with talk of re-integrating the rebooted QtWebKit it is no longer so likely to disappear.
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!