From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastien <bzg@gnu.org>
Subject: Re: ox-html: Bug or feature for export of title and meta
 information?
Date: Sun, 16 Feb 2020 11:44:27 +0100
Message-ID: <875zg66cc4.fsf@gnu.org>
References: <87d0ft3kpa.fsf@informationelle-selbstbestimmung-im-internet.de>
 <8736bhwnbl.fsf@gnu.org>
 <87k14pdqzl.fsf@informationelle-selbstbestimmung-im-internet.de>
 <87y2t5rmna.fsf@nicolasgoaziou.fr> <87tv3trmc6.fsf@nicolasgoaziou.fr>
 <87pnegyjze.fsf@gnu.org> <87sgjbrk8l.fsf@nicolasgoaziou.fr>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:44903)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <bzg@gnu.org>) id 1j3HPe-000112-2o
 for emacs-orgmode@gnu.org; Sun, 16 Feb 2020 05:44:34 -0500
In-Reply-To: <87sgjbrk8l.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of
 "Sat, 15 Feb 2020 15:35:54 +0100")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
 <mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org
Sender: "Emacs-orgmode"
 <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org

Hi Nicolas,

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> I don't think so. It is a constant, which may only matter when you write
> an export-backend. Its value is not even particularly important since
> any back-end can ignore it. Only its syntax really matters, as pointed
> out in, e.g., `org-export-define-derived-backend' docstring. To sum it
> up, I see it is an implementation detail.

I see, thanks.

> The manual might, however, be more rigorous about what keywords each
> back-end really interprets. I don't know how, and where, it could fit,
> tho.

I guess a tutorial on how to write a new export backend will give us a
hint on where and how to mention this. I am not sure it belongs to the
manual.

Best,

-- 
 Bastien