[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xliff-comment] xliff_core_2.1.sch: canDelete' attribute is set to 'no', but the corresponding element is missing in the sibling target.
Thanks Jan,
I’ll record the issue and look at it.
Cheers,
-yves
From: Ján Husarčík [mailto:jan.husarcik@gmail.com
]
Sent: Tuesday, November 15, 2016 4:39 AM
To: xliff-comment@lists.oasis-open.org
Subject: [xliff-comment] xliff_core_2.1.sch: canDelete' attribute is set to 'no', but the corresponding element is missing in the sibling target.
Hello,
a file
<?xml version="1.0" encoding="utf-8"?>
<xliff xmlns:mda="urn:oasis:names:tc:xliff:metadata:2.0" xmlns="urn:oasis:names:tc: xliff:document:2.0" srcLang="en-US" version="2.0" >
<file id="1">
<group id="content">
<unit id="1">
<segment>
<source>some <pc id="p1" canDelete="no">sentence</pc></source>
</segment>
</unit>
</group>
</file>
</xliff>passes XLIFF2.0 validation using Lynx.
When validated using xliff_core_2.1.sch (https://tools.oasis-open.org/
version-control/browse/wsvn/ ) an error "canDelete' attribute is set to 'no', but the corresponding element is missing in the sibling target." is reported.xliff/trunk/xliff-21/schemas/ xliff_core_2.1.sch Maybe the rule should check whether sibling <target> is defined first.
Regards,
Jan
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]