On Tue, Oct 22, 2013 at 1:42 AM, Frédéric Kayser <f.kayser@free.fr> wrote: > If Mozilla is serious about its integrated PDF viewer they will have to > better support JPEG 2000 since it is part of the PDF specs. > See 7.4.9 JPXDecode Filter in: > > http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/pdf/pdfs/PDF32000_2008.pdf > > Current JPX file support in PDF.js (the PDF renderer used by Firefox) is > suboptimal. > Compare Google Chrome and Firefox rendering of this file: > http://fanat1k.ru/tmp/test_pdf.pdf > > The iBooks reader on iOS devices also displays JPEG 2000 images found in > PDF files since iOS 5 (it was not the case before). > > Hey, PDF is a nice trojan horse! > > Regards > -- > Frédéric Kayser > > Marcos Caceres wrote: > > > On Monday, October 21, 2013 at 6:27 PM, lists@ericportis.com wrote: > > > >> I'd love to hear more from browser vendors about why the format never > made the cut, historically. > > > > > > Wish I could give that insight, but I'm too new at Mozilla :( However, > JPEG2000 is also being discussed as part of the thread about the image > formats study: > > > > https://groups.google.com/forum/#!topic/mozilla.dev.platform/9NKc7OeEFLM > > > > See this message from Henri, who has been with Mozilla for about 10 > years: > > > https://groups.google.com/d/msg/mozilla.dev.platform/9NKc7OeEFLM/4B_JtvpiKTgJ > > > I think it would be extremely helpful if someone could run some JP2K tests and prove or disprove Henri's claims. The following comment https://groups.google.com/d/msg/mozilla.dev.platform/9NKc7OeEFLM/kH35YH62uMUJsuggests that it's a matter of encoder settings.Received on Tuesday, 22 October 2013 06:39:09 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:06:10 UTC