Live data from Hacker News

Kagi Translate

blog.kagi.com

21–30 of 119 posts

Re: Kagi Translate

#21
post #10
post #6

> Limitations > We do not translate dynamically created content ... What does that mean?

I assume it means they only translate what's in the HTML, not anything that's added via Javascript later.

Indeed, that's what would make most sense to me.

I also strongly suspect the way they're able to make it free is by caching the results, so each translation only happens one time regardless of how many requests for the page happen. If they translated dynamic content, they couldn't (safely) cache the results.

Re: Kagi Translate

#22
I can't use it because I'm not classified as "human" by a computer. There is no captcha that I could get wrong, just a checkbox that probably uses a black box model to classify me automatically

Was curious after the post claimed that the quality is better than Google and DeepL, but the current top comment showed translations from Afrikaans that it got wrong but I could understand as a Dutch person who doesn't even speak that language (so it's not like seven levels of negation and colloquialisms that they broke it on)

What do I do with this "Error Code: 600010"? I've submitted a "report" but obviously they're not going to know if those reports are from a bot author frustrated with the form or me, a paying customer of Kagi's search engine. The feedback page linked in the blog post has the same issue: requires you to log in before being able to leave feedback, but "We couldn't verify if you're a robot or not." The web is becoming more fragmented and unusable every day...

Re: Kagi Translate

#23
On the sidenote, does anyone know what methods Yandex use? When I'm trying to translate Kyrgyz, Google Translate shows utter trash that makes less sense than if they chose words at random. Yandex in comparison is very impressive. What's the secret ingredient?

Re: Kagi Translate

#24

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. I…

Google Translate often translates words through English.

Re: Kagi Translate

#25
post #10
post #6

> Limitations > We do not translate dynamically created content ... What does that mean?

I assume it means they only translate what's in the HTML, not anything that's added via Javascript later.

Ah, that makes sense. In my head it sounded like server-side dynamic content OR not wanting to translate LLM outputs, neither of which makes sense or is possible.

Re: Kagi Translate

#27
post #2

> Quality ratings based on internal testing and user feedback I'd be interested in knowing more about the methodology here. People who use Kagi tend to love Kagi, so bias would certainly get in the way if not controlled for. How rigorous was the quality-rating process? How big of a difference is there between "Average", "High" and "Very High"? I'm also curious to the 1 additional language that Kagi supports (Google i…

[deleted]

Re: Kagi Translate

#28
post #10
post #6

> Limitations > We do not translate dynamically created content ... What does that mean?

I assume it means they only translate what's in the HTML, not anything that's added via Javascript later.

that's what I think too, which kinda makes sense since it's a page, and not a browser plugin. If they implemented a browser plugin that would do what Google recently removed from their plugin, that would be a killer feature. (assuming they can then translate all html as it comes in)

Brave browser does it already though, but sometimes it's unusably slow.

Re: Kagi Translate

#29

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…

Just tried translating your comment to German. Kagi took a very literal approach, keeping sentence structure and word choice mostly the same. Google Translate and DeepL both went for more idiomatic translations.

However translating some other comments from this thread, there are cases where Kagi outperforms others on correctness. For example one comment below talks about "encountering multiple second page loads". Google Translate misunderstands this as "encountering a second page load multiple times" while DeepL and Kagi both get it right with "encountering page loads of multiple seconds" (with DeepL choosing a slightly more idiomatic wording)

Re: Kagi Translate

#30

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. I…

Google Translate often translates words through English.

DeepL also, for the record (since it's being compared in the submission)

It's pretty clear if you use the words out of context and they're true friends but it gets you the German translation of the English translation of whatever Dutch thing you put in. I also heard somewhere, perhaps when interviewing with DeepL, that they were working towards / close to not needing to do that anymore, but so far no dice that I've noticed and it has been a few years

Post reply on HN