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

--- Comment #10 from Dave Gilbert <[email protected]> ---
OK, I think the problem is that LO is using it's fonts to decide which font to
use but then mmap'ing the system fonts that aren't consistent with them;

Turning on some debug, in the working one I see:

info:vcl.fonts:PIDb:PIDb:vcl/unx/generic/fontmanager/fontconfig.cxx:1123:
PrintFontManager::Substitute: replacing missing font: 'serif' with 'Noto Serif'
info:vcl.unx.freetype:PIDb:PIDb:vcl/unx/generic/glyphs/freetype_glyphcache.cxx:139:
mmap'ed '/usr/share/fonts/google-noto/NotoSerif-Regular.ttf' successfully

so that's found my system NotoSerif-Regular I guess.

On the broken one we have:
warn:vcl.fonts:2547652:2547652:vcl/unx/generic/fontmanager/fontconfig.cxx:1029:
no FC_FILE found, falling back to name search
info:vcl.fonts:2547652:2547652:vcl/unx/generic/fontmanager/fontconfig.cxx:1123:
PrintFontManager::Substitute: replacing missing font: 'serif' with 'Noto Naskh
Arabic'
Lots of:
info:vcl.gdi:2547652:2547652:vcl/source/outdev/font.cxx:1083: Font fallback to
the same font, but has missing codes

but if I look at the LO provided Naskh Arabic font in FontForge the font has
the standard latin A-Z/a-z - so it should be fine.

But...

grep'ing for noto and mmap, in the working one:
[dg@dalek core]$ grep -i noto log.00db8423d18d |grep -i mmap
info:vcl.unx.freetype:PIDb:PIDb:vcl/unx/generic/glyphs/freetype_glyphcache.cxx:139:
mmap'ed '/usr/share/fonts/google-noto/NotoSans-Regular.ttf' successfully
info:vcl.unx.freetype:PIDb:PIDb:vcl/unx/generic/glyphs/freetype_glyphcache.cxx:139:
mmap'ed '/usr/share/fonts/google-noto/NotoSans-Thin.ttf' successfully
info:vcl.unx.freetype:PIDb:PIDb:vcl/unx/generic/glyphs/freetype_glyphcache.cxx:139:
mmap'ed '/usr/share/fonts/google-noto-vf/NotoSansArabic[wght].ttf' successfully
info:vcl.unx.freetype:PIDb:PIDb:vcl/unx/generic/glyphs/freetype_glyphcache.cxx:139:
mmap'ed '/usr/share/fonts/google-noto/NotoSans-Medium.ttf' successfully
info:vcl.unx.freetype:PIDb:PIDb:vcl/unx/generic/glyphs/freetype_glyphcache.cxx:139:
mmap'ed '/usr/share/fonts/google-noto/NotoSerif-Regular.ttf' successfully

and in the broken one:
info:vcl.unx.freetype:PIDb:PIDb:vcl/unx/generic/glyphs/freetype_glyphcache.cxx:139:
mmap'ed '/usr/share/fonts/google-noto/NotoSans-Regular.ttf' successfully
info:vcl.unx.freetype:2547652:2547652:vcl/unx/generic/glyphs/freetype_glyphcache.cxx:139:
mmap'ed '/usr/share/fonts/google-noto/NotoSans-Regular.ttf' successfully
info:vcl.unx.freetype:2547652:2547652:vcl/unx/generic/glyphs/freetype_glyphcache.cxx:139:
mmap'ed '/usr/share/fonts/google-noto/NotoSans-Thin.ttf' successfully
info:vcl.unx.freetype:2547652:2547652:vcl/unx/generic/glyphs/freetype_glyphcache.cxx:139:
mmap'ed '/usr/share/fonts/google-noto-vf/NotoSansArabic[wght].ttf' successfully
info:vcl.unx.freetype:2547652:2547652:vcl/unx/generic/glyphs/freetype_glyphcache.cxx:139:
mmap'ed '/usr/share/fonts/google-noto/NotoSans-Bold.ttf' successfully
info:vcl.unx.freetype:2547652:2547652:vcl/unx/generic/glyphs/freetype_glyphcache.cxx:139:
mmap'ed '/usr/share/fonts/google-noto/NotoSans-Thin.ttf' successfully
info:vcl.unx.freetype:2547652:2547652:vcl/unx/generic/glyphs/freetype_glyphcache.cxx:139:
mmap'ed '/usr/share/fonts/google-noto-vf/NotoSansArabic[wght].ttf' successfully
info:vcl.unx.freetype:2547652:2547652:vcl/unx/generic/glyphs/freetype_glyphcache.cxx:139:
mmap'ed '/usr/share/fonts/google-noto/NotoSans-Medium.ttf' successfully
info:vcl.unx.freetype:2547652:2547652:vcl/unx/generic/glyphs/freetype_glyphcache.cxx:139:
mmap'ed '/usr/share/fonts/google-noto-vf/NotoNaskhArabic[wght].ttf'
successfully

now if look at /usr/share/fonts/google-noto-vf/NotoNaskhArabic[wght].ttf it is
missing the standard ASCII letters. (That's from Fedora's
google-noto-naskh-arabic-vf-fonts-20230801-3.fc39.noarch package)

So, it looks like LO is making decisions on the font to use based on it's
installed set, but then using the system fonts that are inconsistent with that
decision.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to