From: Denis Maier <email@example.com> To: Bruce D'Arcus <firstname.lastname@example.org>, Denis Maier <email@example.com>, Org Mode List <firstname.lastname@example.org>, email@example.com Subject: Re: (Not so) Short note about citations in Org Date: Mon, 26 Apr 2021 22:14:41 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Oh, and what do you think regarding the multiple bibliographies question? Denis Am 26.04.2021 um 22:02 schrieb Nicolas Goaziou: > Hello, > > "Bruce D'Arcus" <firstname.lastname@example.org> writes: > >> On this, on the other (big) wip-cite thread, Nicolas said the following: >> >> "A drawback with allowing emphasis there is that prefix and suffix become >> parsed data and not plain string anymore. As a consequence, searching >> through them, e.g., when looking for locator names, requires an >> additional level of indirection, since you need to first transform >> parsed data back into plain text." >> >> Nicolas: I get that you need more code to do this, but are there other >> practical consequences of allowing more than plain-text? > > The code I need to write does not count, really. It is 10 locs at most, > without the tests. > > My concern is the additional burden for processor developers. They will > need to shift from one representation to the other, this is not > convenient. Also some tasks then become an order of magnitude harder. > > For example, let's consider the suffix: " p.32 and following" If it is > plain text, I can recognize p.32 as a locator, and replace it with "page > 32" using something like `replace-regexp-in-string'. > > Now, if it is a somewhat opaque parsed string, I need to first expand > it, for example with `org-element-interpret-data', modify the output as > above, and then parse it again to get a new parsed string. > > I can no longer (concat "(" prefix author "," year suffix ")") either, > because prefix and suffix are not strings anymore. I need to > > (format "(%s%s, %s%s)" > (org-export-data prefix info) > (org-export-data author info) > year ;I assume year cannot contain problematic characters > (org-export-data suffix info)) > > So, nothing impossible, but still slightly inconvenient. > > Regards, >
next prev parent reply other threads:[~2021-04-26 20:15 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-21 23:34 Nicolas Goaziou 2021-04-22 0:15 ` Bruce D'Arcus 2021-04-22 0:35 ` Nicolas Goaziou 2021-04-22 0:56 ` Bruce D'Arcus 2021-04-22 12:02 ` Bruce D'Arcus 2021-04-22 13:14 ` Nicolas Goaziou 2021-04-22 13:23 ` Bruce D'Arcus 2021-04-22 17:47 ` M. ‘quintus’ Gülker 2021-04-22 20:44 ` Bruce D'Arcus 2021-04-24 7:53 ` Nicolas Goaziou 2021-04-24 0:07 ` Bruce D'Arcus 2021-04-24 7:53 ` Nicolas Goaziou 2021-04-24 11:40 ` Bruce D'Arcus 2021-04-25 21:19 ` Denis Maier 2021-04-26 18:36 ` Bruce D'Arcus 2021-04-26 20:02 ` Nicolas Goaziou 2021-04-26 20:13 ` Denis Maier 2021-04-26 20:14 ` Denis Maier [this message] 2021-04-26 20:33 ` Nicolas Goaziou 2021-04-26 20:38 ` Denis Maier 2021-04-26 21:11 ` Nicolas Goaziou 2021-04-26 21:52 ` Denis Maier 2021-04-26 21:15 ` Joost Kremers 2021-04-27 12:21 ` Bruce D'Arcus
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 \ --email@example.com \ --subject='Re: (Not so) Short note about citations in 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
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).