Per wrote:

But is the wiki the right way to go?
How often will different versions of the different manuals be
published for download.

a) If WikiMedia is used, one can archive key pages for a specific
version of OOo.

For example:
* Stylist:
* Stylist_1.0
* Stylist_1.1
* Stylist_1.2
* Stylist_1.3
* Stylist_1.4
* Stylist_1.5
* Stylist_2.0.0
* Stylist_2.0.1
* Stylist_2.0.2
* Stylist_2.0.3
* Stylist_2.0.4
* Stylist_2.1
* Stylist_2.2
* Stylist_2.3

With the first page "Stylist" describing how to use the current
version of Stylist, and the other pages describing how to use Stylist
with the stated version.

My guess is that most of the feature_version_number pages will be redirects.

b) I've seen an addon for MediaWiki that allows the user to generate a
PDF that is then emailed to them.

How will formatting work be done? The wiki involves excellent tools for 
discussion and a
really simplistic way of editing, but the content is actually too big for the 
system to handle.

Break the content into chunks that can be handled by the wiki.

For example:  _OOo in a Multi-Linugal Environment_ as a single
document is 2500 pages long.   Break it down by target language, and
it is roughly 50 languages of 50 pages each.  Toss it onto a wiki, and
you have roughly 2000 pages of material that is heavily interlinked.

Versions tracking would be problematic

The history log of WikiMedia covers version tracking of the specific
page.  If your concern was OOo versions, that is solved by archiving
the page with the version number.

and references to different parts would, mean a lot of extra work
between formats as this is not supported in the wiki?

Wikimedia does not produce a decent table of contents, or similar
indexing structures.
A _good_ format translation program will convert the [[wikimedia
internal link]] markup to either a URL, or a document name.

xan

jonathon
--
OOo can not correct for incompetence in creating documents from MSO.
Furthermore,OOo can not compensate for the defective and flawed
security measures used by Microsoft. As such, before using this product
for exams that require faulty and defective software, ensure that you
will not be unjustly penalized for the incompetence of the organization
that requires the use of software that is known to be flawed,
defective, bug-ridden, and fails to meet ISO file format standards.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to