Due to essential maintenance, access to Trados cloud will be unavailable on Saturday 30 August from 00:00 to 12:00 UTC.
  • State Suggested Answer
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 434 subscribers
  • Views 119 views
  • Users 0 members are here
Options
Related

Placeholders at the beginning of a segment not showing

Pelle Persson

When opening an XML file in Trados Studio 2019 SR2, any tags in the beginning of a segment are not shown in the editor.

Example:

In the segment below, the 3 ph tags starting the segment are removed, and only the word "auswählen is shown.

<seg mid="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" isContextMatched="False" translate="yes">
<ph ctype="x-unknownattribute" gt:class="standard" gt:display-text="v-ref" gt:leftedge="round" gt:rightedge="angle" gt:type="start" gt:style="nonxlatable" gt:payload="<v-ref y.io.id="f08a2ecef001936dac1c0c0577f30e9a" y.io.version="1" y.io.language="de" y.io.variant="DE" y.io.type="swtext" y.reftype="textvar" y.id="ID_363ff717f90c11efb700bbd697ec6001" y.ref.io.types="swtext" translate="no" y.target.language="da" y.target.variant="DK" y.target.content="Parametre">" id="gt_cca9279e-4bc9-4ead-bb99-24aeb84e9dec" gt:desc="<ut Type="start" Style="nonxlatable" RightEdge="angle" DisplayText="v-ref">&lt;v-ref y.io.id="f08a2ecef001936dac1c0c0577f30e9a" y.io.version="1" y.io.language="de" y.io.variant="DE" y.io.type="swtext" y.reftype="textvar" y.id="ID_363ff717f90c11efb700bbd697ec6001" y.ref.io.types="swtext" translate="no" y.target.language="da" y.target.variant="DK" y.target.content="Parametre"&gt;</ut>"/>
<ph ctype="x-unknownattribute" gt:class="standard" gt:display-text="Parameter" gt:leftedge="split" gt:rightedge="split" gt:type="standalone" gt:style="nonxlatable" gt:payload="Parameter" id="gt_0168bdb6-8f47-4b82-b863-240f65c4dc0d" gt:desc="<ut Style="nonxlatable" LeftEdge="split" RightEdge="split" DisplayText="Parameter">Parameter</ut>"/>
<ph ctype="x-unknownattribute" gt:class="standard" gt:display-text="v-ref" gt:leftedge="angle" gt:rightedge="round" gt:type="end" gt:style="nonxlatable" gt:payload="</v-ref>" id="gt_74cd0beb-b16d-4d8f-bbfe-9b957ffa7c60" gt:desc="<ut Type="end" Style="nonxlatable" LeftEdge="angle" DisplayText="v-ref">&lt;/v-ref&gt;</ut>"/>
auswählen
</seg>
I've tried updating settings under View -> Options, and under File -> Options -> Editor -> Formatting display style, but no change. Since changing the settings doesn't have any effekt, I'm assuming that this happens during the parsing.
emoji
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • 0

     

    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.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
  • 0 in reply to Paul

    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. 
    emoji
  • 0 in reply to 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.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
Reply
  • 0 in reply to 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.

    Paul Filkin | RWS Group

    ________________________
    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

    emoji
Children
No Data