Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | No manifest:version attribute in manifest:manifest element | ||||||
---|---|---|---|---|---|---|---|
Product: | xml | Reporter: | chriskimball <mail> | ||||
Component: | code | Assignee: | michael.ruess | ||||
Status: | CLOSED FIXED | QA Contact: | issues@xml <issues> | ||||
Severity: | Trivial | ||||||
Priority: | P3 | CC: | issues, michael.brauer, mikhail.voytenko, svante.schubert | ||||
Version: | OOO330m1 | Keywords: | odf_validation | ||||
Target Milestone: | 3.4.1 | ||||||
Hardware: | Mac | ||||||
OS: | All | ||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||
Developer Difficulty: | --- | ||||||
Attachments: |
|
Description
chriskimball
2010-11-25 17:34:57 UTC
Created attachment 75141 [details]
Fails validation in META-INF/manifest.xml
reassigned Set target to 3.4, and re-assigned issue. I can confirm the issue, in the attached document with the latest version of the online validator http://tools.odftoolkit.org/odfvalidator/ The version attribute is missing in the root element of the manifest.xml. Instead the missing mimetype attribute is a problem of the validator. It can also reproduced by the latest online available OOo version OOo-dev/3.4$Win32 OpenOffice.org_project/300m94$Build-9547 and OpenOffice.org/3.3$Win32 OpenOffice.org_project/330m15$Build-9546 By saving any document, for instance an empty text document. Respectfully, in the normal course of affairs when might this problem be resolved? (I'm an advocate for the OpenDocument Text format, choosing to distribute ODT files of biblical text at my site <tanach.us>. In promoting this new feature and ODT I've claimed that my files validate with your validator. And they did a few weeks ago. Now they don't, a source of consternation and embarrassment.) fixed in cws fwk162 Today, 6 dec 2010, http://tools.services.openoffice.org/odfvalidator/ fails to validate the trival OpenWriter file test.odt attached. Same error results. Are the repairs to "cws fwk162" for the validator or OpenOffice Writer? When will they take effect for the site users? Thanks, Chris Kimball Today, 6 dec 2010, http://tools.services.openoffice.org/odfvalidator/ fails to validate the trival OpenWriter file test.odt attached. Same error results. Are the repairs to "cws fwk162" for the validator or OpenOffice Writer? When will they take effect for the site users? Thanks, Chris Kimball The changes in cws fwk162 fix the bug in package generation in OOo. As the target field shows it is going to be integrated in OOo3.4 branch. If you would like to test the cws after the integration in the development branch you should wait for integration of the cws. Before the cws is integrated this bug have to be set to Verified ( that would mean that the cws is already in QA ). After the bug is verified you can track the status of the cws using the following link: https://tools.services.openoffice.org/EIS2/cws.ShowCWS?logon=true&Id=9948&Path=DEV300%2Ffwk162 The response by sus Mon Nov 29 11:39:22 +0000 2010 indicates the problem is in the validator: "The version attribute is missing in the root element of the manifest.xml. Instead the missing mimetype attribute is a problem of the validator." In creating my own manifest files, nothing is accepted by your validator. Would you please provide an example of a valid manifest file? Or at least its root element. The latest ODF1.2 draft explicitly requires that manifest:manifest element contains manifest:version attribute. Before this bug was fixed, it had not been the case. I have no information regarding the validator problem with the media-type that sus has mentioned. Changing the Summary to avoid further confusions. This bug is only about manifest:version attribute in manifest:manifest element. I am not sure how the validator issues are handled, but if issuezilla bugs are used for them as well, then we need a new issue for validator. The ODF validator has, apparently, been repaired. My unchanged files now validate. OOWriter 3.3 files don't. Thanks, Chris mav->mru: Please verify in fwk162. Verified in CWS fwk162. Checked in DEV300m98. |