Ha! I was working on a completely automated script to produce a CHM
file, just like the ones I use from the PHP dox.

Is there an XML source for the files or are they manually maintained as HTML?

I would STRONGLY recommend storing the dox in an XML format and then
using a conversion process to produce HTML (static or dynamic is
server can support it)/CHM/PDF/ThoutReader (http://www.osoft.com).

Converting the XML to HTML can be done via XSLT easily enough. If the
pages are held in DOCBOOK format this would be common with PHP dox.

If there are any XSL experts out there (I'm not sorry), then
http://cvs.php.net/phpdoc contains all the PHP documentation and build
system (build system for web, html download, chm download - 2 variants
with and without advanced styling/skinning capability), etc. The raw
XML files are in the process of being converted to DOCBOOK and I
believe most are already done.

All the syntax highlighting for PHP is done within the XSLT and is fine.

If anyone IS XSL expert and would like to see how the PHP build
process works, then I can talk you through the installation process
and build process easily enough (requires Cygwin if you are on
Windows, otherwise I believe *ix has all the bits and pieces already
in place, but you would need to check - for Windows, Cygwin contains
everything you would need).

Other than that, Kjell has done a great job. I didn't know there was
one already available.

I am in the process of building a process to construct my own CHM file
(as I want to be able to add it to my own CHM dox -
PHP/HTML/SQL/JS/CSS and now Prototype).

I'm on Windows and use Teleport Pro to grab the entire site which also
makes the entire site localhost only - no web files. From there
stripping out Google/meta/scripts, etc. and then build index and
finally construct CHM project file. Still a WIP, but fully automated.


Richard Quadling.

On 10/03/07, Kjell Bublitz <[EMAIL PROTECTED]> wrote:
> I would agree, but i was unable to find feeds for the subpages eg,
> ajax/options/atom.xml or ajax_options/atom.xml .. all lead to 404. But
> even if you have atoms for all pages (IIRC you do) then things like
> HTML tables would still mess up the layout. I would have to rework the
> whole file after this operation.
> Anyways.. It is good as it is right now. The initial creation was hard
> but updating is rather easy now, so switching now from manual to
> auto-creation is not an option for me anymore.
> By the way.. i tried the auto-discovered feed and it is the feed from
> the blog. You might want change that to the feed-adress for the
> api-page or place a link to it somewhere.
> On 3/10/07, Mislav Marohnić <[EMAIL PROTECTED]> wrote:
> > On 3/10/07, Kjell Bublitz <[EMAIL PROTECTED]> wrote:
> > > Yes, i copied page by page and added custom syntax highlightinh etc..
> > > Doing this automaticly is not a good idea. I tried it the day after
> > > the docs were put online but it was a mess. Too much different markup,
> > > crosslinks, etc..
> >
> > I don't agree that it would be a mess. Write a script that pulls down the
> > XML files, eg.:
> > http://prototypejs.org/feed/api/ajax/atom.xml
> >
> > Then the same script should split the entries into HTML files and rewrite
> > the crosslinking. But, suit yourself.
> >
> >
> >  >
> >
> --
> Regards, Kjell
> www.m3nt0r.de
> >

Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"

You received this message because you are subscribed to the Google Groups 
"Prototype: Core" group.
To post to this group, send email to prototype-core@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 

Reply via email to