EVL> Task of html2text - convert HTML to text, not implement proxying. EVL> Use wget or curl, then html2text through pipe, for example:
EVL> curl -s http://www.server.com/aaa/bbb/ccc.html | html2text You are making a big mistake. You see, you already support URLs, I.E., $ html2text http://www.server.com/aaa/bbb/ccc.html is the same as your curl line. I'm just saying that if you are going to support URLs, then do it to a proper extent, or don't do it at all. $ html2text http://www.videolan.org/doc/ ****** Moved Permanently ****** The document has moved here. Where? $ html2text http://wiki.videolan.org/ [spews some PNG]. And also implement http_proxy. On the other hand, it would seem better to rip out all URL support and just concentrate on turning STDIN into text, like you said, to keep the roles simple. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
