Per Eriksson wrote:
But is the wiki the right way to go? How often will different versions
I'm not sure but I would like to evaluate that. For some info types it will definitely be the right way to go (FAQs, Howtos, Application Help, all that modular stuff).
of the different manuals be published for download. How will formatting work be done? The wiki involvs excellent tools for discussion and a
A colleague of mine, Clayton, has experience in using a different wiki system (JSP Wiki) for maintaining manuals that are for production extracted from the wiki, converted, formatted, and output as PDF. The tool chain for all of this is available (needs to be put in place and adjusted, though).
really simplistic way of editing, but the content is actually too big for the system to handle. Versions tracking would be problematic, and
I agree that topic size may actually be an issue. If you split books by chapter, the individual chapters may get too big to handle via wiki. Maybe you need to get more granular.
references to different parts would, mean a lot of extra work between formats as this is not supported in the wiki?
References inside the wiki just work fine, I see no problem there. But I admit the chapter size could be an issue. Ultimately, there won't be a one-size-fits-all solution and we may need to look for different approaches for different info types. I would still like to find out what a wiki can handle beyond the "classical" wiki formats. Can you elaborate how a Pootle solution would look like? What would we need? Frank -- The OOo Documentation Project: SIGN UP - PARTICIPATE - CONTRIBUTE IT'S FREE! NO OBLIGATIONS! http://documentation.openoffice.org http://wiki.services.openoffice.org/wiki/Documentation --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
