I believe that in both the IETM and the publishing tool that they are
MS .NET based. Definitely on the IETM.
All the styling is currently handled within 3rd party applications,
where normally I would be running saxon via scripts and such. Ken's
message has me thinking about looking at the overall
workflow/pipeline and see if there is something that I can do outside them.
I have several resources available to me, it just happens that this
particular S1000D process uses a specific set of tools and has been
done this way for 5-6 years.
..dan
At 01:42 PM 5/26/2012, you wrote:
Dan,
In your prior email you said you were doing S1000D to PDF output.
What XSLT processor are you using?
On May 26, 2012, at 4:25 PM, Dan Vint wrote:
> Thanks, I am restricted to 1.0
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
---------------------------------------------------------------------------
Danny Vint
Panoramic Photography
http://www.dvint.com
voice: 619-938-3610
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--