Summary: | KDE applications should use the standard Windows fonts | ||
---|---|---|---|
Product: | kde-windows | Reporter: | Veeti Paananen <veeti.paananen> |
Component: | general | Assignee: | KDE-Windows <kde-windows> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | kamikazow |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: |
Description
Veeti Paananen
2011-06-30 21:11:19 UTC
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! I'm curious about WHAT specifically is unmaintained to justify closing this. Although there is no longer a main KDE Windows installer, I would ask whether the font issue is present with any KDE programs compiled for Windows using Craft. Given the age of the ticket, and the lack of any follow-up, I'm guessing the original poster has no further interest, and my interest is purely out of curiosity, as I no longer have a Windows system to test (thus I'm leaving this closed.) (In reply to Jack from comment #3) > I'm curious about WHAT specifically is unmaintained to justify closing this. Anything Qt4-related. I agree that anything Qt4 (and anything depending on it) is unsupported, but does this problem still exist with Frameworks (Qt5) versions? Without the general KDE installer for Windows, I assume this is currently up to each application individually, so even more reason to close this as a generic issue. |