Version "0.9.0" and external fonts and default-features = false show no Text in PDF Reader

[watchtmouse]

Hello Felix thank for a great tool,

This is the first issue I post on Github

I came from Version 0.7 of printpdf and switched to version 0.9.0 yesterday.
When I user internal fonts my generated PDFs Show text when opening them in a PDF Reader when I use External fonts no Text is shown.

Can you please verify that PDFs generated with printpdf 0.9.0 have there External fonts Embedded?

To verify I used the program https://github.com/fschutt/printpdf/blob/master/examples/otf-font.rs , I now think there is nothing wrong with my program, since this shows the same behaviour (no Text shown in the PDF reader).

At the moment 17.02.2024 14:45 CET I Cannot compile without "default-features = false" because I get the following Error

   Compiling azul-css v0.0.6
   Compiling thiserror v2.0.18
   Compiling derive_more v0.99.20
error[E0308]: mismatched types
   --> /home/bert/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/azul-css-0.0.6/src/corety.rs:232:47
    |
232 |         let c_str = core::ffi::CStr::from_ptr(ptr);
    |                     ------------------------- ^^^ expected `*const u8`, found `*const i8`
    |                     |
    |                     arguments to this function are incorrect
    |
    = note: expected raw pointer `*const u8`
               found raw pointer `*const i8`
note: associated function defined here
   --> /home/bert/.rustup/toolchains/stable-aarch64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ffi/c_str.rs:253:25
    |
253 |     pub const unsafe fn from_ptr<'a>(ptr: *const c_char) -> &'a CStr {
    |                         ^^^^^^^^

This is my Cargo.toml

[package]

name = "fonts"
version = "0.1.0"
edition = "2024"

[dependencies]
#printpdf = { git = "https://github.com/fschutt/printpdf", rev = "ebe45a6" }
#printpdf = { version = "0.9.0"}
printpdf = { version = "0.9.0", default-features = false }

Thanks

[fschutt]

Commit 6a01c46 (2025-11-24, "Add a fake ParsedFont when text_layout is disabled") introduced a stub ParsedFont and minimal font serialization path that shipped in 0.9.0. When default-features = false, the text_layout feature is disabled. Therefore, the font serialization generated an invalid PDF font dictionary.

Fixed in ead57b8.

The other issue (azul-css not compiling) was fixed in fschutt/azul@d9c11de - a small type casting problem. Released / fixed in azul-css 0.0.7 on crates.io.

NOTE: Without the text_layout feature, ParsedFont::from_bytes() still creates a stub with empty mappings — you need to use with_glyph_data() to provide cmap/width data manually, or enable the text_layout feature for automatic font parsing via azul-layout. This was more or less "intentional" to allow users to use the other PDF features without depending on allsorts (if you have your own font shaper). The "bug" was introduced when the dependencies were refactored (in order to help cut down the number of dependencies).

[watchtmouse]

Thanks for investigating so quickly, from your comments I tried the following in the Cargo.toml
printpdf = { git = "https://github.com/fschutt/printpdf", rev = "ead57b8", default-features = false, feature = "text_layout" }
it compiles but the Text is still not shown in the PDF Reader.

I happily wait for the Next released version of printpdf, for me no need to rush.