[solved] MessageTemplates with wrong Characters

Hi Anton,
I had to implement several messagetemplates for several users, so I decided to do it directly in the database. the templates are available to all the users as desired, but with special characters I have some issues. German umlauts (ä,ö,ü…) are correctly stored in the playsms-database, but in the web frontend they are shown wrong and are sent as sms in the same way as they are shown in the GUI…
any hint?

regards,
andre

what do you mean by “do it directly in the database” ?

anton

i connected to the mysql-db “playsms” and isnerted the data into table …featureMsgTemplate.

the insert was running fine, data is available. i have only a mismatch of special characters (on linux-level -> connect to database -> view data: everything fine; having a look to the templates via playsms-gui, i have wrong “translation” of those characters.
example:
database: | 0 | 507 | 28 | Strom_Entstoer_intern | ENTSTÖRUNG
playsms-gui: Strom_Entstoer_intern ENTSTÖRUNG

mysql> SELECT DEFAULT_CHARACTER_SET_NAME, DEFAULT_COLLATION_NAME
-> FROM INFORMATION_SCHEMA.SCHEMATA WHERE SCHEMA_NAME = ‘playsms’;
±---------------------------±-----------------------+
| DEFAULT_CHARACTER_SET_NAME | DEFAULT_COLLATION_NAME |
±---------------------------±-----------------------+
| latin1 | latin1_swedish_ci |
±---------------------------±-----------------------+
1 row in set (0.00 sec)

Hi,

I added it form web and this is what I got:

playSMS web gui:

in db:

collation:

do you use playsms 1.4? i am using 1.3.1… maybe something has changed there. or is it possible to change character encoding of playsms-web

i did the same test as you, and in db i get another result:
| 0 | 59 | 3 | Strom_Entstoer_intern | ENTSTÖRUNG Die IHK kann seit XX:XX Uhr wieder in
| 0 | 508 | 3 | Strom_TEST | Bitt▒ N▒cht ben▒tzen! ▒ - ▒ - ▒

maybe my unix-environment, where i inserted the entries into the database, is not well configured.

my locales look quite ok:
[playsms01:gro] /opt/playsms/web> locale
LANG=de_DE.UTF-8
LC_CTYPE="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_PAPER="de_DE.UTF-8"
LC_NAME="de_DE.UTF-8"
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=

hi anton,
I was able to solve the issue by manually convert my sql-script to iso-8859-1 and then execute it.
So the problem was related to charctersets…
regards,
andre