https://bugs.kde.org/show_bug.cgi?id=402288
--- Comment #5 from Daniel Laidig <lai...@kde.org> --- I was testing with the 6.2.0 Appimage. Thanks for the info that I can add the same namespace multiple times. This is certainly an improvement for my current setup. :) When looking at the default config for Xmp.lr.hierarchicalSubject, I noticed that Xmp.lr.hierarchicalSubject is set to TAG_XMPBAG and the alternative name is Xmp.lr.HierarchicalSubject (capitalized) as TAG_XMPSEQ. From what I understand now, this looks digikam always write the non-capitalized version only (as Bag) and if not found during reading, it will try to read the capitalized version as Seq only. Considering that you wrote in comment 1 that you use the "capitalized alternative Xmp.lr.HierarchicalSubject as Seq" (which seems not the current behavior any more), doesn't that mean there is another issue and digikam might not be able to read tags from its own sidecars from older versions any more? In any case, while I very much appreciate your comments that help me configure digikam to be usable for my workflow, I would be very happy if out-of-the-box compatibility between digikam and other applications is as high as possible. I guess this would either mean making the reading more fault tolerant or adding another default entry. Is as good as possible out-of-the-box compatibility with darktable and other applications also something you are aiming for or is this something where I should just tune my config? -- You are receiving this mail because: You are watching all bug changes.
