Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Kagi Translate

blog.kagi.com

Post reply on HN
Print view View original

11–20 of 119 posts

Re: Kagi Translate

#11

Post by burkaman »

ohmahjong wrote: post #7

Disclaimer: I am already a Kagi customer. At least for Afrikaans I'm not impressed here. There are some inaccuracies, like "varktone" becoming "pork rinds" instead of "pig toes" and also some censorship ("jou ma se poes" does NOT mean "play with my cat"!). Comparing directly against Google Translate, Google nails everything I threw at it. I didn't see any option to provide feedback, suggested translations, etc, but I…

This is the link they gave for feedback: https://kagifeedback.org/d/5305-kagi-translate-feedback/4

Re: Kagi Translate

#12

Post by dlkmp »

Just as a quick usability feedback: As long as Deepl translates asynchronously as I type, while Kagi requires a full form send & page refresh, I am not inclined to switch (translation quality is also already too good for my language pairs to consider switching for minor improvements, but the usability/ speed is the real feature here).

This is coming from a user with existing Kagi Ultimate subscription, so I'm generally very open to adopt another tool if it fits my needs).

Slightly offtopic, slight related: As already mentioned the last time Kagi hit the HN front page when I saw it: the best improvement I could envision for kagi is improved search performance (page speed). I still encounter multiple second page loads far too frequently that I didn't notice with other search engines.

Re: Kagi Translate

#13

Post by burkaman »

krackers wrote: post #3

How is this compared to using gpt-4 directly?

I don't know how the translation quality compares, but the advantages to this would be that it's free and it can translate web pages in-place.

Re: Kagi Translate

#14

Post by pentacent_hq »

I recently noticed that Google Translate and Bing have trouble translating the German word "Orgel" ("organ", as in "church organ", not as in "internal organs") to various languages such as Vietnamese or Hebrew. In several attempts, they would translate the word to an equivalent of "internal organs" even though the German word is, unlike the English "organ", unambiguous.

Kagi Translate seems to do a better job here. It correctly translates "Orgel" to "đàn organ" (Vietnamese) and "עוגב" (Hebrew).

Re: Kagi Translate

#15

Post by o11c »

If you write the input in Pig Latin, Kagi detects it as English but translates it correctly.

Bing detects it as English but leave it unchanged.

Google detects it as Telegu and gives a garbage translation.

ChatGPT detects it as Pig Latin and translates it correctly.

Re: Kagi Translate

#16

Post by Aachen »

dlkmp wrote: post #12

Just as a quick usability feedback: As long as Deepl translates asynchronously as I type, while Kagi requires a full form send & page refresh, I am not inclined to switch (translation quality is also already too good for my language pairs to consider switching for minor improvements, but the usability/ speed is the real feature here). This is coming from a user with existing Kagi Ultimate subscription, so I'm general…

Interesting, I'm actually annoyed that DeepL sends every keystroke and I'm using idk how many resources on their end when I'm just interested in the result at the end and for DeepL to receive the final version I want to share with them

That it's fast, you don't have to wait much between finishing typing and the result being ready, that's great and probably better than any form system is likely to be. But if it could be a simple enter press and then async loading the result, that sounds great to me

Re: Kagi Translate

#17

Post by jabroni_salad »

Looks like the page translator wants to use an iframe, so of course the x-frame-options header of that page will be the limiting factor.

> To protect your security, note.com will not allow Firefox to display the page if another site has embedded it. To see this page, you need to open it in a new window.

This is a super common setting and it's why I use a browser extension instead.

Re: Kagi Translate

#18

Post by elashri »

krackers wrote: post #3

How is this compared to using gpt-4 directly?

It varies depending on the language but I find GPT4o to be good into knowing the context and go sometimes with the intent not just the grammar and rules of the language. But for most cases it is an overkill and you still have the chance of hallucination (although it has less occurrence chances in these use cases)

This is of course based on my experience using it between Arabic, English and French which is among the 5 most popular languages. Things might be dramatically different with other languages.

Re: Kagi Translate

#20

Post by czottmann »

dlkmp wrote: post #12

Just as a quick usability feedback: As long as Deepl translates asynchronously as I type, while Kagi requires a full form send & page refresh, I am not inclined to switch (translation quality is also already too good for my language pairs to consider switching for minor improvements, but the usability/ speed is the real feature here). This is coming from a user with existing Kagi Ultimate subscription, so I'm general…

I uninstalled the DeepL extension because it would load all its assets (fonts etc) into every. single. page. No matter the host.

Unacceptable.

Post reply on HN