ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Request for arbitrary n-by-m printing setup.
Date: Mon, 04 Mar 2002 08:44:40 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20020304084108.02b2c680@server-1> (raw)
In-Reply-To: <02022717361000.08926@gaia>

At 05:36 PM 2/27/2002 -0600, Daniel Joyce wrote:
>         Okay, after sturggling to make business cards with a graphic in 
> them, and
>finding that embedding a placefigure inside a frame inside a combination
>yields inconsistent and unfixable results (1), I finally got it working
>using combinations, frames, and figuretext. Figuretext is less flexible
>than placefigure, but fixes the problem mention in (1), IE, the weird
>tabbing down/over of other placefigures.
>
>         1) Fix placefigure so it works inside combination, and other 
> placefigures.
>externalgraphic does work inside combinations, buuut, you can't have
>laid-out out text inside a external graphic... Maybe I should try
>tex-graphics?

floats (and fixed floats are also floats) will float when needed, and make 
decisions based on the curren tpag estate, so it will alwaye be a problem 
to use them inside boxes

>         2) Allow arbitrary n-by-m pagesetups for printing. Businesscards 
> come out
>as punchouts 2 wide by 5 deep on a US letter page. If I could define a
>'business' card page and then lay them out for printing on such a page, I
>would have had to use the frame/combination kludge. As it is, I had to
>define a frame 3.5x2 inches, put my text & graphics in that, then put the
>frames inside a combination. Works, but it's messy.

this is there

\definepapersize[BC][width=3.5in,height=2in]
\setupapersize[BC][letter]
\setuplayout[nx=3,ny=6] % or so

will give you small pages (this is the way we do our business cards

>         (1) By unfixable, the very first text/graphic would be layed out 
> properly
>inside the combination, but all the others would be moved down or over a
>set amount. What's funny is the frames would stay put, but the
>text/graphics inside would be moved down/out of the frames! Frames don't
>seem to contain their contents very well. No amount of twiddling with
>combination, frames, or placefigure settings fixed this.  Frames also don't
>seem to 'wrap' their contents very well. I needed the frame because I
>needed it to make sure that each part of the 2*5 combination was exactly
>3.5x2inches so it'd match up with the perfs.

see (1)

Hans
-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
                                   fall-back web server: 
www.pragma-pod.nl
-------------------------------------------------------------------------


      parent reply	other threads:[~2002-03-04  7:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27 23:36 Daniel Joyce
2002-02-28  8:36 ` Hans Hagen
2002-03-04  7:44 ` Hans Hagen [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=5.1.0.14.1.20020304084108.02b2c680@server-1 \
    --to=pragma@wxs.nl \
    --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).