moewew

Ah. I can look into not using `\ifthenelse`, but I we can't really control what contributed styles do. Many will have copied standard code that uses `\ifthenelse` and probably won't...

Hmm. `xifthen` looks a bit unmaintained, though, judging by https://github.com/JosselinNoirel/xifthen/issues, so I'm not sure how realistic that is...

I've moved all standard styles away from `\ifthenelse` constructs in https://github.com/plk/biblatex/compare/dev...moewew:biblatex:patches. But this does not actually solve the underlying issue. We have to continue to patch `\ifthenelse` because we cannot...

As mentioned in https://github.com/plk/biblatex/issues/1142 and https://github.com/plk/biblatex/issues/1139, I have little experience with bidi typesetting. So for a proper solution we'd need help from someone who knows how to properly deal with...

I don't have access to the current version of the (German or indeed any) norm. `biblatex`'s standard styles do not attempt to conform to (any interpretation) of the ISO norms....

I don't think there are any plans at the moment to do anything about archival sources (at least I'm not planning anything. @plk obviously has to speak for himself, but...

This is more or less expected behaviour. That's why there is a more verbose warning for this specific issue > Package biblatex Warning: citation 'book3' > (biblatex) was not found...

As you probably know I'm generally not too keen on changes to core definitions like this. Strictly speaking this would be backwards incompatible and could change existing documents. In practice...

The point about auto-exported data is a good one. Especially if people use the "ol' `\clearfield{month}` trick" (as opposed to sourcemapping - which may or may not be a bit...

My worry is that package options work well when they give you a choice of a small number of fixed ... well ... options, but not so great, when there...