ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Piotr Kopszak <kopszak@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Thoughts on ConTeXt: ditched
Date: Sun, 3 Jan 2010 19:45:54 +0100	[thread overview]
Message-ID: <d56d340e1001031045r369d376n190c8d65275abd9f@mail.gmail.com> (raw)
In-Reply-To: <4B39FCC5.9080500@gmail.com>

Well, well,

ConTeXt can help you if you give him a little love and don't try pull
all triggers at once. Having written my Ph.D. in LaTeX and published
couple of books in ConTeXT I can assure you, ConTeXt is surprisingly
better suited  for "scientific" texts (oops sorry, I  just mean text
with footnotes, bibliography,  a couple of indexes, list of
illustrations, definitions whatever) even if you disregard its
typographic quality. That's of course my entirely subjective opinion.

Piotr

2009/12/29 Manuel P. <ayeye.sysforge@gmail.com>:
> Il 29/12/2009 3.48, berend@pobox.com ha scritto:
>>
>>     Manuel>  Another "problem" is the "fluidity" of ConTeXt: it changes
>>     Manuel>  rapidly and the documentation is left behind.
>>
>> Maybe for some things, but I'm using a manual from 2004 and from my
>> point of view very little has changed.
>>
>> I would say the interface is remarkably stable, so hopefully that
>> might be some encouragement to come back one day.
>>
>>
>
> Sure!
>
> --
> Manuel P.
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>



-- 
http://okle.pl
___________________________________________________________________________________
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:[~2010-01-03 18:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-27 15:54 Manuel P.
2009-12-27 18:41 ` Wolfgang Schuster
2009-12-28 13:44   ` Manuel P.
2009-12-28 15:12     ` Khaled Hosny
2009-12-28 17:59     ` Hans Hagen
2009-12-29 12:48       ` Manuel P.
2009-12-29  2:48     ` berend
2009-12-29 12:57       ` Manuel P.
2010-01-03 18:45         ` Piotr Kopszak [this message]
2010-01-04 21:46           ` Manuel P.
2009-12-27 19:16 ` Peter Münster
2009-12-27 21:11   ` Hans Hagen
2009-12-28 13:48   ` Manuel P.
2009-12-28 17:19     ` Peter Münster
2009-12-28 11:30 ` Gour
2009-12-28 12:36 ` R. Bastian

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=d56d340e1001031045r369d376n190c8d65275abd9f@mail.gmail.com \
    --to=kopszak@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).