Bug 158259 - Manage Fonts
Summary: Manage Fonts
Status: RESOLVED DUPLICATE of bug 67200
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.6.2.1 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-18 04:55 UTC by افشین
Modified: 2023-11-18 11:29 UTC (History)
0 users

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 افشین 2023-11-18 04:55:16 UTC
Description:
If the user has installed many fonts, the drop-down menu of fonts will be too crowded and it will be difficult to select fonts.

Steps to Reproduce:
Hello. 

As a book editor, I have to install many fonts on my system in order to read various documents properly.
This causes there to be a lot of fonts in the drop-down fonts menu, and LibreOffice only separates the last 5 used fonts.

As you know, in the Adobe InDesign program, the user can manage (add/remove) his favorite fonts in a list.
I think the addition of this feature to LibreOffice is very useful and prevents the font drop-down menu from getting too crowded.

Actual Results:
Now there is 5 recent used fonts in drop-down fonts list. 

Expected Results:
I think this is better that the user manage installed fonts. 


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 60(Build:1)
CPU threads: 2; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: fa-IR (en_US.UTF-8); UI: en-US
Ubuntu package version: 4:7.6.2~rc1-0ubuntu0.22.04.1~lo1
Calc: threaded
Comment 1 Ming Hua 2023-11-18 06:47:18 UTC
I believe this is a duplicate of bug 67200, I suggest you add your opinion and suggestion there.

The design team's blog post at https://design.blog.documentfoundation.org/2018/02/18/improvements-font-listing/ discussed many possible improvements to font list.
Comment 2 افشین 2023-11-18 11:29:40 UTC

*** This bug has been marked as a duplicate of bug 67200 ***