https://bugs.kde.org/show_bug.cgi?id=458583

            Bug ID: 458583
           Summary: Typos are not correctable in at least some fields in
                    IPTC metadata.
           Product: digikam
           Version: 7.8.0
          Platform: Microsoft Windows
                OS: Microsoft Windows
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Metadata-Iptc
          Assignee: digikam-bugs-n...@kde.org
          Reporter: j...@acm.org
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***

Weekly version of Digikam:
Build date: 8/23/2022 3:24 PM (target: RelWithDebInfo)
Revision: 87d0bb259a475adf94fd188cb3685d8efc16f121
Branch: qt5-maintenance


STEPS TO REPRODUCE
1. Make a typo in the Digikam Metadata Edit dialog box in the Edit IPTC, Origin
panel in the City field (Smyrnat)
2. Try to correct the typo.  (Smyrna)
3. No matter what I have tried for saving the corrected data, the incorrect
data keeps showing back up.
4.  I have tried Apply, and OK, and Next followed by Previous followed by
apply.  When I hit apply, the incorrect data shows up again.  

OBSERVED RESULT
The typo I am trying to correct keeps popping back up.

EXPECTED RESULT
The typo would be corrected in all cases listed in step 4 above.


SOFTWARE/OS VERSIONS
Windows: 11
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Note that I am having to do this one image at a time because of a couple of
separate bugs.
   Templates are horribly broken as they insist on doing everything and I have
several thousand locations, so templates are useless to me.  (There are already
bugs written on this - and they have not been fixed in YEARS).
   I tried doing it directly with ExifTool, and while the information appears
in the image, it is refusing to read it into the database and repopulate the
data in the right panel or the metadata dialog box.  (I will be writing a bug
on this shortly.).
  Reverse Geocoding also does not populate these fields as they should.  (there
are already bugs written on this).

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to