| Summary: | Hierarchical Keywords | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | herb <herb.k> |
| Component: | Metadata-Xmp | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 7.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Other | ||
| Latest Commit: | Version Fixed/Implemented In: | 7.3.0 | |
| Sentry Crash Report: | |||
|
Description
herb
2021-04-02 14:06:39 UTC
>For digiKam:TagsList and MicrosoftPhoto:LastKeywordXM the separator character is >"/" and for the others it is "|". >Why does DigiKam use differnt characters? Interroperability : digiKam:TagsList -> internal uses, so we do do what we want. MicrosoftPhoto:LastKeywordXM -> to work with M$ tools. lr:hierarchicalSubject -> Light Room compatibility. etc. These namespaces are not standardized in XMP definitions. Each program can write data in private format, but of course using XMP containers/rules. The only section standardized in XMP are Exif, Iptc, Tiff, etc... >Which characters are used as separator when all tags of a file are read? The characters which is mostly used by the program generating data. It evaluated by reverse engineering, as these data are not standardized. The way that Xnview can customize the separator is a error which make a mess in metadata. It's already difficult to have an homogeneous contents everywhere, no need to customize extra format for tags... Best Gilles Caulier Gilles Caulier You can deactivate the default metadata tags in the advanced metadata settings and create your own with other separators. But as Gilles writes, you shouldn't do it if you want to exchange tags with other programs. Maik Hello, thanks for your comments. @maik: thanks for your private lession Best regards herb |