Ok, that's the known bug then. We're still working on fixing that. Basically the default language strings fail to load properly in the language finder when the backend language is anything other than English. It only impacts the language finder though so it's a bit of a strange issue to track down and fix, but believe it's due to language tags not being normalized in our API, which we're looking to fix.