Changes between Version 15 and Version 16 of BluePrintTransliteration

01/03/14 05:16:31 (7 years ago)
Samsruti Dash



  • BluePrintTransliteration

    v15 v16  
    2929According to the points explained above, a transliteration engine is quite a lot of work, as we have no consistent database of roman -> Indian, Chinese, or Cyrillic characters which we could use. As long as we are not able to find one, an implementation of a transliteration engine is not recommended. If we could find a professional and consistent database we could start to implement the feature using the JQuery plugin explained above.
    31 == Possible use-cases ==
    32 The CAP broker, which is currently  [[ | work-in-progress]], supports messages in different languages. A CAP Profile for Sri Lanka would require that a message carries the <> segment carry information in Sinhala, Tamil, and English. Message creators will need to type the <> for all three languages with the country-specific language characters.Example, the hazard event "tsunami" pronounced su-na-mi, when typed in this manner would result in the Sinhalese equivalent "සුනාමි".
    34 Another one is an emergency coordinator may want to search for a person's name or product name written in the localized script. For example, the medical proper noun "Aspirin" would we pounced the same way in Arabic but may be written as "أسبرين". Hence, the user should be able to switch to Arabic transliteration to try that option in a search for medical supplies.
    3531=== List of Other transliteration services ===
    3632There are a few alternative transliteration services. They have no adoptable GUI, a few have APIs, which, again, require a permanent Internet connection.