On Friday 05 November 2010 08:21, David Nelson wrote:

> General question: since it's a wiki, doesn't it make more sense to
> have the docs in wiki format rather than ODT?

Which do you personally prefer?

Historcally, the question has been raised a couple of years ago in the 
ooo project. The answer was to use the format in which most people 
preferred to contribute (which seems pretty rational). Both 
possibilities were offered, but AFAIK the community has preferred ODT 
for writing User Guides by far, whereas Dev Documentation has been 
mainly produced in wiki form. 

> I may have missed a decision and a reasoning about this, because of
> the floods of threads there have been on the various lists over the
> past weeks, so could you please excuse me if so and be kind enough to
> briefly explain the adopted policies? Thanks if so...

I don't think that a formal decision has been made. Up to now, there is 
no official (or inofficial) team in charge of the doc project. So who 
should make a decision? Things are just evolving ;-)

But anyways - I think it would be a good decision to take ODT as master 
format for User Guides and Wiki as master for Developer documents. 
Conversion ODT -> Wiki and vice versa is possible but time consuming, 
so keeping both formats in sync does not seem a good option unless we 
have enough people taking the task.

With using drupal as CMS there could be a third option: to produce 
drupal master documents which then could be offered in web form and 
then transformed to ODT/PDF, but this possibility has to be implemented 
and tested still. This will take some months, I think. 

Nevertheless, for quick drafting, the wiki can always be used without 
problems.

> I plan to work through the posted material and do some proofreading.

Fine.  

Nino

-- 
E-mail to documentation+h...@libreoffice.org for instructions on how to 
unsubscribe
List archives are available at http://www.libreoffice.org/lists/documentation/
All messages you send to this list will be publicly archived and cannot be 
deleted

Reply via email to