Hi Diego, Diego Nicola Barbato skribis: > When converting certain PDF files to PostScript pdf2ps (from the > Ghostscript package) will print the following error messages: > > **** Error reading a content stream. The page may be incomplete. > Output may be incorrect. > **** Error: File did not complete the page properly and may be damaged. > Output may be incorrect. > > The resulting file will be missing some (sometimes all) of the text. I have spent time investigating this issue, in vain so far. There’s already one conclusion that can be drawn: pdf2ps succeeds in my experience with PDFs that do *not* embed fonts (one of the 14 standard fonts.) It fails, as in this case, when fonts *are* embedded. Looking at the strace output, I initially thought our gs was missing its resource files: they were supposed to be compiled in (“COMPILE_INITS=1”), but my understanding was that this was only the case for the statically-linked gs, which we disabled in commit eb354bdacbf4154ec66038dac07f19bf4ced1fad. So I started by passing --disable-compile-inits and then fixing up ENOENT issues that I could notice in the strace output (patch below), but that didn’t make any difference. I’m still not sure how to interpret this error, it’s really not clear to me what it really means. Reports like suggest it has to do with fonts, but it’s not all that clear in this case. Anyway, it’s also clear that this is the same problem people experience when printing. Ideas welcome! Ludo’.