https://bugs.kde.org/show_bug.cgi?id=518569

            Bug ID: 518569
           Summary: Default UI font is monospace not proportional (QT6
                    bug)
    Classification: Applications
           Product: digikam
      Version First 9.0.0
       Reported In:
          Platform: Microsoft Windows
                OS: Microsoft Windows
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Usability-Ergonomy
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

SUMMARY

By default, digiKam uses "Segoe UI Mono Regular" on Windows 11 rather than 
"Segoe UI Regular" or "Segoe UI Variable".

Monospaced font is unattractive, mismatched to the rest of the desktop, takes
up more screen space, tends to overflow controls, and is more difficult to
read.

This bug has appeared on multiple QT6 applications (not just digiKam) that have
been recently updated, so it appears to be an issue with QT6 that needs a
workaround.

A user workaround is available for digiKam because the Settings dialog allows
UI font to be customised (and it can be set to "Segoe UI Variable Display").

There is no option to select "Segoe UI Regular" as it is missing from the list.
It appears that QT6 is not enumerating system fonts correctly, which suggests
the default system font is effectively unavailable and monospace is being used
as a fallback.

STEPS TO REPRODUCE

1. Install digiKam on Windows 11
2. Observe digiKam UI font
3. Review digiKam font settings

OBSERVED RESULT

1. DigiKam UI uses "Segoe UI Mono Regular" instead of "Segoe UI Regular" by
default.
2. "Segoe UI Regular" is not an available option in the font selection dialogs.

EXPECTED RESULT

1. DigiKam should use the Windows 11 system font "Segoe UI Regular".
2. "Segoe UI Regular" should be an available option in the font selection
dialogs.

SOFTWARE/OS VERSIONS

Windows:  25H2 26200.8117
Qt Version:  6

ADDITIONAL INFORMATION

Other applications based on QT6 now have the same problem after recent updates
to their latest versions. There appears to be no workaround for the problem
unless the affected application allows a UI font to be specified in Settings.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to