Context Navigation

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

initial	v1
2	2	> Using a translatable core string does not require any new files.
3	3
4		still, it's a new data that needs to be managed (I thought of new file because I imagined a new domain, I see now you're using ~~_x in your example, not __~~, my bad)
	4	still, it's a new data that needs to be managed (I thought of new file because I imagined a new domain, I see now you're using "_x" in your example, not "__" , my bad)
5	5
6	6	> To whole point of this new core functionality is to have a generic fallback for all plugins and themes. You are right, that having a core translation file named with the locale name would be OK for the WordPress core. But all plugins and themes, that do not have a correct lanuguage variant file, would fall back to English.