https://bugs.kde.org/show_bug.cgi?id=517111
--- Comment #4 from Living Creatures <[email protected]> --- Thanks. Meanwhile, I've located the source of the issue I was experiencing and seem to have answered my own question about the format of the imported text file that digikam can accept. For the latter, am I correct in assuming that the only format that digikam accepts for an imported tag/keyword hierarchy is a UTF-8 encoded, tab delimited, plain text file with indents to define the hierarchy? Example: Term 1 Sub-term 1 Sub-term 2 Sub-term 3 Sub-term Term 2 Sub-term In my case, the imported file I was using contained lines with characters that causes digikam to ignore the entire line, e.g. [ and { In the case of square brackets, these are typically considered non-exporting terms. In the case of the curly brackets, in a typical controlled vocabulary, these are considered synonyms of the previous term. Example: Dog {Canine} Removing these characters from the file I was importing changes the structure of the imported hierarchy, but otherwise eliminates the behavior I was observing. Thus, I don't consider this a bug; digikam doesn't currently support this behavior. Hence my question about documenting the format of what digikam expects for the imported vocabulary. -- You are receiving this mail because: You are watching all bug changes.
