Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of rabastus@gmail.com designates
 209.85.210.175 as permitted sender)
MIME-Version: 1.0
Sender: rabastus@gmail.com
In-Reply-To: <D3D07120-9E5A-43A2-A53F-34E5A0A5B30D@comcast.net>
References: 
 <CAP-ksohK2+nOPwZ1dC9PGev_wL6YinsQnR21pRjDOxEpOWYPmg@mail.gmail.com>
	<D3D07120-9E5A-43A2-A53F-34E5A0A5B30D@comcast.net>
Date: Wed, 6 Jul 2011 18:55:42 -0400
Message-ID: 
 <CAP-ksohQD2LggWtk9mo1qvVUi3E3BerdvuKCTPRtUP+BfF4bjA@mail.gmail.com>
Subject: Re: DITA for Doc?
From: Rob Weir <apache@robweir.com>
To: ooo-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 6, 2011 at 6:11 PM, Dave Fisher <dave2wave@comcast.net> wrote:
> Hi Rob,
>
> On Jul 6, 2011, at 2:10 PM, Rob Weir wrote:
>
>> =C2=A0we've already done the work
>> of converting much of the OOo help to DITA.
>
> Is there a software grant coming?
>

It is worth considering.  But I'm not going to face that corporate red
tape merely on speculation that this might be useful.  Let's first
discuss whether the DITA approach seems reasonable.  I think it is
important for content authors to be aware that this would be writing
documentation with tags, similar to HTML.  Good HTML.  But this
structure would give us loads of flexibility for how we structure the
content, combine it is different ways, and publish it.

You can get a flavor of DITA here:

http://www.xmlmind.com/tutorials/DITA/index.html

Tags are off-putting to some people who just want to work in a WYSIWYG
fashion, so I wanted to check.  One possible way of working is to
accept raw content in any reasonable format, ODF, DOC, HTML, yellow
crayon on a napkin, etc., and then have a manual cut & paste process
to get that into DITA initially, and then maintain it that way going
forward.

> Regards,
> Dave
>