From owner-freebsd-doc  Mon Nov  6  3:12:20 2000
Delivered-To: freebsd-doc@freebsd.org
Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222])
	by hub.freebsd.org (Postfix) with ESMTP id 984A737B4D7
	for <freebsd-doc@freebsd.org>; Mon,  6 Nov 2000 03:12:17 -0800 (PST)
Received: from localhost (murray@localhost)
	by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id eA6BC3Z06151
	for <freebsd-doc@freebsd.org>; Mon, 6 Nov 2000 03:12:03 -0800 (PST)
	(envelope-from murray@osd.bsdi.com)
Date: Mon, 6 Nov 2000 03:12:03 -0800 (PST)
From: Murray Stokely <murray@osd.bsdi.com>
To: freebsd-doc@freebsd.org
Subject: <programlisting> woes
Message-ID: <Pine.BSF.4.21.0011060307410.5211-100000@pike.osd.bsdi.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-doc@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

  What's the best way to include source code within DocBook?
Currently I'm using <programlisting> but I don't want to have to
enclose my header files, and pointers within <literal> tags so that
Jade doesn't think I'm referring to non existant sgml tags (like
sys/types.h) or unknown entities (like &buffer).
  I don't think that the actual code in a program listing should be
marked up, should it?  For some reason I assumed a programlisting
would contain nothing but character data.

	- Murray



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message