ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: luigi scarso <luigi.scarso@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: jpeg problem: Dimension too large
Date: Tue, 10 Mar 2015 09:35:01 +0100	[thread overview]
Message-ID: <CAG5iGsDc5PL53=xPFq=+yhJ=cbDdu03yz07RVqgJDBUpXcvHaQ@mail.gmail.com> (raw)
In-Reply-To: <20150309211828.GA18849@hl.fritz.box>


[-- Attachment #1.1: Type: text/plain, Size: 1700 bytes --]

On Mon, Mar 9, 2015 at 10:18 PM, Harald Koenig <
koenig@tat.physik.uni-tuebingen.de> wrote:

> Hi,
>
> and here a 1st problem including (some) JPGs which are created/converted
> using "convert"
> from ImageMagick (using ImageMagick-6.8.6.9-2.28.1.x86_64 from openSUSE
> 13.1 -- just in case...)
>
> btw. -- I'm using a decent standalone context installation, full log file
> attached...
>
> running "context j1.tex" I get
>
>         LuaTeX warning: arithmetic: number too big
>         graphics        > inclusion > limiting natural dimensions of
> './IMG_9712c1_bad.jpg' (height)
>
>         tex error       > error on line 1 in file
> /home/harald/tex/Indien-2015/j1.tex: ! Dimension too large
>
> for "IMG_9712c1_bad.jpg" which was generated with this command:
>
>      convert -resize 632x330 IMG_9712c1_ok.jpg IMG_9712c1_bad.jpg
>
>
> using other tools I can't find any problem with that "bad" jpg, only
> context complains:-(
>
> what's wrong with "IMG_9712c1_bad.jpg" ?also with pdftex
>

also with pdftex:

figures         : dimensions of IMG_9712c1_ok loaded from figurefile itself


pdfTeX warning: pdftex: arithmetic: number too big
 <./IMG_9712c1_bad.jpg>
! Dimension too large.
<to be read again>
                   >
\setanalyzedfiguredimensions ...lyzedfigurewidth >
                                                  \zeropoint \ifdim
\analyze...

\doanalyzefiguredimensionsinternal ...ions \!!ten
                                                  \fi
<argument> ...}\doanalyzefiguredimensionsinternal

\doanalyzefiguredimensions...

\firstoftwoarguments #1#2->#1

\dododoanalyzeunknownfiguretype ...guredimensions
                                                  \fi
...

-- 
luigi

[-- Attachment #1.2: Type: text/html, Size: 2843 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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:[~2015-03-10  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 21:18 Harald Koenig
2015-03-10  8:35 ` luigi scarso [this message]
2015-03-10  8:42 ` Hans Hagen
2015-03-10  8:51 ` Hans Hagen
2015-03-10  9:30   ` luigi scarso

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='CAG5iGsDc5PL53=xPFq=+yhJ=cbDdu03yz07RVqgJDBUpXcvHaQ@mail.gmail.com' \
    --to=luigi.scarso@gmail.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).