Lynx - XLIFF files created with missing subFlowsEnd attribute and found Valid

[Archit Khanna]

1. I extracted a set of html files using python Scrapy.
2. These files were then extracted to xliff using Okapi Rainbow.
3. Files generated were then validated in Lynx and oXygen Editor 21.1
4. Lynx found the files to be valid, however oXygen stated 'the subFlowsStart and SubFlowsEnd attributes must be used in a pair' as an error. Files were validated against xliff_2_Advanced_Validation NVDL Schema from Oasis SVN.
5. File used is attached.
6. Link to NVDL Schema: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-21/schemas/xliff_2_advanced_validation.nvdl.

‌

[ysavourel]

It seems subFlowsStart would be used when a sub-flow exists in a start tag (like in <p> in HTML. And subFlowsEnd for sub-flows in ending code, which never exist in HTML. So I’m not sure I understand the validation error.

This probably need to be verified by the TC. I’ll ping them.

[ysavourel]

Reported at https://lists.oasis-open.org/archives/xliff-comment/201911/msg00000.html

[christian.preinesberger]

Issue #40 was marked as a duplicate of this issue.