Steps how to reproduce [Reproducible] with server installation of "LibO 4.0.2.2 rc - German UI / German Locale [Build ID: 4c82dcdd6efcd48b1d8bba66bfe1989deee49c3)]" {tinderbox: @6, pull time 2013-03-26 12:00(?)} on German WIN7 Home Premium (64bit) with newly created own user profile: 1. Save Attachment 77203 [details] for Bug 62873 2. Open document from LibO Start center 3. Menu 'Tools -> Options -> Load/Save -> General - ODF Formt Version = 1.2 (Extended) <ok> 4. Type a blank into cell A1 5. Menu 'File -> Save as - ODF12EXTENDED.ods' 6. Menu 'Tools -> Options -> Load/Save -> General - ODF Formt Version = 1.2 (Strict) <ok> 7. Menu 'File -> Save as - ODF12STRICT.ods' 8. Validate both documents with <http://odf-validator.rhcloud.com/> Result: ODF12EXTENDED.ods validation fails, Error see below Error: tag name "calcext:conditional-formats" is not allowed. Possible tag names are: <named-expressions>,<soft-page-break>,<table-header-rows>,<table-row-group>,<table-row>,<table-rows> This MIGHT be the reason why many LibO Versions (for example: parallel Dev-installation of "Version 4.1.0.0.alpha0+ (Build ID: 049ce78144650d92eb6bd73292868f73d37c901) TinderBox: Win-x86@6, Branch:master, Pull Time: 2013-03-29_23:59:42" ENGLISH UI / German Locale on German WIN7 Home Premium (64bit) with LODev/4 Masters User Profile) do not show CF when they open ODF12EXTENDED.ods
That sounds strange. ODF 1.2 extended allows any element names to be added to the document and just request from the consumer that they are ignored if they can't be handled. Are you sure that you explicitly selected "ODF 1.2 extended" during validation? Auto detect does not work with extended documents.
(In reply to comment #1) No, I had "auto detect" for Validator. So it seems we have 2 questions a) Is our document type marker correct? b) is it really necessary to produce a nonconformat 1.2 (strict) document? I see no missing functions when I save that document as 1.2 (strict), and we might risk unnecessary compatibility issues.
(In reply to comment #2) > (In reply to comment #1) > No, I had "auto detect" for Validator. > > So it seems we have 2 questions > > a) Is our document type marker correct? No. I think there is no official value for 1.2 extended. Extended is just the mode that the producer uses. ODF just allows foreign elements in ODF 1.2 extended vs 1.2 strict and specifies that a document after removing all foreign elements must conform to the strict spec. > > b) is it really necessary to produce a nonconformat 1.2 (strict) document? I > see no missing functions when I save that document as 1.2 (strict), and we > might risk unnecessary compatibility issues. Yes.
So - closing :-)