On Sun, 2011-07-03 at 16:08 -0700, Dave Fisher wrote:
> On Jul 3, 2011, at 2:14 PM, Jean Weber wrote:
> 
> > On Mon, Jul 4, 2011 at 04:16, C <smau...@gmail.com> wrote:
> >> On Sun, Jul 3, 2011 at 18:53, Dave Fisher <dave2w...@comcast.net> wrote:
> >> 
> >> A few example items... the existing/legacy MediaWiki instance is using
> >> several creative tweaks such as (not an exhaustive list.. just a few):
> >> 
> >>  - PDF and ODT export.  Confluence can do PDF, but cannot do ODT..
> >> only MS Word DOC format (a significant issue in my view for an OOo Wiki...
> > 
> > Even worse, AFAICT Confluence cannot export more than one wiki page at
> > a time to MS Word DOC format, which would make compiling a whole book
> > in that format a lot more difficult.
> 
> It is very cumbersome, but it is possible to export all or part of a space to 
> PDF in Confluence - The function is found on the Advanced page.

PDFs exported from a wiki may be convenient for individuals wanting a
copy of info but not concerned about its appearance. They are not of an
acceptable quality for publishing as a book, particularly if they
contain images -- or at least I have never seen one that was acceptable,
by which I mean looking like a reasonably professional publication. 

We (people producing user guides) need to be able to get editable
documents that can be massaged into an acceptable form before exporting
to PDF. Indeed, that is one of the major reasons why we want the user
guides to be maintained in ODT, not wiki form.

> > 
> >> Export to PDF and ODT is something a lot of people use
> >> for the OOo Docs - especially the Basic and Developer's Guides.
> >> [...]
> >> 

Those are the books maintained on the wiki, with input from the
developers. They don't have many images. Getting a reasonable result
from the export is still challenging, but Clayton (and whoever else has
worked on this) has done a heroic job creating templates for export from
MediaWiki. 

--Jean

Reply via email to