News for hackers. Stuff that matters.
Re:Why Bother with What Three Words? by chrisrhoden on Thursday March 28, 2019 @04:38PM (#19516347)
It is localized to other languages, as explained in the article.

One of the complaints in the article is that the different localizations offer uneven quality.

Re:Why Bother with What Three Words? by duskwuff on Thursday March 28, 2019 @09:35PM (#19518406)
> One of the complaints in the article is that the different localizations offer uneven quality.

And there's no publicly documented way to convert between the localizations. It's not even clear that there's a 1:1 correspondence between the word lists!

Re:Why Bother with What Three Words? by rtkwe on Thursday March 28, 2019 @10:29PM (#19518627)
It's clear in the article that the lists don't map so you can't even translate between them without going back to W3W and running it through their stuff.

> So, if I want to tell a French speaker where ///mile.crazy.shade is, I have to use ///embouchure.adjuger.saladier

> Loosely translated back as ///mouth.award.bowl an entirely different location!

Re:Why Bother with What Three Words? by duskwuff on Friday March 29, 2019 @12:28AM (#19519155)
It's no great surprise that the words don't translate. But what I'm asking is it's possible to infer a word-to-word mapping along the lines of

    English   French
    -------   ------
       mile = embouchure
      crazy = adjuger
      shade = saladier
or if the mapping is weird enough that even that doesn't work.
Re:Why Bother with What Three Words? by fredzel on Friday March 29, 2019 @04:28AM (#19519989)
Just checked that by changing last phrase in Polish, than changing language to English. It doesn't work:

"plomba.rewelacja.oczy" => "exclaim.mainland.engages"

"plomba.rewelacja.fasada" => "dare.lawn.sleepy"