From: Timothy <orgmode@tec.tecosaur.net>
To: Scott Randby <srandby@gmail.com>
Cc: Ihor Radchenko <yantar92@posteo.net>, emacs-orgmode@gnu.org
Subject: Re: HTML export meta tag
Date: Tue, 30 May 2023 04:37:26 +0800 [thread overview]
Message-ID: <87cz2iuay7.fsf@tec.tecosaur.net> (raw)
In-Reply-To: <9e96d574-e9ff-fb2e-078a-7cc8a232c528@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
Hi Scott,
> Just to give some support to my request, the HTML standard
> (<https://html.spec.whatwg.org/multipage/syntax.html#start-tags>) says this:
> “Then, if the element is one of the void elements, or if the element is a
> foreign element, then there may be a single U+002F SOLIDUS character (/), which
> on foreign elements marks the start tag as self-closing. On void elements, it
> does not mark the start tag as self-closing but instead is unnecessary and has
> no effect of any kind. For such void elements, it should be used only with
> caution — especially since, if directly preceded by an unquoted attribute value,
> it becomes part of the attribute value rather than being discarded by the
> parser.”
The things is the ox-html exporter currently tries to (mostly) support XHTML,
which as I understand requires the self-closing slash.
I think what’s really needed is an HTML export implementation that can more
easily support different “modes” of export, but somebody needs to work on that
🙃.
All the best,
Timothy
--
Timothy (‘tecosaur’/‘TEC’), Org mode contributor.
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/tec>.
next prev parent reply other threads:[~2023-05-29 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 18:02 HTML export meta tag Scott Randby
2023-05-29 18:07 ` Ihor Radchenko
2023-05-29 18:19 ` Scott Randby
2023-05-29 20:37 ` Timothy [this message]
2023-05-29 22:25 ` Scott Randby
2023-05-30 6:12 ` Ihor Radchenko
2023-05-30 15:37 ` Max Nikulin
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=87cz2iuay7.fsf@tec.tecosaur.net \
--to=orgmode@tec.tecosaur.net \
--cc=emacs-orgmode@gnu.org \
--cc=srandby@gmail.com \
--cc=yantar92@posteo.net \
/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).