https://bugs.documentfoundation.org/show_bug.cgi?id=112020
Heiko Tietze <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #5 from Heiko Tietze <[email protected]> ---
Font substitution is another question. We made a suggestion how to improve this
situation at
https://design.blog.documentfoundation.org/2016/10/21/dealing-with-missing-fonts/
Talking about the special character dialog there is room for advanced features,
no question. While the average user searches by the unicode name <foo>, your
use case is to look for a particular unicode id <U+XYZ> not knowing in what
font it is defined. Once we have collected all these advanced functions we can
think about a second view, perhaps a tab or an expandable area, where those
could be added. But for now I believe our solution is superior to KCharSelect
for most users.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
