Am Wed, 25 Dec 2024 22:58:40 +0900 schrieb Norbert Preining:
Hi Hans,
On Wed, 25 Dec 2024, Hans Hagen wrote:
It's a GS issue ... it can't handle an in itself valid
Might be, but the statement:
│ **** file that it does not conform to Adobe's published PDF │ **** specification.
says something different. I am not sure about the PDF spec here, but if an empty beginbfrange is not allowed per spec, then luatex should not produce it.
In the ghostscript bug report Ken relaxed this statement to "senseless but legal" and the next gs seems to accept that. https://bugs.ghostscript.com/show_bug.cgi?id=708042#c3. The PDF/Postscript specs do not really say if 0 is allowed as value (typical vagueness) but as all readers seem to handle that ... -- Ulrike Fischer http://www.troubleshooting-tex.de/