Ophir LOJKINE

Results 1257 comments of Ophir LOJKINE

This website seems to be using the deepzoom zoomable image format, which is supported. The meta-information file is : https://jarvis.haltadefinizione.com/images/dzi-backend/db/14366c5d-26b7-4968-a9d0-7fd144035f33/file.dzi Which gives : ![baccus-badqal](https://user-images.githubusercontent.com/552629/106386657-4d8a6a00-63d6-11eb-9e49-c03957c0808d.jpg)

blocked by https://github.com/image-rs/image/issues/1550

This would indeed be very cool! Would you be interested in implementing that and making a pull request? I can provide help and guidance.

Yes, all of these steps make sense. Ideally we would break up the huge [dezoomify](https://github.com/lovasoa/dezoomify-rs/blob/master/src/lib.rs#L141-L225) function that currently drives the whole dezoomifying process. We could have a function that accepts...

dezoomify does not have this functionality at the moment. You may want to try [dezoom.sh](https://github.com/lovasoa/dezoom.sh), which can do that.

There was also a recent change in dezoomify concerning very large images. Image size is now limited to 268 megapixels. You should also read our documentation concerning very large images:...

[dezoomify-rs](https://github.com/lovasoa/dezoomify-rs) has a *custom YAML* dezoomer which does what you want: it lets you specify custom bounds for x and y. See https://github.com/lovasoa/dezoomify-rs/wiki/Usage-example-for-the-custom-YAML-dezoomer

It looks like they use a json-encoded dzi file (instead of the usual xml). I'll mark this as "enhencement" and keep this issue open until we add support for it....

![superzoom_2 copy](https://user-images.githubusercontent.com/552629/94810116-e2169880-03f3-11eb-8930-09287b578fbc.jpg)

Have you read the documentation for the custom yaml dezoomer ? This is the kind of things you can do with it.