Bug 158296 - Show the fallback font in the Writer UI
Summary: Show the fallback font in the Writer UI
Status: RESOLVED DUPLICATE of bug 151121
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-11-21 10:27 UTC by Chris Sherlock
Modified: 2023-11-21 12:24 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 Chris Sherlock 2023-11-21 10:27:17 UTC
Description:
When a glyph cannot be found in the font being used, we fallback to another font that has the relevant glyph. Unfortunately, it is not obvious what font we are using, or even if we are actually using a fallback font. 

I would like to find a way to show this in the Writer UX. 

Steps to Reproduce:
1. Type in some text with CJK and latin characters.
2. Highlight all the text and make it a font that doesn't have latin characters (like for instance, Source Han Sans)
3. Now look at the latin-based characters. You cannot tell what font is being selected. On MacOS this falls back to Helvetica, on Linux it's another font and on Windows its another.

Actual Results:
Cannot see what font is being actually displayed as the fallback font. 

Expected Results:
I would like to know what the font being actually displayed is. 


Reproducible: Always


User Profile Reset: No

Additional Info:
I found this whilst I was writing a unit test for text layout - see https://gerrit.libreoffice.org/c/core/+/159221
Comment 1 Stéphane Guillou (stragu) 2023-11-21 12:24:48 UTC
As noted in the QA channel, this is already tracked in some other tickets:
* bug 61134 : show the fallback font info in font UI
* bug 78186 : summarise which fonts are used in document, and which are missing on system
* bug 151121 : show the glyph fallback info in UI

Let's mark as duplicate of bug 151121 - unless you disagree?

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