From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id EOBgGHQSyWPGUgEAbAwnHQ (envelope-from ) for ; Thu, 19 Jan 2023 10:50:44 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id +PxHGHQSyWM9QgAA9RJhRA (envelope-from ) for ; Thu, 19 Jan 2023 10:50:44 +0100 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 054E415705 for ; Thu, 19 Jan 2023 10:50:43 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pIQOV-00059Z-0I; Thu, 19 Jan 2023 03:35:35 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pIQOT-00059R-MH for emacs-orgmode@gnu.org; Thu, 19 Jan 2023 03:35:33 -0500 Received: from mout-p-201.mailbox.org ([80.241.56.171]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_CHACHA20_POLY1305:256) (Exim 4.90_1) (envelope-from ) id 1pIQOR-0005hx-Dj for emacs-orgmode@gnu.org; Thu, 19 Jan 2023 03:35:33 -0500 Received: from smtp102.mailbox.org (smtp102.mailbox.org [10.196.197.102]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-201.mailbox.org (Postfix) with ESMTPS id 4NyGCr1Lllz9v0B; Thu, 19 Jan 2023 09:35:20 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=guelker.eu; s=MBO0001; t=1674117320; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=N7nhBzeDB6BmRm2raCeX7DEzDL4sXiab1xflHD2SRTE=; b=Q3OnRkBE6GpBSUe0NIvuUZNAlSq7rE76R4dtILi/kbdUcdGKIzoaUaCR6rDYiXIp7dz+FQ 0BCdsxbDjU5IB/PKA0LqXvaSFkIZBD29zU8r8pIS1GnMfxh7lxKjVysXZYlVWo4efUBxZu yZPxtj4EHyMRy3pwGAZIAjxmU2Xog+WvuhCtTRAYIG4oK7pYdFyaOgaGEPfxTGNB57Ddv5 /GpmuzDPr0uJL/LJntIvioqJnod3X664UxI1+uCvP11NMCSeKph9aPRIujLCHgh6N4fVzo 6zGZjcUtnBfcfuW3S6JXenS2o6pNY9EcvUXJyPTGlAJlEb3h/o61gIWybr78EQ== References: <87r0ytoqi6.fsf@localhost> <87k04dlvie.fsf@localhost> <87zgd87di9.fsf@localhost> <87zgauqzb8.fsf@guelker.eu> <87ilh889bz.fsf@localhost> From: M. =?utf-8?B?4oCYcXVpbnR1c+KAmSBHw7xsa2Vy?= To: =?utf-8?Q?Andr=C3=A1s?= Simonyi Cc: Ihor Radchenko , emacs-orgmode@gnu.org Subject: Re: [PATCH][oc-csl] Improve reference parsing Date: Thu, 19 Jan 2023 09:21:35 +0100 In-reply-to: Mail-Followup-To: =?utf-8?Q?Andr=C3=A1s?= Simonyi , Ihor Radchenko , emacs-orgmode@gnu.org Message-ID: <87wn5isz00.fsf@guelker.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=80.241.56.171; envelope-from=post+orgmodeml@guelker.eu; helo=mout-p-201.mailbox.org X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN ARC-Seal: i=1; s=key1; d=yhetil.org; t=1674121844; a=rsa-sha256; cv=none; b=tcUB8ngRIRWfMjKYmom2BNL2pDFsmmCiq777HKv93/9rPfvPw6LAAJiEl9bpwZxhsqSqjg 4uK668TcIdFi/6x1kaN8365LfvNiiqOdA7ASn+imHQTNNZZn7P4w4cuUNbKWKkDsnnz23H fCNnLrkf7YSdegf3xotPBNctosTvF1Q9NHyKQMH9noANj0ThdTaHlU96/nl8DQZ+P3L7wf pWeia6MDwT0o3bxT4llOFwToiZHr0gUqF5Gcia+2QxYCRm9OHO1XN76nvZxZvHDP3xMON9 Z2kok+NRce505nOnIYY6Hn7MU8ddWv9Il66uD0juGE9vk8LQ9qprHBLU4qq9yg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=guelker.eu header.s=MBO0001 header.b=Q3OnRkBE; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1674121844; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=N7nhBzeDB6BmRm2raCeX7DEzDL4sXiab1xflHD2SRTE=; b=DhvLYOgyRal65nAqbo2JHUhNdneKrSBnIrWwW020InWNRgZVGJ6Red9Kd7CXT8HLTMEANr ybUOPYJMWU+LbxVTcOdE9NGeF5q3fuka1zT411kZszoR2F6KzAsyOguaPVQtXeI8wb/37J Q15C5ELYj7emk1m7wZPrHtbwIl7KtaXSZTFhnsfWxsLsdPpVCfibBdOHQdPGEN9t/Emc0I XmB7/Ln6DWq1B71LCw5WAFrVWRjPG2v9FdxeeT+H+4vnYvtTTIxHTC9ZMwtc1vzgB2FcJB IUusUy7EpYvrytGmkWehsEePMpALCSquFoM/KW7g2UqeDGLKGmcEnAInAM3sVw== X-Spam-Score: -9.43 X-Migadu-Queue-Id: 054E415705 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=guelker.eu header.s=MBO0001 header.b=Q3OnRkBE; dmarc=none; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Scanner: scn0.migadu.com X-Migadu-Spam-Score: -9.43 X-TUID: 0+xixhG5AIqv Am Donnerstag, dem 19. Januar 2023 schrieb Andr=C3=A1s Simonyi: > apologies for replying that late. If I understand the situation > correctly, we could handle the question of allowing macros in > citations independently of the handling of other constructs, because > macros are resolved before processing citations, so they have no > effect on the input of Citeproc-el. In light of this, maybe there > could be a separate patch for just allowing macros? I am not sure this targets the usecase I am pursuing, which is to use macros to produce @@latex: escape constructs in order to have small-caps markup in the citation footnotes: #+MACRO: name @@latex:\textsc{$1}@@@@html:$1@@ If the macro resolves, but the @@latex construct does not, that would be problematic. That being said, I /found/ an alternative that works, albeit it is a bit ugly. I can create an explicit footnote, use a [cite/default/bare:] construct (to suppress the terminal period) within it and terminate the citation before the macro begins. That way, the macro is outside of the citation construct. This construction is however unfortunate when I want to cite multiple sources and have the macro used on an earlier one, e.g.: [fn:1] [cite/default/bare:@foo p. 5], countering {{{name(Doe=E2=80=99s)= }}} argument; [cite/default/bare:@bar p. 37]. It would be nicer if I could just write into the main text [cite:@foo p. 5, countering {{{name(Doe=E2=80=99s)}}} argument;@bar p. = 37] I can however live with the more elaborate construction, if nothing else. -quintus --=20 Dipl.-Jur. M. G=C3=BClker | https://mg.guelker.eu | PGP: Siehe Webseite Passau, Deutschland | kontakt@guelker.eu | O<