From: Vikas Rawal <vikasrawal@gmail.com>
To: John Kitchin <jkitchin@andrew.cmu.edu>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: citations: org-cite vs org-ref 3.0
Date: Mon, 21 Mar 2022 08:57:19 +0530 [thread overview]
Message-ID: <CALtzAB3dRXU+j32ZE2yX_C3ii7CuQeZyohSNrKWgksuA5j-utA@mail.gmail.com> (raw)
In-Reply-To: <m2sfrc149c.fsf@andrew.cmu.edu>
[-- Attachment #1: Type: text/plain, Size: 3442 bytes --]
Dear John,
Thanks very much for taking time to write a detailed reply.
I do not think it is productive for the community to say or consider it
> is a sad situation.
From the perspective of a user, this was only meant to express a sentiment
that one finds oneself in a situation of having to choose between two good
things, and that we have not been able to find a way to make both
compatible with each other. It was in not meant as a disrespect in any way.
My use case is very similar to yours and I have been an org-ref user for a
long time (I was surely one of the earliest beneficiaries of your work),
having written two books and innumerable research papers with org-ref
citation syntax. Being able to export to LaTeX has been my primary use but
the fact that citations were not exported easily to other formats thus far
was a problem I had to struggle with every now and then.
> There are more than 8 years of legacy org-ref documents. I have written
> 40+ scientific papers with it, and countless technical documents with
> more than 8000 cite links among them. org-ref has exceeded 190K
> downloads from MELPA, so I feel obligated to maintain org-ref for
> myself, and those users.
Given that it is not very difficult to convert a document from old org-ref
citation syntax to the org-cite syntax, at least as far as citation is
concerned, this should not be a big problem. Do these documents use
citation commands that are not available in org-cite? Can those not be
added to org-cite?
> I think org-ref and org-cite have different priorities, they solve
> different problems with different approaches, and they have different
> pros and cons.
It might be useful to discuss specific gaps (such as citenum) that need to
be plugged in org-cite for it to be usable. In fact, making org-cite usable
for a heavyweight user like you is a useful goalpost.
I understand that you do not particularly like the modularity and
complexity of org-cite way of specifying styles and variants. But if one is
able to make the two compatible, filling the gaps, they could have a
friendly co-existence with some way of being able to convert a document
between the two styles. And if there are some incompatibilities that cannot
be resolved, it would be good to know exactly what all those are. If
somebody was to write functions to convert from one format to the other,
they could choose how they want to deal with those incompatibilities.
> Cross-references are critical for me; without them, there is no path
> forward for me with org-cite. I did work on a cross-reference approach
> that leveraged org-cite syntax
> (https://github.com/jkitchin/org-ref-cite/issues/16), but there was not
> much appetite for the approach so I abandoned that.
What org-ref seems to do with cross-references is very nice. Unfortunately
this would not be available if a user chooses to use org-cite. Do the
capabilities of cross-referencing have to be wedded to the citation system?
Can this not be resolved?
> I am content to agree to disagree on these points and move forward with
> both packages because they solve different problems, are suitable for
> different communities, and they continue to benefit each other.
Friendly co-existence should be our goal. But can that be a situation in
which one is able to choose between the best of both and, as far as
possible, switch from one to the other.
Thanks again for your time and effort,
Vikas
[-- Attachment #2: Type: text/html, Size: 4675 bytes --]
next prev parent reply other threads:[~2022-03-21 3:28 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 12:08 citations: org-cite vs org-ref 3.0 Vikas Rawal
2022-03-20 13:19 ` Nicolas Goaziou
2022-03-20 14:08 ` Vikas Rawal
2022-03-20 14:38 ` Bruce D'Arcus
2022-03-21 0:31 ` John Kitchin
2022-03-21 1:39 ` Timothy
2022-03-21 8:16 ` Dominik Schrempf
2022-03-21 11:51 ` Bruce D'Arcus
2022-03-21 12:34 ` Dominik Schrempf
2022-03-21 12:52 ` Bruce D'Arcus
2022-03-21 13:05 ` Dominik Schrempf
2022-03-21 13:24 ` Bruce D'Arcus
2022-03-23 21:27 ` Nicolas Goaziou
2022-03-23 21:53 ` Bruce D'Arcus
2022-03-23 22:04 ` Nicolas Goaziou
2022-03-23 22:47 ` Bruce D'Arcus
2022-03-24 10:04 ` Dominik Schrempf
2022-03-21 12:19 ` John Kitchin
2022-03-21 12:42 ` Bruce D'Arcus
2022-03-21 14:06 ` John Kitchin
2022-04-19 22:37 ` Bruce D'Arcus
2022-03-21 3:27 ` Vikas Rawal [this message]
2022-03-21 11:51 ` John Kitchin
2022-03-21 17:20 ` Vikas Rawal
2022-03-25 15:53 ` Max Nikulin
2022-03-27 15:33 ` John Kitchin
2022-03-27 15:44 ` Vikas Rawal
2022-03-25 17:10 ` Max Nikulin
2022-03-26 12:41 ` Bruce D'Arcus
2022-03-27 19:40 ` John Kitchin
2022-03-28 12:34 ` Max Nikulin
2022-03-28 13:16 ` Bruce D'Arcus
2022-03-29 15:22 ` Max Nikulin
2022-03-29 16:14 ` Bruce D'Arcus
2022-03-30 13:50 ` Denis Maier
2022-03-31 15:10 ` Max Nikulin
2022-03-31 17:27 ` Bruce D'Arcus
2022-04-02 11:41 ` org-cite, CSL styles and space before citation Max Nikulin
2022-03-30 21:43 ` citations: org-cite vs org-ref 3.0 John Kitchin
2022-03-21 12:59 ` juh
2022-03-22 13:03 ` indieterminacy
2022-03-23 21:06 ` Nicolas Goaziou
2022-03-27 17:00 ` John Kitchin
2022-03-27 23:17 ` Bruce D'Arcus
2022-03-21 14:40 ` Max Nikulin
2022-03-21 15:19 ` Bruce D'Arcus
2022-03-21 17:00 ` John Kitchin
2022-03-25 15:21 ` Max Nikulin
2022-03-22 14:41 ` Max Nikulin
2022-03-22 17:20 ` Bruce D'Arcus
2022-03-23 12:44 ` Max Nikulin
2022-03-23 14:39 ` Bruce D'Arcus
2022-03-23 15:26 ` Eric S Fraga
2022-03-23 17:17 ` Max Nikulin
2022-03-23 22:50 ` Bruce D'Arcus
2022-03-26 19:08 ` M. Pger
2022-03-22 23:52 ` Nicolas Goaziou
2022-03-23 16:30 ` Max Nikulin
2022-03-23 23:04 ` Nicolas Goaziou
2022-03-25 16:30 ` Max Nikulin
2022-03-27 15:38 ` John Kitchin
2022-03-27 23:18 ` Bruce D'Arcus
2022-03-20 13:32 ` Bruce D'Arcus
2022-03-20 13:42 ` Ihor Radchenko
2022-03-20 18:12 ` Thomas S. Dye
2022-03-20 20:13 ` Dominik Schrempf
2022-03-20 20:30 ` Vikas Rawal
2022-03-20 20:34 ` Bruce D'Arcus
2022-03-20 22:10 ` Dominik Schrempf
2022-03-20 19:44 ` Bruce D'Arcus
2022-03-20 21:14 ` chris
2022-03-21 14:21 ` John Kitchin
2022-03-21 14:10 ` John Kitchin
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=CALtzAB3dRXU+j32ZE2yX_C3ii7CuQeZyohSNrKWgksuA5j-utA@mail.gmail.com \
--to=vikasrawal@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jkitchin@andrew.cmu.edu \
--cc=mail@nicolasgoaziou.fr \
/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).