From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/30420 Path: news.gmane.org!not-for-mail From: "Mojca Miklavec" Newsgroups: gmane.comp.tex.context Subject: Re: Bold rules with TABLE Date: Mon, 21 Aug 2006 18:32:12 +0200 Message-ID: <6faad9f00608210932m520e95dbmb63d2195056410ce@mail.gmail.com> References: Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1156177982 14472 80.91.229.2 (21 Aug 2006 16:33:02 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 21 Aug 2006 16:33:02 +0000 (UTC) Original-X-From: ntg-context-bounces@ntg.nl Mon Aug 21 18:33:00 2006 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from ronja.vet.uu.nl ([131.211.172.88] helo=ronja.ntg.nl) by ciao.gmane.org with esmtp (Exim 4.43) id 1GFChb-0005Yu-8M for gctc-ntg-context-518@m.gmane.org; Mon, 21 Aug 2006 18:32:39 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id BC0E41FBB9; Mon, 21 Aug 2006 18:32:38 +0200 (CEST) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 22745-01; Mon, 21 Aug 2006 18:32:27 +0200 (CEST) Original-Received: from ronja.vet.uu.nl (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 3A1DF1FDF9; Mon, 21 Aug 2006 18:32:27 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 2E3CC1FDF9 for ; Mon, 21 Aug 2006 18:32:22 +0200 (CEST) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20936-04 for ; Mon, 21 Aug 2006 18:32:15 +0200 (CEST) Original-Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by ronja.ntg.nl (Postfix) with SMTP id 5B7591FDEA for ; Mon, 21 Aug 2006 18:32:13 +0200 (CEST) Original-Received: by nf-out-0910.google.com with SMTP id d4so410473nfe for ; Mon, 21 Aug 2006 09:32:12 -0700 (PDT) Original-Received: by 10.49.21.8 with SMTP id y8mr7928951nfi; Mon, 21 Aug 2006 09:32:12 -0700 (PDT) Original-Received: by 10.78.175.15 with HTTP; Mon, 21 Aug 2006 09:32:12 -0700 (PDT) Original-To: "mailing list for ConTeXt users" In-Reply-To: Content-Disposition: inline X-Virus-Scanned: amavisd-new at ntg.nl X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.7 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl X-Virus-Scanned: amavisd-new at ntg.nl Xref: news.gmane.org gmane.comp.tex.context:30420 Archived-At: On 8/17/06, Fredrik Sjunnesson wrote: > Hi, > > As this is my first mail to the list I'd like to start by thanking Hans > and all other ConTeXt contributors. I stumbled upon ConTeXt just > recently and I have fallen in love badly. :) > > Now to my question. > > Is it possible to control the rule thickness of a specific frames with > TABLE, i.e. something like > > \setupTABLE[row][1][bottomframe=1pt] > \setupTABLE[column][1][leftframe=2pt] > > If not, I'd guess it could be possible to fake this by inserting extra > rows and columns with zero height and width, respectively, and use the > rulethickness parameter to change the thickness of all their frames. > Since this approach would add extra complexity to the table definitions > I hope that you have better solutions. Unless I have missed something (I would be glad if I would), there is no support for that yet. You could either do: \setupTABLE[row][1][frame=off,bottomframe=on,rulethickness=1pt] or \setupTABLE[column][1][leftframe=on,rulethickness=2pt] but none of that is what you really want. Table building macros depend highly on \framed. And there are at least two feature requests I know of that have been around for quite some time now: 1. Support for setting different leftoffset/rightoffset/topoffset/bottomoffset (natural tables look ugly to me just because they have too little left/rightoofset and too big top/bottomoffset) Framedcontent supports that already, but cannot be used as a replacement in tables. 2. Support for different line widths (or colors or whatever) for left/right/top/bottom line. Some special care should be taken on borders of course. There is a workaround for your problem though: you can draw a frame in metapost (where you can draw arbitrary lines around the cell) and then use that frame as a background for the cells, but that's an extremely lengthy and cumbersome solution for such a standard and well-defined need. I would vote for both of the features if Hans or someone else would manage to implement them. One of the problems might be that \framed is used very often and it is not desireble to have too much overhelm in it, but I would really be very happy if functionality like that would be made available for the usage in tables. Mojca