[TYPO3] Documentation nightmare

[virgil huston]

OK, this is a good discussion and we need to come up with a good way to
work. Personally, I do not like the wiki to actually work on docs, but only
to manage the docs. With the wiki, when things are edited, etc., afterwards
someone still has to put them into OOffice, format them, etc. This seems
like a waste of time. I would use the wiki to manage and organize and
discuss, but the actual manuals (or section being done by separate authors
if appropriate) should be written and edited in OOffice, as long as OO is
the standard. We need to go beyond OO, I think, I have clients where I have
to convert the docs to PDF for them, they will not usee OO. But OO as a
writing standard is fine.

Virgil

On Fri, Mar 14, 2008 at 5:58 PM, Dmitry Dulepov [typo3] <dmitry at typo3.org>
wrote:

> Hi!
>
> Peter Kindström wrote:
> > Well, _I_ dont think it matters if you use OO. The down side is that it
> > may be more difficult to cooperate. But then we have Google Docs?
> >
> > On the other hand you usually have to do the work yourself. ;-) And then
> > it would not be a problem at all working with OO or any other word
> > processor.
> >
> > The docTeam should (if not already done?) have tools for converting
> > different doc formats (say OO) to the preferred Typo3 doc format. Then
> > it does not matter what format/word processor you as a writer use, the
> > important thing is to get the job done!
> >
> > Oh, and I still think the wiki should be used only for work in
> > progress.  OO, DocBook or web pages should be used for final versions.
>
> Fully agree with all above!
>
> --
> Dmitry Dulepov
> TYPO3 core team
> Web: http://typo3bloke.net/
> Skype: callto:liels_bugs
> "Nothing is impossible. There are only limits to our knowledge"
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
>