content: Document image compresssion option #3331
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jmooring
force-pushed
the
document-image-compression-option
branch
3 times, most recently
from
6df9682 to
606f09e
Compare
jmooring
force-pushed
the
document-image-compression-option
branch
from
606f09e to
013fee4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP. Do not merge. Needs some DRY refactoring; we document this stuff in multiple places.
images.ProcessResource.Process(andResource.Crop/Fill/Fit/Resizewith shared inclusion)EDIT 2025-12-31T07:27:33-08:00...
Given the different contexts in which the imaging spec is presented, and the desire for semantically correct definition lists, the cost of a DRY implementation far exceeds the value. This still needs some work, which will have to wait for a couple of days.