Subject: Re: DocBook and Jade for Literate Programming From: "James H. Cloos Jr." <cloos@xxxxxxxxxxx> Date: 03 Nov 1998 21:07:22 -0600 |
>>>>> "MW" == Mark Wroth <MARK.WROTH@xxxxxxxxxxx> writes: MW> Have you looked at W. Eliot Kimber's "Using SGML Architectures and MW> DSSSL to Do Literate Programming" MW> (http://www.sil.org/sgml/kimberDSSSLLitProg.html)? [etc] MW> I also note C. M. Sperberg-McQueen's "SWEB: an SGML Tag Set for MW> Literate Programming" MW> (http://www.uic.edu/~cmsmcq/tech/sweb/sweb.html), which appears to MW> be even closer to what you are aiming at, ... I knew *someone* had to have spent some effort already on this. From the first site I eventually ended up at `Literate Programming with SGML and XML' <http://www.oasis-open.org/cover/xmlLitProg.html>, refered from `The SGML/XML Web Page -- Extensible Markup Language (XML)' <http://www.oasis-open.org/cover/xml.html>. How I missed that one on my first search I'll never know ... :( MW> ... with this model, how would you handle a code "scrap" which MW> is included in several output files? Sweb is very close to what I was thinking, but is better thought/ fleshed out than my initial concept. JHC> Also, all whitespace after the CODE tag and before the /CODE tag JHC> would be ignored during extraction. MW> Consider this one carefully before you make it the only approach MW> you support; some potential output languages consider whitespace MW> significant (e.g. makefiles). Point taken. I guess I was thinking more like ignoring [ \t]*[\n\r]+ than ignoring [ \t\n\r]* and munged the translation to prose. :) MW> I'd be happy to discuss this general topic with you further, but MW> we may be going astray from the DSSSList's topics (or maybe not, MW> since some of the significant issues is how to process the MW> resulting marked up text, and what markup to use in the MW> documentation parts -- while a new markup could certainly be MW> defined, it may make sense to use an existing one). Yes, the concept of using DSSSL (Jade in specific) for both weaving and tangling was the motivation for crossposting here. That said, the <xml-litprog-l@xxxxxxxxxxx> list may be the better place for discussion, as I would prefer to use XML over SGML: the ability to publish the doc by just uploading the XML file to a web server is appealing. (Of course that will only work after the next round of browsers is released, but ....) -JimC -- James H. Cloos, Jr. <http://www.jhcloos.com/cloos/pgp_public_key.txt> <cloos@xxxxxxxxxxx> E9E9 F828 61A4 6EA9 0F2B 63E7 997A 9F17 ED7D AEA6 DSSSList info and archive: http://www.mulberrytech.com/dsssl/dssslist
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
RE: DocBook and Jade for Literate P, W. Eliot Kimber | Thread | DocBook stylesheets version 1.22, Norman Walsh |
How to Build a Typesetter, Jack Fitzpatrick | Date | Re: DocBook and Jade for Literate P, Wroth, Mark |
Month |