There are things you can do programmatic to manage the code.
I recently came across this tool called Ecrion .. I thought this was
cool as you can design one front ( PDF / HTML Etc) in the designer and
ask the designer to produce the HTML/PDF/Text outputs.. This was cool.
The only problem with this is ofcourse, if the designs are different
for HTML and for PDF and the text. in which case, you will have to
redesign .. But if they are simple designs, then it does work a
magic.. May not be completely in context with the original question,
but nevertheless, worth its GBP 0.02 ...
On 26 May 2012 22:18, Dan Vint <dvint(_at_)dvint(_dot_)com> wrote:
The publication module may be a key difference. The current tools manage the
content of the publication through an interface and proprietary XML format.
So their graphical interface is used to organize the content and then
publish it. This is easy for the writers to use, but it doesn't allow me to
introduce any processing of my own. Anything I add has to be done after the
fact.
..dan
At 01:40 PM 5/26/2012, you wrote:
Hi Dan,
I am working in a similar environment, except we use 2 different sets of
stylesheets, but have many imported/included stylesheets shared across the
IETM and PDF. Like you, we have a S1000D input to publish a MIL-STD-40051
output. As you know the 40051 output covers a number of different Technical
Manuals (PDF output). We have over 15 Publication Modules which share over
1000 data modules. We use a "pipeline" approach like you do. We have been
doing this for 2 years with great success. Managing 2 sets of stylesheets
for 2 completely different outputs is manageable. In fact, I prefer it this
way. But trying to great a single set of stylesheets to output 2 completely
different outputs (IETM or PDF) would be a nightmare to manage (IMO).
Phil
On May 26, 2012, at 4:05 PM, Dan Vint wrote:
I have at least 3 environments that I need to keep consistent.
1) Arbortext editing environment
2) IETM output as HTML
3) 3rd party application that merges the data modules together into one
XML file that is then processed to make the PDF. Originally designed to be
a
mil-spec manual output but typically now just used for review copies where
the requirement is to make it more like the IETM output.
--~------------------------------------------------------------------
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>
--~--
--
Vasu Chakkera
NodeLogic Limited
Oxford
www.node-logic.com
==============
--~------------------------------------------------------------------
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>
--~--