Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X
Hi All,
Two Qs:
1) Is there a place/functionality within these forums to provide 'pinned' or FAQ items that get repeatedly searched for? Like searching the software changes by build, with a list showing the areas affected with the new build? Or even a little topic organization?
2) In Arbortext Editor 6.0 Build 040, we've got some peculiarities with our Print Composer PDF Table of Contents and Alpha Index Outputs that we do not have in Build 010. I know there are stylesheets involved, but the DoD provided DTD and stylesheet files we are using have not changed. Specifically,
- a. The autogenerated Table of Contents have a couple of places where they run off the page bottom, overwriting the page number, and not displaying the rest of the TOC entries for that section (called a 'Work Package' in military tech manual parlance.) Not all TOC sections are affected, but it's a very obvious and noticeable problem to anyone doing DoD MIL-STD 40051-2 military tech manuals with standalone Arbortext Editor 6.0 and Print Composer to PDF with this problem.
- b. The alphabetic index also having a similar 'run-on' problem at the entries for the letter 'M' and none of the rest of the index after M shows up.
Again - I do realize that there is are stylesheet files involved here - but my point is that none of the DTD or stylesheet files have changed. We did not have these problems with Build 010, only with 040. So something has obviously changed in the software and it's interaction with Print Composer, the stylesheet files, or both.
Any and all insights appreciated.
Regards,
Bob Williams
East Providence RI, US
Hi Bob,
That "peg" place has been in existence since 1996, but it's hosted over at PTCuser.org: Adepters mailing list. is your best place for questions. Monitored by PTC R&D and Product Management as well as new and old customers.
Page fidelity is not guaranteed between releases (full or maintenance). Check the release notes for specific issues. Unfortunately, if you don't have the budget/skills to update the stylesheets (or your customer is responsible for their maintenance) your best bet is to downgrade to the maintenance release against which the stylesheets have been vetted.
Liz