Hi all,
Regarding point 5) below I would like to
clarify that the segmentation markup is entirely optional and does not affect
the functionality of the files as XLIFF files. The filter will ignore the
segment boundaries when back-converting to the native format, and thus the
entire content of the <target> element will be used, including content
appearing outside of segments.
The segmentation markup is intended for
tools such as translation memories to optimize recycling of previously
translated content, and as such it often makes more sense to not include spaces
between sentences in the segments (though that is entirely up to the tools). This
does not in any way prevent users from editing the content between the
segments, removing spaces or adding additional ones as needed. In fact it is
fully allowed (and may frequently happen) that only part of the translated content
in the <target> element is part of segments.
The example in point 5) attempts to
explicitly show this by not including the space characters in the segments (which
normally gives better re-use when applying a TM). Perhaps we need to clarify
the text in the specification to make that more explicit?
Cheers,
Magnus
I've revised the spec to address the issues raised by Rudolfo,
although three issues remain open as they require additional input from the
TC. I've also corrected a couple of minor problems with the spec HTML in
order to certify spec as HTML 4.01 compliant. And additionally, the spec
includes a number of minor corrections to typos as was kindly reported by
Asgeir Frimannsson.
Asgeir also flagged a minor issue with the XSD's that will require a
revision, so the spec distribution package will need to be reissued once
fixed documents are produced.
Below are the original emails and actions taken. I would
appreciate feedback on the remaining open issues as we need to close these
issues down by the end of the week in order to complete any required revisions
before Tuesday's TC teleconference.