I'm using ckeditor 3.4 to place data (text) to database after which display it on the page.

Problem: after i write (greek )within the ckeditor things are fine. After I press the HTML button from the ckeditor again things are fine (e.g. i begin to see the actuall text typed not html organizations). However, if I save the information (and therefore store these to the db) the saved data within the db are just like this

"<p style="text-align: center;">
    ... σÏντομα πεÏισσότεÏες πληÏοφοÏίες...</p>

Note: after i can remember the data the are properly displayed on the internet page.

Actions taken to date:

1- the bond file towards the db has got the following: $conn->query("SET NAMES 'utf8'");

2- Within the config.js from the ckeditor I've added the next lines

config.entities = false;
config.entities_greek = false;
config.entities_latin = false;
config.entities_processNumerical = false;
    // Define changes to default configuration here. For example:
     config.language = 'el';
    // config.uiColor = '#AADC6E';

3- my web pages are going to: content="text/html;charset=utf-8"

4- db colation: utf8_unicode_ci / type MyIsam

I have been looking around but no luck. I'd appreciate any help

Thanks all for the solutions. Solution was easier. The best writing is SET NAMES UTF8 rather than SET NAMES 'utf8'

If you work with PHP or other language that does not do that instantly, you have to invoke


around the connection before calling any claims, to be able to use UTF-8 inside your database.

Also make certain you're serving all pages as UTF-8 to ensure that published information is in UTF-8.

You will find several configuration parameters that controls the way the information is sent and processed through the server, but I have not handled to have it to operate without it statement.

se more here: http://dev.mysql.com/doc/refman/5.0/en/charset-connection.html

EDIT: Ah, sorry, did not observe that you really did this. If it's displayed properly whenever you output it as well as your charset is placed to UTF-8 around the page, then I am presuming that you simply only notice within the DB having a tool that does not support UTF-8, or is not set up for this? What exactly exactly may be the problem at this time?