ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: David van Diepen <david@diepenvan.nl>
To: ntg-context@ntg.nl
Subject: Introducing myself
Date: Sat, 18 Apr 2020 17:37:07 +0200	[thread overview]
Message-ID: <8bf6482dd859703086ddd8a9aeee331a89d463da.camel@diepenvan.nl> (raw)

Dear everybody,

I don't have a particular question for the moment but I thought it
would be nice to introduce myself as I have just joined the email list.

My name is David van Diepen, 49 years old. I am a process engineer. I
have two children.

A few months ago my son had to prepare his thesis and that's when I
thought latex would be applicable. Very many years ago I learned to
work with latex during my education, so I thought that it wouldn't be
too hard to help him out with that. At the end of the day it actually
was hard work to get to grisps again but after 10 days we had prepared
a very good-looking thesis and that's what counts.

In the line of my work I regularly have to prepare technical documents.
So I thought it's perhaps a good idea to start using latex for that
too. My teamleader has given me some space to do that even though latex
is completely unsupported at work, so I'm doing all that from home. The
first document was recieved quite wel actually. 

As you'll probably understand my collegues have difficulty appreciating
the value of a properly designed document. Everybody seems to agree to
a similar and often poor appearance. I am the son of a graphic
designer, so maybe that's why I do care what the documents I produce
look like. For instance, I have a couple of nice books with examples of
typefaces (letterproeven) lying about that I inherited, these are an
inspiration too. Also I think a well designed document conveys the
content better. So I'm glad that I am allowed start with this
development even though the benefits are very abstract still.

That's when I thought whether it would be a good idea to continue
investing time in latex, or whether it would be better to go with the
new developments, that being the luatex/context combination. So I
thought I should at least give it a try. 

That try was actually harder than I expected. On hindsight I think it
could have been easier if I had found the right channels to
documentation sooner. There is a lot of information on context to be
found but that includes a lot of information that's already superseded.
So a couple of times it took me quite some time before I realized there
was a newer and easier method. Anyway I'm well on my way now with my
first technical ducument in context. The thing I like most about
context is that the structure makes good sense. In latex there have
been so many additions troughout the years that it has become quite
messy really. In the longer run I think the greater array of
possibilities is going to pay off for my purposes too.

So I would like to thank you all for allowing me to use this great
software. I expect that I may post questions in the future because I am
planning to try more things. For now it's maybe a good idea if I put
some contributions in the wiki. As a newby I have struggled at some
points and maybe some howto's with that perspective can be helpful for
other newcomers.

For now, thanks again, yours faithfully, David



___________________________________________________________________________________
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:[~2020-04-18 15:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-18 15:37 David van Diepen [this message]
2020-04-18 18:26 ` Henning Hraban Ramm
2020-04-19  7:36 ` Rudolf Bahr

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=8bf6482dd859703086ddd8a9aeee331a89d463da.camel@diepenvan.nl \
    --to=david@diepenvan.nl \
    --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).