In the description box “charset=Ascii” is being added on import and written to image data on export even when hidden and /or private are selected. Any idea where this is coming from and how to correct it.
This was a bug, just fixed in master now. Will be ok in 3.4.
1 Like
Bump.
Happened again in dt 3.4
Sample RAW:2020-12-28.14-27.5483.NEF (24.8 MB)
Dontask
December 28, 2020, 6:05pm
5
My issue was resolve in 3.4.
Reported the bug. Dev found the issue. It will be fixed by 3.6
opened 03:26PM - 31 Dec 20 UTC
closed 02:25PM - 02 Jan 21 UTC
bug: pending
scope: DAM
understood: unclear
**Describe the bug**
When importing RAWs to darktable 3.4, a description meta… data is added with the content "binary comment".
I'm importing NEF RAWs from a Nikon camera, I tried changing comments off and comments on with a blank field, issue persists.
**Expected behavior**
A clear description metadata
**Screenshots**
**Platform (please complete the following information):**
- Darktable Version: 3.4
- OS: Ubuntu 20.10
**Additional context**
<!-- Add any other context about the problem here, for example:
Sample NEF:
[sample.zip](https://github.com/darktable-org/darktable/files/5757601/sample.zip)
darktable-org:master ← phweyland:imp-fix
opened 09:43PM - 31 Dec 20 UTC
Fixes #7579
This fixes two issues:
- charset=xxx is not part of the UserComm… ent. The method comment() allows to get the text properly decoded. BTW, this charset=xxx was then written in xmp description and polluted it as well.
- special text "binary comment" return by exiv2 in case of invalid text.
Hello, I just installed Darktable 4.0.0 this morning and a good part of my photo collection contains the string “charset=Ascii” in the Description field.
