ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Room for comment on the backside of form
Date: Tue, 7 Sep 2010 18:27:38 +0200	[thread overview]
Message-ID: <5346435B-77DB-412C-A7CB-1DF27CE553B9@gmail.com> (raw)
In-Reply-To: <87hbi1wq7t.fsf@linux-lqcw.site>


Am 07.09.2010 um 17:03 schrieb Cecil Westerhof:

> Op dinsdag 7 sep 2010 15:35 CEST schreef Wolfgang Schuster:
> 
>>> I am still trying to make a useful environment for paper feedback
>>> forms. One thing I am trying to do now, is to but lines on the back
>>> for when someone needs more space to give the feedback. For this I
>>> made the following macro:
>>> \def\PageWithComment[#1]{
>>> \page
>>> #1
>>> \crlf\crlf
>>> \thinrules[n=35,inbetween=\vskip1.5ex]
>>> \page
>>> }
>>> 
>>> There are several needed optimisations.
>>> For starters the number of lines is hard coded. Is there a way to
>>> calculate them?
>> 
>> \def\PageWithComment[#1]%
>> {\page
>> #1
>> \blank[2*line]
>> \getnoflines{\dimexpr\pagegoal-\pagetotal-3\lineheight\relax}
>> \thinrules[n=\noflines]
>> \page}
> 
> I tried something like that, but that generated 32 pages. Had properly
> to do with the inbetween.
> 
> I changed it to:
>    \def\PageWithComment[#1]{
>      \page
>      #1
>      \blank
>      {\switchtobodyfont[2.3em]
>       \getnoflines{\dimexpr\pagegoal-\pagetotal-3\lineheight\relax}
>       \thinrules[n=\noflines]
>      }
>      \page}
> 
> For the inbetween by thinrules I use 1.4em, but to get the same space
> I need to use here 2.3em. Do not know why.


The number of lines are calculated with the normal line distance
and your extra space is not taken into account by the calculation.

Instead of changing the fontsize you can change the interlinespace
but for vertical distances you should use ex-values and not em-values.

Here is a variant which use the inbetween key and use the value
for the calculation of the lines:

\def\PageWithComment[#1]%
  {\page
   #1
   \blank[2*line]
   \scratchcounter\dimexpr(\pagegoal-\pagetotal-2\lineheight)/(\dimexpr\lineheight+2.2ex\relax)\relax
   \thinrules[n=\number\scratchcounter,inbetween={\blank[2.2ex]}]
   \page}

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
___________________________________________________________________________________


      reply	other threads:[~2010-09-07 16:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-07 12:26 Cecil Westerhof
2010-09-07 13:35 ` Wolfgang Schuster
2010-09-07 15:03   ` Cecil Westerhof
2010-09-07 16:27     ` Wolfgang Schuster [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=5346435B-77DB-412C-A7CB-1DF27CE553B9@gmail.com \
    --to=schuster.wolfgang@googlemail.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).