AI Professional does not respect tags in source elements despite appropriate config options?

Question

I switched from "Open AI translator" to "AI Professional". Now I ran into several situations where the tags of the source text is not respected by AI Professional (whereas both NM I use, DeepL and Language Weaver work as expected). My current version of AIP is 1.0.1.2 (from February 1st), but the effect was there in the previous version as well. Here example 1: 
 And example 2: 
 I checked the appropriate option in the AIP config (gpt-3.5-turbo shows the same problem, btw, as expected):

Patrick Andrew Hartnett · Answer

Hi Jens Olaf Koch , I confirm that there was a bug that prevented the plugin from recognizing locked tags. We worked on this with priority over the weekend and released a new version to resolve this problem. The latest release is already available from the Integrated AppStore in Trados Studio or directly from the AppStore webpage. 
 We value your feedback and suggestions, all aimed at enhancing our offering. I would encourage you to submit these innovative ideas to AppStore Ideas . This platform allows us to systematically track and address all feedback, which is important in our commitment to continuous improvement. 
 I can share with you that some of the features you suggested are already on our backlog and scheduled for release in the near future. For example, as you mentioned here, a general assistant prompt & the ability to include additional context such as previous & next segments. We are also exploring more advanced features, and will provide updates on these developments in due course. 
 As for the query on our approach to communicating tags to AI technology, we follow an agnostic strategy. This involves simplifying the information that needs to be interpreted by the NLP, focusing only on the tag type and their position within the content. Our initial results have reinforced this approach. 
 Regarding your question on the preference of Translation Providers and sequence/order. I'm not a linguist, so probably not the right person to answer your question. Anyone care to follow up here?

Patrick Andrew Hartnett · Answer

Hi Jens Olaf Koch , 
 Thank you for this feedback. This might a bug with the TM provider in how the locked tags are interpreted; I'll need to confirm and then circle back. 
 If your prompt is instructing the AI technology to refine an existing translation & it does not contain tags (regardless of whether the source contains tags or not), then, the translation suggestion from AI will not contain tags, as it will use the existing translation as the basis for the request. Having said that, occasionally, during my initial investigations/ tests, OpenAI simply ignored instructions to include tags in the translation suggestion. We need to keep in mind that this is AI technology. OpenAI's GPT models, including gpt-3.5-turbo and gpt-4, are powered by machine learning and do their best to understand and respond appropriately to the prompts given to it. However, understanding HTML-like tags, can occasionally be challenging for these models. The models are trained on a diverse range of internet texts, but they do not know specifically which documents were in their training set or have access to any proprietary databases. Therefore, they could sometimes overlook or misunderstand complex inputs, like tags. Addtionally, each model may behave a bit differently due to refinements and updates included in newer versions. GPT-4 may present improvements over gpt-3.5-turbo in recognizing and correctly handling these tags, but no model is perfect and occasionally either could miss the tags.

RWS AppStore > 2. RWS AppStore Applications

AI Professional does not respect tags in source elements despite appropriate config options?

Top Replies