atw: Re: XML and Word

Hi Nikki,
 
I have developed and commercially implemented what you are talking about. I
have XSLT transforms from a fairly straightforward Word template to HTML
sites (currently 3 different audiences) and PDF and CHM.
 
Tools wise all you need is sufficient XML Spy licences for the author(s).
See www.altova.com for pricing.
 
Someone with your background can easily learn to author in XML Spy without
having to code. Basically Spy gives you a drag and drop structured authoring
interface.
 
There is a lot of work behind the XSLT to do all this. I'd be happy to give
you general pointers off line. Otherwise we may be able to come to an
arrangement to get you underway asap.
 
Regards,
Tony Cusack
tony@xxxxxxxxxxxxxxxx
 
 
  _____  

From: austechwriter-bounce@xxxxxxxxxxxxx
[mailto:austechwriter-bounce@xxxxxxxxxxxxx] On Behalf Of Nikki Ward
Sent: Thursday, 13 July 2006 3:25 PM
To: austechwriter@xxxxxxxxxxxxx
Subject: atw: XML and Word





Melanie and Chris, 
 
Wow!.. thanks for your responses. 
 
Basically I started out with experimenting with VBA for Word (know this area
quite well) 
and it grew into toying with XML "for fun" as I got a little bored and XML
beckoned me with its promise of 're-use of data'
Yes I hear you tsk-tsk-ing Melanie :) - i actually do have a life ... I
think... 
 
I currently use AuthorIT at my current place of employment but in about a
weeks time I move into a 
smaller environment where no documentation or systems have been set up.  
 
My immediate brief is to automate document production without moving to a
CMS for the short term 
For the long term, however a CMS for Online, Print and Web output will be
considered once we have gone through the 
'design' phase of assessing what documentation is required and what is most
critical, and what outputs we need ie .chm, .doc, .xml, .html. 
 
What I am most interested in doing is
 
1) Using a template setup from the outset that will move cross-platform
without too much 
reformatting etc when it comes time to import into the CMS. 

2) Finding a way to re-use text and single-sourcing via XML if I can.. still
not 100% that I can do this without the need for enlisting the 
heavyweight AuthorIT programmers... :)
 
so thar ye go!
 
Nikki

Other related posts: