MHonArc v2.5.2 -->
xliff message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: RE: [xliff] element 'defaults' proposal
I'm not sure about this proposal for the following reasons:
1) By putting this in, we will be sacrificing some level of validation
against the DTD/Schema. The example below is a case in point. The "maxwidth"
attribute (as I understand it) is numeric. There's no way to validate that
this is the case in the content of the <default> element.
2) Although such a mechanism is useful, I'm not sure that it's necessary.
All we are doing is providing a shorthand method for specifying default
values. The longhand method is simply to put the correct attribute values in
each element. Although this grows the size of the XLIFF file, is this a big
drawback right now?
3) The new element is also introducing an extra level of complexity in to
XLIFF, namely XPath. No doubt some tools will use "homegrown" parsers for
XLIFF which won't support XPath and so this will lengthen the adoption
period for 1.1.
David Pooley
Software Architect
SDL International