[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Dan apologizes, and then rants... (Was Re: TOCs in articles?)
Dan York wrote:
> Apologies for bothering you all with the question when I had not gone back
> to the manual first. (RTFM)
Another author helped by the H-H! Woo!
> In working with DocBook, both for some LDP stuff as well as for some things
> within Linuxcare, I have found working with jade and stylesheets to be the
> most painful part of it all. Creating DocBook files is, to me, trivial and
> easy. It's what to do with them afterward that is the headache.
> Take the example here with "ldp.dsl". The instructions say to use jade (or in
> my case openjade) with the following options:
> jade -t sgml -ihtml -d /usr/lib/sgml/stylesheets/ldp.dsl\#html
> In all the other tutorials and information I have had with jade, I have not
> seen the "-ihtml" option used anywhere. Likewise, I have never seen the
> "\#html" at the end of a "*.dsl" file. Maybe I missed something in reading the
> but these were not options I would have tried without having read the
> Maybe this is just something particular to ldp.dsl. But it's not easy for
> new to all of this.
The -i html means that you're generating SGML in HTML format
The \#html means to pay attention to the HTML section of the ldp.dsl file.
I'm not sure why (open)jade doesn't pull this from the -i, but I didn't
> For that matter, it still seems bizarre to me that I must use "-t sgml" to
> an HTML file, whereas "-t rtf" or "-t mif" produces those other file formats.
> And I
> find it extremely weird that there is not "-t text" and that you have to do a
> with lynx (or another text browser).
I think that's something that will have to be taken up with the openjade
Carlo Gavazzi IPC | Mark F. Komarinski, RHCE - Compat. Engineer|
176 Second Ave | email@example.com - www.cgipc.com |
Waltham, MA 02451 USA | Ph: 781-266-1138 Fx: 781-290-4810 |
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com