Follow up to https://github.com/backdrop/backdrop-issues/issues/704:
Seems to be that locale.module remembers the path at which the translated string was first seen, then provides a path to that location? Perhaps that's so that you can try and find if a string is used on that page. However... not very useful for something like site_name which is literally on every page. If we can find a way to suppress this behavior when strings are translated through config, that would be preferable. Most config strings will probably be shown in lots of places (e.g. field labels and descriptions, view names, block titles, etc)
For reference, in D8 there's now a separate table for locale location and it better represents config strings:
Recent comments
Ruby Text can be a bit of a hassle to edit... Yes, I can imagine that. No idea, how an editor dialog (or whatever) for easier editing of those should look like - in terms of...
Specific tags to work in CKEditor 5
"why are these tags only relevant for admins?" I'm allowing the editor as well. That being said, Ruby Text can be a bit of a hassle to edit... easy to accidentally delete a tag or part of a...
Specific tags to work in CKEditor 5
Out of curiosity: why are these tags only relevant for admins? Don't "regular" editors on that site also need them under circumstances? Yes, the editors play nicely, no problem to...
Specific tags to work in CKEditor 5