From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/36739 Path: news.gmane.org!not-for-mail From: "Santy, Michael" Newsgroups: gmane.comp.tex.context Subject: split table widows/orphans and splitting threshold Date: Mon, 24 Sep 2007 08:17:10 -0500 Message-ID: <6703815B292B664DBAEC55EE3192386A20BBA4@poseidon.in.dynetics.com> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1290930385==" X-Trace: sea.gmane.org 1190639886 18398 80.91.229.12 (24 Sep 2007 13:18:06 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 24 Sep 2007 13:18:06 +0000 (UTC) To: Original-X-From: ntg-context-bounces@ntg.nl Mon Sep 24 15:17:58 2007 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 lo.gmane.org with esmtp (Exim 4.50) id 1IZnos-0002iI-P5 for gctc-ntg-context-518@m.gmane.org; Mon, 24 Sep 2007 15:17:50 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 66B771FCE9; Mon, 24 Sep 2007 15:17:46 +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 15710-10; Mon, 24 Sep 2007 15:17:34 +0200 (CEST) Original-Received: from ronja.vet.uu.nl (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id CEC101FCDF; Mon, 24 Sep 2007 15:17:33 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 8DA9F1FCDF for ; Mon, 24 Sep 2007 15:17:30 +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 15669-02 for ; Mon, 24 Sep 2007 15:17:25 +0200 (CEST) Original-Received: from myrddin.dynetics.com (myrddin.dynetics.com [204.154.192.33]) by ronja.ntg.nl (Postfix) with ESMTP id C934F1FCD9 for ; Mon, 24 Sep 2007 15:17:24 +0200 (CEST) Original-Received: from poseidon.in.dynetics.com ([10.1.15.106]) by myrddin.dynetics.com (8.13.1/8.13.1) with ESMTP id l8ODEAGW001972 for ; Mon, 24 Sep 2007 08:14:11 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: split table widows/orphans and splitting threshold Thread-Index: Acf+rTajC/KKX9usS6mN40jHLkIOOg== X-dynetics.com-MailScanner-Information: Please contact the ISP for more information X-dynetics.com-MailScanner: Found to be clean X-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1.439, required 2, autolearn=disabled, ALL_TRUSTED -1.44, HTML_MESSAGE 0.00) X-MailScanner-From: michael.santy@dynetics.com X-Virus-Scanned: amavisd-new at ntg.nl X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.9 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:36739 Archived-At: This is a multi-part message in MIME format. --===============1290930385== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C7FEAD.36AEFDE7" This is a multi-part message in MIME format. ------_=_NextPart_001_01C7FEAD.36AEFDE7 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, I'm using ConTeXt as part of a XML -> PDF workflow for technical = documentation. These documents often have large tables, so I am using = "placetable[split]" for table placement. While placetable[split] works = as advertised, the output quality often suffers. One of the issues that = I've found is that you'll often see a table with one row on a separate = page from the rest of the table. Is there any way to control table = orphans and widows such that there will never be just one (or some = arbitrary number) rows of a table split across a page. Another feature that I think would be useful is the ability to set a = split threshold for a table. In my use, tables that are less than 1/3 = to 1/2 page should probably be included as a float (i.e., not split), = whereas tables larger than this would benefit from being split. Is it = possible to add a new placement option for tables that includes a = splitting threshold? I would add this as part of my XML->TeX transform, = but I don't think the rendering path has enough information to know how = large table rows will be when rendered. Any thoughts? Cheers, Mike =20 ------_=_NextPart_001_01C7FEAD.36AEFDE7 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable split table widows/orphans and splitting threshold

Hello,

I'm using ConTeXt as part of a XML -> PDF workflow for technical = documentation.  These documents often have large tables, so I am = using "placetable[split]" for table placement.  While = placetable[split] works as advertised, the output quality often = suffers.  One of the issues that I've found is that you'll often = see a table with one row on a separate page from the rest of the = table.  Is there any way to control table orphans and widows such = that there will never be just one (or some arbitrary number) rows of a = table split across a page.

Another feature that I think would be useful is the ability to set a = split threshold for a table.  In my use, tables that are less than = 1/3 to 1/2 page should probably be included as a float (i.e., not = split), whereas tables larger than this would benefit from being = split.  Is it possible to add a new placement option for tables = that includes a splitting threshold?  I would add this as part of = my XML->TeX transform, but I don't think the rendering path has = enough information to know how large table rows will be when = rendered.

Any thoughts?

Cheers,
Mike  

------_=_NextPart_001_01C7FEAD.36AEFDE7-- --===============1290930385== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________________________________________ 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 : https://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net ___________________________________________________________________________________ --===============1290930385==--