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

Preserve XML markup in imported full-text documents #2510

Open
davidzbiral opened this issue Jan 14, 2025 · 0 comments
Open

Preserve XML markup in imported full-text documents #2510

davidzbiral opened this issue Jan 14, 2025 · 0 comments
Assignees
Milestone

Comments

@davidzbiral
Copy link
Collaborator

Some editions of texts come as an XML (or TEI-XML) document. Allow the import of such documents, and make the following changes to Annotator:

  • Preserve all of them and their attributes.
  • Only show these in xml mode. In highlight mode and text edit mode, hide them, only show text.
  • Ensure the tags cannot be corrupted by either anchor adding (i.e. anchors must not be added into XML tags) or plain text editing in text edit mode - only allow their changes in XML mode.
  • Our UUID anchors can go across start and end tag, thereby creating invalid XML (because of overlapping markup: XML start tag 1 is before XML start tag 2, but xml end tag 1 is after XML end tag 2, which is invalid in XML). But while allowing this situation, do not contribute to it - i.e. if the UUID anchor is adjacent to another xml tag (in the XML view), make as little crosses of markup as possible when adding our UUID anchor (related to Anchor overlap prevention  #2403, just putting the original XML into the picture).

If needed, in full-text import and the rendering of anchors, ensure the recognition of InkVisitor database UUIDs which should pair up, telling them apart from other <>-delimited XML markup.

@davidzbiral davidzbiral added this to the 1.4.2 milestone Jan 14, 2025
@davidzbiral davidzbiral changed the title Preserve XML markup in imported documents Preserve XML markup in imported full-text documents Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants