When opening a .ppt file, if impress does not know the font, impress showed the font differently but write the true font name not the seen font name.
Steps to Reproduce:
1.open the sample.ppt file
2.fonts seems diffently
Font is not monitored correctly
True output of the sample file
User Profile Reset: No
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36
Created attachment 138595 [details]
Created attachment 138596 [details]
impress output screenshot
It is not a bug: if you do not have the expected font on your computer, LibreOffice try its best to find an available font as close as possible to the expected one. Sometimes LibreOffice can't find on your computer a good replacement font and the rendering is not good.
LibreOffice make you aware that it uses another font by displaying its name in italic and provide that information as tooltip as shown on your screenshot.
Closing as NotABug.
Best regards. JBF
I also think that it's not a bug however, UI needs improvement.When an inexperienced user opens a file and saw something like sample file not understand that the font was changed because not found in the library. There is the only visual clue that font was written in italic. The user is not informed when opening the file, "There is no such a font like....., this font will you changed from ...... font."
Because of that reason, this situation needs UI improvement.
(In reply to nurcantur from comment #4)
> Because of that reason, this situation needs UI improvement.
Absolutely, and we have a number of tickets about this. For example bug 78186 requesting better information on the complete document, bug 61134 which asks for improvement on the actual substitution appearance, and finally bug 96872 about to make it more obvious that a font has been substituted. Taking the latter as duplicate.
In https://design.blog.documentfoundation.org/2016/10/21/dealing-with-missing-fonts/ we suggested an infobar as solution.
*** This bug has been marked as a duplicate of bug 96872 ***