You are currently working on UAT 

  • State Verified Answer
  • Replies 2 replies
  • Subscribers 429 subscribers
  • Views 1086 views
  • Users 0 members are here
Options
Related

"x-ContextContent" produces invalid XML in SDL Trados Studio 2017 SR1 14-1-10015.44945

Michael Bauer

Collaborating with translators who are on MemoQ, we've run into a snag sharing TMs because the "x-ContextContent" attribute is not a valid XML attribute.

For example:

<tu creationdate="20190506T121536Z" creationid="ABC\DEF" changedate="20190506T121541Z" changeid="ABC\DEF" lastusagedate="20190506T121541Z">
      <prop type="x-LastUsedBy">ABC\DEF</prop>
      <prop type="x-Context">3378625255402972, -4457987119356656726</prop>
      <prop type="x-ContextContent">Request files |  | Iarr faidhlichean | </prop>
      <prop type="x-Origin">TM</prop>
      <prop type="x-ConfirmationLevel">Translated</prop>
      <prop type="x-StructureContext:MultipleString">x-tm-table-cell</prop>
      <tuv xml:lang="en-US">
        <seg>Here's the link people can use to upload files</seg>
      </tuv>
      <tuv xml:lang="gd-GB">
        <seg>Seo an ceangal a chleachdas daoine airson faidhlichean a luchdadh suas</seg>
      </tuv>
    </tu>

The character "|" is not allowed in XML attributes. Also, the context information can get longer than 254 characters, which is not allowed. A Text node with CDATA should be used for this.

We also filed a ticket with MemoQ to see if they can hack around this on their end, but it's really not their issue.
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
Parents
  • +1

    Michael Bauer said:
    we've run into a snag sharing TMs because the "x-ContextContent" attribute is not a valid XML attribute.

    Why not?  The attribute is actually type, x-ContextContent is just the value.  The TMX specification says this:

    It is the responsibility of each tool provider to publish the types and values of the properties it uses. If the tool exports unpublished properties types, their values should begin with the prefix "x-".

    So in my opinion there is nothing wrong with this at all.  If memoQ cannot read the TMX because of this then this is a bug in memoQ, not Studio.  They should be able to ignore anything they don't recognise and can't use.

    Michael Bauer said:
    The character "|" is not allowed in XML attributes.

    This character is not in the attribute at all.  It's simply text in the prop element.  The TMX specification says:

    As your tool is fully responsible for handling the content of a <prop> element you can use it in any way you wish. For example the content can be a list of instructions your tool can parse, not only a simple text.

    So why is this a bug in Studio?  I don't believe this requires a hack on their end, it just requires them to be able to handle a TMX.  If the pipe symbol was in the attribute name then it would be a problem.  But this is not the case here.

    Paul Filkin | RWS

    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

Reply
  • +1

    Michael Bauer said:
    we've run into a snag sharing TMs because the "x-ContextContent" attribute is not a valid XML attribute.

    Why not?  The attribute is actually type, x-ContextContent is just the value.  The TMX specification says this:

    It is the responsibility of each tool provider to publish the types and values of the properties it uses. If the tool exports unpublished properties types, their values should begin with the prefix "x-".

    So in my opinion there is nothing wrong with this at all.  If memoQ cannot read the TMX because of this then this is a bug in memoQ, not Studio.  They should be able to ignore anything they don't recognise and can't use.

    Michael Bauer said:
    The character "|" is not allowed in XML attributes.

    This character is not in the attribute at all.  It's simply text in the prop element.  The TMX specification says:

    As your tool is fully responsible for handling the content of a <prop> element you can use it in any way you wish. For example the content can be a list of instructions your tool can parse, not only a simple text.

    So why is this a bug in Studio?  I don't believe this requires a hack on their end, it just requires them to be able to handle a TMX.  If the pipe symbol was in the attribute name then it would be a problem.  But this is not the case here.

    Paul Filkin | RWS

    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

Children