Context Navigation

Changes between Initial Version and Version 1 of Ticket #28197, comment 7

initial	v1
1	1	@grapplerulrich There's no additional work required from the translators, on the contrary. First, that's a totally optional solution, the "en_US" (or "en_UK") files don't have to be renamed to "en" (and even then, that's not much of a work), and second, it simplifies work for plugins and themes developers who wants to provide localised versions.
2	2
3		I can see some theoretical or political reasons why locales should be kept separated but from a purely practical standpoint, me having to provide 4+ version of spanish files where one would be enough to make most people happy is just ludicrous and actually prevent them from using their language.
	3	I can see some theoretical or political reasons why locales should be kept separated but from a purely practical standpoint, me having to provide 4+ version of spanish files where one would be enough to make most people happy is just ludicrous and actually prevent them from using my plugins in their language.
4	4
5	5	Contrary to what I said earlier there's also no actual requirement for WP to decide on a default locale per language, it would just be better. And it can also be done on a per language basis. I can imagine people agreeing on en_UK being the default English and if Ukrainian is an issue then let things separated (Tho I should note that the idea is to fallback on a default locale, not another language, like in your Ukrainian/Russian exemple).