https://bugs.kde.org/show_bug.cgi?id=438888
--- Comment #21 from herb <[email protected]> --- (In reply to caulier.gilles from comment #20) > >I guess option -charset iptc=utf8 is missing in the command you used. > > This will work in your case as you know that your IPTC is UFT8 encoded. > > But it's not so far universal. IPTC can be encoded with other encoding. This > si why there is a tag dedicated to identify the encoding for this container. > > What's happen if another image is not encoded as UTF8 in IPTC. The decoding > will be broken if we force UTF8 with ExifTool argument. > > This is why IPTC encoding tag is highly recommended. It's identify which > encoding is used in one image. This is what we call interoperability. Yes you are right. But: (1) Exiftool uses the following coding rule: (see FAQ 10): The value of the IPTC:CodedCharacterSet tag determines how the internal IPTC string values are interpreted. If CodedCharacterSet exists and has a value of "UTF8" (or "ESC % G") then string values are assumed to be stored as UTF‑8. Otherwise the internal IPTC encoding is assumed to be Windows Latin1 (cp1252), but this can be changed with "-charset iptc=CHARSET". For me it is better to start Exiftool with -charset iptc=utf8 than using the above mentioned rule. (2) In tab "IPTC" of metadata panel all tagsvalues are displayed properly; so Exiv2 must know that they are UTF8 encoded. Who gives this information? Does Exiv2 really support all possible encoding given in CodedCharacterSet? Best regards herb -- You are receiving this mail because: You are watching all bug changes.
