Bug 260468

---- Reported by chris.vigelius@gmx.net 2006-11-25 16:46:10 ----

Version:           1.6.0 (using KDE KDE 3.5.5)
Installed from:    Ubuntu Packages

Apparently, Krita takes the full name of the user (probably out of Kontact) and adds it to the metadata of every image saved without telling about it. There also seems to be no setting to turn this feature off.

I consider this to be a major privacy issue, and kindly ask you to either remove that feature completely, or at least add a setting so the user can decide whether he wants to publish his full name with the image automatically (this should be turned off by default).

There are many reasons why a user might not want his full name to be exposed along with any image he has edited, so having that enabled by default in Krita seems totally wrong to me; also no other image editor I know of does something similar.



---- Additional Comments From chris.vigelius@gmx.net 2006-11-25 17:23:34 ----

Addition: The behaviour described above does not seem to apply to JPG files, but works (at least) with PNG. Also, the name is taken from System Settings -> "About Me", not from Kontact as I suspected before.

Steps to reproduce: 
1.) Get a PNG from somewhere
2.) Open PNG with Krita
3.) Save Image
4.) Close Krita
5.) Right-click PNG in Konqueror, select "Properties" and see your name appear on "Meta-Info" tab



---- Additional Comments From zander@kde.org 2006-11-25 18:40:51 ----

KOffice wide we use the document information dialog that allows the user to add his name to the image.
In krita this is also done. See file->document information. I do believe that this is automatically saved in kritas native format.

This means that the only way to get author information attached to a document is to open that dialog and press ok.

I suggest using this information (if present) when exporting.



---- Additional Comments From chris.vigelius@gmx.net 2006-11-25 18:55:24 ----

Hello Thomas, 

the user information is also saved when editing PNGs and the user info gets definitely attached without opening the file info dialog.

A possible solution would be to extend the "Author" tab in that dialog with a checkbox saying "Always save user information" or something similar (default should be off) - then users would have full control over that in all KOffice apps.



---- Additional Comments From zander@kde.org 2006-11-25 19:17:48 ----

On Saturday 25 November 2006 18:55, Chris Vigelius wrote:
> the user information is also saved when editing PNGs and the user info gets
> definitely attached without opening the file info dialog.


Yes, and that's a bug. Which is why I confirmed this report.
My post was meant as a possible solution to that problem.




---- Additional Comments From cyb@lepi.org 2006-11-25 20:11:28 ----

I can understand that some people don't want their name in png files (actually I don't see a reason why someone wouldn't want to be associated with its work, but well) but :

1) I want all my png to have my name in the meta information, at the time I used photoshop, I got angry with it because half of the time I forgot to add my name in the comments of the files I saved with it

2) we allready saved what it's in image information, which is automatically filled at startup by koffice, and I don't think that having to open that dialog which will then magicaly change how metainformation is saved a good idea. But if you remove your name from that dialog it isn't saved anymore in the png file, now the default values of the author information needs to be editable and be automatic, but that's not a krita bug, it's a koffice wide one. (maybe even kde ?)



---- Additional Comments From boud@valdyas.org 2006-11-25 22:25:47 ----

All koffice applications indeed automatically save your full name with all documents -- along with other information from that kcontrol screen. I'll set the product to koffice. 

I think we want a setting in the settings dialog that enables the saving of this data and that it should be off by default.



--- Bug imported by faure@kde.org 2010-12-17 19:42  ---

This bug was previously known as bug 137863.