From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Best source of ConTeXt documentation?
Date: Mon, 02 Aug 2004 18:08:14 +0200 [thread overview]
Message-ID: <410E66EE.10802@wxs.nl> (raw)
In-Reply-To: <200408021457.i72Ev94B025117@blue1.Math.Berkeley.EDU>
Paulo Ney de Souza wrote:
>This is one of the sore points of ConTeXt and of the development
>
>
i addition to patricks remarks:
- it would take a lot of effort to keep such a source code repository up
to date and in sync (else too many questions) with the pdf repositoty
- we only publish documented sources
- i want to stimulate users to writ etheir own styles not to mimick
existing ones (i.e. avoid the 'all tex files look the same' problem)
- also: most examples in manuals are typeset using
\startbuffer
...
\stopbuffer
\typebuffer \getbuffer
so ... there are no hidden tricks (unless it would bother/confuse
users); and .. things like cover designs i wanna keep for myself if only
to avoid cutting and pasting
in due time, probably more sources will go on line, but only when i have
a system/method of keeping things in sync; i don't like the idea to go
on-line for each change that i want to make (we only have dsl for half a
year, before that i had to do all on 64 lines which is no fun)
Hans
next prev parent reply other threads:[~2004-08-02 16:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 14:57 Paulo Ney de Souza
2004-08-02 15:46 ` Patrick Gundlach
2004-08-02 23:13 ` Paulo Ney de Souza
2004-08-03 6:31 ` Patrick Gundlach
2004-08-02 16:08 ` Hans Hagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-03 15:13 Paulo Ney de Souza
2004-08-03 17:44 ` Patrick Gundlach
2004-08-03 5:05 Paulo Ney de Souza
2004-08-03 6:40 ` Patrick Gundlach
2004-08-03 9:56 ` Nikolai Weibull
2004-08-03 3:05 skhilji
2004-08-03 6:38 ` Patrick Gundlach
2004-08-03 7:09 ` Hans Hagen
2004-08-02 19:30 Paulo Ney de Souza
2004-08-02 2:55 skhilji
2004-08-01 22:23 Brooks Moses
2004-08-02 1:57 ` Gary Pajer
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=410E66EE.10802@wxs.nl \
--to=pragma@wxs.nl \
--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).