public inbox for docbook-tools-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jorge Godoy <godoy@conectiva.com.br>
To: Dan Miner <dminer@edison.chisp.net>
Cc: 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: <20000223082034.G8077@conectiva.com.br> (raw)
In-Reply-To: <200002230442.VAA07833@edison.chisp.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2013 bytes --]

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.

<propaganda>

I've started a HOWTO on DocBook (and I'm improving it for LDP's
2nd. version) and placed it in http://metalab.unc.edu/godoy - there's
a link to the Portuguese and English versions. There's explained how
to do this.

</propaganda>

<excuses>

English errors are being corrected, since the translator was not a
technical one. 

</excuses>

> 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. 


> Is there any hope for me?  :)

There's always hope. But it doesn't means that you'll do what you want
to :-))


Regards,
--
Godoy.	<godoy@conectiva.com.br>               GPG Fingerprint
                                         851B B620 626D 2AD0 E783
"Ser poeta não é minha ambição,          E932 1330 BE6D A4A3 0625 
 é minha maneira de estar sozinho"
              - Fernando Pessoa.       Publicações @ Conectiva S.A. 

Except where explicitly stated I speak on my own behalf.
Exceto onde explicitado as declarações aqui feitas são apenas minhas.

  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 ` Jorge Godoy [this message]
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=20000223082034.G8077@conectiva.com.br \
    --to=godoy@conectiva.com.br \
    --cc=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).