Hi Mats, We use the Confluence Wiki to develop and review documents collaboratively. When we are ready we either directly generate the required outputs such as Word, PDF, CHM, HTML, EPUB etc. or generate DocBook to be used in an existing publishing tool chain (using the www.k15t.com tools).
David Cramer could maybe also share his thoughts on this approach. Cheers, Tobias On Thu, Jan 2, 2014 at 9:57 PM, Mats Wichmann <[email protected]> wrote: > > A little backstory here... > > I inherited a specification document that was written in MS-Word. > Although not my preferred format, existing institutional familiarity > meant I didn't initially have the option to change. However, when the > project evolved and it became clear I'd have to produce a half dozen or > more variants of the document, while maintaining large chunks of the > content as common text, I went ahead and did the conversion to docbook > to maintain some semblance of my sanity. > > The problem I now have is my existing internal "customers" are used to > reviewing with a wysiwyg tool (namely, Word) so they can markup and > comment inline. Turns out I haven't had luck generating stuff Word can > read directly, but it comes out at least acceptably if you feed it html. > However... it doesn't seem ideal to convert to another format for > reviewing, then have to "backport" things to the master. This might be a > case for the roundtripping stuff (dbk2wordml) but I can't get a usable > doc out of that at all. > > So... asking for advice. What do people typically do when it's time to > pass a document around to multiple reviewers? I'm not convinced > something like Word is the best answer even there (you end up having to > review serially, not in parallel, or you'll go nuts reconciling the > comments in multiple different docs, but it's certainly comfortably > familiar to folks whose companies run on MS-Office). Is there a "better > way" that ties in well with having sources in docbook? > > -- mats > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
