Detecting language please wait for.......
I have noticed that NMT engine tends to truncate or totally distort some drug molecule names. It totally scrambles everything and invents words instead. See screenshot hereunder. I would like to point out that this does NOT happen with Language Cloud engines (I checked it on the same file, same segments, etc.), and since NMT is supposed to be more powerful and efficient than Language Cloud, this should be resolved ASAP.
Isla ... on behalf of all medical translators
SDL Machine Translation Cloud (aka BeGlobal v4 NMT) translation provider plugin for SDL Trados Studio 2019 does not yet support Dictionary. There are plans to add it, but don't know when that will be.…
would it help / be possible for the NMT engines to use an SDL Language Cloud Terminology termbase (which includes such non-translatable medical terms) as an MT dictionary?
Though the MT dictionaries…
There is an upgrade path to a paid subscription of SDL Machine Translation that will allow you to use its Dictionary feature: https://docs.sdl.com/LiveContent/content/en-US/SDL%20BeGlobal…
NMT has an algorithmic imperative to provide a result even if it has no worthwhile data to work with. So, it will find something that looks kinda like it could maybe be relevant, and returns that as output. See https://www.teachyoubackwards.com/qualitative-analysis/#ooga-booga for an example.
Isla, as Martin pointed out, NMT will struggle with very long strings full of tags and unknown words, not normally found in English dictionary (or in corpora used to train the MT engine). These are a domain specific terms (Medical) for which more useful would be a custom-trained engine.
The quality of the MT output also depends on what filter on MT side is used to parse the content. You may get different results when you send the same string with tags converted to XLIFF, SDLXLIFF or HTML format
In your example I can see the segmentation could be improved e.g. ( <p> <ul> and <li> tags should be set as Structure tags), so you get each list item on a new segment. In that case you'll get better leverage from a TM and Machine translation.
Though the MT dictionaries just provide an override mechanism / simple search and replace of dictionary entries in the NMT output, it might actually provide to be very beneficial in this case.
See https://gateway.sdl.com/apex/communityknowledge?articleName=000004051 - I think it is still valid for NMT?
SDL Machine Translation Cloud (aka BeGlobal v4 NMT) translation provider plugin for SDL Trados Studio 2019 does not yet support Dictionary. There are plans to add it, but don't know when that will be.
SDL Language Cloud provider does provide Dictionary support, but it is for SMT (Statistical MT) and soon to be deprecated.
In Isla's case the first step should be to resolve the segmentation which should help. If the medical terms in brackets () don't need to be translated then in Studio they could be added to a Variable Lists within Language resource Template alternatively crafting some Regex rules in filter settings to lock them/turn them into placeholders during text extraction.
There is an upgrade path to a paid subscription of SDL Machine Translation that will allow you to use its Dictionary feature: https://docs.sdl.com/LiveContent/content/en-US/SDL%20BeGlobal%20Online%20Help-v1/GUID-C0E595E6-28F5-4C59-8BBB-CAF8620FB4FA.
The Trados Studio to SDL Machine Translation Cloud plugin is being updated to include the ability for users to select which Dictionary to use while they're in Trados Studio. You can watch for updates here: https://appstore.sdl.com/language/app/sdl-machine-translation-cloud/941/.
If you are interested in the upgrade plan, SDL sales reps can walk you through your options.