OK, thanks for testing. I'll check what can be done. Regards, Rodolfo -- Rodolfo M. Raya Maxprograms
http://www.maxprograms.com -------- Original Message -------- Subject: RE: [xliff] Whitespace handling in <data> From: Yves Savourel <
ysavourel@enlaso.com > Date: Fri, August 31, 2012 1:20 pm To: <
xliff@lists.oasis-open.org > Hi Rodolfo, all, I've tried the following, as we di sc ussed. But that didn't work. < xs:element name= data > < xs:complexType mixed= true > < xs:sequence > < xs:element minOccurs= 0 maxOccurs= unbounded ref= xlf:cp /> </ xs:sequence > < xs:attribute name= id use= required type= xs:NMTOKEN /> < xs:attribute name= xml:space fixed= preserve /> </ xs:complexType > </ xs:element > Note using name= xml:space caused errors for me. Then when I've changed name= xml:space to ref= xml:space , I got import problems in the other modules. Cheers, -yves > -----Original Message----- > From: Rodolfo M. Raya [ mailto:
rmraya@maxprograms.com ] > Sent: Wednesday, August 22, 2012 4:52 PM > To: Yves Savourel > Subj ec t: RE: [xliff] Whitespace handling in < data > > > Hi, > > We can have the xml:space attribute set to preserve in the sc hema > but we can't make it unchangeable. > > Regards, > Rodolfo > -- > Rodolfo M. Raya
rmraya@maxprograms.com > Maxprograms
http://www.maxprograms.com > > > > -----Original Message----- > > From:
xliff@lists.oasis-open.org [ mailto:
xliff@lists.oasis-open.org ] > > On Behalf Of Yves Savourel > > Sent: Wednesday, August 22, 2012 4:15 PM > > To:
xliff@lists.oasis-open.org > > Subj ec t: [xliff] 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 exp ec tation of s ec tion 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 b ec ause 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 sp ec ification. > > > > 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:sequence > > > < xs:element minOccurs= 0 maxOccurs= unbounded ref= xlf:cp /> > > </ xs:sequence > > > < xs:attribute name= id use= required type= xs:NMTOKEN /> > > < xs:attribute ref= xml:space fixed= preserve /> > > </ xs:complexType > > > </ xs:element > > > > > That would solve the issue. > > > > Cheers, > > -yves > > > > > > > > > > -------------------------------------------------------------------- > > - To unsub sc ribe, e-mail:
xliff-unsubscribe@lists.oasis-open.org > > For additional commands, e-mail:
xliff-help@lists.oasis-open.org > > --------------------------------------------------------------------- To unsub sc ribe, e-mail:
xliff-unsubscribe@lists.oasis-open.org For additional commands, e-mail:
xliff-help@lists.oasis-open.org