Adds a GH workflow to validate XML syntax and well-formedness

[funkyfuture]

ciao Simon,

i'd like to use this text corpus within the integrations test suite for the delb library. unfortunately there's quiet a lot of errors in the corpus.

thus i've added a Github workflow to validate all documents.

due to the amount of errors i don't see that it'd be reasonable to fix the issues by hand.

[funkyfuture]

this is the outcome of an example run: https://github.com/delb-xml/test-corpus-aed-tei/actions/runs/19209861146/job/54910465966

the forth step includes the emitted error messages. but due to the usage of find there's no non-zero exit code, so the action/workflow doesn't fail. @JKatzwinkel could we parler in the coming days about possible solutions, i don't wanna over-engineer.

[JKatzwinkel]

since when has this --pedantic flag been a thing and why is it not in the man page??

[funkyfuture]

my installation even has --strict-namespace. i use Arch btw.

[funkyfuture]

a'ight, i got this action thing tucked in.

here's an example run on a fork.

future pull requests would display error annotations in the review tab, see screenshots here

[JKatzwinkel]

how is the action on the container registry lol i didnt even know you could do that!?

[simondschweitzer]

Thanks for your work and sorry for my late reply! I don't know what this means:

So, first of all, I will click the button "Approve workflows to run" :-)

[simondschweitzer]

1 failing and 1 successful check:

Is this a problem?

[simondschweitzer]

Ah, o.k., this failing check is because of the errors in the corpus, right?

[funkyfuture]

how is the action on the container registry lol i didnt even know you could do that!?

this is the how. and yeah that's the common thing w/ the GH docs, there's a lot of info in it, but cluttered and hard to find.

Ah, o.k., this failing check is because of the errors in the corpus, right?

yes, it is. the best comprehension for an assessment is this summary.

at least regarding the unencoded ampersands seem to be suited for a simple search & replace action, doesn't it?

[funkyfuture]

i did that search & replace; interestingly it affects exactly 500 files.

also, note that the editor (VS code) removed some CR characters at line endings, leaving the LFs only.