From: "Bruce D'Arcus" <email@example.com>
To: "András Simonyi" <firstname.lastname@example.org>
Cc: "Rudolf Adamkovič" <email@example.com>,
"emacs-orgmode list" <firstname.lastname@example.org>
Subject: Re: [RFC PATCH] oc-csl: Add support for title, locators and bibentry styles
Date: Sat, 13 Aug 2022 10:01:04 -0400 [thread overview]
Message-ID: <CAF-FPGMr=t4jsWKqJsHnuRrojQJOUvTZQ5QWZsrm0p75z8M4_Q@mail.gmail.com> (raw)
On Sat, Aug 13, 2022 at 8:30 AM András Simonyi <email@example.com> wrote:
> Dear All,
> On Tue, 9 Aug 2022 at 17:38, Rudolf Adamkovič <firstname.lastname@example.org> wrote:
> > THANK YOU for working on this! I have tried the "locators" style, and
> > it works great. At last, we can write in the APA style with no hacks!
> thanks for your kind words, I'm glad that you find the additions useful.
> > P.S. Not a fan of using "ti" for the title. I would go for "T" for
> > "Title", or "p" for "publication", or "s" for "subject", or something
> > like that.
> interesting, it didn't occur to me that we could use capital letters
> as well, certainly an alternative to consider.
I'm not a fan; I think it would open a can-of-worms vis-a-vis the
latex processors and commands.
> Another solution could be to make the whole mapping customizable as
> it's done, I think, in the case of the biblatex export processor.
I actually think the case for this is weakest with the oc-csl processor.
Here, there is no style -> command mapping; it's just direct.
So effectively the style names and shortcuts are just aesthetic.
And changing them means the citations are then tied to the export
processor, and the specific user.
prev parent reply other threads:[~2022-08-13 14:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 11:14 [RFC PATCH] oc-csl: Add support for title, locators and bibentry styles András Simonyi
2022-08-02 12:08 ` Bruce D'Arcus
2022-08-07 9:46 ` Ihor Radchenko
2022-08-08 17:01 ` András Simonyi
2022-08-09 12:03 ` Ihor Radchenko
2022-08-09 15:38 ` Rudolf Adamkovič
2022-08-13 12:30 ` András Simonyi
2022-08-13 14:01 ` Bruce D'Arcus [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).