From: Ihor Radchenko <yantar92@gmail.com>
To: Bruce D'Arcus <bdarcus@gmail.com>
Cc: alain.cochard@unistra.fr, Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: @string abbreviation in bib file not honored in (basic) org-cite
Date: Sat, 09 Jul 2022 11:55:36 +0800 [thread overview]
Message-ID: <877d4n9byf.fsf@localhost> (raw)
In-Reply-To: <CAF-FPGPMwe4DvB3ZGwUz66uXNcEL7_NjQ2pJocXTh4acD4atJQ@mail.gmail.com>
"Bruce D'Arcus" <bdarcus@gmail.com> writes:
> On Fri, Jul 8, 2022 at 7:25 AM <Alain.Cochard@unistra.fr> wrote:
>
>> As I do not know which of these alternatives
>>
>> - it is normal, this feature should not be there,
>> - it is an oversight,
>> - this feature is not implemented yet,
>
> I believe this is the answer, and it's arguable (I have no opinion,
> and could see reasonable arguments either way) whether a "basic"
> processor should support it?
>
> The parsebib library, which most third party packages use (for
> org-cite, there's my citar), does support this feature.
oc-basic.el is relying on built-in bibtex.el. AFAIK, bibtex.el does not
support @string abbreviations.
The problem with parsebib is that it does not even have license
(I do not see any in https://github.com/joostkremers/parsebib). If
parsebib were a part of Emacs core or at least a part of ELPA, we would
also be able to use it in Org core.
Or one could extend bibtex.el with abbreviation support.
Best,
Ihor
next prev parent reply other threads:[~2022-07-09 3:55 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 11:17 @string abbreviation in bib file not honored in (basic) org-cite Alain.Cochard
2022-07-08 12:05 ` Bruce D'Arcus
2022-07-09 3:55 ` Ihor Radchenko [this message]
2022-07-09 8:40 ` András Simonyi
2022-07-10 9:22 ` Can citeproc be installed without using MELPA? (was: @string abbreviation in bib file not honored in (basic) org-cite) Ihor Radchenko
2022-07-10 19:37 ` Joost Kremers
2022-07-11 2:06 ` Ihor Radchenko
2022-07-12 10:23 ` András Simonyi
2022-07-09 6:10 ` @string abbreviation in bib file not honored in (basic) org-cite [and a minimal working example with natbib] Alain.Cochard
2022-07-09 12:40 ` Bruce D'Arcus
2022-07-10 7:17 ` Ihor Radchenko
2022-07-12 11:14 ` András Simonyi
2022-07-12 11:36 ` John Kitchin
2022-07-12 11:48 ` András Simonyi
2022-07-13 4:52 ` Alain.Cochard
2022-08-07 14:08 ` Ihor Radchenko
2022-07-17 8:26 ` @string abbreviation in bib file not honored in (basic) org-cite Ihor Radchenko
2022-07-17 8:52 ` Alain.Cochard
2022-07-19 20:35 ` Joost Kremers
2022-07-19 20:40 ` Bruce D'Arcus
2022-07-20 10:46 ` Joost Kremers
2022-07-28 12:12 ` Ihor Radchenko
2022-07-29 8:02 ` Joost
2022-10-30 6:25 ` Ihor Radchenko
2022-11-02 21:54 ` Joost Kremers
2022-11-03 7:25 ` Ihor Radchenko
2022-11-04 14:26 ` Joost Kremers
2022-11-05 8:13 ` Ihor Radchenko
2022-11-07 18:41 ` Joost Kremers
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=877d4n9byf.fsf@localhost \
--to=yantar92@gmail.com \
--cc=alain.cochard@unistra.fr \
--cc=bdarcus@gmail.com \
--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).