From: Jean Louis <email@example.com>
To: Tim Cross <firstname.lastname@example.org>
Subject: Re: org-mode Publishing fails xhtml validation and LibreJS test.
Date: Sun, 13 Dec 2020 18:53:29 +0300 [thread overview]
Message-ID: <X9Y4+UMo67v/2CH7@protected.rcdrun.com> (raw)
* Tim Cross <email@example.com> [2020-12-13 04:09]:
> 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?
There is no deprecation of XHTML, not until there comes XHTML5. And
XHTML will remain for good number of years. It serves slightly
different purpose and is more suitable for Org exports due to its
XHTML must all the time be valid. Org export function should, when
possible, or by user configured, include the validator check.
It would not be good to switch to HTML5 because software does not
produce XHTML well. It is better finding those bugs.
> Would it be sufficient to just have the license information embedded
> as a simple comment?
Here are ways to make it compatible with LibreJS:
prev parent reply other threads:[~2020-12-13 17:41 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
2020-12-13 7:20 ` Colin Baxter
2020-12-13 15:53 ` Jean Louis [this message]
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 \
* 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).