New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error reading metadata #51
Comments
Photini supports accented characters in metadata, with some restrictions. All modern image files should use UTF-8 encoding, which is what Photini writes. Photini attempts to read data using other encodings, but can't always succeed. This is partly due to a limitation in the PyGObject wrapper for libexiv - in Python 3 it decodes all strings with UTF-8, throwing an exception if that fails. Some data can be read as raw bytes and then decoded with other likely encodings (usually Latin-1) but not all. The error message alerts the user that their metadata might have been corrupted. It tells you which file and which data field ('description'). If you correct any errors and save the file it will be read without errors next time. If you can send me one of the problem files I can check it isn't using an encoding I haven't encountered before. I like to have a "rogues gallery" of problem files for testing. |
Where can you send the file ? |
You could attach it here (which would make it very public) or email it to me jim@jim-easterbrook.me.uk and I'll keep it private. |
I sent it to your email address with "Photini issue #51" for subject. |
Thanks - received and I'm already testing it. |
That's interesting. The problem is in the The "text" appears to be some other sort of data, with a lot of zero value bytes:
I'm not sure I'll be able to do anything useful with this. |
I think Photoshop I mentioned only because I pixelate faces. It comes from
an old Samsung smartphone. And has been manipulated using Picasa.
Le mar. 27 oct. 2020 à 11:46, Jim Easterbrook <notifications@github.com> a
écrit :
… That's interesting. The problem is in the Exif.Photo.UserComment value,
which was an early attempt by Exif to allow non-ascii characters in
metadata. The first 8 bytes are supposed to be the name of the character
set used, and in this example they are ASCII\x00\x00\x00. The file says
it was created by Adobe Photoshop, which I would have expected to do it
properly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#51 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADZAXT2A2SHYUH5DWN6DOT3SM2QHTANCNFSM4S2I57RA>
.
|
That |
Ah, I would have preferred to have the original image before any modification. It's very likely that Photoshop changed the metadata. (It certainly set |
See also drewnoakes/metadata-extractor#105 |
I've found some more examples on the web, and the data looks similar. Unless someone out there has reverse engineered this Samsung specific metadata I'm not planning to make any change to Photini. It does the best it can under the circumstances. |
I understand and thanks for your time. I think this issue should be closed as it's not related to Photini but related to Samsung. |
Do you have any Samsung software that might make use of this information? At present Photini will wipe the information when a user updates the "description" field, but if it's important then it should be preserved. |
In commit 1e7e707 I've added a warning to the user when |
When I click on some photos I have this error :
I suppose it's because there is maybe a 'ë' character in the metatdata. It's for the word 'Noël' which mean Christmas in French.
The text was updated successfully, but these errors were encountered: