Date: prev next · Thread: first prev next last
February 2017 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=105318

--- Comment #4 from V Stuart Foote <vstuart.foote@utsa.edu> ---
(In reply to Heiko Tietze from comment #3)
Should be solved with
https://design.blog.documentfoundation.org/2016/10/21/dealing-with-missing-
fonts/. The topic is one of the GSoC'17 ideas, and Akshay seems to be
interested. No mentor yet, though.

Hmm, not quite. Issue is that absent the font (no embed, or not installed to
system) the Special Character dialog does not use the fall-back font. Rather it
uses the System font.

Otherwise, from edit cursor positions using an installed font, the Special
Character dialog opens to that font.

So the Special Character dialog opening to System font is currently
inconsistent as is. But--by picking up the fall-back font replacement in use at
the edit cursor--the dialog could be made more useful and less inconsistent.

That would be regardless of the UI work that the design blog/GSoC'17 might
address.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.