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

Check for elements pointing to non-existing target ids #20

Open
mapscl opened this issue May 2, 2023 · 1 comment
Open

Check for elements pointing to non-existing target ids #20

mapscl opened this issue May 2, 2023 · 1 comment
Labels
feature request Wanted new functionality

Comments

@mapscl
Copy link
Collaborator

mapscl commented May 2, 2023

Problem
Whenever an element is removed that can be referenced by spanning elements (like <note> in most cases) the spanning element can not be rendered anymore. This makes it very difficult to find and delete the spanning element manually so there are no dead elements in your file.

Solution
Either the spanning element should be deleted right away when the referenced element is deleted or a function could be implemented that removes all spanning elements that reference non-existent elements.
Because reinserting a spanning element is relatively easy for most of them, just deleting them right away would probably be best for workflow.

@wergo wergo added the feature request Wanted new functionality label May 8, 2024
@wergo wergo changed the title Delete spanning elements with non existent referenced elements Check for elements pointing to non-existing target ids May 8, 2024
@wergo
Copy link
Member

wergo commented May 8, 2024

Add new function to check all (or a subset of) data.URI pointing elements starting with a hash (e.g., @startid="#note0123") for the existence of the targeted element within the current encoding and provide an interface for user action (delete, ignore, ...).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Wanted new functionality
Projects
None yet
Development

No branches or pull requests

2 participants