Re: Demystifying “symbol” fonts

Khaled Hosny <khaledhosny -AT- eglug.org>
Fri, 18 Nov 2016 05:53:45 +0200

On Fri, Nov 18, 2016 at 02:28:59AM +0200, Khaled Hosny wrote:

So I think the problem here is that we are not doing any glyph fallback
for OpenSymbol. Looks like we skip glyph fallback for symbol fonts in
vcl/unx/generic/fontmanager/fontsubst.cxx
FcPreMatchSubstitution::FindFontSubstitute(), which makes sense generally,
except when you need it…


I think messing with the font fallback is something I want to do, so the
simplest fix is to find a suitably licensed font and copy the few
missing glyphs (a quick look shows only 21 glyphs are missing from Adobe
Symbol encoding). What is the current license of OpenSymbol? I remember
is was a bit of a mess few years ago.

Regards,
Khaled

Context

Re: Demystifying “symbol” fonts (continued)
- Re: Demystifying “symbol” fonts · toki
  - Re: Demystifying “symbol” fonts · Khaled Hosny
    - Re: Demystifying “symbol” fonts · Kaganski Mike
- Re: Demystifying “symbol” fonts · Caolán McNamara
  - Re: Demystifying “symbol” fonts · Khaled Hosny
    - Re: Demystifying “symbol” fonts · Khaled Hosny
      - Re: Demystifying “symbol” fonts · Caolán McNamara

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.