From: "Patrick Gundlach" <patrick@gundla.ch>
Subject: Re: Need more documentation on tables
Date: 15 Sep 2005 11:44:22 +0200 [thread overview]
Message-ID: <m2aciefyx5.fsf@levana.de> (raw)
In-Reply-To: <17010687280.20050911152340@iol.it> (Giuseppe Bilotta's message of "Sun, 11 Sep 2005 15:23:40 +0200")
[...]
> Should I write some documentation about TaBlE preambles and
> commands (for the Wiki),
Giuseppe, please do so.
> or would it be against some rule about its ($$$) documentation?
I doubt that there is any law that prohibits writing a documentation
from scratch.
Patrick
--
ConTeXt wiki and more: http://contextgarden.net
next prev parent reply other threads:[~2005-09-15 9:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 17:23 Giuseppe Bilotta
2005-09-11 13:23 ` Giuseppe Bilotta
2005-09-11 18:12 ` Hans Hagen
2005-09-15 9:44 ` Patrick Gundlach [this message]
2005-09-19 10:57 ` Giuseppe Bilotta
2005-09-12 11:07 ` Hans Hagen
2005-09-12 14:35 ` Re[2]: " Giuseppe Bilotta
2005-09-14 17:38 ` Re[3]: " Giuseppe Bilotta
2005-09-15 21:31 ` Hans Hagen
2005-09-16 13:47 ` Re[2]: " Giuseppe Bilotta
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=m2aciefyx5.fsf@levana.de \
--to=patrick@gundla.ch \
--cc=ntg-context@ntg.nl \
/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).