ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Andy Thomas <andythomas@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: doublesided wider paragraphs
Date: Tue, 22 May 2012 22:05:03 +0200	[thread overview]
Message-ID: <A81C8042-FB78-43AD-AA43-399E30ED900F@web.de> (raw)
In-Reply-To: <27005B7C-3F28-4FBD-A022-19DBA8220D47@googlemail.com>

This works. Thank you for help.

Andy

On May 22, 2012, at 7:44 PM, Wolfgang Schuster wrote:

> 
> Am 22.05.2012 um 19:29 schrieb Andy Thomas:
> 
>> It only works without my page layout. Did I make a mistake using \setuplayout? With \showframe it looks fine though.
> 
> You’re setting leftmargin to 0pt but I used in my example this value to calculate the additional space. When you set the argument for \doadapt… to a fixed value it will produce the right output but you can get an unexpected output when the fullwidth environment appears at the start of a new page.
> 
> \definepapersize[wissenschaft][width=170mm,height=240mm]
> \setuppapersize [wissenschaft]
> 
> \setuplayout
>  [topspace=40pt,
>   header=0pt,
>   headerdistance=0pt,
>   backspace=42pt,
>   leftmargin=0pt,
>   width=280pt,
>   height=560pt,
>   rightmargindistance=20pt,
>   rightmargin=100pt,
>   footer=0pt]
> 
> \setuppagenumbering[alternative=doublesided]
> 
> \usemodule[annotation]
> 
> \define[2]\FullwidthCommand
>  {\doifoddpageelse
>     {\doadaptrightskip{-120pt}}
>     {\doadaptleftskip {-120pt}}%
>   #2}
> 
> \defineannotation
>  [fullwidth]
>  [alternative=command,
>   command=\FullwidthCommand]
> 
> \starttext \showframe
> 
> \input tufte
> 
> \startfullwidth
> \input tufte
> \stopfullwidth
> 
> \input knuth
> 
> \startfullwidth
> \input tufte
> \stopfullwidth
> 
> \input tufte
> 
> \startfullwidth
> \input tufte
> \stopfullwidth
> 
> \input tufte
> 
> \stoptext
> 
> Wolfgang
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________

___________________________________________________________________________________
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:[~2012-05-22 20:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 16:11 Andy Thomas
2012-05-22 16:52 ` Marco
2012-05-22 16:58   ` Andy Thomas
2012-05-22 17:04 ` Wolfgang Schuster
2012-05-22 17:29   ` Andy Thomas
2012-05-22 17:44     ` Wolfgang Schuster
2012-05-22 20:05       ` Andy Thomas [this message]

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=A81C8042-FB78-43AD-AA43-399E30ED900F@web.de \
    --to=andythomas@web.de \
    --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).