kde comments

Hello,

Kde applications like Dolphin can write comments on images, but these
comments are stored in a special location, not in exifs, not in the
image itself.

but it looks like digikam is not able to read (neither write) these
comments.

could it be possible to have some import module to keep these comments
in digikam?

may be it's already here and I don't find it?

thanks
jdd
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

[Gilles Caulier-4]

Ah welcome to Nepomuk / Baloo world.

Typically, yes and no. Yes because DK has an interface to talk witk Baloo metadata storage. No, because Baloo is full of bug and crash.

My tip : ignore this feature for the moment. Also, it's a optional at compilation time (disabled by default).

If the Baloo stability is not improved in the future, i will remove Baloo support in DK. Why, because i recieve a lots of duplicate reports saying a DK crash about Baloo database.

Gilles Caulier

2016-01-30 18:43 GMT+01:00 jdd <[hidden email]>:

Hello,

Kde applications like Dolphin can write comments on images, but these comments are stored in a special location, not in exifs, not in the image itself.

but it looks like digikam is not able to read (neither write) these comments.

could it be possible to have some import module to keep these comments in digikam?

may be it's already here and I don't find it?

thanks
jdd
_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users

Le 30/01/2016 18:56, Gilles Caulier a écrit :
> Ah welcome to Nepomuk / Baloo world.

:-)

right now I use openSUSE Leap, and it seems to use a stripped down Baloo
(I see Baloo is installed, but the file search interface is very minimal)
>
> Typically, yes and no. Yes because DK has an interface to talk witk
> Baloo metadata storage. No, because Baloo is full of bug and crash.

surprise :-)

>
> My tip : ignore this feature for the moment. Also, it's a optional at
> compilation time (disabled by default).

good
>
> If the Baloo stability is not improved in the future, i will remove
> Baloo support in DK. Why, because i recieve a lots of duplicate reports
> saying a DK crash about Baloo database.

ok

thanks
jdd

_______________________________________________
Digikam-users mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-users