Community Tip - You can Bookmark boards, posts or articles that you'd like to access again easily! X
I've now dug through 17 PTC PDF manuals.
Where in the world is an honest to goodness error log?
It is bad enough the composer log window when it does give the line of the stylesheet where it hit an error, it doesn't tell you which XML file it was parsing at the time. I've got those cleaned up now BUT!
I still have a multitude of errors that are just too vague to be useful (like "received fo:block when expected fo:root" with no code context at all).
I've dug through the transaction archives file by file. I still don't know what to do with a .dat file even with all the PDF manuals.
Shoot, I can't even get our Windows 2003 Server to show the Java Console!
Finally get through IT and get some access to the server, but I still can't find a decent error log.
Thanks again, guys...
John T. Jarrett
Sr. Tech Writer, BAE Systems
Arbortext version 5.4
LOGSA XSL-FO v 1.5