Hi Kevin,

I appreciate the quick response and will try setting this.

Is there a way to determine what element (line number or content) that's throwing the following error?

The value for DataReferenceEnd (d2) does not refer to a valid Data element.

The stack trace was not helpful and I scanned through every dataRefEnd="d2" and <data id="d2"> element but saw no malformed tag.

EDIT: As a follow-up I found the issue. The translation company copy/pasted without double-checking their work and there were <pc/> elements in the <target/> tag that didn't exist in the <source/> elements.

--Brian

Hi Brian,

yeah there appears to be a lot missing from the orginalData section in that segment - do you happen to have the original file that was sent to the translator - it might be that the translator's processes removed them :( (i don't think the copy of <source> to <target> changes that bit of the file.

Hey Kevin,

Here is the original <unit/> element from the file provided to the translators:

<unit id="u183-2" name="p">
  <originalData>
    <data id="d1">&lt;br/&gt;</data>
  </originalData>
  <segment>
    <source>Glass<ph dataRef="d1" id="1" subType="xlf:lb" type="fmt" />100 Red Drive<ph dataRef="d1" id="2" subType="xlf:lb" type="fmt" />Chester, MO 12345<ph dataRef="d1" id="3" subType="xlf:lb" type="fmt" />(123) 987.6543<ph dataRef="d1" id="4" subType="xlf:lb" type="fmt" />(111) 123.1234</source>
  </segment>
</unit>

I can send you the original and translated files if you want to look at them. What's the best way to get them to you?

Thanks again for the support.

--Brian

Hi Brian,

Yeah if you could send us the file [email protected] .

the segment above on its own seems to to work for me, so maybe something else in the file is having knock on effects.

Kevin

Hey Kevin,

I emailed both of the files to you.

Take care.

--Brian

Hey Kevin,

I upgraded our version from 8.2.5 to 8.2.8 and the fix worked very well. Thank you for the quick turnaround on this update.

Something that seems off is how links are handled in <target> tags.

I'm not sure if this has to do with the Overwrite Blank Targets setting or not but when importing a link through the originalData tag the imported translated content is converted to Localization.Xliff.OM.Core.SpanningCode.

The following tags from the translated file do not import correctly and replace the <target> content with Localization.Xliff.OM.Core.SpanningCode.

<unit id="u4-3" name="p">
  <originalData>
    <data id="d1">&lt;a href="/{localLink:umb://document/d9f9db91d4be44ec8a13ad02a3038944}" title="Glass" class="white-button"&gt;</data>
    <data id="d2">&lt;/a&gt;</data>
  </originalData>
  <segment>
    <source><pc dataRefEnd="d2" dataRefStart="d1" id="1" type="link">GET SAMPLES</pc></source>
    <target><pc dataRefEnd="d2" dataRefStart="d1" id="1" type="link">OBTENER MUESTRAS</pc></target>
  </segment>
</unit>

However, when using the metaGroup tag to define links then it imports correctly and unaltered.

The following tags from the translated file import correctly:

<unit id="u233-1-13" name="a">
  <mda:metadata>
    <mda:metaGroup id="a_attributes">
      <mda:meta type="href">/{localLink:umb://document/c7a8768051654c5eb394758352f8a369}</mda:meta>
      <mda:meta type="title">Network</mda:meta>
    </mda:metaGroup>
  </mda:metadata>
  <segment>
    <source>&lt;em&gt;Network&lt;/em&gt;</source>
    <target>&lt;em&gt;Red&lt;/em&gt;</target>
  </segment>
</unit>

We've gone through and manually updated the links impacted by this throughout the site so this is more of a bug report than a request for help but I felt it was important to let you know.

Again, your quick response and package update was greatly appreciated and allowed us to finish the last steps of our site build.

Take care.

--Brian