moewew

Erh. This really shouldn't have been closed by my bringing my fork of `polyglossia` up to date. Sorry about this. Reopened.

Yes, we need to handle hyphenation pattern names that differ from the language identifier. Thing is I don't really know how and I think this isn't really `biblatex`'s job: We...

I'm wondering if it wouldn't be easier if `polyglossia`'s `\babelname` (and friends) would *not* return the dot modifiers. After all, `babel`'s `\languagename` doesn't expose the dot modifiers either. Since `polyglossia`...

I guess in that case I'd much rather be given `babelname=latin,` and be left to deal with the rest myself (sift through the options). The trouble with made up things...

The whole reason why I bothered you about the `babel`-equivalent names was so we wouldn't have to think too hard about whether a user uses `polyglossia` or `babel` once we...

Ah, I only saw your reply after I posted the comment above. That would explain things: I want `babelname` to be a `babel`-equivalent, so I just have to deal with...

Thank you for reporting that issue. It seems that the code used to detect whether small caps are available in the current font https://github.com/plk/biblatex/blob/4c0a029acf7c226daacf381957c65df1178cca49/tex/latex/biblatex/biblatex.def#L396-L400 does not work correctly in all...

> Since it is quite unlikely `\textsc` to be used before `biblatex` is imported, is it possible to test this in advance? Yes, we could do that, but if we...

This sounds like a niche feature, but a useful one nonetheless. I'm all for implementing it and would even want to go a bit further and add a similar function...

I looked at making all trackers available as `...entry` versions yesterday and hit a few issues. 1. The `context` version of the trackers uses `\blx@ifcitesingle`, which might not be available...