Jürgen,
Jürgen Schmidt wrote:
We also thought about a transformation into the wiki but it is not yet
clear how we can extract the relevant info from the wiki to prepare a
usable guide (e.g. PDF) as we can it currently. Although a wiki would
have some advantages we currently prefer a different format.
I am all for the wiki approach. The wiki allows to split the content
according to the projects. It scales, is designed to be very simple to
use as well as it is offering a place for discussion. On the other hand,
I am certainly no expert in professional writing at all.
Maybe you have some further ideas what would be the best way to maintain
and work with such a huge document. Splitting in smaller parts is
already planned ;-) (DevGuide 1-5 or something like that) But that
wouldn't change the problem because even the split parts of the guide
are parts of one big project.
The pure size is IMHO the biggest problem, I suggest to split it into
pieces according to the established OOo projects. This is the only way I
can think of, to get it scaling.
Juergen
Kay
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
