From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: ConTeXt, debian and wiki
Date: Wed, 07 Sep 2005 11:54:30 +0200 [thread overview]
Message-ID: <431EB8D6.7040705@elvenkind.com> (raw)
In-Reply-To: <1126011042.4847.8.camel@yquem.lmt.ens-cachan.fr>
Hi David,
David Marsal wrote:
> Hello,
>
> I would like to specify some stuff about ConTeXt on Debian on the wiki,
> (like tetex3 via apt-get and texfont for the beginning)
>
> Do you prefer a very specific page for Debian or should I put the
> informations on the font page, the tetex3 page etc...
The page subjects tend to be task-based, so in my opinion a single
unified Debian page is not a good idea. If needed, it would be better
to have pages for 'Debian Installation' and 'Debian Fonts'.
On the other hand, an approach I find useful is to start a section
in an already existing page, and only start a separate page when
that page becomes too complex to read and comprehend easily. That
prevents a proliferation of near-empty pages.
The bottom line: Its a wiki. You decide!
Greetings, Taco
prev parent reply other threads:[~2005-09-07 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 12:50 David Marsal
2005-09-07 9:54 ` Taco Hoekwater [this message]
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=431EB8D6.7040705@elvenkind.com \
--to=taco@elvenkind.com \
--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).