Skip to content

feat: navigation respect text boundary#261

Draft
tuurma wants to merge 2 commits intomainfrom
nav-fix
Draft

feat: navigation respect text boundary#261
tuurma wants to merge 2 commits intomainfrom
nav-fix

Conversation

@tuurma
Copy link
Member

@tuurma tuurma commented Jan 30, 2026

  • establishing navigation sections in page or div view only look within text; ignore any other, e.g. in standOff or teiHeader
  • same for iiif manifest config
  • same for establishing order in pb-facs-link via ODD

- establishing navigation sections in `page` or `div` view only look within `text`; ignore any other, e.g. in standOff or teiHeader
- same for iiif manifest config
- same for establishing order in `pb-facs-link` via ODD
@tuurma tuurma requested a review from wolfgangmm January 30, 2026 11:00
@tuurma tuurma marked this pull request as draft January 30, 2026 11:00
@tuurma
Copy link
Member Author

tuurma commented Feb 2, 2026

Still problematic is the case for determining next/prev section for parts that are encoded not as part of transcription, but e.g. in standOff; at least for the page view, where reconstructing the page requires knowing the next/prev pb

$div
case element(tei:pb) return
let $nextPage := $div/following::tei:pb[1]
let $nextPage := $div/following::tei:pb[ancestor::tei:text][1]
Copy link
Contributor

Choose a reason for hiding this comment

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

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.

2 participants