Changes between Version 7 and Version 8 of BluePrintTransliteration

Timestamp:

12/30/11 13:14:01 (13 years ago)

Author:

Daniel Klischies

Comment:

--

BluePrintTransliteration

@@ -25 +25 @@
 The last aspect that needs to be mentioned is the work required to maintain everything. If there is an update by one of the transliteration services requiring us to rebuild our JSON/XML files, everything might get outdated.
 
-Another point is the GUI. We need a textarea with similar functions like Eclipse's autocomplete or Visual Studio's IntelliSense, a dropdown with possible meanings a letter combination can have. The only suitable solution found so far is [[http://wiki.jqueryui.com/w/page/12137993/ListBuilder | jQueryUI ListBuilder]]. This needs a bit of styling, but supports JSON as a data source. 
+Another point is the GUI. We need a textarea with similar functions like Eclipse's autocomplete or Visual Studio's IntelliSense, a dropdown with possible meanings a letter combination can have. The only suitable solution found so far is [[http://wiki.jqueryui.com/w/page/12137993/ListBuilder | jQueryUI ListBuilder]]. This needs a bit of styling, but supports JSON as a data source.
+
+=== 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.
+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).
 
 == Suggestion ==