Is there a way to capture positional tabs in a segmentation rule?

I noticed that Studio 2017 differentiates between normal tabs and "positional tabs", which are AFAIK are normal tabs with additional properties (see https://msdn.microsoft.com/en-us/library/documentformat.openxml.wordprocessing.positionaltab.aspx).

Apparently they are not captured by a Tab rule (eg. .\t+.). Can they be captured? How?

Cheers
Angela

Parents
  • Hi ,

    Can we see a small document with these in?

    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

  • Hi Paul,

    thanks for looking into this.

    I cannot share the original document with you but will try to fix up an obfuscated version if required.

    For now this should suffice:

    • I recently upgraded to MS Office 2016 and updated SDL Trados 2017 to SR1. I only noticed "positional tabs" after this.
    • So far I saw it only in documents of 1 client (a large EU body who probably generates its docs automatically from a db)
    • I just noticed that it only happens with the WordprocessingML v. 2 importer (2007-2016) and not with Word 2007 v 2.0.0.0 (2007-2013). I might have used the latter exclusively before the update.
    • The relevant generated sdlxliff for one of the affected tu looks like this:
      <trans-unit id="07ef7ff8-1ce6-4442-aa08-7fc170374b21"><source><x id="7"/><x id="8"/>PROVISIONAL TEXT OF 14/03/2018</source><seg-source><mrk mtype="seg" mid="3"><x id="7"/><x id="8"/>PROVISIONAL TEXT OF 14/03/2018</mrk></seg-source><target> ...

      where tags 7 and 8 are ( is the positionaltab):
      <tag id="7"><ph name="42" word-end="false" seg-hint="IncludeWithText">&lt;field name=&quot;Page&quot; value=&quot;42&quot;/&gt;</ph><props><value key="FieldTagId">7</value><value key="HasNonTranslatableTypeSection">False</value><value key="FieldType">PAGE</value><value key="ComplexFieldStartSection">&lt;w:r&gt;&lt;w:fldChar w:fldCharType=&quot;begin&quot;/&gt;&lt;/w:r&gt;&lt;w:r&gt;&lt;w:instrText xml:space=&quot;preserve&quot;&gt; PAGE  \* Arabic \* MERGEFORMAT &lt;/w:instrText&gt;&lt;/w:r&gt;&lt;w:r&gt;&lt;w:fldChar w:fldCharType=&quot;separate&quot;/&gt;&lt;/w:r&gt;</value><value key="TagType">Field</value><value key="ComplexFieldEndSection">&lt;w:r w:rsidR=&quot;00891EBC&quot; w:rsidRPr=&quot;00891EBC&quot;&gt;&lt;w:rPr&gt;&lt;w:rStyle w:val=&quot;FooterCharacterStyle&quot;/&gt;&lt;w:noProof/&gt;&lt;/w:rPr&gt;&lt;w:t&gt;42&lt;/w:t&gt;&lt;/w:r&gt;&lt;w:r&gt;&lt;w:rPr&gt;&lt;w:rStyle w:val=&quot;FooterCharacterStyle&quot;/&gt;&lt;w:noProof/&gt;&lt;/w:rPr&gt;&lt;w:fldChar w:fldCharType=&quot;end&quot;/&gt;&lt;/w:r&gt;</value></props></tag>
      <tag id="8"><ph name="pos tab" word-end="false" seg-hint="IncludeWithText">&lt;positionaltab/&gt;</ph><props><value key="&lt;positionaltab/&gt;">&lt;w:ptab w:relativeTo=&quot;margin&quot; w:alignment=&quot;center&quot; w:leader=&quot;none&quot;/&gt;</value></props></tag>


      and the document xml where it comes from is (it's actually in the 1st footer):
      <w:p w:rsidR="003B147B" w:rsidRDefault="003B147B"><w:pPr><w:pStyle w:val="Footer"/></w:pPr><w:r><w:fldChar w:fldCharType="begin"/></w:r><w:r><w:instrText xml:space="preserve"> PAGE  \* Arabic \* MERGEFORMAT </w:instrText></w:r><w:r><w:fldChar w:fldCharType="separate"/></w:r><w:r w:rsidR="00891EBC" w:rsidRPr="00891EBC"><w:rPr><w:rStyle w:val="FooterCharacterStyle"/><w:noProof/></w:rPr><w:t>42</w:t></w:r><w:r><w:rPr><w:rStyle w:val="FooterCharacterStyle"/><w:noProof/></w:rPr><w:fldChar w:fldCharType="end"/></w:r><w:r><w:ptab w:relativeTo="margin" w:alignment="center" w:leader="none"/></w:r><w:r><w:t xml:space="preserve">PROVISIONAL TEXT OF </w:t></w:r><w:r w:rsidR="005A096E"><w:t>14/03/2018</w:t></w:r></w:p>

    From what I can see it is the run with the tab (in blue bold) which is rendered as the "positional tab".

    Kind regards
    Angela

Reply
  • Hi Paul,

    thanks for looking into this.

    I cannot share the original document with you but will try to fix up an obfuscated version if required.

    For now this should suffice:

    • I recently upgraded to MS Office 2016 and updated SDL Trados 2017 to SR1. I only noticed "positional tabs" after this.
    • So far I saw it only in documents of 1 client (a large EU body who probably generates its docs automatically from a db)
    • I just noticed that it only happens with the WordprocessingML v. 2 importer (2007-2016) and not with Word 2007 v 2.0.0.0 (2007-2013). I might have used the latter exclusively before the update.
    • The relevant generated sdlxliff for one of the affected tu looks like this:
      <trans-unit id="07ef7ff8-1ce6-4442-aa08-7fc170374b21"><source><x id="7"/><x id="8"/>PROVISIONAL TEXT OF 14/03/2018</source><seg-source><mrk mtype="seg" mid="3"><x id="7"/><x id="8"/>PROVISIONAL TEXT OF 14/03/2018</mrk></seg-source><target> ...

      where tags 7 and 8 are ( is the positionaltab):
      <tag id="7"><ph name="42" word-end="false" seg-hint="IncludeWithText">&lt;field name=&quot;Page&quot; value=&quot;42&quot;/&gt;</ph><props><value key="FieldTagId">7</value><value key="HasNonTranslatableTypeSection">False</value><value key="FieldType">PAGE</value><value key="ComplexFieldStartSection">&lt;w:r&gt;&lt;w:fldChar w:fldCharType=&quot;begin&quot;/&gt;&lt;/w:r&gt;&lt;w:r&gt;&lt;w:instrText xml:space=&quot;preserve&quot;&gt; PAGE  \* Arabic \* MERGEFORMAT &lt;/w:instrText&gt;&lt;/w:r&gt;&lt;w:r&gt;&lt;w:fldChar w:fldCharType=&quot;separate&quot;/&gt;&lt;/w:r&gt;</value><value key="TagType">Field</value><value key="ComplexFieldEndSection">&lt;w:r w:rsidR=&quot;00891EBC&quot; w:rsidRPr=&quot;00891EBC&quot;&gt;&lt;w:rPr&gt;&lt;w:rStyle w:val=&quot;FooterCharacterStyle&quot;/&gt;&lt;w:noProof/&gt;&lt;/w:rPr&gt;&lt;w:t&gt;42&lt;/w:t&gt;&lt;/w:r&gt;&lt;w:r&gt;&lt;w:rPr&gt;&lt;w:rStyle w:val=&quot;FooterCharacterStyle&quot;/&gt;&lt;w:noProof/&gt;&lt;/w:rPr&gt;&lt;w:fldChar w:fldCharType=&quot;end&quot;/&gt;&lt;/w:r&gt;</value></props></tag>
      <tag id="8"><ph name="pos tab" word-end="false" seg-hint="IncludeWithText">&lt;positionaltab/&gt;</ph><props><value key="&lt;positionaltab/&gt;">&lt;w:ptab w:relativeTo=&quot;margin&quot; w:alignment=&quot;center&quot; w:leader=&quot;none&quot;/&gt;</value></props></tag>


      and the document xml where it comes from is (it's actually in the 1st footer):
      <w:p w:rsidR="003B147B" w:rsidRDefault="003B147B"><w:pPr><w:pStyle w:val="Footer"/></w:pPr><w:r><w:fldChar w:fldCharType="begin"/></w:r><w:r><w:instrText xml:space="preserve"> PAGE  \* Arabic \* MERGEFORMAT </w:instrText></w:r><w:r><w:fldChar w:fldCharType="separate"/></w:r><w:r w:rsidR="00891EBC" w:rsidRPr="00891EBC"><w:rPr><w:rStyle w:val="FooterCharacterStyle"/><w:noProof/></w:rPr><w:t>42</w:t></w:r><w:r><w:rPr><w:rStyle w:val="FooterCharacterStyle"/><w:noProof/></w:rPr><w:fldChar w:fldCharType="end"/></w:r><w:r><w:ptab w:relativeTo="margin" w:alignment="center" w:leader="none"/></w:r><w:r><w:t xml:space="preserve">PROVISIONAL TEXT OF </w:t></w:r><w:r w:rsidR="005A096E"><w:t>14/03/2018</w:t></w:r></w:p>

    From what I can see it is the run with the tab (in blue bold) which is rendered as the "positional tab".

    Kind regards
    Angela

Children