pdf_version_found > pdf_version_wanted
Hi, current pdfTeX will not embed pdfs with a newer version than the one to be produced. I want to make this behaviour configurable through pdftex.cfg (and a corresponding primitive). pdfTeX would then only emit a warning but embed the pdf anyway (like older versions did). Reason is to be backwards-compatible: We have installations where we want to upgrade the pdfTeX-installation but not the TeX-producing application. Objections? Best regards Martin -- Martin Schröder, MS@ArtCom-GmbH.DE ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10
On 2003-07-08 17:55:17 +0200, Martin Schröder wrote:
one to be produced. I want to make this behaviour configurable through pdftex.cfg (and a corresponding primitive). pdfTeX would
Currently the primitive is tentatively named \pdfoptionpdfversionerrorlevel. Any better idea? Best regards Martin -- Martin Schröder, MS@ArtCom-GmbH.DE ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10
On Thu, Jul 10, 2003 at 05:29:13PM +0200, Martin Schroeder wrote:
On 2003-07-08 17:55:17 +0200, Martin Schröder wrote:
one to be produced. I want to make this behaviour configurable through pdftex.cfg (and a corresponding primitive). pdfTeX would
Currently the primitive is tentatively named \pdfoptionpdfversionerrorlevel. Any better idea?
What is the semantics?
pdfTeX generates 1.x and an image has version 1.y:
x := \pdfoptionpdfversion
z := \pdfoptionpdfversionerrorlevel
x >= y
no problems
y > x
??
* Abort with error message / continuing with warning
depending on z.
* Accepting some images with versions smaller 1.z or 1.(x+z)
with warning, aborting otherwise.
What happens, if there will be PDF 2.? some day?
Yours sincerely
Heiko
On 2003-07-10 18:06:29 +0200, Heiko Oberdiek wrote:
pdfTeX generates 1.x and an image has version 1.y: x := \pdfoptionpdfversion z := \pdfoptionpdfversionerrorlevel
x >= y no problems
y > x ?? * Abort with error message / continuing with warning depending on z.
Yes. pdfTeX <1.10a didnn't care for x and y; you only got a warning from the xpdf layer when y was greater than the y supported by xpdf. I want to get that behaviour back to be backwards-compatible. [...]
What happens, if there will be PDF 2.? some day?
Then we will need a major rewrite of pdfTeX anyway, as this will break almost any pdf consuming application anyway (see PDFRef H.1). Of course a float for x would be nice, but it's currently not needed and there is no code in pdfTeX yet to scan float parameters. Best regards Martin -- Martin Schröder, MS@ArtCom-GmbH.DE ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10
On 2003-07-10 18:17:36 +0200, Martin Schröder wrote:
Yes. pdfTeX <1.10a didnn't care for x and y; you only got a warning from the xpdf layer when y was greater than the y supported by xpdf. I want to get that behaviour back to be backwards-compatible.
I'm leaning towards naming the primitive \pdfoptionpdfinclusionerrorlevel, since it will be initialized with 1 (error if y > x) and allows future extensions. Comments? Martin -- Martin Schröder, MS@ArtCom-GmbH.DE ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10
On 2003-07-11 10:51:08 +0200, Martin Schröder wrote:
I'm leaning towards naming the primitive \pdfoptionpdfinclusionerrorlevel, since it will be initialized with 1 (error if y > x) and allows future extensions.
#3319 - The behaviour when an included pdf has a newer version than the one specified with \pdfoptionpdfminorversion can be controlled by the new internal integer \pdfoptionpdfinclusionerrorlevel: If it's 0, pdfTeX gives only a warning; if it's 1, it raises an error. This can also be set in pdftex.cfg with pdf_inclusion_errorlevel Best regards Martin -- Martin Schröder, MS@ArtCom-GmbH.DE ArtCom GmbH, Lise-Meitner-Str 5, 28359 Bremen, Germany Voice +49 421 20419-44 / Fax +49 421 20419-10
participants (2)
-
Heiko Oberdiek -
Martin Schroeder