[docbook-apps] Re: blogging using DocBook articles or so ...
Grant Taylor writes: On 07/18/10 08:43, Jochen Hayek wrote: Would be exciting to use DocBook also for that. I have considered (and am in fact putting together pieces in my head) using DocBook in combination with some other things for something similar. Currently I am planning on using DocBook, Make (files), SSI and possibly a few other shell level things to manage a website / blog (if you will) for my self. In short, I'm trying to use (what I consider to be) the best tool for the job. Grant. . . . Well, pls, keep meus updated! J. - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Re: blogging using DocBook articles or so ...
Dave Pawson writes: From the above, you can see that the html header from docbook is all redundant? Not from the above, but if I want to keep the article separate, then yes. I'm unsure what an atom feed reader would do with a link to docbook source in the body. Try it? Hmm, Dave, *come* *on*!! Pls! I mean, of course the link points to HTML content, not to literal DocBook content. Have a look at this feed e.g.: http://pragprog.com/feed/global Minimal content for each atom feed entry (or is it RSS?!?), just a pointer to the content, which is separate. By now I am also aware of Norm's Own Approach, pointed to by Maurith, see below! I assume, that's DocBook articles with the feed refering to the HTML content generated from DocBook. Whether it really is like that with Norm's Own Approach or not, I would like it like that, and that's where I would like to get. Separate articles, each written in DocBook, atom being the wrapper pointing to articles living for themselves, one by one. Hand craft a feed and see what bloglines or something does with it before you go further. HTH regards Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk Thanks for your patience and for your offer as well! J. MJ == Mauritz Jeanson m...@johanneberg.com writes: MJ Norman Walsh writes his blog in (a customization of) DocBook: MJ http://norman.walsh.name/ MJ Here is an old (obsolete?) article describing the machinery: MJ http://norman.walsh.name/2003/05/14/how MJ Mauritz - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Re: blogging using DocBook articles or so ...
MJ == Mauritz Jeanson m...@johanneberg.com writes: MJ Norman Walsh writes his blog in (a customization of) DocBook: MJ http://norman.walsh.name/ MJ Here is an old (obsolete?) article describing the machinery: MJ http://norman.walsh.name/2003/05/14/how MJ Mauritz I really like this approach. But it needs a web server of your own, if I understand Norm's explanations correctly. Alright, I have been on my way to my own Linux in the Cloud for a while anyway! Once that's sorted, I think, this is my route! Thanks for the pointer! J. - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Re: blogging using DocBook articles or so ...
Remko Tronçon writes: … maybe there has already been an attempt to use DocBook for blogging? FWIW, I created a stylesheet for integrating DocBook documents with the WordPress blogging platform: http://el-tramo.be/blog/integrating-docbook-with-wordpress I downloaded your docbook-kit-master.zip, and I like especially its size, I mean how small it seems to be. small is beautiful in that respect. But just like Norm's Own Approach you need an entire web-server and so forth for yourself. I would still love to run a script over all (DocBook) articles located on my disk in one directory or so, let it assume, there is already HTML generated and uploaded for all of them, create RSS resp. ATOM, upload that to a public place. As simple as that. Unreasonable? Undoable? I don't really use it for blogging, though, only for integrating my DocBook articles in my webpage. Moving from dynamic blogs to 'static' blogs has gained some popularity recently, with projects like Jekyll being used a lot. These projects use Textile, Markdown, etc. wiki-like syntax as input formats, but DocBook would work as well. So my approach isn't really to insane, I understand ;-) cheers, Remko - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Re: blogging using DocBook articles or so ...
On 07/21/10 06:49, Jochen Hayek wrote: Well, pls, keep meus updated! Will do. Currently I have all the individual pieces except for the glue around make. I have no doubt that I can write a Makefile to kick off some actions the way that I want to. The thing that I haven't sat down to finalize is how I want things inter-linked. (I'm not talking about olinking either.) I'm thinking that I want each document / article in its own (sub)directory and that the parent directory's index page (most likely manually edited, but could be automatic if desired) will link (not exactly sure how, olink, include, other?) in to the (sub)directories and include the child document titles and descriptions in to the index. I'm planing on the linking being a manual process so that I can add other content around the links and control the order of appearances as well as what does and does not appear. I'm also hoping to make extensive use of titles and descriptions for such things as generating RSS / Atom feeds, sending notifications to email (lists) / newsgroups, etc. I am going to completely separate layout / appearance from the raw content and output SSI directives from DocBook that are then interpreted by Apache to bring in my site layout and every thing associated there with. - One of the things that I've not nailed down here is how to inject (if you will) the page title in the middle of what is included via SSI. I don't know if I will ultimately do a couple of includes, or set an SSI variable that is then used by what is included. I'm also considering using AJAX to bring in the navigation menu so that I can have a simple static page that will dynamically be updated (on page load) when new content is added to the section / site. One of my secondary / tertiary goals is to have the generated content be as cache friendly as possible as well as being accessible / section 508 friendly. Like I say, lots of little pieces that need to be assembled to find the missing holes. Once I have the missing holes, I'll start plugging them. If any one cares to talk more details about what's in my head, it would probably be best to move this discussion off list. That being said, drop me an email. Grant. . . . - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Re: blogging using DocBook articles or so ...
On Sun, 18 Jul 2010 19:44:13 +0200 jochen+oasis-o...@hayek.name wrote: The wrapper is atom, not docbook, which I publish directly. ure. A standard. Fine. Isn't that OPML-related? Rings a bell somehow. http://www.ietf.org/rfc/rfc4287.txt But usually (I thought at least) the wrapper (i.e. the feed) does not contain the entire articles, but it only refers to the content. But at least some feed providers restrict it to that, as far as I can say. Not in my experience. But maybe I got something fundamentally wrong. Go find some rss or atom feeds and have a look at the structure. From the above, you can see that the html header from docbook is all redundant? Not from the above, but if I want to keep the article separate, then yes. I'm unsure what an atom feed reader would do with a link to docbook source in the body. Try it? Separate articles, each written in DocBook, atom being the wrapper pointing to articles living for themselves, one by one. Hand craft a feed and see what bloglines or something does with it before you go further. HTH -- regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Re: blogging using DocBook articles or so ...
Robert Lucente writes: We have to be very conscious of who is the intended audiance. Warning pontification: You can't be everything to everybody. Creating DocBook XML and then getting the processing chain to work to convert XML to HTML and then screwing around to get something to look exactly the way you want it to in order to create a blog seems like way overkill. My standards a lower there. Aesthetics are important but not prio 1. And IMHO DocBook output *is* nice. And you do know, that O'Reilly books (all/some/a few?!?) are written in DocBook nowadays, don't you? Maybe bloggingsharing would get far more often done, if the means were easier. My current experience is DocBook Website, which glues separate documents together using a layout.xml, which serves quite a few different purposes including customization. I would even regard it as acceptable to maintain something like the source of the RSS/atom feeds, which could be the corresponding thing to that layout.xml. If something is not long or if the aesthetics are very critical, perhaps DocBook is not the tool ? I am not trying to start a flame war, just trying to look at things from everybody's perspective. Fair enough. Thanks for your contribution. I just wanted to ask around and maybe suggest and idea. Sometimes it take a spark, you know, in order to start projects, tiny ones and big ones. Just my $0.05. - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
RE: [docbook-apps] Re: blogging using DocBook articles or so ...
And IMHO DocBook output *is* nice. Ooops. Did not mean to imply otherwise. O'Reilly books (all/some/a few?!?) are written in DocBook Yes, I am aware. Please note that O'Reilly focuses on the tech market. Maybe blogging sharing would get far more often done, if the means were easier. Please name the one specific thing that you would like to be easier. glues separate documents together I am confused. If we are talking about a simple blogg, why are we talking about glueing documents together ? Please note that I am a newbie and trying to figure out where the various tool sets fit in. So, if I am making silly comments or asking silly questions, request your patience. -Original Message- From: jochen+oasis-o...@hayek.name [mailto:jochen+oasis-o...@hayek.name] Sent: Sunday, July 18, 2010 10:16 AM To: docbook-apps@lists.oasis-open.org Subject: [docbook-apps] Re: blogging using DocBook articles or so ... Robert Lucente writes: We have to be very conscious of who is the intended audiance. Warning pontification: You can't be everything to everybody. Creating DocBook XML and then getting the processing chain to work to convert XML to HTML and then screwing around to get something to look exactly the way you want it to in order to create a blog seems like way overkill. My standards a lower there. Aesthetics are important but not prio 1. And IMHO DocBook output *is* nice. And you do know, that O'Reilly books (all/some/a few?!?) are written in DocBook nowadays, don't you? Maybe bloggingsharing would get far more often done, if the means were easier. My current experience is DocBook Website, which glues separate documents together using a layout.xml, which serves quite a few different purposes including customization. I would even regard it as acceptable to maintain something like the source of the RSS/atom feeds, which could be the corresponding thing to that layout.xml. If something is not long or if the aesthetics are very critical, perhaps DocBook is not the tool ? I am not trying to start a flame war, just trying to look at things from everybody's perspective. Fair enough. Thanks for your contribution. I just wanted to ask around and maybe suggest and idea. Sometimes it take a spark, you know, in order to start projects, tiny ones and big ones. Just my $0.05. - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Re: blogging using DocBook articles or so ...
Robert Lucente writes: And IMHO DocBook output *is* nice. Ooops. Did not mean to imply otherwise. O'Reilly books (all/some/a few?!?) are written in DocBook Yes, I am aware. Please note that O'Reilly focuses on the tech market. That's O'Reilly, not necessarily you and me. *** THIS IS NOT A FLAME, HONEST *** What makes DocBook unsuited for others than the tech market? Is is it the same with LaTex? Because you can write math. formulas with it, you can't write prose with it? Alright… people writing prose might not want to get bothered with something as profane as XML tags resp. LaTeX markup? I used to use troff Memorandum Macros, and not just for the job. Do you think the addressees bothered, whether my letters were written in that incredible markup language? Maybe blogging sharing would get far more often done, if the means were easier. Please name the one specific thing that you would like to be easier. I hate to edit text outside the emacs universe. I hate it to edit text in a web browser. I hate it to not be able to use Control-S to save my text every couple of seconds, w/o even being really aware, that I have done it again. Too much hatred, I know. Again: this is not a flame. I am just not a WYSIWYG guy. Yes, occasionally I like using formatted e-mail in Google Mail, yes, it is a serious temptation. Yes, I am Google Buzzing a lot. But there again: I use old-fashioned markup there, too. I prefer focussing on content, and *marking* *up* my text, yes with some kind of eagerness for perfection. Your mileage may vary, they say. With your preferred editor – do you actually type the end tag or does your editor achieve that for you? My editor does it for me, so I don't bother. I think end tags do help. But than I am also one of the guys out there (with Ada being my 5th programming language or so), who loves end if, end case, and that sort of stuff, and with perl and ruby and whatever I add it myself as a comment. glues separate documents together I am confused. If we are talking about a simple blogg, why are we talking about glueing documents together ? To keep things simple, one approach may be to regard every blog article a document of its own. Alright? But if the blog is sort of DocBook Blog, then what keeps the articles together? I assume you are familiar with blog subscription features, like adding the blog's RSS resp. atom feed to your preferred feed reader. What creates the RSS resp. atom feed in the case of DocBook Blog? Well in the case of DocBook Website there is a meta-document called layout.xml, which is not really DocBookish but (at least) XML with a defined DTD/schema. Maybe there will be sort of layout.xml for DocBook Blog as well. I am sorry, you must be bored by this, as I keep reusing my own words. Please note that I am a newbie and trying to figure out where the various tool sets fit in. So, if I am making silly comments or asking silly questions, request your patience. If I am not patient enough: pls forgive me! And see: I am still here :-) Maybe DocBook Blog is serious enough for a student's thesis an whatever level. No idea. Just suggesting… Another approach may well be to regard the entire blog as a book, with the articles being sections of level 1. But then: as the blog grows article by article the generation process for the whole will more and more degrade. And I just thought, that's not a good idea. And why start there, if we know that from the very beginning. Just my $0.05. Sic. - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
RE: [docbook-apps] Re: blogging using DocBook articles or so ...
I think that the various perspectives have been adequately presented and each user must decide for themselves what is the appropriate tool to use. -Original Message- From: jochen+oasis-o...@hayek.name [mailto:jochen+oasis-o...@hayek.name] Sent: Sunday, July 18, 2010 11:51 AM To: docbook-apps@lists.oasis-open.org Subject: [docbook-apps] Re: blogging using DocBook articles or so ... Robert Lucente writes: And IMHO DocBook output *is* nice. Ooops. Did not mean to imply otherwise. O'Reilly books (all/some/a few?!?) are written in DocBook Yes, I am aware. Please note that O'Reilly focuses on the tech market. That's O'Reilly, not necessarily you and me. *** THIS IS NOT A FLAME, HONEST *** What makes DocBook unsuited for others than the tech market? Is is it the same with LaTex? Because you can write math. formulas with it, you can't write prose with it? Alright… people writing prose might not want to get bothered with something as profane as XML tags resp. LaTeX markup? I used to use troff Memorandum Macros, and not just for the job. Do you think the addressees bothered, whether my letters were written in that incredible markup language? Maybe blogging sharing would get far more often done, if the means were easier. Please name the one specific thing that you would like to be easier. I hate to edit text outside the emacs universe. I hate it to edit text in a web browser. I hate it to not be able to use Control-S to save my text every couple of seconds, w/o even being really aware, that I have done it again. Too much hatred, I know. Again: this is not a flame. I am just not a WYSIWYG guy. Yes, occasionally I like using formatted e-mail in Google Mail, yes, it is a serious temptation. Yes, I am Google Buzzing a lot. But there again: I use old-fashioned markup there, too. I prefer focussing on content, and *marking* *up* my text, yes with some kind of eagerness for perfection. Your mileage may vary, they say. With your preferred editor – do you actually type the end tag or does your editor achieve that for you? My editor does it for me, so I don't bother. I think end tags do help. But than I am also one of the guys out there (with Ada being my 5th programming language or so), who loves end if, end case, and that sort of stuff, and with perl and ruby and whatever I add it myself as a comment. glues separate documents together I am confused. If we are talking about a simple blogg, why are we talking about glueing documents together ? To keep things simple, one approach may be to regard every blog article a document of its own. Alright? But if the blog is sort of DocBook Blog, then what keeps the articles together? I assume you are familiar with blog subscription features, like adding the blog's RSS resp. atom feed to your preferred feed reader. What creates the RSS resp. atom feed in the case of DocBook Blog? Well in the case of DocBook Website there is a meta-document called layout.xml, which is not really DocBookish but (at least) XML with a defined DTD/schema. Maybe there will be sort of layout.xml for DocBook Blog as well. I am sorry, you must be bored by this, as I keep reusing my own words. Please note that I am a newbie and trying to figure out where the various tool sets fit in. So, if I am making silly comments or asking silly questions, request your patience. If I am not patient enough: pls forgive me! And see: I am still here :-) Maybe DocBook Blog is serious enough for a student's thesis an whatever level. No idea. Just suggesting… Another approach may well be to regard the entire blog as a book, with the articles being sections of level 1. But then: as the blog grows article by article the generation process for the whole will more and more degrade. And I just thought, that's not a good idea. And why start there, if we know that from the very beginning. Just my $0.05. Sic. - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Re: blogging using DocBook articles or so ...
Dave Pawson writes: On Sun, 18 Jul 2010 15:43:20 +0200 Jochen Hayek wrote: So far I have been blogging on a couple of blogger.com blogs of mine, and I got quite used to the capabilities there, I mean WYSIWYG is not that disgusting, even for an open-minded emacs guy as me, but then … … maybe there has already been an attempt to use DocBook for blogging? I mean, *what* *is* a *blog* *really*??? A time-consecutive list of articles, together with a commenting facility (but that's not most important, I think), and automatically supplied RSS and/or atom feeds. Not docbook, but I've been generating atom blog entries for some time now. Each entry a different file (by date, then date.1 etc) Bit of python to get the xml file list, XSLT to generate html + toc XSLT to generate the full atom feed. It's worked for about 5 years for me. Validated using NVDL. Let me know if you're interested. I am of course. Just to make sure: there is no DocBook envolved at all? I would love to see DocBook at the core. And you regard the file format, that embraces the articles (DocBook?!?), as nice enough? I mean, I am sure, it must actually be nice enough, if it's Dave Pawson's work. Whatever grammar you are using, I guess we can derive RNC from that, which will enable my happy authoring in emacs with nxml-mode. If I create an article (for the time being I asssume a DocBook article in one HTML chunk), how much extra work is it around that? do I have to manually keep redundant information like the article title and its creation DateTime? Can we get away from that sort of redundancy? You are a bright guy, that deserves my admiration. I am only asking silly questions and creating cheaky requests. So I am looking forward to any news from you. Kind regards, J. -- pls don't reply privately! pls don't regard this Hun as rough! - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Re: blogging using DocBook articles or so ...
On Sun, 18 Jul 2010 18:01:37 +0200 jochen+oasis-o...@hayek.name wrote: Just to make sure: there is no DocBook envolved at all? I would love to see DocBook at the core. Not sure how it would help with Atom? Perhaps to create the inserted html? And you regard the file format, that embraces the articles (DocBook?!?), as nice enough? The wrapper is atom, not docbook, which I publish directly. I mean, I am sure, it must actually be nice enough, if it's Dave Pawson's work. Whatever grammar you are using, I guess we can derive RNC from that, which will enable my happy authoring in emacs with nxml-mode. I have some code which generates the 'wrapper' $new tag Longer title generates ?xml version=1.0 encoding=utf-8? entry xmlns=http://www.w3.org/2005/Atom; xmlns:atom=http://www.w3.org/2005/Atom; xmlns:xhtml=http://www.w3.org/1999/xhtml; titleLonger title/title id100718/id updated2010-07-18T18:13:54/updated author nameDave Pawson/name urihttp://www.dpawson.co.uk/nodesets/100718.xml/uri email email adds /email /author category term=tag label=Longer title/ rights© Dave Pawson 2005, 2006, 2007, 2008,2009/rights link href=http://www.dpawson.co.uk/nodesets/entries/100718.html; rel=alternate/ link href=http://www.dpawson.co.uk/nodesets/100718.xml; rel=self/ published2010-07-18T18:13:54/published summarytag/summary content type=xhtml div xmlns=http://www.w3.org/1999/xhtml; p /p /div /content /entry Then I just type html into the div, as html. I use emacs nxml-mode for authoring but nvdl for validation. Then run a build script, using xslt. If I create an article (for the time being I asssume a DocBook article in one HTML chunk), how much extra work is it around that? do I have to manually keep redundant information like the article title and its creation DateTime? As you can see, some info is required. I use the date as the key 'hook' with tag and title coming from the command line. Can we get away from that sort of redundancy? From the above, you can see that the html header from docbook is all redundant? I am only asking silly questions and creating cheaky requests. No, just strikes me as 'I have a hammer' it all looks like a nail? I don't really see how docbook can help with a blog distributed in atom? -- regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Re: blogging using DocBook articles or so ...
Dave Pawson da...@dpawson.co.uk writes: On Sun, 18 Jul 2010 18:01:37 +0200 jochen+oasis-o...@hayek.name wrote: Just to make sure: there is no DocBook envolved at all? I would love to see DocBook at the core. Not sure how it would help with Atom? Perhaps to create the inserted html? I thought I could create the articles, i.e. the *content* using DocBook. And you regard the file format, that embraces the articles (DocBook?!?), as nice enough? The wrapper is atom, not docbook, which I publish directly. ure. A standard. Fine. Isn't that OPML-related? Rings a bell somehow. But usually (I thought at least) the wrapper (i.e. the feed) does not contain the entire articles, but it only refers to the content. But at least some feed providers restrict it to that, as far as I can say. I would like it that way. I don't like to slurp an entire newspaper into my iPhone and not via wifi, and only read 2% of it. Yes, it's a little more time consuming, to read the articles, that you decide to go for from the feed TOC. But I find that more reasonable. But maybe I got something fundamentally wrong. I mean, I am sure, it must actually be nice enough, if it's Dave Pawson's work. Whatever grammar you are using, I guess we can derive RNC from that, which will enable my happy authoring in emacs with nxml-mode. I have some code which generates the 'wrapper' $new tag Longer title generates [...] Then I just type html into the div, as html. But I could basically just wrap the URL for the article itself in fullblown HTML here, right? I mean, some articles are not just 140 characters, right?!? I use emacs nxml-mode for authoring but nvdl for validation. Then run a build script, using xslt. Sounds great to me. If I create an article (for the time being I asssume a DocBook article in one HTML chunk), how much extra work is it around that? do I have to manually keep redundant information like the article title and its creation DateTime? As you can see, some info is required. I use the date as the key 'hook' with tag and title coming from the command line. Can we get away from that sort of redundancy? From the above, you can see that the html header from docbook is all redundant? Not from the above, but if I want to keep the article separate, then yes. I am only asking silly questions and creating cheaky requests. No, just strikes me as 'I have a hammer' it all looks like a nail? Well, I think we have different approaches, but I think I can make use of your software for my approach. I don't really see how docbook can help with a blog distributed in atom? Separate articles, each written in DocBook, atom being the wrapper pointing to articles living for themselves, one by one. regards Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk Kind regards, Jochen hayek http://Hayek.name/Jochen.html P.S. I am taking my knowledge from some O'Reilly Short Cuts, namely: $ pdfinfo 9780596528221.pdf […] Title: Getting Acquainted with OPML Author: Amy Bellinger […] $ pdfinfo 9780596529383.pdf […] Title: How to Build an RSS 2.0 Feed Author: Mark Woodman […] But maybe that literature does not really fit here. - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Re: blogging using DocBook articles or so ...
Dave Pawson writes: […] Not docbook, but I've been generating atom blog entries for some time now. Each entry a different file (by date, then date.1 etc) Bit of python to get the xml file list, XSLT to generate html + toc XSLT to generate the full atom feed. It's worked for about 5 years for me. Validated using NVDL. Dave, all you out there including NDW, How far is your approach away from Norman's: Norman Walsh writes his blog in (a customization of) DocBook: http://norman.walsh.name/ Here is an old (obsolete?) article describing the machinery: http://norman.walsh.name/2003/05/14/how Mauritz And if I have the choice, what should I go for? I mean after all these years, there must have been a few out there, that stood before the same decision, right? Maybe both of you even presented your approach in a conference… :-) Kind regards, Jochen - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
