[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] Draft 10
-----Original Message-----Hi Yves and all:
From: Tony Jewtushenko [mailto:Tony.Jewtushenko@oracle.com]
Sent: Wed, March 12, 2003 10:06 PM
To: ysavourel@translate.com
Subject: Re: [xliff] Draft 10
I've noticed an inconstancy in the spec for the <g> inline elementhowever, later on in the same definition we're told:A
<g>
element can contain another<g>
element. In this case, if the embedded group has anid
attribute, it should never be moved outside of its parent group.Is it possible that the entire line was pulled from opentag and refers to the group tag, not the general placeholder tag? This line has beein in since at least the XLIFF 1.0 spec, but the entire statement doesn't make sense to me. Any insight? Or am I slowing going mad and in need of professional help?Required attributes:
id
.
Cheers
Tony Yves Savourel (RWS) wrote:
Hi everyone, The updated specification and schema (along with 2 sample XLF files) are attached. Notes: - We still have not voted on the value lists fo mtype, size-unit and unit. - There are still some definition missing for datatype, and other attributes. Please, make sure to have some ready soon. - The schema has been re-worked to allow easier use of the lists in the same attribute type (like for 'count-type'), I think all is ok, but double and triple check are more than welcome. - I still can get XMLSpy to validate the samples when there is text content after inline elements. But at this point I'm not sure what exactly XMLSpy supports. The samples validate with MS XML Validator (and do not validate when expected). cheers, -ys-- Tony Jewtushenko mailto:tony.jewtushenko@oracle.com Sr. Tools Program Manager direct tel: +353.1.8039080 Product Management - Tools Technology Team Oracle Corporation, Ireland
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]