Kagi says PHP 8.3 is worth 13.72 euro cents

amk

Do not treat any PHP version as a currency.

Also, €0.1372 would probably be less ambiguous.

GrygrFlzr

This is because PHP is also the currency shorthand for Philippine Pesos. It would require positional checks to make sure that 8.3 PHP is treated as a currency, but PHP 8.3 is not.

amk

I'm aware of that, though:

1) I didn't ask how much it was worth in EUR.
2) Given the region, defaulting to EUR is incorrect anyway.

Vlad

amk On the other hand people expect to do exactly this when one currecy is recognized https://kagifeedback.org/d/3271-short-currency-conversion-queries-100-usd-should-default-to-regions-currency

How to approach this?

lorenz

Vlad

I think this should be revised. When I search for "Euro 2024" (which considering the current media presence is pretty obvious what I search for: the football tournament), Kagi tells me first how many USD this equivalents to.

I would propose that Kagi only shows the currency conversion when a user searches for:

X EUR [to/in] USD
EUR X [to/in] USD

Or at the bare minimum, have exceptions for special cases such as PHP (as mentioned above) or the football tournaments (there is one every 4 years).

amk

I'm not sure how Google does it, to be honest.

It does not treat the following as a currency:

8 php
php 8
php 84
84 php
php 156

On the other hand, "156 php" is treated as a currency. No idea how it behaves for a different region or user with a different search/browsing history.

frin

Number after the currency code does not make sense, so it should ignore "EUR 5.6", "PHP 8.3", etc. Usually you would write 5.6 EUR, or at the very least with the currency symbol, 5.6 €, €5.6

amk

I'm not really that bothered by the fact the conversion happens, what I'm looking for is right under it anyway. But there's still something odd about this.

At some point it changed the conversion from EUR (which wasn't the correct default currency to begin with) to USD. My IP is the same, the selected region is the same and it does this regardless of the Accept-Language header value:

en,en-US;q=0.9,cs;q=0.8,sk;q=0.7 (this is default for MS Edge for CS locale)
en-US,en;q=0.5

Also, the converted value, while technically correct, seems rather unconventional and confusing to me. If you're used to how other search engines and probably all converters for that matter do it, you can easily miss the fact it decided to convert the price to cents rather than dollars, giving you potentially a very bad idea about the actual exchange rate.