Changes between Version 16 and Version 17 of BluePrintTransliteration


Ignore:
Timestamp:
01/03/14 07:50:05 (7 years ago)
Author:
Samsruti Dash
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintTransliteration

    v16 v17  
    4040 * [Mygengo Translation API] http://mygengo.com/api/
    4141 * [Microsoft Translator APIs] http://www.microsofttranslator.com/dev/
    42  * [Speaklite Translate API] http://www.speaklike.com/access-professional-translation-via-api/
     42 * [Speaklite Translate API] /
    4343 * [WebServiceX Translate API] http://www.webservicex.net/ws/wsdetails.aspx?wsid=63
     44
     45||'''Name'''||'''Web URL'''||'''Status'''|| ||
     46||Mygengo Translation API||http://mygengo.com/api/||''Online''||Cost According to Translation
     47||Microsoft Translator APIs||http://www.microsofttranslator.com/dev/||''Online''
     48||Speaklite Translate API||http://www.speaklike.com/access-professional-translation-via-api||''Online''
     49||WebServiceX Translate API||http://www.webservicex.net/ws/wsdetails.aspx?wsid=63||''Online''
    4450=== Thoughts about server-side implementation ===
    4551Another 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.