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: problem with \startlines
Date: Mon, 03 Jan 2000 00:34:08 +0100	[thread overview]
Message-ID: <3.0.6.32.20000103003408.007ec7f0@pop.wxs.nl> (raw)
In-Reply-To: <200001021954.UAA07802@ldhpux.immt.pwr.wroc.pl>

Hi, 

>after some times I have problem with \startlines \stoplines:

Can you send me a small test file showing the problem? It more looks like
you've forgotten some ] of } somewhere. 

>And, I think -- after pdftex update, some png and jpg figures gives a 
>error:
>
>floatblocks    : 4 placed
>resolution read from image <./wow05.png>
>figures        : dimensions of ./wow05.png loaded from figurefile itself
>! Dimension too large.

What are the dimensions? You can check it with texutil --fig *.png and look
into texutil.tuf.

You can try to set \traceexternalfigurestrue and see what context reports.
Maybe indeed your png is problematic. 

Pretty low level you can try: \pdfimage{wow05.png} and see what happens then. 

>and the image is includen without scalling.

When using pdtex, context always includes the image at 100% as an xform,
and then scales that form. This is related to object reuse as well as the
fact that in pdf by up/down scaling on forehand one can loose precission. 

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:[~2000-01-02 23:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200001021954.UAA07802@ldhpux.immt.pwr.wroc.pl>
2000-01-02 23:34 ` Hans Hagen [this message]
2000-01-13 21:08 ` Grzegorz Sapijaszko
2000-01-13 21:52   ` Hans Hagen

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=3.0.6.32.20000103003408.007ec7f0@pop.wxs.nl \
    --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).