user Tags are "UnknownToMe" - feature request

[yuribudilov]

Hello.

This is a feature request, not a bug/problem.

Reading the JPEG (.JPG) files your crate picks up "User Tags" but reports them as follows (sample output of Rust println!())

pub fn get_all_rexif(re: &rexif::ExifData) {
    for e in &re.entries {
        // println!("{:?}", e);
        println!(
            "tag:{:?} value:{:?} value_more_readable:{:?} unit:{:?}",
            e.tag, e.value, e.value_more_readable, e.unit
        );
    }
}

tag: UnknownToMe
value: U8([89, 0, 117, 0, 114, 0, 105, 0, 59, 0, 80, 0, 97, 0, 114, 0, 105, 0, 115, 0, 59, 0, 70, 0, 114, 0, 97, 0, 110, 0, 99, 0, 101, 0, 0, 0])
value_more_readable: "89011701140105059080097011401050115059070011409701100990101000"
unit: "Unknown unit"

The above Tags are (in ASCII): Yuri;Paris;France

As you see there is a byte-0 after each ASCII character in above output, perhaps this is due to UTF-8 or some other reason, I dont know.

Anyhow, if this project is still active perhaps you can consider adding the retrieval of User Tags for the JPG files (photos).

The rest of this rexit crate is working very well for me.
I was able to extra GPS Latitude and Longitude and Image Date-Time for over >10,000 JPG files correctly, very useful.

Thank you very much!

[elvis-epx]

Will take a look. The string looks 16-bit Unicode (UTF-16LE).

[yuribudilov]

A bit more info: I am running it on Windows-10, with JPG files copied from my Android mobile/cell phone and then I used Windows-10 properties to Add use Tags to JPG file manually. In future I hope to do this via a Rust program too. This "update/write" EXIF data in JPG file I will have to do using some other Rust or C++ library because the rexif crate is read-only access. If you are aware of any Rust crates or C/C++ libraries that will allow me to write/append/update tag values into JPG file, please advise. I am very new to JPG file processing.

[elvis-epx]

Can you attach a JPG with the User Tags mentioned in opening post?

[polarathene]

Just curious, since @elvis-epx is actively commenting here and the crate links to a forked repo where the latest version seems to be matched.. is this repo going to continue development or is the discussed fix here to go into the fork? (which lacks an issues section)