Summary: | HIG CL3: Warning messages from light table | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Jakob Østergaard <joe> |
Component: | Usability-Ergonomy | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.6.0 |
Description
Jakob Østergaard
2007-06-06 23:32:35 UTC
This is not a bug. These messages come from Exiv2 library witch handle metadata from pictures. Its want mean than Canon encode an Exif tag using a lenght bigger than the limit defined in Exif standard... Gilles Caulier On Wednesday 06 June 2007 23:42:19 Gilles Caulier wrote:
...
> These messages come from Exiv2 library witch handle metadata from pictures.
> Its want mean than Canon encode an Exif tag using a lenght bigger than the
> limit defined in Exif standard...
>
Ok thanks Gilles,
I thought the warning messages might point to the cause of some of the other
problems I see (I have found two problems and I am reporting them now).
So, while I usually would never report such a warning message, I felt it might
be important in this case. Thanks for the quick reply!
http://wiki.openusability.org/guidelines/index.php/Checklist_Warning_Messages Language Warning dialogs should be: Understandable. Clearly phrased messages, non-technical terms and no obscure error codes should not be used. Specific instead of general. If the message is reporting a problem concerning a specific object or application, the object or application name should be used when referring to it. Informative and constructive. The reason for a problem should be given, and hints how to solve it. Polite, non-terrifying and non-blaming. Wording that terrifies the user ("fatal", "illegal") shouldn't be used, users shouldn't be blamed for their behavior, and the message should be polite. Mik, I cannot accept this B.K.O file as well (:=))). The message do not appear in a dialog, but in the console as debug messages. Also these messages are generated by Exiv2 library, not digiKam implementation. I'm agree with the way than debug console messages must be more explicit. There are a lots informations generated by Exiv2 in the console. But this is not relevant of digiKAm implementation. Please close this B.K.O file and open a new one the Exiv2 bugzilla... Thanks in advance Gilles I should add that I only submitted this bug because I thought it was related to #146464 (before I investigated #146464 properly). |