Add a dedicated translation page to Kagi.com and use LLMs to translate

carl

Vlad
Another thing about SELCET vs DATALIST is that you cannot search a SELECT dropdown on mobile by typing, at least not on iOS.

Nashwan In the experimental translate interface, you might consider adding a way to select part (or all) of a translation and trigger a search query with it?

At least on MacOS and iOS, this is built into the system when you right click any selected text or word anywhere, also in Kagi Translate.

Nashwan

carl
Well look at that, it works in Firefox on Windows too, I had no idea! Thanks 😊

dai

Hey folks.

Not many people are aware of the fact that since Firefox changed its normal translations to its own Firefox Translator (bergamot 1), the number of languages it covers has narrowed considerably.

It now only supports European languages and English, and other languages from South America, Asia, and the Middle East are no longer supported 2.

This means that Firefox can no longer translate Japanese pages into English without using an external translation extension 3.

Firefox is working on a local LLM-based translation for this 4, 5.
The same applies to Chrome 6.

It can be said that browsers are moving toward a policy of local translation solutions without online support in the future.

Sorry for the long post.
Best Regards.

Dustin

@dai I would argue that web translation serves a different purpose than a browser-based page translator.

carl

Hi! Could you change the RETURN key in the input textfield to make a new line instead of translating the text? I know I can use Shift+Return, but new line is standard behaviour for text fields, and more practical when the user is writing something to be translated and not pasting.

« Previous Page