[Bug 77878] Font list organization: request for user-managed hiding, filtering, or language-based views
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.
[Bug 77878] Font list organization: request for user-managed hiding, filtering, or language-based views
https://bugs.documentfoundation.org/show_bug.cgi?id=77878 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||9180 --- Comment #17 from Eyal Rozenberg --- In bug 169180, I asked for user ability to filter fonts, in the context of LO alone. While my request there regards some finer-grain filtering (e.g. filtering for a specific language/language group), it does seem rather related. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 77878] Font list organization: request for user-managed hiding, filtering, or language-based views
https://bugs.documentfoundation.org/show_bug.cgi?id=77878 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #16 from Mike Kaganski --- On Windows, there is well-defined key/value for the hidden fonts: HKCU\Software\Microsoft\Windows NT\CurrentVersion\Font Management\Inactive Fonts (and likely also respective HKLM?). It is OK to use it when populating font lists in UI. Having a VCL-plugin-implemented "IsFontHidden" function is OK, and allows to implement it as respective integration allows. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 77878] Font list organization: request for user-managed hiding, filtering, or language-based views
https://bugs.documentfoundation.org/show_bug.cgi?id=77878 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org --- Comment #15 from Heiko Tietze --- Don't think this needs much consideration from UX: if fonts are suppressed to be shown by the OS/DE we should hide them in the list of available fonts (but use if the documents contains it). And surely it is very much desirable given the large number of Noto variants worldwide that are installed with the full Noto set, for example. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 77878] Font list organization: request for user-managed hiding, filtering, or language-based views
https://bugs.documentfoundation.org/show_bug.cgi?id=77878 V Stuart Foote changed: What|Removed |Added Status|REOPENED|UNCONFIRMED Ever confirmed|1 |0 CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval Component|Writer |LibreOffice OS|Windows (All) |All --- Comment #14 from V Stuart Foote --- Given that comment 13 wants to expand beyond the Windows platform, so much more than revisiting advances in the ChooseFont API. Also, no reason to not implement for all modules--reseting back to the LibreOffice component, not just Writer. And back through UX-advise, as this really does not seem an overly urgent requirement from a usability perspective. Nice to do if feasible, but DE integration not core to module function. IMHO remains a => WF or can't fix. Here is a Google query "are there desktop environment api for programs to hide or show fonts based on user configuration" returns the following response for doing something cross platform, suggests it would need a lot of native code effort and then might not support all os/DE: AI Overview Yes, desktop environments provide APIs and mechanisms for managing font visibility, and well-behaved programs that use standard system font selection APIs will automatically respect the user's configuration. However, the specific APIs and their effectiveness depend on the operating system and how strictly applications adhere to system guidelines: Windows Built-in Font Dialogs: Applications that use the standard Windows font common dialog box (ChooseFont API) automatically filter out fonts that the user has hidden or which do not match the current language settings. DirectWrite/GDI: Lower-level APIs like DirectWrite and GDI (EnumFontFamiliesEx) can enumerate all installed fonts regardless of their "hidden" status, as there are no direct API calls in these interfaces to check the user's hidden font list. Developer Responsibility: For a consistent user experience, developers are encouraged to use the system font picker or respect user settings via specific accessibility APIs. Applications like Microsoft Office often generate their own font menus and historically have not always respected the Control Panel font settings. Linux Fontconfig: This is the primary library used by applications on Linux to discover and configure fonts. It uses XML-based configuration files (e.g., ~/.config/fontconfig/fonts.conf for per-user settings) that allow users or desktop environments to reject specific fonts or font families from the list provided to applications. Automatic Respect: Applications that rely on Fontconfig for font lists will automatically respect these configurations without needing extra code to handle hiding or showing fonts. macOS and iOS Core Text: Apple provides the Core Text API for precise font layout and typography. The system generally manages font visibility and accessibility, and applications are expected to use system-provided font choosers and APIs to ensure consistency and respect user preferences, such as dynamic type and installed fonts. In summary, the functionality exists, but its implementation and consistency rely on applications utilizing the correct system-level APIs for font selection rather than custom enumeration methods. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 77878] Font list organization: request for user-managed hiding, filtering, or language-based views
https://bugs.documentfoundation.org/show_bug.cgi?id=77878 [email protected] changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Bug 77878] Font list organization: request for user-managed hiding, filtering, or language-based views
https://bugs.documentfoundation.org/show_bug.cgi?id=77878 [email protected] changed: What|Removed |Added Component|LibreOffice |Writer -- You are receiving this mail because: You are the assignee for the bug.
[Bug 77878] Font list organization: request for user-managed hiding, filtering, or language-based views
https://bugs.documentfoundation.org/show_bug.cgi?id=77878 [email protected] changed: What|Removed |Added Severity|enhancement |normal Version|4.3.0.0.alpha0+ Master |25.8.4.2 release -- You are receiving this mail because: You are the assignee for the bug.
[Bug 77878] Font list organization: request for user-managed hiding, filtering, or language-based views
https://bugs.documentfoundation.org/show_bug.cgi?id=77878 [email protected] changed: What|Removed |Added Summary|Fonts hidden in Windows |Font list organization: |Control Panel continue to |request for user-managed |be displayed in font list |hiding, filtering, or ||language-based views -- You are receiving this mail because: You are the assignee for the bug.
