OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

opendocument-users message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [opendocument-users] simple OO.org document goes awry in MS Office 2007 w/SP2 - what went wrong?

On Mon, Jun 15, 2009 at 12:40 PM, Cody, John (OFT) <John.Cody@cio.ny.gov> wrote:

> What went wrong?  Is there anything I should be doing in particular when I draft documents in OO.org 3.1 that will help the document be interpreted better by MS Office 2007 SP2?

Hi, John,

Did you set OOWriter to save as ODF 1.1?  By default, OOo 3.x writes
to what is called ODF 1.2, although there is no ODF 1.2 yet. The
setting is at Tools > Options > Load/Save > General. Note, however,
the warning on that dialog page that not using ODF 1.2 may cause data
loss when saving.

If you experienced that after setting the save format to ODF 1.1, I'd
suggest reporting the experience to the ODF TC along with a request
that they indentify the relevant portions of the ODF 1.1 and IS 26300
specifications that are ambiguous and to repair those defects in the
specs. If you experienced that with the save format set to ODF 1.2,
you might report it as pointing to a potential incompatibility between
the ODF 1.1 and 1.2 specs

The proper list for such reports is the office-comment list,
<office-comment@lists.oasis-open.org>>. Subscription instructions are
here. <http://www.oasis-open.org/maillists/guidelines.php#subscribing>.

I encourage you to make a regular practice of reporting such
interoperability failures to the ODF TC along with similar requests.
ODF has no reference implementation and using OOo as a de facto
reference implementation is problematic because it is a moving target
not under the control of the ODF TC. So interop bug reports should go
to the ODF TC so that the ambiguities in the specification can be
repaired, unless you are certain that the interop failure results from
non-conformance to the specification(s).

Best regards,

Paul E. Merrell, J.D. .

Universal Interoperability Council

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]