Bug 151119 - Font (family) selection UI elements should allow searching by substring
Summary: Font (family) selection UI elements should allow searching by substring
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Character-Dialog Fonts-Name-Combobox
  Show dependency treegraph
 
Reported: 2022-09-22 09:02 UTC by Eyal Rozenberg
Modified: 2022-10-08 20:05 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eyal Rozenberg 2022-09-22 09:02:21 UTC
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
Comment 1 Heiko Tietze 2022-09-22 13:21:21 UTC
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.
Comment 2 Eyal Rozenberg 2022-09-22 15:09:47 UTC
(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.
Comment 3 Cor Nouws 2022-10-04 10:38:27 UTC
Would be a useful improvement.
Esp. when available over all font-select controls.
Comment 4 Heiko Tietze 2022-10-07 07:38:46 UTC
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.
Comment 5 Cor Nouws 2022-10-08 20:05:58 UTC
(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 :)!