From: Stephan Beyer <s-beyer@gmx.net>
To: Abdelrazak Younes <younes@lyx.org>
Cc: git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Julian Phillips <julian@quantumfyre.co.uk>,
Scott Chacon <schacon@gmail.com>, Petr Baudis <pasky@suse.cz>
Subject: Re: markdown 2 man, was Re: Git Community Book
Date: Thu, 31 Jul 2008 15:01:01 +0200 [thread overview]
Message-ID: <20080731130101.GC18106@leksak.fem-net> (raw)
In-Reply-To: <4891A0D0.6060503@lyx.org>
Hi,
Abdelrazak Younes wrote:
> Please ignore if this is not appropriate.
Well, so I should've ignored, but I think this is worth some correction.
> Asciidoc or Markdown are tools that accommodate the _developer_, not the
> user. I understand that these markup language are ideally suited for in
> source documentation (thought I personally much prefer Doxygen).
http://www.methods.co.nz/asciidoc/ says
``AsciiDoc is a text document format for writing short documents,
articles, books and UNIX man pages. AsciiDoc files can be translated to
HTML and DocBook markups using the asciidoc(1) command.''
http://daringfireball.net/projects/markdown/ says
``Markdown is a text-to-HTML conversion tool for web writers. Markdown
allows you to write using an easy-to-read, easy-to-write plain text
format, then convert it to structurally valid XHTML (or HTML).''
So those are not suited for in-source documentation.
They're "lightweight" markup for documentation, very easy to read and somehow
easy to write for non-developers.
The user manual can give you an impression:
http://repo.or.cz/w/git.git?a=blob;f=Documentation/user-manual.txt
I think, this is easier than LyX for users and developers..
Regards,
Stephan
--
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F
next prev parent reply other threads:[~2008-07-31 13:02 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 16:20 Git Community Book Scott Chacon
2008-07-29 16:28 ` Miklos Vajna
2008-07-29 17:09 ` Petr Baudis
2008-07-29 18:30 ` Scott Chacon
2008-07-29 18:42 ` Junio C Hamano
2008-07-29 19:00 ` Julian Phillips
2008-07-29 19:09 ` Junio C Hamano
2008-07-30 13:27 ` markdown 2 man, was " Johannes Schindelin
2008-07-30 19:32 ` Junio C Hamano
2008-07-30 23:48 ` Wincent Colaiuta
2008-07-31 0:13 ` Scott Chacon
2008-07-31 0:30 ` Junio C Hamano
2008-07-31 11:24 ` Abdelrazak Younes
2008-07-31 13:01 ` Stephan Beyer [this message]
2008-07-31 14:13 ` Abdelrazak Younes
2008-07-31 14:33 ` Abdelrazak Younes
2008-07-31 15:09 ` Miklos Vajna
2008-07-31 15:29 ` Abdelrazak Younes
2008-07-31 19:00 ` Miklos Vajna
2008-08-01 0:45 ` Junio C Hamano
2008-08-01 7:11 ` Abdelrazak Younes
2008-08-01 9:46 ` Thomas Rast
2008-08-01 10:19 ` Abdelrazak Younes
2008-07-31 20:57 ` Jan Krüger
2008-08-01 7:50 ` Abdelrazak Younes
2008-08-01 10:45 ` Dmitry Potapov
2008-08-01 11:06 ` Abdelrazak Younes
2008-07-29 19:34 ` Scott Chacon
2008-07-29 19:57 ` Junio C Hamano
2008-07-30 21:39 ` J. Bruce Fields
2008-07-29 17:43 ` Junio C Hamano
2008-07-29 18:25 ` Junio C Hamano
2008-07-29 19:29 ` Scott Chacon
2008-07-29 19:24 ` Scott Chacon
2008-07-29 22:34 ` Daniel Barkalow
2008-07-29 22:47 ` Junio C Hamano
2008-07-30 13:20 ` Bart Trojanowski
2008-07-30 18:27 ` Junio C Hamano
2008-07-30 13:31 ` Bart Trojanowski
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=20080731130101.GC18106@leksak.fem-net \
--to=s-beyer@gmx.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=julian@quantumfyre.co.uk \
--cc=pasky@suse.cz \
--cc=schacon@gmail.com \
--cc=younes@lyx.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 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 NNTP newsgroup(s).