New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<source> with only spaces are emptied on deserialization #11
Comments
Thanks for reporting this issue. If you would like to contribute a fix, please do so via a pull request. Otherwise, we will evaluate and prioritize the fix as appropriate. |
Upon further examination of the issue, this is by design. If you declare xml:space="preserve" then you will get the expected output. Perhaps you are expecting the default "processing mode" of the OM to be to preserve whitespace? In which case, this is not a bug but a design change. |
To clarify a bit more: this is the default behavior of the OM because it is based on .Net XmlReader/Writer which does not preserve by default. |
Looking more closely at the XML specification, I have to agree: So it's not a bug. But I would change this as a request for a change in behavior. While remove spaces on outer content is fine, it seems that completely removing spaces in elements that are content like I'll also post a not to answer your email in the XLIFF list. |
Thanks for reporting this issue. If you would like to contribute a fix, please do so via a pull request. Otherwise, we will evaluate and prioritize the design change request appropriately. |
It looks like the content of
<source>
is removed on reading when it is made of spaces.For example if we have this:
We get this output (no content for
<ignorable>
):While I would expect this output:
It happens also for
<segment>
elements.The text was updated successfully, but these errors were encountered: