Dear All, I've just merged a pull request which hopefully fixes the problem (commit e3bf1f8). (Incidentally, the problems came from major changes in how libxml2 parses trivial html fragments.) best wishes, András
On Thu, 22 May 2025 at 22:11, András Simonyi <andras.simo...@gmail.com> wrote: > > Dear All, > > thanks for reporting -- this seems to be a Citeproc-el problem, most > probably related to Emacs 30.1 (possibly to changes in the xml > parser's output), see the issue at > https://github.com/andras-simonyi/citeproc-el/issues/174. I'll try to > investigate and push a fix shortly. > > best wishes, > András > > On Thu, 22 May 2025 at 21:33, Frederic Santos > <frederic.san...@u-bordeaux.fr> wrote: > > > > Marvin Gülker <m...@guelker.eu> writes: > > > > > I have experienced a similar error recently. The culprit is in the > > > .bib file, namely this line: > > > > > > title = {A Robust Tangent {{PCA}} via Shape Restoration [...] > > > > > > > > > The error happens when you force capitalisation with braces {}. Try > > > this instead: > > > > > > title = {A Robust Tangent PCA via Shape Restoration [...] > > > > Hi Marvin, > > > > Thanks for your answer! Well, you're right: it works, but this is really > > weird... and I'm pretty sure this recent change in Org-cite can really be > > considered as a bug. > > > > My bib files are not created by hand, but exported automatically from a > > Zotero collection (using the BetterBibTeX plugin). Those *double* braces > > {{}} are added by this plugin for protecting each capitalisation when it's > > needed, and it had never raised any problem with Org-mode / Org-cite ever, > > for me, until v9.7.30. I may be wrong, but there's no setting in > > BetterBibTeX to protect capitalisation in other ways than with double > > braces. It's always been working just fine for me. > > Basically, it means any bib file generated from Zotero/BetterBibTeX is now > > unusable through Org (unless you edit it by hand, or run a script to parse > > it each time Zotero exports a new version, which does not look very > > appealing...). > > > > Not sure of what to do here, but I anticipate that a few other people may > > hit a similar issue sooner or later. (There are already the two of us. :-)) > >
