moewew

Sounds like a plan. I also found `\ifundef\hyper@natanchorstart` in the `hyperref` code https://github.com/plk/biblatex/blob/58f64eb55fb9f534457ebaaca22ae446168218bf/tex/latex/biblatex/biblatex.sty#L12167-L12205 so that `\hyper@natlinkstart` is only used if that command is defined. Do you happen to know why...

Ah. Another thing: For the `hyperref` branch, `biblatex` currently saves and resets spacefactor codes (with `\blx@sfsave` and `\blx@sfrest` - presumably due to whatsits?). Will we need the same for the...

Ah, nice. That should unify the interface a little. Thanks for the answer. I will see if I can rustle something up.

It would be great if you could have a look at https://github.com/moewew/biblatex/commit/c8198ff8bee8a9d4948d13716003cfba164456ae in https://github.com/moewew/biblatex/tree/nohypertag and give it a spin.

I've never tried that. We use `l3build` for our tests, but I'm not sure about other package tests. You can use the file https://github.com/moewew/biblatex/blob/nohypertag/tex/latex/biblatex/biblatex.sty as a drop-in replacement for the...

I'll look into `l3build` at some point, but the last time I looked I had trouble getting it to use the files in subfolders (like `lbx` etc.) for tests and...

The changes discussed here (with global `\providecommand`) are now available via https://github.com/plk/biblatex/commit/cdd65b01c6ec47ae96b507b48a62b62d4c558b58 in `dev`.

I think a release in the very near future is a good idea, yes. I'd still like to deal with https://github.com/plk/biblatex/issues/1348, though. @u-fischer Any thoughts? (Any official LaTeX team advice...

The output seems reasonable. It might be subtly different from what `biblatex` previously had, but so far I don't think anyone complained.

Oh, this is going to be a bigger project. I haven't yet looked at `\babelprovide`, which is a completely different way of loading languages than previously in `babel` (it doesn't...