On 10 September 2011 12:13, Bruno Girin <[email protected]> wrote: > Piergi, > > What would be really useful to help understand and fix the problem is if you > could provide us with an example. Take one of your photos and provide us > with the following info: > * The tag hierarchy in F-Spot,
http://traversin.org/shotwell-test/FSpotScreenshot.png > * The tag entries in the photo metadata, http://traversin.org/shotwell-test/BeforeImport.txt > * The resulting tag hierarchy when you import that photo from F-Spot to > Shotwell, http://traversin.org/shotwell-test/AfterImport.txt http://traversin.org/shotwell-test/AfterImportScreenshot.png > * What you would have expected the tag hierarchy to be in Shotwell (i.e. > where did it go wrong). In the words of the ticket #4081: 'When Shotwell imports from the F-Spot database, it will create two copies of each hierarchical tag: one inside the tag hierarchy and one at top level.' Well, it still do in version 0.11.1. I know that English is not my first language, but what I am trying to say is just that what is happening is what is described in the ticket. As in 'not-fixed'. That's what I did: A very simple f-spot database (three photos, see screenshot) exiftool -all:all * > BeforeImport.txt Import in shotwell (see screenshot): shotwell added the children tags both in the correct hierarchy and as top-level tags. exiftool -all:all * > AfterImport.txt Any clue? I've put the three photos (after the shotwell import) in the same directory with a csv version of the output of exiftool as well: http://traversin.org/shotwell-test/ Ciao ciao, Piergi -- Web: http://traversin.org GNU/Linux user 190604 _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
