Metadata characters encoding issue
-
Hi!
Please… How to handle IPTC metadata well with NextGEN? Why special characters (diacritic) are all corrupted?
[The same pictures goes correctly on NextGEN 1.9.13 on my other website.]
-
@ayek – Thanks for reporting this. I just tested it and this appears to be an existing issue we were not aware of.
I have added it to our developer notes for them to review.
– Cais.
…any good news?
@ayek – We’re still working on this and hope to have a more robust solution in our next (major) update.
Thanks!
– Cais.
I’ve applied JIN Weijie’s fix, and it works for me.
Found:foreach ($iptcTags as $key => $value) { if (isset ( $this->iptc_data[$key] ) ) $meta[$value] = trim(utf8_encode(implode(", ", $this->iptc_data[$key]))); }Replaced by:
foreach ($iptcTags as $key => $value) { if($this->iptc_data[$key]) $meta[$value] = mb_convert_encoding(implode(', ', $this->iptc_data[$key]), 'UTF-8', 'UTF-8'); }Now NGG gets and displays all diacritics and other special chars as they was written in IPTC meta 🙂
I haven’t checked this solution, but looks like it makes sense, what do you think?
BTW: Custom sorting by date/time doesn’t work for me (v. 2.0.66.33), although default sorting does.
@ayek – Thanks for sharing your find. I have updated our internal notes with this information. Once our developers have proven it out, or found a better solution we will have it included in the following update.
As to the second reference we will be looking into that as well.
Thanks, again!
– Cais.
The topic ‘Metadata characters encoding issue’ is closed to new replies.