If you’re looking to store localization data and propagate it through your localization pipeline allowing tools to interoperate then you may want to use the XLIFF 2.0 object model. The XLIFF 2.0 object model implements the OASIS Standard for the XLIFF 2.0 specification as defined at http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html.
Other
86
stars
26
forks
source link
The validator should validate ref attributes on <sm/> tags which do not contain note #6
Currently if we use the ref attribute on the tag, we can only set reference to notes as value of that attribute, irrelevant of the type of the . However, this is true only in the case of the comment type. In the case of term or custom types, the ref attribute can have other values than reference to notes.
As an example, the following snippet should be valid:
<sm id="m1" translate="yes" type="term" ref="http://dbpedia.org/page/Doppelgänger"/>marked span start<em startRef=”m1”/>
Currently if we use the ref attribute on the tag, we can only set reference to notes as value of that attribute, irrelevant of the type of the . However, this is true only in the case of the comment type. In the case of term or custom types, the ref attribute can have other values than reference to notes.
As an example, the following snippet should be valid:
<sm id="m1" translate="yes" type="term" ref="http://dbpedia.org/page/Doppelgänger"/>marked span start<em startRef=”m1”/>