Repository navigation
Retain thin filled PDF rule geometry without inferring cells - #230
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A measured table page draws its horizontal rules as thin filled rectangles. The extractor previously dropped them under the 5-point cell-rectangle floor, leaving neither filled-bar nor stroke evidence for downstream review.
This change retains a bounded single closed axis-aligned fill/eoFill rectangle with transformed short side 0.05 through 2 points and long side at least 5 points. It records the actual filled area in existing neutral rectangle evidence, not a fabricated stroke centerline, cell border or visibility claim. Full command consumption rejects residual drawing after closePath. The established cell-grid candidate path independently retains its 5-point minimum on both sides.
Validation:
Source/share mirrors agree. No schema shape, API, dependency, OCR/model/provider call, release, or installation change is included.