ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Jonas Baggett <jonasb@tranquille.ch>
To: ntg-context@ntg.nl
Subject: Re: Ideas for improving documentation of ConTeXt
Date: Tue, 11 Oct 2016 23:36:15 +0200	[thread overview]
Message-ID: <577450bb-29f4-dc9c-437b-9c8af8e27c45@tranquille.ch> (raw)
In-Reply-To: <c9505ca1-117a-4382-f35e-ccef42eebab6@wxs.nl>

Le 10. 10. 16 à 09:35, Hans Hagen a écrit :

> Don't worry, no one feels offended. FYI, Pragma is not that large a 
> company so we cannot allocate more resources than we do now (and did 
> the last couple of decades). We just provide the manuals we write in 
> the process and happily leave the rest to others.
> (...)
> Not all old manuals will be updates. There are already a lot in the 
> distribution and another 6 on my disk waiting for an mkiv update. 
> These are often covering a specific aspect. I happily leave writing 
> additional manuals to others.

Good approach, I believe. It is always better to have a community that 
participate to the work instead of doing all the work.
> Each year at the context meeting this topic pops op and there are many 
> plans but a lack of time interferes.
>
> Btw, Alan is writing a larger story for beginners.

Having a good tutorial for beginners will be a good advertisement for 
ConTeXt, I guess.
> The interface is actually rather stable otherwise we could not use it 
> ourselves. However the move to luatex made it possible to kick out 
> code related to input and font encoding as well as update to new 
> technologies so there have been changes. So, the trick is to point new 
> users to the right examples and documentation.

The letter generator was located there in my system : 
/usr/share/texmf/doc/context/base/examplap/gui/letter.pdf. You have 
written previously that the examplap code and examples where mkii. In 
this case, if this would be located there 
/usr/share/texmf/doc/context/base/mkii/examplap/gui/letter.pdf instead, 
in a mkii folder, I would have known at first glance that it is outdated 
documentation. So a quick first improvement could be to put mkii related 
documentation in a mkii folder.

Cheers,
Jonas
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2016-10-11 21:36 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-09 11:18 Jonas Baggett
2016-10-09 13:49 ` Yi Qingliang
2016-10-10  5:21   ` Jonas Baggett
2016-10-09 19:31 ` Henri Menke
2016-10-09 22:49   ` Jonas Baggett
2016-10-10  7:35     ` Hans Hagen
2016-10-11 21:36       ` Jonas Baggett [this message]
2016-10-09 20:51 ` Wolfgang Schuster
2016-10-10  5:43   ` Jonas Baggett
2016-10-10  7:24     ` Hans Hagen
2016-10-11 21:05       ` Jonas Baggett
2016-10-12 11:30       ` Jonas Baggett
2016-10-12 15:29         ` Yi Qingliang
2016-10-12 15:33           ` Mica Semrick
2016-10-12 17:32             ` Jonas Baggett
2016-10-12 17:45               ` Bomber K.
2016-10-12 17:55           ` Bomber K.
2016-10-10  7:57     ` Thomas A. Schmitz
2016-10-10 17:04       ` Jean-Pierre Delange
2016-10-10 17:34         ` Hans Hagen
2016-10-10 21:41         ` Henning Hraban Ramm
2016-10-11  5:20           ` Jean-Pierre Delange
2016-10-12 21:18         ` Jonas Baggett
2016-10-12 10:17       ` Jonas Baggett
2016-10-10  5:32 ` Aditya Mahajan
2016-10-10  5:43   ` Aditya Mahajan
2016-10-11 20:26     ` Jonas Baggett
2016-10-11 20:40       ` Henning Hraban Ramm
2016-10-12 21:27         ` Jonas Baggett
2016-10-13  8:15           ` Henning Hraban Ramm
2016-10-13  9:23             ` Aditya Mahajan

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=577450bb-29f4-dc9c-437b-9c8af8e27c45@tranquille.ch \
    --to=jonasb@tranquille.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).