\pdfoptionpdfminorversion
Hi, I'm wondering whether pdftex complains if I set the variable \pdfoptionpdfminorversion to a very low value and use PDF features which had been introduced in more recent versions of Acrobat. Does pdftex complain in this case? There is a problem with the manual, the file pdftex-a.pdf contains the line "%PDF-1.5" which requires AR6 which is not available for Linux. I doubt that this is necessary here because it doesn't make use of the latest features. So "%PDF-1.4" would be better. Maybe even a lower value could be used. Because many people work on the manual, it makes sense to set \pdfoptionpdfminorversion explicitely in the file. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-4592165 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ----------------------------------------------------------------------------
On 2005-02-21 02:29:24 +0100, Reinhard Kotucha wrote:
I'm wondering whether pdftex complains if I set the variable \pdfoptionpdfminorversion to a very low value and use PDF features which had been introduced in more recent versions of Acrobat.
Does pdftex complain in this case?
No. It's only checked against the version of included pdfs. 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 http://www.artcom-gmbh.de
On Mon, Feb 21, 2005 at 02:29:24AM +0100, Reinhard Kotucha wrote:
Hi, I'm wondering whether pdftex complains if I set the variable \pdfoptionpdfminorversion to a very low value and use PDF features which had been introduced in more recent versions of Acrobat.
Does pdftex complain in this case?
User code (in dictionaries, streams, ...) is not interpreted
by pdfTeX and is not checked against the different PDF
specifications. Thus the user have to take care. Or
\pdfoptionpdfminorversion should be set to low values
by experts only.
But perhaps at least code by pdfTeX itself could be checked.
Consider this example:
\pdfoptionpdfminorversion=0
\pdfdest name {foobar} Fit
\null
\nopagenumbers
\bye
Now the pdf file contains a named destination using a string
This is a feature of PDF 1.2. The pdf file, however,
is marked as "%PDF-1.0".
This could be solved by an internal variable that records the
maximum version of used PDF features. Then conflicts with
\pdfoptionpdfminorversion can be detected and an error or
warning can be raised.
Also this can be extended by a new primitive, thus that
packages such as hyperref also can mark its code with
its maximum version number of used PDF features.
Yours sincerely
Heiko
On Mon, 21 Feb 2005, Heiko Oberdiek wrote:
This could be solved by an internal variable that records the maximum version of used PDF features. Then conflicts with \pdfoptionpdfminorversion can be detected and an error or warning can be raised.
Or pdftex could track the maximum of minor version and write this value at the _end_ of the pdftex run (currently it's written at the start, and frozen). There is already a procedure for setting the /Length counts, which can be mis-used, e. g. i have just tried this: @
Also this can be extended by a new primitive, thus that packages such as hyperref also can mark its code with its maximum version number of used PDF features.
Regards, Hartmut
"Hartmut" == Hartmut Henkel
writes:
On Mon, 21 Feb 2005, Heiko Oberdiek wrote:
This could be solved by an internal variable that records the maximum version of used PDF features. Then conflicts with \pdfoptionpdfminorversion can be detected and an error or warning can be raised.
Or pdftex could track the maximum of minor version and write this value at the _end_ of the pdftex run (currently it's [...]
If you really want to change the pdftex sources, keep in mind that Adobe certainly will change the *major* number in the near future. Maybe it's better to keep the whole version number within one variable, so that if Adobe changes the major number, not everything has to be changed again. Regards, Reinhard -- ---------------------------------------------------------------------------- Reinhard Kotucha Phone: +49-511-4592165 Marschnerstr. 25 D-30167 Hannover mailto:reinhard.kotucha@web.de ---------------------------------------------------------------------------- Microsoft isn't the answer. Microsoft is the question, and the answer is NO. ----------------------------------------------------------------------------
On 2005-02-23 23:00:07 +0100, Reinhard Kotucha wrote:
If you really want to change the pdftex sources, keep in mind that Adobe certainly will change the *major* number in the near future.
Nope. Changing the major number means everything can be incompatible; e.g. PDF 2.0 could use XML instead of XREF+objects. That would break everything, which even Adobe can't do. 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 http://www.artcom-gmbh.de
Martin Schröder wrote:
On 2005-02-23 23:00:07 +0100, Reinhard Kotucha wrote:
If you really want to change the pdftex sources, keep in mind that Adobe certainly will change the *major* number in the near future.
Nope. Changing the major number means everything can be incompatible; e.g. PDF 2.0 could use XML instead of XREF+objects. That would break everything, which even Adobe can't do.
i suppose they will do the same as with PS, level 3 is still downward compatible, so major is not so much breaking things but more indicating some real big change (whatever that may be) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 2005-02-24 10:53:38 +0100, Hans Hagen wrote:
i suppose they will do the same as with PS, level 3 is still downward compatible, so major is not so much breaking things but more indicating some real big change (whatever that may be)
The spec says this in H.1: "Adobe increments the major version number when the PDF specification changes in such a way that existing viewer applications are unlikely to read a document without serious errors that prevent pages from being viewed." 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 http://www.artcom-gmbh.de
Martin Schröder wrote:
On 2005-02-24 10:53:38 +0100, Hans Hagen wrote:
i suppose they will do the same as with PS, level 3 is still downward compatible, so major is not so much breaking things but more indicating some real big change (whatever that may be)
The spec says this in H.1:
"Adobe increments the major version number when the PDF specification changes in such a way that existing viewer applications are unlikely to read a document without serious errors that prevent pages from being viewed."
sure, but the reader will read older versions; i wonder, what criterium do we use for incrementing a pdf major number Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 2005-02-24 12:35:25 +0100, Hans Hagen wrote:
i wonder, what criterium do we use for incrementing a pdf major number
ITIYM pdftexs version? :-) MAJOR feature enhancements. 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 http://www.artcom-gmbh.de
participants (5)
-
h h extern
-
Hartmut Henkel
-
Heiko Oberdiek
-
Martin Schröder
-
Reinhard Kotucha