Trados Business Manager
Speech to Text
Managed Translation - Enterprise
Translation Management Connectors
Language Weaver Connectors
Language Weaver Edge
Tridion Docs Developers
RWS User Experience
Internal Trados Ideas Community
RWS Community Internal Group
RWS Access Customer Portal
RWS Professional Services
RWS Training & Certification
RWS Enterprise Technology Partners
Trados Academic Partners
Trados Approved Trainers
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic Tridion Docs User Group
Tridion Docs Europe & APAC User Group
Tridion UK Meetup
Tridion User Group Benelux
Tridion User Group New England
Tridion User Group Ohio Valley
Tridion West Coast User Group
WorldServer User Group
Trados GroupShare Ideas
Trados Studio Ideas
Language Weaver Ideas
Language Weaver Edge Ideas
RWS Language Cloud TMS Ideas
RWS Language Cloud Terminology Ideas
RWS Language Cloud Online Editor Ideas
Managed Translation - Enterprise Ideas
Tridion Docs Ideas
Tridion Sites Ideas
LiveContent S1000D Ideas
Events & Webinars
To RWS Documentation
To RWS Support
Detecting language please wait for.......
I use MT Enhanced Plugin to enable Microsoft MT.
My language pair is Ru -> Es (Spanish International), and the Russian source contains English phrases that I do not need to translate.
Can I somehow disable translation of Latin characters in Cyrillic?
I guess you have a number of ways to do this but all will require some effort on your side.
Way #1Add them to a redact list in the MT Enhanced plugin so they are not sent for translation…
In case you didn't notice this plugin was updated a couple of days ago and it included a fix for the issue mentioned in this thread:
We have a problem with plugin installation. Studio version is not compatible (grayed out). No updates are found for this version yet.
If your EN phrases are complete segments then you could filter out the Russian. For example, if you have this:
You could use this in the display filter:
And this gets you this:
If you wanted to lock the EN just reverse the filter, copy source to target, change status to translated and lock:
Unfortunately, this option doesn't help me, because English text is inside Russian and I get the following after MT:
So, I need to leave English in Spanish...is it possible?
Way #1Add them to a redact list in the MT Enhanced plugin so they are not sent for translation.https://github.com/sdl/Sdl-Community/tree/master/MT%20Enhanced%20Provideralso explained nicely here by Spiros Doikashttps://metafrastis.wordpress.com/2016/05/06/customise-machine-translation-in-sdl-studio/
Way #2Depending on the filetype you may be able to hide the text or give it a non-translatable style in the source file. This would lock it like this for example (marked as hidden text in Word):
Looks like this in Studio:
Way #3If you can't hide this text because the source format doesn't allow it (it's easy in Word for example) then you could also do the same thing by tagging after the file is open in Studio using the SDL Data Protection Suite from the appstore. It's very simple to create a list and have them ignored.
Way #4Add the English as variables to your TM. This should work, but I did get some odd things happening:
Segment #1 didn't pay attention to it at all even though it was recognised (note the blue underline), segment #2 worked but the quotes look wrong, segment #5 worked perfectly. I probably pushed the use of variables to the limit here, not sure, but I do think this method should work. Will investigate with support when we get back from xmas leave.
I tried Way #3 to tag English words but MT engine still translates them in an odd way.
What am I doing wrong?
I suppose that I should lock these tags (like make them non-translatable). But I don't know how.
In the same file I have the following (non-translatable entities are not translated):
I don't think you're doing anything wrong... although you could convert these into single tags as you don't need to add word by word.
I tested with SDL MT Cloud first as I had that installed... and it works fine:
So I then tried again using MT Enhanced and using the Microsoft MT:
I get the same as you. So it looks like it's either a bug in the plugin or a bug with Microsoft handling of the tags. So I tested with the Google side to the plugin too and have the same problem. So I'm leaning towards this being a problem with the plugin. I'll log it, but we won't get to this until we return in the New Year I'm afraid as the entire community dev team are on leave until the new year now.
The only thing I can suggest is that you use SDL MT Cloud instead, or try a different approach.
For your reference to make it easier to follow up, I logged this as SDLCOM-2355.
Thank you for your response. I will keep track of that.
Have a blissful Christmas Eve!
An important point is that we were able to solve this on the Google side, but there is still a small problem with Microsoft in your example, but we cannot address this as it's a problem related to how the information is being handled on the Microsoft server and not the plugin. Have a play and see whether this resolves things for you.
Where did you get the plugin from? Are you sure you are using the correct plugin for this version of Studio? I just downloaded thelatest plugin from the appstore and ran the installer:
It definitely works.
Hi Paul, I did get the last version 18.104.22.168 for 2021 and yet have the same problem as Victoria Zolotareva, my Studio version is grayed out. What can I do to make it work? Thank you!
And your version of Studio 2021?
Anna Yurikhina said:I did get the last version 22.214.171.124 for 2021
Now you show this:
Anna Yurikhina said:It's 126.96.36.19949
Sounds as though you are trying to install a plugin designed for Trados Studio 2021 into Trados Studio 2019. This will not work. You need the 2019 version of the plugin.