Re: HTML export meta tag

On 30/05/2023 03:37, Timothy wrote: The things is the ox-html exporter currently tries to (mostly) support XHTML, which as I understand requires the self-closing slash. ox-html has (:html-doctype "HTML_DOCTYPE" nil org-html-doctype) option that may be set to e.g. xhtml-11 or html5. Ideall

Re: HTML export meta tag

Scott Randby writes: > Okay, but when I try to validate my page as XHTML, I get numerous errors that > would be inconvenient to fix especially since I'm only interested in > obtaining valid HTML. What I think I'll do is to edit the > org-html--build-meta-entry function in my ox-html.el file to

Re: HTML export meta tag

On 5/29/23 16:37, Timothy wrote: Hi Scott, Just to give some support to my request, the HTML standard () 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 singl

Re: HTML export meta tag

Hi Scott, > Just to give some support to my request, the HTML standard > () 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 (

Re: HTML export meta tag

On 5/29/23 14:07, Ihor Radchenko wrote: Scott Randby writes: This did not happen when I used Org 9.4.6: I wouldn't care about this change, but when I validate the page code (https://validator.w3.org/) I get the following: "Info: Trailing slash on void elements has no effect and interact

Re: HTML export meta tag

Scott Randby writes: > > > This did not happen when I used Org 9.4.6: > > > > I wouldn't care about this change, but when I validate the page code > (https://validator.w3.org/) I get the following: "Info: Trailing slash on > void elements has no effect and interacts badly with unquoted attrib