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: Thu, 06 May 2021 14:29:28 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <CAF-FPGN2OVgFwZG5T1VmjyL6Ev+D-t6d94yAKsHCsh2email@example.com> (Bruce D'Arcus's message of "Wed, 5 May 2021 11:20:31 -0400") Hello, "Bruce D'Arcus" <firstname.lastname@example.org> writes: > The question comes down to whether to support sub-styles or not, and > if yes, what the syntax should be. > > I think it makes more sense to include them because otherwise you end > up with an insanely long list of styles, which won't map well onto > different kinds of output formats. I think only oc-citeproc (and oc-basic) may be targetting multiple output formats. I doubt it would even use styles; I assume that is entirely determined by the CSL file. > E.g. biblatex users will want like 20 commands available, which won't > all work with other formats. So you would have 20 styles, with shortcuts for the most commons. This is not insane, and the mapping is done only once. Styles do not need to be compatible between processors. As a reminder, there's the "fallback rule". According to it, each processor must: - provide a default styles; - map any unknown style to the style above. Thanks to this, there will not be any incompatibility between documents upon switching processors. Agreeing on a small set of common styles is a good thing; this is what your doing on your wiki. But there is nothing wrong to map "text-alt-full" style to the default one in another processor. Of course, the default style may be unrelated to "text", but is it a problem in practice? If you switch processor and use complex styles (here style + sub-styles), you will need to change them anyway, because the compatibility is so low. > Also consider that for processors, they're going to have to map those > internally to something like styles+sub-styles anyway. Exactly. For developers, it doesn't make a huge difference here. > Even if not perfect, I think it's a small price to pay for the > benefits. I'm still not convinced by the benefits. Could you describe a situation where sub-styles would be really beneficial? Regards, -- Nicolas Goaziou
next prev parent reply other threads:[~2021-05-06 12:30 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 [this message] 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 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --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).