@AlanMunn I'm using biber 2.16 from texlive on a mac without problems. I did not get this error for years.

@JosephWright didn't you want to setup a doodle for the workshop date?

@UlrikeFischer Yes, I am going to do it over my lunch break today (slipped my mind)

@UlrikeFischer Have been busy fixing bugs in siunitx ;)

@JosephWright I lost track of the version number ;-)

@UlrikeFischer If you look back, I had exactly the same with v1 and v2 - lots and lots of bug fix releases

@UlrikeFischer v3.0.15 just went to CTAN

@UlrikeFischer I'm pondering how much to put in v3.1.0 - the complex number upgrade looks nice and easy ...

@UlrikeFischer I'm mainly happy so far that the change of how I do fonts hasn't really been an issue - it's all been about oversights or subtle bugs, almost all in the number code

@LukeTheWolf You need to find one with the correct cover:

@samcarter_looks_forward_TUG'21 I didn't think our library was so well stocked, I did find that too! bit.ly/3d2NmMV

Holy moly, that book's older than me :D

@LukeTheWolf :) much better!

@LukeTheWolf Frank is working on TLC3 :)

amazon.co.uk/LaTeX-Companion-Techniques-Computing-Typesetting/…

@JosephWright That's crazy! amazon.it sells the digital version for only 38 € (compared to 54 £ of the UK's version LOL)

@LukeTheWolf It's about right given it's an 'academic' textbook, really

@JosephWright I'm afraid, I think I've explained myself incorrectly: what I found strange was the fact that the digital version of this book on amazon.co.uk costs £54, while the same version on amazon.it costs €38. Quite a difference for being the same book

Today I found the following quote making me blush:

> However, there is another keyval package that does: the excellent package expkv.

(from the SemanTeX documentation)

@Skillmon I took a look: I suspect something to do with parsing [...]? (Of course, expkv is very good)

@Skillmon but nobody will read the documentation and see that praise

@samcarter_looks_forward_TUG'21 Yes, me too.

@Skillmon <3

@JosephWright ooh 14 Jan. 2022

@PauloCereda Indeed ...

@JosephWright interesting arrangement on the doodle :-)

@DavidCarlisle ooh will there be a duck?

@PauloCereda conference dinner

@DavidCarlisle oh no

@DavidCarlisle perhaps one should add another day @JosephWright ;-)

@UlrikeFischer Looking at tex.stackexchange.com/questions/602271/… I'm thinking about merging luaotfload's score-dev branch to fix all these issues. I'm a bit worried though that it breaks stuff. Does it work on your system?

@MarcelKrüger hmm what does score-dev do?

@UlrikeFischer It rewrites the classification logic for regular/bold/italic/bolditalic fonts to ensure that: Every family has a regular font and bold/italic fonts are bold/italic relative to the regular font.

Therefore it allows e.g. to load Latin Modern Roman Slanted by fontname using fontspec since it no longer complains that no font in the family is regular.

But since it completely changes the detection code, there is the risk of it breaking while analyzing weird fonts (e.g. I just fixed an issue which occured only for a font with italic angle higher than 17000) and it might select different font variants by default, thereby changing documents.

@MarcelKrüger hm, probably we should discuss that with the team.

@MarcelKrüger btw: did you see the question on the context list about "bidi and empty line"? I directly thought about your bug and wondered ;-)

@JosephWright the "issue" is that \keyval_parse:NNn has the rule that there can only be one equals sign on top level per pair (expkv treats that differently, assuming that the first equals sign is the separator), and though [] adds a pair of brackets (similar enough like braces when it comes to optional arguments) for the user's eye that isn't regarded as sufficient protection for \keyval_parse:NNn. So he suggests using expkv's parser if one wants to nest key=value macros.

@JosephWright either that, or his own package strictex, that will replace every [ with [{ and every ] with }] with LuaTeX's input buffer manipulations.

@JosephWright oh, and: aaww for the part in parentheses :)

@DavidCarlisle I did, the only person who matters in this regard to me :D

@PauloCereda CARROT!

@Skillmon Sure, I just mean that as the example has \foo[...] then ideally the split is to take \foo first