Hi Brianna,
Brianna Laugher wrote:
It's hard to tell if it's useful because it's hard to tell what the purpose of it is. Put search terms in one language, get search results in another? Or something else? What is supposed to be the difference between 'single language' and 'cross language'?
Single language is just like what Wikipedia has already done, but only in a different interface.
For cross-lingual search use case, basically yes, search terms in one language and get results in another. Obviously it's not as good as Google's new experiment, http://translate.google.com/translate_s , but let me introduce a possible scenario:
Translated books in different area may have different convention of terms. In Taiwan, for example, we usually have a translated term in Traditional Chinese followed by the original term in the bucket. In China, however, translated terms in Simplified Chinese usually lack of original terms and indexes. To someone who is reading Simplified Chinese articles, it may be useful to search in Simplified Chinese and then get Wikipedia results in English, for disambiguating the term.
It's just a college student project and I want to extend it. That's why I'm asking for more possible use cases that could be helpful.
Also, it is not currently aware of redirects and this produces multiple results for one page, search for 'HSK' to see an example.
I see, it should be considered to mark.
Also does it use interwiki links to determine the 'cross language' links? It seems like it doesn't... it should! It would be able to produce better links in many more languages than five or so.
I can only guess since I didn't have the source code yet (expected to have in a week). According to my friend, the adviser of this system, it did use interwiki links but seems not enough, so they decided to parse all contents in five languages for a demo purpose.
Thank you for your precious advises!
Sincerely, /Mike/