summaryrefslogtreecommitdiffstats
path: root/src/gui/kernel/qplatformwindow.cpp
diff options
context:
space:
mode:
authorEskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>2025-04-04 12:55:14 +0200
committerEskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io>2025-04-23 11:32:40 +0200
commit09805f355c7eb2ece70bcc58e731433980e31126 (patch)
treed8a2aa2bf7527b421d7fd6aa9de77c24dcee9314 /src/gui/kernel/qplatformwindow.cpp
parent616d33c87ab6dd77809ee56e39e08eed30089130 (diff)
directwrite: Fix embedding fonts in PDF
For a reason still unclear to me, the PDF engine refuses to embed fonts if the file name is empty (so fonts that are loaded directly from byte arrays typically). It could be that this in itself is outdated. However, embedding fonts that are loaded from the file system has worked so far, but in Qt 6.8 we moved to the DirectWrite engine on Windows and this stopped working there. The reason is that our custom file loader did not support tracking the file name and thus it would always be empty. This is experienced as a regression and can only be worked around by manually selecting the GDI engine instead (with the limitations that implies). We fix this by implementing the loader as a IDWriteLocalFontFileLoader instead, which supports the API which we currently use to retrieve the paths of system-wide fonts. Pick-to: 6.8 6.9 Fixes: QTBUG-134695 Change-Id: I1411b0617fd1c113c7c28154968c234920f5289e Reviewed-by: Eirik Aavitsland <eirik.aavitsland@qt.io>
Diffstat (limited to 'src/gui/kernel/qplatformwindow.cpp')
0 files changed, 0 insertions, 0 deletions