While this may sound bad, it really isn't all that bad. There are plenty of other transliterators. I personally prefer Bing to Google. You also have Quillpad and Baraha. Apart from this, I use a tool called Keymmanweb on the English wikipedia which works as an on screen indic keypad. There are plenty of alternatives to Google. Just as we don't use Google Maps for locations, but use all providers including OSM, we can try something new this time. Regards, Rsrikanth05
On May 27, 2011 11:35 PM, "Sudhanwa Jogalekar" sudhanwa.com@gmail.com wrote:
Google shutting down translate and transliterate APIS. Many Indic websites & applications will now be affected
Read more here: http://googlecode.blogspot.com/2011/05/spring-cleaning-for-some-of-our-apis....
Looks like this is the right time for WMF tech team to create their own APIs
--Sudhanwa
~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~! web: www.sudhanwa.com blog: www.sudhanwa.in Twitter: sudhanwa Check on FB, Linkedin for more.
_______________________________________________ Wikimediaindia-l mailing list Wikimediaindia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimediaindia-l
Just noticed, Google is replacing the Translation API with Google Web Elements, available at http://www.google.com/webelements/#!/translate Do have a look and see, if you can make anything of it. I can't find anything from Google to replace the Transliteration API, I won't be surprised if they ask us to use the Translator toolkit. Microsoft Translator : http://www.microsofttranslator.com/
On 28 May 2011 00:07, Srikanth Ramakrishnan rsrikanth05@gmail.com wrote:
While this may sound bad, it really isn't all that bad. There are plenty of other transliterators. I personally prefer Bing to Google. You also have Quillpad and Baraha. Apart from this, I use a tool called Keymmanweb on the English wikipedia which works as an on screen indic keypad. There are plenty of alternatives to Google. Just as we don't use Google Maps for locations, but use all providers including OSM, we can try something new this time. Regards, Rsrikanth05
On May 27, 2011 11:35 PM, "Sudhanwa Jogalekar" sudhanwa.com@gmail.com wrote:
Google shutting down translate and transliterate APIS. Many Indic websites & applications will now be affected
Read more here:
http://googlecode.blogspot.com/2011/05/spring-cleaning-for-some-of-our-apis....
Looks like this is the right time for WMF tech team to create their own APIs
--Sudhanwa
~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~! web: www.sudhanwa.com blog: www.sudhanwa.in Twitter: sudhanwa Check on FB, Linkedin for more.
Wikimediaindia-l mailing list Wikimediaindia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimediaindia-l
Sorry for the incessant replies. Here is what I meant to post in the previous post. Microsoft Indic Language Input Tool http://specials.msn.co.in/ilit/Hindi.aspx
Regards, Rsrikanth05
On 28 May 2011 01:19, Srikanth Ramakrishnan rsrikanth05@gmail.com wrote:
Just noticed, Google is replacing the Translation API with Google Web Elements, available at http://www.google.com/webelements/#!/translate Do have a look and see, if you can make anything of it. I can't find anything from Google to replace the Transliteration API, I won't be surprised if they ask us to use the Translator toolkit. Microsoft Translator : http://www.microsofttranslator.com/
On 28 May 2011 00:07, Srikanth Ramakrishnan rsrikanth05@gmail.com wrote:
While this may sound bad, it really isn't all that bad. There are plenty of other transliterators. I personally prefer Bing to Google. You also have Quillpad and Baraha. Apart from this, I use a tool called Keymmanweb on the English wikipedia which works as an on screen indic keypad. There are plenty of alternatives to Google. Just as we don't use Google Maps for locations, but use all providers including OSM, we can try something new this time. Regards, Rsrikanth05
On May 27, 2011 11:35 PM, "Sudhanwa Jogalekar" sudhanwa.com@gmail.com wrote:
Google shutting down translate and transliterate APIS. Many Indic websites & applications will now be affected
Read more here:
http://googlecode.blogspot.com/2011/05/spring-cleaning-for-some-of-our-apis....
Looks like this is the right time for WMF tech team to create their own APIs
--Sudhanwa
~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~!~! web: www.sudhanwa.com blog: www.sudhanwa.in Twitter: sudhanwa Check on FB, Linkedin for more.
Wikimediaindia-l mailing list Wikimediaindia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimediaindia-l
-- Regards, ME. Wear a Lungi, Support the Movement My infrastructure invasion... plus other images too.. on Wikimedia Commons. http://bit.ly/d50SIq
There is major problem in depending upon Non-FOSS solutions. It seems google used api's for collecting crowd sourced input for improving their database & now shutting it down. Input methods such as Tranlitration does not need online services . It can be easily done without google or microsoft. And popularise extensions such as Narayam existing on mediawiki is the best way to move forward. In addition, it will be good if Indic wikipediam's can develop a stylebook for correct usage and link it with extensions such as narayam. Then the possibility of typing errors can also be reduced.
In my pinion Translation Service& its api of google for indic is not that great anyway , and usable for wikimedia projects . So i believe it will not make much issues in wikimedia indic projects
Anivar
On Sat, May 28, 2011 at 8:23 AM, Anivar Aravind anivar.aravind@gmail.com wrote:
There is major problem in depending upon Non-FOSS solutions.
There is. However, the line that comes immediately next might just need to be couched as a personal opinion in the absence of cited facts around it :)
It seems google used api's for collecting crowd sourced input for improving their database & now shutting it down. Input methods such as Tranlitration does not need online services . It can be easily done without google or microsoft. And popularise extensions such as Narayam existing on mediawiki is the best way to move forward. In addition, it will be good if Indic wikipediam's can develop a stylebook for correct usage and link it with extensions such as narayam. Then the possibility of typing errors can also be reduced.
I am more interested in the line in Sudhanwa's mail which seems to suggest that WMF should be providing APIs (and, hosting a service therefore ?) around this aspect.
And, I am afraid I also do not comprehend the usage of the term 'stylebook' - what does it mean in this context ?
In my pinion Translation Service& its api of google for indic is not that great anyway , and usable for wikimedia projects . So i believe it will not make much issues in wikimedia indic projects
The usage of the Google Translate API has been, for a while, discussed under the umbrella of whether the translated content can be 'freely' (as in libre-ly) used across domains.
On Wed, Jun 1, 2011 at 11:58 AM, sankarshan foss.mailinglists@gmail.com wrote:
On Sat, May 28, 2011 at 8:23 AM, Anivar Aravind anivar.aravind@gmail.com wrote:
There is major problem in depending upon Non-FOSS solutions.
There is. However, the line that comes immediately next might just need to be couched as a personal opinion in the absence of cited facts around it :)
It seems google used api's for collecting crowd sourced input for improving their database & now shutting it down.
We have seen its evolution & improvement of service with wide adoption over time. One curious factor i used to notice always is the formation of words with chillu characters in transliteration API . Since there is a standard difference between Unicode 5.0 and 5.1 Chillu Characters it is easy to identify. Google is officially following most recent unicode version, but since most of the malayalam users uses chillu letters in unicode 5.0 specifications, it is periodically changed in that way .
Input methods such as Transliteration does not need online services . It can be easily done without google or microsoft. And popularise extensions such as Narayam existing on mediawiki is the best way to move forward. In addition, it will be good if Indic wikipedian's can develop a stylebook for correct usage and link it with extensions such as narayam. Then the possibility of typing errors can also be reduced.
I am more interested in the line in Sudhanwa's mail which seems to suggest that WMF should be providing APIs (and, hosting a service therefore ?) around this aspect.
Yes, it is an interesting possibility
And, I am afraid I also do not comprehend the usage of the term 'stylebook' - what does it mean in this context ?
In google transliterate , it took a lot of time to correct spellings in word formations Since wikipedia have a large DB , and editors , who are aware about correct usage , a style book of correct indic language spellings for transliterated inputs can help input tools like narayam to auto correct common spelling errors . It was a major feature of google transliterate . This can be also implemented in API level as well
In my opinion Translation Service& its api of google for indic is not that great anyway , and usable for wikimedia projects . So i believe it will not make much issues in wikimedia indic projects
The usage of the Google Translate API has been, for a while, discussed under the umbrella of whether the translated content can be 'freely' (as in libre-ly) used across domains.
In case anybody missed out. Transliteration: http://en.wikipedia.org/wiki/User:Keymanweb/Keymanweb Enjoy. Cheers.
On 1 June 2011 12:41, Anivar Aravind anivar.aravind@gmail.com wrote:
On Wed, Jun 1, 2011 at 11:58 AM, sankarshan foss.mailinglists@gmail.com wrote:
On Sat, May 28, 2011 at 8:23 AM, Anivar Aravind anivar.aravind@gmail.com wrote:
There is major problem in depending upon Non-FOSS solutions.
There is. However, the line that comes immediately next might just need to be couched as a personal opinion in the absence of cited facts around it :)
It seems google used api's for collecting crowd sourced input for improving their database & now shutting it down.
We have seen its evolution & improvement of service with wide adoption over time. One curious factor i used to notice always is the formation of words with chillu characters in transliteration API . Since there is a standard difference between Unicode 5.0 and 5.1 Chillu Characters it is easy to identify. Google is officially following most recent unicode version, but since most of the malayalam users uses chillu letters in unicode 5.0 specifications, it is periodically changed in that way .
Input methods such as Transliteration does not need online services . It
can be easily done
without google or microsoft. And popularise extensions such as Narayam existing on mediawiki is the best way to move forward. In addition, it will be good if Indic wikipedian's can develop a stylebook for correct usage and link it with extensions such as narayam. Then the possibility of typing errors can also be reduced.
I am more interested in the line in Sudhanwa's mail which seems to suggest that WMF should be providing APIs (and, hosting a service therefore ?) around this aspect.
Yes, it is an interesting possibility
And, I am afraid I also do not comprehend the usage of the term 'stylebook' - what does it mean in this context ?
In google transliterate , it took a lot of time to correct spellings in word formations Since wikipedia have a large DB , and editors , who are aware about correct usage , a style book of correct indic language spellings for transliterated inputs can help input tools like narayam to auto correct common spelling errors . It was a major feature of google transliterate . This can be also implemented in API level as well
In my opinion Translation Service& its api of google for indic is not that great anyway , and usable for wikimedia projects . So i believe it will not make much issues in wikimedia indic projects
The usage of the Google Translate API has been, for a while, discussed under the umbrella of whether the translated content can be 'freely' (as in libre-ly) used across domains.
Wikimediaindia-l mailing list Wikimediaindia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikimediaindia-l
wikimediaindia-l@lists.wikimedia.org