From: Dan Miner <dminer@edison.chisp.net>
To: docbook-tools-discuss@sourceware.cygnus.com
Subject: NEWBIE: getting your document structure right.. :)
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <200002230442.VAA07833@edison.chisp.net> (raw)
I've been playing with DocBook and reading what I can find for a couple of
days now. I'm still coming up empty handed...
I'm making an electronic copy of an old book from the Commodore 64 days
written by Jim Butterfield. I would really like to *capture* the structure
of the book and its content. However, I've run into a couple of things I
can't quite identify approiate tags.
This book is about learning 650x machine language and the author uses
rather informal lists and examples. I'm looking for something meaning this:
<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.
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.
Is there any hope for me? :)
I'm using the docbook-tools (jade 1.2.1, 0.10, etc -- latest RPMs) and
the db2html for "display".
Regards,
Dan
--
Dan Miner dan@miner.org | "That vulnerability is completely | Doing
Linux & UNIX | theoretical." -- Microsoft | Linux
Programmer/Consultant | "What yonder light Windows 95 breaks?" | since
http://www.dan.miner.org/ | "Free software: The New Frontier" | v0.12
------------------------------------------------------------------------------
By filing this bug report, you have challenged the honor of my
family. PREPARE TO DIE!
next 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 [this message]
2000-12-27 6:36 ` Jorge Godoy
2000-12-27 6:36 ` Norman Walsh
2000-12-27 6:36 ` Norman Walsh
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=200002230442.VAA07833@edison.chisp.net \
--to=dminer@edison.chisp.net \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
/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).