Pelle Persson 

Can you explain why you want to see these tags?  From your snippet it looks like a TMX, but maybe not, and as far as I can see the only benefit of seeing the tags... would be to see the word "Parameter"  within the second tag, but still not translatable.  There is only one translatable piece of content in there - "auswählen".  Maybe "Parameter" gives you some context you need... I don't know!

So what's the reason for seeing all the detail hidden in there?  It almost certainly should not be translated.  Maybe worth clarifying with your client what they actually need you to deliver here.

Hi Paul,

Thanks for taking the time to answer.  I need the initial tag because of the different properties of the source language DE and the target DA. In German, the verbs go after the subject, e.g. "<tag> löschen" but that needs to go before the subject in Danish "Slet <tag>" (or in English for that matter: "Delete <tag>".)  Without the tag present, translating isn't possible without compromising quality and native feel. 

Hi Paul,

Thanks for taking the time to answer.  I need the initial tag because of the different properties of the source language DE and the target DA. In German, the verbs go after the subject, e.g. "<tag> löschen" but that needs to go before the subject in Danish "Slet <tag>" (or in English for that matter: "Delete <tag>".)  Without the tag present, translating isn't possible without compromising quality and native feel. 

Pelle Persson 

Well... in the example you provided there is only one word so I doubt it matters at all.  If you can provide a proper sample showing the complete structure of the file you are handling, including content where this distinction matters, it would help you get a better reply... especially since this seems to be something you have not meddled with before.

ok - so in this case you 100% need a custom xml filetype to handle the file, but if you are handling this as a bilingual file that may be tricky... unless the target has not been translated yet?

I think if a custom xml is the way forward I'd use a stylesheet rather than the tags for that information so you have a preview that clearly contains what you need to know.

Hi, sorry to step in here, as I do not see a solution in the answers so far. If this issue is solved already, then ignore my message.

I think, the example with "<tag> löschen" and "Delete <tag>" makes clear, where the problem is.

As the front tag is not shown in Studio, the translator only sees "löschen" in that segment and translates this with "delete".

When you then create the target version, the hidden tag is placed again in the front of the segment. So the translation then will be "<tag> delete", wich is incorrect English.

The problem goes back to the settings in the xml file, when the Studio project is created, during parsing of the file (your assumption is correct). So if the client is providing you with a Studio project, you cannot change that anymore.

In the settings of the clients XML file type, this specific tag needs to get a property, that says, that it may not be removed during the parsing process. You do this in your XML file type definition, under Parser, there you have to change the Tag Type option from Structure to Inline, and then in the Segmentation hint box, you select Include. Then this tag will always be included in your segment, no matter where its position in the segment.

Hope that helps,

Johannes

Johannes Purer 

Indeed... but we still don't know whether this is a bilingual file or not (it looks like one) and whether it's translated at all or not.  Hence the reason I asked for a sample file.  But you are correct, it is a settings issue.