All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] DocBook testing
Date: Sun, 10 Mar 2002 23:42:54 +0000	[thread overview]
Message-ID: <marc-lartc-101580382705924@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101580034531979@msgid-missing>

On Sun, Mar 10, 2002 at 04:55:22PM -0600, Amit Kucheria wrote:
> 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.

Well, cool, but I'm hesitant. The problem is that these figures would then
live outside of the main file, and will most definitely start to diverge.

I also investigated pic(1) which has a cool syntax and very cool output.

ellipse "kernel";
arrow;
box "network";
arrow;
circle "internet";

This turns into http://ds9a.nl/tmp/pic.png which is rather nice (it needs
some work to make it really pretty). However, it still does not look good in
ascii.

So basically I'm looking for something that:
	- can live in the source
	- generates legible ASCII
	- generates good looking postscript/png

The real solution may be to use pic in the DocBook and also provide an ASCII
version in the source. That *would* mean double work, but at least
everything would be in the same place.


Regards,


bert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-03-10 23:42 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
2002-03-10 23:42 ` bert hubert [this message]
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-101580382705924@msgid-missing \
    --to=ahu@ds9a.nl \
    --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.