When one needs to choose a font, one is often certain only about an aspect of the font, which does not appear at the beginning of the font family name. Alternatively, one may want a specific font, but may not remember its prefix. Example: I want to use a "Gothic" font. On my system, I have "MS Gothic" and "Century Gothic". But by typing "Gothic" - I get none of them. I should actually get both. Some ways of achieving this: * Always search by substring, not by prefix * Separate the search result with a separator, putting prefix-search-results first, then remaining by-substring search results
IMO, searching for *<text>* is a nice to have (acceptable simple to implement and not adding too much confusion) but not crucial for the font picker dropdown. Font management belongs to the system - or dedicated dialogs ideally realized per extension.
(In reply to Heiko Tietze from comment #1) 1. LO doesn't only have features which are crucial. The question is what's useful enough to have in the app by default, balanced against considerations such as implementation effort, clutter, etc. 2. You're taking the underlying assumption that searching by prefix is more crucial, or more important, than searching by substring. I would say that's not true. If only one behavior is supported, surely it should be substring rather than prefix search. 3. This is not about the management of fonts, it's about choosing from the available fonts.
Would be a useful improvement. Esp. when available over all font-select controls.
We discussed the topic in the design meeting. There is agreement to change the behavior in the dialog and filter the list of font when text is being entered (would start with three letters minimum). Doing the same for dropdown controls is desirable but means to change the behavior completely since we currently just autocomplete. Similar request in bug 139099 was rejected as the effort bears no relation to the benefit.
(In reply to Heiko Tietze from comment #4) > We discussed the topic in the design meeting. > > There is agreement to change the behavior in the dialog and filter the list > of font when text is being entered (would start with three letters minimum). > > Doing the same for dropdown controls is desirable but means to change the > behavior completely since we currently just autocomplete. Similar request in > bug 139099 was rejected as the effort bears no relation to the benefit. Good to see the investigation done here :)!