[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Encoding programming statements
-----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-----
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]