Word 2013 can't render xml based docs correctly [message #1441062] |
Thu, 09 October 2014 03:56  |
Eclipse User |
|
|
|
Hi all, I am facing the exact same problem with this guy. But since there is no response to it, I re-post the problem again at here.
"I use the BIRT reporting tool to generate word reports for the company I work for.
The tool outputs an xml based word doc and up until now there has been no issues with our reports, until we started using Office 2013.
I am confident that this is not an issue with the tool as previous versions of it and the current version have worked fine with previous versions of word but we are now seeing issues with older and current versions of our reports in word 2013.
The same report viewed in office 2010 looks perfect but it 2013 random tables in the report start getting torn apart or go missing, there are formatting errors and text get overlapped from one line into another .
It differs from report to report where the errors occur but given the same report viewed on multiple devices running office 2013 the errors appear in the same place, so its not a completely random occurrence.
It is also not a view issue as I have printed the docs and printing from 2010 is fine, but 2013 still has a large amount of errors.
In some cases when printing 2013 takes information in one column from one cell and puts it into another cell above or below it, all other cells get populated correctly but this one column gets populated with the wrong information in each of the cells.
This is what has led me to believe that it must be an issue with word as the idea of skipping around an xml file to pick an element that is not in sequence points to an obvious flaw in its ability to render xml correctly.
Viewing the doc in its raw xml form it seems to have the correct tags.
My question is can someone point me somewhere where I could do a comparison of what xml tags are expected in 2010 vs 2013 and if there has been any change to the schema?
Or if someone has the knowledge; is this a known issue and is there a bug in 2013 that causes this?"
The Birt version I'm using is 2.5.1. Is there any known solution or explanation to it?
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.10195 seconds