Activity log for bug #638321

Date Who What changed Old value New value Message
2010-09-14 18:20:22 Duncan Lithgow bug added bug
2010-09-14 18:20:22 Duncan Lithgow attachment added Dependencies.txt https://bugs.edge.launchpad.net/bugs/638321/+attachment/1584402/+files/Dependencies.txt
2010-09-14 18:42:47 Adam Dingle bug watch added http://trac.yorba.org/ticket/2557
2010-09-14 20:16:07 Jim Nelson bug task added shotwell
2010-09-14 20:44:00 Omer Akram shotwell (Ubuntu): importance Undecided Low
2010-09-14 20:44:00 Omer Akram shotwell (Ubuntu): status New Triaged
2010-09-15 19:32:59 Bug Watch Updater shotwell: status Unknown New
2011-02-20 15:29:45 Duncan Lithgow description Binary package hint: shotwell This is a bug about the way Shotwell handles importing a batch of photos which have previously been managed by F-spot. In F-spot there is no problem with having commas in the tag names, so a tag like Surname, Firstname is fine. When this tag is imported into Shotwell it keeps the tag as Surname, Firstname but as soon as you apply it to anything creates two new tags one called Surname and one called Firstname. This quickly starts to make a real mess of my tagging system where I have lots of people in the Surname, Firstname format. Workarounds: * I can manually edit all the tags which include commas before I apply them to any pictures. But that assumes I'm aware of the problem in advance. * I can fix it up afterwards. But I can only remove tags from one picture at a time, tags can't be edited as a batch operation for some reason. Solutions: * What about if Shotwell collected all the tags and presented the ones including commas, explained the problem and asked that they be renamed. * Shotwell could use a different separator. * Shotwell might be able to encode commas found in imported tags in a way which made them different from the tag separators. Anyway, I think this is going to be a big headache for people who want to migrate from F-spot to Shotwell if it isn't fixed. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: shotwell 0.7.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4 Uname: Linux 2.6.35-20-generic i686 Architecture: i386 Date: Tue Sep 14 20:02:32 2010 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1) ProcEnviron: LANG=en_DK.UTF-8 SHELL=/bin/bash SourcePackage: shotwell Binary package hint: shotwell This is a bug about the way Shotwell handles importing a batch of photos which have previously been managed by F-spot. In F-spot there is no problem with having commas in the tag names, so a tag like Surname, Firstname is fine. When this tag is imported into Shotwell it keeps the tag as Surname, Firstname but as soon as you apply it to anything creates two new tags one called Surname and one called Firstname. This quickly starts to make a real mess of my tagging system where I have lots of people in the Surname, Firstname format. Workarounds: * I can manually edit all the tags which include commas before I apply them to any pictures. But that assumes I'm aware of the problem in advance. * I can fix it up afterwards. But I can only remove tags from one picture at a time, tags can't be edited as a batch operation for some reason. Solutions: * What about if Shotwell collected all the tags and presented the ones including commas, explained the problem and asked that they be renamed. * Shotwell could use a different separator. * Shotwell might be able to encode commas found in imported tags in a way which made them different from the tag separators. Anyway, I think this is going to be a big headache for people who want to migrate from F-spot to Shotwell if it isn't fixed. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: shotwell 0.7.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4 Uname: Linux 2.6.35-20-generic i686 Architecture: i386 Date: Tue Sep 14 20:02:32 2010 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1) ProcEnviron:  LANG=en_DK.UTF-8  SHELL=/bin/bash SourcePackage: shotwell I've now manually upgraded to shotwell 8.1 and the issue is still there, just letting you know. But wow, fast pace of development and good looking application. I genuinely look forward to when I can make the switch.