cpesch
commented
3 years ago @KovalevArtem I can reproduce the problem here – on a Mac. So the problem is not Windows-related as suggested in the original issue https://github.com/hvdwolf/jExifToolGUI/issues/152
Besides that, I have no clue, what is the source of the problems.
Here they state
1st limitation: Officially, Exif supports ASCII characters only. However, Metadata Working Group (MWG) organisation recommends using UTF-8 charset in Exif. No problem with that, as long characters 32..126 are used. But as soon we use some foreign characters, then again, there's no guarantee, that these characters will be displayed correctly if another software is used -software might "expect" that characters conforms Exif specification (are ASCII only) and will thus decode foreign characters wrong!
So that's exactly the case here:
Something similar is already happening: To make use of foreign characters possible, today, most software uses ANSI charset when writting/reading Exif section. So, as long software makers don't change that, your foreign characters (encoded in UTF-8) won't be shown properly. Ok, there's one exception, where this limitation doesn't apply: UserComment tag. For this tag, foreign characters can be used officially, but I wouldn't say this makes a big difference in Exif usage. Conclusion: if you're from Poland, you should't put your name in Exif, because your friend in Germany might not be able to read it.
So now you're from Russia but the problem stays the same: to make sure all software can read the EXIF header, it has to be ASCII.
https://user-images.githubusercontent.com/36500228/133140976-42f88f9a-7319-4c2c-a3c9-35360ee1c6cc.mp4
Moscow_Original.jpg
Moscow_Edited_RouteConverterWindows_2.30.jpg
I understand perfectly well that this bug has practically NO effect on the operation of the RouteConverter. But, unfortunately, it strongly affects the work of jExifToolGUI. Therefore, the idea for solving this little problem here will greatly help in solving the big problem THERE.