Actually, it looks like a JIRA entry won't be necessary. Switching to OTFParser seems to do the trick for this file.
Further, I think the difference in behavior was due to the disappearance of the "parseOnDemand" option, which I was using (when on-demand is enabled in FontBox 2.x, this CFF validation doesn't run). Thanks again for the pointers! Daniel On Mon, Feb 9, 2026 at 9:13 PM Daniel Gredler <[email protected]> wrote: > That's odd. It has a ".otf" file extension, and FontBox 2.x didn't seem to > have any issues with it. > > I'll create a JIRA issue with more information, since it sounds like > feature parity is expected here (and I should be able to attach the > offending file). > > Take care, > > Daniel > > > On Mon, Feb 9, 2026 at 8:57 PM Tilman Hausherr <[email protected]> > wrote: > >> Am 09.02.2026 um 20:43 schrieb Daniel Gredler: >> > Ah, got it -- thanks! This indeed fixed the EOF issue. >> > >> > However, I'm now getting the following error: "True Type fonts using CFF >> > outlines are not supported" >> > >> > This is while reading the Noto Sans CJK Regular font file. Is this an >> area >> > where FontBox 3.x functionality is more limited than FontBox 2.x was? >> >> No, you should get the same exception in 2.0. If you don't have it as a >> ttf file, it should work as a ttc file, however the calls are different >> >> https://github.com/notofonts/noto-cjk/tree/main/Sans/OTC >> >> https://github.com/notofonts/noto-cjk/tree/main/Sans >> >> from the EmbeddedMultipleFonts.java example >> >> TrueTypeCollection ttc2 = new TrueTypeCollection(new >> File("c:/windows/fonts/batang.ttc")); >> >> PDType0Font font2 = PDType0Font.load(document, >> ttc2.getFontByName("Batang"), true); // Korean >> >> >> TrueTypeCollection can take an inputstream. >> >> However I see from that website that ttf files are also available, if >> you know which country you need. >> >> >> Tilman >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
