:rolleyes:
Printable View
:rolleyes:
Keith wrote:This is not because GIF is better, but because we always export PNG in 32 bit mode. GIF is 8 bit, so is smaller. But if we would like to go for such an optimization, we still would use 8bpp PNG not GIF. There is really no point to use GIF any more except for animations. PNG supports all modes that GIF does, and is actually smaller at the same number of colors used as it uses better compression algorithms.Quote:
Some of the PNG's that are produced are 103k - the same file converted to a GIF the same size is 37k. and as far as websites go there is no appreciable loss of quality.
So, please don't ask for GIF, ask for better control over the exported image quality and mode. ;)
Please can we have better control over the exported image quality and mode.
It would be nice to get the image size down (That was really my point ... Not specifically GIF ... the images just seemed to be larger than necessary). If we could have the option of 8bpp export that would be good.
Yes, could we possibly have the option of creating "PNG8bit" or "PNG4bit" please. ;)
John...better control over the exported image quality and mode please :)
Can someone confirm this please?
Create a CMYK text object, convert to shapes, ungroup twice, then colour each letter accordingly Cyan Magenta Yellow blacK.
Group all four letters.
Create a bitmap copy and choose 256 colours (8bit) PNG with or without transparency (it makes no difference to the results)
Delete vector letters.
Now you should have just one 256 colour object on the page comprising 4 colours.
Now export to HTML.
The result I get is a 32bit PNG - surely this should have forced export of 8bit PNG?
??
I believe XXP just exports all PNG's at 32bit in HTML export Steve. Thus the requests for 32, 24, 8 and 4 bit export options.
EDIT. Just did a test. Created a single red filled rectangle Set Name to PNG. Exported the page as html. The created PNG as exported was 32 bit.
Yes but also see, that if you have GIF resources prepared for your web pages, then Xtremes HTML export will convert them all to 32bit PNG and thus increase the files sizes significantly.
eg: in my test, an 89KB 8bit GIF file becomes a 168KB 32bit PNG
Imagine a dozen 89KB files on a single page that are exported as a dozen 168KB files? Suddenly your fast loading website begins to drag it's feet.
Under these conditions the claim that PNG is better, is in fact, nonsense.
Totally agree Steve. Charles argues that gifs, apart from animated gifs are history and I agree. HOWEVER the export filter should have the option to create 4, 8 24 and 32 bit PNG's not JUST 32 bit png's as it does at present.
You should be able to open the name dialogue window and not only type in PNG but "PNG8bit" or "PNG4bit" etc.
Yes I'm in favour of having those options but they would only be helpful to those who would use them under the condition that they knew the benefits of such options.
I think the point is more relevant that an 8bit resource should be exported as an 8bit resource and not auto converted to 32bit.
Neither should it be necessary to maintain the colour depth of a resource by having to first name as such, in effect making this a 'preventative' action.