From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Standardize #+BIBLIOGRAPHY line
Date: Mon, 22 Jul 2013 11:03:55 +0200 [thread overview]
Message-ID: <87hafn55l0.fsf@gmail.com> (raw)
In-Reply-To: <87k3kjyr37.fsf@gmail.com> (Jambunathan K.'s message of "Mon, 22 Jul 2013 12:55:25 +0530")
Hello,
Jambunathan K <kjambunathan@gmail.com> 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
next prev parent reply other threads:[~2013-07-22 9:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 7:25 Standardize #+BIBLIOGRAPHY line Jambunathan K
2013-07-22 9:03 ` Nicolas Goaziou [this message]
2013-07-22 13:16 ` Jambunathan K
2013-07-22 13:19 ` Jambunathan K
2013-07-22 13:31 ` Nicolas Goaziou
2013-07-22 13:47 ` Jambunathan K
2013-07-22 13:58 ` Nicolas Goaziou
2013-07-22 16:09 ` Jambunathan K
2013-07-22 19:33 ` Jambunathan K
2013-07-22 14:15 ` Rasmus
2013-07-22 16:29 ` Jambunathan K
2013-07-22 21:51 ` Rasmus
2013-07-25 8:47 ` Jambunathan K
2013-07-22 17:01 ` Jambunathan K
2013-07-22 19:34 ` Jambunathan K
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=87hafn55l0.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
/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).