From: Ihor Radchenko <yantar92@posteo.net>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: ox-html content-type metadata (was: [BUG] ox-html output does not pass validation for html4-strict doctype [9.7-pre (release_9.6.23-1423-gcea6a1.dirty @ /home/yantar92/.emacs.d/straight/build/org/)])
Date: Thu, 28 Mar 2024 11:27:41 +0000 [thread overview]
Message-ID: <87o7aytx3m.fsf@localhost> (raw)
In-Reply-To: <uu1ecu$pfe$1@ciao.gmane.io>
This is tangent to the original problem I described.
Max Nikulin <manikulin@gmail.com> writes:
> On 25/03/2024 18:18, Ihor Radchenko wrote:
>> I am wondering whether it is at all possible to use the same syntax and
>> yet pass validation for all the allowed values of `org-html-doctype':
>> "html4-strict", "html4-transitional", "html4-frameset", "xhtml-strict",
>> "xhtml-transitional", "xhtml-frameset", "xhtml-11", "html5", "xhtml5".
>
> Is it correct to use text/html for XHTML? I would expect
> application/xhtml+xml, but it is better to check standard.
It is certainly not an error.
Also,
https://developer.mozilla.org/en-US/docs/Web/HTTP/Basics_of_HTTP/MIME_types#texthtml
says
All HTML content should be served with this type. Alternative MIME types
for XHTML (like application/xhtml+xml) are mostly useless nowadays.
> For html5 my expectation is
>
> <meta charset="utf-8">
>
> instead of http-equiv
> https://developer.mozilla.org/en-US/docs/Web/HTML/Element/meta#charset
What made you think that your expectation is not fulfilled by ox-html?
--
Ihor Radchenko // yantar92,
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/yantar92>
prev parent reply other threads:[~2024-03-28 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 11:18 [BUG] ox-html output does not pass validation for html4-strict doctype [9.7-pre (release_9.6.23-1423-gcea6a1.dirty @ /home/yantar92/.emacs.d/straight/build/org/)] Ihor Radchenko
2024-03-27 15:35 ` Max Nikulin
2024-03-28 11:27 ` Ihor Radchenko [this message]
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=87o7aytx3m.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.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).