Google's Webp support

[forart.eu]

WebP is a method of lossy compression that can be used on photographic images. The degree of compression is adjustable so a user can choose the trade-off between file size and image quality.

A WebP file consists of VP8 image data, and a container based on RIFF. Webmasters, web developers and browser developers can use the WebP format to create smaller, better looking images that can help make the web faster.

​http://code.google.com/intl/it-IT/speed/webp/

[michaelvoliveira]

This one is for Haikuports

Please create this ticket there

​http://ports.haiku-files.org

[tangobravo]

The link seems to be about using WebP as an image format. I'm not sure I quite agree with their comparison method (random jpegs from the net probably have all sorts of compression artifacts already that makes re-compression not necessarily a good test). Anyhow as a new image format a translator should be used, which would make it part of core haiku.

Still, please don't tag bugs "[IMPORTANT]". The devs can set a priority if they think it is necessary.

I think there's already a ticket for Google's VP8, so the component of this one should be changed to translators.

[michaelvoliveira]

Done

​http://ports.haiku-files.org/ticket/429

[korli]

WebPTranslator was added to the image. Can we close this ?

[phoudoin]

Replying to korli:

WebPTranslator was added to the image. Can we close this ?

It only support decoding images, not encoding. This enhancement is still valid, but should be promoted to Full Google's WebP read & write support instead.

The libwebp port is great except for this gcc4 only issue. I guess switching the translator to use this lib instead is the right move to do. I will give a look, eventually, if nobody beat me.

[phoudoin]

Since hrev40869, we've read & write WebP image support, thanks for latest libwebp now featuring encoding API too.

[phoudoin]

While the write support has some input colorspace limitation ATM, I consider the main task done.