[Okular-devel] [Bug 154698] Won't open some TIFF files

[Pino Toscano]

> >> That is not actually the case.
> >
> > It's nice to see how you reject the explanation of the developers of
> > that architecture.
>
> Perhaps if you read the rest of what I said, you would not jump to
> conclusions.

/dev/null.

> >> KDE is using the MIME type of the file to determine which Okular
> >> backend to call.
> >>
> >> So, this problem might be caused by Okular's architecture.
> >
> > No. Okular asks KMimeType to determine the mimetype of the file, then
> >  it chooses which backend to call acording to what KMimeType reports.
>
> IIUC, there are to issues, the KParts which rely on KDE to determine the
> MIME type before the appropriate Okular KPart is called, and the Okular
> front end that is called as an external application and, based on the
> file, calls a KPart to display it.  I think that you are talking about
> the front end and I am talking about the KParts.  I don't see how it can
> work for the KParts running in Konqueror, but since the GwenView front
> end works OK, there is no reason that the Okular front end won't work as
> well.

Okular is registered as KPart for image/jpeg and image/tiff.
And, for your information, KPart has NOTHING to do here.

> > Okular just trusts what KMimeType reports as results. No less and no
> > more.
>
> Probably not the greatest of ideas since KMimeType is known to be
> somewhat broken in KDE3 and I doubt that it has been fixed.  Actually,
> it needs some design work first.

Sadly, it's ALL we have, no less and no more.

> >> Gwenview, OTOH, is directly presented with the file and has no
> >> problem reading it.
> >
> > ... just because both TIFF and JPEG are image formats supported by
> > gwenview. If you do kfile --dialog <image>
>
> I presume that you mean "kfile4".

Yes.

> It is here I can demonstrate what I mean when I say that KMimeType is
> somewhat broken.

Then go bug against KMimeType, NOT in any application where you face issues.
Again, your behaviour-pattern "spread again" is applied.

> > Thus, I'm reassigning the problem to kdelibs (where KMimeType is), as
> >  should be KMimeType to report us the correct mimetype for it.
>
> As I see it, there are issues with BOTH Okular and the KDE MIME type
> system.

No, as okular "blindly" accepts what KMimeType reports (and, it could not do 
else).

As I see it, you quite freely judge with NO single knowledge on the inner of 
both okular and kdelibs. Instead of randomly shoot your opinions around 
different mailing lists, please *trust* who know (at least in this case) more 
than you.

-- 
Pino Toscano
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/okular-devel/attachments/20071228/76e3f695/attachment-0001.pgp