Hi, I talked a few months back about a book, but it never seemed to get any traction. I'm big on Xml / Xsl, and am very willing to lend myself to a project like this.
With Python you want the gnome / libxml2 & libxslt python bindings. They are fantastic. I also recommend using the Gentoo stylesheets. I've been working with them for a year now, and have found them to be lighter / easier to write to than DocBook. A recommendation is ... don't worry about the style, just come up with the content. Let people who know the xml / xsl stuff worry about xml'izing the stuff. At least for the first go round. Actually an even better way might be to get one or two people that know Xml / Xsl and the stylesheets in question, and take the existing docs, and transfer them over to the requisite Xml. That way those that wish to work on the docs, have a base to start from, as well as a live reference to see how the xml document works. I gladly volunteer to take any of the existing docs and start that off. If anybody else wants to join please let me know so we don't duplicate the work. I'd like to get started tonight, and just whack some of the short ( easy ) stuff out. Thanks Ray contact me at on : Microsoft Messenger ( rayleyva ) On Thu, 24 Oct 2002 12:13:19 -0400 Michael Engelhart <[EMAIL PROTECTED]> wrote: > Hi - > > I'm new to this list and while I just barely have scratched the surface > of Webware (and python for that matter), I would be glad to take files > in XML format and generate the HTML documentation using XSLT. > Unfortunately I've had a lot of problems generating output with the > Python XSL processors (partially due to my newbie python status) but I > could easily do it using Java which I've been doing for other projects > for the past couple of years.g. I would just need the XML and the > general look and feel that everyone would like the output in. > > > Mike > > On Thursday, October 24, 2002, at 11:58 AM, Aaron Held wrote: > > > Personally I find that I can write the fastest when I write in XML > > because I do not have to think at all about the layout. > > > > But the fundamental problem is the content. I would not mind compiling > > a list somewhere of what docs we need. I would reccomend that we all > > work towards a single book. Collaborate on the table of contents and > > then individually write whatever section you can. > > > > ------------------------------------------------------- > This sf.net email is sponsored by: Influence the future > of Java(TM) technology. Join the Java Community > Process(SM) (JCP(SM)) program now. > http://ad.doubleclick.net/clk;4729346;7592162;s?http://www.sun.com/javavote > _______________________________________________ > Webware-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/webware-devel ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0003en _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
