Wednesday, 21 December 2016

Message Character Encoding

If you've been seeing some illegible characters in your messages then rest assured we're working on resolving these. It's been an annoying issue that pops up every now and then as we try to manage encoding across all the message mediums.

The issue is that Tokeet was built to be multi-language. As such it must be able to handle all UTF-8 characters across the various languages. This seems simple, however as your message moves from the DB to the API and then out to the various channels (Email, SMS, Airbnb, Booking.com, etc) we must change encodings, strip some encodings, translate from UTF-8 to HTML encodings, from language specific unicode to other forms, and so forth. This has resulted in a whack-a-mole type issue where we are constantly finding new, unhandled scenarios.

Please hang in there with us as we try to get this correct.

0 comments:

Post a Comment

Note: only a member of this blog may post a comment.

Welcome to the Tokeet changelog. This blog will be used to communicate any and all changes, bug fixes, and new feature releases made to Tokeet's web and mobile applications.