Bug 98817 - Better font selection
Summary: Better font selection
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.0.5.2 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Font-List
  Show dependency treegraph
 
Reported: 2016-03-22 08:13 UTC by Ulrich Windl
Modified: 2017-11-04 11:50 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Windl 2016-03-22 08:13:32 UTC
Copying what Microsoft does is just the Chinese way of innovation, but I think we can do better:
For the font selection dialog here is what I missed all the time (wasted lots of time scrolling a huge font list looking for some specific look):

1) When listing available fonts, the fonts already used in the document should be on the top of the list, because it's very likely they will be re-used, and it will avoid random errors by selecting a similar, but not the same font.

2) Fonts selected most recently should be on the top of the list (for the same reasons stated in 1)). Maybe 1) OR 2) is sufficient, but 1) neither includes 2), as 2) does not include 1).

3) There should be a way to sort fonts by similarity instead of names (that aren't really helpful to most users). If you don't know what I'm talking about, maybe start with https://en.wikipedia.org/wiki/PANOSE.

4) Once the framework for 3) is set up, the user should be allowed to filter the list by attributes.

5) For systems where there exist "font aliases" (like "Sans" in Linux), the real name of each font should be displayed and alias names avoided (hidden). More frequently than not, those alias definitions change after operating system upgrades (talking Linux now), and what the user does not want is that a different font is used in the document. (I'm not 100% sure this happens in LibreOffice, but it happened in Inkscape).

6) I'm not sure about this one: If you have 3) implemented, the list of fonts could start with the font currently selected, the sort according to similarity with the font most different at the end of the list. Rationale: Sometimes the user want a similar font, while sometime he/she wants a completely different font.

7) Sorting by coding systems (Unicode blocks) may seem useful also: Europeans may typically use one coding system, people from Asia another, in between Greeks and Russians (apologies to all the others I missed).  Unless you write dictionaries or multi-language documents, you would hardly change the coding system. OK Symbol and ornament fonts play a special role here.
Comment 1 Buovjaga 2016-03-29 14:50:16 UTC
Ulrich: I advise you to join the design team IRC channel to discuss these things: #libreoffice-design @ Freenode (or http://webchat.freenode.net/?channels=libreoffice-design )

I remember there being a report for 2) already.
Comment 2 Robinson Tryon (qubit) 2016-08-25 05:49:48 UTC Comment hidden (obsolete)
Comment 3 Heiko Tietze 2016-09-21 11:43:53 UTC
Set NEW and adding it to the tasks of the design team.
Comment 4 Heiko Tietze 2016-09-30 13:11:55 UTC
We talked about this ticket in the UX meeting. Your ideas to improve the UI are greatly appreciated, while bringing structure into fonts also a huge topic.

However, I close this ticket as INVALID - there are too many aspects in one report. Please create new tickets with small tasks for the developers. Ideally the proposal includes observation from and a _consistent solution_ to all parts of the program. Keep also in mind that we aim for _simplicity_ (our primary persona is Benjamin [1]) and want to be powerful on demand (for the Eves).

[1] https://wiki.documentfoundation.org/Design/HIG_foundations#Persona