From: Colin Baxter <m43cap@yandex.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Adam Porter <adam@alphapapa.net>, emacs-orgmode@gnu.org
Subject: Re: ox.html causes w3c xhtml validation
Date: Mon, 16 Mar 2020 08:38:24 +0000 [thread overview]
Message-ID: <874kuozocf.fsf@yandex.com> (raw)
In-Reply-To: <87r1xt8es6.fsf@kyleam.com> (Kyle Meyer's message of "Sun, 15 Mar 2020 21:54:49 +0000")
>>>>> Kyle Meyer <kyle@kyleam.com> writes:
> Adam Porter <adam@alphapapa.net> writes:
>> Colin Baxter <m43cap@yandex.com> 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
next prev parent reply other threads:[~2020-03-16 8:38 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
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 [this message]
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=874kuozocf.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=adam@alphapapa.net \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.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).