Community Tip - Learn all about the Community Ranking System, a fun gamification element of the PTC Community. X
Hi,
I am having issues when a PDF is created, the labeling is incorrect and out of order on table of contents, tables and figures. Please see sample file for example. Has anyone co
Is this the using the ootb stylesheet or have you customized it already?
Bryon
They were actually customized for us by PTC, have not modified it since. Have been using the same stylesheet since 5.3 and is now experiencing issues in 8.2.3.
That is a huge jump. The stylesheet will have been modified by editor when you first opened it to bring it up to speed with the version of software. But there will probably be issues like you are seeing. You will probably need to get PTC or Partner (GSPL, EAC, etc) to take a look at the stylesheet and fix anything that broke during the upgrade. We ran into the same issue.
Bryon
EAC here, happy to review the stylesheet and define a plan for making it work with Arbortext 8.2.3.
Mike (msimon at eacpds.com)
Hello, I am working with the original poster and I wanted to add some context. We are working on switching from Arbortext 5.3 to 8.2.3 (these issues also happen with 6/7/8). Our issues seems to be a result of using variants. We noticed that when PDF’ing using 8.2.3 the labelling is not correct for the types of elements that can have a label. We have many variants, meaning that figures, tables, paras, steps, etc may only be tagged for certain variants. A figure might be 1-10 for one variant, but be 1-12 for another variant, and not exist for the other variants. There did not seem to be an issue with labelling in 5.3. When we PDF’d, the figure/table/para/step numbers would be correct. If there was no label, it would automatically be labelled in the PDF, and if the label was incorrect in Arbortext, it would be corrected in PDF. The PDF labelling was also sequential, so elements not applicable to a variant would not affect the PDF labelling. However, in Arbortext 8.2.3 the labelling does not seem to be working. If an element does not have a label, then when PDF’d it does not get a label. When you PDF the elements that have existing labels will be labelled but they do not get automatically numbered to the correct label. So the result is many elements missing numbers and the numbers skipping. Hardtyping labels would not be possible because we have many variants and the labels would all be different for each variant.
We encountered a similar issue recently, where Warning/Cautions/Notes aligned correctly in 5.3 but not when using 6/7/8/8.2.3. The resolution was that this was a side effect of a functional change with Arbortext 6 & up and to fix it we needed to alter a line in the block-atts.sgm file. I think the labelling issue is also a result of a functional change with Arbortext 6 & up, but we aren't sure what to change to get it to work like it did previously.