ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Christopher Creutzig <christopher@creutzig.de>
Subject: Re: I need some advices/guidelines before start writing my PhD thesis
Date: Fri, 17 Jun 2005 12:57:09 +0200	[thread overview]
Message-ID: <42B2AC85.8020802@creutzig.de> (raw)
In-Reply-To: <000c01c57321$d95ad1d0$bb1c8453@CasaAlex>

Alexandra Ribeiro wrote:

> At this moment I’ve to make a choice: continue using Word or start 
> learning a new tool, which will probably consume much of my time. So, 
> I’m in a dilemma. That’s why I’m asking for help.

  Off the top of my head, I'd say you have to ask yourself at least the 
following questions:

- How much time are you willing to spend on a tool?
- How much do you *really* bother about the final appearance?
- What formats is your PhD advisor happy with?
- Assuming you would like to reuse some parts of your thesis for
   independent publications, what formats do the journals in your
   field accept?
- How much help do you need when learning?  How much of this
   can come from a mailing list (and its archives), how much
   must be presented in book format and how much face-to-face
   introduction do you need?  What do people around you know
   and use?

> Is it really worth learning Context? I mean, does this package deal 

  It depends.  For me, definitely, but I've long reached the area in 
LaTeX where doing what I want to do means hacking around the design 
limitations of that system – and that probably implies that I'll have a 
hard time being satisfied by InDesign, OOo or whatever program limited 
by the WYSIWYG approach.

> efficiently with some important things like TOC, cross-references, 
> bibliography, figures, math, …?

  Certainly.  (You did not mention footnotes and multiple indices, but I 
regard those as crucial in any typesetting tool, too.)

>                                 Is it too hard to learn (for a mere 
> mortal, of course)?

  It depends.  The worst thing about ConTeXt is its almost complete lack 
of error diagnostics.  Forget a curly brace somewhere or mistype the 
name of an option and you'll probably spend hours looking for it, the 
first couple of times.  It certainly helps to have some programming 
experience.

>                      What about support for different languages, in 
> particular for Portuguese?

  I don't know any Portuguese, but multiple languages are supported.

> If I choose Context, can some somebody give me some guidelines/advices?

  Do read the manual.  Print it and have it next to your computer.  Make 
notes in there.

  After reading the manual, go to contextgarden.net and click on “Random 
Page” a couple of times.  Do this every morning – you will find a lot of 
things which are completely irrelevant to you (and solve problems of 
others, which is why they are there), but the occasional gem is worth 
the time.


Christopher

  reply	other threads:[~2005-06-17 10:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-17  9:49 Alexandra Ribeiro
2005-06-17 10:57 ` Christopher Creutzig [this message]
2005-06-17 11:22 ` Jörg Hagmann
2005-06-17 12:02 ` luigi.scarso
2005-06-18 14:18 ` Willi Egger
2005-06-18 16:06 ` Peter Münster
2005-06-19 16:27   ` Henning Hraban Ramm
2005-06-19 22:33     ` Peter Münster
2005-06-20  7:11     ` andrea valle
2005-06-20  7:24       ` andrea valle
2005-06-20 17:52 ` Peter Münster
2005-06-20 16:52 Alexandra Ribeiro

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=42B2AC85.8020802@creutzig.de \
    --to=christopher@creutzig.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).