ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: ntg-context@ntg.nl
Subject: Re: general suggestion for ConTeXt documentation
Date: Wed, 8 Aug 2018 18:31:28 +0200	[thread overview]
Message-ID: <91d681f6-6095-3226-18db-95d7ca21fa9b@gmx.es> (raw)
In-Reply-To: <80E517BC-3D98-4687-A7FD-5335A3AE4FA4@fiee.net>

On 08/08/2018 08:50 AM, Henning Hraban Ramm wrote:
> [...]
> I’m also writing a (beginners) book on ConTeXt in German, and I find
> it really hard to decide what I should include. It can’t become a
> reference, a complete one is impossible anyway.

Hi Hraban,

your book will be an important reference, althought it won’t be “the
reference” (I doubt such a thing might exist).

> E.g. I wanted margin notes. Like footnotes, but in the margin. No
> problem if you want them at the bottom. Very hard if you want them like
> marginals, starting in the line of the marker... Is this common enough
> to include it in my book?

I would say this is too specific. But I would provide the explanation in
the wiki.

> As a media designer, who’s also working with InDesign, my focus is of
> course different from a scientist who just wants her thesis
> readable...

I think it is essential to have a wider range of explanations on how to
do things with ConTeXt (or even with computers, but this is a different
topic).

I’m not saying that other approaches are wrong. Just only not everyone
may understand things the same way.

Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
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  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2018-08-08 16:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-06 21:59 footnote and endnote markers aligned with the left margin of the main text Robert Zydenbos
2018-08-07 15:54 ` Pablo Rodriguez
2018-08-07 22:40   ` general suggestion for ConTeXt documentation (was: footnote and endnote markers...) Robert Zydenbos
2018-08-07 22:54     ` Alan Braslau
2018-08-08 13:30       ` Robert Zydenbos
2018-08-08 15:28         ` general suggestion for ConTeXt documentation Pablo Rodriguez
2018-08-09 12:17           ` Robert Zydenbos
2018-08-09 18:15             ` Pablo Rodriguez
2018-08-08 15:54         ` Hans Hagen
2018-08-08 16:12           ` Alan Braslau
2018-08-08  6:18     ` Pablo Rodriguez
2018-08-08  6:50       ` Henning Hraban Ramm
2018-08-08 16:31         ` Pablo Rodriguez [this message]
2018-08-10 15:50           ` Henning Hraban Ramm
2018-08-10 16:38             ` Hans Hagen
2018-08-10 17:16               ` Henning Hraban Ramm
2018-08-10 17:35               ` Alan Braslau
2018-08-11  5:51         ` Jan U. Hasecke
2018-08-08 16:02       ` Hans Hagen

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=91d681f6-6095-3226-18db-95d7ca21fa9b@gmx.es \
    --to=oinos@gmx.es \
    --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).