[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: DOCBOOK-APPS: DocBook to man pages XSL
Ok, I found ways to solve both problems: 1) Use an xsl to post-process the xhtml output of the docbook xsls to change li/p[1] to just li + children and following siblings of p. 2) links -dump inputfile.html | tr -d '\000' > outputfile.txt to remove the null character. David -----Original Message----- From: David Cramer Sent: Tuesday, February 18, 2003 12:48 AM To: docbook-apps@lists.oasis-open.org Subject: RE: DOCBOOK-APPS: DocBook to man pages XSL Hi Bob, The output from links is very nice with two exceptions: 1) there's a line break after each bullet/number in listitems (<li><p>text</p></li> doesn't go over well with links). 2) there's a character that shows up as ^@ in more/less or as a box in notepad before each step number in a procedure. I was wondering if you were seeing the same thing and how you get around it. Same result with Elinks 0.3 and 0.96. Thanks, David -----Original Message----- From: Bob Stayton [mailto:bobs@caldera.com] Sent: Tuesday, November 20, 2001 11:05 AM Are you using one of the text-based web browsers to convert HTML to text? I'm currently using "links" (no, not lynx) from http://artax.karlin.mff.cuni.cz/~mikulas/links/ and it handles tables nicely. It even does frames! And then there is the venerable lynx which I think handles tables now, and another called w3m from Japan http://ei5nazha.yz.yamagata-u.ac.jp/~aito/w3m/eng/ All of these have a "dump" option to let you save the generated text into a file.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC