From: Max Nikulin <manikulin@gmail.com>
To: "András Simonyi" <andras.simonyi@gmail.com>
Cc: emacs-orgmode list <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] oc-csl: New custom option `org-cite-csl-sentence-case-bibtex-titles'
Date: Fri, 21 Jun 2024 17:27:04 +0700 [thread overview]
Message-ID: <e4264d65-0ff1-4813-bc76-eb1783b95e92@gmail.com> (raw)
In-Reply-To: <CAOWRwxDqLyYUr-dyMFDUcZJUajbpLQ9Y5=2PZeJH-zFdBb=kxA@mail.gmail.com>
On 19/06/2024 16:27, András Simonyi wrote:
> On Wed, 15 May 2024 at 13:48, Max Nikulin wrote:
>
>> I had a hope that it might alleviate the issue and to make things
>> working out of the box for more users.
[...]
> Of course it could be checked whether
> a CSL style contains explicit instructions about how to format titles
> and skip sentence-case conversion of input for those but this
> probably would not
> solve the problems of users who do not want the conversion at all.
Do you mean using title (original) case despite some style requites
sentence case for English entries? I believed that fields should be
surrounded with double braces {{...}} this case and the only issue is
difference of original capitalization and result of conversion to
sentence case and then back to title case.
>> It is not clear for me why `org-cite-csl-sentence-case-bibtex-titles' is
>> a part of Org, not of citeproc-el. The only thing that Org can do is to
>> pass it to citeproc-el. It is not configurable per .org file and likely
>> it should not be. From my point of view it might be more suitable per
>> .bib file. Anyway it is almost unrelated to Org.
>
> citeproc-el doesn't have customizable user options by design because
> it was conceived as a relatively low level
> rendering library. Also, it's used by several user-facing packages by
> now in addition to Org (org-ref, citar etc.) so
> I think it would be both confusing and difficult to try to keep this
> type of customizations in the library.
My expectation is that to get consistent results across applications,
they should share the same preference. However since your choice is
conscious, I do not insist.
next prev parent reply other threads:[~2024-06-21 10:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-11 15:33 [PATCH] oc-csl: New custom option `org-cite-csl-sentence-case-bibtex-titles' András Simonyi
2024-05-11 17:26 ` Ihor Radchenko
2024-05-14 9:58 ` András Simonyi
2024-05-17 13:34 ` Ihor Radchenko
2024-06-17 11:39 ` Ihor Radchenko
2024-06-18 15:52 ` András Simonyi
2024-06-19 9:27 ` András Simonyi
2024-06-19 14:36 ` Ihor Radchenko
2024-06-20 5:56 ` András Simonyi
2024-06-21 10:27 ` Max Nikulin [this message]
2024-07-06 9:59 ` András Simonyi
2024-07-08 10:57 ` Max Nikulin
2024-07-08 12:56 ` András Simonyi
2024-07-08 15:18 ` András Simonyi
2024-07-12 10:58 ` Max Nikulin
2024-05-15 11:48 ` Max Nikulin
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=e4264d65-0ff1-4813-bc76-eb1783b95e92@gmail.com \
--to=manikulin@gmail.com \
--cc=andras.simonyi@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).