@Michael Davies

I experience a similar problem when confirming (CTRL+ENTER) the first segments at the beginning of the translation.

1. I don't remember having faced this problem before Studio 2019 (But this is when I started using the MyMemory plugin).
2. I must shut down Studio using the MS (Windows 7 Pro) Task Manager, open it again and deactivate MyMemory before confirming my first segment.

(Well, I found a workaround, but if I get distracted and do not apply the workaround procedure to the letter, troubles again!)

In my personal case, is it a MyMemory bug  or a Studio bug? 

Regards, Gérard

That's an interesting observation, Gérard. I will try to do as you have suggested as I also use the MyMemory plugin. However, the work process I usually use in connection with MyMemory is to have the plugin activated during a first pass machine translation and then deactivate it (to avoid being charged twice for the lookups) during a following post-editing pass. This should mean that when I restart Studio 2019 following a lockup, it should be in the same state as you have described in your reply.

I do not have the same problem when I use Studio 2017 where I also have the MyMemory plugin installed.

I am inclined to think that, in my case, it is not the MM plugin that is the cause of the problem. However, I could try uninstalling the MM plugin completely and see if it makes a difference.

/ Michael

@Michael Davies

Since your problem is more similar to mine than what I initially thought, here is the workaround (while waiting for the bug to be solved either by Studio or by MM developers).

If, right at the beginning of the translation, a target segment is filled in by a 99% TM match (My settings are: 100% matches are auto-confirmed) or a lower TM match you have selected and reworked, don't confirm this/these segment(s). Wait for the first MM translation proposal, which you will select, rework and confirm, and only then you can go back to the previous segments and confirm them. From then on everything runs smoothly.

To sum up, with Studio 19 and MM as they are, the first target segment  to be manually confirmed must always be a translation deriving from a MM proposal.

I hope this can prove useful to you and maybe some other fellow translators.

Regards. Gérard

@Michael Davies

Since your problem is more similar to mine than what I initially thought, here is the workaround (while waiting for the bug to be solved either by Studio or by MM developers).

If, right at the beginning of the translation, a target segment is filled in by a 99% TM match (My settings are: 100% matches are auto-confirmed) or a lower TM match you have selected and reworked, don't confirm this/these segment(s). Wait for the first MM translation proposal, which you will select, rework and confirm, and only then you can go back to the previous segments and confirm them. From then on everything runs smoothly.

To sum up, with Studio 19 and MM as they are, the first target segment  to be manually confirmed must always be a translation deriving from a MM proposal.

I hope this can prove useful to you and maybe some other fellow translators.

Regards. Gérard

Gérard LAMBERT

Gérard LAMBERT said:

To sum up, with Studio 19 and MM as they are, the first target segment  to be manually confirmed must always be a translation deriving from a MM proposal.

Does this happen for you with any other MT provider?  If it does it's probably an issue we should look at in Studio, but if it doesn't....

@Paul FILKIN

Sorry for not being able to answer either yes or no, but currently I am not using any other MT.

Gérard LAMBERT

ok... perhaps when you get a chance in the future you can see whether you have the same problem.  If you add Language Cloud from Studio just to test as it's free then it might be helpful.  But if you have access to another MT plugin it would be better as we would be comparing MT providers that get used in Studio in the same (similar) way.

Merci, Gérard ... very interesting suggestion, which I will try. From your described solution, it sounds as though the bug might be in MM. I will, as I mentioned, remove the MM plugin completely and see if this makes a difference. If so, then this would appear to confirm that the MM plugin is indeed the culprit.

Cordialement, Michael

I hve been a user of Language Cloud for at least a couple of years.

Further to my last posting re. the MM plugin, I have now completed the following tests using a previously completed translation where I have changed the status of the 1st 100 TU's from 'confirmed' to 'draft' after which, I then proceeded to confirm the individual TUs using the shortcut keys (CTRL+ALT+ENTER - the default with my version of Studio 2019 :

1. With the MM plugin deactivated

2. With the MM plugin activated, but not added to the TM's for the project

3. With MM plugin activated and added to the TM's for the project but not selected

4. with the MM plugin activated, adeed to the TM's for the project and selected.

In all 4 cases, the result was identical: I was able to confirm the 1st 80 TUs without a hitch, but when I tried to confirm TU No. 81, the user interface locked up. I could see (using Process Explorer - a more advanced replacement for the Task Manager) that the underlying application was still functioning, which confirmed my earlier impression that it is only the UI that freezes, not the underlying application.