Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Create a standard for naming keys of lexicons #14313
There is confusion in the keys of lexicons, for example, there are duplicate lines with different keys (for example, new_tv | tv_new | add_tv), there is also excessive terminology.
I propose to mark the standard of the name of the keys, and bring the current lexicons to the new standard (many duplicates will be deleted).
It makes sense to link other elements through the key, if they are connected according to logic, for example in the system settings:
The key must clearly indicate its "essence" and "location" of the key, and only then the action or characteristic of the key:
Using the example "mgr_browser_sort_default" key, we see what needs to be written:
There are many discussions, but there is no standard, it is necessary to designate it and always refer to it.
Perhaps it is worth making lexicons in a separate project on github and in the process of working with it, define the standard and the final changes (what has changed, what has been removed).
Lexicon keys should be easy to group, sort, filter and describe their purpose.
A lexicon named
To describe a key's purpose I think it would be better to name them like this:
Without context it's more clear for a translator that values for those keys should describe the name/description for something referring to an "site index identifier" setting.
In my opinion, "setting_name" is an unnecessary expression, just "setting" is already enough.
The problem is not so much in the writing of keys, but in the fact that there are too many variants for keys, for example, the section "Back-end Manager" in the "System Settings":