Hi Suresh-
A more robust way to do this, i.e. manage separate editor and print
stylesheets, is to put the stylesheets in the doc type directory, and
make sure each stylesheet's APT Stylesheet processing instruction has
the correct info about the composition types it supports. You can set it
up like this:
1) For client:
a. Make the editor stylesheet name match the DTD name. In other
words, if DTD is mydoctype.dtd, then make the editor stylesheet
mydoctype.fos
b. Edit the Stylesheet PI in that stylesheet so the
CompositionTypes field does NOT contain "pdf" or "print"
c. Make the print stylesheet have a different name, e.g.
mydoctype_print.fos
d. Edit the Stylesheet PI in that stylesheet so the
CompositionTypes field DOES contain "pdf" and "print" (this is probably
true already)
2) For server:
a. Put a copy of the print stylesheet there, making sure it
contains the "pdf" and "print" options for CompositionTypes in the
Stylesheet PI.
Finally, remove the hard-coded stylesheet associations from your actual
document files. After you've done that, Arbortext should be able to
successfully find the right stylesheet for the right task, whether you
are composing locally or on the server.
Good luck!
--Clay
