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 08:38:24 +0000 Message-ID: <874kuozocf.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]:40743) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jDlGc-0007Es-R7 for emacs-orgmode@gnu.org; Mon, 16 Mar 2020 04:38:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jDlGa-0004Cv-EY for emacs-orgmode@gnu.org; Mon, 16 Mar 2020 04:38:33 -0400 Received: from forward101p.mail.yandex.net ([2a02:6b8:0:1472:2741:0:8b7:101]:36410) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jDlGZ-0003SD-MY for emacs-orgmode@gnu.org; Mon, 16 Mar 2020 04:38: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. I've now applied the patch to my local org-mode and exported the file "index.org". It seems to work because I now get "This document was successfully checked as XHTML 1.0 Strict!" when validating by uploading the html file "index.html" to http://validator.w3.org/. As to librejs, I don't actually use js on my web-site so apart from the js license information in the html header there is no js on the page. However, I've opened my "index.html" file with icecat (v52.3.0 32 bit) and get the following output: ---------- Begin ----- List of accepted JavaScript in file:///home/redknight/public_html/index.html LibreJS did not allow the execution of any scripts on this page: ' There may be no scripts on this page (check source, C-u) The inline and on-page JavaScript code may not be free and/or may not have proper license information and external scripts (if present) may have been removed by default. External scripts may not be free and/or may not have proper licensing and are not part of the whitelist of free JavaScript libraries. List of blocked JavaScript in file:///home/redknight/public_html/index.html LibreJS did not block any scripts on this page: There may be no scripts on this page (check source, C-u). All the scripts on this page may be trivial and/or free. You may have whitelisted this domain name or url from the preferences (Type about:addons in your location bar to check) You may have clicked the "allow all scripts" button, which causes LibreJS to load all JavaScript on a page regardless of whether it is free, trivial, nontrivial or nonfree. This policy is effective for the entire duration of a Firefox session. If for any reason you think LibreJS should have blocked JavaScript code on this page, please report this issue to: bug-librejs@gnu.org ---------- End ----- I hope this helps - and thanks Best wishes, -- Colin Baxter www.Colin-Baxter.com