Technically Speaking – Luminoso: Computers Listening, Interpreting Human Language

Luminoso’s CEO and co-founder, Catherine Havasi, was recently featured on an episode of “Technically Speaking,” hosted by Tim Muma.

In this episode, Catherine describes how we work to give computers the ability to not only understand words, but break down concepts and emotions coming from human language. She explains to Tim Muma the value of our technology and the way that our design can benefits our many customers.

Listen to the podcast HERE!!

Luminoso Listens – Webinar on July 23 @ 2:00 p.m. ET

What is the value of a good listener?

Personally, it’s the promise of a valuable relationship. If you are a business with customers, it’s also the promise of a valuable relationship, which in turn generates the promise of a successful business. If you listen to your customers, you’ll know who they are, what they want, and how they want it. You’ll listen when they’re unhappy or displeased so you can make them happy . Just like in any successful relationship, if you take care of your customers, they will take care of you.

What are some other qualities of good listeners?

Good listeners are empathetic – they seek to understand what you have to say and can relate. A good listener needs to have the ability to get into their heads and understand their needs, and see from the eyes of the customer.

Good listeners have emotional intelligence – they can focus on the people who are sharing their voice and perspective. It’s clear that if a customer is willing to share their voice, they want to be heard.

Good listeners are unbiased and unprejudiced – they are only going to act on the information provided. A good listener wouldn’t include their preconceived notions or prescribe subjective solutions based on what they thought their customer was going to say, or even worse, what they wanted the customer to say.

Good listeners get to the heart of the why and the what – they are going to go deeper than shallow sentiment and get to the heart of the matter. Without having the ability to dig deeper, you’ll never truly understand the drivers behind your customers.

How do you listen to your customers?

Luminoso is truly the best listener. Our solutions can take all that your customers – and your employees – are saying into consideration and help your company to determine how to make those relationships better. Luminoso listens to things that your customers and employees are saying that you might not have heard otherwise. We can also recognize how certain issues relate to others and connect the dots.

If you’re interested in learning more, please join us on July 23 at 2:00 p.m. for a 15 minute webinar. Follow the link here to register.

Brand Wars: Netflix vs. Hulu vs. Amazon Prime

We are proud to have launched our second installment of Brand Wars in collaboration with our partners over at iModerate! While the first edition focused on two athletic consumer brands, Nike and Under Armour, this one focuses on brands that provide streaming services: Netflix, Hulu, and Amazon. Of the three, which do you think will be the winner?

Check out the report here! You can also see some press that we’ve received about this report in AdWeek, and in USA Today!

MIT Industrial Liaison Program (ILP) Interview featuring CEO Catherine Havasi

Have you ever wondered about the foundations of Luminoso, and from where we came? Check out this short five-part interview featuring Luminoso’s CEO & co-founder, Catherine Havasi. These videos, produced by MIT’s Industrial Liaison Program (ILP), highlight the reasons why Luminoso’s solutions are remarkably different from other solutions out there. The first secret? Common sense!

Please follow the link here to learn more about this, how we work, and about our future in Catherine’s exclusive interview!

ftfy (fixes text for you) 4.0: changing less and fixing more

ftfy is a Python tool that takes in bad Unicode and outputs good Unicode. I developed it because we really needed it at Luminoso — the text we work with can be damaged in several ways by the time it gets to us. It’s become our most popular open-source project by far, as many other people have the same itch that we’re scratching.

The coolest thing that ftfy does is to fix mojibake — those mix-ups in encodings that cause the word más to turn into más or even más. (I’ll recap why this happens and how it can be reversed below.) Mojibake is often intertwined with other problems, such as un-decoded HTML entities (más), and ftfy fixes those as well. But as we worked with the ftfy 3 series, it gradually became clear that the default settings were making some changes that were unnecessary, and from time to time they would actually get in the way of the goal of cleaning up text.

ftfy 4 includes interesting new fixes to creative new ways that various software breaks Unicode. But it also aims to change less text that doesn’t need to be changed. This is the big change that made us increase the major version number from 3 to 4, and it’s fundamentally about Unicode normalization. I’ll discuss this change below under the heading “Normalization”.

Mojibake and why it happens

Mojibake is what happens when text is written in one encoding and read as if it were a different one. It comes from the Japanese word “•¶Žš‰»‚¯” — no, sorry, “文字化け” — meaning “character corruption”. Mojibake turns everything but basic ASCII characters into nonsense.

Suppose you have a word such as “más”. In UTF-8 — the encoding used by the majority of the Internet — the plain ASCII letters “m” and “s” are represented by the familiar single byte that has represented them in ASCII for 50 years. The letter “á”, which is not ASCII, is represented by two bytes.

Text:  m  á     s
Bytes: 6d c3 a1 73

The problem occurs when these bytes get sent to a program that doesn’t quite understand UTF-8. This program probably thinks that every character is one byte, so it decodes each byte as a character, in a way that depends on the operating system it’s running on and the country it was set up for. (This, of course, makes no sense in an era where computers from all over the world can talk to each other.)

If we decode this text using Windows’ most popular single-byte encoding, which is known as “Windows-1252″ and often confused with “ISO-8859-1″, we’ll get this:

Bytes: 6d c3 a1 73
Text:  m  Ã  ¡  s

The real problem happens when this text needs to be sent back over the Internet. It may very well send the newly-weirdified text in a way that knows it needs to encode UTF-8:

Intended text: m  á           s
Actual text:   m  Ã     ¡     s
Bytes:         6d c3 83 c2 a1 73

So, the word “más” was supposed to be four bytes of UTF-8, but what we have now is six bytes of what I propose to call “Double UTF-8″, or “WTF-8″ for short.

WTF-8 is a very common form of mojibake, and the fortunate thing is that it’s reasonably easy to detect. Most possible sequences of bytes are not UTF-8, and most mojibake forms sequences of characters that are extremely unlikely to be the intended text. So ftfy can look for sequences that would decode as UTF-8 if they were encoded as another popular encoding, and then sanity-check by making sure that the new text looks more likely than the old text. By reversing the process that creates mojibake, it turns mojibake into the correct text with a rate of false positives so low that it’s difficult to measure.

Weird new mojibake

We test ftfy on live data from Twitter, which due to its diversity of languages and clients is a veritable petri dish of Unicode bugs. One thing I’ve found in this testing is that mojibake is becoming a bit less common. People expect their Twitter clients to be able to deal with Unicode, and the bugs are gradually getting fixed. The “you fail at Unicode” character � was 33% less common on Twitter in 2014 than it was in 2013.

Some software is still very bad at Unicode — particularly Microsoft products. These days, Microsoft is in many ways making its software play nicer in a pluralistic world, but they bury their head in the sand when it comes to the dominance of UTF-8. Sadly, Microsoft’s APIs were not designed for UTF-8 and they’re not interested in changing them. They adopted Unicode during its awkward coming-of-age in the mid ’90s, when UTF-16 seemed like the only way to do it. Encoding text in UTF-16 is like dancing the Macarena — you probably could do it under duress, but you haven’t willingly done it since 1997.

Because they don’t match the way the outside world uses Unicode, Microsoft products tend to make it very hard or impossible to export and import Unicode correctly, and easy to do it incorrectly. This remains a major reason that we need ftfy.

Although text is getting a bit cleaner, people are getting bolder about their use of Unicode and the bugs that remain are getting weirder. ftfy has always been able to handle some cases of files that use different encodings on different lines, but what we’re seeing now is text that switches between UTF-8 and WTF-8 in the same sentence. There’s something out there that uses UTF-8 for its opening quotation marks and Windows-1252 for its closing quotation marks, before encoding it all in UTF-8 again, “like this”. You can’t simply encode and decode that string to get the intended text “like this”.

ftfy 4.0 includes a heuristic that fixes some common cases of mixed encodings in close proximity. It’s a bit conservative — it leaves some text unfixed, because if it changed all text that might possibly be in a mixed encoding, it would lead to too many false positives.

Another variation of this is that ftfy looks for mojibake that some other well-meaning software has tried to fix, such as by replacing byte A0 with a space, because in Windows-1252 A0 is a non-breaking space. Previously, ftfy would have to leave the mojibake unfixed if one of its characters was changed. But if the sequence is clear enough, ftfy will put back the A0 byte so that it can fix the original mojibake.

Does this seem gratuitous? These are things that show up both in ftfy’s testing stream and in real data that we’ve had to handle. We want to minimize the cases where we have to tell a customer “sorry, your text is busted” and maximize the cases where we just deal with it.

Normalization

NFC (the Normalization Form that uses Composition) is a process that should be applied to basically all Unicode input. Unicode is flexible enough that it has multiple ways to write exactly the same text, and NFC merges them into the same sensible way. Here are two ways to write más, as illustrated by the ftfy.explain_unicode function.

This is the NFC normalized way:

U+006D  m       [Ll] LATIN SMALL LETTER M
U+00E1  á       [Ll] LATIN SMALL LETTER A WITH ACUTE
U+0073  s       [Ll] LATIN SMALL LETTER S

And this is a different way that’s not NFC-normalized (it’s NFD-normalized instead):

U+006D  m       [Ll] LATIN SMALL LETTER M
U+0061  a       [Ll] LATIN SMALL LETTER A
U+0301  ́        [Mn] COMBINING ACUTE ACCENT
U+0073  s       [Ll] LATIN SMALL LETTER S

If you want the same text to be represented by the same data, running everything through NFC normalization is a good idea. ftfy does that (unless you ask it not to).

Previous versions of ftfy were, by default, not just using NFC normalization, but the more aggressive NFKC normalization (whose acronym is quite unsatisfying because the K stands for “Compatibility”). For a while, it seemed like normalizing even more was even better. NFKC does things like convert fullwidth  letters into normal letters, and convert the single ellipsis character into three periods.

But NFKC also loses meaningful information. If you were to ask me what the leading cause of mojibake is, I might answer “Excel™”. After NFKC normalization, I’d instead be blaming something called “ExcelTM”. In cases like this, NFKC is hitting the text with too blunt a hammer. Even when it seems appropriate to normalize aggressively because we’re going to be performing machine learning on text, the resulting words such as “exceltm” are not helpful.

So in ftfy 4.0, we switched the default normalization to NFC. We didn’t want to lose the nice parts of NFKC, such as normalizing fullwidth letters and breaking up the kind of ligatures that can make the word “fluffiest” appear to be five characters long. So we added those back in as separate fixes. By not applying NFKC bluntly to all the text, we change less text that doesn’t need to be changed, even as we apply more kinds of fixes. It’s a significant change in the default behavior of ftfy, but we hope you agree that this is a good thing. A side benefit is that ftfy 4.0 is faster overall than 3.x, because NFC normalization can run very quickly in common cases.

Future-proofing emoji and other changes

ftfy’s heuristics depend on knowing what kind of characters it’s looking at, so it includes a table where it can quickly look up Unicode character classes. This table normally doesn’t change very much, but we update it as Python’s unicodedata gets updated with new characters, making the same table available even in previous versions of Python.

One part of the table is changing really fast, though, in a way that Python may never catch up with. Apple is rapidly adding new emoji and modifiers to the Unicode block that’s set aside for them, such as 🖖🏽, which should be a brown-skinned Vulcan salute. Unicode will publish them in a standard eventually, but people are using them now.

Instead of waiting for Unicode and then Python to catch up, ftfy just assumes that any character in this block is an emoji, even if it doesn’t appear to be assigned yet. When emoji burritos arrive, ftfy will be ready for them.

Developers who like to use the UNIX command line will be happy to know that ftfy can be used as a pipe now, as in:

curl http://example.com/api/data.txt | ftfy | sort | uniq -c

The details of all the changes can be found, of course, in the CHANGELOG.

Has ftfy solved a problem for you? Have you stumped it with a particularly bizarre case of mojibake? Let us know in the comments or on Twitter.

The State of Text Analytics 2015 & 14th Text Analytics Summit East

Have you seen this new whitepaper? This whitepaper was developed by Data Driven Business with contributions from the speakers associated with the 14th Text Analytics Summit East – taking place on June 15th & 16th in New York City.

In fact, we will be attending the event, and delivering a presentation with our esteemed client, Intel, on June 16 at 9:00 a.m. ET. Josh Ritchie, Regional Sales Director at Luminoso, and Roop Gill, Manager, Insights & Analytics at Intel, will present on the advantages of automated insights and machine learning based on work performed using Luminoso.

But, back to the report – it really hits the nail on the head when it comes to the text analytics world that we know so well, so much that it almost feels like it was written FOR us and our customers!

If you haven’t see the report, we highly recommend that you download it from this link hereWe’ve highlighted a few passages below that really speak to us.

This passage could be referring to the work that we do at-large.

img1

They could be directly speaking to our real-time enterprise listening solution, Compass.

img2

If you’re interested in attending the Text Analytics Summit, please let us know! We can provide you with a discount code that will give you $300 off of the regular purchase (not to mention, we’d just love to see you there anyway). Please reach out to me at ian@luminoso.com, if interested.

As always, if you have any questions that we can answer for you about our work, and how we can help you and your business with our best-in-class enterprise feedback and analytics solutions, please contact me at the e-mail above or generally at info@luminoso.com.

Luminoso Software Update 5/15/15

Our development team has been working hard to make some really valuable improvements to our solutions. Check out what they’ve been working on here, including:

  • We now support Dutch! (Analytics Platform)
  • Saved Topics are now presented as a scrolling list (Analytics Platform)
  • Fix for issue, browsers crashing in projects with large numbers of subsets and topic (Analytics Platform)
  • Now you can specify negative seeds to exclude keywords used in listening for Twitter content (Compass)
  • Fix of issue where initial topic velocity was sometime incorrectly calculated (Compass)
  • Fix for issue where topic velocity and acceleration did not take into account the sampling rate for Twitter messages (Compass)

If you ever have any questions at all, please don’t hesitate to reach out to us at support@luminoso.com.