Wolfram|Alpha integration feedback

xkc7

I have to say that I think currency conversion has gotten worse since the integration. If I now type "100 eur cop", I don't get any immediate result anymore. Of course, this can be bypassed by typing "100 eur to cop", but I'm already used to doing it like that as it is accepted on other search engines like Google and DDG.

fristitijd

When searching for [chemical name] + CAS, kagi gives the CAS number (a molecule identifier) automatically via Wolfram Alpha, which is great. However, the formatting is slightly wrong. For instance, the glucose CAS number is 50-99-7, but kagi shows it as "= 50 99 7":

This makes it slightly annoying to copy-paste the number (which is something I do a lot in my job unfortunately).

I expect a correctly formated CAS number, e.g. 50-99-7 for glucose.

vengefulkiwi

seems like the calculator is just completely broken now. Not even "1+1" returns an answer anymore.

Vlad

vengefulkiwi Not able to reproduce

youngji22

https://kagi.com/search?q=9900+won+to+usd&r=us&sh=gQykwLoaK9ryuO2NqbroMQ

It should understand that "won" here refers to the currency. Currently, it's only current if you put
"korean won"

gladiator2339

It shouldn't.

1) Won is not exclusive to South Korea. There's North Korean Won(KPW) as well. 2) Although 99.9% of the time when we say Won we're talking about South Korean Won, KRW is the ISO 4217 standard for it.

KRW to USD works just fine.

youngji22

ISOs are standards for developers, not users. I don't think it's relevant, because either way I am asking for a currency conversion and the South Korean won should be the implied default. Asking the same question on Wolfram directly provides the expected result, so this is an issue with Kagi's integration.

sefidel

Something that would also be solved by using the calc widget for currency conversion (please!)

jstolarek

At the moment Kagi uses dot as the decimal separator, but in certain regions it is customary to use comma instead. For example, what Americans write as 21.37 people in Poland write as 21,37. But Kagi does not recognize this, resulting in bogus results. For example here are results of searching for "21,37 PLN in USD".

Kagi:

DuckDuckGo:

Google:

Note that both DDG and Google do the right thing, despite being set to English and not Polish.

I imagine several solutions to the problem:

Be smart. If a user uses only dot or only comma in the numbers, assume this as the decimal separator. If the user mixes up dots and commas feel free to return nonsense. This is what other search engines implement at the moment.
Pre-define decimal separator based on Kagi's language settings. Don't rely on browser settings - as you can see by my DDG and Google examples above my browser reports English locale.
Allow user to select what decimal separator they want to use.

I lean towards 1 since it's a simple heuristic that works well in practice.

zut

with locales that use decimal, this is also a problem with the _-underscore feature.

eikowagenknecht

This would be great, had the same problem today:

This happens even though my browser reports as primarily "German":

stom

Hey @Vlad and team.
This one has been marked as "Done" for a while, but I continue to have that incorrect outcomes.
Kagi doesn't recognize comma as fraction separator, which means queries like currency converter don't work.

My situation is exactly as in original posters reports. Any query like "35,04 PLN in USD" fails, but "35.04 PLN in USD" fails.
Of course "fail" in this scenario is that kagi doesn't detect this as an attempt to convert currencies - standard search results for a text are presented.

Tried multiple browsers (Fx, Chrome, Edge) multiple times in last few months, all with proper local settings.

sefidel

Not sure why that was merged, looks like the comments are referring to the calculator widget, not WA.

p.s. How did you manage to trigger the calc widget instead of WA when asking for currency conversion?
Would definitely love that.

frin

I am trying to convert gold/troy ounces (XAU) to grams. I write the query:

1 XAU in grams

The widget shows an error:

= 1 gold ounce and gram are not compatible

It works if I enter "troy ounce" instead of XAU or gold ounce.

It should return how much 1 XAU/gold ounce is in grams (31,1034768 g).

Even trying "to" instead of "in", or calc, calculate does not work at all.

Sure XAU is monetary unit, but it has a fixed weight.

tschoesi

XAU is a currency code, which happens to correspond to the price of one troy ounce of gold. XAU is not a weight.
A US quarter probably also has a fixed weight, but you wouldn't think of converting it to grams.

frin

tschoesi it is very common though, for example my banking app shows price for 1 XAU, and I'd like to compare it to physical weight which is in grams. Right now I have to manually convert that. My country lists and trades gold in grams.

Comparing a US quarter to grams would not make sense as it has a fixed value to a unit.

« Previous Page Next Page »