Version: 0.9.3 (using KDE 3.5.9) OS: Linux Installed from: Ubuntu Packages When I build a hirachy in my keyword list for example: place/canada/toronto/CN-Tower and if I then for example check the Tag 'CN-Tower', it only shows 'CN-Tower' underneath the picture but in the metadata I find 'place/canada/toronto/CN-Tower'. When I now export my image to flickr: this hirachy is recognized as Tag because that is what it says in the keyword field. But this doesn't look very nice. I have seen a tutorial about lightroom and there you can decide for every keyword if the one above it is also embedded into the image. I could e.g. only check CN-Tower but also the words 'toronto' and 'canada' are embedded into the metadata. Not 'place' (this isn't a very usefull Tag). Also it would be nice to have such a complicated feature like I described it is not to important, but I would really like to have rather single words than a hirachy tree as Keyword. For my case this would mean to have the keywords: canada toronto CN-Tower instead of canada/toronto/CN-Tower as one keyword. I am new to Bugzilla so please forgive me any major mistake I made. What do you think of this suggestion. Cheers Dominik
Dominik, All is already implemented in digiKam for KDE4. Nothing is done in KDE3, and nothing will be done. Let's me explain why: In KDE4, we support XMP metadata. in XMP, we have declared a digiKam namespace where we store tags path list, to be able to recreate tags hierarchy inot database if image is moved to another computer. IPTC still supported but now IPTC keywords records only tags name, not tags path. In KDE3, XMP is not supported, only Exif and IPTC. There is no others place in IPTC, excepted keywords to record tags path. so, we will still use it to be able to recreate tags hierarchy in database if image is moved. XMP support will be not backported to KDE3. it require huge changes in the code and a lots of regression tests. All is already done in KDE4 version. that all... Gilles Caulier
Thx for your answer. Makes sense. So I can't wait for the new version now :-) Dominik