From: Jens Lechtenboerger <jens.lechtenboerger@fsfe.org>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: ox-html: Bug or feature for export of title and meta information?
Date: Sat, 15 Feb 2020 08:45:22 +0100 [thread overview]
Message-ID: <874kvsfg4t.fsf@informationelle-selbstbestimmung-im-internet.de> (raw)
In-Reply-To: <87y2t5rmna.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Fri, 14 Feb 2020 20:31:37 +0100")
On 2020-02-14, at 20:31, Nicolas Goaziou wrote:
> Hello,
>
> Jens Lechtenboerger <jens.lechtenboerger@fsfe.org> writes:
>
>> 1. Export to HTML when the title contains markup, say this one:
>>
>> #+TITLE: This does *not* work
>
> What does not work?
>
>> The HTML title element contains a nested b element, which is
>> invalid as only text is allowed.
>
> Who said that? The above is perfectly valid.
Good morning (over here),
the W3C Markup Validator [1] disagrees with this output from
ox-html (which I reduced to the essential parts):
#+begin_src html
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<title>This does <b>not</b> work</title>
</head>
<body><p></p></body></html>
#+end_src
Best wishes
Jens
[1] https://validator.w3.org/#validate_by_input
next prev parent reply other threads:[~2020-02-15 7:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-21 12:20 ox-html: Bug or feature for export of title and meta information? Jens Lechtenboerger
2020-02-11 8:16 ` Bastien
2020-02-14 17:21 ` Jens Lechtenboerger
2020-02-14 19:31 ` Nicolas Goaziou
2020-02-14 19:38 ` Nicolas Goaziou
2020-02-14 20:47 ` Bastien
2020-02-15 14:35 ` Nicolas Goaziou
2020-02-16 10:44 ` Bastien
2020-02-15 7:45 ` Jens Lechtenboerger [this message]
2020-02-15 14:02 ` Nicolas Goaziou
2020-02-16 18:16 ` Jens Lechtenboerger
2020-02-17 9:47 ` Nicolas Goaziou
2020-02-17 18:32 ` Jens Lechtenboerger
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=874kvsfg4t.fsf@informationelle-selbstbestimmung-im-internet.de \
--to=jens.lechtenboerger@fsfe.org \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/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).