Character set problem

[Harun Barış Bulut]

There is a really interesting character set problem with confluence. We are using Jira and Confluence together. Jira works fine but confluence works interesting;

What is happening is; when we create a page and write something in it and save, non-latin characters seem to be replaced with ? For instace with the word; Barış, it becomes -> Bar??. However when I want to edit it and click edit, I see the word as Barış which is fine. When I save again it becomes Barış which is also fine, but when I open again to edit it somehow wusiwyg form element shows it as Bar?? sometimes but again it shows it correct sometimes.

As this is happening almost like 1 times per 2 edit, it becomes annoying. I have edited database connection string to set collation utf8 as shows in your documentation, but it still makes this thing.

How do you think we can solve this ?

Thank you very much

[JohnA · Accepted solution]

Hi Harun,

It's good that you have configured the database to use UTF-8 but you should actually make sure all components are running using UTF-8 so please check the documents outlined below to ensure that your encoding scheme is consistent across your components:

Confluence encoding: https://confluence.atlassian.com/display/DOC/Configuring+Character+Encoding
Tomcat encoding: https://confluence.atlassian.com/display/DOC/Configuring+Tomcat%27s+URI+encoding
Database encoding: https://confluence.atlassian.com/display/DOC/Configuring+Database+Character+Encoding

You should also ensure that any proxies you have configured are passing all the data without disrupting the traffic as this can also cause problems such as the one you're seeing.

All the best,
John

[hsuhailah]

John has some points there and it seems that you are hitting this issue: https://confluence.atlassian.com/display/CONFKB/Characters+Appear+as+Question+Marks+Using+MySQL

You may need to set default-character-set=utf8, restart database and the server and see how it goes.

[Harun Barış Bulut]

Thanks Hanis, the problem was about all actually, our system admin somehow do everything wrong about collation. When we fix it, it started working correct.

Thanks