Wim de With

I see that #1122 touches something related to this change. If both are merged, we probably need to update some stuff to reuse the same code paths for resizing images.

> Awesome! I hope this works :) Do you need to reconfigure `ProgressSync` to avoid encoding in this case? No, this change is entirely transparent. It just changes the ProgressSync...

> Can confirm this works! Thank you @wfdewith for taking the initiative on this and frankly I love this solution, it just makes everything better. Thanks! > Few tweaks: >...

> One alternative, reusing the `max_advance` of line breaking for alignment probably also won't really work, as floated boxes likely impact `max_advance`. My understanding was that we should be moving...

> > My understanding was that we should be moving to using line.max_advance for alignment anyway as the separate alignment width mostly existed to account for (near) infinite line.max_advance. >...

For my use case `--identifier` is not sufficient. I'm syncing a pool to an external HDD periodically as a backup. I can connect this external HDD to different hosts to...

> Yeah, that is correct. Having that guarantee from the integration tests would be nice. Wouldn't that be as easy as just adding a step to CI with `cd runtime...

> **To be able to yield control flow when a "floated box" is encountered in the layout.** A "floated box" would be specified like the existing "inline boxes" but a...

> @wfdewith It's because the position of the float depends on line-breaking. The position of a float is not specified in terms of pixels, it's specified as an index into...

@shuvashish76 doesn't your use case work already? You can currently backup and restore the sidecar files through this plugin when you connect to the synced folder in Calibre. The plugin...