[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Ozone Doc Project

> Hi All,
> Was wondering how people felt about having an install for the docs.
I think it works fine the way it is now.


> I'm not an ANT expert but here is my idea.
>
> 1. Zip up the contents of the style sheet as they change often.
Wouldn't this mean a lot of work when a change is made (the zip file has to
be updated every time a change is made)?
> 2. Zip up the contents of the docbook dtd.
> 3. Include both of these in CVS.
>
> Create a target to use the jar task to unzip these either as a separate
> target or as part of a depends. If the target removes the zip file after
> uncompressing we could have a little installed target that looks for the
> zips and recommends to do the install if it is not installed yet.
>
> Is this a good idea?
Maybe. What is the problem you like to solve by doing this?

>
> What is the cvs command to ci binary files? cvs -kb add?
yes, cvs add -kb <filename>

>
> I'm still working on the Doc How to.

I am too :) Lets sync our different suggestions. I just put what i did in
CVS src/howto/ozone-documentation-howto.xml and also a licence text as
src/howto/ozone-documentation-licence.xml. I saw some problems that i tried
to solve in this suggestion. As far as i can tell there is no legal body
that holds Ozone copyright other than SMB so I put SMB as the copyright
holder for the document and propose we do the same for everything else
coming, that is if SMB agrees ;) Another possibility would be to use the GNU
documentation licence. As you'll see this is a very rough and thin draft but
i hope we can merge our versions and maybe spawn off some good discussion in
the process :)


> One other thing. Do we want to add one target for each document?
> Somebody who has more ant experience may want to look at this. There is
> a call task that could be used. The added target would just set some
> variables for the in and out file and then call the target that does the
> transform. I wanted to use the pattern task but couldn't get it to work.

I was thinking the same. The build would go through all XML files under src
and process them with same style sheet using the patters of whatever.xml
into whatever.html and whatever.pdf but i could not find a good way to
traverse unspecified subdirectories. Take a look at build.xml in
ozone-modules/ozoneXML - maybe you find some useful ideas there?

Best regards,
Per