![]() ![]() The Solution: Unicode with Broad Compatibility & Character Recognition And because that Gateway does not support GSM, the message will not pass through correctly despite any initial encoding compatibility. To specify, even though an SMS gateway supporting SMPP 3.4 may support many character encodings (like ISO 8859-1, ISO 8859-8, ISO 8859-5, IA5), the message will eventually need to get converted to GSM 3.38 when sending to most GSM/3G handsets. So what happens if a provider does not to support GSM, for example? If either the user sending a character – or a user receiving that character – is using a carrier that requires GSM encoding, the message will not pass through correctly (eg ☐) or will be dropped entirely. Some providers decide the juice isn’t worth the squeeze and choose not to support the troublesome character sets. The character set GSM 3.38, for example, is not natively supported by most programming runtimes, and therefore is extremely challenging to support. The trouble is some character sets are harder for these providers to encode than others. They need to verify, for example, that the provider they select can encode both the characters sent by their end users (eg emoji, kanji) AND encode the character sets required by the receiving user’s phones (eg GSM). ![]() They then need to pass this information to the SMS gateway (the mechanism to send SMS) they’re using for the message to be sent with proper encoding.Īdditionally, developers need to check that the API or SMPP gateway they use supports the encoding that they need. To avoid the above problem, the first thing a developer typically needs to do is programmatically determine which character set to use. The left example uses Twilio’s API with unicode support, and the API on the right doesn’t support it. We tested two different messaging APIs (Twilio and another) to echo back inbound messages that contained a variety of different characters. ![]() If they don’t, these messages may show the dreaded ☐, or worse – nothing at all. How many times a day do you receive one of these a smiley face or thumbs emoji? What about 漢字or العربية? When developers build an SMS app, they need to take extra steps to ensure all your thumbs up emojis, kanji, arabic, and smiley faces are sent and received properly. The Wrench: Compatibility with Emojis, Kanji, and Other Characters In this post, we’ll show you how the many different languages and characters that can be sent in an SMS can also cause complications – and that it’s not necessarily easy to send them all. Earlier this month we walked you through a common SMS delivery challenge that occurs when sending long messages, and how a developer can address it successfully. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |