199

I've been using Translate to help a bit with Japanese learning. What I discovered just now is that the text to speech pronunciation doesn't seem to operate correctly for Japanese when using kanji? Maybe someone more experienced can confirm.

For example: 貴金属 the hiragana form is spoken correctly ききんぞく (kikinzoku), but the kanji sounds what I'm guessing is some Chinese reading, although the text is correctly automatically identified as Japanese. The romanization of the kanji is also correct, so it's just whatever is happening with the speech API you're using.

Sorry if this has been mentioned already, this thread is really long!

    I can't get the URL translation to work through the text input box. The box template text says "Start typing a URL" but if I put one in there, the translation output box just displays, at best, a translation of the actual URL contents. The URL feature is also mentioned in the documentation.
    I would have expected this to display the translated text of what's actually on the page, or at least redirect me to the translate.kagi.com/www.example.com version of the feature. Hope this helps 🙂

      Nashwan Hey, no worries - it was not mentioned. We'll look into this 🙂
      eggnog_90241 This will get fixed soon, thanks for the feedback.

          Japanese romaji are sometimes written incorrectly. I tried translating Japanese to English:

          次の漫画巻読み始まりました

          Kagi Translate displayed romaji: "Tsugi no manga-kan yomi hajimemashita"
          The correct romaji is: "Tsugi no manga-kan yomi hajimarimashita"

          The final word is wrong. This probably comes from the issue that the sentence is a bit weird, and it would be more natural to say "hajimemashita", so the AI assumed that. It should just spell romaji for what is written though, not what it thinks it should be.

            Can Kagi implement a user friendly way to download the audio from a translation?

              • dai

                • Post #420

                frin

                次の漫画巻読み始まりました ("Tsugi no manga-kan yomi hajimarimashita")

                I wonder if this is what it means when including the context?

                このマンガの1巻を読み終えたので2巻を読み始めたよ

                Native Japanese is,

                巻(Kan) means "volume" e.g. SONGS Vol1 or "chapter"

                "Kono manga no tsugi-no-kan wo yomi hajimemashita." is correct.

                frin-san is mostly correct.

                I hope this helps.

                  Thanks for including Latin, I find the translations to be pretty accurate. That's one over DeepL because they don't offer Latin. The German also seems pretty good. One feature I would request is that it would remember what languages you chose the next time visit the site, I.E. if you're translating English to German then close the site and come back it would go to English to German again instead of detect language.

                  Would like the kanji and/or kana (Japanese) to be displayed when typing romaji into Kagi translate.

                  For example: If I type "hajimeru" in google translate, it shows the kanji and kana for that below. But in Kagi translate, it does not.

                    Hello dear Kagi team,

                    I really appreciate the time you put into this service it is really useful.

                    Though recently my primary language (Central Kurdish (Sorani)) was remove from the list of supported languages and now only Kurmanji Kurdish is available.

                    Can you please add the remove language again? for your reference google translation supports both https://translate.google.com

                      Most of the PDF is not being translated and the ones that are translated are not properly placed.

                        Hey all, we've just released an update for Translate with several improvements:

                        • Modernized UI that's more consistent with our other products (like Assistant)

                        • Better theme support - your Kagi Search theme options are now fully respected, with fallback to browser preferences

                        • More natural translations that also better respect your settings (nichu42)

                        • Improved Word Insights, Alternatives, and Romanization (although frin is still happening - we're going to give it a second look soon)

                        • Enhanced alternative translations now provide insight about the main translation

                        • Dictionary entries now appear in the input box when translating single words

                        • Added 80+ languages including Central Kurdish (Sorani) which was previously removed (some-user sorry about that!) plus 80 other languages (thank you Ademalhanolu). And if you still can't find your language, you can manually type it in - and use it anyway. (jvbf).

                        • Default Target Language- When enabled, your locale language will be automatically set as the default "translate to" language whenever you open the app instead of it defaulting to the last one you used.

                        • New website translation views - while translating a website, you can now view both the original and translated versions in a horizontal or vertical split, in addition to the mode we already had. Drag your mouse in the middle to resize the iframes to your liking.

                        • Audio download now available for translations (peterfgalbraith)

                        Thank you all for the feedback! As a reminder, we are still looking into improving our translation of websites so that we can translate a larger number of them. We're also looking into improving our document translation, especially for PDFs. batuhan

                                        The Android app keeps crashing whenever I try to download the translated documents.

                                          batuhan I assume you are using the PWA? Does the same thing happen if you use a browser?

                                              Giorgio this update brought hilarious UI bug - Polish (the language) in the UI set to polish is translated as polerować (which is the thing you do to make something shiny) instead of Polski (which is the language name)

                                                  Giorgio Also, there is a lot of incorrectly translated elements in the UI, can you consider using localazy for Kagi Translate UI?
                                                  How it is currently:

                                                  How it should be (and it's just the settings menu, there are more incorrect translations in tooltips, other parts of Kagi Translate UI):

                                                    Judging from the pictures here, it seems the font is incorrect on my system (Firefox 137, Windows)?