Re: ox.html causes w3c xhtml validation

[Kyle Meyer]

Colin Baxter <address@hidden> writes:

> ----- Begin -----
> Warning Line 205, Column 74:
> cannot generate system identifier for general entity "dn"
>
> …rn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt 
> GPL-v3-or-Later
>
>     An entity reference was found in the document, but there is no
>     reference by that name defined. Often this is caused by misspelling
>     the reference name, unencoded ampersands, or by leaving off the
>     trailing semicolon (;). The most common cause of this error is
>     unencoded ampersands in URLs as described by the WDG in "Ampersands
>     in URLs".
>
> ----- End -------
>
> The cause is ox-html, which has the following lines
>
> ./lisp/ox-html.el:235:// @license
> magnet:?xt=urn:btih:1f739d935676111cfff4b4693e3816e664797050&dn=gpl-3.0.txt
> GPL-v3-or-Later
[...]
> I think the culprit is commit 68fa5e589f00c8d5b4f7f0dc70be6ebe59238bb8,
> 11 Feb.
>
> Is it possible to fix this?

>From what I gather from briefly searching around (mostly based on this
information [0]), I don't think there's an easy fix for inline
javascript.

I wonder if Arne [+cc], who suggested the change [1], knows of a solution.

[0]: https://mrcoles.com/blog/how-use-amersands-html-encode/
[1]: https://lists.gnu.org/archive/html/emacs-orgmode/2019-11/msg00030.html