https://bugs.documentfoundation.org/show_bug.cgi?id=77878
--- Comment #18 from [email protected] --- Thank you all for the clarification and follow-up, especially regarding the Windows registry key for inactive fonts and the possibility of implementing an IsFontHidden check at the VCL level. Based on the discussion so far, it seems that the original 2020 limitation (“no API to query hidden fonts”) is no longer the core blocker. On Windows, the hidden state is accessible via a documented registry location; on Linux, Fontconfig already supports user-level filtering; and on macOS, system APIs provide similar mechanisms. That suggests this could be handled per-platform within VCL without affecting document fidelity. >From a usability perspective, I’d like to gently reframe this not as a cosmetic enhancement, but as a scalability consideration. Font ecosystems have grown significantly in recent years — particularly with large families such as full Noto installations, CJK variants, symbol collections, etc — and they will only continue to grow. On systems with extensive font sets, the font dropdown can become very long, which makes selection slower and increases visual scanning effort. Respecting OS-level hidden fonts in LibreOffice’s UI would: • Align LibreOffice behavior with platform expectations • Reduce font list size without removing actual font support • Preserve document rendering (hidden fonts would still work if used in documents) • Apply consistently across modules I’m not proposing removal of fonts or deviation from system configuration — only that LibreOffice honor the user’s existing font visibility preferences when populating UI lists. If implementation effort is the primary concern, perhaps a minimal first step would be Windows support via the documented registry key, implemented through VCL as suggested. That could provide immediate benefit without requiring a full cross-platform filtering framework from the outset. I’m happy to help test or document behavior if this moves forward. -- You are receiving this mail because: You are the assignee for the bug.
