Skip to main content
J
JamesCLS12-Amethyst
12-Amethyst
November 11, 2019
Solved

How to Set ArborText Publishing Engine to Use Local Graphics

  • November 11, 2019
  • 2 replies
  • 2280 views

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).

 

Best answer by JamesCLS

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.

2 replies

G
GarethOakes16-Pearl
16-Pearl
November 12, 2019

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.

J
JamesCLS12-AmethystAuthor
12-Amethyst
November 12, 2019

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.

G
GarethOakes16-Pearl
16-Pearl
November 13, 2019

Thanks for taking the time to follow up! This is valuable knowledge for the community and I'm glad you got the problem resolved.

J
JamesCLS12-AmethystAuthorAnswer
12-Amethyst
November 12, 2019

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.

Terms & ConditionsCookie settingsAccessibility statement