From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp10.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id 6ORlHYyDOGLyDgEAgWs5BA (envelope-from ) for ; Mon, 21 Mar 2022 14:54:20 +0100 Received: from aspmx1.migadu.com ([2001:41d0:8:6d80::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp10.migadu.com with LMTPS id mG0vFoyDOGJ7ggAAG6o9tA (envelope-from ) for ; Mon, 21 Mar 2022 14:54:20 +0100 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 71F133DDDB for ; Mon, 21 Mar 2022 14:54:19 +0100 (CET) Received: from localhost ([::1]:45406 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nWIUE-0005OY-4l for larch@yhetil.org; Mon, 21 Mar 2022 09:54:18 -0400 Received: from eggs.gnu.org ([209.51.188.92]:43820) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nWIR8-00040t-Ny for emacs-orgmode@gnu.org; Mon, 21 Mar 2022 09:51:07 -0400 Received: from [2607:f8b0:4864:20::f2f] (port=38541 helo=mail-qv1-xf2f.google.com) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nWIR4-000696-JI for emacs-orgmode@gnu.org; Mon, 21 Mar 2022 09:51:06 -0400 Received: by mail-qv1-xf2f.google.com with SMTP id jo24so3991545qvb.5 for ; Mon, 21 Mar 2022 06:51:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:references:user-agent:from:to:cc:subject:date:in-reply-to :message-id:mime-version; bh=0tTpRwgKrYTBZK8sMo9VdF9QPtUhQLcMyvdq2e+Wpw0=; b=PFC8TAPcaOUXx5K7SP1Nzp2W4VbO73sm14FxCzpJAo3ZcoISW/ZOADupniLVZP7DAC i3AJsC0G5+B2dU69DpIKqC2mnaEtTcMcQvLyUHJFbgpYMtpWFUAe74eVBmLc0A5f/qwb 5cKYgKeOguXiTVc3Geiyq7d3XRAckSyVu5U8ZsAxaotIpBEprodMWI/njym6GXUGckTd ETfVW3bHTbAWNY/i48axMqb7xWoUDwsfqY1hHbG6e2zb4x5ghbTvxoxXtK9jiiNdXYNi dE2WbNhEUUTQGhLiKU7KJtQN1ldqShC6eC3nkYC9SMz23bd0MFNbbvqauQ0lM9Mw9xQ7 J4XA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:references:user-agent:from:to:cc:subject :date:in-reply-to:message-id:mime-version; bh=0tTpRwgKrYTBZK8sMo9VdF9QPtUhQLcMyvdq2e+Wpw0=; b=0MU0L50IZPcmDXzgzuJyG4jnhsLZKcTejdbSOKjI+TjCQF0FDch0ZjXX5zNgQb4JMD 96V3o4b423cuwsbhMmkREddZIu2GlMuOTMH6TZIyw+isleV5NEWNjnqLTYfuDEX6tMXe kmWUK7tvYAvhkTZrHfGKoX4ffKfOxPe2EwquhB5yE7r+ine5PU0H8N+NO+2pLe5qe1ZY A0whGCW7wIKRmUHyCPCb2RkFl9MN34ZO8+Yz40ujqUfsTIWSWq974Z1TXpWg3kjcXG+O ghcON3FRvIOOX54rqyR3DR04trNR2LRyiIqf/AgVemT0I236Dw/+IzmFbxf89Y6ij3C8 2KKQ== X-Gm-Message-State: AOAM533OQ75oIoZjTwBJ/pjSF6oRqk1xTz/58eWSTidk+N6raQSKaeNg HI8qPiAXcnB11DEVrrz3k3ioOJKHKmM= X-Google-Smtp-Source: ABdhPJzR9L7CYRYM2GNvuexAEFCdVATWQFjM41Bl82vwzCJa0FCwu5eRZYUAvM+0dUFUhNsmO4T1eA== X-Received: by 2002:ad4:5be5:0:b0:441:97c:a97a with SMTP id k5-20020ad45be5000000b00441097ca97amr8892131qvc.16.1647870660871; Mon, 21 Mar 2022 06:51:00 -0700 (PDT) Received: from Johns-iMac.local ([2601:547:901:82e0:15dd:d6d8:2808:7987]) by smtp.gmail.com with ESMTPSA id o4-20020a05620a22c400b0067e02a697e0sm8098319qki.33.2022.03.21.06.50.59 (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Mon, 21 Mar 2022 06:51:00 -0700 (PDT) References: <87wngosqvm.fsf@nicolasgoaziou.fr> User-agent: mu4e 1.6.10; emacs 28.0.90 From: John Kitchin To: Vikas Rawal Subject: Re: citations: org-cite vs org-ref 3.0 Date: Mon, 21 Mar 2022 07:51:32 -0400 In-reply-to: Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Host-Lookup-Failed: Reverse DNS lookup failed for 2607:f8b0:4864:20::f2f (failed) Received-SPF: pass client-ip=2607:f8b0:4864:20::f2f; envelope-from=johnrkitchin@gmail.com; helo=mail-qv1-xf2f.google.com X-Spam_score_int: 0 X-Spam_score: -0.1 X-Spam_bar: / X-Spam_report: (-0.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, PDS_HP_HELO_NORDNS=0.659, RCVD_IN_DNSWL_NONE=-0.0001, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: org-mode mailing list , Nicolas Goaziou Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1647870860; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=0tTpRwgKrYTBZK8sMo9VdF9QPtUhQLcMyvdq2e+Wpw0=; b=HGry+XBKQbs5M0P6KRXQdDNoJtOMarLk1U0i+h8XpQ4x4M1FqNvC414WoKecdadpjDSBIP r2wXxXL5WgM+Yj/g3QGbn7+B6o+CfwlMedB1n4/2FWnUoqCxXx9kWJRxd2C9XSr2kljRvL GaoONtH897u3DVRudrBPO+SOpjak7Ld9bpWRCF5mL0OZIZWJu818Mnp4OVwHFuok30FXW5 uA2NsAhWjU3MRRIKf3AwksdmW7JGuFibGpxsUEjfgwEjZ8VSAQ80faKrzN9nuWFUzxrA0d zTe5lSW2zu9Aydceaq1LQ1+5uDOKg9u7jQ+AY349ymo9+qUGivFOg1yKDMGAWQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1647870860; a=rsa-sha256; cv=none; b=C0fd1xNpgK3KfsdroTwoROMAkI0uhl7BHQrqo94nP2ZZMQ3cK3zsSdMteHHixofrm8pbTx 49ogDq1zhXbvy1R2Dpp8yu3/J4uMqmojNQ0MYCS4xXPKUHouYvVj5cTqRVrkQyXNErOVWa +Wie6l7ldeFirNWs7kSgZHcV4nNbH9mqfpoqP7133xOvvBt/6cu+5eQRxJmGED0lCipJy4 vfAu8PxuoTzXv6UnRrMD4Vd/SKYhdsoHhrotLTB2y90iliGaOGCBs6+XEEELa4Etx+KO6c Sx+E0UEiQrm7e0lxKSXTi9pNtyGOMiQv2TrQQ3R1XtlhF14sl2mDnX0cwfW+iw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20210112 header.b=PFC8TAPc; dmarc=fail reason="SPF not aligned (relaxed)" header.from=andrew.cmu.edu (policy=none); spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: 6.08 Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=gmail.com header.s=20210112 header.b=PFC8TAPc; dmarc=fail reason="SPF not aligned (relaxed)" header.from=andrew.cmu.edu (policy=none); spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: 71F133DDDB X-Spam-Score: 6.08 X-Migadu-Scanner: scn0.migadu.com X-TUID: QvU7Np2QW5UK Vikas Rawal writes: > 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. I don't think you have to choose. You can use org-cite for citations, and org-ref for cross-references. The citation syntax is orthogonal, you just should not mix them. You can even wire org-ref to use org-cite-insert like this: (setq org-ref-insert-cite-function (lambda () (org-cite-insert nil))) or use your own key binding if you need the prefix arg functionality of org-cite-insert. org-ref is more configurable and modular than it is given credit for. This is not an either/or choice. > > 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. with org-ref-3, this is much better, but org-cite also works well, probably even better if you use footnote styles. Either way, it is not trivial to get the same output from LaTeX and CSL for arbitrary styles. They are often close though. > 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? It is possible to convert, I wouldn't say not very difficult. In principle one maps over the links and citations, and then in reverse order replace the one format with the converted other format in a buffer. That basically means change & to @ (easy), and provide the mapping between org-ref link type and org-cite style. org-ref has 70ish cite commands that it supports because those are in bib(la)tex. If you only use the basic types, it "should be easy". If you use others, you will have to settle for approximately correct in some cases. > 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. citenum and bibentry are the only two I am not sure have a CSL analog. I guess that things like citedate and citetitle are not fully implemented in citeproc. That is fine, org-cite does not need to fully support all of bib(la)tex, no single user needs that. Lots of users need one part or another though, and collectively bib(la)tex exists for them. > > 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. I guess you won't know what all the incompatibilities are until you try this. In my experience with org-ref, there is a years long tail of discovery as people try different things and have corner cases of need. > > 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? They don't have to be integrated. Someone could separate out that functionality. I don't have unlimited time to spend on these things, and org-ref is designed with the constraints I have so that I am able to develop and support it. That is all you should read into this. I don't have the time or energy develop and maintain separate packages that I use together. I do not want to separate org-ref into separate core packages for cross-references, indexes, glossary/acronyms, bibtex utilities, and packages that integrate helm, ivy, etc. > > 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. As far as I can tell, you can already do this. > > Thanks again for your time and effort, > > Vikas -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu Pronouns: he/him/his