Niels Kristian Bech Jensen <nkbj1...@hotmail.com> writes:

>> Considering the harm it can cause, I think it would be better not to
>> try and open these files. I think that we might want to take a further
>> step and also ignore tif and jpg endings. These raw files come from
>> very old cameras. I don't think anyone would care if the gimp plug-in
>> cannot open them, as they could still open them with ufraw
>> stand-alone.
>> 
> Maybe we should make it a compile time option disabled by default?
> Regards,Niels Kristian

I tend to agree with Udi: we seem to have no users/examples, and having
them picked up by the file manager seems to be more trouble than it's
worth.   One can still invoke them manually, so a compile-time option
even off by default seems like needless complexity, where the cognitive
load of its  mere presence is more than the benefit for the theoretical
(but as yet unidentified) user.

Attachment: pgphrEr26Jfbi.pgp
Description: PGP signature

------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
ufraw-devel mailing list
ufraw-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ufraw-devel

Reply via email to