[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?
----- Original Message ---- From: marbux <email@example.com> On Tue, Jun 16, 2009 at 4:03 PM, <firstname.lastname@example.org> wrote: > > marbux <email@example.com> wrote on 06/16/2009 01:16:31 PM: > >> On Tue, Jun 16, 2009 at 12:37 AM, <firstname.lastname@example.org> wrote: > >> So I understand it, are you saying that every bug report I or anyone > >> else sends you on an interop failure between Lotus Symphony and other > >> ODF implementations will result in you promptly submitting a TC > >> proposal to fix the relevant spec(s) with as many mandatory interop > >> requirements as are needed to remove the relevant ambiguity if the > >> failure is due to an ambiguity or other flaw in the spec, Rob? And > >> that you'll shepherd that proposal through the TC and implement the > >> fix? > > If you find an interop bug, then you can certainly submit a defect report > > online at the support forums at http://symphony.lotus.com > > Of course, those with a support contract will get a more rapid response. > > But if you write up a defect report, preferably with an example file, then > > it will certainly be looked at. > That doesn't answer what I asked, Rob. Take another swing at it, please? Just as a watcher on the list reading this thread... How is an end-user suppose to know the difference between a bug in the ODF spec, and an application bug? As a software developer, I don't know think there is any way for the end-user to know that. However, the implementer would be able to diagnosis it in their implementation as such and respond accordingly. Now, if the implementer told the end-user that it is an ODF spec and did nothing about it, then there is probably good reason for the end-user to notify the OIC/ODF TC about the issue. Unfortunately, most software producers are not that open with their customers. Open Source software has no choice about being that open since all dealings, and even the code itself is fully public. Any how...just a few thoughts from a lurker... Ben