Re: [Phpwebsite-developers] Build Proceedure for the XML Manual Files

[Greg M. <drk...@co...>]

Mike Noyes wrote:
> On Sat, 2004-03-13 at 07:14, Greg Morgan wrote:
> 
>>Is there a document that explains how the xml build is setup?  I was 
>>fooling around with the manual .xml files and could not get them to 
>>build the same way that they are in phpwebsiteroot/manual directory.
> 
> 
> Greg,
> Building the DocBook manual should be fairly straight forward, provided
> your environment is setup properly. You'll need the proper entities
> also. Let me know if you need help.
> 
> manual.xml
> http://res1.stddev.appstate.edu/horde/chora/cvs.php/phpwebsite/manual
> 
Good.  It looks like no one has worked on these files for eight months.

Here's what I have done so far 
http://kissalice.sourceforge.net/phpmanual/output/set1.html.  It has all 
my rough ideas in rough rough form.  I cleaned up the CVS section today. 
  I have added an "Installation, Upgrade, and Maintenance" and fleshed 
out the "Developer's Guide".  Essentially, I have cobble many of my 
phpWS forum responses together.  I've started to manipulate them into a 
manual.  I think Ray O. on the LEAF list said that's one way to help. 
Watch what is happening in the mailing lists/forums and try and solve 
those problems. LOL, I've created a few of my own with docbook.

In the http://kissalice.sourceforge.net/phpmanual/ directory are two 
files.  00readme.txt explains what I had to do to get this working on 
Redhat's fedora core 1.  That file says, "
jw -f docbook -b html -o output manual.xml

docbook2html manual.xml

While working on this book, I had to change all instances of
"http://docbook.org/xml/4.2/docbookx.dtd" to
"/usr/share/sgml/docbook/sgml-dtd-4.2-1.0-22.1/docbook.dtd"
on Fedora Core 1."

The jw with -o to output placed all the html files in the output 
directory.  makemanual.sh is the jw command in a shell script.

I don't understand why the official manuals look like this
...
bk01ch01.html     bk01ch06s06.html  bk02ch04s04.html  bk02ch08s06.html
bk01ch01s02.html  bk01ch06s07.html  bk02ch04s05.html  bk02ch08s07.html
bk01ch01s03.html  bk01ch06s08.html  bk02ch04s06.html  bk02ch08s08.html
...
when mine look like this
...
book1977.html  c2150.html  x1048.html  x2015.html  x2154.html  x252.html
book1.html     c2152.html  x1051.html  x2016.html  x2155.html  x312.html
book2006.html  c2155.html  x107.html   x2019.html  x2156.html  x35.html
...

I believe the main problem I have is on this example page, 
http://kissalice.sourceforge.net/phpmanual/output/x2223.html.  See all 
the '>'s.  Those are supposed to be graphics.  I receive this error when 
executing jade i.e. jw, 
"jade:/home/edrive/phpwebsite/phpwebsite932/manual/xml/core/developer/themedevel.xml:151:42:E: 
character data is not allowed here".  Google did not point me to 
anything outstanding.  Moreover, I copied this stanza from the user guide,
     <screenshot>
       <graphic fileref="images/winxp.png"/>
     </screenshot>
These three lines are lines 150-152 in the above error message.  I don't 
have a clue.  Right now I am happy to massage the text into something 
meaningful.

The module you and I talked about on IRC and email is at the beginning 
of the developer tutorial.  Can I quote our session as an example of how 
the item class is discovered?

Oh! I tried searching for the xml editor you and Lynn talked about on 
the LEAF developer's list.  However, I was fruitless.  Do you have have 
the URL for that editor?

After reading this article, http://www106.pair.com/rhp/hacking.html, I 
thought I should post what I've done with the documentation.  One the 
one hand, I wanted to be able to "show the code" while on the other hand 
I wanted to make sure that I start coordinating with others.  If this is 
  acceptable work, then I would like to merge it with the official 
documentation.  I'd rather work in the community than go off and be the 
lone cowboy and have yet another place for the users to look for 
information.

Any solutions and feedback would be appreciated.

Regards,
Greg Morgan