https://bugs.documentfoundation.org/show_bug.cgi?id=77878
V Stuart Foote <[email protected]> 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 <[email protected]> --- 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: <quote> 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. </quote> -- You are receiving this mail because: You are on the CC list for the bug.
