#1994 - De-generalise "missing resource" errors, possibly other messages

Identifier #1994
Issue type Feature request or suggestion
Title De-generalise "missing resource" errors, possibly other messages
Status Closed (duplicate)
Handling member Chris Graham
Addon core
Description Try and not ever use the word "resource" or even "entry" in messaging to the user.

We may just have to bite the bullet and accept that messages will need translating individually for each content type, rather than us having a shared message used for all content types.

Trying to drop in content types to a shared string is dicey, as languages with masculine/feminine and complex tense rules don't allow us to cleanly do that.

Actually, maybe there is a middle-ground. Maybe we can use a shared language string set and generate the messages via a new API function. That function would support individual language strings, as well as building up via inserting the content type. i.e. the individual language strings would be like an override for the automatically constructed phrasing, added to a language pack if and when needed.
Steps to reproduce

Funded? No
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Rating

Unrated