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

--- Comment #2 from IWBR <iwannaber...@gmail.com> ---
Well, in my case, the picture library is shared among several family members,
where each can use different software to edit and manage the collection, so as
long as changes are saved in the metadata and scanned when you first start your
picture manager, there should be no problem. (Btw, currently not 100% possible
with digikam, because of bug #380876 where the database is not properly updated
after a scan)

Now, in pictures where someone appears, they are tagged with that person's
name. In addition to that, some face recognition software has also identified
people faces and names have been assigned to them and saved in the metadata.
These face regions can be named the same way as an existing tag, but that's not
a problem since these are two completely separate things and should not
interfere.

When I started using digikam a few weeks ago, it scanned the full collection,
and as I see, it merged tags and face regions and treated both as the same
thing. Both are displayed in the "Tag" panel. Although only face-region
pictures are showed in the People tags (this is alright). So in the Tag panel,
there's no way to know which is which. They have even the same icon. I don't
even know if the name under the face region has been written in the metadata as
a regular tag (as names in the regular tag do automatically).

Relevant picture (I posted it before in another bug): https://imgur.com/a/vvPPV
. Some of these tags are regular tags, some of these are face regions, and some
of them have been fused by digikam. I just don't know which are which.

The workaround you mentioned would be to rename all non-face region tags to
something like "John Smith (no face)". But I think this not optimal and would
require overwriting hundreds of gigabytes of data, and could be inconvenient to
the rest of users.

Simply showing tags and face tags separately, even if they're in the same list
with a different icon, would help.

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

Reply via email to