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: RE: [xliff] Question on xml:space handling


Thanks Yves!

 

I agree that a change in behavior is preferable after gathering feedback both internally to MS and externally in the community. We will make the change in our next iteration (unless someone else wants to beat us to the punch J)

 

Ryan

 

From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Yves Savourel
Sent: Thursday, February 25, 2016 3:04 PM
To: xliff@lists.oasis-open.org
Subject: RE: [xliff] Question on xml:space handling

 

Hi Ryan, all,

 

Looking more closely at the XML specification I agree with Ryan that it’s valid to remove spaces when xml:space is default.

 

But I would suggest that a better behavior for the elements <source> and <target> would be to either preserve or normalize.

For a logical viewpoint if there is an <ignorable><source> </source></ignorable> entry it is very likely because it separates two segments that will still need that separation after merging. So a better default XLIFF processor behavior would be to either preserve or normalize.

 

Cheers,

-yves

 

 

From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Ryan King
Sent: Thursday, February 18, 2016 4:09 PM
To: 'xliff@lists.oasis-open.org' <xliff@lists.oasis-open.org>
Subject: [xliff] Question on xml:space handling

 

Hi all,

 

Yves logged two issues on the MS XLIFF OM github project (thanks Yves for testing!):

 

<data> made of spaces only is not preserved
https://github.com/Microsoft/XLIFF2-Object-Model/issues/13

 

<source> with only spaces are emptied on deserialization

https://github.com/Microsoft/XLIFF2-Object-Model/issues/11

 

I have no doubt that the first one is a bug since the default for <data> is preserve.

 

The second one is trickier. The default for <source> and <target> is to allow the application to decide. In this case, the OM is using .Net XmlReader, which removes whitespace by default. So, in order to preserve whitespace during serialization/deserialization, the user must set xml:space=”preserve” to override the default behavior of XmlReader.

 

So my question to this esteemed body of professionals: Should the MS XLIFF OM override the default behavior of XmlReader and preserve whitespace when xml:preserve=”default”?

 

Thanks,

Ryan

 



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