- From: Frédéric Kayser <f.kayser@free.fr>
- Date: Mon, 21 Oct 2013 02:36:10 +0200
- To: public-respimg@w3.org
- Cc: Jason Grigsby <jason@cloudfour.com>
- Message-Id: <01A3FA06-2FB6-4F46-9BA5-2357CDE6107C@free.fr>
The recent image file comparison conducted by Mozilla regarding WebP inclusion did not even involve JPEG 2000. https://bugzilla.mozilla.org/show_bug.cgi?id=856375#c147 https://groups.google.com/forum/#!topic/mozilla.dev.platform/9NKc7OeEFLM File size and image quality are an important aspect but this study did not take progressive rendering nor data stream flexibility to offer responsive (or hierarchical as it was called in the JPEG specs) capabilities in account. Regards -- Frédéric Kayser Jason Grigsby wrote: > This seems like a question for the browser vendors (John? Tab?). I'm assuming JPEG 2000 has been considered. What was the result of that consideration? > > > On Fri, Oct 18, 2013 at 12:52 PM, Eduardo Marques <ebmarques@gmail.com> wrote: > IMO, those are ***THE*** keywords for the solution we need(!!!): > > > With every client requesting just the bytes it needs from the full-res > source file. > > Simple as that. Not less, not more than that. > The challenge is: How to do that? > > > > From: lists@ericportis [mailto:lists@ericportis.com] > Sent: sexta-feira, 18 de outubro de 2013 16:33 > To: Frédéric Kayser > Cc: public-respimg@w3.org > Subject: Re: JPEG 2000 (was: Multiple image files?) > ... > With every client requesting just the bytes it needs from the full-res > source file. > ... > > > > > > -- > +1 (503) 290-1090 o | +1 (503) 502-7211 m | http://cloudfour.com
Received on Monday, 21 October 2013 00:36:39 UTC