From: Paulo Ney de Souza <desouza@Math.Berkeley.EDU>
Subject: Re: Re: Best source of ConTeXt documentation?
Date: Mon, 2 Aug 2004 16:13:46 -0700 (PDT) [thread overview]
Message-ID: <200408022313.i72NDkpC006902@blue1.Math.Berkeley.EDU> (raw)
>From ntg-context-bounces@ntg.nl Mon Aug 2 08:46:53 2004
>From: "Patrick Gundlach" <patrick@gundla.ch>
>To: ntg-context@ntg.nl
>Subject: [NTG-context] Re: Best source of ConTeXt documentation?
>
>Oh come on, this is completely crap. The people at PRAGMA (i.e. Hans)
>share ConTeXt, wich is the holy grail that PRAGMA is based on
>(besides the knowledge). It is such a generous gift to the community.
>Please think about if you write stuff like that.
I realize better that you do Hans contibutions to the Open Source community
and I never complained about the sharing of ConTeXt, which is indeed the
best typesetting system I have seen. You are taking my comment into a
completely different context, pun not intended!
>You are right, that not all (only few) manuals are available in .tex
>format. See pdftex manual and the magazines. Putting source
>code online needs time, a lot of time. Source code needs to get
>documented. And I don't know Hans very well, but I'd guess that his
>day only has 24h.
>
>There are already some styles in the ConTeXt wiki. And there are
>styles that come with the distribution.
The discussion is not about styles, it is about examples and how-to.
>Why reverse-engineer? Just cook up the style you want. If you have
>questions doing this, ask on the ConTeXt list. If you are ready, put
>the style onto the Wiki. The styles at pragma are very good, but
>definitely not the only way to go. Making a good style is not
>copy/paste. It is a matter of experience. Experience is something you
>have to gain yourself.
We are not talking about experience and or copy/paste, if you are assuming
that I don't have the experience or that the guy that posted the initial
message wants to copy and paste, again you are on the wrong track.
>And yes, it is time for us to put examples online. But the ConTeXt
>community is still rather small. So there won't be many results in a
>short time.
I certainly will welcome the day we have a minimal how-to posted in there.
>You can do the first step. Go to the wiki, edit a page that states
>your questions regarding style development. Put a table of contents
>or something similar there, which steps you would like to see, which
>things you would like to have explained and so on. After that "we"
>(the more experienced ConTeXt users) can fill in the gaps. And
>finally we all have a small manual on style design. This is much
>better than being so aggressive on the unwillingness to share source.
>
>Patrick
I'll give it a try, the wiki is certainly the way to go ...
Paulo Ney
next prev reply other threads:[~2004-08-02 23:13 UTC|newest]
Thread overview: 7+ 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 [this message]
2004-08-03 6:31 ` Patrick Gundlach
2004-08-02 16:08 ` Hans Hagen
2004-08-03 5:05 Paulo Ney de Souza
2004-08-03 9:56 ` Nikolai Weibull
2004-08-03 10:22 ` Hans Hagen
2004-08-03 15:13 Paulo Ney de Souza
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=200408022313.i72NDkpC006902@blue1.Math.Berkeley.EDU \
--to=desouza@math.berkeley.edu \
--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).