You are viewing the PKP Support Forum | PKP Home Wiki

character encoding problem

Are you responsible for making OJS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.

Moderators: jmacgreg, btbell, michael, bdgregg, barbarah, asmecher

Forum rules
What to do if you have a technical problem with OJS:

1. Search the forum. You can do this from the Advanced Search Page or from our Google Custom Search, which will search the entire PKP site. If you are encountering an error, we especially recommend searching the forum for said error.

2. Check the FAQ to see if your question or error has already been resolved.

3. Post a question, but please, only after trying the above two solutions. If it's a workflow or usability question you should probably post to the OJS Editorial Support and Discussion subforum; if you have a development question, try the OJS Development subforum.

character encoding problem

Postby viat » Mon Feb 03, 2014 9:06 am


We had the problems with the character encoding during migration from 2.3.5 to 2.4.2.

Similar problems took place during migration from one server to another for OJS version 2.3.5.

I wonder when the settings from the configuration file have impact on the encoding

; Localization Settings ;


; Default locale
locale = ru_RU

; Client output/input character set
client_charset =utf-8

; Database connection character set
; Must be set to "Off" if not supported by the database server
; If enabled, must be the same character set as "client_charset"
; (although the actual name may differ slightly depending on the server)
connection_charset = utf-8

; Database storage character set
; Must be set to "Off" if not supported by the database server
database_charset = utf-8

; Enable character normalization to utf-8 (recommended)
; If disabled, strings will be passed through in their native encoding
; Note that client_charset and database collation must be set
; to "utf-8" for this to work, as characters are stored in utf-8
charset_normalization = Off

a) during upgrade
b) dirung rinning installed version
c) for both cases.

Posts: 8
Joined: Tue Jan 28, 2014 2:31 am

Re: character encoding problem

Postby asmecher » Mon Feb 03, 2014 1:04 pm

Hi Viat,

Can you describe the problem?

Did you dump and restore the database as part of the process? If so, sometimes it's necessary to specify --default-character-set=utf8 to mysqldump/mysql in order to preserve character set configuration.

Alec Smecher
Public Knowledge Project Team
Posts: 9920
Joined: Wed Aug 10, 2005 12:56 pm

Return to OJS Technical Support

Who is online

Users browsing this forum: Bing [Bot], roball and 7 guests