Live data from Hacker News

Localization Failure: Temperature Is Hard

randomascii.wordpress.com

41–50 of 157 posts

Re: Localization Failure: Temperature Is Hard

#41
post #4

Earlier quoted context omitted.

"To be fair", there is ASCII in the name

"To be fair..." (chorus of Letterkenny voices) I appreciate the ASCII-only excuse, but I've corrected the omission anyway. Non-ASCII characters in randomascii - what will they think of next?

Pssst... You over-corrected

> 278 °K to 283 °K,

There's no ° symbol before the kelvin unit, just a regular non-breaking space if you want to be SI-compliant.

Re: Localization Failure: Temperature Is Hard

#42

A bit related, but I hate how many errors I get because I want my system language to be English instead of my native language (Norwegian) on my laptop, phone etc. Because I don't want a badly translated experience. However, I still want units in meters, Celsius, dates written sensibly, time in 24h format etc. But not all apps understand this, which is quite annoying. It's like they only look at the language and make…

It really is incredible how many translated apps/websites talk like a drunken finn, when i set language to finnish. Only the things made by native finns seem to have good Finnish on them.

[deleted]

Re: Localization Failure: Temperature Is Hard

#43

GPT-4 correctly converts the difference to 36F. GPT-3.5 on the other hand gets crazy and decides that the difference is 154.4F. Same prompt. At this point I'm starting to believe GPT3.5 is dangerously stupid.

I worded the question as: "What's the temperature difference between 43°C and 23°C in Fahrenheit?" and GPT3.5 answered correctly.

Re: Localization Failure: Temperature Is Hard

#44

Hard? So is using the degree symbol apparently: not a single one in the whole article. (68F is not a temperature — it’s a seat number.) https://degreeswhat.com/?68

No, 68 farads is a capacitance. Pretty massive one, too. It's another question how they obtain that from coulombs...

That would be 68 F [1]. I agree with parent, 68F is a seat number.

[1] https://physics.nist.gov/cuu/Units/checklist.html (number 15).

Re: Localization Failure: Temperature Is Hard

#45

It's not hard at all, the localization team just made a mistake. The solution is to not localize for Americans.

Yes just ignore the vast majority of native English speakers. I wonder why an English-language newspaper (which heavily markets itself outside the UK) didn’t think of that.

Or we can just use a calculator. I'm sure most people's phones can even translate it by a voice command "What's 20 degrees Celsius in Fahrenheit?"

Re: Localization Failure: Temperature Is Hard

#46
post #4

Earlier quoted context omitted.

"To be fair", there is ASCII in the name

"To be fair..." (chorus of Letterkenny voices) I appreciate the ASCII-only excuse, but I've corrected the omission anyway. Non-ASCII characters in randomascii - what will they think of next?

You may have overcorrected a bit; 300 Kelvin is written 300K, not 300 °K. (The system is a mess.)

Re: Localization Failure: Temperature Is Hard

#47
post #45

Earlier quoted context omitted.

Yes just ignore the vast majority of native English speakers. I wonder why an English-language newspaper (which heavily markets itself outside the UK) didn’t think of that.

Or we can just use a calculator. I'm sure most people's phones can even translate it by a voice command "What's 20 degrees Celsius in Fahrenheit?"

That will give the same wrong answer this post is discussing.

Re: Localization Failure: Temperature Is Hard

#48

A bit related, but I hate how many errors I get because I want my system language to be English instead of my native language (Norwegian) on my laptop, phone etc. Because I don't want a badly translated experience. However, I still want units in meters, Celsius, dates written sensibly, time in 24h format etc. But not all apps understand this, which is quite annoying. It's like they only look at the language and make…

I usually set my system to English / Ireland. I get English but with normal units and € as a default currency.

Re: Localization Failure: Temperature Is Hard

#49
post #27

Earlier quoted context omitted.

This used to work back in the old days, but more and more sites decides to ignore this a few years ago. The reasoning is that the percentage of users with misconfigured browsers (who don't know how to fix this and also don't know how to click a "change language" button on the website) is bigger than the percentage of users who intentionally use a language that's different from their geolocated one. So the ad-revenue…

That’s why I like travelling: I’ll get all my web content in English (the language I do know) and the ads in a language I don’t know (perfect).

It used to work on Facebook to just change your location to a weird country and you would get their advertisements. Or none if there weren't any like for North Korea. Then I got banned on Airbnb (where I used Facebook login) because they thought I'm from North Korea and they would break sanctions by renting me a bnb...

Re: Localization Failure: Temperature Is Hard

#50
post #37

A bit related, but I hate how many errors I get because I want my system language to be English instead of my native language (Norwegian) on my laptop, phone etc. Because I don't want a badly translated experience. However, I still want units in meters, Celsius, dates written sensibly, time in 24h format etc. But not all apps understand this, which is quite annoying. It's like they only look at the language and make…

I'm Italian and I have the same problem. You just have to set the system to English (UK) and all your problems will be fixed :)

Perhaps not all of your problems! I have my phone in en-gb and live in Switzerland. When I travel to the US it starts showing me temperatures in farenheit

When I travel to the US/UK I _do_ actually want to start seeing distances in miles (I'm "bilingual" with m/km, it's useful to think in distances that locals understand and that match signage). So "just use my home locale's units all the time" wouldn't work (especially for speeds!). So yeah I guess localization is indeed hard!

Honestly I've now just started trying to learn Farenheit! 90 is hot, 70 is nice, 50 is cold, 30 is ice.

Post reply on HN