[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [tdf-discuss] OOXML ECMA-376, transitionnal and strict


Taking a look to the 'standard' I see that section 17.2.3 of ISO/IEC 29500-1 (Part 1) indicates that there must be a conformance="strict" attribute in the Main Document Story. I have generated some documents with office 2013 and the tags appear inside the document in this way:
+for word (docx) is in word\document.xml and appears as <w:document ... w:conformance="strict">
+for excel (xlsx) is in xl\workbook.xml and appears as <workbook ... conformance="strict">
+for powerpoint (pptx) is in ppt\presentation.xml and appears as <p:presentation ... conformance="strict">

Creating a regular expression for checking this must be easy, for example:
grep "<\(p:\)\?presentation.*\(p:\)\?conformance=\"strict\".*>" presentation.xml

Be careful as the xml probably is not pretty printed so it can be quite long and impact performance when parsing. This can easily be solved parsing only the first 2048 characters, for example, but of course this deserves further testing

Best regards

El 02/05/16 a les 14:24, mjollnir66@laposte.net ha escrit:
Just seen with the System IT team :

Unzipping every OOXML attachment and checking a tag inside a specific XML file could be done by script.
This would be done on the incoming email server.
We would choose a behaviour depending on the result, wether the file is strict OOXML or transitionnal OOXML.

As we never had this kind of need before, it's costy in matter of ingeneering time.

If/when you have information about how to dinstinguish transitionnal from strict OOXML, I would be glad to hear from it.

Then I'll ask my direction if we can dig this (and update the thread whatever the answer is).

Thank you again for your care and your expertise.

Best Regards.

M.

----- Mail original -----

De: "Italo Vignoli" <italo@libreoffice.org>
À: discuss@documentfoundation.org
Envoyé: Jeudi 28 Avril 2016 14:37:08
Objet: Re: [tdf-discuss] OOXML ECMA-376, transitionnal and strict

On 28/04/2016 09:15, mjollnir66@laposte.net wrote:

The question is, how do we enforce the rules with the greatest
efficiency possible.
Unfortunately, interoperability is strictly related to the user
behaviour, and should become a topic for students in schools. Users
should learn how to create interoperable documents, not only related to
fonts but also to other document elements.

In my opinion, an automatic reply of the administration ingoing email
platform would be the best solution. It would reply automatically to
anyone who sends an email with a transitionnal OOXML attached. This
email would be written very carefully whith information about IGR v2,
about the 2 versions of OOXML and about what are the best practices
to communicate with a french administration (ODF).
This could educate users, over the very long term (as most users will
completely ignore the remark).

Therefore is the following question : What is the easiest way to know
wether a file is written in strict OOXML or not ?
I am investigating the issue myself, as I will talk to an audience of
public administration employees in Italy in two weeks, and I will have
to cover the topic.

Or maybe just checking if a single file exists or not would tell us
if the file is strict or transitionnal ?
For sure, MS Office 2013 used to have huge problems in handling OOXML
Strict: http://www.italovignoli.org/2014/02/redmond-we-have-a-problem/.

Microsoft answer on the topic is that I did something wrong as a user,
because I created some content before saving the OOXML Strict, while MS
Office defaults to OOXML Transitional when you enter contents (so, you
cannot save as OOXML Strict a document with contents).

By the way, this was scrutinized by the UK Cabinet Office.




--
To unsubscribe e-mail to: discuss+unsubscribe@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

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.