Skip to content

docs(readme): say the nested-table limit is the page estimate's, not table support's - #558

Merged
airmang merged 1 commit into
mainfrom
docs/readme-nested-table-wording
Oct 24, 2026
Merged

airmang merged 1 commit into
mainfrom
docs/readme-nested-table-wording

Conversation

@airmang

@airmang airmang commented Oct 24, 2026

Copy link
Copy Markdown
Owner

The README's fidelity table and known limitations read as if tables inside table cells were unsupported. They are supported for reading, editing and structure editing. The only limit is in the experimental page estimate (estimate_pages), which skips a document when a table is placed among text or floating inside a cell and the cell has no line layout data (it returns the reason instead of a guess).

  • Fidelity table: the second of the two unmatched documents is described as "a table in a cell the page estimate cannot lay out yet".
  • Known limitations: names the two cases the page estimate skips today (a character grid without line layout data, the nested table above) and states that table reading and editing are not affected. The line grid is no longer listed, since the page estimate follows it now.

🤖 Generated with Claude Code

…table support's

The fidelity table and the limitations read as if tables inside cells were
unsupported. Only the experimental page estimate skips one case: a table
placed among text or floating in a cell without line layout data. Reading
and editing nested tables is unaffected. The line grid, now estimated, is
no longer listed as a limit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

@airmang airmang left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

head 337c1ce / base 1fed0b8ef536c69d69e77a88c189b5c6d9fa5bfa를 검토했습니다. 한·영 README의 변경을 비교하고 pages._row의 nested-table unsupported 조건, character-grid 캐시 조건 및 기존 중첩 표 읽기/작성/round-trip 경로와 대조했습니다. 표 편집 자체의 제한으로 오해할 문구를 쪽 수 추정의 제한으로 좁히며, 실행 코드/예제는 바꾸지 않습니다. 새 README 소스의 SHA256이 ledger의 두 항목과 모두 일치합니다. 미해결 결함은 발견하지 못했습니다.

정확한 head의 CI13개 성공과 Python3.12 로그의 7,105 passed / 18 skipped / 1 xfailed, coverage90.13%, Ruff·mypy·pyright 통과를 확인했습니다. 문서 변경 범위에 맞춰 추가 로컬 전체 테스트는 반복하지 않았습니다. 자기 PR이므로 COMMENT로 결과를 남깁니다.

@airmang
airmang merged commit 708a854 into main Oct 24, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant