emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Kyle Meyer <kyle@kyleam.com>
To: Colin Baxter <m43cap@yandex.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ox.html causes w3c xhtml validation
Date: Tue, 17 Mar 2020 05:15:41 +0000	[thread overview]
Message-ID: <87h7yn7e9u.fsf@kyleam.com> (raw)
In-Reply-To: <874kuozocf.fsf@yandex.com>

Hi Colin,

Colin Baxter <m43cap@yandex.com> writes:

>>>>>> Kyle Meyer <kyle@kyleam.com> writes:

>     > 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:

Thanks for reporting back.  Arne sent an equivalent patch (see sibling
thread), verifying that LibreJS worked with it.  I applied that in
661696036 (ox-html: escape & in license magnets, 2020-03-15), so we
should be all set.

next prev parent reply	other threads:[~2020-03-17  5:15 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
2020-03-17  5:15           ` Kyle Meyer [this message]
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=87h7yn7e9u.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=m43cap@yandex.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

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