I'm thinking a different tree might be a good idea too.
Rick
On Thu, Aug 9, 2012 at 4:05 PM, David Ashley <w.david.ash...@gmail.com>wrote:
> At this point I was just beginning to think about a plan :-)
> The sandbox was just so you could see how it all was structured and give
> you something to play with.
>
> Honestly I am not sure where we stand with the docs at this moment. I
> know that you are doing some stuff with the ooDialog guide but that is
> all I am aware of.
>
> My preference would be to create a whole tree for the docs since the
> structure is different. Then merge it back into the trunk when we finish
> the migration. And we should target it for the 4.2 release, that way we
> have some time to get it right.
>
> David Ashley
>
> On Thu, 2012-08-09 at 12:49 -0700, Mark Miesfeld wrote:
> > David,
> >
> > Sounds pretty good.
> >
> > What is your plan for the migration? Convert all the docs in your
> > sandbox and when they are all converted, move or merge the sandbox
> > back to the docs directory?
> >
> > Or maybe, leave the docs directory and copy the sandbox directory to a
> > new top level directory and do all new work in that directory? Leave
> > the docs directory alone, just don't put new work in it?
> >
> > Or ?
> >
> > --
> > Mark Miesfeld
> >
> > On Thu, Aug 9, 2012 at 12:21 PM, David Ashley <w.david.ash...@gmail.com>
> wrote:
> > > All -
> > >
> > > I have commited my Publican sandbox to SVN. You can check it out at
> > > http:..
> oorexx.svn.sourceforge.net/svnroot/oorexx/sandbox/david/publican.
> > >
> > > Here are some notes about Publican and the sandbox source.
> > >
> > > 1. Publican uses a "brand" concept to give a project a customized look
> > > and feel for their documentation. Our brand is contained in the oorexx
> > > subdirectory. This brand must be built and then installed on the build
> > > machine. There is a Makefile in the oorexx directory and all you need
> to
> > > do is run "make brand" and then run "make install". The "make install"
> > > assumes you have sudo authority to write to the target install
> directory
> > > (/usr/share/publican on Linux systems).
> > >
> > > 2. The rxsock subdirectory contains everything needed for the rxsock
> > > documentation. It was built using the "publican create" command and
> then
> > > customized. When ou create a new document you really only need to copy
> > > the directory structure of another document and then customize it.
> > >
> > > 3. To build rxsock just run "make pdf" or "make html" from the rxsock
> > > directory (rxsock has to be your current directory). This will create a
> > > new directory called tmp. You will find your output in either
> > > tmp/en-US/pdf or tmp/en-US/html. If files can not be found then you
> > > probably forgot to install the brand. See step 2.
> > >
> > > 4. A documentation build causes the brand files and the document files
> > > to be merged in the document's tmp directory. First the brand files are
> > > copied and then the document files are copied to this location. This
> > > allows the document files to override the brand files so that a
> document
> > > can vary from the brand if necessary.
> > >
> > > 5. There are some special files that need attention for each release
> > > cycle. The one you have to touch is the entities file. For rxsock this
> > > is located in rxsock/en-US/rxsock.ent. Every document will have one of
> > > these entities file with its own name but always with the .ent
> > > extension. The entities file has a version variable that needs to be
> > > updated for each release of the documentation.
> > >
> > > I know I have probably forgotten some things but this should get you
> > > started. The main Publican web page is at
> > > https://fedorahosted.org/publican/. There is a link to the user's
> guide
> > > on that page. I was able to figure everything out from that guide.
> > >
> > > Do not hesitate to drop me an email if you run into problems.
> > >
> > > David Ashley
> > >
> > >
> > >
> ------------------------------------------------------------------------------
> > > Live Security Virtual Conference
> > > Exclusive live event will cover all the ways today's security and
> > > threat landscape has changed and how IT managers can respond.
> Discussions
> > > will include endpoint security, mobile security and the latest in
> malware
> > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > > _______________________________________________
> > > Oorexx-devel mailing list
> > > Oorexx-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> >
> >
> ------------------------------------------------------------------------------
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> > _______________________________________________
> > Oorexx-devel mailing list
> > Oorexx-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Oorexx-devel mailing list
> Oorexx-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
