Ihor - on *, he is bringing oc-csl in line with the oc-natbib and oc-biblatex processors.
On Sun, Jul 3, 2022, 7:57 AM Ihor Radchenko <yanta...@gmail.com> wrote: > András Simonyi <andras.simo...@gmail.com> writes: > > >> By "*", do you mean something like [cite/n:@*]? > >> If so, will it be correctly fontified as an existing citation? > > > > ... As for fontification, this is a very good > > question! I've checked it now with the built-in "basic" > > activation processor and it shows the "*" with an "error" face, > > indicating that it's not a key in the bibliography file(s), which > > might not be ideal. Nonetheless, this problem is not limited to or > > introduced by this patch, because the same construct and > > functionality is also supported by the "biblatex" and "natbib" export > > processors. Actually, the possibility of using "*" as a key comes > > simply > > from a citeproc-el change, not from oc-csl, I just thought that it is > > obscure enough to merit an explicit mention in the NEWS file. > > I do understand that @* syntax is coming from citeproc-el. However, we > are talking about changes to Org core. If Org highlights @* with 'error > face, some users will be confused. > > Could you please elaborate about "the same construct and functionality > is also supported by the "biblatex" and "natbib" export processors"? > I cannot call myself expert in LaTeX, but I've never heard about LaTeX > \cite/\nocite commands supporting "*" argument. I cannot find any traces > of "*" functionality in oc-bibtelatex/oc-natbib as well. > > Best, > Ihor > > >
