-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Incomplete XML serialization #238
Comments
Thanks for reporting @ansFourtyTwo , yeah it's on the same topic mixed content, this time the parser favors the dedicated b attribute and skips the handling of it's tail content. |
Notes: That's my worst case solution... I want to resolve this in the xml nodes but that seems tricky
Hey @ansFourtyTwo The fix is on master and it will be included in the next release 👍 Here is the updated sample rendered. I am relying heavily on the w3c-test-suite for evaluation and out of the 25k tests none were able to reproduce your case, thanks again! There are a couple more things I still want to address regarding mixed content like whitespace preserve but your feedback has helped to improve wildcard/mixed content support a lot! |
Hi @tefra , your solution works as expected now. Thanks for the fix. Regarding whitespace preservation, I've checked some of the content and indeed it seems that parsing and serializing content back and forth strips out some of the whitespace. Currently, for me this is a cosmetic defect, but it in the end i will rely on propper formatting. Any idea, when you will tackle this issue? Best of luck |
I've opened the #243, it sounds easy... |
Hi @tefra ,
I ran into another issue when serializing the data model back to XML again. It might be related to former issue #213.
Once again my data models are generated using the command below:
I am still using the example file attached below:
example.reqif.txt
To parse the file and serialize it back to XML I use the follwing code:
I mostly use your tool to parse and write ReqIF files, where it is all about Specification Objects and their field attributes (The values of the attributes, to be more precise). Some of them contain some XHTML for formatted text. For the example file above I found out, that at least one attribute is not searialized correctly and most probably not parsed correctly.
To understand the problem, have a look at following XML Element in the example:
When serialized back the resulting content within looks like this:
As you can see, the serialized file does not contain the second part of the text within the
<xhtml:p>
tags, i.e. missing the part "Das eigene Fahrzeug auf das sich die Funktionsberschreibung bezieht " after the first<xhtml:br/>
.The text was updated successfully, but these errors were encountered: