SMS transliteration

Send full-size messages in original language alphabet using transliteration conversion.

Sending messages with special characters can be quite expensive in terms of maximum characters per message. This should be taken seriously because if even one illegal character is included, message capacity drops from 160 to only 70 characters! This can cause a message to split into multiple parts, increasing the price significantly.

Character encoding

Reasons behind the maximum characters decrease from 160 to 70 are described in the SMS language tutorial.

If you need to handle special characters in your SMS messages, there are two main approaches that can be taken in order to increase character capacity closer to the standard SMS size:

1. National Language Identifier (NLI)

2. Transliteration

National Language Identifier (NLI)

NLI is the technique of handling language-specific characters by instructing mobile devices to use the proper alphabet in order to display a message properly. NLI is covered in more details in this tutorial.

Transliteration

Transliteration is a method of replacing special (unsupported) characters with similar or related characters that are part of the default alphabet. This process ensures that a maximum number of 160 characters per message can still be used in a message, instead of only 70 (because of the different encoding standard). The downside of this approach is that the delivered message will look slightly different.

With this method you can send messages in your preferred alphabet and they will automatically convert into the appropriately transliterated script. This way you can use the full capacity of the message text without sending any Unicode characters.

Supported alphabets:

  • "TURKISH"
  • "GREEK"
  • "CYRILLIC"
  • "SERBIAN_CYRILLIC"
  • "PORTUGUESE"
  • "COLOMBIAN"
  • "BALTIC"
  • "NON_UNICODE"

By specifying the desired output alphabet, some unsupported characters will be converted differently, depending which character is the most appropriate for the selected language.

Warning

Using any of the alphabets available, transliteration will be done on matching characters recognized by the selected language, leaving other characters untouched.

Any character that is not recognized by the selected language and not part of the default alphabet, will be replaced by (.).

Note

Using "NON_UNICODE" transliteration message text will be converted from Unicode to GSM charset using all of the available alphabets conversions, leaving unmatched characters replaced with dots (ie. "©™ø- ˆ¨л- ˙˚λ- ∆ƒ∂" will become "..ø- ..l- ..A- ...").

The example bellow shows how to send a transliterated message. Just put one of the supported alphabets in the transliteration parameter.

POST /sms/1/text/advanced HTTP/1.1
Host: api.infobip.com
Authorization: Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ==
Content-Type: application/json

{
    "messages":[
        {
            "from":"InfoSMS",
            "destinations":[
                {
                    "to":"41793026727"
                }
            ],
            "text":"Ως Μεγαρικό ψήφισμα είναι γνωστή η απόφαση της Εκκλησίας του δήμου των Αθηναίων (πιθανόν γύρω στο 433/2 π.Χ.) να επιβάλει αυστηρό και καθολικό εμπάργκο στα",
            "transliteration":"GREEK"
        }
    ]
}	
  

Text sent:

Ως Μεγαρικό ψήφισμα είναι γνωστή η απόφαση της Εκκλησίας του δήμου των Αθηναίων (πιθανόν γύρω στο 433/2 π.Χ.) να επιβάλει αυστηρό και καθολικό εμπάργκο στα

Text received by the recipient of the message:

ΩΣ MEΓAPIKO ΨHΦIΣMA EINAI ΓNΩΣTH H AΠOΦAΣH THΣ EKKΛHΣIAΣ TOY ΔHMOY TΩN AΘHNAIΩN (ΠIΘANON ΓYPΩ ΣTO 433/2 Π.X.) NA EΠIBAΛEI AYΣTHPO KAI KAΘOΛIKO EMΠAPΓKO ΣTA

By using transliteration, Greek lower case letters which are not supported in the default alphabet were converted to upper case letters which are supported, as you can see in the table below.

Preview messages before sending!

Transliteration may cause unexpected output message text. We recommend using the SMS preview method to explore all options before sending.