This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
[docbook] Re: Encoding programming statements
- From: Norman Walsh <ndw at nwalsh dot com>
- To: BigSmoke <bigsmoke at home dot nl>
- Cc: docbook mailing list <docbook at lists dot oasis-open dot org>
- Date: Thu, 17 Jul 2003 15:40:53 -0700
- Subject: [docbook] Re: Encoding programming statements
- References: <200306041205.11126.bigsmoke@home.nl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
/ BigSmoke <bigsmoke@home.nl> was heard to say:
| What is 'the right way' to encode a programming statement. For example:
|
| <para>
| Both the <unknown>return</unknown> and <unknown>if</unknown>
| statement are impossible to mark-up properly if you can't find suitable
| elements in the TDG.
| </para>
This depends a little bit on the context of your document. In addition to
Michael's solution, I can imagine using "token", "literal", or "nonterminal"
in various kinds of documents.
Be seeing you,
norm
- --
Norman Walsh <ndw@nwalsh.com> | Almost every man wastes part of
http://www.oasis-open.org/docbook/ | his life in attempts to display
Chair, DocBook Technical Committee | qualities which he does not
| possess, and to gain applause
| which he cannot keep.--Dr. Johnson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>
iD8DBQE/FyX0OyltUcwYWjsRAnVUAKCHcPsAAAi5EMha7YqsxVsgfoFXFgCdGr5g
SWP9iXcXf882okM6iuSEssM=
=eGdW
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: docbook-help@lists.oasis-open.org