[Bug 159227] Special Character selection applying another font

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Sun Mar 2 21:39:50 UTC 2025


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

--- Comment #15 from V Stuart Foote <vsfoote at libreoffice.org> ---
 (In reply to Jan Lachnitt from comment #14)
> (In reply to Heiko Tietze from comment #13)
> > Sounds easy: use the current font if the symbol exists. But what if the font
> > "abuses" a unicode character to draw something completely different? For
> > example https://www.azfonts.net/fonts/wingding-review/normal-107375
> 
> I see the problem, but I think LO should rather be adapted for standards
> than for fonts that break them.
> 
> Alternatively, you can add a switch to LO settings, thus letting the user
> choose.

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

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


More information about the Libreoffice-ux-advise mailing list