[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [docbook] DocBook - a success story?
Daniel, > And (X)HTML is not a "simple markup language"? What is simpler than this? Ok, so when you write an article in wikipedia you write it in XHTML then? >> 3. Rendering my CV as man page would have been fun > > That is a silly idea. Do you really know, what a manual page is and what > it looks like? I would really love to know, what would be in your NAME, > SYNOPSIS and OPTIONS sections. In AUTHORS you would put your parents and > in COPYRIGHT your wife? :) Yes, why not. What do you care about how I what I write into a manual? Btw, I believe the most interesting part would be the "KNOWN PROBLEMS" :-) > Of course. Why do you expect that article == book == refentry? If all > would have the same meaning, we wouldn't need all of them. <refentry> > fits best to the manual page contents and its format. That's a good point anyway. Do we really need to differenciate between article, book and refentry? Why isn't there instead a generic 'container' element? > JFTR: It's much easier to dump the output of a HTML/PD/PS browser/viewer > into a text file. Again you missed the point Daniel. I just learned today that I'm not the only one who tried to produce a "pretty" plain text document. I got stuck at (a) nice word wrap when reaching 80 chars and (b) tables.. > PS: You have already been pointed to the xmlresume software, which is > probably what you are looking for. No, I'm looking into DB. Btw, so far I got a lot of feedback. They all tell me that I'm using DocBook in a way it has not been designed for. The "success-feedback-counter" is still zero. Greetz, Wolfgang. On Wed, Jan 20, 2010 at 9:30 PM, Daniel Leidert <daniel.leidert.spam@gmx.net> wrote: > Am Dienstag, den 19.01.2010, 18:02 +0100 schrieb wolfgang haefelinger: > > [..] >> 2. DocBook is probably also fine to create (X)HTML. I did not give it >> a try cause I consider generating HTML obsolete cause most web content >> is generated nowadays by using some simle markup languages > > And (X)HTML is not a "simple markup language"? What is simpler than > this? > >> 3. Rendering my CV as man page would have been fun > > That is a silly idea. Do you really know, what a manual page is and what > it looks like? I would really love to know, what would be in your NAME, > SYNOPSIS and OPTIONS sections. In AUTHORS you would put your parents and > in COPYRIGHT your wife? :) > >> but it did not work >> cause I'm using the "wrong" docbook format (i.e. "article"). There a >> lot of tools which claim to render a DocBook source into a man page. >> They all only render a subset of DocBook only .. > > Of course. Why do you expect that article == book == refentry? If all > would have the same meaning, we wouldn't need all of them. <refentry> > fits best to the manual page contents and its format. > >> 4. I wrote my own "DocBook to Plain text" XSLT stylesheet in a couple >> of hours work. > > JFTR: It's much easier to dump the output of a HTML/PD/PS browser/viewer > into a text file. > > PS: You have already been pointed to the xmlresume software, which is > probably what you are looking for. > > Regards, Daniel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: docbook-unsubscribe@lists.oasis-open.org > For additional commands, e-mail: docbook-help@lists.oasis-open.org > > -- Wolfgang Häfelinger häfelinger IT - Applied Software Architecture http://www.haefelinger.it +31 648 27 61 59
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]