[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (XLIFF-11) Enforce <target> existence based on segment state
David Filip created XLIFF-11: -------------------------------- Summary: Enforce <target> existence based on segment state Key: XLIFF-11 URL: https://issues.oasis-open.org/browse/XLIFF-11 Project: OASIS XML Localisation Interchange File Format (XLIFF) TC Issue Type: Improvement Components: other Affects Versions: 2.1_csprd01 Environment: https://lists.oasis-open.org/archives/xliff-comment/201611/msg00003.html Reporter: David Filip Assignee: David Filip Priority: Minor Fix For: 2.1_csprd02 FROM: Ján Husarčík <jan.husarcik@gmail.com> 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" trgLang="fr-FR" version="2.0"> <file id="1"> <group id="content"> <unit id="1"> <segment state="final"> <source>1</source> </segment> </unit> </group> </file> </xliff> is reported as valid with state="final", while the <target> is not present. Could you please consider enforcing existence of <target> (even if it's empty) for segment states different from default? If you decide to do so, could you please update processing requirements in http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.html#contentmodification accordingly, and reference them (at least) in http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.html#state and http://docs.oasis-open.org/xliff/xliff-core/v2.1/csprd01/xliff-core-v2.1-csprd01.html#target -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]