[NTG-pdftex] pdftex.ch few prose garbled

Hartmut Henkel hartmut_henkel@gmx.de
Sun, 21 Sep 2003 11:32:42 +0200 (CEST)


The description text didn't fit to the ordering within the record.
Trivial text change see below. Record change would have consequences...

Greetings Hartmut


--- pdftex.ch.orig	Sat Aug  2 21:53:45 2003
+++ pdftex.ch	Sun Sep 21 11:21:52 2003
@@ -1738,21 +1738,21 @@
     int0, int1, int2, int3: integer;
 end;

-@ The first field of |obj_entry| contains link to the next
-object in |obj_tab| if this object in linked in a list.
-
-The second field contains information representing identifier of this object.
-Tt is usally a number for most of object types, but it may be a string number
+@ The first field contains information representing identifier of this object.
+It is usally a number for most of object types, but it may be a string number
 for named destination or named thread.

-The third field usually represents the pointer to some auxiliary data
-structure depending on the object type; however it may be used as a counter as
-well.
+The second field of |obj_entry| contains link to the next
+object in |obj_tab| if this object in linked in a list.

-The last field holds the byte offset of the object in the output PDF file.
+The third field holds the byte offset of the object in the output PDF file.
 Objects that have been not written yet have this field set to zero. However
 sometimes we have to use this field to store some info before the object is
 written out.
+
+The last field usually represents the pointer to some auxiliary data
+structure depending on the object type; however it may be used as a counter as
+well.

 @d obj_info(#) == obj_tab[#].int0 {information representing identifier of this object}
 @d obj_link(#) == obj_tab[#].int1 {link to the next entry in linked list}


------------------------------------------------------------------------
H. Henkel, Oftersheim, Germany
------------------------------------------------------------------------