Description:
I noticed an issue regarding the categories of my post when importing my XLIFF 2.0 file in Matecat. Let's try to explain, I have a post in English with a category "News," translated into French as "Nouvelles" thanks to Polylang Pro (WordPress multilingual plugin).
For XLIFF 2.0, this French translation is properly recognized in the Poedit tool. However, it is not recognized in Matecat as translation. I have to manually create the French translation in Matecat.
This issue does not occur in Matecat when using XLIFF 1.2.
Here are the data in XLIFF 2.0 regarding the terms:
<group id="4" type="x:term" name="354">
<unit id="6" type="x:name">
<segment>
<source><![CDATA[News]]></source>
<target><![CDATA[Nouvelles]]></target>
</segment>
</unit>
</group>
And here are the data in XLIFF 1.2 regarding the same terms:
<group restype="x-term" resname="354">
<trans-unit id="6" restype="x-name">
<source><![CDATA[News]]></source>
<target><![CDATA[Nouvelles]]></target>
</trans-unit>
</group>
Are you aware of this kind of issue on your side?
Steps to reproduce the issue:
Here is how I encountered the issue:
- Using Polylang Pro, export an English post with the category term translated into French, for example, translate the English category "News" to French as "Nouvelles."
- Export this post in French, choosing the file format 2.0.
- Drop the generated file into Matecat.
- Navigate to the translation table => The term "Nouvelles" is missing from the French suggestion field.

Description:
I noticed an issue regarding the categories of my post when importing my XLIFF 2.0 file in Matecat. Let's try to explain, I have a post in English with a category "News," translated into French as "Nouvelles" thanks to Polylang Pro (WordPress multilingual plugin).
For XLIFF 2.0, this French translation is properly recognized in the Poedit tool. However, it is not recognized in Matecat as translation. I have to manually create the French translation in Matecat.
This issue does not occur in Matecat when using XLIFF 1.2.
Here are the data in XLIFF 2.0 regarding the terms:
And here are the data in XLIFF 1.2 regarding the same terms:
Are you aware of this kind of issue on your side?
Steps to reproduce the issue:
Here is how I encountered the issue: