Bug 126153

Summary: Camera stores both jpeg and raw (nef), handle both as one
Product: [Applications] gwenview Reporter: Roger Larsson <roger.larsson>
Component: generalAssignee: tom.darboux
Status: CONFIRMED ---    
Severity: wishlist CC: a.nolting, kdebugs, kristo, nate, rayambrosi, tom.darboux
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Roger Larsson 2006-04-24 10:04:19 UTC
Version:           1.2.0 (using KDE 3.4.2 Level "b" , SUSE 10.0)
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.13-15.8-default

My camera stores both a jpeg and raw (nef)
it would be nice if Gwenview could handle them as one.
rln_0220.jpg
rln_0220.nef

Think of it like. RAW (NEF) is the negative and jpeg is the
processed image.

Do not show the NEF when there is an equally named jpeg.
(Maybe indicate somewhere that the negative is available)

This is especially important for the slideshow since only
the thumbnail (very small, and unrotated) will be shown.

Note:
* A user might have several cameras with different
  names of the RAW format.
* There might be RAWs with no corresponding jpeg.
  (but does the user really want to show an unprocessed image?
   in slideshow?)
Comment 1 Angelo Naselli 2006-04-24 10:46:20 UTC
Kameraclient plugin issue?
Comment 2 Roger Larsson 2006-04-26 12:35:27 UTC
One problem is probably the fact that NEFs from Nikon 
are identified as TIFF files, i.e. images in their own 
right... 
 
 Found another even better EXIF reader (made in Perl) 
 http://www.sno.phy.queensu.ca/~phil/exiftool/ 
 
 This tool reports the MIME type as 
 MIME Type                       : image/x-raw 
 
After modifying the file association gwenview
skip NEF files when browsing. Much better!
Comment 3 Nate Graham 2017-09-11 15:46:00 UTC
*** Bug 276718 has been marked as a duplicate of this bug. ***
Comment 4 Nate Graham 2017-09-11 15:46:26 UTC
*** Bug 188965 has been marked as a duplicate of this bug. ***
Comment 5 Nate Graham 2017-09-11 15:46:42 UTC
*** Bug 173665 has been marked as a duplicate of this bug. ***