Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
odfdom-0.8.5
-
None
-
Operating System: All
Platform: All
-
200
Description
Frank Meies reported an issue that imported ODF 1.1 documents would receive an ODF 1.2 version tag, but not for settings.xml.
In addition as they still keep their ODF 1.1 structure, the documents get invalid.
The final solution for the problem should be handled in issue 199 by providing the possibility to import ODF 1.0 and ODF 1.1 to ODF 1.2, adapting XML changes.
Following dilemma, when loading an previous ODF:
1) Adding a new ODF 1.2 feature, but not the version attribute (INVALID)
2) Not adapting ODF changes, but the version attribute (INVALID)
I suggest that we might apply a better heurisitic.
a) Adding access to the settings.xml
b) Do NOT adding the ODF 1.2 version to every ODF document being opened
Aside of the better statistic of less invalid documents (my bold assumption), we have a much better change to repair them when #199 is fixed and adapt the changes, as the version attribute is still prior 1.2
PS: I would have added a regression test case, but unfortunately the ODF Validator of the ODF TOOLKIT is not a Maven project and can not be applied easily as tool for our regression testing. The project owner my colleague Michael Brauer is currently on vacation.