From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Standardize #+BIBLIOGRAPHY line Date: Mon, 22 Jul 2013 11:03:55 +0200 Message-ID: <87hafn55l0.fsf@gmail.com> References: <87k3kjyr37.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44384) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1CCF-00074h-Ex for emacs-orgmode@gnu.org; Mon, 22 Jul 2013 05:14:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V1CCE-0002JG-0R for emacs-orgmode@gnu.org; Mon, 22 Jul 2013 05:14:23 -0400 Received: from mail-wi0-x231.google.com ([2a00:1450:400c:c05::231]:44074) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V1C1u-0006l5-SC for emacs-orgmode@gnu.org; Mon, 22 Jul 2013 05:03:42 -0400 Received: by mail-wi0-f177.google.com with SMTP id ey16so1614114wid.10 for ; Mon, 22 Jul 2013 02:03:42 -0700 (PDT) In-Reply-To: <87k3kjyr37.fsf@gmail.com> (Jambunathan K.'s message of "Mon, 22 Jul 2013 12:55:25 +0530") 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Jambunathan K Cc: emacs-orgmode@gnu.org Hello, Jambunathan K writes: [...] > I am finalizing JabRef support for ODT. At *some* future point in time, > I will include ox-jabref.el (and all other patches) in official Emacs > distribution. Thanks for you work. However, I think it ought to be merged in ox-bibtex.el instead. "ox-bibtex" name is misleading as it is not directly related to "bibtex" program. At its core, it merely introduces a BIBLIOGRAPHY keyword and [[cite:...]] links. It also provides accessors and predicates wrt them: - org-bibtex-get-file - org-bibtex-get-style - org-bibtex-get-arguments - org-bibtex-citation-p - org-bibtex-get-citation-key So, if you use them, you don't have to bother about BIBLIOGRAPHY keyword syntax (at least for now). Also, if we ever use ox-bibtex.el as a basis to implement bibliography handling in Org core, it will be easier to have most major back-ends already behaving uniformly. > You may also want to review the #+TOC settings, more for consistency > than anything else. > > Instead of > #+toc: headlines 4 > > we can have > #+toc: headlines :levels 4 > > or > #+toc: :type headlines :levels 4 Initially, as its name suggests, `org-export-read-attribute' was meant to make attributes keywords more consistent across back-ends. As it is a bit heavy, I'm not convinced that it would be a good generic syntax for all keywords. Also, the problematic is slightly different. "attr_backend" is generic, so it makes sense if its value starts with some :keyword. But what about: #+BEAMER_THEME: Madrid It would be redundant to use #+BEAMER_THEME: :theme Madrid (or :name Madrid). On the other hand, I admit that, currently, #+BEAMER_THEME: Rochester [height=20pt] is not great either. Maybe all of this calls for a generalization of the reader function. Something like "stuff everything before the first keyword as the value of a generic keyword". IOW, #+keyword: :a val :b val2 => (:a "val" :b "val2") #+keyword: text :a val => (:head "text" :a "val") #+keyword: text :head other => not good Regards, -- Nicolas Goaziou