I’ve noticed 3 issues (at least I think they are issues) in the example file before getting to one on the <item> element that
I was expecting since my build of Lynx doesn’t have your SD file included yet.
1) Issue with subFlowStart:
In <mtc:match ref="#m76"> there is a <target> with a code <pc id="2"> that has subFlowStart="", which I believe is not allowed
by the schema.
2) Issue with xml:lang:
The <xliff> element has a xml:lang="en" attribute.
But the target language of the file is ‘de’ and the <target> elements do not overwrite the xml:lang of the <xliff>, therefore
they are inherited and set to "en" instead of "de". The solution is to either remove the xml:lang in <xliff> or add xml:lang in the <target> elements.
3) Issue with <originalData>:
Several <mtc:match> elements have inline codes. But they have no corresponding <originalData>.
The <originalData> is only stored at the <unit> level, while according to the specification, <mtc:match> has its own <originalData>.
I hope that feedback helps,
Dear Committee Members
This is to deliver my
action item with regards to my
proposal to allow storage of inline markup along with the text content of
<source /> and
<target /> elements within Change Tracking
<item /> elements.
I attach the following in this email:
Sample XLIFF file (adapted from one in Bryan’s book).
Modified change_tracking.xsd. The main modification to this file is to insert an
<xs:group /> element within the definition of the
<item /> element which references back to XLIFF Core
<inline /> element group.
Proposed new text for the description of the
<item /> element in the specification.
I have validated my attached
punk-bands-ctr-with-inline.xlf by updating the XLIFF 2.0 schema hierarchy with my attached
change_tracking.xsd and validating with XMLSpy.
I hope we can discuss this at the next TC meeting on 16/8.
Vistatec Ltd. Registered in Ireland 268483.
Registered Office, Vistatec House, 700, South Circular Road, Kilmainham. Dublin 8. Ireland.
The information contained in this message, including any accompanying documents, is confidential and is intended only for the addressee(s). The unauthorized use, disclosure, copying, or alteration of this message is strictly forbidden. If you have received
this message in error please notify the sender immediately.