- Oct 2, 2024
- 190
- 100
Cannot load translation procedure. Please reinstall your DeepL addonYou must be registered to see the links
Cannot load translation procedure. Please reinstall your DeepL addonYou must be registered to see the links
Hi
Do you have translator ++ with Baidu Web addon worked inside ?
Actually that error is not correct.Thank you for sharing the addon
But I installed it by extracting the zip file to the translator++ folder
When I try to translate by Baidu Web
It said that
View attachment 4321322
Do you know how to fix ?
are you gonna open source urs?Actually that error is not correct.
And is a small example of how buggy dreamsavior code is... (I could use harsher words but anyway...)
It should state that: "The addon was installed correctly, please reinstall it..."
And is related with the files "addon.js", "AddonUtils.js" in the directory "\Translator++\www\js" and the various "*.js" files in the "Translator++\www\js\autoload\utils" subdirectory.
Extracting an addon or even installing it through the translator++ interface won't work, unless you are already logged in as a patron.
You can override it (and force an offline installation), if you modify a bit the "addon.js" and the "updater.js" files.
ps. This is my last post in this thread, since I do not consider the current translator++ a worthy project... neither for my money, nor time... I lost enough of them by being dreamsavior's patron for 3-4 years... (heck with all the time I spend debugging this @#!@ program I could have developed my own proxy translator/parser)
can you share the accountActually that error is not correct.
And is a small example of how buggy dreamsavior code is... (I could use harsher words but anyway...)
It should state that: "The addon was installed correctly, please reinstall it..."
And is related with the files "addon.js", "AddonUtils.js" in the directory "\Translator++\www\js" and the various "*.js" files in the "Translator++\www\js\autoload\utils" subdirectory.
Extracting an addon or even installing it through the translator++ interface won't work, unless you are already logged in as a patron.
You can override it (and force an offline installation), if you modify a bit the "addon.js" and the "updater.js" files.
ps. This is my last post in this thread, since I do not consider the current translator++ a worthy project... neither for my money, nor time... I lost enough of them by being dreamsavior's patron for 3-4 years... (heck with all the time I spend debugging this @#!@ program I could have developed my own proxy translator/parser)
are you going to do it? If so, will you maintain compatibility with translator++ addons? his code always triggered my OCD. I always wanted to refactor the backend to use only nodeJS and use astro in the frontend to add componentization and typescript, so the resulting JS files would be split and wouldn't be huge as they are now.Actually that error is not correct.
And is a small example of how buggy dreamsavior code is... (I could use harsher words but anyway...)
It should state that: "The addon was installed correctly, please reinstall it..."
And is related with the files "addon.js", "AddonUtils.js" in the directory "\Translator++\www\js" and the various "*.js" files in the "Translator++\www\js\autoload\utils" subdirectory.
Extracting an addon or even installing it through the translator++ interface won't work, unless you are already logged in as a patron.
You can override it (and force an offline installation), if you modify a bit the "addon.js" and the "updater.js" files.
ps. This is my last post in this thread, since I do not consider the current translator++ a worthy project... neither for my money, nor time... I lost enough of them by being dreamsavior's patron for 3-4 years... (heck with all the time I spend debugging this @#!@ program I could have developed my own proxy translator/parser)
At least he heard me
are you gonna open source urs?
At the moment, I have no plans of making one.are you going to do it? If so, will you maintain compatibility with translator++ addons? his code always triggered my OCD. I always wanted to refactor the backend to use only nodeJS and use astro in the frontend to add componentization and typescript, so the resulting JS files would be split and wouldn't be huge as they are now.
give us a heads-up if you do itAt the moment, I have no plans of making one.
If in the future I have more free time and decide to make one it will be open source.
Sure, if I decide to do it... but don't get your hopes up, since it is not something that will happen anytime soon.give us a heads-up if you do it