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: Fri, 14 Feb 2020 18:21:34 +0100 [thread overview]
Message-ID: <87k14pdqzl.fsf@informationelle-selbstbestimmung-im-internet.de> (raw)
In-Reply-To: <8736bhwnbl.fsf@gnu.org> (Bastien's message of "Tue, 11 Feb 2020 09:16:46 +0100")
On 2020-02-11, at 09:16, Bastien wrote:
> Hi Jens,
>
> it is difficult to justify existing code, it is easier to answer to
> bug reports. If you think there is a bug in this aread, can you tell
> what it is?
Hi Bastien,
many thanks for following up on this!
I see two or more bugs:
1. Export to HTML when the title contains markup, say this one:
#+TITLE: This does *not* work
The HTML title element contains a nested b element, which is
invalid as only text is allowed.
2. The documentation does not explain which headers are exported how
to HTML. I described different variants in my previous e-mail.
I’m not sure whether there was a reason to treat them differently.
So, this is at least a bug in the documentation (with potentially
more bugs in the code if the current treatment was not desirable).
Best wishes
Jens
next prev parent reply other threads:[~2020-02-14 17:21 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k14pdqzl.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.