On Sun, Jan 12, 2003 at 10:21:57AM -0500, Dan Espen wrote:
Olivier Chapuis [EMAIL PROTECTED] writes:
On Sat, Jan 11, 2003 at 10:32:32PM -0500, Dan Espen wrote:
Olivier Chapuis [EMAIL PROTECTED] writes:
However the .sgml is really hard to read.
The markup gets in the way.
I don't
On Sun, Jan 12, 2003 at 12:16:51AM -0500, parv wrote:
in message [EMAIL PROTECTED], wrote
Dan Espen thusly...
- Possibility to have a printable version of the documentation.
I.e., a ps and/or pdf FVWM book.
I'd add, the ability to include images. Some of the documentation
talks
On Sat, Jan 11, 2003 at 11:39:51AM +0100, Olivier Chapuis wrote:
On Sat, Jan 11, 2003 at 01:16:57AM -0500, Eric Gillespie wrote:
Olivier Chapuis [EMAIL PROTECTED] writes:
I think that what we need is SGML+DocBook. The LDP and numerous open
source project use this now.
Everyone
and/or pdf FVWM book.
I think that what we need is SGML+DocBook. The LDP and numerous open
source project use this now.
Maybe I don't have all the facts, but using SGML seems like overkill to
me. Were it up to me, I'd maintain the fvwm documentation as POD (perl's
Plain Old Documentation
I send an answer to this message but it does not appear.
Maybe it was condidered as a SPAM as it contains html?
I try again ...
Olivier
--
Visit the official FVWM web page at URL:http://www.fvwm.org/.
To unsubscribe from the list, send unsubscribe fvwm-workers in the
body of a message to [EMAIL
On 10 Jan 2003 23:26:41 +0100, Olivier Chapuis wrote:
I have a concrete proposition for improving FVWM documentation.
Looks pretty good to me.
I may write pod2xml convertor once I understand how it should work, so we
don't need to worry about the existing pod documentation.
If this helps, we
Olivier Chapuis [EMAIL PROTECTED] writes:
On Sat, Jan 11, 2003 at 10:32:32PM -0500, Dan Espen wrote:
Olivier Chapuis [EMAIL PROTECTED] writes:
I'm sorry, what did Dominik say?
Take a look at the thread which start with:
8 Aug 2002 Len Philpot Documentation (was: Re: FVWM: How do I
On Sat, Jan 11, 2003 at 10:32:32PM -0500, Dan Espen wrote:
Olivier Chapuis [EMAIL PROTECTED] writes:
Hello,
I have a concrete proposition for improving FVWM documentation. This
has been discussed a number of time and I think that action is
needed. I am really agree with the last mail
On Sat, Jan 11, 2003 at 10:32:32PM -0500, Dan Espen wrote:
Olivier Chapuis [EMAIL PROTECTED] writes:
Hello,
I have a concrete proposition for improving FVWM documentation. This
has been discussed a number of time and I think that action is
needed. I am really agree with the last mail
Answer attached as I think it is rejected by the SPAM filter.
Olivier
On Sat, Jan 11, 2003 at 10:32:32PM -0500, Dan Espen wrote:
Olivier Chapuis [EMAIL PROTECTED] writes:
Hello,
I have a concrete proposition for improving FVWM documentation. This
has been discussed a number of time
Olivier Chapuis [EMAIL PROTECTED] writes:
I think that what we need is SGML+DocBook. The LDP and numerous open
source project use this now.
Everyone else has moved on to XML, using Norm Walsh's very nice
docbook-xsl stylesheets.
docbook2man - a dramatic perl script that can convert the
. The LDP and numerous open
source project use this now.
Maybe I don't have all the facts, but using SGML seems like overkill to
me. Were it up to me, I'd maintain the fvwm documentation as POD (perl's
Plain Old Documentation). POD is a very simple format, and there already
exists many scripts
On Sat, Jan 11, 2003 at 01:16:57AM -0500, Eric Gillespie wrote:
Olivier Chapuis [EMAIL PROTECTED] writes:
I think that what we need is SGML+DocBook. The LDP and numerous open
source project use this now.
Everyone else has moved on to XML, using Norm Walsh's very nice
docbook-xsl
Olivier Chapuis [EMAIL PROTECTED] writes:
Hello,
I have a concrete proposition for improving FVWM documentation. This
has been discussed a number of time and I think that action is
needed. I am really agree with the last mail of Dominik on the
subject.
I'm sorry, what did Dominik say
in message [EMAIL PROTECTED], wrote
Dan Espen thusly...
- Possibility to have a printable version of the documentation.
I.e., a ps and/or pdf FVWM book.
I'd add, the ability to include images. Some of the documentation
talks about visual effects, but there are no illustrations in our
Hello,
I have a concrete proposition for improving FVWM documentation. This
has been discussed a number of time and I think that action is
needed. I am really agree with the last mail of Dominik on the
subject. I've just this mail in my brain but roughly speaking we need:
- The current man pages
16 matches
Mail list logo
