From mboxrd@z Thu Jan 1 00:00:00 1970 From: Colin Baxter Subject: Re: ox.html causes w3c xhtml validation Date: Mon, 16 Mar 2020 06:50:25 +0000 Message-ID: <878sk0ztce.fsf@yandex.com> References: <871rpt1hod.fsf@alphapapa.net> <87r1xt8es6.fsf@kyleam.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:58066) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jDja7-0000ZO-0T for emacs-orgmode@gnu.org; Mon, 16 Mar 2020 02:50:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jDja4-0004Wg-S8 for emacs-orgmode@gnu.org; Mon, 16 Mar 2020 02:50:33 -0400 Received: from forward103p.mail.yandex.net ([2a02:6b8:0:1472:2741:0:8b7:106]:45244) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jDja4-0003fT-74 for emacs-orgmode@gnu.org; Mon, 16 Mar 2020 02:50:32 -0400 In-Reply-To: <87r1xt8es6.fsf@kyleam.com> (Kyle Meyer's message of "Sun, 15 Mar 2020 21:54:49 +0000") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org Sender: "Emacs-orgmode" To: Kyle Meyer Cc: Adam Porter , emacs-orgmode@gnu.org >>>>> Kyle Meyer writes: > Adam Porter writes: >> Colin Baxter writes: >> >>> In my opinion, if it can't be fixed then the changes should be >>> removed. Surely, we cannot have an org-mode that knowingly >>> exports/publishes something that causes a validation error! >> >> Looking at the error message, the fix might be very simple: >> >> The most common cause of this error is unencoded ampersands in >> URLs as described by the WDG in "Ampersands in URLs". > Hmm, perhaps it is as simple as encoding the ampersand. That > won't work with inline javascript, if I'm understanding correctly > the link I gave in my reply. *But*, despite being embedded > javascript, the librejs magnet link happens within a comment, so I > suppose it really just comes down to how librejs treats it. > Poking around in librejs (525e3a5), it seems it is clever and will > s/&/&/: > // Match by link on first parameter (legacy) if > (licenses[key]["Magnet link"] === first.replace("&","&") || > licenses[key]["URL"] === first.replace("&","&")) { return > [true, `Recognized license: "${licenses[key]['Name']}".`]; > Colin, could you try exporting with the change below and see if > that resolves your validation issues? It'd also be great if you > could check whether librejs is still happy after that change. Ok, I'll try later today and report back. Thanks again. Best wishes, -- Colin Baxter www.Colin-Baxter.com --------------------------------------------------------------------- GnuPG fingerprint: 68A8 799C 0230 16E7 BF68 2A27 BBFA 2492 91F5 41C8 --------------------------------------------------------------------- Since mathematicians have invaded the theory of relativity, I do not understand it myself. A. Einstein