I, for one, am glad that licenses exist that aren't written in English exclusively.
Most of the world aren't native English speakers and most native English speakers live in a particularly British-derived system of law. Most open source licenses are full of assumptions that the legal system they're implied in are either modeled after the American system or derived from Common Law. Translations exist, but they're not more than that.
The EUPL was explicitly designed to comply with EU trademark and copyright law, which differs from American copyright law in various ways. It also fixed the "you can read the license in your own language but if you want to use those freedoms you'd better learn English because that's the version that counts" problem.
One big limitation to the EUPL is that it only covers European languages (as it was designed for the EU).
I can't say I feel too bad about needing to pick the English license from an alphabetically sorted list. There aren't any officially valid translations of AGPL, nor for Apache, nor for MIT. I don't think many programmers will run into problems using English, as programming is often very English oriented, but for the common people, that's different. A rural farmer with little to no access to higher education should know that he has the right to change the software on the embedded equipment he bought, even if he doesn't speak a word of English. He won't be altering the software, but perhaps he knows someone who could, and knowledge about possibilities can be the start of change.
After all, what freedoms does free software provide if it's only free to the minority of English readers?