User Details
- User Since
- Dec 15 2014, 6:00 PM (441 w, 4 h)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- Phoenix303 [ Global Accounts ]
Jul 16 2016
Dec 31 2015
Oct 26 2015
Oct 14 2015
Oct 5 2015
Sep 22 2015
Sep 10 2015
Aug 28 2015
Aug 25 2015
If you want your project to be featured in the blogpost on the Google OSPO blog, kindly comment back with a short, catchy description of the project along with a screenshot.
Aug 24 2015
Aug 22 2015
Aug 21 2015
Aug 20 2015
Aug 19 2015
Aug 18 2015
According to Niklas, language search should index all the words(using default analyzer), therefore, we do not need language analyzer now.
With some more testing and digging deeper into the features of ElasticSearch, I have found few conclusions we made earlier not to be completely true.
- ElasticSearch does not score phrase matches higher( not found any document to support ), but scores AND higher than OR. In other words, even with the default 'OR' search ES would score documents which match all the query words high. However, this is only true for each shard. ES does not score based on the entire index (globally) Ref.
- An example in translatewiki.net and with the offset=150.
Something like this. I have used an alphabet 'X' here. Does the positioning look good? what about the color, I think a different color like red would look better?
Aug 17 2015
Aug 15 2015
Aug 14 2015
Yes, the project is almost complete. It is available here
By when do you think you can merge the code, if at all?
The code review is in progress by @Nikerabbit.
Aug 12 2015
Aug 9 2015
Aug 7 2015
Aug 6 2015
Jul 31 2015
Jul 27 2015
This is taken care of by the existing update().
Jul 26 2015
Thanks @Nemo_bis for the feedback.
Jul 25 2015
See T106931
Jul 21 2015
Jul 19 2015
Jul 18 2015
Jul 16 2015
I would like to propose a design for Cross language search.
Jul 10 2015
Searching any word in the string is the default behaviour which is already supported in the product.
Thanks @Nemo_bis
We have been able to provide a user to search in the source language which defaults to the wiki's content language and get translations in their language. We have not come up yet with any interface to let users select a source language or tell user what source language is searched in, however, a user can force the search in any source language with URL parameter 'sourcelanguage'.
One solution to find the source language is to detect the language of the search string using a language detection plugin, if one already exists? The another solution can be to let a user select it while typing a search string, see the attached mockup.
Jul 9 2015
Jul 8 2015
Jul 7 2015
@Nemo_bis: Source language is English for http://translation-search.wmflabs.org/w/index.php?title=Special:SearchTranslations&filter=translated&language=ksh&query=edit&string=edit&uselang=en
and Finnish for http://translation-search.wmflabs.org/w/index.php?title=Special:SearchTranslations&filter=translated&language=ksh&query=edit&string=edit&uselang=fi right?
Jul 5 2015
Jul 3 2015
Thank you so much @Nemo_bis @Nikerabbit :)
@Nemo_bis: Thank you. Will recheck all the smaller bugs found.