protect text in xml translation project

Question

Hi there, i have to adapt the filetype of an existing Project Type in WorldServer. The actual implemented state is, that there are xml files to be translated which can contain html-tags. The filetype used is xml v 1.3.0.5 and also Embedded Content Plain Text. I am using Trados Studio 2021 for the changes. The following needs to be adapted 1. text which is in curly brackets needs to be protected from translation e.g. "Zum Beispiel {model.trunkCapacity} " 2. for xml-elements which have certain attribute (anchor, itemLink, linkURL, modelCode, path, sling:alias) the text needs to be protected from translation 3. for xml-elements which have certain attributes (navTitle, jcr:description) the text needs to be colored I have done following changes in Trados Studio to implement the changes 1. protected text in curly brackets: I created a placeholder in the inline-tags for the embedded content, in the placeholder i entered a regular expression which should cover all text in curly brackets. When i preview in Trados Studio the curly brackets are not protected....what am i doing wrong here? 2. protected text for xml-elements with certain attributes: I created a parser rule for the file type (for tests only for the anchor attribute) and set it to not translatable. This works but the problem is that the text is therefore not shown in the preview, he is removed completely. This is not what is needed, the text needs to be shown but only protected...what am i doing wrong here? 3. differently colored text for certain xml-elements: i created a parser rule and set the formating to a different color, this works as intended, so no questions here. i have attached a example xml-file with which i tested the changes Fullscreen 0741.test.xml Download Modell: Modelle, technische Daten und Preise neues Modell Alle Highlights des neuen Modells: Modelle, Ausstattung, technische Daten, Preise und Services. Jetzt entdecken und konfigurieren. Modell: Überblick Test Modell false Zum Beispiel {model.trunkCapacity} l(1) Kofferraumvolumen, in denen von Fahrrad bis Kinderwagen alles Raum findet. Ein großzügiges Interieur, in dem Sie auch auf Langstrecken komfortabel reisen. Digitale Highlights wie das große, geschwungene BMW Curved Display. Und sportliche {model.Power} kW ({model.horsePower} PS)(1), die jeden Tag noch aufregender machen. Entdecken Sie seine Modellvarianten, Ausstattungsoptionen und technische Daten sowie vielfältige Leasing- und Finanzierungsmöglichkeiten. Can someone help me with the first two points, i dont know how to solve this. Any help is greatly appreciated, thanks in advance

Paul · Answer

Markus Herkommer 
 Markus Herkommer said: i have to adapt the filetype of an existing Project Type in WorldServer. 
 If this is a file coming from Worldserver it will be an XLIFF and not anything else. You can only make changes to the filetype in Worldserver, not Studio.

Paul · Answer

Markus Herkommer 
 ok - I don't have 1.3.0.5, so I guess this is something you got from Worldserver perhaps? I'm not familiar with that at all. So I used the 1.2 (legacy embedded) version after I installed Trados Studio 2021: 
 
 It's working for me as you intended I think. So I put t my settings file here: MH_v1.zip 
 The only things I can think might be affecting you based on what you have shared so far are these: 
 
 in the advanced settings you need to make sure your segmentation hint is set to "include" otherwise that segment will be excluded altogether 
 in the embedded content part... perhaps your other rules are interfering? I don't have your rules so can't check that one

Trados Studio > 1. Trados Studio

protect text in xml translation project