171

Peter This issue will be resolved soon. 🙂
jvbf We are currently evaluating this. In the meantime, you can keep editing the URL. If you have a compelling specific use case for this, we'd love to hear about it.
tuesday This should now be fixed, thank you!
dai Hello! Website translation does not support options yet. Once they are available in the UI, you will also be able to manually add them in the URL. 🙂

Also as a FYI: we are still investigating the older issues that have not yet been addressed. Thanks for the constant stream of feedback!

          The English word 'capitalization' partly—according to Merriam-Webster—means 'the use of a capital letter in writing or printing'.

          According to Kagi Translate, the translation is either 'kapitalisering', which is a finance term, or 'versalisering'—a word that does not exist; check https://svenska.se, for example—or 'skrivning med stora bokstäver', which can be translated to 'writing in big letters', which is wrong.

            The Translate widget in Search is buggy: the search field inside the language drop-menu menu does not return anything anymore.

            Also, I cannot get the widget to show up for queries with more than "Translate" like

            • translate hello
            • translate hello to french
            • translate hello from english to french
              …

            This is a new, unexpected behavior for me.

              pivic Hey, I am kind of lost here - what would be the correct translation for capitalization then?
              goulot_situez Sorry, we are fixing this!

              edit:
              Peter We should have fixed this, let us know if it happens again 🙂

                    Not sure if this has been mentioned before, but selecting text in the translated output is a hit and a miss, one of the vexing things I have to say. Included a gif:

                      bkrein Hey, I apologize for the inconvenience. Looks like it's a bug that specifically affects Firefox users only, and we'll have it fixed soon. As a workaround, you can just CTRL/CMD+A and CTRL/CMD+C in the meantime.

                      garymm
                      lango_tri We are currently investigating both of these. 🙂

                            I absolutely love the alternative translation suggestions and word insights. It's too bad that they stop working if a text exceeds 150 characters. Is there any change to adjust the app that the features are re-enabled when I mark a certain sentence in the translation box? Right now, I have to copy the translation in notepad and copy back single sentences out of it.

                              bkrein This issue has now been fixed. Sorry again about that!

                              nichu42 This feature is partially implemented. You can now select a specific portion of the output translation (as long as it remains under the 150 character limit), and alternative translations for that selected text will load automatically.

                              Regarding word insights, the implementation is more complex (primarily from a UI/UX perspective), so we need to give it additional consideration.

                              nichu42 Thank you! 😄

                                    Kagi translate down?

                                    https://translate.kagi.com/?text=bonjour&target=auto&from=fr&to=auto and changing languages returned multiple errors and changing languages didn't fix anything.

                                    I first got Firefox console error: Language detection failed: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data. But I'm now getting errors 503 (Service Unavailable).

                                    I'm in West Europe and https://status.kagi.com/ doesn't report any issue at the moment (I assume it would be under Search europe-west2 or -west4).

                                      Recently there's been this focus outline around the input field for me (Firefox):

                                      Doesn't impact usability at all but looks funky especially with the sharp corners over top the rounded ones.

                                        My main use-case is translating between two languages in a given setting. Changing back and forth between those languages. E.g. German and English in a certain context, English and Spanish in another.

                                        Now, let's say I translate Beispiel from German to English:

                                        Next I enter an English sentence, it would be nice if Kagi could recognize the language and automatically switch them from English to German, instead of me having to click every time:

                                        I don't see the use-case ever where one doesn't want the left upper to say 'English' when Kagi can recognize that it is English.

                                        Or have that as an option in the settings.

                                          Giorgio

                                          from 2025-02-25. Japanese/
                                          javascript:(function()%7Bvar%20selectedText=window.getSelection().toString().trim();window.location.href='https://translate.kagi.com/Japanese/'+(selectedText?'?text='+encodeURIComponent(selectedText):encodeURIComponent(window.location.href));%7D)();

                                          But. this bookmarklet not work to 2025-02-26.

                                              lghjb656 I believe I've captured your use case below, lmk if I've gotten smth wrong.

                                              As you can see Translate is already able to switch between languages just fine, so long as you start with Detect Language selected (i.e. I wouldn't want to have selected Russian before pasting the text). The language that it says it detected doesn't change tho, that would be worth looking at to improve UI readability.
                                              Also not sure if the line breaks not being copied from the output is a bug or an epic fail on my part, if bug that should be fixed too 🙂