Chore: update .html files for xslt/xml processing

[patrickhlauke]

• change <link …></link> to self-closing <link … /> ... not elegant, but at least not invalid html
• add xml:space="preserve" to all instances of <pre> to maintain spaces through xslt transformation

---

Preview | Diff

[alastc]

Someone who can build the docs locally needs to test this (me and Francis so far).

[alastc]

@iadawn this seems to build ok for me, can you have a look to see if there are any issues for the guidelines index or other respec docs?

[iadawn]

I will confess to being slightly perplexed by this one. However, I have built stuff and checked ReSpec and there are no issues that I can spot.

[alastc]

So this update looks ok (with approval from Kevin), but we've got a bunch of conflicts now, could you try and resolve those @patrickhlauke?

[patrickhlauke]

we've got a bunch of conflicts now, could you try and resolve those @patrickhlauke?

done

[bruce-usab]

@patrickhlauke could you walk the TF through this on the call next Friday, 8 March? As has been the pattern, probably alastair or Michael will be screen sharing.

[patrickhlauke]

sure

[alastc]

Hmm, I just tried to build and got...
BUILD FAILED /Sites/wcag/build.xml:167: ; SystemID: file:/Sites/wcag/xslt/generate-technique-associations.xslt; Line#: 24; Column#: 32 net.sf.saxon.trans.XPathException: org.xml.sax.SAXParseException; systemId: file:/Sites/wcag/understanding/22/accessible-authentication-enhanced.html; lineNumber: 7; columnNumber: 3; The element type "link" must be terminated by the matching end-tag "</link>".

I think essentially there's a clash between the build-process expecting valid XHTML, and your editing environment expecting valid HTML... but in the current state that will block all new updates to the documents if it is merged.

So either that change needs to be undone, or perhaps there's a way of getting the XSL to accept the <link />?

@patrickhlauke it would be good to get a local build setup, it should only take about 5 minutes, then you'll be able to work out if a change breaks things. (I'm not sure why this didn't happen before, it looks like someone did manage to build it above?)

[patrickhlauke]

@alastc

I just tried to build and got

that was an oversight, i forgot to add the self-closing slash to that particular file's <link>. I'll have a check to make sure all others are kosher.

getting the XSL to accept the <link />

XSL is fine with self-closing elements, as it's valid XML. the error you got was in that one file because I forgot it (but will check that i didn't slip up in other files as well)

would be good to get a local build setup,

anything that starts with "install java" gets a hard pass from me ;)

[patrickhlauke]

@alastc try now

[bruce-usab]

Briefly discussed on call 3/22/2024.