FiskmoMTPlugin for MemoQ causes DeepL plugin for MemoQ to fail during pretranslate

[Neil-Allen]

The error can be reproduced as follows:

• open MemoQ and make sure the FiskmoMTPlugin is loaded
• create a project in MemoQ and try to pretranslate it using the DeepL plugin that is part of MemoQ version 9.10 by default
• the pretranslation fails with an error message stating that some segments could not be translated
• when MemoQ is opened, there is a message asking if you want to load the unsigned FiskmoMTPlugin. If you do not load it, DeepL pretranslation works perfectly.

Attached is the MemoQ log file showing the exception involving FiskmoMTPlugin

It is not clear to me whether the problem lies in the FiskmoMTPlugin or in the DeepL Plugin
MemoQLite.2022-02-23-2022-03-09.log

[Neil-Allen]

For info, I have just had an online MemoQ project fail with the DeepL plugin when the Fiskmo plugin was not loaded. I created a local project, imported the same file and it pretranslated ok, whether or not the Fiskmo plugin was loaded in MemoQ. Looking at the MemoQ log (attached) there is an exception involving the Fiskmo plugin, but it did not stop the pretranslation.

This would seem to indicate that the problem lies with the DeepL plugin. I will try to gather further evidence and re-open a ticket with MemoQ to look into this. If I get any further relevant info, I will let you know.
MemoQLite.log

[TommiNieminen]

Hi, thanks for the exemplary bug report. The Fiskmo plugin (I have been intending to rebrand this as OPUS-CAT plugin for some time, but have not had time to do it yet) errors in the log file seem to indicate that there was no connection to the local MT engine while running the pretranslation. Does the Fiskmo plugin work in the editor view?

Unfortunately I can't test the pretranslation functionality directly, since pretranslation requires a proper memoQ license, but I tried out the relevant method in the plugin, and it appears to work. But the MT engine has to be running on the local computer, and the port setting must be the same in the memoQ plugin and the MT engine.

By the way, if you run the pretranslation in memoQ, isn't it only one MT provider that gets used? So if you receive errors from the Fiskmo plugin during pretranslation, then Fiskmo has been selected as the default pretranslation MT provider, and in that case DeepL would not have been used for pretranslation in any case? Or is it that the Fiskmo errors are generated even when DeepL is the MT provider selected for pretranslation?

-Tommi

[Neil-Allen]

Tommi, I just received another online project, so I was able to test the DeepL plugin both with this project and with the same files in a local project. The DeepL plugin failed each time. The Fiskmo plugin was not in the MemoQ directory structure. So I will take this matter up with MemoQ support and I apologise if I have wasted your time on this matter. Kind regards, -- Neil ALLEN www.allentrad.com <https://mailtrack.io/trace/link/5a3f17c372ddf2069c8924806cb1f3f53be4d87c?url=http%3A%2F%2Fwww.allentrad.com%2F&userId=3458764&signature=86d4e9b39e263c39> LinkedIn <https://mailtrack.io/trace/link/7c0fe9ba90f8002e9514151f358ed235c0111658?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Fneil-allen-language-services&userId=3458764&signature=1ce9f118046259fc> Tel: +33 982524950 Mobile: +33 661792057 https://www.ciol.org.uk/translator/profile/29634/36/596 <https://mailtrack.io/trace/link/00e5950560d3bf8669d1054c4c6e449fa8d93afa?url=https%3A%2F%2Fwww.ciol.org.uk%2Ftranslator%2Fprofile%2F29634%2F36%2F596&userId=3458764&signature=abafb046582e9ed2>

…

On Tue, Mar 15, 2022 at 10:11 AM Neil Allen ***@***.***> wrote: Hi Tommi, I suspect that the problem is related to the use of online projects, prepared on a MemoQ server, rather than projects prepared locally. I raised a ticket with MemoQ support to look into this, and they asked me to send them the log. However, when I looked at the log file, I saw the exception involving the Fiskmo plugin, so I ran a test on a LOCAL project without the Fiskmo plugin loaded, and it worked perfectly. So I jumped to what I now believe was the wrong conclusion that the Fiskmo plugin was at fault, and I closed the support ticket. In all cases, the DeepL plugin was selected as the default. But yesterday, I got another ONLINE project from one of my clients and the pretranslate with DeepL failed again, despite the fact that the Fiskmo plugin was not loaded. So I created a test LOCAL project and tried the DeepL pretranslate twice, once with the Fiskmo plugin loaded and once with it not loaded, and the DeepL pretranslation worked correctly both times. So it appears that it is only ONLINE projects (which I cannot create myself) that are involved. I have now completely removed the Fiskmo plugin .dll from my MemoQ installation and I am waiting for another online project from a client (unfortunately, this might take a while) to see what happens when I try to use the DeepL plugin. If it fails again without the Fiskmo .dll even being present, I think we can rule out this plugin as the source of the problem. When I have more evidence, I will raise another support ticket with MemoQ and I will keep you informed of the outcome. In the meantime, I will delete my tweet about the OPUS-CAT plugin, as we cannot say that it is the source of the problem. Neil -- Neil ALLEN www.allentrad.com LinkedIn <https://www.linkedin.com/in/neil-allen-language-services> Tel: +33 982524950 Mobile: +33 661792057 https://www.ciol.org.uk/translator/profile/29634/36/596 On Tue, Mar 15, 2022 at 9:35 AM TommiNieminen ***@***.***> wrote: > Hi, thanks for the exemplary bug report. The Fiskmo plugin (I have been > intending to rebrand this as OPUS-CAT plugin for some time, but have not > had time to do it yet) errors in the log file seem to indicate that there > was no connection to the local MT engine while running the pretranslation. > Does the Fiskmo plugin work in the editor view? > > Unfortunately I can't test the pretranslation functionality directly, > since pretranslation requires a proper memoQ license, but I tried out the > relevant method in the plugin, and it appears to work. But the MT engine > has to be running on the local computer, and the port setting must be the > same in the memoQ plugin and the MT engine. > > By the way, if you run the pretranslation in memoQ, isn't it only one MT > provider that gets used? So if you receive errors from the Fiskmo plugin > during pretranslation, then Fiskmo has been selected as the default > pretranslation MT provider, and in that case DeepL would not have been used > for pretranslation in any case? Or is it that the Fiskmo errors are > generated even when DeepL is the MT provider selected for pretranslation? > > -Tommi > > — > Reply to this email directly, view it on GitHub > <#34 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AYG2XK4CSPHLBXYQES6WHEDVABDUDANCNFSM5QVBK4LQ> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[Neil-Allen]

Hi Tommi, I suspect that the problem is related to the use of online projects, prepared on a MemoQ server, rather than projects prepared locally. I raised a ticket with MemoQ support to look into this, and they asked me to send them the log. However, when I looked at the log file, I saw the exception involving the Fiskmo plugin, so I ran a test on a LOCAL project without the Fiskmo plugin loaded, and it worked perfectly. So I jumped to what I now believe was the wrong conclusion that the Fiskmo plugin was at fault, and I closed the support ticket. In all cases, the DeepL plugin was selected as the default. But yesterday, I got another ONLINE project from one of my clients and the pretranslate with DeepL failed again, despite the fact that the Fiskmo plugin was not loaded. So I created a test LOCAL project and tried the DeepL pretranslate twice, once with the Fiskmo plugin loaded and once with it not loaded, and the DeepL pretranslation worked correctly both times. So it appears that it is only ONLINE projects (which I cannot create myself) that are involved. I have now completely removed the Fiskmo plugin .dll from my MemoQ installation and I am waiting for another online project from a client (unfortunately, this might take a while) to see what happens when I try to use the DeepL plugin. If it fails again without the Fiskmo .dll even being present, I think we can rule out this plugin as the source of the problem. When I have more evidence, I will raise another support ticket with MemoQ and I will keep you informed of the outcome. In the meantime, I will delete my tweet about the OPUS-CAT plugin, as we cannot say that it is the source of the problem. Neil -- Neil ALLEN www.allentrad.com <https://mailtrack.io/trace/link/f94fde28a91825f45377af50a5889f53fc31dc8a?url=http%3A%2F%2Fwww.allentrad.com%2F&userId=3458764&signature=9fe9127f8f271baf> LinkedIn <https://mailtrack.io/trace/link/ff2bef798b6abbe9ff52b1812c0b2ded0c3055fe?url=http%3A%2F%2Fwww.linkedin.com%2Fin%2Fneil-allen-language-services&userId=3458764&signature=5ceb76bb9b01711a> Tel: +33 982524950 Mobile: +33 661792057 https://www.ciol.org.uk/translator/profile/29634/36/596 <https://mailtrack.io/trace/link/a237ee6ea512d63ac46db0e3f9c82375aca349a6?url=https%3A%2F%2Fwww.ciol.org.uk%2Ftranslator%2Fprofile%2F29634%2F36%2F596&userId=3458764&signature=b88b3327961a512f>

…

On Tue, Mar 15, 2022 at 9:35 AM TommiNieminen ***@***.***> wrote: Hi, thanks for the exemplary bug report. The Fiskmo plugin (I have been intending to rebrand this as OPUS-CAT plugin for some time, but have not had time to do it yet) errors in the log file seem to indicate that there was no connection to the local MT engine while running the pretranslation. Does the Fiskmo plugin work in the editor view? Unfortunately I can't test the pretranslation functionality directly, since pretranslation requires a proper memoQ license, but I tried out the relevant method in the plugin, and it appears to work. But the MT engine has to be running on the local computer, and the port setting must be the same in the memoQ plugin and the MT engine. By the way, if you run the pretranslation in memoQ, isn't it only one MT provider that gets used? So if you receive errors from the Fiskmo plugin during pretranslation, then Fiskmo has been selected as the default pretranslation MT provider, and in that case DeepL would not have been used for pretranslation in any case? Or is it that the Fiskmo errors are generated even when DeepL is the MT provider selected for pretranslation? -Tommi — Reply to this email directly, view it on GitHub <#34 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYG2XK4CSPHLBXYQES6WHEDVABDUDANCNFSM5QVBK4LQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>