ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Malte Stien <malte@stien.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Learning ConTeXt from the Ground Up
Date: Fri, 14 Jun 2013 15:19:44 +1000	[thread overview]
Message-ID: <79333642-1A64-4BB5-89A6-B0153EB56AA4@stien.de> (raw)

Hello Everyone,

I have been using ConTeXt for over a year now and worked out how to do most things I need to do. Every now and then, though, I need to do something that I cannot find any information about and in most cases I post a question here on the forum. I have received great help here over the months and like to thank everyone who took the time to answer my questions. The other day, however, I had a problem, posted a message here, got an answer and the answer did not quite work; I went back to the forum, got more help...

In the process I realised that I should have been able to work this out myself; I was not even able to tweak the first answer and make it work. I am an IT engineer myself, but with little time (I guess I am not unique here) and even less experience in TeX. I guess what I am saying is, that I would like to gain a much deeper understanding of ConTeXt which will allow me to "program" in ConTeXt rather than just using the documented command.

To gather information about ConTeXt I have
- read the ConTeXt Reference Manual (http://pmrb.free.fr/contextref.pdf)
- bought a couple of the published books by Hans Hagen
- started reading the "TeX book" by Donald Knuth

I have even briefly flirted with the idea of switching to LaTeX mainly because it would mean having a lot more literature and a broader community at my disposal. However, I just prefer the command structure and output of ConTeXt. Can anyone relate to my problem? Am I on the right track? What else should I be doing or reading to really break into ConTeXt?

Regards,
Malte.

PS: Just to be clear; I don't mean for the above to be conceived as shortcomings of ConTeXt, rather I think of them as shortcomings of myself. The developers of ConTeXt have done a fantastic job and I really enjoy writing in ConTeXt and looking at the output.

--
“The Electric Monk was a labour-saving device, like a dishwasher or a video recorder... Electric Monks believed things for you, thus saving you what was becoming an increasingly onerous task, that of believing all the things the world expected you to believe.”

― Douglas Adams, Dirk Gently's Holistic Detective Agency

___________________________________________________________________________________
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
___________________________________________________________________________________

             reply	other threads:[~2013-06-14  5:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-14  5:19 Malte Stien [this message]
2013-06-14  7:17 ` luigi scarso
2013-06-14  7:46   ` Hans Hagen
2013-06-14  7:41 ` Procházka Lukáš Ing. - Pontex s. r. o.
2013-06-16  8:56 ` Dmitriy Tokarev

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=79333642-1A64-4BB5-89A6-B0153EB56AA4@stien.de \
    --to=malte@stien.de \
    --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).