Changes between Version 25 and Version 26 of BluePrintTransliteration


Ignore:
Timestamp:
01/03/14 08:22:14 (8 years ago)
Author:
Samsruti Dash
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintTransliteration

    v25 v26  
    7373that this is not the same as translation -- it is the sound of the words that is converted from one alphabet to the other, not their meaning.
    7474Converted content will always be in Unicode.
     75
    7576[[Image(http://3.bp.blogspot.com/_C8NLLuO4CdQ/S1VUnCIT1ZI/AAAAAAAAESo/j9iqcDc0QSE/s400/IME_edit_window.png)]]
    7677
    77  Google Transliteration IME offers several features focused on an improved user experience, including offline support, word completion, personalized choices, easy-to-use keyboard, quick search and several cool customization options. As a user types, a suggestion menu is displayed with alternatives and word completions. For example, as you type "googl" you will see five options from you can select the correct one.
     78Google Transliteration IME offers several features focused on an improved user experience, including offline support, word completion, personalized choices, easy-to-use keyboard, quick search and several cool customization options. As a user types, a suggestion menu is displayed with alternatives and word completions. For example, as you type "googl" you will see five options from you can select the correct one.
    7879
     80A developer can download the Google Transliteration IME. Google Transliteration IME is currently available for 19 different
     81languages - Amharic, Arabic, Bengali, Farsi (Persian), Greek, Gujarati,Hindi, Kannada, Malayalam, Marathi, Nepali, Punjabi, Russian, Sanskrit,
     82Serbian, Tamil, Telugu, Tigrinya and Urdu.
    7983=== Thoughts about server-side implementation ===
    8084Another 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.