https://bugs.kde.org/show_bug.cgi?id=463378
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In||8.1.0
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=463378
--- Comment #18 from Metal450 ---
Aha, perfect, thanks!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=463378
Peter changed:
What|Removed |Added
CC||benedekppe...@gmail.com
--- Comment #17 from Peter
https://bugs.kde.org/show_bug.cgi?id=463378
--- Comment #16 from Metal450 ---
(In reply to caulier.gilles from comment #15)
> Hi Maik and Merry Christmas,
>
> Yes, i'm busy bu i advance well
>
> https://docs.digikam.org/en/index.html
>
> I hope to finalize online doc in few days...
>
> I
https://bugs.kde.org/show_bug.cgi?id=463378
caulier.gil...@gmail.com changed:
What|Removed |Added
Platform|Other |Microsoft Windows
https://bugs.kde.org/show_bug.cgi?id=463378
--- Comment #14 from Metal450 ---
(In reply to Maik Qualmann from comment #13)
> Normally, Gilles creates weekly snapshots. However, he is very busy at the
> moment, restructuring and porting the digiKam documentation. I don't think
> he'll be anywhere
https://bugs.kde.org/show_bug.cgi?id=463378
--- Comment #13 from Maik Qualmann ---
Normally, Gilles creates weekly snapshots. However, he is very busy at the
moment, restructuring and porting the digiKam documentation. I don't think
he'll be anywhere near the build machines over the holidays
https://bugs.kde.org/show_bug.cgi?id=463378
--- Comment #12 from Metal450 ---
(In reply to Maik Qualmann from comment #11)
> The metadata viewer only displays the entry of a single selected image. In
> the case of a multi-selection or maintenance tool process, we would have to
> examine the
https://bugs.kde.org/show_bug.cgi?id=463378
--- Comment #11 from Maik Qualmann ---
We already have requests to provide a user viewable log in digiKam. I'm sure it
will come in the future.
The metadata viewer only displays the entry of a single selected image. In the
case of a multi-selection or
https://bugs.kde.org/show_bug.cgi?id=463378
--- Comment #10 from Metal450 ---
(In reply to Maik Qualmann from comment #7)
> Giving a warning every time isn't really practical.
So currently the software has that toast UI, i.e. "Updating database - process
is done." I was thinking a similar
https://bugs.kde.org/show_bug.cgi?id=463378
Maik Qualmann changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit|
https://bugs.kde.org/show_bug.cgi?id=463378
--- Comment #8 from Maik Qualmann ---
Git commit d71f6605893d5b1b801ebc425756114711c5fc97 by Maik Qualmann.
Committed on 25/12/2022 at 10:20.
Pushed by mqualmann into branch 'master'.
add support for XPTitle and remove XP* metadata when writing
https://bugs.kde.org/show_bug.cgi?id=463378
--- Comment #7 from Maik Qualmann ---
Giving a warning every time isn't really practical. On the one hand we don't
get an error message from Exiv2 in this case. On the other hand, we would have
to read all the metadata of the images to determine which
https://bugs.kde.org/show_bug.cgi?id=463378
--- Comment #6 from Metal450 ---
Those options all work as a one-off fix for a particular images/images (or for
users who somehow become aware of the issue), but more broadly, the software
should really provide some warning. Ie just a simple check to
https://bugs.kde.org/show_bug.cgi?id=463378
--- Comment #5 from Maik Qualmann ---
Exactly, XP Keywords is the problem. I can look up the relevant bug reports for
you. Just so much, because of the encoding, this tag has historically only been
read-only in Exiv2. It also doesn't help to enable
https://bugs.kde.org/show_bug.cgi?id=463378
--- Comment #4 from Metal450 ---
Is the output of exiftool enough? Let me know if not & I'll send the picture
itself, but exiftool's output is below. I do see mention of "XP Keywords."
However, if there's a known issue that a particular type of
https://bugs.kde.org/show_bug.cgi?id=463378
--- Comment #3 from Maik Qualmann ---
According to the log, the metadata was written without errors. If the tag was
written with Windows programs, there is a possibility that the tag is written
in Microsoft XP* metadata. Exiv2 can currently only read
https://bugs.kde.org/show_bug.cgi?id=463378
--- Comment #2 from Metal450 ---
> Whether the modification date changes depends on the metadata settings.
Yeah, that was desired - was just mentioning it to illustrate that digiKam had
actually done something to the file (even though no binary
https://bugs.kde.org/show_bug.cgi?id=463378
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
19 matches
Mail list logo
