[digikam] [Bug 467713] Rating unintentionally set to max. after cropping an image

2023-10-15 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=467713 --- Comment #12 from caulier.gil...@gmail.com --- Git commit bbb2603eb75c734a56682bd86fdf53ce99a32939 by Gilles Caulier. Committed on 15/10/2023 at 09:49. Pushed by cgilles into branch 'master'. digiKam online doc: remove the map of transcription of IPT

[digikam] [Bug 467713] Rating unintentionally set to max. after cropping an image

2023-10-14 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=467713 --- Comment #11 from Maik Qualmann --- Note: For this change to take effect, the rating must be reset to the default in the advanced metadata settings or the digiKam profile must be imported using the profile load function. Maik -- You are receiving

[digikam] [Bug 467713] Rating unintentionally set to max. after cropping an image

2023-10-14 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=467713 Maik Qualmann changed: What|Removed |Added Version Fixed In||8.2.0 Status|REPORTED

[digikam] [Bug 467713] Rating unintentionally set to max. after cropping an image

2023-10-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=467713 --- Comment #9 from caulier.gil...@gmail.com --- Hi Maik, Yes IPTC Urgency is and older way to store Rating when digiKam XMP+sidecar support was not yet usable. Now the situation is completely different and definitively, this can be removed at all. Gil

[digikam] [Bug 467713] Rating unintentionally set to max. after cropping an image

2023-05-03 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=467713 --- Comment #8 from Maik Qualmann --- I see this comment in the source code: // NOTE : with digiKam 0.9.x, we have used IPTC Urgency to store Rating. // Now this way is obsolete, and we use standard XMP rating tag instead. When I look at the meaning o

[digikam] [Bug 467713] Rating unintentionally set to max. after cropping an image

2023-05-03 Thread Daimonicon
https://bugs.kde.org/show_bug.cgi?id=467713 --- Comment #7 from Daimonicon --- So there was a Photoshop entry there that took care of the stars and color markings ? So I use Photoshop but not in connection with these pictures. In the meantime I have also left out the sidecars. Up to this point th

[digikam] [Bug 467713] Rating unintentionally set to max. after cropping an image

2023-05-03 Thread Daimonicon
https://bugs.kde.org/show_bug.cgi?id=467713 --- Comment #6 from Daimonicon --- I mean already that I had sent both files. However, the images do not cause any more problems - reducing the size of the images with an external program was apparently the beginning of the error and I have completely o

[digikam] [Bug 467713] Rating unintentionally set to max. after cropping an image

2023-05-03 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=467713 --- Comment #5 from Maik Qualmann --- Yes, I received a sample. Maybe it got lost somehow then. I tested it again. The sidecar contains the entry "photoshop:Urgency="1" which is interpreted by the Exiv2 conversion table for XMP metadata as "Iptc.Applica

[digikam] [Bug 467713] Rating unintentionally set to max. after cropping an image

2023-05-03 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=467713 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment

[digikam] [Bug 467713] Rating unintentionally set to max. after cropping an image

2023-03-23 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=467713 --- Comment #3 from Maik Qualmann --- Well sidecars are "XMP" files, so yes. It is possible that the rating is in the metadata of the images themselves. Use the metadata viewer to check whether rating metadata is available. Otherwise send me an image +

[digikam] [Bug 467713] Rating unintentionally set to max. after cropping an image

2023-03-23 Thread Daimonicon
https://bugs.kde.org/show_bug.cgi?id=467713 --- Comment #2 from Daimonicon --- (In reply to Maik Qualmann from comment #1) > I can't reproduce that here. We copy the metadata to the new image. Either > the correct rating was not imported into the DB beforehand or there was > another problem. Are

[digikam] [Bug 467713] Rating unintentionally set to max. after cropping an image

2023-03-23 Thread Maik Qualmann
https://bugs.kde.org/show_bug.cgi?id=467713 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik