> > unlike other output drivers, (x)dvipdfmx translates link destination > strings, such as (testA), (testB) in > > pdf:dest (testA) [@thispage /XYZ @xpos @ypos null] > pdf:dest (testB) [@thispage /XYZ @xpos @ypos null] > > specials, into internally generated integer strings (0), (1), ... in > /Dests <</Names [...] >> and in Link annotations of the final PDF. >
I think the problem here is that @token is used by the driver to reference a PDF object. For example, \special{pdf:obj @pdfOBJ PDF_Code1} \special{pdf:obj PDF_Code2} %here PDF_Code2 contains @pdfOBJ In PDF_Code2 every reference to @pdfOBJ will be replaced by a reference to the object that contais PDF_code1. A.S. ---------------------- Apostolos Syropoulos Xanthi, Greece -------------------------------------------------- Subscriptions, Archive, and List information, etc.: http://tug.org/mailman/listinfo/xetex