Changes between Version 30 and Version 31 of BluePrintTransliteration


Ignore:
Timestamp:
01/03/14 10:31:47 (8 years ago)
Author:
Samsruti Dash
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintTransliteration

    v30 v31  
    9797  Serbian, Tamil, Telugu, Tigrinya and Urdu.
    9898=== Thoughts about server-side implementation ===
    99 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.
    100 That would require modification of the search-engine. The transliteration database could be the same as for the client-side (again, XML or JSON is recommended).
    101 
     99" 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.
     100That would require modification of the search-engine. The transliteration database could be the same as for the client-side (again, XML or JSON is recommended). "