[Bug 159227] Special Character selection applying another font

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Sun Mar 2 23:30:52 UTC 2025


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

--- Comment #16 from Jan Lachnitt <pepalogik at seznam.cz> ---
(In reply to V Stuart Foote from comment #15)
> Any font substantially structured with PUA glyphs is breaking Unicode
> standard, it makes programs unstable. LibreOffice gains little in trying to
> interpret glyphs specified in PUA, while requiring too much non-standard
> font handling to do so.
> 
> Need only look at the PUA mapping of StarSymbol/OpenSymbol spread across the
> code base to see why this is not appealing. And why fonts, e.g. Type1,
> bitmap, even symbol (those are special case and get mapped) are not
> appealing to support.
> 
> So no, non-standards PUA glyphs are not welcome. And there is no up side to
> attempting to handle them when os/DE font fallback methods kick in.
> 
> IMHO => NAB and => WF

I'm sorry, but I don't understand your reasoning (and don't know what WF
means). I can give my reasoning.

For example, ɑ (alpha) or ± (plus-minus) are well-defined Unicode symbols,
which, I believe, are available in all common fonts. When inserting them, there
is no reason to preserve the font from which they were inserted previously.

So, I'm proposing this change: When a symbol is inserted using the popup (with
popular and recently used symbols), the current font should be used, except if
the character is in a PUA or if it's not available in the current font.

Maybe the present behavior is not precisely a bug, as it was intended. We may
then call this a feature request.

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


More information about the Libreoffice-ux-advise mailing list