From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jens Lechtenboerger Subject: ox-html: Bug or feature for export of title and meta information? Date: Sat, 21 Sep 2019 14:20:01 +0200 Message-ID: <87d0ft3kpa.fsf@informationelle-selbstbestimmung-im-internet.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:54269) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iBeMx-0003BE-4B for emacs-orgmode@gnu.org; Sat, 21 Sep 2019 08:20:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iBeMw-0002Gk-9H for emacs-orgmode@gnu.org; Sat, 21 Sep 2019 08:20:07 -0400 Received: from mx2a.mailbox.org ([80.241.60.219]:60355) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1iBeMw-0002GK-30 for emacs-orgmode@gnu.org; Sat, 21 Sep 2019 08:20:06 -0400 Received: from smtp1.mailbox.org (smtp1.mailbox.org [IPv6:2001:67c:2050:105:465:1:1:0]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by mx2.mailbox.org (Postfix) with ESMTPS id D3CF7A1934 for ; Sat, 21 Sep 2019 14:20:04 +0200 (CEST) Received: from smtp1.mailbox.org ([80.241.60.240]) by spamfilter01.heinlein-hosting.de (spamfilter01.heinlein-hosting.de [80.241.56.115]) (amavisd-new, port 10030) with ESMTP id vYCtxd5SF3HV for ; Sat, 21 Sep 2019 14:20:02 +0200 (CEST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Hi there, I wonder about the treatment of different pieces of HTML header information in org-html--build-meta-info: Contents for the title element are computed by org-export-data. This interprets Org markup such as italics or hyperlinks although title elements are not allowed to contain the resulting sub-elements. Why is org-export-data applied? Why not produce plain text? Contents for the description and keywords meta attributes are computed with org-html-encode-plain-text and replacement of quotation marks. Seems fine to me. Contents for the author meta attribute are computed with org-element-interpret-data, before org-html-encode-plain-text and quotation mark replacement are applied. How would author information look like that benefits from this more complex treatment (compared to description and keywords)? Thanks Jens