When I put on MySql 4.1 last year we were suddenly faced with a situation where all Japanese code was crippled. We are running Japanese in UTF-8 and of course the internal code was set to LATIN1-sweden. So, when the database was dumped the MySql was assuming that the data is in Latin1 and produced a mess.
At that time a wrote a small conversion utility and also changed the character set using "SET NAMES 'UTF8' " in pnAPI.
Recently I installed PN 800 M3 and surely the character set was again Latin1. So, I had to convert again.
I checked pnAPI and the Adodb code and it seems that the mysqli driver has a function 'SetCharSet'.
Would it be possible to add a variable to the installation dialog asking for the character set to be used?
Alternatively, where could I add this manually to the PN code?
Any comments are appreciated!
Thanks,
Bernd
Watch
GitHub Core
Show your support for Zikula! Sign up at Github account and watch the Core project!
GitHub Modules
Forum Activity
- mazdev responded to »Hide "Register new account" and change template to 3 col« 07:50 AM
- mesteele101 created topic »Zikula 1.3.3 - Site Search 1.5.2 - Unable to turn off plug-ins« 07:48 AM
- internetking created topic »password problem« 25. May
- mesteele101 responded to »ERR (3): E_USER_ERROR: Smarty error: [in pagesvar:pagesitem2en line XXX]…« 25. May
- mazdev responded to »Pages 2.5.0 and updating - Page not found« 25. May
- mesteele101 responded to »Zikula 1.3.3 - Selecting a category in Pages not working« 25. May
- mdee created topic »How to implement returnpage ?« 25. May
Zikula Blog
- Anatomy of Open Source Projects on Mar 07
- Continuous Review on Mar 01
- Not Invented Here on Feb 24
- How to Contribute Your Code at Github on Jan 13
- 10 Steps to Coding-Nirvana: Tips for Successful Module Writing on Nov 12
- Submitting Bug Report Tickets That Get Results on Aug 17
- Cozi Tricks #1: Syntax Highlighting on Aug 07
Login
UTF-8 support
-
- Rank: Registered User
- Registered: Jun 19, 2003
- Last visit: Oct 21, 2009
- Posts: 32
Posted: Mar 14, 2007 - 03:23 AM
-
**unknown user**
- Rank: Senior
- Registered: Mar 16, 2002
- Last visit: Oct 21, 2009
- Posts: 2204
Posted: Mar 14, 2007 - 12:59 PM
+1 for that request :) -
- Rank: Software Foundation
- Registered: Sep 03, 2002
- Last visit: May 09, 2010
- Posts: 909
Posted: Mar 15, 2007 - 03:17 AM
There is a German manual about how to convert Postnuke to UTF-8 (http://support.pn-cms.de/Article1036.htm)
UTF-8 will not be part of .8 as there are all ready a lot of new things in .8. But I am sure that UTF-8 is on the devs mental roadmap.
--
best regards from Kiel, sailing city
Steffen Voss
Member of the Zikula Steering Committee
Read The Zikulan's Blog "If you want people to RTFM, make a better FM!" -
- Rank: Registered User
- Registered: Jun 19, 2003
- Last visit: Oct 21, 2009
- Posts: 32
Posted: Mar 15, 2007 - 01:22 PM
We are using English and Japanese. Japanese has been produced by recoding from the EUC version. English is no problem anyway. German etc requires recoding for special characters to work.
We have been running PN in UTF-8 since about 2003 - so that is not the problem.
However, ever since MySQL started to include character set support PN gets installed with the wrong character set for all tables. That's why we have to (manually) convert the database tables. We have a simple tool for this (which works not 100% but 95%) and maybe I should make it available.
What I was asking for is a possibility to set the default charset (UTF-8 instead of ISO-8859-1) during the installation.
Thanks,
Bernd
- Moderated by:
- Support
