From: Stefan Nobis <stefan-ml@snobis.de>
To: emacs-orgmode@gnu.org
Subject: Re: Citation syntax: Underscore MUST(?) be allowed in cite keys?
Date: Mon, 09 Mar 2015 12:27:41 +0100 [thread overview]
Message-ID: <m17fuq76mq.fsf@nobis-it.eu> (raw)
In-Reply-To: <54FD7A20.60907@gmail.com> (Vaidheeswaran C.'s message of "Mon, 09 Mar 2015 16:16:56 +0530")
Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com> writes:
> By saying "bibtex is not a requirement",
I said "exporting to bibtex". You talked about Zotero but showed a
bibtex entry. Therefore exporting from Zotero to bibtex may not
be a requirement, there may be a direct interface to Zotero,
eventually.
We are at the start of the development, we are currently CUTTING EDGE!
Therefore tool support (hopefully including guides to configure
citation managers) will evolve in the future.
My main point is: You found a single example that *may* be a problem
with the current syntax. But there are multiple software packages
involved (Zotero, Zotero to bibtex exporter, org-mode, etc.). The
citation syntax will never be able to handle all of the possible
problems in a longer chain of tools. Sometimes its better to fix a
problem at the start of in the middle of this chain.
IMHO it's a good idea to constrain the syntax for keys a little bit
(no whitespace, no arbitrary unicode character, no punctuation at the
end etc.). If in some cases the default configuration of the involved
tools will create invalid keys, than the configuration should be fixed
instead of dropping constraints for the key syntax.
> I hope you don't mean to imply that bibtex users are any less
> blessed or less holy or that their needs wouldn't be "readily"
> catered to.
I am a bibtex user. :)
I want to say, that it is impossible to accomodate for all the
citations managers with any possible configurations of them. Sometimes
we have to state: This case is not supported, please adjust your
configuration.
--
Until the next mail...,
Stefan.
next prev parent reply other threads:[~2015-03-09 11:28 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 18:21 Citation syntax: Underscore MUST(?) be allowed in cite keys? Vaidheeswaran C
2015-03-04 18:30 ` Rasmus
2015-03-04 18:42 ` Vaidheeswaran C
2015-03-04 19:01 ` Rasmus
2015-03-04 19:18 ` Vaidheeswaran C
2015-03-04 21:38 ` Christian Moe
2015-03-05 5:00 ` Richard Lawrence
2015-03-06 10:49 ` Nicolas Goaziou
2015-03-06 11:55 ` Rasmus
2015-03-06 17:34 ` Nicolas Goaziou
2015-03-06 17:55 ` Rasmus
2015-03-06 21:01 ` Eric S Fraga
2015-03-06 12:41 ` Vaidheeswaran C
2015-03-06 18:09 ` Richard Lawrence
2015-03-07 6:28 ` Vaidheeswaran C
2015-03-07 17:09 ` Richard Lawrence
2015-03-07 18:20 ` Vaidheeswaran C
2015-03-08 8:19 ` Stefan Nobis
2015-03-07 17:50 ` Thomas S. Dye
2015-03-08 0:18 ` Nicolas Goaziou
2015-03-08 2:12 ` Rasmus
2015-03-08 4:19 ` Thomas S. Dye
2015-03-08 12:34 ` Rasmus
2015-03-08 17:07 ` Thomas S. Dye
2015-03-08 17:49 ` Rasmus
2015-03-09 1:56 ` Richard Lawrence
2015-03-09 2:29 ` Thomas S. Dye
2015-03-09 8:57 ` Stefan Nobis
2015-03-09 9:19 ` Vaidheeswaran C
2015-03-09 9:49 ` Stefan Nobis
2015-03-09 10:46 ` Vaidheeswaran C
2015-03-09 11:02 ` Rasmus
2015-03-09 11:27 ` Stefan Nobis [this message]
2015-03-09 16:05 ` Richard Lawrence
2015-03-09 16:37 ` Thomas S. Dye
2015-03-09 16:49 ` Eric S Fraga
2015-03-09 17:49 ` Thomas S. Dye
2015-03-09 18:00 ` Eric S Fraga
2015-03-09 18:44 ` Thomas S. Dye
2015-03-09 19:26 ` Eric S Fraga
2015-03-09 18:50 ` Richard Lawrence
2015-03-09 21:07 ` Rasmus
2015-03-09 22:33 ` Richard Lawrence
2015-03-10 0:37 ` Rasmus
2015-03-10 15:35 ` Richard Lawrence
2015-03-10 0:36 ` Richard Lawrence
2015-03-10 7:06 ` Eric S Fraga
2015-03-10 8:15 ` Nicolas Goaziou
2015-03-10 8:50 ` Rasmus
2015-03-10 10:18 ` Eric S Fraga
2015-03-10 14:35 ` Matt Price
2015-03-10 15:32 ` Richard Lawrence
-- strict thread matches above, loose matches on Subject: below --
2015-03-04 18:21 Vaidheeswaran C
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=m17fuq76mq.fsf@nobis-it.eu \
--to=stefan-ml@snobis.de \
--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).