ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: table formatting mystery
Date: Fri, 26 Apr 2013 09:20:39 +0200	[thread overview]
Message-ID: <CAG5iGsBnPcCsZdVPGvLC+7SHDE2m_wAuzn4D0pF0ZvfRvGOzBA@mail.gmail.com> (raw)
In-Reply-To: <CADK45bHQCzunY6PYz7hB+QW6aT=CLP32L1-AfG-wxpdON3DvHw@mail.gmail.com>

On Thu, Apr 25, 2013 at 5:02 PM, Lance Larsen <lance.c.larsen@gmail.com> wrote:
> I created the following table, but I am running into a mysterious
> problem. When I include the text 'Geometry Calulations' in row 2, the
> table row expands as if this text takes up lines of text. However the
> text fits well within the cell length, and the text itself remains on
> one line. If I delete 'Geometry Calculations', the height of row 2 is
> the height of one line of text. How do I fix this? I have included
> snapshots of what I am getting with and without 'Geometry
> Calculations' included. Any help or insight is appreciated.
>
> \setupTABLE[c][1][width=0.16\textwidth]
> \setupTABLE[c][2,3,4][width=0.13\textwidth]
> \setupTABLE[c][5][width=0.20\textwidth, align=middle]
> \setupTABLE[c][6][width=0.25\textwidth, align=middle]
> \bTABLE[width=0.5\textwidth, rulethickness=0.5pt]
> \bTR \bTD[nc=2]   \bf ~\cb Preliminary \cb Final    \eTD
> \bTD[align=middle] \bf Revision \eTD \bTD[align=middle] X \eTD \bTD
> \bf Document ID \eTD \bTD         \DocID         \eTD \eTR
> \bTR \bTD[nc=2]   \bf ~Document Title:  \eTD \bTD[nc=4,align=middle]
>  Geometry Calculations  \eTD \eTR
> \bTR \bTD[nc=2]   \bf ~Originating Discipline:  \eTD
> \bTD[nc=4,align=middle]                               \OrigDisc
>                                               \eTD \eTR
> \bTR \bTD[nc=2]   \bf ~Effective Date:  \eTD \bTD[nc=3]  \tfx  ~\cb
> Approval Date \sp\sp\cb Other: ________   \eTD \bTD
> Page~\pagenumber~of~\totalnumberofpages  \eTD \eTR
> \bTR \bTD         \bf ~Issued for: \eTD \bTD[nc=5,align=middle]
> \tfx Phase 1 Design \cb\sp Phase 2 Design \cb\sp Phase 3 Design \cb\sp
> Input to DCD \cb\sp N/A \cb         \eTD \eTR
> \eTABLE
can you make an example without your own macros like \DocID, \OrigDisc etc. ?



--
luigi
___________________________________________________________________________________
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:[~2013-04-26  7:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25 15:02 Lance Larsen
2013-04-26  7:20 ` luigi scarso [this message]
2013-04-26  7:22 ` Wolfgang Schuster
2013-04-26  7:53 ` luigi scarso
2013-04-29 15:19 Lance Larsen
2013-04-30  6:45 ` Wolfgang Schuster

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=CAG5iGsBnPcCsZdVPGvLC+7SHDE2m_wAuzn4D0pF0ZvfRvGOzBA@mail.gmail.com \
    --to=luigi.scarso@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).