Re: [docbook-apps] DocBook/XSL/FO-HTML and Table Column Widths
On Sun, Jul 18, 2010 at 11:03, Bob Stayton wrote: > Hi Tom, > First question: was there any column width information in the HTML tables > from which you converted that content? If so, ensuring that the conversion > included the column widths would likely help. Yes, there was: column widths as integers, no units--pixels I assume. > But I believe you said you were using FOP, and FOP does not currently > support the table-layout="auto" property. You would need to use another FO > processor. So then fop is what needs to be updated--thanks. Regards, -Tom - 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
[docbook-apps] Re: blogging using DocBook articles or so ...
> Dave Pawson 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
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 http://www.w3.org/2005/Atom"; xmlns:atom="http://www.w3.org/2005/Atom"; xmlns:xhtml="http://www.w3.org/1999/xhtml";> Longer title 100718 2010-07-18T18:13:54 Dave Pawson http://www.dpawson.co.uk/nodesets/100718.xml email adds © Dave Pawson 2005, 2006, 2007, 2008,2009 http://www.dpawson.co.uk/nodesets/entries/100718.html"; rel="alternate"/> http://www.dpawson.co.uk/nodesets/100718.xml"; rel="self"/> 2010-07-18T18:13:54 tag http://www.w3.org/1999/xhtml";> 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: article / info / author / address - how do I make it appear?
> Mauritz Jeanson writes: | -Original Message- | From: jochen+oasis-o...@hayek.name | | I searched Bob's book for that (paper and online), | but to no success. | | I wrote a little document, | and it's necessary, that it shows my address. | | Any pointer pls? > The stuff inside is part of the "titlepage", > which has its own customization system: > http://www.sagehill.net/docbookxsl/HTMLTitlePage.html > http://www.sagehill.net/docbookxsl/TitlePagePrint.html "Example 13.6. Adding an element to a title page." Would I have to copy that t:titlepage-content rule and add "" there? And if the original rule gets improved during its lifetime, how would I notice but by "setting a watch-dog"? I had hoped, I would find a simple switch saying "include author?". > Mauritz Jochen - 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] blogging using DocBook articles or so ...
| -Original Message- | From: jochen+oasis-o...@hayek.name | | 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? 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 - 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] DocBook/XSL/FO-HTML and Table Column Widths
Off the subject but is there a way to stop FO from breaking a row in the middle? IOW, to push an entire row to the next page? Thanks On 7/18/2010 11:03 AM, Bob Stayton wrote: Hi Tom, First question: was there any column width information in the HTML tables from which you converted that content? If so, ensuring that the conversion included the column widths would likely help. The column widths stylesheet extension is not going to help you if your tables have no column width information. The extension just converts potentially complex CALS colwidth values to simpler HTML values. If there is no column width information to work with, it will just give each column the same percentage width. The extension has no means of measuring the widths of typeset columns, because the columns have not yet been typeset. If your HTML tables did not have column width information, then the browser was choosing how wide to make each column based on the column content. A similar function is available in XSL-FO in the table-layout="auto" property on the fo:table element. That engages a formatting algorithm in the XSL-FO processor that reads the width of the typeset content in the columns and adjusts the column widths for a better fit. It works best with short entries that don't have to wrap lines. But I believe you said you were using FOP, and FOP does not currently support the table-layout="auto" property. You would need to use another FO processor. Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: "Tom Browder" To: Sent: Sunday, July 18, 2010 8:05 AM Subject: [docbook-apps] DocBook/XSL/FO-HTML and Table Column Widths I have pretty much converted an old, large html-based set of docs into DocBook 5. The only chunk I'm not happy with are the tables which need customizing to adjust column widths. Adjusting the column widths seems problematic at the moment for one using xsltproc. I see that Norm Walsh has a Python wrapper to take care of that (and I'll explore that soon), but that seems to add another layer to the tool chain that is already daunting for a newbie. My questions are: 1. Where should the necessary missing functions and algorithms be inserted, into xsltproc, or? 2. Are the table column formatting functions really extensions, or should they be considered part of a core standard that is missing in xsltproc and other xsl programs? I would like to offer my help for the situation but am not sure where to start. Thanks, -Tom Thomas M. Browder, Jr. Niceville, Florida USA - 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 -- Steve Johnson, Senior Content Developer Caringo ste...@caringo.com - 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] DocBook/XSL/FO-HTML and Table Column Widths
Hi Tom, First question: was there any column width information in the HTML tables from which you converted that content? If so, ensuring that the conversion included the column widths would likely help. The column widths stylesheet extension is not going to help you if your tables have no column width information. The extension just converts potentially complex CALS colwidth values to simpler HTML values. If there is no column width information to work with, it will just give each column the same percentage width. The extension has no means of measuring the widths of typeset columns, because the columns have not yet been typeset. If your HTML tables did not have column width information, then the browser was choosing how wide to make each column based on the column content. A similar function is available in XSL-FO in the table-layout="auto" property on the fo:table element. That engages a formatting algorithm in the XSL-FO processor that reads the width of the typeset content in the columns and adjusts the column widths for a better fit. It works best with short entries that don't have to wrap lines. But I believe you said you were using FOP, and FOP does not currently support the table-layout="auto" property. You would need to use another FO processor. Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: "Tom Browder" To: Sent: Sunday, July 18, 2010 8:05 AM Subject: [docbook-apps] DocBook/XSL/FO-HTML and Table Column Widths I have pretty much converted an old, large html-based set of docs into DocBook 5. The only chunk I'm not happy with are the tables which need customizing to adjust column widths. Adjusting the column widths seems problematic at the moment for one using xsltproc. I see that Norm Walsh has a Python wrapper to take care of that (and I'll explore that soon), but that seems to add another layer to the tool chain that is already daunting for a newbie. My questions are: 1. Where should the necessary missing functions and algorithms be inserted, into xsltproc, or? 2. Are the table column formatting functions really extensions, or should they be considered part of a core standard that is missing in xsltproc and other xsl programs? I would like to offer my help for the situation but am not sure where to start. Thanks, -Tom Thomas M. Browder, Jr. Niceville, Florida USA - 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 ...
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 ...
> 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] How to Adjust Table Column Widths with xsltproc
| -Original Message- | From: Tom Browder | | How can I affect table column widths with the current db 5, xsltproc, | and fop tool chain without hand modifying the fo file? Are you sure that you really need to adjust column widths? That is not supposed to be necessary for FO output (even though the stylesheet extension also works for FO). See http://www.sagehill.net/docbookxsl/ColumnWidths.html. 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] DocBook/XSL/FO-HTML and Table Column Widths
I have pretty much converted an old, large html-based set of docs into DocBook 5. The only chunk I'm not happy with are the tables which need customizing to adjust column widths. Adjusting the column widths seems problematic at the moment for one using xsltproc. I see that Norm Walsh has a Python wrapper to take care of that (and I'll explore that soon), but that seems to add another layer to the tool chain that is already daunting for a newbie. My questions are: 1. Where should the necessary missing functions and algorithms be inserted, into xsltproc, or? 2. Are the table column formatting functions really extensions, or should they be considered part of a core standard that is missing in xsltproc and other xsl programs? I would like to offer my help for the situation but am not sure where to start. Thanks, -Tom Thomas M. Browder, Jr. Niceville, Florida USA - 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] blogging using DocBook articles or so ...
On Sun, 18 Jul 2010 15:43:20 +0200 jochen+oasis-o...@hayek.name 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. -- 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
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 blogging&sharing 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: > 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 blogging&sharing 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] blogging using DocBook articles or so ...
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. 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. -Original Message- From: jochen+oasis-o...@hayek.name [mailto:jochen+oasis-o...@hayek.name] Sent: Sunday, July 18, 2010 9:43 AM To: docbook-apps@lists.oasis-open.org Subject: [docbook-apps] blogging using DocBook articles or so ... 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. Would be exciting to use DocBook also for that. Kind regars, J. -- As nice as you guys here are, pls usually only reply to my post right on this mailing list. I honestly do follow this list. Of course, if you want to tell me, how silly I am, then let's keep that private ;-) but usually it's only my Bad Simple English, not my ideas. - 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] blogging using DocBook articles or so ...
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. Would be exciting to use DocBook also for that. Kind regars, J. -- As nice as you guys here are, pls usually only reply to my post right on this mailing list. I honestly do follow this list. Of course, if you want to tell me, how silly I am, then let's keep that private ;-) but usually it's only my Bad Simple English, not my ideas. - 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] article / info / author / address - how do I make it appear?
> Denis Bradford writes: > Hi Jochen Hi, Denis, you are my diligent tutor! Thanks a lot for that! > According to 'DocBook 5: The Definitive Guide' > (http://www.docbook.org/tdg51/en/html/info.html), article/info is not > designed to appear in output: Well, if it comes to processing and output orientation, I have never used to look at TDG4 resp TDG5 for the last 12 years or so, but "always" at Bob Stayton's book. Maybe that was a fault. On the other hand: How "holy" are "Processing expectations" in the TDG? It wouldn't really be against the spirit of a DocBook "article" to show the author details, if the user requested that on purpose, or is this regarded as "simply incorrect" by the community and the gurus? I mean for a "general purpose document" (be it of type "article"), what sense does that restriction make? I hope, I do not unnecessarily restart old discussions. Maybe somebody points me at an ancient agreement on this matter. > == > Description > The info element contains meta-information about the element that > contains it. > Processing expectations > Suppressed. > == > So I think you need to use address in a different context if you want > it displayed. The same DocBook design document /address.html) has this > example: > […] Alright, I will definitely do this, as long as I don't achieve it in the place, where I actually attempt to achieve it. > - Denis Jochen > On 07/18/2010 07:58 AM, jochen+oasis-o...@hayek.name wrote: >> I searched Bob's book for that (paper and online), >> but to no success. >> >> I wrote a little document, >> and it's necessary, that it shows my address. >> >> Any pointer pls? >> >> Kind regards, >> J. - 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] article / info / author / address - how do I make it appear?
| -Original Message- | From: jochen+oasis-o...@hayek.name | | I searched Bob's book for that (paper and online), | but to no success. | | I wrote a little document, | and it's necessary, that it shows my address. | | Any pointer pls? The stuff inside is part of the "titlepage", which has its own customization system: http://www.sagehill.net/docbookxsl/HTMLTitlePage.html http://www.sagehill.net/docbookxsl/TitlePagePrint.html Mauritz - 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] article / info / author / address - how do I make it appear?
Hi Jochen According to 'DocBook 5: The Definitive Guide' (http://www.docbook.org/tdg51/en/html/info.html), article/info is not designed to appear in output: == Description The info element contains meta-information about the element that contains it. Processing expectations Suppressed. == So I think you need to use address in a different context if you want it displayed. The same DocBook design document /address.html) has this example: Example address An example of a postal mail address in the United States: John and Jane Doe 100 Main Street Anytown, NY 12345 USA - Denis On 07/18/2010 07:58 AM, jochen+oasis-o...@hayek.name wrote: I searched Bob's book for that (paper and online), but to no success. I wrote a little document, and it's necessary, that it shows my address. Any pointer pls? Kind regards, J. - 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] article / info / author / address - how do I make it appear?
I searched Bob's book for that (paper and online), but to no success. I wrote a little document, and it's necessary, that it shows my address. Any pointer pls? Kind regards, J. - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: Re: [docbook-apps] callout.unicode.font question
Monday 12 July 2010 > On 9 juil. 2010, at 18:56, David Cramer wrote: > > > I found the way to custom callout.xsl and it works. But the font I found is > not so beautiful as I expected :-( You could try Linux Libertine, maybe you like it: http://linuxlibertine.sourceforge.net/ It has callouts up to 20. Tom - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
