NetBSD Problem Report #10210

Received: (qmail 24627 invoked from network); 28 May 2000 07:57:34 -0000
Message-Id: <200005280757.AAA04146@digital.clock.org>
Date: Sun, 28 May 2000 00:57:34 -0700 (PDT)
From: "Erik E. Fair" <fair@digital.clock.org>
Reply-To: fair@netbsd.org
To: gnats-bugs@gnats.netbsd.org
Subject: vgrind should also produce HTML
X-Send-Pr-Version: 3.95

>Number:         10210
>Category:       bin
>Synopsis:       vgrind should also produce HTML
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sun May 28 07:58:00 +0000 2000
>Closed-Date:    
>Last-Modified:  Sun Jul 17 03:15:14 +0000 2011
>Originator:     Erik E. Fair
>Release:        1.4.2
>Organization:
International Organization of Internet Clock Watchers
>Environment:

System: NetBSD digital.clock.org 1.4.2A NetBSD 1.4.2A (DIGITAL) #2: Tue May 23 17:26:00 PDT 2000 root@digital.clock.org:/usr/obj/sys/arch/alpha/compile/DIGITAL alpha


>Description:
	People look at code with web browsers. vgrind(1) was designed to
	format code nicely for printing (bold keywords, etc), and it could
	probably be modified to produce HTML output so that it can be used
	to format NetBSD's source code for web browser viewing.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed
State-Changed-By: jruoho@NetBSD.org
State-Changed-When: Tue, 03 May 2011 18:03:02 +0000
State-Changed-Why:

I will close this; the word "should" is always subjective. The same thing 
could be said about most of the standard utilities. There should be either  
a big XML discussion or a resolution from core@ about the general directions
involving HTML/XML. Thus, as such, this is a drop in the ocean.



State-Changed-From-To: closed->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sun, 17 Jul 2011 03:15:14 +0000
State-Changed-Why:
 > I will close this
...and I'll reopen it.

vgrind is the standard tool for prettyprinting source. If it is outdated to
the point of uselessness, it should be removed. If it is incapable of ever
supporting anything but roff, then perhaps it should be replaced. Granted
HTML is not a typesetting language or a "pretty" printing language for
anything, but it's also currently a convenient way of getting acceptably
mediocre output, and an intelligently written vgrind should not have trouble
supporting multiple output backends.

Meanwhile, as you say there are unanswered questions about text and document
processing and the ongoing role of roff; these should be answered but it
doesn't do any good to close the PRs that contain reminders of what the issues
are.


>Unformatted:

Home	PR Database Search