[NTG-pdftex] Version numbering

Reinhard Kotucha reinhard.kotucha at web.de
Thu Jun 9 02:57:52 CEST 2005

>>>>> "Heiko" == Heiko Oberdiek <oberdiek at uni-freiburg.de> writes:

  >   \pdftexmainversion: readonly integer for A 
  >   \pdftexsubversion:  readonly integer for B 
  >   \pdftexbugfixversion: readonly integer for C

if you really intend to introduce new primitives, it would be better
to call them \pdfmajorversion and \pdfminorversion instead of
\pdftexmainversion and \pdftexsubversion.  It's easier to remember
because we already have \pdfoptionpdfminorversion.

As far as compatibility is concerned, it's probably best to leave
things as they are and add a new primitive \pdftexrevisionnumber.

\pdftexversion is quite straightforward as it is now.  It can easily
be split into major/minor version.

\pdftexrevision can be kept for backward compatibility.  It returns a

\pdftexrevisionnumber returns an integer.

Internally (in pdftex, the program), it is most straightforward if the
revision number is an integer rather than a character (maybe it
already is).  It can be used easily by printf to type the banner, and
\pdftexrevisionnumber has nothing to do but return this integer.
\pdftexrevision has to translate the number to a character.  This is
straightforward and absolutely backward compatible.

I'd then vote for the following translation scheme:

0  => ''
1  => 'a'
2  => 'b'
26 => 'z'

That means that a release has not automatically to be a bugfix release.
We can have 1.30 instead of 1.30.0 if \pdftexrevisionnumber=0.

\pdftexrevision expands to an empty string in this case.


Reinhard Kotucha			              Phone: +49-511-4592165
Marschnerstr. 25
D-30167 Hannover	                      mailto:reinhard.kotucha at web.de
Microsoft isn't the answer. Microsoft is the question, and the answer is NO.

More information about the ntg-pdftex mailing list