Bug#394875: closed by Rene Engelhard <firstname.lastname@example.org> (Re: Bug#394875: openoffice.org: OOo in Sarge doesn't know ODT ...)
On Mon, Oct 23, 2006 at 02:07:20PM -0700, Debian Bug Tracking System wrote:
> Paolo wrote:
> > ... yet it happily open an .odt without a warning though the user is left
> > with a dumb blank page.
> And? OOo 1.1.3 ddidn't support ODT yet. That's not a bug in 1.1.3.
it shouldn't silently open a doc in a format it doesn't know anything of.
It *is* a bug. I complained to the author who sent me an 'OOo document'
which for me was a just a blank page. Not a glich from OOo in Sarge, hence
I wrongly deemed the doc was void.
> sarge is not updated with new upstrema versions. Never. It never was and never
dosn't matter. It'll mean a plain Sarge system won't read .odt, yet OOo
should complain and offer some text open mode, like you get if you try to
open a binary. Or just popup a warning and bailout. Surely not giving the
feel it knows how to handle that format.
> If you really need ODT either use the 2.0.3 sarge backport or (if you
> know how to handle it) use etch or sid.
of course I need it and have installed 1.1.5 in /opt/. I wasn't asking for
new feat in 1.1.3 though, perhaps I badly named the bugrep, but my point
is explained above and I think it's a bug.
Given that Etch release is approaching, and that the fix might not be so
easy, I understand you might want to ignore it. But OOo or any other prog,
for that matter, should know the stuff it can eat, and check & complain
loudly if feeded with wrong types. Else it's buggy.