OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Cloning of <g> elements

Hi all,


Following a discussion in the segmentation subcommittee today I took an action item to post a question to the main XLIFF committee requesting a clarification on how cloning of <g> elements should work.


As you may be aware, the <g> element has an optional attribute named clone, with a default value “yes”. This implies that all <g> elements that do not have an explicit clone=”no” attribute value may be cloned by any tool processing the XLIFF content.


This functionality is of special interest to the segmentation subcommittee, and our current work-in-progress proposal for representation of segments relies on the ability to clone <g> elements that span segment boundaries in order to be able to introduce segments.


For these reasons I would like to have the following assumptions confirmed:

a)       When a <g> element is cloned, all attribute values of the original <g> element, including the id and xid values, are replicated into the clone.



<source>Some <g id=”1” ctype=”bold” xid=”42” ts=”offset:983”>marked-up</g> text.</source>

<target>Some <g id=”1” ctype=”bold” xid=”42” ts=”offset:983”>translated</g> marked-up <g id=”1” ctype=”bold” xid=”42” ts=”offset:983”>text</g>.</target>



b)      The current specification mentions that multiple copies of the source <g> element may be placed in the <target> content. For segmentation purposes we would also need to clone them inside <source>. Would this be a reasonable extension?


Whatever the outcome I would suggest that we update the XLIFF 1.1 specification to clarify how this mechanism is intended to work.


Best regards,

Magnus Martikainen

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]