In bug 50189: "Font type picker in Format Bar should show that selected font type is not available on PC" it was sugested I file a separate enhancement request, which is this report. Bug 50189 has been resolved by two patches: http://cgit.freedesktop.org/libreoffice/core/commit/?id=0376a4c13ccffa64c938c6361a337264ad8f2b67 "if a font is not available, show its name in italic in the font combo" http://cgit.freedesktop.org/libreoffice/core/commit/?id=17d86df23e7be3ab0a161f69ff0f703728e0e135 "also change the font combo tooltip to say font is not available" The further suggested enhancement is that it would be nice if when a substitute font is being used, the "font combo tooltip" message also said which substitute font was being used.
I believe we were going to implement this font substitution tooltip for 4.0 right ? did we do that already ? :-)
Michael Meeks in comment 1 said: I believe we were going to implement this font substitution tooltip for 4.0 right ? did we do that already ? :-) My understanding is that there is a patch that will implement a tooltip to say that a font substitution has taken place: http://cgit.freedesktop.org/libreoffice/core/commit/?id=17d86df23e7be3ab0a161f69ff0f703728e0e135 This ticket is an enhancement suggestion that the tooltip should say which font is actually being used as the substitute. Otherwise we are telling the user his font is not available, but not which font is actually being used. In fact the tooltip should ideally say: * which font is not available * which one is being used as a substitute * if desired how to change which font is being used as the substitute This may be too much information...
I agree with this enhancement. Apparently, showing the substituted font name in the tool tip was never implemented, since it is still not available in LO 5.0.2 RC1. Also, it would be nice to add the ability to apply all substituted fonts to the current document, but that would probably be another report.
(In reply to tmacalp from comment #3) > I agree with this enhancement. Apparently, showing the substituted font > name in the tool tip was never implemented, since it is still not available > in LO 5.0.2 RC1. I'm sorry, I completely misread the comment above. The feature was implemented so the tooltip says that a font substitution has taken place. I agree with comment 2 that the tooltip should at least say which font is being used for the substitution.
Alternatively the actual font could be added in brackets like "Gentium (Sans)". The tooltip would a worthy enhancement but not really obvious to users (saying that in respect to #96872).
*** Bug 98650 has been marked as a duplicate of this bug. ***
Clarifying the summary Also, the enhancement could be implemented in the fontname tooltip, or more ambitiously in the combobox font listings. Either way, currently there is no UI provided means of determining the specific font substitution.
(In reply to Heiko Tietze from comment #5) > Alternatively the actual font could be added in brackets like "Gentium > (Sans)". The tooltip would a worthy enhancement but not really obvious to > users (saying that in respect to #96872). This wont always work well as the size of the combobox is small and it sometimes cant even hold the characters of a single font (e.g. Linux Libertine Display G), so users wont see the bracket substitution, i guess unless the bracket substitution will also appear in the drop down menu. So i'd recommend placing it both in the text field of the combobox and in the tooltip.
*** Bug 113176 has been marked as a duplicate of this bug. ***
*** Bug 122439 has been marked as a duplicate of this bug. ***
Changing priority back to 'medium' since the number of duplicates is lower than 5
I was opening a new bug with title "[enhancement] font substitution tooltip" but I read this META bug, so I comment here: I want to report this issue: font substitution tooltip doesn't show with which font has been substituted I attach a screenshot
Created attachment 159336 [details] tooltip doesn't show "target" font
*** Bug 138923 has been marked as a duplicate of this bug. ***
*** Bug 151010 has been marked as a duplicate of this bug. ***
*** Bug 151121 has been marked as a duplicate of this bug. ***