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
We have two very similar DTDs. Both DTDs have the exact same graphic definition. Graphics for both DTDs are using the same exact folder structure. SGML files for both DTDs are pointing to graphics in the same exact manner.
However, graphics are behaving very differently. For DTD-A, ArborText Publishing Engine will use local graphics when creating the PDF. For DTD-B, ArborText Publishing Engine will not use local graphics when creating the PDF.
Am I missing a setting someplace?
EDIT: Both DTDs are using the same exact style sheet (the DTDs are that similar that one style sheet works for both of them).
Solved! Go to Solution.
For anyone who comes across this, it was the DCF file - DTD-A had one while DTD-B did not. Plus, after providing DTD-B with the same DCF file, there was a delayed reaction from the ArborText Publishing Engine. After about 20 minutes, the PE started reading the new DCF file.
I don't have an answer but it would be interesting to learn more details: what publishing engine you are using (FOSI or APP), if your graphics are referenced by entity (as opposed to filename), is NOTATION or NDATA used, etc.
I'm using the XSL-FO engine. The graphics are using an entities with NDATA.
However, it was a missing DCF file that was the culprit. Additionally, the PE took a few minutes to start using the new DCF file.
Thanks for taking the time to follow up! This is valuable knowledge for the community and I'm glad you got the problem resolved.
For anyone who comes across this, it was the DCF file - DTD-A had one while DTD-B did not. Plus, after providing DTD-B with the same DCF file, there was a delayed reaction from the ArborText Publishing Engine. After about 20 minutes, the PE started reading the new DCF file.