ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Layer for all pages and for specific pages
Date: Mon, 6 May 2013 17:06:09 +0200	[thread overview]
Message-ID: <535133AA-A348-41C8-A25B-DBE1B9125408@gmail.com> (raw)
In-Reply-To: <5187B662.5040403@mmnetz.de>


[-- Attachment #1.1: Type: text/plain, Size: 1681 bytes --]


Am 06.05.2013 um 15:55 schrieb H. Özoguz <h.oezoguz@mmnetz.de>:

>> > Hi,
>> > 
>> > I use a vertical line (realized as a layer) for a bilingual project. My question is:
>> > 1. How can I set this line on all pages?
>> 
>> When this is the text where you place both columns with a table you can just enable the rule between both columns.
> 
> Thanks Wolfgang!
> 
> The reason for the use of the layer is the following: If I use frames of the natural table, then I have this:
> 
> \def\arde[#1][#2]{%
> \bTABLE
> \setupTABLE[frame=off]
> \setupTABLE[c][1][rightframe=on]
> \bTR 
> \bTD #1 \eTD
> \bTD #2 \eTD 
> \eTR
> \eTABLE}
> \setuptolerance[tolerant,stretch]
> \starttext
> \arde[\input knuth][\input knuth]
> \arde[\input knuth][\input knuth]
> \stoptext
> 
> There you can see the problem, you have to zoom into the pdf: Between the two tables, there is a tiny tiny (!) space betweeen the vertical lines. Its not a big issue, but it is there.

The space is inserted by TeX when characters in different lines are touching.

You can avoid this when you put everything in a single table. You should also avoid
to use brackets as delimiters for text, use normal braced arguments why can be
grouped without problems.

\startsetups[arde]
  \setupTABLE[c][1][rightframe=on]
\stopsetups

\def\startarde
  {\bTABLE[frame=off,width=.5\textwidth,setups=arde,split=yes]}

\def\stoparde
  {\eTABLE}

\define[2]\arde
  {\bTR
     \bTD#1\eTD
     \bTD#2\eTD 
   \eTR}

\setuptolerance[tolerant,stretch]

\starttext
\startarde
\arde{\input knuth }{\input knuth }
\arde{\input knuth }{\input knuth }
\stoparde
\stoptext

Wolfgang

[-- Attachment #1.2: Type: text/html, Size: 2796 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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-05-06 15:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-06 13:55 "H. Özoguz"
2013-05-06 15:06 ` Wolfgang Schuster [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-05-07  5:49 "H. Özoguz"
2013-05-07 10:38 ` Wolfgang Schuster
2013-05-06  6:26 "H. Özoguz"
2013-05-06 10:19 ` 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=535133AA-A348-41C8-A25B-DBE1B9125408@gmail.com \
    --to=schuster.wolfgang@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).