[GUI Plugin] Ebook Translator

[Beeff]

I installed the latest version of Calibre 7.24 and the Ebook Translator v.2.3.5 to translate epubs. That worked more than excellently a few times. But from one day to the next it didn't work anymore. When I selected an epub and pressed Start, the next screen flashes by and disappears again no matter what I try. I uninstalled the plugin and reinstalled it: no result. Then I uninstalled Calibre, removed all remnants with Ccleaner, also cleaned the Windows registry and reinstalled it: again no result. What else can I do because I am so happy with the plugin when it works?

[JSWolf]

Originally Posted by Beeff

I installed the latest version of Calibre 7.24 and the Ebook Translator v.2.3.5 to translate epubs. That worked more than excellently a few times. But from one day to the next it didn't work anymore. When I selected an epub and pressed Start, the next screen flashes by and disappears again no matter what I try. I uninstalled the plugin and reinstalled it: no result. Then I uninstalled Calibre, removed all remnants with Ccleaner, also cleaned the Windows registry and reinstalled it: again no result. What else can I do because I am so happy with the plugin when it works?

It could be that the translate website that's being used changed something and the plugin need to be adjusted for these changes.

When a plugin does not work, there's no need to be so extreme. Most times it's the plugin that needs updating.

[cvs]

Hi, amazing plugin, thanks for making it.

I'm using rolling release ebook-translator_20250117111414, but unfortunately, Google is not playing ball (it used to before) when converting from:
Portuguese Brazilian to
Portuguese from Portugal.

In Google (Free) the output comes out as brazilian verbatim.
In Google (Basic) there's always an error returned: Bad language pair: pt|pt-PT . I believe it happens the same for the pair pt-BR|pt-PT.

But if I go to Google Translate official web interface, it converts perfectly (with the highest accuracy of all) between brazilian and portuguese.

Could you possibly look into it and update these engines? It makes a huge difference for portuguese people, most books on the market come in brazilian pt....
Thanks!

[BetterRed]

Nice plugin, couple of issues.

1. Why is the bookfere.com folder not stored in the config plugins folder? Plugin specific folders can be stored in the plugins folder - e.g job_spy:



2. Can an option be added to store the output file in the book's 'data' folder, which would be created if it didn't exist.

Thanks BR

[DNSB]

Has anyone heard anything from kindlefere in the last while. The last update was in June, 2024 and his last login was in Sept., 2024? I was reminded of this when looking at BetterRed enhancement request.

[Comfy.n]

Originally Posted by DNSB

Has anyone heard anything from kindlefere in the last while. The last update was in June, 2024 and his last login was in Sept., 2024? I was reminded of this when looking at BetterRed enhancement request.

I noticed this too, but it seems @kindlefere is currently more active on other platforms like Github (latest commit: January 17, which is also the latest rolling release date) and 𝕏 (latest post: February 6), Telegram (also last seen Feb 6) and website (2025-02-06T14:26:52+08:00). 🕵️

[BetterRed]

Originally Posted by DNSB

Has anyone heard anything from kindlefere in the last while. The last update was in June, 2024 and his last login was in Sept., 2024? I was reminded of this when looking at BetterRed enhancement request.

I hadn't noticed the OPs absence, my interest was rekindled by Reuben's post in the Sigil forum.

BR.

[kindlefere]

Originally Posted by dunhill

I leave the mo and po files completing the Spanish translation of the plugin.

Thank you. The translation has been updated to the latest version.

[kindlefere]

Originally Posted by Niki22

Hi, Thank you for developing such a useful plugin! However, I’ve encountered an issue with Ebook Translator when translating my books. After the translation process, the original CSS classes and styles in the book are altered. For example, custom <span> tags with class names are either replaced or overwritten with inline styles. This causes the book's formatting, such as italics or specific designs, to break.

Is it possible to add an option to preserve the original HTML structure and CSS classes during the translation process? It would be helpful if the plugin could translate only the text without modifying any of the existing tags, classes, or inline styles.

Looking forward to your reply and thank you in advance for your time!

Currently, translation removes all tags, leaving only plain text, since most engines can't handle HTML properly. I'll try to preserve the original format if possible.

[kindlefere]

Originally Posted by scibra

Please update the plugin, Google added new languages ​​to the Cloud API, and now supports both variations of the Portuguese language (Portugal and Brazil). Thank you very much!

The latest version includes an updated Google Translate API.

[kindlefere]

Originally Posted by levante

Thanks a lot for this plugin. There are so many books that will never be translated.
Please, if possible, consider adding an engine for ollama so that it can work without internet.

Thanks again

I suggest using the Custom Engine feature to add any engine not yet included in the built-in engines. For details, refer to the project wiki.

[kindlefere]

Originally Posted by scibra

Thank you very much for this wonderful translation tool.
I made a donation as a thank you.

[IMG]https://ibb.co/q0b6d8p[/IMG]

Why isn't ebook title metadata being translated? Since version 2.3.5, it no longer automatically translates ebook titles.

[IMG]https://ibb.co/xLHFctZ[/IMG]

The title translation doesn't appear here, as shown in the figure. If you don't check and modify it, it will be translated along with the other content. First, make sure that "Metadata Translation" is enabled in the settings.

[kindlefere]

Originally Posted by Beeff

I installed the latest version of Calibre 7.24 and the Ebook Translator v.2.3.5 to translate epubs. That worked more than excellently a few times. But from one day to the next it didn't work anymore. When I selected an epub and pressed Start, the next screen flashes by and disappears again no matter what I try. I uninstalled the plugin and reinstalled it: no result. Then I uninstalled Calibre, removed all remnants with Ccleaner, also cleaned the Windows registry and reinstalled it: again no result. What else can I do because I am so happy with the plugin when it works?

There may be a bug. To make debugging easier, I suggest running the command

calibre-debug -sg

to open Calibre in debug mode. Then, run the plugin as usual and check the console for any error messages.

[kindlefere]

Originally Posted by cvs

Hi, amazing plugin, thanks for making it.

I'm using rolling release ebook-translator_20250117111414, but unfortunately, Google is not playing ball (it used to before) when converting from:
Portuguese Brazilian to
Portuguese from Portugal.

In Google (Free) the output comes out as brazilian verbatim.
In Google (Basic) there's always an error returned: Bad language pair: pt|pt-PT . I believe it happens the same for the pair pt-BR|pt-PT.

But if I go to Google Translate official web interface, it converts perfectly (with the highest accuracy of all) between brazilian and portuguese.

Could you possibly look into it and update these engines? It makes a huge difference for portuguese people, most books on the market come in brazilian pt....
Thanks!

I checked the API endpoint for Google (Basic) and didn't find any changes. Maybe the API version doesn't support this language pair? I'll continue tracking the issue.

[kindlefere]

Originally Posted by BetterRed

Nice plugin, couple of issues.

1. Why is the bookfere.com folder not stored in the config plugins folder? Plugin specific folders can be stored in the plugins folder - e.g job_spy:

Attachment 213653

2. Can an option be added to store the output file in the book's 'data' folder, which would be created if it didn't exist.

Thanks BR

The first issue has been resolved in the latest version. As for the second suggestion, is manually specifying the output path sufficient?