From owner-freebsd-doc Thu Aug 24 13:50: 7 2000 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7A2EA37B424 for ; Thu, 24 Aug 2000 13:50:03 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id NAA39941; Thu, 24 Aug 2000 13:50:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 24 Aug 2000 13:50:03 -0700 (PDT) Message-Id: <200008242050.NAA39941@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Brooks Davis Subject: Re: docs/20028: ASCII docs should reflect tags in the source Reply-To: Brooks Davis Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR docs/20028; it has been noted by GNATS. From: Brooks Davis To: Rasmus Kaj Cc: freebsd-doc@FreeBSD.ORG, FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: docs/20028: ASCII docs should reflect tags in the source Date: Thu, 24 Aug 2000 13:49:36 -0700 On Thu, Aug 24, 2000 at 12:53:02PM +0200, Rasmus Kaj wrote: > > Well, *foo* looks like bold to some, but isn't, really. Same goes for > /bar/ ... So, while I'm in favor of foo -> *foo* > and bar -> _bar_ or /bar/, I think and really should > be ignored when font controll isn't availible. I think I agree here. If we changed the style sheet to output either or when it seems the DocBook tag and then hack w3m to produce either some variation on *foo* when it sees that tag then we'd accomplish the task of translating to something visiable in ASCII docs and avoid screwing things up that actually do use or for typographic reasions. > Also, you may want to make it possible to disable this stuff in > certain tags, for example, if you have an example command line that > looks like: > > % *rm* /junk/ > > ... then there is bound to be some questions about that ... :-) That's a style sheet issue. In this case we probably shouldn't be writing rm junk as html output because that's not what we mean. In this case we really do mean rm junk because this is purley a typographical convention at this point not a symantic markup. > That said, I agree with the basic suggestion that it would be nice to > have e.g. render visibly in plain text. My prefrence is for a result that renders in the *baz* style. I think what I'll do is hack up some patches to translates to and w3m translates and to *. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message