discuss: db2omf
Subject:
Re: db2omf
From:
David Merrill ####@####.####
Date:
8 Mar 2001 20:12:54 -0000
Message-Id: <20010308151147.A22621@lupercalia.net>
On Thu, Mar 08, 2001 at 02:00:55PM -0600, Kristin E Thomas wrote:
> > If this is just a matter of "make sure these tags are filled out", let
> > me know what the tags in question are, and I'll put it in the style
> > section.
>
> >Good point. It really is a matter of "make sure these tags are filled
> >out". An author shouldn't *need* to know anything beyond that.
>
> >I guess you can argue this point either way. I do want to see it
> >documented, but we can discuss whether it goes into the LAG or whether
> >it is just included with the scripts as *their* documentation as a
> >separate issue.
>
> I want to make sure I understand the result of this afternoon's discussion
> before I go duplicates someone else's work. The information about OMF (if
> any) will not go in the "Encoding Indexes" section of the LAG.
>
> What does this leave me adding to that section? It sounds like there might
> be some interest in including something about ScrollKeeper. Just wanted to
> make sure before I proceed.
I think we've established that the details of omf implementation don't
belong in the author document, but we want them documented somewhere.
Scrollkeeper is likewise not an author concern but should be
documented somewhere.
Whoever feels like attacking the documentation of db2omf, go ahead but
let us know you're doing it. It *will* go somewhere, but not in the
LAG. Once we have that db2omf documentation, we will make sure our db
recommendations in the LAG will have authors using the db properly to
support omf, but without specific omf references being necessary.
I think this covers all the concerns that have been expressed. We will
have omf-compliant docbook, but without adding complexity for authors
because they won't need to know omf, just follow the db recommended
usage.
btw, I wrote to the sk group and they are interested in our doing a
db2omf script. They are planning to automatically generate omf upon
document installation, so it looks like we won't have to generate it
ourselves to have our documents included in sk. Still, since we have a
volunteer already to do it, let's go ahead and do it. Our mission
includes collaboration with other groups, and this is a good way to
help them out.
--
Dr. David C. Merrill http://www.lupercalia.net
Linux Documentation Project ####@####.####
Collection Editor & Coordinator http://www.linuxdoc.org
Finger me for my public key
In English, every word can be verbed. Would that it were so in our
programming languages.
