From: Kyle Meyer <kyle@kyleam.com>
To: Colin Baxter <m43cap@yandex.com>, emacs-orgmode@gnu.org
Cc: Arne Babenhauserheide <arne_bab@web.de>
Subject: Re: ox.html causes w3c xhtml validation
Date: Sun, 15 Mar 2020 19:45:31 +0000 [thread overview]
Message-ID: <871rpt9zc4.fsf@kyleam.com> (raw)
In-Reply-To: <87eett7bql.fsf@yandex.com>
Colin Baxter <m43cap@yandex.com> 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
next prev parent reply other threads:[~2020-03-15 19:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-15 17:45 ox.html causes w3c xhtml validation Colin Baxter
2020-03-15 18:35 ` Colin Baxter
2020-03-15 19:45 ` Kyle Meyer [this message]
2020-03-15 19:56 ` Colin Baxter
2020-03-15 20:34 ` Adam Porter
2020-03-15 21:54 ` Kyle Meyer
2020-03-16 6:50 ` Colin Baxter
2020-03-16 8:38 ` Colin Baxter
2020-03-17 5:15 ` Kyle Meyer
2020-03-17 7:43 ` Colin Baxter
2020-03-15 22:40 ` Arne Babenhauserheide
2020-03-15 23:59 ` Kyle Meyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871rpt9zc4.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=arne_bab@web.de \
--cc=emacs-orgmode@gnu.org \
--cc=m43cap@yandex.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).