From: "Jan U. Hasecke" <juh+ntg-context@mailbox.org>
To: ntg-context@ntg.nl
Subject: documentation sprint at 10th ConTeXt meeting
Date: Mon, 25 Jan 2016 15:44:47 +0100 [thread overview]
Message-ID: <56A634DF.3080505@mailbox.org> (raw)
Dear list,
are there any plans to have a documentation sprint at Kalenberg?
I am currently trying to setup a small documentation about ConTeXt in
order to better learn how to use it, and I face several issues.
1. documentation is scattered. Sources of documentation are the Wiki and
a lot of PDF documents.
2. it is not always possible to decide whether a pdf document is related
to MKII or MKIV. So I start reading only to learn that it is outdated.
3. I had the hope to access all commands via the xml interface mechanism
(showsetup) which could be a kind of auto generated documentation
(using: mtxrun --script server --auto) but it seems that not all
commands are accessible through this mechanism
I would like to propose a documentation sprint at the meeting in
Kalenberg this fall to improve the situation.
juh
--
Software-Dokumentation mit Sphinx
http://www.amazon.de/dp/1497448689/
Paperback: 224 Seiten
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2016-01-25 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 14:44 Jan U. Hasecke [this message]
2016-01-25 14:55 ` Wolfgang Schuster
2016-01-25 15:17 ` Jan U. Hasecke
2016-01-25 16:44 ` Hans Hagen
2016-01-25 17:20 ` Alan BRASLAU
2016-01-25 18:36 ` Jan U. Hasecke
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=56A634DF.3080505@mailbox.org \
--to=juh+ntg-context@mailbox.org \
--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).