From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Citation syntax: Underscore MUST(?) be allowed in cite keys?
Date: Sat, 07 Mar 2015 09:09:42 -0800 [thread overview]
Message-ID: <87vbiczqcp.fsf@berkeley.edu> (raw)
In-Reply-To: 54FA9AA9.9070505@gmail.com
Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com> writes:
> On Friday 06 March 2015 11:39 PM, Richard Lawrence wrote:
>> Hi Vaidheeswaran,
>>
>> Vaidheeswaran C <vaidheeswaran.chinnaraju@gmail.com> writes:
>>
>>> The following combination works when passed through the LaTeX/PDF
>>> exporter. It doesn't work when the cite syntax is switched to the new
>>> one.
>>>
>>> \cite{center_for_history_and_new_media_zotero_????}
>>
>> Is that a realistic example of a key?
>
> Yes.
> It is generated by Zotero.
OK.
> Have you tried it with \cite{} and \bibliography{} combination and
> seen it works or not. My argument relies on how existing tool works.
I don't understand what your argument is, exactly. So what if Zotero
sometimes produces keys like this? So what if a LaTeX document will
compile with such keys? Is it your position that that means Org keys
must allow punctuation at the end?
> I see that you haven't exporter Zotero libraries to .bib files. My
> guess is the 4 question marks are for "missing" (or "irrelevant") yyyy
> digits.
If such keys represent references with missing data, the document
produced by even `successful' compilation will be incomplete in some
way.
Like I said, this seems like an edge case, and I don't see that it is
necessarily Org's responsibility to accommodate the keys produced by
Zotero in such edge cases. And there is a significant benefit to *not*
accommodating such keys: namely, you can use in-text citations at the
end of a sentence.
Again, if there were reason to think that keys which end with
punctuation are common even in the normal case where the data is
complete and correct, that would be reason to re-think the syntax of Org
citation keys. But Org's citation syntax can't be expected to handle
every tool's behavior in every edge case.
Best,
Richard
next prev parent reply other threads:[~2015-03-07 17:10 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 [this message]
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
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=87vbiczqcp.fsf@berkeley.edu \
--to=richard.lawrence@berkeley.edu \
--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).