PNG support
Michael n Alison
running GIMP version 1.2 on a Whinedows 98 system. GIMP itself doesn't seem
to be bothered too much about it, it usually prompts me to export it for
transparency & such, but I get no errors on conversion. However, the final
.png image is unviewable? I thought I saw a blip on the png website itself
about a bug or similar in some versions of the plugins, any info on this
from anyone, & any possible fixes?
Thx In Advance,
/*MM*/
--en bocca cerrada no entran moscas
mgma...@OMAAC.com 816.777.1842
Jean-Louis HAMEL
Michael n Alison a écrit :
>
> I seem to be having trouble saving files to a .png format. I am currently
> running GIMP version 1.2 on a Whinedows 98 system. GIMP itself doesn't seem
> to be bothered too much about it, it usually prompts me to export it for
> transparency & such, but I get no errors on conversion. However, the final
> .png image is unviewable? I thought I saw a blip on the png website itself
> about a bug or similar in some versions of the plugins, any info on this
> from anyone, & any possible fixes?
> Thx In Advance,
> /*MM*/
>
I run GIMP 1.2 on Win 98 SE and the png (and other formats) files are
OK...
Have you tryied some other format ?
(I am using an ATI Rage Fury video card with the last driver)
JLH
Simon Lemieux
>
> I seem to be having trouble saving files to a .png format. I am currently
> running GIMP version 1.2 on a Whinedows 98 system. GIMP itself doesn't seem
> to be bothered too much about it, it usually prompts me to export it for
> transparency & such, but I get no errors on conversion. However, the final
> .png image is unviewable? I thought I saw a blip on the png website itself
> about a bug or similar in some versions of the plugins, any info on this
> from anyone, & any possible fixes?
> Thx In Advance,
From my point of view, GIMP is supposed to use a different coding library for
PNGs than the libPNG that all other programs uses... I think the code is just
about the same under windows or linux as for PNG support.... But I also have
problem while reading PNG that were written by GIMP.
I posted something about it here and got no answers...
--
|| 'How do you know I'm mad?' said Alice.
|| 'You must be,' said the Cat, 'or you wouldn't have come here.'
--
Simon Lemieux (lemieu...@yahoo.com)
Michael n Alison
I am only having this problem only reading the file in Internet Explorer
5.50, in my Netscape Communicator 4.7 & Navigator 6.0 the image is readable,
again I am using GIMP v1.2 WIN32 on a Win98 SE platform. My IE has no
trouble reading .png files in general, just ones I make =)
Maybe that will help narrow it down?
Thanks again
/*MM*/
--
Olivier Ripoll
> OK, new discovery....
> I am only having this problem only reading the file in Internet Explorer
> 5.50, in my Netscape Communicator 4.7 & Navigator 6.0 the image is readable,
> again I am using GIMP v1.2 WIN32 on a Win98 SE platform. My IE has no
> trouble reading .png files in general, just ones I make =)
> Maybe that will help narrow it down?
> Thanks again
> /*MM*/
> --
Yes, this helps greatly. It really does not look as a bug of gimp, but a bug of
internet explorer. Send a bug report to microsoft. :)
Simon Lemieux
>
> Yes, this helps greatly. It really does not look as a bug of gimp, but a bug of
> internet explorer. Send a bug report to microsoft. :)
As I said, Gimp does has a bug for creating PNGs, but in this case, I doubt the
bug I'm talking about is the cause of this problem!
I was wondering if you tried with and without interlacing, compression, etc...
Michael n Alison
view png's across the 'net, not locally. I hear there's a registry fix but
haven't found it yet, if I do, I'll send it along to the NG.
Incidentally to anyone out there involved in web programming, just learned
this a.m. that IE 6.0 Beta is out at MS,
http://www.microsoft.com/windows/ie/preview/default.asp
good a whole new batch of bugs to learn to write for.
Many thanks.
/*MM*/
--it's not a bug, it's a feature
mgma...@OMAAC.com 816.777.1842
Simon Lemieux <lemieu...@yahoo.com> wrote in message
news:3B28D39F...@yahoo.com...
Olivier Ripoll
> Olivier Ripoll wrote:
> >
> > Yes, this helps greatly. It really does not look as a bug of gimp, but a bug of
> > internet explorer. Send a bug report to microsoft. :)
>
> As I said, Gimp does has a bug for creating PNGs, but in this case, I doubt the
> bug I'm talking about is the cause of this problem!
>
> I was wondering if you tried with and without interlacing, compression, etc...
>
If you are so sure there IS a bug in creating png, and if it's not the "open gif,
save png, transparency dissappears" bug (which I don't seem to be able to reproduce
and already has a simple workaround), then you should make a bug report:
http://bugzilla.gnome.org
I'm using png very often, indexed or not, w or w/o transparency, and have yet to find
a problem with gimp.
Sincerely,
Olivier.
DGiunti
<m.ma...@netzero.net> writes:
>I seem to be having trouble saving files to a .png format. I am currently
>running GIMP version 1.2 on a Whinedows 98 system. GIMP itself doesn't seem
>to be bothered too much about it, it usually prompts me to export it for
>transparency & such, but I get no errors on conversion. However, the final
>.png image is unviewable? I thought I saw a blip on the png website itself
>about a bug or similar in some versions of the plugins, any info on this
>from anyone, & any possible fixes?
I have a PNG problem similar to yours, but I know what caused the errors for
me. I installed a trial version of Paint Shop Pro and it hijacked the PNG
extension. I did not keep that editor, but there appears to be no way to
easily recover use of the extension. It need more than a file association of
PNG with explorer.
To fix my problem I would have to either reinstall the OS or find and
transcribe the exact registry entries which include lots fields of what appears
to be gibberish. I had a similar problem with JPGs and explorer, but
fortunately there was an undisturbed association with JPEG to copy.
Unfortunately I don't know anyone else with W98 that I could copy this from.
David Giunti email: DGi...@aol.community
What is the question? Gertrude Stein's last words
No one mouth is big enough to utter the whole thing. Alan Watts
On Display in the UK http://www.web-gallery.co.uk
Simon Lemieux
>
> http://bugzilla.gnome.org
> I'm using png very often, indexed or not, w or w/o transparency, and have yet to find
> a problem with gimp.
Thanks for the address, my "bookmark" from inside Gimp would not work with
netscape and I couldn't find a bug report page on gimp.org...
As for the bug itself, it seems that for one big image I can't ever load it if
it's bugged, although I can reopen it with Gimp and scale the image to the same
resolution or any kind of change that doesn't really change anything and save it
over the old one, then there is chance the bug will be gone...
I will report it and see what happens!...
Thanks,
Simon
Michael Sweet
> ...
> From my point of view, GIMP is supposed to use a different coding
> library for PNGs than the libPNG that all other programs uses...
Actually, the PNG plug-in uses libpng and doesn't get built if you
don't have >v0.89 (or something like that)
I suspect what is happening is that the application you are viewing
the PNG files in does not support alpha transparency, but the image
you are saving uses it...
--
______________________________________________________________________
Michael Sweet, Easy Software Products mi...@easysw.com
Printing Software for UNIX http://www.easysw.com
Simon Lemieux
>
> I suspect what is happening is that the application you are viewing
> the PNG files in does not support alpha transparency, but the image
> you are saving uses it...
I have programmed the image reader myself and it works perfectly with Alpha
channel, actually it is optimised for it! However, it just don't support
interlacing and I took the attention not to create an interlaced PNG image...
And as I said sometimes, just rescaling the image to its current resolution
solves the bug, sometimes it doesn't, but there is a bug and my program is not
the cause. The images have too many IDATs and that is a bug...
Nick Lamb
> I have programmed the image reader myself and it works perfectly with Alpha
> channel, actually it is optimised for it! However, it just don't support
> interlacing and I took the attention not to create an interlaced PNG image...
> And as I said sometimes, just rescaling the image to its current resolution
> solves the bug, sometimes it doesn't, but there is a bug and my program is not
> the cause. The images have too many IDATs and that is a bug...
>
Gimp's PNG plug-in uses libpng to read and write image files, the bug is
almost certainly in your image reader. If you'd like to email me an
image which was saved _directly_ from Gimp and which you feel has a
"bug" I will be happy to look into it.
If you were expecting all the image data to be inside a single IDAT
chunk then I'm afraid you need to go away and actually read the PNG
specification from cover to cover before continuing development of your
"image reader". Just because Adobe write shoddy software doesn't give
you an excuse to do the same.
Nick.
Simon Lemieux
>
> Gimp's PNG plug-in uses libpng to read and write image files, the bug is
> almost certainly in your image reader. If you'd like to email me an
> image which was saved _directly_ from Gimp and which you feel has a
> "bug" I will be happy to look into it.
>
> If you were expecting all the image data to be inside a single IDAT
> chunk then I'm afraid you need to go away and actually read the PNG
> specification from cover to cover before continuing development of your
> "image reader". Just because Adobe write shoddy software doesn't give
> you an excuse to do the same.
Well, normally a PNG shouldn't too much IDAT chunks and here is the case, my
program can read many chunks but it hung over some limit that Gimp sometimes
overpass and sometimes not for the same exact image (it is odd, isn't it?).
I've had to recompile my libPNG with a hack in it so it doesn't care anymore
about such problems and will continue to read the PNG anyway, but this is not
the way to do, and I'm not impressed at all by Gimp with its png support...
That's all..
Simon
Greg Roelofs
>> the cause. The images have too many IDATs and that is a bug...
Nick Lamb <ru...@innocent.com> wrote:
>Gimp's PNG plug-in uses libpng to read and write image files, the bug is
>almost certainly in your image reader. If you'd like to email me an
>image which was saved _directly_ from Gimp and which you feel has a
>"bug" I will be happy to look into it.
I'm also interested. As far as I've heard, only POV-Ray has the
"too many IDATs" bug, and it's somewhat understandable due to its
incremental-save design. The GIMP has no need for that feature
and shouldn't have such a problem.
>If you were expecting all the image data to be inside a single IDAT
>chunk then I'm afraid you need to go away and actually read the PNG
>specification from cover to cover before continuing development of your
>"image reader". Just because Adobe write shoddy software doesn't give
>you an excuse to do the same.
That's a bit harsh, isn't it?
--
Greg Roelofs n_e_w_t_(at)_p_o_b_o_x_(period)_c_o_m
Newtware, PNG Group, Info-ZIP, Philips Research, ...
Svante Vinther
> OK, new discovery....
> I am only having this problem only reading the file in Internet
> Explorer 5.50, in my Netscape Communicator 4.7 & Navigator 6.0 the
> image is readable, again I am using GIMP v1.2 WIN32 on a Win98 SE
> platform.
In my experience, the transparency does not work in ie6 and netscape 6,
neither in ie 5.5 or netscape 4.7. The picture is viewable, but the
background is just white.
But in Mozilla (www.mozilla.org) it works perfectly :). I also noticed a
lack of transparent png files on the GIMP homepage, is that just me being
paranoid?
W.b.r. Svante
Branko Collin
>> OK, new discovery....
>> I am only having this problem only reading the file in Internet
>> Explorer 5.50, in my Netscape Communicator 4.7 & Navigator 6.0 the
>> image is readable, again I am using GIMP v1.2 WIN32 on a Win98 SE
>> platform.
>
>In my experience, the transparency does not work in ie6 and netscape 6,
>neither in ie 5.5 or netscape 4.7. The picture is viewable, but the
>background is just white.
>But in Mozilla (www.mozilla.org) it works perfectly :).
At the moment, browser support for even palette based transparency
(i.e. pick a index colour and say it is transparent) is less than
optimal. If you care about your audience, just do not use transparent
PNGs on webpages yet.
(According to Jakob Nielsen, and IIRC, it takes about two years for
the majority of people to adopt the latest browser. If you consider
Netscape 6 to be a beta (basically it is a build of beta Mozilla),
then it will probably be around 2004 that we can expect 99% of the
people to have browsers that will show transparent PNGs correctly.)
>I also noticed a lack of transparent png files on the GIMP
>homepage, is that just me being paranoid?
I do not know what you mean with 'paranoid'. Yes, Unisys does fly all
GIMP developers and everybody who's even remotely associated with them
to a tropical paradise, where we sip long drinks six months of the
year, but that is just because they're nice people, and in no way has
influenced the decision to use GIFs. ;-) Just keep paying these
license fees, people. ;-)
In all seriousness: the web site gets updated once in every blue moon,
by whoever feels like it and has write access. There are very few
people with write access and even fewer who 'feel like it', so do not
expect major changes.
There is a group of people working on a completely new web site,
though. Activities in this group are at a low, probably because of the
holidays. I guess it should pick up around now.
--
Real Men Don't Need Anaesthetics
William Kendrick
: Hi GIMPers.
: In my experience, the transparency does not work in ie6 and netscape 6,
: neither in ie 5.5 or netscape 4.7. The picture is viewable, but the
: background is just white.
: But in Mozilla (www.mozilla.org) it works perfectly :). I also noticed a
: lack of transparent png files on the GIMP homepage, is that just me being
: paranoid?
IE 3.x for MacOS 8 completely dies when it tries to view PNGs.
And for some reason, Netscape decided it wanted to use QuickTime to view
them (and that didn't have scrollbars!)
I feel sorry for my dad... that old Mac was 'top-o-the-line' back when
we got it for my parents, but damn... what a piece of crud.
I've also heard of IE for WIndows showing little "[X]" icons where PNGs
were supposed to be.
Long live GIF, I suppose.
<gag>
-bill!