From: Nicolas Goaziou <email@example.com> To: "Bruce D'Arcus" <firstname.lastname@example.org> Cc: Org Mode List <email@example.com> Subject: Re: [wip-cite-new] New natbib processor Date: Sun, 09 May 2021 22:25:06 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CAF-FPGNKhi-Y6HD-ij2D73BOxruxATzVJfK6AdVZtXD7Tdd=7Q@mail.gmail.com> (Bruce D'Arcus's message of "Sun, 9 May 2021 09:49:57 -0400") Hello, "Bruce D'Arcus" <email@example.com> writes: > To bottom line it, seems the decision comes down to something like > these three choices: > > 1. no change; keep sub-styles as they are ATM > 2. change sub-styles to a simple string. So [cite/text/caps+full:...], > where sub-style is the string "caps+full"; short cut would be > something like [cite:/t/c+f:...] > 2. remove sub-styles entirely; just have things like > [cite/text+caps-full:...], where the style is "text+caps-full"; or > with shortcuts [cite/t+c-f:...] > > Any of them seem reasonable to me. > > Maybe 2 is the best balance of flexibility and simplicity? But there are two 2 ;) I think that sub-styles as currently implemented, i.e., per processor, are not useful. They could as well be replaced by a list of regular styles (e.g., "text-caps-full"). Completion is not really an issue either. We could require export-oriented citation processors to declare the styles they support through a dedicated keyword in `org-cite-register-processor'. Completions utilities, like the function you wrote, could then read from that list. The question you raise about compatibility between processors is interesting however. Without sub-styles, non-standard styles (roughly anything but default, text, author and year) would, as you noted, fallback to default style upon switching citation processors. E.g., "text-caps-full" would become default. With sub-styles, OTOH, fallback mechanism would be able to grab root style and try using it before dropping the ball to default. E.g., "text/caps-full" could gracefully degrade to "text", and, if not supported, default. Sub-styles buy us nicer switching between processors, indeed. But they come at a price, too. In particular, we need to re-define inheritance between styles defined in `org-cite-export-processor', "cite_export" keyword and the citation object. As I wrote earlier in this thread, there are multiple ways to deal with it, so a clear design is in order. Plain styles already exist. Sub-styles requires more work. Does the benefit outweigh it? If so, what do you suggest for the inheritance problem? Regards, -- Nicolas Goaziou
next prev parent reply other threads:[~2021-05-09 20:25 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-05 14:53 Nicolas Goaziou 2021-05-05 15:20 ` Bruce D'Arcus 2021-05-05 15:32 ` Bastien 2021-05-06 12:29 ` Nicolas Goaziou 2021-05-06 12:56 ` Bruce D'Arcus 2021-05-05 18:08 ` Bruce D'Arcus 2021-05-05 21:25 ` Bruce D'Arcus 2021-05-05 21:40 ` Bruce D'Arcus 2021-05-05 22:32 ` Bruce D'Arcus 2021-05-06 7:36 ` Denis Maier 2021-05-06 10:06 ` Bruce D'Arcus 2021-05-06 11:22 ` Bruce D'Arcus 2021-05-06 12:05 ` Nicolas Goaziou 2021-05-06 13:09 ` Bruce D'Arcus 2021-05-06 14:12 ` Nicolas Goaziou 2021-05-06 14:23 ` Bruce D'Arcus 2021-05-06 16:20 ` Nicolas Goaziou 2021-05-06 16:59 ` Bruce D'Arcus 2021-05-06 8:47 ` Bruce D'Arcus 2021-05-06 12:11 ` Nicolas Goaziou 2021-05-06 12:37 ` Bruce D'Arcus 2021-05-07 11:37 ` Bruce D'Arcus 2021-05-08 13:51 ` Bruce D'Arcus 2021-05-09 8:57 ` Nicolas Goaziou 2021-05-09 13:49 ` Bruce D'Arcus 2021-05-09 20:25 ` Nicolas Goaziou [this message] 2021-05-09 22:01 ` Bruce D'Arcus 2021-05-10 17:07 ` Bruce D'Arcus 2021-05-10 20:22 ` Nicolas Goaziou 2021-05-10 20:52 ` Bruce D'Arcus 2021-05-15 21:29 ` Nicolas Goaziou 2021-05-15 21:54 ` Bruce D'Arcus 2021-05-16 9:47 ` Nicolas Goaziou 2021-05-11 12:13 ` Eric S Fraga
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [wip-cite-new] New natbib processor' \ /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
Code repositories for project(s) associated with this 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).