| 50 | | === Implementation === |
| 51 | | If we would decide to develop the transliteration input ourselves, the recommended approach is an S3Widget, as it is easy to implement into the existing structures of Eden (a simple widget=TransliterationTextarea in the model is the only thing we would need to change to enable transliteration for a text-value). As everything has to be real-time, the Widget should fire an AJAX request. The problem is the data source. Even if the websites above would allow us to use their data, we would have to bring the given data into a consistent format like XML or JSON. |
| 52 | | Furthermore everything needs to be tested a LOT, as the data might not be 100% correct. Lives may depend on it and if a CAP message, for instance, is not correct because the transliteration engine made a mistake, we have a serious problem. Because of this we need native speakers of these languages to test them. |
| 53 | | 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. |
| 54 | | |
| 55 | | 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. |
| 56 | | |
