From: Norman Walsh <ndw@nwalsh.com>
To: Jorge Godoy <godoy@conectiva.com.br>
Cc: Dan Miner <dminer@edison.chisp.net>,
docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: NEWBIE: getting your document structure right.. :)
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <4369-Wed23Feb2000070608-0500-ndw@nwalsh.com> (raw)
In-Reply-To: <20000223082034.G8077@conectiva.com.br>
/ Jorge Godoy <godoy@conectiva.com.br> was heard to say:
| On Tue, Feb 22, 2000 at 09:42:15PM -0700, Dan Miner wrote:
| >
| > <Goals>
| > <GoalDef>my goal</GoalDef>
| > <GoalExplain>more details about why this goal is important, etc.</GoalExplain>
| > <GoalDef>my goal 2</GoalDef>
| > <GoalExplain>more text about why this goal is important, etc.</GoalExplain>
| > </Goals>
| >
| > I understand display is somewhat a secondary concern but I'l hoping
| > for a display like:
| >
| > * my goal
| > more details about why this goal is important, etc.
| >
| > * my goal 2
| > more text about why this goal is important, etc.
|
| It seems to me like a variablelist.
I agree, with perhaps some stylesheet tweaks to get precisely that
formatting.
| > Also, how can I express example information/code/command that is actually
| > part of the paragraph flow?
| >
| > For example:
| >
| > <para>Be sure to run <InlineExample role=eg>G C000</InlineExample> your newly
| > created program by using the monitor run or go command.</para>
| >
| > Formatted as:
| > Be sure to run (e.g. G C000) your newly created program by using the
| > monitor run or go command.
|
| You'll have to create this new element or modify some element's
| appearance using a stylesheet.
Oh, I really try to avoid that answer whenever possible because it makes
the documents much less portable. I'd be tempted myself to use
<literal>, <userinput>, or even <systemitem role="inlineexample">
before creating a new element.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | If you are hankering after
http://nwalsh.com/ | certainty, you are better advised
| to seek it in religion: the
| stock-in-trade of science is not
| certainty but doubt.--K.C. Cole
prev parent reply other threads:[~2000-12-27 6:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 6:36 Dan Miner
2000-12-27 6:36 ` Norman Walsh
2000-12-27 6:36 ` Jorge Godoy
2000-12-27 6:36 ` Norman Walsh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4369-Wed23Feb2000070608-0500-ndw@nwalsh.com \
--to=ndw@nwalsh.com \
--cc=dminer@edison.chisp.net \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=godoy@conectiva.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).