Control: severity 995392 grave
Control: severity 995678 normal
Control: tags 995678 - moreinfo
Please be careful with the bug numbers...
On 2021-10-11 08:27:55 +0900, Norbert Preining wrote:
> Then, this is by far not a grave bug in TL. pdflatex is **not**
> affected, since it generated pdf files without using ghostscript.
??? A PDF file is designed to be read by other tools. If pdflatex
generates an invalid PDF file (as assumed by some Ghostscript
developer, which has not been confirmed yet), then it could be a
grave bug. This is a bit like C code with undefined behavior: with
some compilers, the compiled code may work, but other compilers may
generate code with erratic behavior; the bug is in the C code.
Here, the consequence is silent data loss when using Ghostscript on
the generated PDF file.
> Vincent, thanks for the tests, but without explanation or make files
> or some hints on **what** you did run, this is not reproducible and
> testable.
I've attached an archive with
* chartest3.tex (already mentioned)
* chartest3.aux, chartest3.log, chartest3.pdf: the files generated
with "pdflatex chartest3.tex"
* out.pdf: the file generated with
/usr/bin/ps2pdf chartest3.pdf out.pdf
(ghostscript 9.54.0~dfsg-5 being installed) after unsetting
GS_OPTIONS.
"pdftotext out.pdf -" gives:
Test: ń donŠt ż.
(but also copy-paste from xpdf and atril).
With chartest3.pdf generated by TL 2020, then the same ps2pdf command,
I get:
Test: « don’t ».
as expected.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Attachment:
chartest.tar.xz
Description: application/xz