From: Hans Hagen <pragma@wxs.nl>
Subject: Re: JPEG file couldn't be read
Date: Thu, 29 Jan 2004 09:13:38 +0100 [thread overview]
Message-ID: <6.0.1.1.2.20040129090411.01df0918@server-1> (raw)
In-Reply-To: <20040129060559.GA1101@ruhrau.de>
At 07:05 29/01/2004, you wrote:
>Hartmut Henkel <hartmut_henkel@gmx.de> [Wed, Jan 28, 2004 at 10:40:59PM CET]:
> > On Tue, 27 Jan 2004, Johannes Hüsing wrote:
> >
> > > Error: pdfetex (file ./rimg0016.jpg): reading JPEG image failed
> >
> > Seems there are only a few error possibilities in some function
> > read_jpg_info(). Could you put the image online for checking?
> >
>
>Certainly: http://www.panix.com/~derwisch/elmar/finger.jpg
>
>I have sidestepped the problem by converting the images with help
>of ImageMagick. The resulting JPEG images are processed without
>problems.
On windows this produced a stand alone pdf graphic:
\starttext \startTEXpage \externalfigure[finger.jpg] \stopTEXpage \stoptext
For the brave, the next also works:
\starttext \startTEXpage
\externalfigure[http://www.panix.com/\string~derwisch/elmar/finger.jpg]
\stopTEXpage \stoptext
However, texexec --pdf --fig=c finger.jpg faisl because texutil cannot read
the jpg banner, so there is something with the file.
On the other hand,
identify.rb finger.jpg
gives me:
http://www.pragma-pod.com/downloads/whatever/graphics.pdf
anyhow, you can use
http://www.pragma-pod.com/downloads/whatever/finger.pdf
in your doc (also faster)
Hans
next prev parent reply other threads:[~2004-01-29 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 22:00 Johannes Hüsing
2004-01-28 21:40 ` Hartmut Henkel
2004-01-29 6:05 ` Johannes Hüsing
2004-01-29 8:13 ` Hans Hagen [this message]
2004-01-29 19:01 ` Hartmut Henkel
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=6.0.1.1.2.20040129090411.01df0918@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).