cgnieder wrote:
Exactly. There are many warnings that breqn is incompatible with a lot of other packages on other forums like TeX.sx.
I wonder if the minipage error was found
cgnieder wrote:
I wouldn't think so: two of the maintainers, Will Robertson and Joseph Wright, are part of the LaTeX3 development team so they surely are qualified LaTeX programmers. Michael J. Downes (RIP) has been a very versatile TeX programmer and both Morten Høgholm and Lars Madsen also are well known in the TeX community.
That's reassuring.

I'm glad that this is probably caused by them looking ahead and using the newest code concepts etc.
cgnieder wrote:
As I quoted in my earlier response: »With unicode-math one can basically use only specially tailored OpenType math fonts«. If you don't use such a font you won't need the package.
One rule I always follow is: I only load packages where I know exactly what they're for.
I have one reason now. I use the
math-style=ISO
option for ISO style (math bold face style for example)!
cgnieder wrote:
This is a very common thing for many LaTeX packages. There simply are too many for a package maintainer to foresee every account. Some packages are especially required to be loaded after others (thinking of hyperref, glossaries or cleveref...). This is especially true for packages that change some standard LaTeX behaviour like breqn does: incompatibilities are bound to happen...
Best
Yes, I know that sometimes packages need to be loaded in a certain order, e.g. all things to do with internal links (the packages you mention). But in this case, the biblatex package seems unrelated to the
breqn
package, so I thought it's strange that the warning pops up.
In addition, that warning is not even what I'm concerned about anymore: it's the various kind of
errors the breqn package apparently causes, using perfectly normal Latex constructs.