Posted on

A More Responsive Google Translate

Google Translate is the world’s most popular translation tool. The company says it now translates 30 trillion sentences a year across 103 languages.

The key data point here is the 103 languages. No other free translation tool comes close to this range of languages. And while the quality across the lesser-used languages is quite uneven, to put it kindly, Google Translate is still the only game in town. Which means some translation is far better, even poor quality, than none at all.

Last week, Google Translate debuted an upgraded design that is now fully responsive. Here is the new interface:

Google Translate: November 2018

And the previous interface:

Google Translate: July 2018

The functionality remains the same, but I appreciate the more prominent “detect language” selector on the text input side. Google pioneered browser-based language detection a decade ago and it is wise to call attention to this powerful feature. Many users assume that they must need to know the source language before taking advantage of Google Translate.

Also nice to see is increased default sizes of the target languages on this menu:

Target language menu

One recommendation I would make — adding a generic globe icon above this menu of languages. Perhaps the downward arrow is sufficient, but I would rather use an icon that speaks across all languages.

Now, for those of you wondering about this list of languages — as in Why are they all in English? — you ask a great question. As I note in my book and reports, you want your global gateway to be globally agnostic, so each language should be presented in its native language. But that’s the rule for a global gateway. What we have here is not a global gateway, but a localized user interface — localized into English.

If I change my web browser setting to Spanish, I will be greeted with this interface:

Spanish-language interface: Target language menu

Google Translate morphs into Google Traductor

Posted on

Peak flag: The decline of flags on websites has begun

I’m pleased to say that, based on the websites I study regularly, we’ve reached “peak flag.” In other words, at a high level, companies are now beginning to move away from using flags on their websites within their global gateways.

This is a good thing.

On a personal level, I love flags. But from a usability perspective, flags often cause more problems than they solve.

Companies that have stopped using flags on their websites over the years include:

  • Delta Airlines
  • General Electric
  • Google
  • Marriott
  • Siemens

To name just a few.

Apple global gateway

And, yes, I’m well aware that Apple still uses flags. I do believe that Apple will drop flags as the risks far outweigh the rewards.

To learn 10 reasons why you should remove flags from your website, check out my report FLAG FREE, which is also included with the Web Globalization Report Card.

Posted on

It’s time for your website to go flag free

If you are flying the Taiwan flag on your website, consider yourself warned.

By China.

As I’ve written many times over the past year, China is paying close attention to how multinationals refer to Taiwan on their websites, not just textually but visually. And this includes the global gateway.

But the fact is, flags are completely unnecessary in global gateways — not just the Taiwan flag but any flag. And now is a very good time to extricate flags from your website.

Flag free means frustration free.

I’ve published a new report that details the many reasons for removing flags from your website; it also includes examples of websites that have gone flag free, including Costco, Google, Sanofi and Siemens.

This report is included free with all purchases of the 2018 Web Globalization Report Card.

Posted on

Yet another reason to avoid using flags on your global gateway

As readers of this blog well know, I often refer to China and Taiwan when making the case for avoiding the use of flags on a global gateway. There are many others reasons, of course, but geopolitical issues have become more acute lately.

I could also point to the Russia and Kosovo as another case study for avoiding the use fo flags. As this New York Times article notes Kosovo, despite being a FIFA member, cannot fly its flag at World Cup stadiums:

The flag — which depicts a gold map of Kosovo under six white stars on a blue background — is one of more than two dozen barred from World Cup stadiums by tournament organizers.

Here’s a visual of the flags not allowed into the stadiums:

While most countries acknowledge Kosovo and its flag, Russia does not. And because this World Cup is hosted by Russia, well, so it goes.

Which brings me back to your global gateway.

Your global gateway is a tool for helping visitors find (or change) their locale setting, not a geopolitical statement.

So keep you life simple and avoid using flags.

And, yes, I know many companies are still learning this lesson the hard way, but more and more websites are removing flags entirely. You can learn more in the Web Globalization Report Card and Think Outside the Country.