199

Looking at the English->Hungarian translator it's mellowing the profanities, like turning "fuck" into "franc" which has the same vulgarity as "hell". Or "Take another fucking step, motherfucker." -> "Tegyél meg még egy rohadt lépést, te rohadék." ("Take another damned step, you bastard")

Excelente traductor, mejor que DeepL pero aún debe limar algunas asperezas. Las cuales están reflejadas en la foto que adjunto.

  • Vlad replied to this.
    Merged 1 post from Imperfecciones en la presentación.

      OscarZamora Please post comments/screenshots in English.

        Que conservara el mismo estilo de redacción.

          Thibaultmol changed the title to Translate doesn't keep exact formatting as source text .
            Merged 2 posts from Translate doesn't keep exact formatting as source text.

              Is there a way to set the language via a query parameter? I'd like to set up a Kagi Bang to translate a phrase from a specific language (to English).

              • BenH replied to this.

                -

                -

                  Certain texts with a lot of offensive words will apparently trigger guardrails of some kind, causing it to only output "I’m sorry, I can’t assist with that." instead of translating the text.

                  One example I found is a giant block of text that (using Google Translate) turned out to be the "Navy Seal Copypasta" translated into Finnish. Removing one of the first sentences then actually causes it to state "I'm not going to translate that." in place of any translation.

                  You can look it up what that text is (an old meme, not a real threat) and you'll probably understand why, but it should still just translate the text and not have "opinions" on what you're translating, especially without any other context.

                    cnp09 Can replicate using the aforementioned Finnish version of the Navy seal copypasta. Interestingly this only seems to trigger with some languages, ex. translating the Engligh Navy seal copypasta from English to Finnish gives an error, yet translating it from English to Russian works fine. Either way definitely an issue.

                      I've realized that the German pronounciation of "Kanban" was wrong: It sounded like "banban", while it should be like the Japanese one, with a K in the beginning: https://translate.kagi.com/?text=kanban. But then, when I chose German "Kanban" to Polish "kanban", the German word suddenly was pronunced correctly. But as soon as I switch (Polish on the left, German on the right), the German proncounciation suddenly is ony "Ban". I also realized that the Polish pronounciation differs, depending on whether it "is on the left" (= source language) or the right (= target): It either sounds like "Nkanban" or "kanban". I'm using the latest Firefox on a WIndows machine, in case that's of importance here.

                      So, in summary: a) The pronounciation of words is inconsistent, sometimes wrong and seems to depend on whether its source or target language as well as if the word is written with a capital letter or not. b) "kanban" makes a strong candidate for semantic oversaturation experience very quickly. 🤣

                        Is there a fix for the following happening when using Kagi translate in Safari?

                        • BenH replied to this.

                          I'm genuinely curious, where is the tts from? It's really good

                            Hey cmdress, does this still happen if Grammarly is disabled? Does this happen every time or just occasionally?