From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/15950 Path: main.gmane.org!not-for-mail From: Siep Kroonenberg Newsgroups: gmane.comp.tex.context Subject: Re: ConTeXt vs. LaTeX Date: Wed, 4 Aug 2004 23:09:01 +0200 Sender: ntg-context-bounces@ntg.nl Message-ID: <20040804210901.GA28298@muisje> References: <4110EDAF.9070508@email.si> <20040804165848.GA10304@fly.srk.fer.hr> Reply-To: Siep Kroonenberg , mailing list for ConTeXt users NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1091653736 17099 80.91.224.253 (4 Aug 2004 21:08:56 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 4 Aug 2004 21:08:56 +0000 (UTC) Original-X-From: ntg-context-bounces@ntg.nl Wed Aug 04 23:08:46 2004 Return-path: Original-Received: from ronja.vet.uu.nl ([131.211.172.88] helo=ronja.ntg.nl) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BsT0A-0000mg-00 for ; Wed, 04 Aug 2004 23:08:46 +0200 Original-Received: from localhost (localhost.localdomain [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 4A02F12772; Wed, 4 Aug 2004 23:08:46 +0200 (CEST) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (ronja.vet.uu.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 01506-01; Wed, 4 Aug 2004 23:08:44 +0200 (CEST) Original-Received: from ronja.vet.uu.nl (localhost.localdomain [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 224A11276C; Wed, 4 Aug 2004 23:08:44 +0200 (CEST) Original-Received: from localhost (localhost.localdomain [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 15BE31276C for ; Wed, 4 Aug 2004 23:08:42 +0200 (CEST) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (ronja.vet.uu.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 01439-02 for ; Wed, 4 Aug 2004 23:08:41 +0200 (CEST) Original-Received: from dep.oprit.rug.nl (unknown [129.125.36.9]) by ronja.ntg.nl (Postfix) with ESMTP id 85D89126F8 for ; Wed, 4 Aug 2004 23:08:41 +0200 (CEST) Original-Received: from client44-3.kabelA.oprit.rug.nl (GN-HE001-COM03-200-159.kabela.oprit.rug.nl [129.125.200.159]) by dep.oprit.rug.nl (8.12.10.Beta2/8.12.10.Beta2) with SMTP id i74L8OS1015015; Wed, 4 Aug 2004 23:08:39 +0200 (MEST) Original-Received: by client44-3.kabelA.oprit.rug.nl (sSMTP sendmail emulation); Wed, 4 Aug 2004 23:09:02 +0200 Original-To: mailing list for ConTeXt users Content-Disposition: inline In-Reply-To: <20040804165848.GA10304@fly.srk.fer.hr> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new at ntg.nl X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.5 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ntg-context-bounces@ntg.nl X-Virus-Scanned: by amavisd-new at ntg.nl Xref: main.gmane.org gmane.comp.tex.context:15950 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:15950 On Wed, Aug 04, 2004 at 06:58:48PM +0200, Zeljko Vrba wrote: > On Wed, Aug 04, 2004 at 04:07:43PM +0200, Mojca Miklavec wrote: > > > > I'm not sure if these are only the problems at the beginning (since I > > have to look for almost any command I use) and would soon disappear or > > would the general advice be "don't use ConTeXt if LaTeX suits your > > needs". What are your opinions about that? Try it for a bit and see whether you like it. Some people find that it makes things simpler and more logical. It is a different way of working, which may or may not suit you. For me personally, somehow Context is a bad match, and it has been fighting all the way. Therefore I use Context only when I have to. > I learned Context because Latex didn't suit my > needs (concrete example: for my diploma work, my mentor required that there > must not be "Chapter" heading for each chapter.. If I put \chapter*, then > it didn't appear in the table of contents.. the solution was dirty - copy > the report class file to local directory and edit it.. however if such a simple > problem has such a dirty solution, how could I cope with tougher problems? The right way to handle this would have been to copy just the relevant code fragment to a package or classfile of your own and modify it. The code would have looked a lot hackier than corresponding Context code, but as long as it sits neatly tucked away in a package of its own, you wouldn't have to let that bother you. LaTeX source code is generally well-documented, and much easier to find your way around in than Context code. For presentations there are pdfscreen and pdfslide, and David Storey has done nteractivestuff with pdf. So don't underestimate the possibilities of LaTeX. -- Siep Kroonenberg