Your database can have any given encoding, also the database connection - both actually do not matter. However, your database tables and the content needs to be encoded in
UTF-8, as do all language files and all templates. There are several tools around to do that, depending on the operating system used and your console skills. You do not need to convert file names, just the content of those files. You should convert file names of uploaded files, though.
Be careful with mixed encoded content (which you might find in news, comments, forums,
PM, etc.), you need to do the conversion there manually. That can easily become quite a lot of work, so for bigger sites seriously consider to create a public read only archive of the site, and start a new one in
UTF-8.
The file language/$yourlanguage/core.php needs the change already described above, and you need to do that for all languages! Also the file /config/config.php needs editing as described above. But: No other core files need to be hacked in Zikula 1.1.x, specially not includes/pnAPI.php (if that would be needed a bug report should instead be filed in
Cozi).
Empty pnTemp/Xanthia_cache and pnTemp/pnRender_cache.
Your milage may vary with some more complex
3rd party modules/blocks/themes, some optionally already might provide
UTF-8 language files, while others need manual fixing. You need to take special care for RSS feeds and all content which might be shown where
UTF-8 is not available.
Starting with 1.2.0 Zikula will default to
UTF-8.
Last word: Browsers need to be able to auto-detect and show
UTF-8, and your operating system needs
UTF-8 fonts ready for that. Both is true for most modern browsers and operating systems, though, but do not forget this when developing for big organisations.
Greetings,
Chris
--
an operating system must operate
development is life
my repo