You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For XLIFF 1.2 the XliffFileDumper correctly adds translation keys into the resname attribute, but does not populate the equivalent name attribute for XLIFF 2.0.
Although optional, the specification describes this as:
The original identifier of the resource corresponding to the Extracted <unit> or <group>.
For example: the key in the key/value pair in a Java properties file, the ID of a string in a Windows string table, the index value of an entry in a database table, etc.
For backward compatibility I don't expect to see a change to the way the <source> element is used, but for the 1.2 and 2.0 formats to be treated as equivalent it seems the same logic should be applied.
The text was updated successfully, but these errors were encountered:
For XLIFF 1.2 the
XliffFileDumper
correctly adds translation keys into theresname
attribute, but does not populate the equivalentname
attribute for XLIFF 2.0.Although optional, the specification describes this as:
For backward compatibility I don't expect to see a change to the way the
<source>
element is used, but for the 1.2 and 2.0 formats to be treated as equivalent it seems the same logic should be applied.The text was updated successfully, but these errors were encountered: