Bug 104538 - Bitmap fonts are not supposed to show up in font selector anymore
Summary: Bitmap fonts are not supposed to show up in font selector anymore
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.3.0.0.beta1
Hardware: All Windows (All)
: low trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Fonts
  Show dependency treegraph
 
Reported: 2016-12-09 18:45 UTC by Aron Budea
Modified: 2022-08-22 23:24 UTC (History)
1 user (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 Aron Budea 2016-12-09 18:45:31 UTC
As Khaled mentioned, these fonts should be hidden in 5.3 (I believe with the resolution of bug 103514), yet the following bitmap fonts are still in the font list:
-Modern,
-Script.
Comment 1 V Stuart Foote 2016-12-09 19:16:14 UTC
A clean user profile for your 5.3 install? And, is there actually another TTF or OTF font by those names on system?
Comment 2 V Stuart Foote 2016-12-09 19:23:46 UTC
Oops, wait I'm seeing them also on Windows 10 Pro with

Version: 5.4.0.0.alpha0+
Build ID: a9f56091b6422ec8c42f09b8472200ae4ab12548
CPU Threads: 8; OS Version: Windows 6.19; UI Render: GL; 
TinderBox: Win-x86@42, Branch:master, Time: 2016-12-05_23:12:26
Locale: en-US (en_US); Calc: CL

Getting some weird fallback in the Special Character dialog, and the font names is showing (not italicized) on the Toolbar formatting droplist.

Hmmm...
Comment 3 QA Administrators 2017-12-10 16:43:51 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2019-12-11 03:38:13 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2021-12-11 04:21:20 UTC
Dear Aron Budea,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug