On Translatewiki I suggest to add the possibility to limit the search based on a prefix (for example, "abusefilter-").
Such a filter is already in mw core when you look for such a subset see for example https://en.wikipedia.org/w/index.php?title=Special%3AAllMessages&prefix=abusefilter-&filter=all&lang=en&limit=50
Version: unspecified
Severity: normal
Please provide an use case that we can evaluate it: As ____ (translator) I can ____ so that ___.
(In reply to comment #1)
Please provide an use case that we can evaluate it: As ____ (translator) I can
____ so that ___.
As an extension developer I cannot quickly enough retriev all my (english standard, and translated) texts starting with my extension prefix "openid-".
Instead, and this is cumbersom, I need to select MediaWiki Extensions and need to manually load all MW extension texts in bunches of 5000 and the locally use the find function of browser. Currentl, there are more then 14.000 MW extensions texts. It is very difficult.
As an extension developer I wish to have the possibility implemented to retrieve _all_ MediaWiki texts with a certain prefix, in my case openid- .
With Translate you can view all messages (in a given language) for any group and use browser's search.
(In reply to comment #3)
With Translate you can view all messages (in a given language) for any group
and use browser's search.
Please tell me, how.
I cannot.
Please send me a deep link to translatewiki.net with which I immediately see
(In reply to comment #6)
Is that what you were
Looking for?
90% yes
10% not
Why isn't there a _simple prefix- filter like in MediaWiki core ?
(In reply to comment #9)
Because we do not see a reason why that should exist.
hehe!
Reason: harmonisation with MediaWiki core functions ( Special:Allmessages ! )
Just use special:allmessages, I'd say. We think the UI already
Allows for a lot
Of flexibility, And adding more options will reduce usability, scaring users away by rising the barrier to entry. No feature mania allowed.
This is a duplicate, the other bug has more use cases which I'll now clarify.