ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Manuel P." <ayeye.sysforge@gmail.com>
To: context-ml <ntg-context@ntg.nl>
Subject: Using ConTeXt for a thesis?
Date: Sat, 19 Dec 2009 14:55:31 +0100	[thread overview]
Message-ID: <4B2CDB53.8040305@gmail.com> (raw)

Hi everyone! This is my first post here.

I've a limited (but sufficient) experience with LaTeX (I've written 
several work-related documents with it) and now I have to write my 
undergraduate thesis (the deadline is mid-january 2010). I've been fairy 
impressed by a book typesetted with ConTeXt, so I used it for some 
documents and liked the idea and the configurability. The possibility of 
having a unique and personalized look-and-feel for every document is 
very appealing to me, and I have already began to assemble a style for 
the thesis.

However, I've a very limited experience with it and I wonder: is ConTeXt 
the right choice in my circumstances? Can it be used without a degree in 
typography? I can't write half thesis and then stumble on some obscure 
(to me) typesetting problem, things have to be smooth and I need to 
concentrate on content (but I still find desiderable a good unique 
look). When I have a problem I try my best to resolve it by myself, but 
given the limited time I can't learn and investigate everything, so if 
I'll write my thesis in ConTeXt in some (desperate) cases I'll need your 
help.

What do you think?

Thank you all!

PS: I live in Italy, sorry for my probably imperfect english!

___________________________________________________________________________________
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:[~2009-12-19 13:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-19 13:55 Manuel P. [this message]
2009-12-19 14:08 ` Hans Hagen
2009-12-19 15:21 ` George N. White III
2009-12-19 21:10   ` Manuel P.
2009-12-20  3:52     ` Aditya Mahajan
2009-12-20 10:14       ` Peter Münster
2009-12-20 16:33         ` \wordright{…} and hyphens Andreas Harder
2009-12-20 23:08         ` extra kerning do nothing Andreas Harder
2009-12-21 12:40           ` Hans Hagen
2009-12-21 13:21             ` Andreas Harder
2009-12-21 15:55               ` Hans Hagen
2009-12-21 16:23                 ` Andreas Harder
2009-12-21 16:34                   ` Hans Hagen
2009-12-21 16:49                     ` Andreas Harder
2009-12-21 17:01                       ` Hans Hagen
2009-12-20 12:38       ` Using ConTeXt for a thesis? Manuel P.
2009-12-20  7:09     ` Mojca Miklavec
2009-12-20 12:42       ` Manuel P.
2009-12-20 12:57         ` John Haltiwanger
2009-12-20 17:12           ` Manuel P.
2009-12-20 19:15             ` luigi scarso
2009-12-21  0:40               ` Curiouslearn
2009-12-21 12:05                 ` Manuel P.
2009-12-21 11:28     ` mode=node and ligatures Andreas Harder

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=4B2CDB53.8040305@gmail.com \
    --to=ayeye.sysforge@gmail.com \
    --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).