Re: [PEPr] Changes in proposal for File Formats::PDF Reader

Thanks, Matthew. As someone who uses web and command line interchangeably, I'm quite used to mentally "filtering" HTML out of command line output I read. However, I find command line output dumped into a web browser to be maddening, and having to write extra code to wrap it in PRE or BLOCKQUOTE just to make it intelligible adds to the frustration. Also, considering PHP is primarily used as a web language and that I work with a number of developers whose skills are far below the average PEAR developer and for whom the command line is terrifying, the HTML formatting makes it more usable for them. Command line users are usually smart enough to ignore the HTML. Web users may not be smart enough to use PRE or BLOCKQUOTE. So, I respectfully decline. -John On Thu, 6 Jan 2011 10:41:27 -0800, Matthew Fonda <matthewfonda@gmail.com> wrote:

On Thu, Jan 6, 2011 at 9:34 AM, John Stokes <jstokes@heartofthefyre.us> wrote:

5.) Your debug output always uses HTML formatting. People might be using this package in a non-web context. JS: I include both command-line "n" and HTML "" so it can be used in either context. I keep the HTML code minimal so command line users will have very little HTML to wade through.

As someone who primarily uses PHP from the command-line, I'd find the debugging output to be useful, but HTML in it to be annoying, however minimal it may be. I suggest removing it completely--if someone wants to display debugging text in HTML they could wrap it in <pre> or something to retain the formatting. Best regards, --Matthew