From: Amit Kucheria <amitk@ittc.ku.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] DocBook testing
Date: Sun, 10 Mar 2002 22:55:22 +0000 [thread overview]
Message-ID: <marc-lartc-101580099601033@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101580034531979@msgid-missing>
On Sun, 10 Mar 2002, bert hubert wrote:
> If you look at http://lartc.org you will find links to a DocBook generated
> version of the HOWTO. Please let me know what you think! If you have tips &
> tricks for using DocBook, please let me know as well. I'm not happy with the
> need to use <paragraph></paragraph> for each paragraph right now!
Disclamer: I know zilch about DocBook format :)
Is there a specific reason to still persist with ascii diagrams like on
pages 41, 102 etc.? I guess its for the text version of the document?
Can we have nicer diagrams in the non-text versions? I volunteer for some
xfig diagrams if its possible to include them.
Regards,
Amit
--
The statement below is true.
The statement above is false.
^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^
Amit Kucheria
EECS Grad. Research Assistant
University of Kansas @ Lawrence
(R)+1-(785)-830 8521 ||| (O)+1-(785)-864 7774
____________________________________________________
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-03-10 22:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-10 22:44 [LARTC] DocBook testing bert hubert
2002-03-10 22:55 ` Amit Kucheria [this message]
2002-03-10 23:42 ` bert hubert
2002-03-10 23:58 ` Amit Kucheria
2002-03-11 6:18 ` Togan Muftuoglu
2002-03-13 14:18 ` Oskar Andreasson
2002-03-13 14:56 ` Togan Muftuoglu
2002-03-13 17:04 ` Oskar Andreasson
2002-03-16 11:25 ` bert hubert
2002-03-17 9:58 ` Togan Muftuoglu
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=marc-lartc-101580099601033@msgid-missing \
--to=amitk@ittc.ku.edu \
--cc=lartc@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.