Hi Patrik,
At the top of my head I don’t think the example should be valid.
One could have a lone <sm/> or <em/> in a segment. But I don’t think it can be isolated like <sc/> or <ec/>.
I’ll try to see what is the code logic behind letting this to be valid in the Okapi library.
-ys
From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Patrik Mazanek
Sent: Thursday, December 17, 2015 6:50 AM
To: 'XLIFF Main List' <xliff@lists.oasis-open.org>
Subject: [xliff] <sm/> and <em/>
HI,
I wanted to ask about <sm/> and <em/> tags. In specification it is said that the marker can be created by using <mrk> tag pair , or the pair of <sm> and <em> elements. What it doesn’t say if you can have situation where only <sm/> or <em/> is present, e.g.:
<xliff xmlns="urn:oasis:names:tc:xliff:document:2.0" xmlns:fs="urn:oasis:names:tc:xliff:fs:2.0" xmlns:slr="urn:oasis:names:tc:xliff:sizerestriction:2.0" version="2.0" xml:space="preserve" srcLang="en-GB" trgLang="fr-FR">
<file id="f1" original="myfile">
<unit id="1">
<segment id="id1" >
<source>Example of an sm with <sm id="2" type="term"/> term</source>
</segment>
</unit>
</file>
</xliff>
It seems both Okapi validator and MS XLIFF OM validate the example above as valid file. If this is indeed correct I believe we should enhance the specification and make sure this bit is explained a bit better.
Regards
Patrik Mazanek l Product Owner – Translation productivity l SDL l Language Technologies Division l (T) +49 (0)1520 9098850 l (F) +49 711 780 4197
SDL PLC confidential, all rights reserved. If you are not the intended recipient of this mail SDL requests and requires that you delete it without acting upon or copying any of its contents, and we further request that you advise us. |
This message has been scanned for malware by Websense. www.websense.com