dheera
commented
9 years ago Hi! Something I've been thinking about but been a bit busy to attack this problem. I'm not sure what the "right" (i.e. Androidic) way to do it is. Advice would be appreciated. The problem is that there are 4 language settings in question:
- The Attopedia language setting, if implemented
- The user's Google Now/voice recognition language
- The user's Google search language
- The phone interface language
If I go with the voice recognition language (is there an API to retrieve this info?), the problem is that the first few Google search results may not match that language. For example, searching "München" (the German name) in Google returns the English article for Munich as the first Wikipedia result, unless I set my Google language also to German. If I search for the language-specific Wikipedia only (i.e. using site:de.wikipedia.org), there are many languages for which Wikipedia does not have the same volume of articles as the English version. For example, although the German Wikipedia is fairly complete, the Malay Wikipedia is not. In these cases I would think that it's best to provide the English language result rather than provide nothing. Is there a way to set this language-first ranking without 2 queries to Google?
If I go with the phone interface language or create a custom setting, the problem is that the voice recognition will not pick up anything if it doesn't match. For example, the user can set their Attopedia setting to German, but if they don't also set their phone to accept German voice recognition, it will not pick up any German, making it impossible to use the app in a useful way.
ghost
I had to compile this App myself to get a german version of it. In SearchActivity (wear) this little change got me the german wiki: [...] http://ajax.googleapis.com/ajax/services/search/web?v=1.0&q=-%22disambiguation+page%22+site: de .wikipedia.org+[...]
How about giving the user an ability to choose the language?