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: Sun, 16 Feb 2020 19:16:18 +0100 [thread overview]
Message-ID: <87imk6o0st.fsf@informationelle-selbstbestimmung-im-internet.de> (raw)
In-Reply-To: <87y2t4q78i.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sat, 15 Feb 2020 15:02:05 +0100")
Hi there!
On 2020-02-15, at 15:02, Nicolas Goaziou wrote:
> Jens Lechtenboerger <jens.lechtenboerger@fsfe.org> writes:
>
>> the W3C Markup Validator [1] disagrees with this output from
>> ox-html (which I reduced to the essential parts):
>
> OK. I was talking about the Org syntax. I misread your initial report.
>
> I won't comment about the generated HTML. If needed, the HTML exporter
> can prevent parsing TITLE keyword.
I do not know what is needed. Function org-html--build-meta-info
should return valid XHTML (also in case of HTML5, I believe that
Org syntax is preferable over ignored [1] HTML tags).
Based on the treatment of meta elements for author and description
in that function, alternatives might use org-element-interpret-data
(author) or not (description). I do not understand the role of
org-element-interpret-data to generate author information. Which
“non exportable objects” can be skipped by that function (as
mentioned in a comment in org-html--build-meta-info)? Should they
also be skipped for description or title?
Best wishes
Jens
[1] https://developer.mozilla.org/en-US/docs/Web/HTML/Element/title
next prev parent reply other threads:[~2020-02-16 18:16 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
2020-02-15 14:02 ` Nicolas Goaziou
2020-02-16 18:16 ` Jens Lechtenboerger [this message]
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=87imk6o0st.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).