Thank you for the bug report. On Sun, 29 Sep 2024 11:26:12 +1000 Stuart Prescott <stu...@debian.org> wrote:
> $ lualatex test3
Strangely, my machine errors out here:
luatex test3
This is LuaTeX, Version 1.18.0 (TeX Live 2025/dev/Debian)
restricted system commands enabled.
(./test3.tex
! Undefined control sequence.
l.1 \documentclass
{article}
?
I have texlive-luatex installed, Is there something else required?
> ### In sid
>
> $ gs --version
> 10.04.0
>
> $ gs -q -sDEVICE=txtwrite -o %stdout% test3.pdf
> X#
Confirmed the same output when using the test3.pdf you generated.
> This problem does not extend to all PDFs; in fact it seems to be
> confined to PDFs generated by lualatex while pdflatex is OK.
> Unfortanately for modern fonts and UTF-8, users are encouraged to use
> lualatex these days, and the plastex test suite does so. As seen below,
> lualatex picks different fonts and encodes them differently - that seems
> to be what ghostscript is getting wrong.
>
> $ pdffonts test3-lualatex.pdf
> name type encoding emb
> sub uni object ID ------------------------------------ -----------------
> ---------------- --- --- --- --------- VFSMBO+LMRoman10-Regular
> CID Type 0C Identity-H yes yes yes 4 0
>
> $ pdffonts test3-pdftex.pdf
> name type encoding emb
> sub uni object ID ------------------------------------ -----------------
> ---------------- --- --- --- --------- ZKXRNQ+CMR10
> Type 1 Builtin yes yes yes 4 0
>
It seems like you may have identified the issue? There's an existing upstream
bug report suggesting incomplete support for "CID-Keyed font". I don't know
what that means, but please take a look at the following bug report and let me
know if this matches your issue or not.
https://bugs.ghostscript.com/show_bug.cgi?id=705288
Best,
-Steve
signature.asc
Description: This is a digitally signed message part.
