Kagi Translate Feedback

carl

whatthefilament I agree, but I don't think underlining is necessary, because almost all words can have multiple meaning. The DeepL translating app lets you click any translated word to give you the alternatives, just like you described, and it's a great feature.

lobochrome

https://www.mansion-review.jp/mansion/224200.html

When attempting to use the bookmarklet.

utf9k

Vlad

Hey Vlad,

Sorry for the delay in replying. I had a look and it seems worse now 😅

The page appears to get duplicated multiple times which you can see in the attached screenshots

Thibaultmol

Vlad ah, somehow thought it did. aight. in that case maybe adding a better error that just says "pdf's aren't supported at this time" would be a good temp addition

uasi

The behavior of the text area on the Kagi Translate page, which hooks the Enter key press event directly to submit the form, is inconvenient for users of the Japanese input method. In the Japanese input method, the Enter key is used to confirm the conversion of characters during a composition session. If the text area captures the key press event and submits, it sends the input before the Japanese text is fully composed.

This issue and reproduction steps are well explained on the following page: https://dninomiya.github.io/form-guide/stop-enter-submit

The problem can be resolved by ignoring the key press when the isComposing property of the keyboard event is true. Could you please address this?

Additionally, this issue also exists in the text area of Kagi Assistant.

dix

Hi,

I created a bang to quickly translate some text in French, that I use mostly on mobile with Orion on iOS (iPhone 12 Mini).

The bang itself, and the translation, work as expected, but the UI result in a sub-optimal experience.

Here what I see when I use the bang:

When I translate something, my priority is to get the translated version of the source text, not the source text and the translation parameters.
Now I have a huge textarea with almost nothing in it, and I have to swipe up to get to the actual translation.

It's the opposite of the powerful experience offered by Quick Answer...

Thibaultmol

my nr 1 annoyance of Translate is that pressing ENTER does the translation.
The confusing part is that because it's a multiline text field, instinctively that means you can multi line type without having to worry about submission.
So I personally would prefer CTRL + ENTER for it to translate

matin

I'd love to try this out more, but it seems like the language selection drop-downs are not working for me. Clicking on either just changes the direction of the little triangle, but doesn't show a list of languages (the reverse detection button doesn't fit anything either). Putting some English text in there on chrome (not logged in) just passes it through, logged in while on Firefox or the kagi app seems to translate it to Spanish (all three attempts are on Android).

mixchiev

It would be nice if there were multiple suggestions for a translation, especially when translating a single word. Google translate gives a list of translated versions and reverse translation for each, which is sort of important in the way I have been using google translate, eg

The suggestions+reverse translations helps me a lot in finding the right word for an exact meaning/context. It does it mostly when translating into english, so eg croatian->english provides suggestions but english->croatian does not (it gives some suggestions if you click on the translated word but it is not as high quality).

Similarly when translating a phrase or a sentence it provides 1 or 2 more suggestions but you have to click on the sentence for that. I guess it is not as relevant when translating larger texts.

Vlad

We are aware of the language selection bug, working on a fix.

MonoMatrix

When pressing the Translate button with the text field empty, the following error appears:

As an idea, the button could remain disabled if the text field is empty:

I have also seen a strange error in the character counter, when you exceed the limit and press Translate, the counter disappears and does not reappear unless you reload the page:

I have also noticed that the language search works very well, but there are cases where I am not sure if it is the most ideal search. For example, if you search for "eng," Bengali appears first and then English. I understand that the search is done with a contains:

But Google Translate has a search that in addition to using the contains method, prioritizes results if your search is the beginning of the word not just that the language contains that word:

« Previous Page