| Summary: | Problem with Tag when Advanced Metadata panel set two different metadatas for Tags as input | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | mahikeulbody <51mfxqck> |
| Component: | Metadata-Xmp | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 8.2.0 | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 8.3.0 | |
| Sentry Crash Report: | |||
|
Description
mahikeulbody
2024-02-12 11:14:24 UTC
Yes it is. You seem to be having some strange problem. Please provide the image with which it occurs and a log of the reading process of the image. Otherwise we can't help as we can't reproduce it. Maik Note that xmp.dc.subject does not contain a tag path (I consider xmp.dc.subject unsuitable for tags), which means that if the tag name is somewhere in a deeper tag hierarchy, it will not be added. Maik (In reply to Maik Qualmann from comment #1) > Yes it is. You seem to be having some strange problem. I think so... I can't reproduce :-( I will retry from the beginning but may be I will have to admit a no sufficient rigorous testing process before to write a report. Sorry in advance if it is the case here. > Note that xmp.dc.subject does not contain a tag path (I consider xmp.dc.subject unsuitable for tags), which means that if the tag name is somewhere in a deeper tag hierarchy, it will not be added. At least, I have learned this important point. Thanks ! |