emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: org-mode Publishing fails xhtml validation and LibreJS test.
Date: Sun, 13 Dec 2020 11:57:51 +1100	[thread overview]
Message-ID: <87v9d6tsut.fsf@gmail.com> (raw)
In-Reply-To: <871rfuykf8.fsf@yandex.com>

Colin Baxter <m43cap@yandex.com> writes:

> Hello,
> When publishing, org-mode inserts the following javascript in the xhtml file:
> #+begin_src js
> <script type="text/javascript">
> // @license magnet:?xt=urn:btih:e95b018ef3580986a04669f1b5879592219e2a7a&dn=public-domain.txt Public Domain
> <!--/*--><![CDATA[/*><!--*/
>      function CodeHighlightOn(elem, id)
>      {
>        var target = document.getElementById(id);
>        if(null != target) {
>          elem.classList.add("code-highlighted");
>          target.classList.add("code-highlighted");
>        }
>      }
>      function CodeHighlightOff(elem, id)
>      {
>        var target = document.getElementById(id);
>        if(null != target) {
>          elem.classList.remove("code-highlighted");
>          target.classList.remove("code-highlighted");
>        }
>      }
>     /*]]>*///-->
> // @license-end
> </script>
> #+end_src
> There are issues with this script.
> 1. The script gives errors in XHTML 1.0 Strict validation. For example,
> the line beginning //@license ... gives errors of the type:
>  a. cannot generate system identifier for general entity "dn"
>  b. general entity "dn" not defined and no default entity
>  c. reference not terminated by REFC delimiter
>  etc.
> 2. The script fails the LibreJS (gnu.org/software/librejs) tests. This
> can be tested by opining the page in icecat.
> In order to pass XHTML and LibreJS validation tests, I have to delete
> the script from my web pages by hand.

Given the move to HTML5 and deprecation of XHTML, how valid are XHTML compliance requirements
these days? Could it be time to 'reverse' the org defaults and export
using HTML5 by default rather than XHTML?

Would it be sufficient to just have the license information embedded as
a simple comment?

Tim Cross

  reply	other threads:[~2020-12-13  1:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-12 17:59 Colin Baxter
2020-12-13  0:57 ` Tim Cross [this message]
2020-12-13  7:20   ` Colin Baxter
2020-12-13 15:53   ` Jean Louis

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:

  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=87v9d6tsut.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).