[wp-meta] [Making WordPress.org] #5228: Consistency tool: create wildcard search option
Making WordPress.org
noreply at wordpress.org
Mon May 25 05:01:49 UTC 2020
#5228: Consistency tool: create wildcard search option
--------------------------------------+---------------------
Reporter: felipeloureirosantos | Owner: (none)
Type: enhancement | Status: new
Priority: low | Milestone:
Component: Translate Site & Plugins | Resolution:
Keywords: dev-feedback has-patch |
--------------------------------------+---------------------
Comment (by felipeloureirosantos):
>I don't really like the idea of only accepting a certain number of
requests per user..
I see that. Would limit the search results make sense? Microsoft seems to
show the first 1000.
Also, maybe you can get something useful from the way that they deal with
that: https://www.microsoft.com/en-
us/language/Search?&searchTerm=Test&langID=594&Source=true&productid=0
>For providing links to new contributors, you'd still be able to offer
them the non-wildcard search which seems like a better option to me..
Would Wildcards really be useful for that? Other than as a shortcut for
not having to type the full string?
Yes, it would. Let me provide you an example around that.
If you search for "Props" on the tool (pt_BR), you won't see results:
https://translate.wordpress.org/consistency/?search=Props&set=pt-
br%2Fdefault&project=
You won't actually find something because it comes just as part of the
string.
You can see a string example here:
https://translate.wordpress.org/projects/wp-plugins/wordpress-seo/dev-
readme/pt-
br/default/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=9836026&filters%5Btranslation_id%5D=72632568
The above example is not an exception. It would be useful on several
similar situations.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/5228#comment:7>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list