Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

text per page return has error when text order is not sequential #3

Open
jeffreycwitt opened this issue Apr 9, 2020 · 0 comments
Open

Comments

@jeffreycwitt
Copy link
Collaborator

codices "sorb" and "svict" have examples where the next page is not sequential.
At a certain point in sorb pages are out of order. Exist-db is using the numbers in the <pb> elements to look for the next page.

It should not be doing this. It should treat these numbers as meaningless ids. Instead it should look for the next sequential element

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

No branches or pull requests

1 participant