Problems with special characters in metadata

577 views
Skip to first unread message

Jan Köster

unread,
Oct 26, 2013, 5:44:45 AM10/26/13
to resourcespace
Some of my picture do have keywords or descriptions containing special
characters. These are German Umlaute like (äöü) and ß. While having such
a character in the "author" field is no problem ("Jan Köster" gets
imported properly ) other metadata are a problem.
When importing using staticsync keywords or decription get cut on the
position of the special character. "Aufführung" gets inserted to the
database as "Auff". The database charset is set to utf-8, the mysql
connection settings are set to utf-8. On the cli exiftool is diplaying
the metadata correctly.
I guess the metadata extracted from iptc fields is not stored as utf-8
in the image and won't be converted to utf-8 during import - so it can't
get stored properly. But I'm not sure about that.
Is there any possibility to change that behaviour?

(Example file:
https://owncloud.cbjck.de/public.php?service=files&t=b0ee376aea9d8ccfc1f3b112812cd373)

Jan Köster

unread,
Nov 9, 2013, 5:11:00 AM11/9/13
to resour...@googlegroups.com

I can't search for keywords or descriptions containing special
characters. Take an image with the following description:
"Aufführung - Workshop Klassisches Ballett - Études.Choreographie: Mark
McClain"
It will be found if I search for "Workshop Klassisches Ballett" (which
is not stored in any other field). But it won't be found when I search
for "Aufführung".
Looking into the mysql table it is stored correctly and when performing
the search by an SQL statement in the database istelf the image will be
found.

in my config.php
> $mysql_charset="utf8";
is set, so I don't really see a reason why this shouldn't work.
Any ideas?

mkl

unread,
Nov 23, 2013, 8:44:12 AM11/23/13
to resour...@googlegroups.com, koest...@gmx.net
Hi there,

which version are you running?
I've tested it on two of my installations 3726 (which I run productive atm) and the newest release 5120.

On 3726 everything works like suggested with your testfile.
On 5120 search and storing in database works fine, but the displaying of the value fails with showing ? instead of the correct umlaut.

my database is on latin1_swedish_ci and nothing special to encoding is set in the config.php.

what I wonder about is the different behaviour of 3726 vs. 5120...

regards,
matthias

Jan Köster

unread,
Jan 9, 2014, 8:58:10 AM1/9/14
to resour...@googlegroups.com
Hi,

sorry for not answering for such a long time.

Currently I'm running 5174.
If I set encoding in the config, the umlaut is displayed correctly, if I
don't the word gets cut at the umaut. So quite similiar behaviour like
yours.

Search is still not working with umlaut.

Regards
Jan
> --
> ResourceSpace: Open Source Digital Asset Management
> http://www.resourcespace.org
> ---
> You received this message because you are subscribed to the Google
> Groups "ResourceSpace" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to resourcespac...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.


Flusel

unread,
Jan 20, 2014, 3:23:57 AM1/20/14
to resour...@googlegroups.com, koest...@gmx.net
Same issue using 'Smart Themes'. Items with german umlaute are not displayed in the list.

Any hint?

Yours, Torsten
Reply all
Reply to author
Forward
0 new messages