ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: beta demo file
Date: Mon, 05 Jul 1999 15:34:51 +0200	[thread overview]
Message-ID: <3780B47B.858087A@wxs.nl> (raw)

Hi all, 

I posted a demo file at our site (context->context->beta) named
johan.pdf. This file plays a little with a scan of a drawing my little
nephew made me (it's an instruction on how to build a plane). It's an
unfinished document, but it demonstrated some features that will be
present in the next versions of context:

(1) shading: using metapost, context can include native pdf shades and
blends (and some day patterns) as fills; currently Matthew and I are
working out a decent model of defining them; PS support will come later;
this feature will be available later this year; im the demo, the blue
and brown are shaded (a bit rough now, but will be better later). 

(2) alternate images: pdf supports low res screen/high res printing
graphics; this feature is available in the next context/pdftex release;
for some obscure reason, pdf can only handle bitmaps as alternates,
while, as matthew remarked recently, it sometimes makes sense to inlude
a bitmap for viewing and vector for printing (because acrobat viewers do
not anti alias graphics); in the demo one sees graphics at 25% of the
resolution as the ones used for printing; Tobias will make sure this
feature works in GS too. 

(3) backgrounds: well known to some already, mp can be used to define
fancy backgrounds; a next release will provide an interface to MP that
gives access to all layout areas, including the ones between the 25
areas currently supported; in the demo, one can see how multiple areas
are treated as one. 

(4) clipping: one can pinpoint pieces of graphics by applying clipping;
all graphics shown are actually clips, so there are only two graphics
embedded: the low res and teh high res; at the last page one can see
that arbitrary clipping paths are supported; indeed, one can use MP to
provide such an path; later taco will have to sort out the PS way of
doing things.

This file is generated with pdftex version 14. Because some low level
changes are rather fundamental, I strongly suggest to update pdftex as
well as context in tandem. I will upload a new version when Thanh is
updating pdftex. Beware, the new pdftex will not work with the old
context, but within limits the new context will work with old pdftex's.
I will announce the moment for updating both here. 

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------


             reply	other threads:[~1999-07-05 13:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-05 13:34 Hans Hagen [this message]
1999-07-05 19:42 ` Wybo Dekker
1999-07-06  9:53   ` Hans Hagen
1999-07-06  9:55   ` Hans Hagen
1999-07-06 11:33 Erik Frambach

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=3780B47B.858087A@wxs.nl \
    --to=pragma@wxs.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).