Changes between Version 16 and Version 17 of BluePrintTransliteration

Timestamp:

01/03/14 07:50:05 (11 years ago)

Author:

Samsruti Dash

Comment:

--

BluePrintTransliteration

@@ -40 +40 @@
  * [Mygengo Translation API] http://mygengo.com/api/
  * [Microsoft Translator APIs] http://www.microsofttranslator.com/dev/
- * [Speaklite Translate API] http://www.speaklike.com/access-professional-translation-via-api/
+ * [Speaklite Translate API] /
  * [WebServiceX Translate API] http://www.webservicex.net/ws/wsdetails.aspx?wsid=63
+
+||'''Name'''||'''Web URL'''||'''Status'''|| ||
+||Mygengo Translation API||http://mygengo.com/api/||''Online''||Cost According to Translation
+||Microsoft Translator APIs||http://www.microsofttranslator.com/dev/||''Online''
+||Speaklite Translate API||http://www.speaklike.com/access-professional-translation-via-api||''Online''
+||WebServiceX Translate API||http://www.webservicex.net/ws/wsdetails.aspx?wsid=63||''Online''
 === Thoughts about server-side implementation ===
 Another idea that came up is, that it would be nice if a user could search for something by using his or her language specific letters. For example, a user wants to search for "Aspirin" in Arabic letters. Currently, he won't find anything, as the UTF-8 encodings of roman letters are different from the Arabic letters ("Aspirin" == "أسبرين" would fail). The idea is to reverse transliterate the non-roman string into roman letters on server-side and perform the search with the reverse-transliterated string.