Hi Szurkebarat, please check with your customer what does their app read - ie the old Legacy IPTC, or IPTC/XML. If XML, there is a good chance it will work with UTF8 encoding. However, Legacy IPTC doesn't specify encodings, and allows only Ansi standard. Therefore, most national newspapers and software vendors needing to put their languages' characters in IPTC way back before IPTC/XML was introduced, simply used their own national and OS encoding. Which can be quite a pitfal because as it is NOT specified inside Legacy IPTC which encoding is used, some apps expect Ansi, some expect same encoding as the OS they run on, and some are completely custom... I had a same problem with one client, whose legacy system doesn't accept anything else then Windows Central European, and accepts only Legacy IPTC. Fortunately in Photomechanic it's easy to set the encoding even for such situations, just that you might have to try few different options before you arrive at the right solution (as I assume, customers with legacy systems usually don't know anything about the technicalities which were implemented by their long-gone-IT dept 10 years ago or outsourced entirely "and it just worked" because their photographers were forced to use their own tools).