SDL Trados Studio PlugIn - Ruby processing workaround using Comment

SDL Trados Studio PlugIn - Ruby processing workaround using Comment
SDL_Trados_Studio_PlugIn_Ruby_processing_workaround_using_Comment



It is version 2017 only












SDL Trados Studio does not support MS Word Ruby


I worte this one as one workaround


It adds Comment to Ruby 
so when Ruby be disappeared at SDL Trados Studio
it keeps Ruby information as a Comment
And at final (translated) file it shows itself as Comment of course


Do You want Count only ?  Why Not..

















Enjoy !!! 























Link
https://drive.google.com/file/d/1QVECPb5VOYMG7CoqgSBwNMYPEYD8iMnz/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 signature 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.
I have found a hard evidence;
https://deeptranslation.blogspot.com/2019/01/sdls-backdoor.html
You can guess what is going on there by this clue.