Last modified: 2012-02-16 12:13:55 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T36416, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 34416 - Suggestion: add a prefix filter to the Translatewiki search interface to limit to a subset of messages starting with that prefix (similar to MediaWiki:Allmessages prefix search)
Suggestion: add a prefix filter to the Translatewiki search interface to limi...
Status: RESOLVED DUPLICATE of bug 32060
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
unspecified
All All
: High normal (vote)
: ---
Assigned To: Niklas Laxström
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-02-15 08:36 UTC by T. Gries
Modified: 2012-02-16 12:13 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description T. Gries 2012-02-15 08:36:33 UTC
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
Comment 1 Niklas Laxström 2012-02-15 08:42:55 UTC
Please provide an use case that we can evaluate it: As ____ (translator) I can ____ so that ___.
Comment 2 T. Gries 2012-02-15 11:21:39 UTC
(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- .
Comment 3 Niklas Laxström 2012-02-15 15:21:43 UTC
With Translate you can view all messages (in a given language) for any group and use browser's search.
Comment 4 T. Gries 2012-02-15 20:04:55 UTC
(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.
Comment 7 T. Gries 2012-02-15 20:09:40 UTC
Please send me a deep link to translatewiki.net with which I immediately see

- all
- messages in Deutsch 
- in Extension AJAXPoll
- which uses the prefix: poll-
Comment 8 T. Gries 2012-02-15 20:10:46 UTC
(In reply to comment #6)
> Try this:
> https://translatewiki.net/w/i.php?title=Special%3ATranslate&taction=translate&group=ext-openid&language=de&limit=1000&task=view
> 
> Is that what you were
> Looking for?

90% yes
10% not

Why isn't there a _simple prefix- filter like in MediaWiki core ?
Comment 9 Siebrand Mazeland 2012-02-15 20:11:56 UTC
Because we do not see a reason why that should exist.
Comment 10 T. Gries 2012-02-15 20:15:18 UTC
(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 ! )
Comment 11 Siebrand Mazeland 2012-02-15 20:19:02 UTC
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.
Comment 12 Nemo 2012-02-16 12:13:55 UTC
This is a duplicate, the other bug has more use cases which I'll now clarify.

*** This bug has been marked as a duplicate of bug 32060 ***

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links