SDL Trados Studio PlugIn - Stupid DeepMachineLearningTranslation kills TagPairs
SDL_Trados_Studio_PlugIn_Stupid_DeepMachineLearningTranslation_kills_TagPairs
It is version 2017 only
some idiot machine translations do not rekon Tags properly
so you should be in trouble
if fixed all of them properly, in One Go
of course
this is a brief testing
I do not use that dummy translation machines
enjoy
Link
https://drive.google.com/file/d/1uyXisvbYh6zKNGnxrSyrrWMT1ddEjxFG/view?usp=sharing
You can guess what is going on there by this clue.
SDL_Trados_Studio_PlugIn_Stupid_DeepMachineLearningTranslation_kills_TagPairs
It is version 2017 only
some idiot machine translations do not rekon Tags properly
so you should be in trouble
<Before you click PlugIn Icon>
<After you click PlugIn Icon>
if fixed all of them properly, in One Go
of course
this is a brief testing
I do not use that dummy translation machines
enjoy
Link
https://drive.google.com/file/d/1uyXisvbYh6zKNGnxrSyrrWMT1ddEjxFG/view?usp=sharing
...
..
.
[Note]
This program is Free of charge and has no hidden string absolutely.
Except, it does not have SDL signature.
I have tried to get SDL's sign but, SDL denied to sign my plugins.
SDL signs plugins exclusively to post their own place ONLY.
As you can see, this place is not the SDL's narrow homeground.
And, SDL says, You (not me) have to pay money to get SDL's signature for this one.
That's nonsense and bullshit. That signature is useless and needless.
The developer has final responsiblity for it, not the SDL.
Let's say you wanted to update or upgrade or nice idea for that.
What the heck SDL can do for you ? N.o.t.h.i.n.g.
- I saw it clearly, when SDL changed their stuff to 2019 version.
- They could do nothing. SDL just waited and saw its developers.
If you want warning_less version of it.
Tell me, I'll do it for you with the same cost.
Additionally, I suspect SDL could make a Backdoor when they check myPlugIns.
Just like Apple/MS/Intel/HuaWei.Though I do not have any kind of hard evidences.
This program is Free of charge and has no hidden string absolutely.
Except, it does not have SDL signature.
I have tried to get SDL's sign but, SDL denied to sign my plugins.
SDL signs plugins exclusively to post their own place ONLY.
As you can see, this place is not the SDL's narrow homeground.
And, SDL says, You (not me) have to pay money to get SDL's signature for this one.
That's nonsense and bullshit. That signature is useless and needless.
The developer has final responsiblity for it, not the SDL.
Let's say you wanted to update or upgrade or nice idea for that.
What the heck SDL can do for you ? N.o.t.h.i.n.g.
- I saw it clearly, when SDL changed their stuff to 2019 version.
- They could do nothing. SDL just waited and saw its developers.
If you want warning_less version of it.
Tell me, I'll do it for you with the same cost.
Additionally, I suspect SDL could make a Backdoor when they check myPlugIns.
Just like Apple/MS/Intel/HuaWei.
I have found a hard evidence;
https://deeptranslation.blogspot.com/2019/01/sdls-backdoor.htmlYou can guess what is going on there by this clue.