Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index




Il 24/04/2011 20:04, NoOp ha scritto:
On 04/24/2011 01:34 AM, Jean-Baptiste Faure wrote:
Le 23/04/2011 11:00, Milos Sramek a écrit :
Dňa 22.04.2011 23:44, Wayne Borean  wrote / napísal(a):
What file?

Send copy as attachment.
It looks like that all tests, presented at
http://www.officeshots.org/galleries, fail because of a single issue. It
can be seen also in the attached file a. odf. This is the log from
http://tools.odftoolkit.org/odfvalidator/:


     Result for a.odt

This file is NOT valid

Result details:

upload:///a.odt:Info:ODF Version: 1.2

Perhaps the problem is there : change default ODF version used by your
LibreOffice and try again.
Menu Tools>  Options>  Load/Save>  General

I ran a few tests as well at http://tools.odftoolkit.org/odfvalidator/
I created a single document with LO 3.3.2, Ubuntu OOo 3.2, Standard OOo
3.3.0, and Standard OOo-Dev (3.4.0). All failed with 1.2 extended with
the exception of OOo-Dev (3.4.0).

With OOo-Dev 3.4.0:
ODF Validator Result Page
Result for OOoDev34_odftTest.odt

This file is valid

Errors whith LO 3.3.2, Ubuntu OOo 3.2, and Standard OOo 3.3.0, were
consistent 'Error:element "manifest:manifest" is missing "version"
attribute':

upload:///LO332_odfTest.odt/META-INF/manifest.xml[2,88]:Error:element
"manifest:manifest" is missing "version" attribute
upload:///LO332_odfTest.odt:Info:Generator: LibreOffice/3.3$Linux
LibreOffice_project/330m19$Build-202
Result details:

upload:///SOOo330_odfTest.odt/META-INF/manifest.xml[2,88]:Error:element
"manifest:manifest" is missing "version" attribute
upload:///SOOo330_odfTest.odt:Info:Generator: OpenOffice.org/3.3$Linux
OpenOffice.org_project/330m20$Build-9567

When changing the format to 1.0/1.1:
ODF Validator Result Page
Result for LO332_odfTest_ODF1.odt

This file is valid

and

ODF Validator Result Page
Result for SOOo330_odfTest_ODF1.odt

This file is valid
====

Note:

1.2 (not extended) fails on all as well - with the exception of OOo-Dev
(3.4.0). Also, I first tested a Word97 document that I'd used in a bug
report (saved as odt) and that doc carries over a style that the odf
test doesn't like:
upload:///Word97Test_wLO.odt/META-INF/manifest.xml[2,88]:Error:element
"manifest:manifest" is missing "version" attribute
upload:///Word97Test_wLO.odt/styles.xml[2,12196]:Error:unexpected
attribute "style:layout-grid-snap-to-characters"
upload:///Word97Test_wLO.odt:Info:Generator: LibreOffice/3.3$Linux
LibreOffice_project/330m19$Build-202

This file is NOT valid

Result details:

upload:///Word97Test_OOoDev.odt/styles.xml[2,12124]:Error:unexpected
attribute "style:layout-grid-snap-to-characters"
upload:///Word97Test_OOoDev.odt:Info:Generator: OOo-dev/3.4$Linux
OpenOffice.org_project/340m0$Build-9583

so I recommend testing using just a cleanly generated file (like I did
afterwards) for the tests.



Very interesting results... we have to deal with them as soon as possible...

If Libò 3.4.0 will be merged again with the last OOo 3.4.0 commits without loosing all the code cleaning (Code Hacks) efforts we could have the same "The file is valid" also for Libò 3.4.0.

Happy Easter evening,

Carlo

--
Unsubscribe instructions: E-mail to users+help@libreoffice.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/www/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.