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: Whitespace handling in <data>

Hi all,

At the last meeting Rodolfo noted that we may have an issue with the way we define whitespace handling currently in some elements.

The issue is the first processing expectation of section 2.6.5 "White Spaces":

"• For the elements <sc>, <ec>, <ph> and <data>: The white spaces of their content must be preserved in all cases, even if the value for xml:space is set or inherited as default."

First we need to update this because now <sc>, <ec>, <ph> do not have any content any more. This is only valid for <data>.
The idea was that when the value of xml:space is default, XLIFF explicitly define that it should be preserved in the specification.

But Rodolfo has a good point, it is probably not the best way to do it.

Could we define <data> with xml:space='preserve' as a default and unchangeable attribute?
Maybe the following would work?

  <xs:element name="data">
    <xs:complexType mixed="true">
        <xs:element minOccurs="0" maxOccurs="unbounded" ref="xlf:cp"/>
      <xs:attribute name="id" use="required" type="xs:NMTOKEN"/>
      <xs:attribute ref="xml:space" fixed="preserve"/>

That would solve the issue.


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