Title: Message
Some questions/observations:
[1] I didn't see
any indication as to whether the new attributes are mandatory or optional on the
<group> and <trans-unit>
elements.
[2] As
equivalent-translation is being set at the
<trans-unit> level, this seems to impose the setting
through all <alt-trans> elements. Is this a good
idea?
[3] Where did you
envisage the manipulation of the elements and attributes taking place? I don't
see how they can realastically be set by the original filter, unless it has
detailed linguistic knowledge or there's some information in the original file
type that can be used. Does this mean that it's the responsibility of the XLIFF
editor to change the DOM structure of the document? If so, I think this will
need to be documented in the specification.
[4] A minor
point, I know, but is it really necessary to have such long attribute names? As
XLIFF documents are potentially being sent to translators, this would seem to be
bloating the file size for someone who potentially is downloading with a modem
:-)
David Pooley
Software Architect
SDL
International
-----Original Message-----
From: Magnus Martikainen
[mailto:]
Sent: Tuesday, March 08, 2005 7:27
PM
To: xliff
Subject: [xliff] Proposal for Additional
Segmentation Support Attributes
Hi
all,
The segmentation
subcommittee has voted unequivocally to put forward the proposal detailed below to the main XLIFF
committee regarding two additional
attributes related to segmentation in XLIFF files.
I would hereby like
to request a formal review of the proposal by the XLIFF Committee for its
inclusion in the XLIFF draft specification.
The following
document explains the proposal and
details the proposed changes to the XLIFF specification:
http://www.oasis-open.org/apps/org/workgroup/xliff-seg/download.php/11725/seg-new-attributes.htm
Best
regards,
Magnus
Martikainen
on behalf of the
XLIFF Segmentation Subcommittee
