https://bugs.kde.org/show_bug.cgi?id=278935
--- Comment #26 from glenn <gl...@dazedowl.uk> --- Thanks for your quick response Maik. So digiKam will default to reading and writing to $BASENAME.xmp if it finds one already existing. That's very helpful to know. This still presents a problem for a typical use case, where the user imports and manages new images through digiKam but processes the RAW files in (say) Capture One. In this case digiKam will create $BASENAME.EXT.xmp files, which Capture One will not be aware of. A common workflow would be rating newly imported images in digiKam, and sorting by these in Capture One for editing (and even changing the ratings or some other metadata in the RAW processor. eg to indicate editing complete and ready for printing). It remains the case that user control over xmp file naming would be very helpful and open digiKam to other users. -- You are receiving this mail because: You are watching all bug changes.
