Ryan Leavengood <leavengood@xxxxxxxxx> wrote: > > For a web browser, progressive loading is also important, which our > > translators currently don't provide AFAIK, so using libjpeg.so over > > our > > translators is probably the way to go (and only otherwise > > unsupported > > images should then be handled by translators). > This isn't a bad idea actually (making translators only a fallback) > and would give us the best of both worlds. Though I was thinking > about > it and there doesn't seem to be any reason that our translators > shouldn't support progressive loading. What is progressive loading > after all but just trying to display a partially downloaded image? If > they don't already support it I would think it wouldn't be hard to > add. You would probably need to introduce a new protocol for that, IIRC. There is no technical reason, though, only some API changes and extensions. Bye, Axel.