While translating server resources, I've encountered the following issue a few times:

In English, "Nauru" designs both a country name and a language name, so in the .po file they're factorized:

#: DB:country/name:148 DB:language/name:294
msgid "Nauru"

However, in French the country name and the language name are different, so I can't translate them properly:
country name = "Nauru"
language name = "nauruan"

I've also encountered this type of collision between language and script.

Noting for future reference: Probably the way to fix this is is to either provide context with these strings or to pull these different things from separate message catalogs – I'm inclined to say the latter without having thought too hard about it, since I/we've already been thinking of trying to split up our currently-gigantic catalog into some reusable chunks (e.g. AR names & descriptions, which can be used by many client applications).

This is in beta testing with the origin/split-domains branch (one merge conflict addressed since Ian's branch).