edge case: original filename too long #28
Comments
arewm
added a commit
to arewm/google-photos-exif
that referenced
this issue
Oct 15, 2022
Edge cases included: * .mp4 can use jpec and heic json files: mattwilson1024#26 * Counters may collide with other rules * Long filenames are truncated: mattwilson1024#28 * Some json files have .j and .jp as the media extension Signed-off-by: arewm <arewm@users.noreply.github.com>
arewm
added a commit
to arewm/google-photos-exif
that referenced
this issue
Oct 15, 2022
Edge cases included: * `.mp4 can use jpeg and heic json files: mattwilson1024#26 * Counters may collide with other rules * Long filenames are truncated: mattwilson1024#28 * Some json files have `.j` and `.jp` as the media extension Signed-off-by: arewm <arewm@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have many files in the original filename that is too long found in the JSON file like this:
01D1C847-D498-4814-9F10-6B81D768077B-1050-0000012BFC8FF17F_tmp.jpg(I have no idea why store the image and filename like this.)
when I was takeout, have two files like this:
01D1C847-D498-4814-9F10-6B81D768077B-1050-00000.jpg01D1C847-D498-4814-9F10-6B81D768077B-1050-0000.jsonI guess google does some operations like fixing the filename to 51 of character length.
After I ran the script, none of the files of this type successfully modified the metadata.
The text was updated successfully, but these errors were encountered: